fields/kerb: Make directionalCombo to allow optional left/right tagging
#1206
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
🍱 You can preview the tagging presets of this pull request here. |
TestingOverpass turbo query: node/9165437876 
|
ConclusionLooking at the numbers some more I don't think this added complexity in the UI is worth it. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When the kerb is tagged on the
highway=crossingnode, it is assumed to have the same kerb left an right of the node. If that is not true, the tagging iskerb:left|right=*.This PR changes the
kerbfields for crossings to adirectionalComboin order to represent thoseleft|rightcases.Current usage:
crossing=*has 340 208 cases withkerbkerb:rightkerb:lefthttps://taginfo.openstreetmap.org/keys/crossing#combinations