-
Notifications
You must be signed in to change notification settings - Fork 44
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Proposal: render cycleway:[left:|right:|both:]segregated:no similar to shared bicycle/foot path #640
Comments
I believe the reason is that it is a "cycleway" and as such is rendered in dark blue (the cycleway color). This issue has been discussed for separate cycleways at #575, but I believe the same principle applies. The way cyclosm wants you to tag unsegregated sidepaths for pedestrians and cyclists is with |
Unfortunately the German-speaking wiki page https://wiki.openstreetmap.org/wiki/DE:Bicycle/Radverkehrsanlagen_kartieren tells me to use the I think it would be an improvement for CyclOSM if different widely used methods to tag the same actual thing would lead to the same output. So IMHO a |
This is indeed very close to #575 and these two issues would deserve being tackled together. Writing the code to handle it is quite simple, but getting the logic right for everyone (worldwide) is something much more difficult. Would anyone involved in these issues have some time to summarize in a table form what is incorrectly handled at the moment? I could imagine something like (taking a non-controversial example here)
Thanks |
Where "blue exclusive" is the current render colour for |
Sorry, I don't quite understand the last one: isn't "Blue separate" the indicator for a segregated cycleway? What exactly would you like to have changed here? |
Another thing: in the first one, you meant to write "segregated=no" rather than "segregated=yes", right? |
Thank you for the edits! I think I now agree with the table, but would like to add some more clarification to avoid misunderstandings:
I also think that you actually had a valid point with the third, meanwhile deleted row in some way: a cycleway with bicycle=designated should not turn light blue if it has a sidewalk. So I think as a further improvement, we could add "sidewalk=no/(unset)" to the conditions of line 2. |
@reinhard-mueller I updated the table to be more specific about cycleway:both/right/left.
|
Thank you!
I think we should not aim to "educate" mappers about what we consider correct mapping, we should rather try to build the map as usefuly as possible based on current tagging. https://wiki.openstreetmap.org/wiki/Key:segregated says "that segregated=no may be safely assumed in at least some cases", so I think segregated being not set in this case should be rendered the same as segregated=no.
Thinking about this once again, I find that combination of foot=designated and sidewalk=yes actually makes no sense, so I agree to leave this out. |
The part that "segregated=no can be assumed in some cases" is somewhat odd, because it's not entirely clear when it can be assumed (and may vary by region). Nonetheless |
There are cycling lanes which are at the same time used as a sidewalk, like here: https://www.cyclosm.org/#map=19/47.43148/9.66819/cyclosm (tagged with cycleway:right:segregated=no and sidewalk:right:segregated=no). I suggest that in such a case, the lane should be marked with the lighter blue, much like unsegregated shared bicycle/foot paths.
The text was updated successfully, but these errors were encountered: