astar (#17) - Path Segments aren't returned in traversal order? (#183) - Message List
I'm having difficulty using the paths returned by an astar query. The rows returned are not in traversal order.
For example: a path from edge 'a' to edge 'e' that traverses edge 'b', 'c', and then 'd' would be returned in the order 'b', 'd', 'c'. On top of that the points that make up edge 'd' (or any other edge) may be in the reverse order of the implicit direction of the path.
Is this a problem with my dataset? The path when drawn on a map is correct, it's just drawn out of order with no regard to the travel order of direction.
I would like to avoid doing post processing of the data.