Thanks Steve for you request i testing the new branch tos see what happend.<br><br><div class="gmail_quote">2012/1/30 Stephen Woodbridge <span dir="ltr"><<a href="mailto:woodbri@swoodbridge.com">woodbri@swoodbridge.com</a>></span><br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Jorge,<br>
<br>
I have posted a few times on this problem, you can check the archives. The short story is the shooting star is broken. I think the last version that worked is 1.03. In my posts is also some information on a new algorithm turn_restricted_shortest_path (trsp) that is in a branch. The current code in a git branch works but is likely to see changes before it is released, but we do not have a release plan yet.<br>
<br>
-Steve<br>
<br>
On 1/30/2012 2:30 PM, Jorge Eliécer Osorio Caro wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Im having a issue when try to calculate the shortest path using turn<br>
restricctions this functions ignores the reverse_cost param.<br>
<br>
here the SQL:<br>
<br>
|SELECT<br>
<br>
*<br>
<br>
FROM<br>
<br>
shortest_path_shooting_star(<br>
<br>
'SELECT<br>
<br>
<br>
routing.network.segment as id,<br>
routing.network.source,<br>
routing.network.target,<br>
routing.network.length as cost,<br>
routing.network.reverse_length as reverse_cost,<br>
<br>
<br>
routing.network.x1,<br>
routing.network.y1,<br>
routing.network.x2,<br>
routing.network.y2,<br>
<br>
routing.network.rule,<br>
routing.network.to_cost<br>
<br>
<br>
FROM<br>
routing.network',<br>
<br>
<br>
-- node_from, node_to<br>
<br>
15365,<br>
<br>
15366,<br>
<br>
--15242,<br>
<br>
<br>
false, -- directed<br>
<br>
true-- reverse_cost<br>
<br>
)<br>
<br>
|<br>
<br>
this generate that route:<br>
<br>
<a href="http://cl.ly/242E2T0A2C410F1S0F3g" target="_blank">http://cl.ly/<u></u>242E2T0A2C410F1S0F3g</a><br>
<br>
that method generate the route but it ignores the one_way restriction ,<br>
the restriction is ok, but take a route where ignores that.<br>
<br>
now in the next image i need the marked red lines are the correct route<br>
because the 15229 and 15228 has both ways.<br>
<br>
<a href="http://cl.ly/3t2O38343F0F0C0o3P2c" target="_blank">http://cl.ly/<u></u>3t2O38343F0F0C0o3P2c</a><br>
<br>
here how look my table:<br>
<br>
id source target cost reverse:cost rule to_cost x1, y1, x2, y2<br>
15245 9082 9150 0.02 100.00021 15214 101.00021 -74.79981 10.94605<br>
-74.7996 10.94605<br>
<br>
how i cant fix that i compiled the last version of pgrouting from git repo.<br>
<br>
<br>
<br>
______________________________<u></u>_________________<br>
Pgrouting-users mailing list<br>
<a href="mailto:Pgrouting-users@lists.osgeo.org" target="_blank">Pgrouting-users@lists.osgeo.<u></u>org</a><br>
<a href="http://lists.osgeo.org/mailman/listinfo/pgrouting-users" target="_blank">http://lists.osgeo.org/<u></u>mailman/listinfo/pgrouting-<u></u>users</a><br>
</blockquote>
<br>
______________________________<u></u>_________________<br>
Pgrouting-users mailing list<br>
<a href="mailto:Pgrouting-users@lists.osgeo.org" target="_blank">Pgrouting-users@lists.osgeo.<u></u>org</a><br>
<a href="http://lists.osgeo.org/mailman/listinfo/pgrouting-users" target="_blank">http://lists.osgeo.org/<u></u>mailman/listinfo/pgrouting-<u></u>users</a><br>
</blockquote></div><br>