Opened 14 years ago

Closed 14 years ago

Last modified 13 years ago

#358 closed defect/bug (worksforme)

navit ignores OSM oneway tag

Reported by: Ernia Owned by: KaZeR
Priority: major Milestone:
Component: core Version: git master
Severity: Keywords:


It seems to me that navit doesn't care about OSM oneway tags in route calculation. With the following points: mg:0x12f543 0x54d095 type=bookmark label="1" mg:0x12f713 0x54cfcd type=bookmark label="2" navit would make me go from 1 to 2 in the wrong direction.

Change History (3)

comment:1 Changed 14 years ago by Ernia

  • Component changed from mapdrivers/OSM to core
  • Owner changed from cp15 to KaZeR

I've tried with Reiseplaner maps and the issue seems to be present too, so i've changed the bug from Mapdriver/OSM to core. to test in Reiseplaner i've tried 2 points around a roundabout, navit always use the shortest way. i'm using svn 2213 in archlinux.

comment:2 Changed 14 years ago by Ernia

  • Resolution set to worksforme
  • Status changed from new to closed

svn 2217 seems to resolve the problem, with both maps. seems to be faster, too. thanks

comment:3 Changed 13 years ago by

Using Navit 0.1.0+svn-2391 from and a California map from, Navit does not obey the oneway OSM attribute, e.g. Gough Street in San Francisco. I see the same problem with maps from the Navit Planet Extractor, as well as maps manually downloaded from and converted (by me) with the latest osm2navit r2391.

Note: See TracTickets for help on using tickets.