-
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
Suggestion: show sidewalks (in the same brown as footways) #487
Comments
Please also consider the following:
For the above reasons, I propose to not render all sidewalks. However, it may be benefitial to render sidewalks under the following conditions:
|
I think those sidewalks should be rendered at a very low rank, even lower than the green
Regular sidewalks should be placed at the end of this list.
I agree with that. But highway classification and low maxspeeds are already shown in the map, which won't be affected by rendering sidewalks.
On higher zoom levels, around z17 and above, the gap between a separated sidewalk and the carriageway becomes visible, so one would still be able to distinguish them from attached sidewalks.
Maybe these filters make sense on mid zoom levels (z15 - z16). If applied on the more detailed zooms, users (and mappers) would again be confused why some sidewalks are shown while others aren't. |
Could we try to gather some examples here where current CyclOSM style is missing useful information and sidewalks rendering would really help? Thanks! |
This place: © RVR, 2020, dl-de/by-2-0 Cycling the carriageway of the East-West road is for tough cyclists here. But for children of 9 years or younger, it is pretty safe, because they may use the sidewalks. Also an adult accompanying a child of 7 years or younger may use this sidewalks. (by german law - but it makes sense, so there are probably similar rules elsewhere. EDIT: another example is New South Wales, Australia, where using the sidewalk is allowed for children of up to 15 years) Also in this place the information about sidewalks is important, but in a completely different way: © RVR, 2020, dl-de/by-2-0 The road in the center of the image is a bicycle road. It has a sidewalk, so cyclists and pedestrians are separated. Pretty similar to At last, places like this: © RVR, 2020, dl-de/by-2-0 This is the last part of a steep road, as can be seen from the contours. Cyclists without motors may want to know if there is a sidewalk so they can fall back on slowly pushing up their bike aside from the carriageway. So use cases of sidewalks boil down to one of those three cases:
The first two cases cover nearly every road, so I'd be consistent and show sidewalks on every road, without discriminating by category. |
With an SVG of this place https://www.openstreetmap.org/#map=18/51.47195/7.26015&layers=Y, I could try to make a mock-up as a basis for further discussion. |
I actually implemented this, but decided not to proceed to a pull request, because when I tried it, at least in my area, there is much duplication of sidewalks, being tagged both as |
As far as I know, there is currently no render showing sidewalks. Due to the lack of visual feedback, incorrect tagging is to be expected in some places. |
I just found out that there are regions where cycling in the sidewalk is allowed generally, e.g. Queensland, Australia. Showing sidewalks is even more important there. |
While not originally dedicated to cyclists, sidewalks can be important to them, too. A street which has a sidewalk can easily be stopped along nearly everywhere. Cyclists can rest safely, apart from the carriageway.
In some cases cyclists are even allowed to use the sidewalk directly
From the perspective of a user not familiar with osm mapping practices, it is not clear why some sidewalks (the separately mapped ones) are shown while others are not.
So i suggest rendering
sidewalk~right|left|both
the same way cyclable sidewalks are already shown, but in a different colour. Footway brown should fit.Naturally regular cycleable sidewalks should remain green as it was explained in #409 and implemented in #464.
The text was updated successfully, but these errors were encountered: