routeserver walking directions

[Winston]

Hi,

I'm primarily interested in transit routing as opposed to auto or
bike. I've noticed that narratives that involve walking on one-way
streets can be bit circuitous because the route paths returned are
always in the direction of the vehicle flow of traffic. This can lead
to walking routes that essentially "loop around the block" instead
walking in the direction against vehicle traffic that more directly
leads to the planned route. For example:

----> A ----->
| |
D B
----< C <----
|
E
\/

I'd like to go from A to E. Logically, the shortest path is A:D:E;
however, routeserver returns A:B:C:E or longer if B is against the
direction that needs to be traversed.

Is there a way to resolve this? I've spent the better part of the day
looking at routeserver.py and events.py but I'm just not good enough
with python to figure it out.

Thanks.

Winston

[Brandon Martin-Anderson]

It's deeper than the narrative generation - it's in how the graph is
put together. Right now, because I had my mind in a bicycle space when
I was hacking out the code, I kept one way roads one way. It's a
matter of a few lines of code to specify whether travel is one-way or
not gs_import_gtfs is run. I'll file a ticket.

-B

> --
> You received this message because you are subscribed to the Google Groups "Graphserver" group.
> To post to this group, send email to graph...@googlegroups.com.
> To unsubscribe from this group, send email to graphserver...@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/graphserver?hl=en.
>
>