[mkgmap-dev] Oneway 1 or -1 BUG?
From nwillink osm at pinns.co.uk on Mon Mar 14 19:09:17 GMT 2016
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.
- Previous message: [mkgmap-dev] splitter r433 released
- Next message: [mkgmap-dev] Oneway 1 or -1 BUG?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the mkgmap-dev mailing list