NOTICE: help.openstreetmap.org is no longer in use from 1st March 2024. Please use the OpenStreetMap Community Forum

I spotted a user import a lot of bad data that appears to overlap or is a copy of existing data - in the wrong spot. There are hundreds of thousands of objects/changes.

Take a look at https://www.openstreetmap.org/note/3543755 as a starting point for the mess.

I think I got the ball rolling correctly but not sure : I put a changeset comment to the apparently bad changesets. There may be more...

What should we be doing at this point to get this fixed up?

asked 04 Feb '23, 16:39

gpserror's gravatar image

gpserror
171101117
accept rate: 0%


You might want to email the DWG for a quick revert.

The more you wait, the more complex the revert will be. And in this specific case, the need of a revert is quite clear.

You can also check the documentation and do the revert yourself, it's usually not that complicated.

And you inform the mapper, and try to see with them what went wrong.

Best regards.

permanent link

answered 04 Feb '23, 17:50

H_mlet's gravatar image

H_mlet
5.4k1781
accept rate: 13%

I sent mail off to the DWG and hope they can handle it, I'm a bit worried about such a big change even if it's a revert. I had submitted a changeset comment which should have sent mail to the user, so I hope that's good on that front.

(04 Feb '23, 18:32) gpserror

Follow this question

By Email:

Once you sign in you will be able to subscribe for any updates here

By RSS:

Answers

Answers and Comments

Markdown Basics

  • *italic* or _italic_
  • **bold** or __bold__
  • link:[text](http://url.com/ "title")
  • image?![alt text](/path/img.jpg "title")
  • numbered list: 1. Foo 2. Bar
  • to add a line break simply add two spaces to where you would like the new line to be.
  • basic HTML tags are also supported

Question tags:

×196
×86
×5

question asked: 04 Feb '23, 16:39

question was seen: 778 times

last updated: 04 Feb '23, 18:32

NOTICE: help.openstreetmap.org is no longer in use from 1st March 2024. Please use the OpenStreetMap Community Forum