I was wondering if someone could help me. I have pgrouting working
and producing routes using both Dijkstra and AStar, but the edges that
are returned by the SQL are in the wrong order... not the order of the
edges as you expect to move through the route from start to finish...
eg: (using a short example)
If I have a route of ten edges, from start edge 1 to finish edge 10 -
I would expect the results to be: 1, 2, 3, 4, 5, 6, 7, 8, 9, 10 (using
the id column that is returned from the sql)
However, the results are more like 3, 6, 2, 8, 1, 9, 4, 7, 10, 5.
Is this supposed to happen? Is there a way to return the results in
the order you traverse through the route?
I was wondering if someone could help me. I have pgrouting working
and producing routes using both Dijkstra and AStar, but the edges that
are returned by the SQL are in the wrong order… not the order of the
edges as you expect to move through the route from start to finish…
eg: (using a short example)
If I have a route of ten edges, from start edge 1 to finish edge 10 -
I would expect the results to be: 1, 2, 3, 4, 5, 6, 7, 8, 9, 10 (using
the id column that is returned from the sql)
However, the results are more like 3, 6, 2, 8, 1, 9, 4, 7, 10, 5.
Is this supposed to happen? Is there a way to return the results in
the order you traverse through the route?
On 29 November 2010 18:30, Daniel Kastl <daniel@georepublic.de> wrote:
Hi Madison,
Could you send me your routing query to see how it looks like?
Daniel
2010/11/30 Madison Shaw <madisonshaw@googlemail.com>
Hi There,
I was wondering if someone could help me. I have pgrouting working
and producing routes using both Dijkstra and AStar, but the edges that
are returned by the SQL are in the wrong order... not the order of the
edges as you expect to move through the route from start to finish...
eg: (using a short example)
If I have a route of ten edges, from start edge 1 to finish edge 10 -
I would expect the results to be: 1, 2, 3, 4, 5, 6, 7, 8, 9, 10 (using
the id column that is returned from the sql)
However, the results are more like 3, 6, 2, 8, 1, 9, 4, 7, 10, 5.
Is this supposed to happen? Is there a way to return the results in
the order you traverse through the route?
SELECT gid, astext(the_geom) FROM dijkstra_sp_delta('roads',1,400,0.1)
Also in dijkstra you pass vertex nodes 1 and 400 BUT you get back edges in the order of traversal. The tricky part is that the edge is return as loaded and NOT as traversed, so you need to do some checking and flip those segments that were traversed backwards from the disrtion that they were loaded.
-Steve W
On 11/29/2010 1:46 PM, Madison Shaw wrote:
Hi Daniel,
Thanks for the quick reply, my SQL statement and its results are below
(with pre selected start and finish points for ease of illustrating my
issue)
As you can see, the edge (gid) that we start from '1' is given the id of 29.
SELECT gid, the_geom FROM dijkstra_sp_delta('roads',1,400,0.1)
On 29 November 2010 18:30, Daniel Kastl<daniel@georepublic.de> wrote:
Hi Madison,
Could you send me your routing query to see how it looks like?
Daniel
2010/11/30 Madison Shaw<madisonshaw@googlemail.com>
Hi There,
I was wondering if someone could help me. I have pgrouting working
and producing routes using both Dijkstra and AStar, but the edges that
are returned by the SQL are in the wrong order... not the order of the
edges as you expect to move through the route from start to finish...
eg: (using a short example)
If I have a route of ten edges, from start edge 1 to finish edge 10 -
I would expect the results to be: 1, 2, 3, 4, 5, 6, 7, 8, 9, 10 (using
the id column that is returned from the sql)
However, the results are more like 3, 6, 2, 8, 1, 9, 4, 7, 10, 5.
Is this supposed to happen? Is there a way to return the results in
the order you traverse through the route?
The query I use within my php script returns a geojson.
I'm sorry I still don't completely understand why the results don't
come back in order... I realise that I may need to flip edges due to
the traversing backwards, but at the moment it looks like I need to
completely loop through everything to reorder it as well. I have
attached a jpg of how it actually looks for the start of the route
with reference to the sql results.
Also if you are writing these loops is it best to do it in the php script?
Cheers
Madison
On 29 November 2010 19:54, Stephen Woodbridge <woodbri@swoodbridge.com> wrote:
A more useful query would be:
SELECT gid, astext(the_geom) FROM dijkstra_sp_delta('roads',1,400,0.1)
Also in dijkstra you pass vertex nodes 1 and 400 BUT you get back edges in
the order of traversal. The tricky part is that the edge is return as loaded
and NOT as traversed, so you need to do some checking and flip those
segments that were traversed backwards from the disrtion that they were
loaded.
-Steve W
On 11/29/2010 1:46 PM, Madison Shaw wrote:
Hi Daniel,
Thanks for the quick reply, my SQL statement and its results are below
(with pre selected start and finish points for ease of illustrating my
issue)
As you can see, the edge (gid) that we start from '1' is given the id of
29.
SELECT gid, the_geom FROM dijkstra_sp_delta('roads',1,400,0.1)
On 29 November 2010 18:30, Daniel Kastl<daniel@georepublic.de> wrote:
Hi Madison,
Could you send me your routing query to see how it looks like?
Daniel
2010/11/30 Madison Shaw<madisonshaw@googlemail.com>
Hi There,
I was wondering if someone could help me. I have pgrouting working
and producing routes using both Dijkstra and AStar, but the edges that
are returned by the SQL are in the wrong order... not the order of the
edges as you expect to move through the route from start to finish...
eg: (using a short example)
If I have a route of ten edges, from start edge 1 to finish edge 10 -
I would expect the results to be: 1, 2, 3, 4, 5, 6, 7, 8, 9, 10 (using
the id column that is returned from the sql)
However, the results are more like 3, 6, 2, 8, 1, 9, 4, 7, 10, 5.
Is this supposed to happen? Is there a way to return the results in
the order you traverse through the route?
Yeah, the list does not allow attachments. You have to post the image to a public site and then put the reference url in the email to the list.
I can't really say what is going on in your example. Most of my code uses modified copies of the wrapper functions to meet my specific needs.
Are you using released wrapper routines? or have you made changes to them?
What happens when you make a shorter route?
Is all your data in decimal degrees or some meter/feet projection?
What did you use for the tolerance value when you ran assign_vertex_ids(...)?
-Steve
On 11/29/2010 5:36 PM, Madison Shaw wrote:
(I sent this to the list but it got bounced - I hope you don't mind me
contacting you directly)
Hi Steve,
The query I use within my php script returns a geojson.
I'm sorry I still don't completely understand why the results don't
come back in order... I realise that I may need to flip edges due to
the traversing backwards, but at the moment it looks like I need to
completely loop through everything to reorder it as well. I have
attached a jpg of how it actually looks for the start of the route
with reference to the sql results.
Also if you are writing these loops is it best to do it in the php script?
Cheers
Madison
On 29 November 2010 19:54, Stephen Woodbridge<woodbri@swoodbridge.com> wrote:
A more useful query would be:
SELECT gid, astext(the_geom) FROM dijkstra_sp_delta('roads',1,400,0.1)
Also in dijkstra you pass vertex nodes 1 and 400 BUT you get back edges in
the order of traversal. The tricky part is that the edge is return as loaded
and NOT as traversed, so you need to do some checking and flip those
segments that were traversed backwards from the disrtion that they were
loaded.
-Steve W
On 11/29/2010 1:46 PM, Madison Shaw wrote:
Hi Daniel,
Thanks for the quick reply, my SQL statement and its results are below
(with pre selected start and finish points for ease of illustrating my
issue)
As you can see, the edge (gid) that we start from '1' is given the id of
29.
SELECT gid, the_geom FROM dijkstra_sp_delta('roads',1,400,0.1)
On 29 November 2010 18:30, Daniel Kastl<daniel@georepublic.de> wrote:
Hi Madison,
Could you send me your routing query to see how it looks like?
Daniel
2010/11/30 Madison Shaw<madisonshaw@googlemail.com>
Hi There,
I was wondering if someone could help me. I have pgrouting working
and producing routes using both Dijkstra and AStar, but the edges that
are returned by the SQL are in the wrong order... not the order of the
edges as you expect to move through the route from start to finish...
eg: (using a short example)
If I have a route of ten edges, from start edge 1 to finish edge 10 -
I would expect the results to be: 1, 2, 3, 4, 5, 6, 7, 8, 9, 10 (using
the id column that is returned from the sql)
However, the results are more like 3, 6, 2, 8, 1, 9, 4, 7, 10, 5.
Is this supposed to happen? Is there a way to return the results in
the order you traverse through the route?
Yeah, the list does not allow attachments. You have to post the image to a public site and then put the reference url in the email to the list.
Attachments should be possible now.
It wasn’t forbidden to attach files but the max. length of the email body was set to 40KB (defaul value, I guess).
I changed it to 2000KB and let’s see if this is enough. I hope that OSGeo Mailman admins don’t get mad at me
I am using the latest released versions (I updated today to see if
that was my issue), and I haven't made any changes to them.
The same thing happens regardless of how long the route is.
I have retried it from scratch today using both a decimal degree
dataset and a meter dataset... when using the decimal degree one the
issues are alot greater, whereas when I use the meter dataset the gid
are reported in numerical order (still not near the right order).
The tolerances I used was 0.00001 for decimal degree and 0.001 for the
meter one.
I'm thinking its probably easiest for me to write a loop in the
wrapper to reorder it.
Madison
On 30 November 2010 01:08, Stephen Woodbridge <woodbri@swoodbridge.com> wrote:
Madison,
Yeah, the list does not allow attachments. You have to post the image to a
public site and then put the reference url in the email to the list.
I can't really say what is going on in your example. Most of my code uses
modified copies of the wrapper functions to meet my specific needs.
Are you using released wrapper routines? or have you made changes to them?
What happens when you make a shorter route?
Is all your data in decimal degrees or some meter/feet projection?
What did you use for the tolerance value when you ran
assign_vertex_ids(...)?
-Steve
On 11/29/2010 5:36 PM, Madison Shaw wrote:
(I sent this to the list but it got bounced - I hope you don't mind me
contacting you directly)
Hi Steve,
The query I use within my php script returns a geojson.
I'm sorry I still don't completely understand why the results don't
come back in order... I realise that I may need to flip edges due to
the traversing backwards, but at the moment it looks like I need to
completely loop through everything to reorder it as well. I have
attached a jpg of how it actually looks for the start of the route
with reference to the sql results.
Also if you are writing these loops is it best to do it in the php script?
Cheers
Madison
On 29 November 2010 19:54, Stephen Woodbridge<woodbri@swoodbridge.com>
wrote:
A more useful query would be:
SELECT gid, astext(the_geom) FROM dijkstra_sp_delta('roads',1,400,0.1)
Also in dijkstra you pass vertex nodes 1 and 400 BUT you get back edges
in
the order of traversal. The tricky part is that the edge is return as
loaded
and NOT as traversed, so you need to do some checking and flip those
segments that were traversed backwards from the disrtion that they were
loaded.
-Steve W
On 11/29/2010 1:46 PM, Madison Shaw wrote:
Hi Daniel,
Thanks for the quick reply, my SQL statement and its results are below
(with pre selected start and finish points for ease of illustrating my
issue)
As you can see, the edge (gid) that we start from '1' is given the id of
29.
SELECT gid, the_geom FROM dijkstra_sp_delta('roads',1,400,0.1)
On 29 November 2010 18:30, Daniel Kastl<daniel@georepublic.de> wrote:
Hi Madison,
Could you send me your routing query to see how it looks like?
Daniel
2010/11/30 Madison Shaw<madisonshaw@googlemail.com>
Hi There,
I was wondering if someone could help me. I have pgrouting working
and producing routes using both Dijkstra and AStar, but the edges that
are returned by the SQL are in the wrong order... not the order of the
edges as you expect to move through the route from start to finish...
eg: (using a short example)
If I have a route of ten edges, from start edge 1 to finish edge 10 -
I would expect the results to be: 1, 2, 3, 4, 5, 6, 7, 8, 9, 10 (using
the id column that is returned from the sql)
However, the results are more like 3, 6, 2, 8, 1, 9, 4, 7, 10, 5.
Is this supposed to happen? Is there a way to return the results in
the order you traverse through the route?
