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: msiebuhr [Submitted to the original trac issue database at 3.57pm, Tuesday, 22nd September 2009]
In the OpenCycleMap, all highway=cycleway'' are rendered alike, despite that the ''surface=''-attribute has quite a lot to say about how usable it is. (Racing on ''surface=unpaved is not fun...)
I suggest this to be changed so the paved paths are a solid line, those without surface is as-is and the unpaved ones are dotted. This would make it immediately distinguishable where you can ride and where you can't.
The text was updated successfully, but these errors were encountered:
Author: Andy Allan [Added to the original trac issue at 2.23pm, Monday, 9th November 2009]
It's a good idea, definitely on the plans. I'll have a look at the surface tags and try to divide them into groups of similar end results, rather than having a slightly different rendering for every different surface.
Reporter: msiebuhr
[Submitted to the original trac issue database at 3.57pm, Tuesday, 22nd September 2009]
In the OpenCycleMap, all highway=cycleway'' are rendered alike, despite that the ''surface=''-attribute has quite a lot to say about how usable it is. (Racing on ''surface=unpaved is not fun...)
I suggest this to be changed so the paved paths are a solid line, those without surface is as-is and the unpaved ones are dotted. This would make it immediately distinguishable where you can ride and where you can't.
The text was updated successfully, but these errors were encountered: