Hailing from Italy so what’s along the Adriatic sort of always slides into my mapping view. A couple of weeks ago worked on the Adriatic relation which was found to have been broken by imports in your area and then found some 5 more. In the end the DWG reversed those edits and removed the Adriatic relation restoring the Adriatic as a place node which was great. A hard relation to maintain often damaged by unsuspecting mappers, or as was the case then, undiscussed imports.
Sorry about that! I fixed the Balkan peninsula and the Istria peninsula now. I was concentrated on not breaking the little administrative units, but forgot about the huge relations. I’ll be more careful next time.
But now that I look at them, it’s a bit strange that the Balkan peninsula has islands in its relation. If we are mapping the geographical entity of a peninsula, then islands can’t be a part of a peninsula. If we are mapping a cultural region of the Balkans, then OpenStreetMap seems like the wrong database for that.
Selecting the history of some of the pink nodes it appeared the last to touch was DWG reverting an import 4 weeks ago, but the break was cause of these imports… no wait, a new import, on the 5th by “Import DGU borders” (has no account here). Was sure the problem had gone and now shows it’s ugly face again.
Thanks! Ok, fixed 4 big relations (3 of which I originally created, so it’s a bit embarrassing i broke them).
My original mistake was downloading boundaries in JOSM with the Overpass service, and not downloading all the relations that those boundaries were in. So when I cut those boundaries in two, JOSM couldn’t keep those new parts in the big relations. This mistake will be avoided next time.
