-
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
Render cycleable sidewalks tagged on roads #464
Conversation
sidewalk:bicycle=designated is still preferred over cycleway=lane, because that is probably a decent cycling facility. But a sidewalk:bicycle=yes has no guarantee of quality, even though it is off-road. It is porbably still better than a mere shared lane, however.
There is 7 sidewalk:bicycle=designated don't worth a special color for it. And 679 for sidewalk:bicycle, does it worth the effort and the rendering cost ? https://taginfo.openstreetmap.org/keys/sidewalk%3Abicycle#values |
sidewalk:bicycle isn't a valid tagging, that's why its so uncommon (and I don't even bother to render it). Look at sidewalk:(both/left/right):bicycle : https://overpass-turbo.eu/s/10Fl
|
There are around 10k However, there are only 32 Given the tag adoption, I think it's not worth making the distinction (perf-wise). I would simply check the value against anything but |
project.mml
Outdated
@@ -675,10 +683,16 @@ Layer: | |||
END AS oneway, | |||
CASE | |||
WHEN tags->'cycleway:left' IN ('track', 'opposite_track') THEN 'track' | |||
WHEN tags->'sidewalk:left:bicycle' <> 'no' and tags->'sidewalk:left:segregated' = 'yes' then 'track' |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Minor (stylistic) comment but could we have an homogeneous SQL code convention here?
Almost all of CyclOSM SQL queries are written using !=
operator (instead of <>
) and uppercase keywords (AND
/ THEN
). Thanks!
I have a SQL query style comment, and I'd like to drop the dedicated |
SGTM, in that case I will rank sidewalk between lane and shared lane.
…On Sun, 29 Nov 2020, 2:31 pm Lucas Verney, ***@***.***> wrote:
I have a SQL query style comment, and I'd like to drop the dedicated
sidewalk:*:bicycle=designated render. Once done, I think it is a go for
merge.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#464 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AEXE4ES5XPUJW5TGN75GMVLSSJEMXANCNFSM4UFUJAJQ>
.
|
My bad. |
I think path green would be better, since most usages are not designated, so having the same colour as |
These are not common enough to justify the performance penalty.
ok |
Thanks! |
Adds two new colours of cycletrack, which represent sidewalks that are primarily for pedestrians but either designated for bicycles (drawn in the same lighter blue as a footway designated for bicycles is) or merely allowed for bicycles (drawn in the same green as a footway that allows bicycles).
The ranking of road-based bicycle features that are drawn in the border of the road is now:
A cycletrack (
cycleway=track
) or a segregated sidewalk, that allows bicycles (sidewalk:bicycle!=no sidewalk:segregated=yes
): solid dark blueA sidewalk designated for bicycles (
sidewalk:bicycle=designated
): solid lighter blueA bike lane (
cycleway=lane
): dashed dark blueA sidewalk allowing bicycles (
sidewalk:bicycle=yes
): solid greenA shared busway or lane: very dashed dark blue
The reasoning for splitting the sidewalks is that a designated off-road path is probably more comfortable than an on-road lane, but a non-designated sidewalk can potentially quite bad infrastructure and so a dedicated lane is better; but then sharing with pedestrians is still better than sharing with cars, so shared road lanes come after it.
Fixes #409.