Opened 15 years ago
Closed 14 years ago
#144 closed defect/bug (fixed)
navit2osm incorrectly ignores highway tag in favor of cycleway tag
Reported by: | deelkar@… | Owned by: | somebody |
---|---|---|---|
Priority: | major | Milestone: | |
Component: | tools | Version: | |
Severity: | Keywords: | navit osm2navit cycleway wrongtagchosen | |
Cc: |
Description
The cycleway=$VALUE tag for ways is always additional info for cyclists, never the primary use of the way. For everything routing the primary key to everything is highway=$VALUE and the cycleway tag is so cyclist and cycle routers can decide a weight for that route.
Possible values for cycleway include lane and track, which denote a separate cycleway track next to the road (but very close to traffic) and just a lane next to the car traffic on the main road surface respectively.
Attachments (1)
Change History (5)
comment:1 Changed 15 years ago by anonymous
comment:2 Changed 15 years ago by dieter@…
cycleway=track is considered as additional feature to a highway track. Yet it als could be wrongly used. In my eyes it should render as highway=cycleway if no other tag is present, yet highway=<something> should outweigh it. I have attached a simple patch which should achieve this. I only changed the order of the tags in *static attrmap {}.
I created and tested this patch with
URL: https://navit.svn.sourceforge.net/svnroot/navit/trunk/navit Repository Root: https://navit.svn.sourceforge.net/svnroot/navit Repository UUID: ffa7fe5e-494d-0410-b361-a75ebd5db220 Revision: 1103
comment:3 Changed 15 years ago by deelkar@…
This fixes the issue, please close.
comment:4 Changed 14 years ago by Tinloaf
- Resolution set to fixed
- Status changed from new to closed
Seems like this has been fixed a long time ago.
example way ids: 4003693, 4381508 (sorry forgot to tell you where this happened)