Obskurer Bug in iD, das die Objekte durcheinandergebracht hat (z.B. statt einem Knoten mit der ID x die Relation mit der ID x gelöscht hat)? Unwahrscheinlich, ich weiß, aber bei Komputtern weiß ja man nie (und bei iD schon gar nicht) …
Ziemlich unwahrscheinlich. Er hat nämlich “nur” type=boundary und boundary=administrative gelöscht - was sich entsprechend schlimm auswirkt, da diese Relation dann halt keine Admingrenze mehr beschreibt.
(that’ll take a while to display - it’s a big relation).
The most recent change (by a relatively new user) is likely part of the problem, but I’m not sure how many other of their changes also contribute to the problems in that area…
And what’s about the actual - wrong - situation? see list one post before.
Regards
walter
i may reset to the old situation, but not doing a revert. because he/she did to many changes.
seems to be a newbie because using iD and doing some newbie-errors. but may be, it’s a socket puppet? i’m not quite sure.
However the latest 2 changesets didn’t affect international borders at first glance, so if subsequent mapping is like that, I’d be tempted to ignore.
I wouldn’t assume that (a) they can understand English or (b) that Google’s English → Chinese Simplified is any good. It should be good enough to indicate to them that “someone is trying to talk to me” but beyond that I wouldn’t hold out much hope.
in about 20 years this problem will no longer exist. Chinese will be the most used language on earth and OSM will change the tagging/language policy to chinese