[Osmf-talk] App damaging OSM data

[Brian M. Sperlongano]

>
> Again I don't see any evidence of this being down to way splitting, it
> could very well be that both ways were added manually to the border..
>
Regardless of the specific error that the user made, iD is allowing broken
boundary relations to be uploaded.  As an example, click on a boundary
relation member in iD and erase the member's role and iD will happily allow
you to upload without so much as a warning.  I am seeing a consistent
stream of broken boundary relations, with the vast majority coming from iD
changesets.  A simple warning that the user is about to do something
harmful would go a long way in reducing these problems.

Below is my current list of relation IDs for currently broken boundaries.
Perhaps there is a pattern here that I am not seeing:

110798 112321 114559 114859 115393 117499 119777 123133 123424 126009
127253 127470 128464 128468 140000 170584 170585 170706 170709 174428
174436 174463 175505 175687 175728 182556 183994 186643 198751 198899
198904 253769 1216638 1663791 1758947 1834225 1863555 2035535 2689456
2726614 3046923 3121904 3352040 3353288 3554304 3880707 3880708 3880715
3880777 3880799 3880800 3881559 3890559 3890567 3936930 4011809 5432268
5634048 6580401 7657827 7854695 8884979 9424586 9686480 11286845 11297185
11488053 11587226 11696227 12235903 12235905 12236003 12927888 13052900
13093315 13183508
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/osmf-talk/attachments/20210920/fe2fbd4b/attachment.htm>