Bug in parsing oneway tag in Graphserver

[Avi Flamholz]

I'm using graphserver to get some approximate driving directions and I noticed that the handling of the OSM 'oneway' tag in gdb_import_osm.py is buggy (around line 56). I'm documenting the problem here in case anyone else wants to fix it for their own use (or someone wants to patch the existing code).

The problem is twofold. 

1) The only tag values that are considered to indicate one-wayness are 'yes' and 'true'. However, a number of other values (including '1' and '-1') also indicate that a way is one-way.

2) oneway='-1' means that the directionality should be reversed. 

This means that graphserver gets onewayness wrong for at least 33 ways in Manhattan and driving directionality wrong for at least 19.

More details on the OSM website

http://wiki.openstreetmap.org/wiki/OSM_tags_for_routing#Oneway

[Brandon Martin-Anderson]

I did not know that, about the -1 thing. Thanks!

-B

> --
> You received this message because you are subscribed to the Google Groups
> "Graphserver" group.
> To view this discussion on the web visit
> https://groups.google.com/d/msg/graphserver/-/o1996NtBeH0J.
> 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.