@campbelltree, @aighes, @VJMK,
thank you all for pointing out the problem. I've fixed all the corrupted data and addressed the root cause within the app. Apologies for the inconvenience — I’ll ensure this doesn't happen again.

@9_tab, hi. That edit had no special meaning — just a technical bug in my app. While saving edits, it rewrote the node with ID 17960327 instead of the relation with the same ID: relation/17960327
I've fixed all the corrupted data and the app's code already.
Sorry for the inconvenience.

fixed it, sorry

fixed it

Ok, sorry - it's kind of a bug. Already fixing it.

Да, странная бага. Буду разбираться.
No special meaning, seems kind of a strange bug. Investigating it...

Пока не могу точно привязать её на местности. Если получится, то исправлю

fixed:
changeset/171537387

Площадь уже обозначена: relation/3365908
Ни к чему переделывать велодорожку.
---
#REVIEWED_BAD #OSMCHA
Published using OSMCha: https://osmcha.org/changesets/122848308

Круто! Буду знать. Спасибо.
---

Published using OSMCha: https://osmcha.org/changesets/140343899

Исправил, спасибо!

Thank you Krako! I've noticed that mistake lately and fixed remaining waterways.

Great! Thank you.

Спасибо что поправил!
---

Published using OSMCha: https://osmcha.org/changesets/136250624

Да. Можно грохать.

Organic Maps меня попутал. Спасибо. fixed

Ok. Thank you for advice. I'll try to make more descriptive comments.

Speaking about that particular changeset - it mostly contains routine fixes of broken boundaries relations.

I was wrong. It's Ok. Sorry for the noise

Hi. Something wrong with your imports to Korea - it's ruining boundaries. Please stop and inspect the issues. In that particular changeset relation/2327259 (relation/2327259) was broken.

Вот тут уже ответчал:
changeset/114698857#map=5/60.377/85.392