If I didn’t hate wetlands enough because they were mosquito-infested swamps of no use to human beings, I would hate them because of how much extra work they cause when they get imported to OSM.
Sorry environmentalists :)
OpenStreetMap
If I didn’t hate wetlands enough because they were mosquito-infested swamps of no use to human beings, I would hate them because of how much extra work they cause when they get imported to OSM.
Sorry environmentalists :)
Discussion
Comment from jumbanho on 18 November 2013 at 22:40
I was just looking around at some of the errors and found some edits by the redaction bot. I wonder if it played a role in that particular disaster.
Comment from eric22 on 19 November 2013 at 20:41
Interesting theory. But in many places, it looks to me like things were horribly broken from the beginning. For example the following link, where points that should be on one way are randomly distributed between two ways.
http://tools.geofabrik.de/osmi/?view=multipolygon&lon=-89.93124&lat=30.35450&zoom=17&overlays=invalid_geometry_hull,duplicate_ways,intersections,intersection_lines,ring_not_closed_hull,ring_not_closed,unconnected_end_nodes,touching_inner_rings_hull,touching_inner_rings,role_mismatch_hull,role_mismatch,ways,role_markers,way_end_nodes,way_nodes
Comment from jumbanho on 20 November 2013 at 04:34
Those objects were also touched by the redaction account. I remember wierd stuff like that happening due to ways being split by non-agreeing users then those entire segments being redacted. This looks like compounding data issues with imports and redaction.