-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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 shared paths differently #10256
base: develop
Are you sure you want to change the base?
Conversation
@k-yle thanks for kicking this off! I am wondering, if we can find a system in how we use the background vs. dashed line.
My mental model has a hierarchy like this on this topic: We could translate this in something like: Document: https://docs.google.com/presentation/d/1zQ6mqbGgyRRwq9Zakof_kPfAzX1JeRVplxMr4SLKMsQ/edit?usp=sharing Notes:
|
And for the crossings… Note: In openstreetmap/id-tagging-schema#1201 (comment) I added crossing presets to match all the main way presets. Given that both background and dash color are now reserved what else can we change?
Thoughts:
|
Sorry for the delayed reply, this comment suprised me:
because I thought that ( |
You are right. Illustrating stuff is always hard and I mixed two things which did not work… Looking at it some more, I think the main issue is: You are introducing the new pink color for foot+bike traffic ways. Does this make sense: The miss-match of Column D vs. I? ![]() I don't have a solution ATM. I really like to separate the crossing styles. But maybe we should look more at options from #10256 (comment) – when we introduce a new modifier to the style, we make it easier to work with what we have for the rest. I am not sure yet how to handle the access. vs. highway class in the styles. Have to stop now, but 🤔 … Docs Updated: I added an "Another try" Column.
|
I think this might be a step backwards from the current situation, where the colours make it easy to distinguish most presets, so I haven't considered it below
These two are already used to distinguish paved/unpaved, so we can't really change the line casing
I think this is the only option...
I overlooked that until now... maybe we need a separate category for unspecified access? Here's what this could look like, using a modified version of your first diagram, including some of the changes from this table: (upper line = normal, lower line = crossing)
|
Closes #10139
Currently, it's impossible to tell the difference between the
Cycleway
andCycle + Foot Path
presets.There are 6 special countries that use a different preset, which is simiarly confusing, since it renders exactly the same as
crossing=*
.This PR makes the styling consistent for
bicycle=designated
+foot=designated
, regardless of whether you usehighway=path
orhighway=cycleway
(only the bottom 2 have changed)