Paul - Thanks for this - we'll take a look at it / test it with the Seattle Import data & report back with lessons learned! Thanks, Jeff
On Sun, Dec 9, 2012 at 1:36 AM, Paul Norman <[email protected]> wrote: > For the last couple of weeks I've been working on addressmerge, a tool to > post-process address data by comparing it with existing OSM data. I have > pushed release 0.1 to https://github.com/pnorman/addressmerge > > Currently it will take a file in importable .osm format, compare it with > existing OSM data in an imposm database and create a resulting importable > .osm file with address nodes that duplicate existing data removed. > > It will correctly handle addresses on building ways, multipolygons and > anything else in the OSM data. It does not currently handle addresses on > objects other than nodes in the import data. > > Requirements: > > An imposm database > imposm.parser > python-lxml > psycopg2 > > Limitations: > It relies on imposm.parser which breaks on some XML files. To fix this try > running xmllint --format original.osm > reformatted.osm > > It omits any ways or relations in the input file, relevant or not. > > The documentation is currently very minimal. > > I intend to make it handle other common address formats aside from > addresses > is a decent amount more complicated. > > > _______________________________________________ > Imports mailing list > [email protected] > http://lists.openstreetmap.org/listinfo/imports > -- Jeff Meyer Global World History Atlas www.gwhat.org [email protected] 206-676-2347
_______________________________________________ dev mailing list [email protected] http://lists.openstreetmap.org/listinfo/dev
