Ticket #144 (new defect/bug)

Opened 7 months ago

Last modified 7 months ago

navit2osm incorrectly ignores highway tag in favor of cycleway tag

Reported by: deelkar@gmx.de Assigned to: somebody
Priority: major Milestone:
Component: tools Version:
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

osm2navit.diff (0.7 kB) - added by dieter@linuxjaeger.de on 06/07/08 09:57:03.
Patch to fix cycleway rendering

Change History

06/05/08 22:07:02 changed by anonymous

example way ids: 4003693, 4381508 (sorry forgot to tell you where this happened)

06/07/08 09:57:03 changed by dieter@linuxjaeger.de

  • attachment osm2navit.diff added.

Patch to fix cycleway rendering

06/07/08 09:59:52 changed by dieter@linuxjaeger.de

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

06/13/08 13:13:26 changed by deelkar@gmx.de

This fixes the issue, please close.