Add "kerb" tag as an optional field to crossings #862
Merged
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.
This is for the uses of the
kerb
tag without abarrier=kerb
, when indicating the accessibility properties of a road crossing (see https://wiki.openstreetmap.org/w/index.php?title=Key:kerb&oldid=2501049#By_itself).And when the
kerb
tag is used completely by itself, we can't assume it should be a barrier (as it might also be an incompletely tagged crossing node). This requires thebarrier=kerb
presets to be more strict on which tags they match. This should fix #858.