Hi Nick, I am sure that mkgmap is interpreting it correctly, but you probably did not consider that it reverses the ways with oneway=-1. In other words, you don't need a 2nd line type for this. But attention: This is happens when the oneway way is also added as a routable way. Users who create a separate layer for oneways and routing data probably need two line types. Gerd ________________________________________ Von: mkgmap-dev <mkgmap-dev-bounces@lists.mkgmap.org.uk> im Auftrag von nwillink <osm@pinns.co.uk> Gesendet: Montag, 14. März 2016 20:09 An: mkgmap-dev@lists.mkgmap.org.uk Betreff: [mkgmap-dev] Oneway 1 or -1 BUG? I have a suspicion that mkgmap quite understandably (!) parses oneway=-1 as oneway=yes and oneway=1 as reverse (ie arrows reversed) . However, for some unknown reason , osm defines oneway=-1 as meaning 'reverse arrows' and uses oneway=1 to mean 'oneway=yes'. In other words, mkgmap , when parsing lines,creates the opposite effect to what is implied in osm. This matters when you create a separate line types for each condition. Not a problem , just a small observation. -- View this message in context: http://gis.19327.n5.nabble.com/Oneway-1-or-1-BUG-tp5869847.html Sent from the Mkgmap Development mailing list archive at Nabble.com. _______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev