preserve natural=coastline on outer ways during Merge operation (Fixes #11816) #11818
+21
−2
Conversation
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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 applies the same fix logic from 62e1714 to the merge operation
fix
Now, when coastline ways are merged into a multipolygon, the natural=coastline tag stays on the outer ways rather than being shifted to the relation, as recommended by the OSM wiki
changes
Modified modules/actions/merge_polygon.js to extract
natural=coastlinebefore merging tagsAdded a regression test in test/spec/actions/merge_polygon.js to verify that
natural=coastlinestays on the way while other tags move to the relation.Fixes #11816