[pgrouting-users] Shortest Path Shooting-Star Ignore Reverse Cost
Jorge Eliécer Osorio Caro
jorgeliecer.osorio at gmail.com
Mon Jan 30 14:30:19 EST 2012
Im having a issue when try to calculate the shortest path using turn
restricctions this functions ignores the reverse_cost param.
here the SQL:
SELECT
*
FROM
shortest_path_shooting_star(
'SELECT
routing.network.segment as id,
routing.network.source,
routing.network.target,
routing.network.length as cost,
routing.network.reverse_length as reverse_cost,
routing.network.x1,
routing.network.y1,
routing.network.x2,
routing.network.y2,
routing.network.rule,
routing.network.to_cost
FROM
routing.network',
-- node_from, node_to
15365,
15366,
--15242,
false, -- directed
true -- reverse_cost
)
this generate that route:
http://cl.ly/242E2T0A2C410F1S0F3g
that method generate the route but it ignores the one_way restriction , the
restriction is ok, but take a route where ignores that.
now in the next image i need the marked red lines are the correct route
because the 15229 and 15228 has both ways.
http://cl.ly/3t2O38343F0F0C0o3P2c
here how look my table:
id source target cost reverse:cost rule to_cost x1, y1, x2, y2
15245 9082 9150 0.02 100.00021 15214 101.00021 -74.79981 10.94605 -74.7996
10.94605
how i cant fix that i compiled the last version of pgrouting from git repo.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.osgeo.org/pipermail/pgrouting-users/attachments/20120130/41431e0c/attachment.html
More information about the Pgrouting-users
mailing list