-
Notifications
You must be signed in to change notification settings - Fork 115
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
Add check for unnecessary multipolygon relations #2191
Comments
There is already a report for 1-object multipolygon. But I am not sure about report of union of simple polygon in multipolygon is a good move. I think such multipolygone can be used to "group" parts a common thing, like part of a named wood cut by a river. |
I know, hence the requirement of having no other tags. No |
I like the idea of flagging multipolygons with only 2 tags - The risk is that e.g. a farmland was added as a multipolygon because it for example belongs to a single farmer, segregated by a road or so. However, these cases will very likely be very minimal. On the other hand, verification of such places would be very difficult, and that's holding me back from implementing it at the moment. Any thoughts on that? |
I've just fixed one of my old changesets (literally from my 2nd day of editing OSM) that I randomly remembered. Back then I was fiddling with iD since I had to split a
landuse=grass
way into two, but somehow I managed to create a multipolygon instead. I guess Osmose can check for such scenarios. If it detects a painfully simple multipolygon relation, just like mylanduse=grass
, with no other tags and a very simple geometry (noinner
members, onlyouter
), it might suggest splitting such unnecessary relation into its member ways. You can refer to changeset 149592903 to see what I mean.The text was updated successfully, but these errors were encountered: