Opened 15 years ago
Closed 12 years ago
#76 closed defect/bug (fixed)
wrong import of dual-tagged OSM ways breaks routing
| Reported by: | grenzdebil@… | Owned by: | cp15 |
|---|---|---|---|
| Priority: | critical | Milestone: | version 0.2.0 |
| Component: | mapdrivers/OSM | Version: | git master |
| Severity: | Keywords: | osm railway highway tram | |
| Cc: |
Description
The osm2navit script imports ways tagged with both highway=some value and railway=some value as railways and thus prevents navit from using them for routing.
Tagging ways as highway and railway is commonly used in OSM when for example tram rails are located directly on a road and tram and car traffic share the same space.
The way osm2navit imports this breaks the routing in my town and I'm sure it does in many places.
One solution would be to create two different ways in the mapnik file for the street and the rails, so the information is not lost - the other one could be to simply consider such ways as a normal street.
Change History (4)
comment:1 Changed 15 years ago by KaZeR
- Milestone set to version 0.0.4
comment:2 Changed 14 years ago by anonymous
comment:3 Changed 13 years ago by KaZeR
- Priority changed from major to critical
comment:4 Changed 12 years ago by kazer
- Resolution set to fixed
- Status changed from new to closed
osm2navit has been reworked, and maptool should now handle cases like this correctly.
actually, this breaks even more things, namely highways that have a cycleway=lane/track additionally when there is a cycle lane on the road.
They are shown as pure cycleways and cannot be used for (car-) routing in navit, which leads to wrong directions given by navit.