[pgrouting-users] Shooting star problem
Espen Isaksen
espen.isaksen at gmail.com
Mon Dec 20 04:50:32 EST 2010
Hi!
I am running the following query:
SELECT gid
FROM shootingstar_sp('elveg',157332,157333,100, 'cost', true, true);
and I get:
gid
--------
157332
157333
(2 rows)
which seems correct. Now if i flip the direction with the this query:
SELECT gid
FROM shootingstar_sp('elveg',157333,157332,100, 'cost', true, true)
then I get:
gid
--------
157333
159163
155337
155336
158776
157332
(6 rows)
which is not correct. There should not be any extra costs on the edges:
gid | cost | reverse_cost | to_cost | rule
--------+------------------+------------------+---------+------
157332 | 61.7253486704361 | 61.7253486704361 | |
157333 | 104.8033 | 104.8033 | |
(2 rows)
>From my understanding I should get 2 rows in both queries. Am I
missing something here?
If I decrease the bounding box in the second query to 10, then I get
this result:
gid
--------
157333
157333
157332
(3 rows)
I thought I should get the same result for a larger bounding box as
long as the shortest path(least cost) is within the smallest bounding
box?
Image of the road network can be seen here:
http://dl.dropbox.com/u/8829/road_network.png
Espen
More information about the Pgrouting-users
mailing list