-
Notifications
You must be signed in to change notification settings - Fork 164
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
Allow tagging crossing without specifying variety (just highway=crossing) #834
Comments
👍 This would require to make the |
Just “Crossing” is probably sufficient. There are some other unspecified-type presets that we give simpler names, such as “Building”. But if we need to differentiate, I’d suggest saying something about a “path–road crossing” or somesuch, to differentiate it from “Railway–Road Crossing” and “Railway–Railway Crossing”. (The standard real-world term for these is “road crossing”, but users could be confused about when they’re supposed to use one preset versus another.) |
What about "Pedestrian Road Crossing"? path has a bit messy implications as a term, some are sure that it is invalid for sidewalks (which is BTW causing problem with people retagging |
“Pedestrian Road Crossing” would be an accurate description of most occurrences of |
Is it possible to have different preset match based on way where it is a vertex? Probably no. |
No, that's not currently possible in the tagging schema, unfortunately. iD could however implement a validation rule that any |
Sometimes memory or aerial is not good enough to specify exact one 0 for example presence of traffic signals may be not entirely clear.
On node within way:
The text was updated successfully, but these errors were encountered: