This is a static archive of our old OpenStreetMap Help Site. Please post any new questions and answers at community.osm.org.

Cannot revert a (huge) changeset

1

Hi,

While adding missing buildings from the Cadastre to OSM, I mistakenly selected the wrong layer in JOSM and uploaded a HUGE amount of (sometimes conflicting) data to a new changeset in OSM. Hitting the Cancel button as soon as I realized my mistake wasn't enough to prevent the damages :(.

Now, the changeset seems so enourmous that I cannot download its content (Request Timeout, ...) while trying the revert tool provided by JOSM or the revert.pl script.

The faulty changeset ID is #41683384. Can someone please help me to solve this?

Thanks.

asked 25 Aug '16, 13:12

GCN's gravatar image

GCN
26112
accept rate: 0%


One Answer:

1

You need to talk to the DWG data@osmfoundation.org (and buy them multiple <insert favourite="" beverages="">)

answered 25 Aug '16, 15:34

SimonPoole's gravatar image

SimonPoole ♦
44.7k13326701
accept rate: 18%

So what could possibly be the favourite beverage of the Drinking Wine Group?

(25 Aug '16, 15:43) scai ♦
1

... and wait more than a couple of hours.

We got the mail, but no-one has had chance to look at it yet.

(25 Aug '16, 15:59) SomeoneElse ♦

@SomeoneElse : I sent the e-mail before asking here. I wasn't sure it was the correct way to handle this situation nor if my e-mail had been received/read by someone.

I'd have hoped for a solution that I could try myself and not bother anyone with but... :( I'll be more careful next time.

(25 Aug '16, 17:15) GCN
2

For completeness the "can't revert" problem is further described in https://help.openstreetmap.org/questions/51646/how-to-revert-3-changesets-containing-136000-untagged-nodes/51648 and the links from there (essentially the API allows more objects in one changeset than can be downloaded from the API before it times out).

(26 Aug '16, 18:32) SomeoneElse ♦
1

As requested, the revert has now been done in https://www.openstreetmap.org/changeset/41730738 .

(27 Aug '16, 12:26) SomeoneElse ♦

Source code available on GitHub .