You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jul 24, 2021. It is now read-only.
Reporter: rasher [Submitted to the original trac issue database at 8.42pm, Monday, 9th February 2009]
Osmarender seems to render cycleways inconsistently when they exist as a tag on a regular road (highway=secondary, cycleway=track).
For tertiary roads, the cycleway shows up, but for secondary roads they don't. I don't know where or how to look for other combinations, but maybe that needs investigating as well.
The tertiary road gets rendered with an indication that a cycleway exists, while the secondary road to the left doesn't, even though they're tagged similarly. This doesn't seem like it's intended behaviour.
Reporter: rasher
[Submitted to the original trac issue database at 8.42pm, Monday, 9th February 2009]
Osmarender seems to render cycleways inconsistently when they exist as a tag on a regular road (highway=secondary, cycleway=track).
For tertiary roads, the cycleway shows up, but for secondary roads they don't. I don't know where or how to look for other combinations, but maybe that needs investigating as well.
An example can be seen here: http://openstreetmap.org/?lat=55.8422&lon=9.82163&zoom=17&layers=0B00FTF
The tertiary road gets rendered with an indication that a cycleway exists, while the secondary road to the left doesn't, even though they're tagged similarly. This doesn't seem like it's intended behaviour.
I've opened a related ticket against mapnik, which contains a bit more background info: http://trac.openstreetmap.org/ticket/1577
The text was updated successfully, but these errors were encountered: