Disable joining ways with conflicting tags #2809
Merged
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
jfirebaugh
force-pushed
the
conflicting-tags
branch
from
d9bf4f1 to
ecb9398
Compare
bhousel
added a commit
that referenced
this pull request
Oct 21, 2015
Disable joining ways with conflicting tags
|
Thanks @jfirebaugh! |
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.
Fixes #2358.
"Uninteresting" tags are exempted -- this includes "attribution", "created_by", "source", "odbl", and "tiger:*". The values of such tags will continue to be joined with semicolons.
The rule also takes into account tag values that will automatically be reversed when the ways are joined. For example, if you have a
oneway: yesway from a to b, and aoneway: -1way from c to b, joining is permitted, and will produce aoneway: yesway going a to b to c.