Could someone please revert this changeset? 160088115
I couldn’t manage to do it using RevertUI or osm-revert.
For context - this changeset was made by a blocked user, who (wrongly) changed an entire trunk road to a motorway in Casablanca, Morocco, without any prior discussion with the community. Thanks in advance.
Looking at achavi - Augmented OSM Change Viewer [attic] they also added some Arabic value into name field (while not moving English name into name:en)
is it bogus or worth preserving somehow?
Their block message speaks about adding fictional roads so likely reverting all their edits may make sense.
Though Changeset: 160320477 | OpenStreetMap made later causes edit conflict 
And I see no problems with achavi - Augmented OSM Change Viewer [attic] itself. Though I am not familiar with area at all. Maybe achavi - Augmented OSM Change Viewer [attic] should be reverted, then achavi - Augmented OSM Change Viewer [attic] should be reverted and then initial revert of 160320477 should be reverted, restoring 160320477 ?
@SomeoneElse as it looks like a trickier issue (is it fine to ping you like this?)
Hi! Since the changeset was made by a blocked user and is causing issues, reverting it is tricky due to later conflicts. A good approach could be to revert the changes in stages, starting with the user’s edits, but make sure to check for conflicts like with changeset 160320477. If you’re still stuck, reaching out to a more experienced mapper or a moderator could help. Hope this helps!
The block message has a ticket number on it. If you email data@openstreetmap.org with that ticket number in square brackets in the subject it’ll reach the person dealing with the ticket. I can’t comment on what their bandwidth for replying will be, as like all of us, they are a volunteer too.
As a general principle, reverts are best done “in one go” rather than piecemeal, but please coordinate with the DWG person handling the ticket before doing that.
I’d like to thank everyone for their help. I took some time to review each changeset, along with the ones that followed, to check for any conflicts. Everything is back to normal now.