<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type content="text/html; charset=utf-8"><meta name=Generator content="Microsoft Word 14 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
{mso-style-priority:99;
mso-style-link:"Balloon Text Char";
margin:0in;
margin-bottom:.0001pt;
font-size:8.0pt;
font-family:"Tahoma","sans-serif";}
span.EmailStyle17
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.BalloonTextChar
{mso-style-name:"Balloon Text Char";
mso-style-priority:99;
mso-style-link:"Balloon Text";
font-family:"Tahoma","sans-serif";}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri","sans-serif";}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body lang=EN-US link=blue vlink=purple><div class=WordSection1><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>According to the wiki docs the only editor in osmose is a raw XML editor. If I wanted to edit raw XML I could do so already. Also according to the docs the backend won’t work for regions outside of France. I suspect that’s wrong and there’s no reason why I couldn’t set it up and run it, but a backend wouldn’t help.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><div style='border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in 4.0pt'><div><div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'><p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'> yvecai@gmail.com [mailto:yvecai@gmail.com] <br><b>Sent:</b> Thursday, January 24, 2013 1:44 AM<br><b>To:</b> Paul Norman; dev@openstreetmap.org<br><b>Cc:</b> imports@openstreetmap.org; josm-dev@openstreetmap.org<br><b>Subject:</b> Re : [OSM-dev] Dealing with conflicts<o:p></o:p></span></p></div></div><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><span style='font-family:"Arial","sans-serif"'>Did you had a look at Osmose merge mechanisms ?<br>Yves<br><br>----- Reply message -----<br>De : "Paul Norman" <<a href="mailto:penorman@mac.com">penorman@mac.com</a>><br>Pour : <<a href="mailto:dev@openstreetmap.org">dev@openstreetmap.org</a>><br>Cc : <<a href="mailto:imports@openstreetmap.org">imports@openstreetmap.org</a>>, <<a href="mailto:josm-dev@openstreetmap.org">josm-dev@openstreetmap.org</a>><br>Objet : [OSM-dev] Dealing with conflicts<br>Date : jeu., janv. 24, 2013 09:17<br><br></span><br>I'm working on software which to be used with importing addresses. I expect<br>to be able to identify cases where OSM data and remote data source data<br>conflict. Obviously automatically overwriting OSM data with the remote<br>source is a no-go, but the quality of the remote source is good enough I<br>don't want to drop these conflicts, but be able to present them some way in<br>an editor.<br><br>My first thought was JOSM's conflict resolution mechanism. To figure out the<br>XML format, I went to JOSM, created a conflict and tried to save. JOSM won't<br>let you save with a conflict and the wiki docs have nothing about conflicts<br>in the file format, so I'm presuming that it can't be done.<br><br>My only other idea was to create a JOSM file that will create conflicts when<br>the objects in it are updated. I am not sure if this is possible in all<br>cases and it seems like a bad way to do it. <br><br>Is anyone aware of a better way to handle this?<br><br>The properties that may conflict between the two sources are tagging and in<br>the case of a feature represented by node, its position. The case of two<br>conflicting way geometries is beyond the scope of what I am doing.<br><br><br>_______________________________________________<br>dev mailing list<br><a href="mailto:dev@openstreetmap.org">dev@openstreetmap.org</a><br><a href="http://lists.openstreetmap.org/listinfo/dev">http://lists.openstreetmap.org/listinfo/dev</a><o:p></o:p></p></div></div></body></html>