-
Notifications
You must be signed in to change notification settings - Fork 5
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
Catch broken coastlines with semicolon separated values #15
Comments
Problem is that most if not all software working with coastlines only handles exactly natural=coastline and not looking for mult-value tag separated with |
Thanks for looking at the issue. I'm not sure from your answer -- did you decide to flag values like |
Oh no, I totally misunderstood your ask, I thought you wanted me to process anything with |
Yes, that's right -- flag Sorry if my original post wasn't clear! |
How would I fix natural=coastline;bare_rock? Duplicate existing way and put tags on existing way natural=coastline and on duplicated geometry I would put natural=bare_rock? |
Yes, exactly. That's one way of separating the tags. It’s also possible to use a multipolygon with natural=bare_rock and with the coastline way as a member. That’s what the Wiki suggests (https://wiki.openstreetmap.org/wiki/Tag:natural%3Dcoastline#How_to_enter_the_data) but I believe the preferred approach is to duplicate the geometry. |
Include ways with semicolon separated values of natural=* where one of the values is "coastline" in the list of broken coastlines. The
natural=coastline;bare_rock
tag is the most common example of this.Just a suggestion for an added feature, since these ways are also broken coastlines.
The text was updated successfully, but these errors were encountered: