[Talk-us] Duplicate TIGER imports
A few weeks after DaveHansen imported the TIGER data for Ohio [1], RSatterf reimported the data for Greene County, Ohio [2]. As a result, every single way in the county is duplicated. On top of that, RSatterf's import also added a loose node (not connected to any way) for every node of every way in the county. Here's an example at the Montgomery–Greene county line [3]. It's a real mess, and it looks like we just need to delete every node or way last edited by RSatterf. We should keep ways that've been edited by another user since then, because in some cases DaveHansen's motorways etc. have probably been deleted in favor of RSatterf's. So does anyone have a handy mass deletion script? [1] http://www.itoworld.com/product/osm/map?area=1053:10style=_default_osm_usersshow=user:5900colour=normal [2] http://www.itoworld.com/product/osm/map?area=1053:10style=_default_osm_usersshow=user:24166colour=normal [3] http://www.openstreetmap.org/edit?lat=39.68902lon=-84.10627zoom=16 -- Minh Nguyenm...@zoomtown.com AIM: trycom2000; Jabber: m...@1ec5.org; Blog: http://notes.1ec5.org/ ___ Talk-us mailing list Talk-us@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk-us
Re: [Talk-us] Duplicate TIGER imports
On Tue, 2009-04-14 at 15:41 -0700, Minh Nguyen wrote: A few weeks after DaveHansen imported the TIGER data for Ohio [1], RSatterf reimported the data for Greene County, Ohio [2]. As a result, every single way in the county is duplicated. On top of that, RSatterf's import also added a loose node (not connected to any way) for every node of every way in the county. Here's an example at the Montgomery–Greene county line [3]. It's a real mess, and it looks like we just need to delete every node or way last edited by RSatterf. We should keep ways that've been edited by another user since then, because in some cases DaveHansen's motorways etc. have probably been deleted in favor of RSatterf's. So does anyone have a handy mass deletion script? Urg. That's too bad. Actually, on the counties that I screwed up on and had to remove and re-apply, I just did it with pieces in JOSM I think. The scripts that I do have to do it are pretty tied to the BerkeleyDB format that I used for my cache. -- Dave ___ Talk-us mailing list Talk-us@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk-us
Re: [Talk-us] Duplicate TIGER imports
On Tue, Apr 14, 2009 at 5:41 PM, Minh Nguyen m...@1ec5.org wrote: A few weeks after DaveHansen imported the TIGER data for Ohio [1], RSatterf reimported the data for Greene County, Ohio [2]. As a result, every single way in the county is duplicated. On top of that, RSatterf's import also added a loose node (not connected to any way) for every node of every way in the county. Here's an example at the Montgomery–Greene county line [3]. It's a real mess, and it looks like we just need to delete every node or way last edited by RSatterf. We should keep ways that've been edited by another user since then, because in some cases DaveHansen's motorways etc. have probably been deleted in favor of RSatterf's. So does anyone have a handy mass deletion script? It probably wouldn't be too hard to whip up something that uses the extended API to query the database and generate an OSM XML file you could churn through using the bulk uploader script (probably just an XSLT transform of the returned XML would do it). The only issue is that you might have some shared nodes that are in-use by ways that you don't want to delete. After API 0.6 is up it would probably be a lot less of a pain to do, too. Chris ___ Talk-us mailing list Talk-us@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk-us
Re: [Talk-us] Duplicate TIGER imports
On Tue, 2009-04-14 at 19:22 -0500, Chris Lawrence wrote: On Tue, Apr 14, 2009 at 5:41 PM, Minh Nguyen m...@1ec5.org wrote: A few weeks after DaveHansen imported the TIGER data for Ohio [1], RSatterf reimported the data for Greene County, Ohio [2]. As a result, every single way in the county is duplicated. On top of that, RSatterf's import also added a loose node (not connected to any way) for every node of every way in the county. Here's an example at the Montgomery–Greene county line [3]. It's a real mess, and it looks like we just need to delete every node or way last edited by RSatterf. We should keep ways that've been edited by another user since then, because in some cases DaveHansen's motorways etc. have probably been deleted in favor of RSatterf's. So does anyone have a handy mass deletion script? It probably wouldn't be too hard to whip up something that uses the extended API to query the database and generate an OSM XML file you could churn through using the bulk uploader script (probably just an XSLT transform of the returned XML would do it). The only issue is that you might have some shared nodes that are in-use by ways that you don't want to delete. I used the xapi interface and I'm already running through them to clean out the duplicates. Minh, I seee 27 standalone nodes of yours that you've fixed up. Do you mind if we just delete these? -- Dave ___ Talk-us mailing list Talk-us@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk-us
Re: [Talk-us] Duplicate TIGER imports
On 4/14/09 5:25 PM, Dave Hansen wrote: On Tue, 2009-04-14 at 19:22 -0500, Chris Lawrence wrote: On Tue, Apr 14, 2009 at 5:41 PM, Minh Nguyenm...@1ec5.org wrote: A few weeks after DaveHansen imported the TIGER data for Ohio [1], RSatterf reimported the data for Greene County, Ohio [2]. As a result, every single way in the county is duplicated. On top of that, RSatterf's import also added a loose node (not connected to any way) for every node of every way in the county. Here's an example at the Montgomery–Greene county line [3]. It's a real mess, and it looks like we just need to delete every node or way last edited by RSatterf. We should keep ways that've been edited by another user since then, because in some cases DaveHansen's motorways etc. have probably been deleted in favor of RSatterf's. So does anyone have a handy mass deletion script? It probably wouldn't be too hard to whip up something that uses the extended API to query the database and generate an OSM XML file you could churn through using the bulk uploader script (probably just an XSLT transform of the returned XML would do it). The only issue is that you might have some shared nodes that are in-use by ways that you don't want to delete. I used the xapi interface and I'm already running through them to clean out the duplicates. Minh, I seee 27 standalone nodes of yours that you've fixed up. Do you mind if we just delete these? -- Dave Be my guest. Thanks for your help! -- Minh Nguyenm...@zoomtown.com AIM: trycom2000; Jabber: m...@1ec5.org; Blog: http://notes.1ec5.org/ ___ Talk-us mailing list Talk-us@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk-us
