This is continuing the previous two changesets, mopping up "Reverting vandalism in israel by cinid15546 " and others.

I wonder if "operator=yes" is really the best tag for e.g. node/3212416963 here?
I'm guessing that "yes" is not the name of the operator, but just says that there is one.

Hello,
node/2604728178 is likely not a valid POI as it appears to be in the middle of the street. How did you "check" this?
Best Regards,
Andy

Hello, if you see an "zig zag" vandalism can you please report it? If it's by a "user that we already know about and who has been blocked" please raise it at https://community.openstreetmap.org/t/vandalism-and-blocks-in-israel/105176 . If it is a _new_ user please email the DWG via [email protected] .

Didn't get back in time to write a comment. which would have been:
"Force reverting some nodes to hopefully the last non-vandalised version. If any nodes are still misplaced. let me know"

Thanks - I'll have a look when I'm next in front of a PC.

There unfortunately will be things that need fixing manually. A couple of users have had a go at manual coastline fixes. It's difficult to reconcile these with the reverts but the results will broadly (but not always) be a better coastline than was there before.

Also, _please_ use meaningful changeset comments, rather than just some hashtag. I can see that there is a "revert:id" in the changeset tags, but what would be useful to know would be how you identified and what needed to be reverted, what remains not yet reverted.

I've just reverted a number of nodes in changeset/143204094 . Can anyone who gets a chance have a look and see if any nodes in that changeset are misplaced? The nodes of e.g. way/5051304 no longer seem to be. My changeset doesn't address everything in this changeset, because it's one in a series. node/8400884853/historyhttps://www.openstreetmap.org/node/8400884853/history has so far not yet been done.

Any changeset-based revert tools is likely to fail, because changets with different vandalism can occur in parallel. See node/8400884853/history

This was a partial revert that had to be redone in changeset/143187297 .

For info, I've filled in a gap in the Suffolk Coast Path 1140775 in changeset/143184043

Didn't get back in time to add a comment, but would have been "Reverting a node to the last non-vandalised version, which includes some more recent well-meaning but invalid reverts "

Please DO NOT apply "osmi routing view fixes" while the revert of this data is ongoing.

Didn't get back in time to add a comment, but would have been "Reverting a node to the last non-vandalised version, which includes some more recent well-meaning but invalid reverts "

With this changeset right now, nothing. When we come to review the objects that were initially deleted and edited we (or the community) will need to do that on an object by object basis, not a changeset by changeset one.

No, this changeset _is_ by someone from the DWG trying to manually repair the data.

@zstadler The 13 nodes to 12 is as a result of a manual tidying exercise (this changeset). What is incorrect about way/26508703/history now?

@zstadler can you link to actual objects that have been reverted to incorrect values?

Thanks!

Hi,
Fizzie41's from the DWG as well and we've discussed internally what we can do in parallel
Regards,
Andy