[OSM-talk] import de-duplication

Andy Robinson Andy_J_Robinson at blueyonder.co.uk
Thu Jul 5 11:16:04 BST 2007


Simon Hewison wrote:
>Sent: 05 July 2007 11:03 AM
>To: talk at openstreetmap.org
>Subject: [OSM-talk] import de-duplication
>
>Just had a few thoughts about systems to merge in large datasets (AND,
>Tiger etc).
>
>Where there is existing data in the vicinity, we need to search both
>datasets
>for attributes that match, and where there is a match, do we update OSM, or
>leave it alone?
>
>For instance, if AND says the equivalent of a segment from X1,Y1 to X2,Y2
>is
>highway=motorway;oneway=true;ref=A17.. And OSM says there's a segment from
>X1+0.000023,Y1-0.00064 to X2-0.00037,Y2+0.0000567 is highway=motorway.. Do
>we
>expect it's actually the same road? If so, do we just update the tags on
>the
>OSM data set.
>
>The other option would be to leave a de-militarized zone for a few metres
>surrounding the existing features in the OSM data set, and for the AND data
>not to be automatically imported but the nearest features from the AND
>dataset
>tagged 'here be dragons'; then for humans to go in and join things up on
>the
>borders.

I could imagine in JOSM the data is downloaded via two API calls. One for
the OSM data and one for the AND data. These sit on two separate layers in
JOSM but with the facility to merge the data to a new layer. It's this new
layer that gets uploaded to the OSM db.

Cheers

Andy

Andy Robinson
Andy_J_Robinson at blueyonder.co.uk 


>
>--
>Simon Hewison
>
>
>
>_______________________________________________
>talk mailing list
>talk at openstreetmap.org
>http://lists.openstreetmap.org/cgi-bin/mailman/listinfo/talk






More information about the talk mailing list