1-member multipolygons

[Friendly_Ghost (Casper)]

@multimodaal

The reason I interpreted your usage of “purging” here as “to delete the relation from the OSM-database (even if the outer has multiple parent-MP’s)”
instead of
“to exclude form the further workflow, so it remains untouched” ,
is that with the campsite -after I pointed out that all the data had vanished from OSM because of the nationwide edits you performed-, you did not restore the relation you deleted, but created a hidden duplicated second way instead. That is exactly the result of purging as in “to delete the relationship from OSM”

The deletion of the camp site was accidental and as I said I learned from my mistake and have multiple safeguards in place for it:

• Omitting (purging) 1-member MPs of which the ways have multiple parent relations when working on 1-member MPs (text edited)
• Omitting (purging) closed ways and their relations when working on MPs with multiple unclosed outers.

The choice to make a closed way of the camp site was deliberate. That’s not hidden, it just overlaps. You can find it right here: Way: ‪Zeeverkennerscentrum Kagerplassen‬ (‪1191402332‬) | OpenStreetMap
Other mappers have already taken the time to explain how you can select it in the editor, and I’m very sure that most OSM-based apps, websites etc. will also be able to find it.

@multimodaal

Again, that is not my responsibility, but the responsibility of the mapper who made nationwide edits on more than 1.700 items that are shown to be error-prone.

As I said right after that sentence, which you forgot to include in my quote, I’ve been quite thorough to prevent these mistakes, this one just slipped through the nets. And like I’ve said repeatedly, I now have multiple safeguards to prevent future issues like that. How often do you plan to circle back to this one camp site that I already restored?