[Talk-us] Another day, another bad import

[Toby Murray]

So it gets worse. It seems that the failure of this changeset was
probably noticed. Later the same day, another changeset[1] was created
that uploaded duplicate nodes but also got at least some (but
apparently not all) of the ways in there.

Then some god damned bot came along and merged all the duplicate
nodes[2] so now I can't revert the original changeset because each
merged node creates a conflict. And since there is no guarantee that
the merge bot only affected the NHD imports, I don't think it would be
a good idea to revert the merge just so I can turn around and revert
the NHD import.

I'm using the JOSM plugin. Does anyone know if the revert script in
SVN handles this type of situation any better? Ideally there would be
an option to delete all nodes in the changeset except if the node is
in use by another way. Or is there a better way to handle this?
Tomorrow I think I may try to use my local pgsnapshot database to
query all untagged, unconnected nodes in the region and nuke them from
that.

Automated edits for the fail.

[1] http://www.openstreetmap.org/browse/changeset/5194965
[2] http://www.openstreetmap.org/browse/changeset/5786162

Toby