[OSM-dev] Re : Dealing with conflicts

[yvecai@gmail.com]

Did you had a look at Osmose merge mechanisms ?
Yves

----- Reply message -----
De : "Paul Norman" <penorman at mac.com>
Pour : <dev at openstreetmap.org>
Cc : <imports at openstreetmap.org>, <josm-dev at openstreetmap.org>
Objet : [OSM-dev] Dealing with conflicts
Date : jeu., janv. 24, 2013 09:17


I'm working on software which to be used with importing addresses. I expect
to be able to identify cases where OSM data and remote data source data
conflict. Obviously automatically overwriting OSM data with the remote
source is a no-go, but the quality of the remote source is good enough I
don't want to drop these conflicts, but be able to present them some way in
an editor.

My first thought was JOSM's conflict resolution mechanism. To figure out the
XML format, I went to JOSM, created a conflict and tried to save. JOSM won't
let you save with a conflict and the wiki docs have nothing about conflicts
in the file format, so I'm presuming that it can't be done.

My only other idea was to create a JOSM file that will create conflicts when
the objects in it are updated. I am not sure if this is possible in all
cases and it seems like a bad way to do it. 

Is anyone aware of a better way to handle this?

The properties that may conflict between the two sources are tagging and in
the case of a feature represented by node, its position. The case of two
conflicting way geometries is beyond the scope of what I am doing.


_______________________________________________
dev mailing list
dev at openstreetmap.org
http://lists.openstreetmap.org/listinfo/dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/dev/attachments/20130124/93357a4b/attachment.html>