I briefly downloaded all sby:bldgtype-tagged ways and relation of Maryland through the overpass-api. Then removed the ones having only a sby:bldgtype tag, run the validator and deleted the duplicated nodes and ways. This would result in a changeset to remove the roughly 71'000 duplicates nodes and ways.
If the area was edited since the import and reverting gets tricky, this might be the option to go, at least the result looks ok at the first glance. Please also note that the conversion step seems to add a building=yes tag on on inner ring of building polygons () which is certainly bad tagging, despite the correct rendering (52 occurrences, so could be fixed manually). M On 22.03.2012, at 12:02, Josh Doe wrote: > On Thu, Mar 22, 2012 at 6:40 AM, Josh Doe <[email protected]> wrote: >> On Wed, Mar 21, 2012 at 10:50 PM, Paul Norman <[email protected]> wrote: >>> If there are duplicated ways and nodes, perhaps reverting is the best >>> option? >> >> Unfortunately I'd agree that reverting these changesets will be the >> easiest and best course of action. Trust me that you'll spend a long >> time cleaning up dupe nodes and ways. Some of the buildings have up to >> four dupe nodes and 3 dupe ways, all from different changesets. > > This is what I can tell from the first few building changesets (not an > extensive investigation): > 10882159: 493 dangling nodes (REVERT) > 10884039: 3517 dangling nodes (REVERT) > 10885267: 1 building node (OK) > 10891857: 5 dangling nodes (REVERT) > 10891870: 8000 dangling nodes (REVERT) > 10893364: building nodes and ways (OK?) > > -Josh > > _______________________________________________ > Imports mailing list > [email protected] > http://lists.openstreetmap.org/listinfo/imports _______________________________________________ Talk-us mailing list [email protected] http://lists.openstreetmap.org/listinfo/talk-us
