<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;}
@font-face
{font-family:Verdana;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";
mso-fareast-language:EN-US;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
p
{mso-style-priority:99;
mso-margin-top-alt:auto;
margin-right:0cm;
mso-margin-bottom-alt:auto;
margin-left:0cm;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
span.EmailStyle17
{mso-style-type:personal;
font-family:"Verdana","sans-serif";
color:windowtext;
font-weight:normal;
font-style:normal;}
span.inline-comment-marker
{mso-style-name:inline-comment-marker;}
span.EmailStyle20
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:70.85pt 70.85pt 70.85pt 70.85pt;}
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-CA" link="#0563C1" vlink="#954F72" style="word-wrap:break-word">
<div class="WordSection1">
<p class="MsoNormal"><span style="color:#1F497D">Bonjour Pauline,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">IMHO, this is a good initiative. OSM best practices have evolved with the community and keeping data as close as possible to current rules - when possible - is in everyone’s interest.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">The current problem arises from a 2009 consensus made within the Canadian OSM community, which was later documented in the wiki [1] (look at the history). At that time, there were no such precise rules on the
structure of data or on the procedure for importing data.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">So, as long as the relevant codes of conduct are respected, I agree with the project.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">Daniel<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">[1] <a href="https://wiki.openstreetmap.org/wiki/CanVec:_Geometric_Model">
https://wiki.openstreetmap.org/wiki/CanVec:_Geometric_Model</a><o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal"><b><span lang="EN-US" style="font-size:10.0pt;font-family:"Tahoma","sans-serif";mso-fareast-language:EN-CA">From:</span></b><span lang="EN-US" style="font-size:10.0pt;font-family:"Tahoma","sans-serif";mso-fareast-language:EN-CA"> OSM [mailto:OSM@tomtom.com]
<br>
<b>Sent:</b> Thursday, December 02, 2021 04:44<br>
<b>To:</b> talk-ca@openstreetmap.org<br>
<b>Subject:</b> [Talk-ca] [bot] Proposal to fix issue with duplicated inner polygons in Canada<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<table class="MsoNormalTable" border="0" cellspacing="3" cellpadding="0" width="100%" style="width:100.0%">
<tbody>
<tr>
<td style="padding:0cm 0cm 0cm 0cm"></td>
<td style="padding:0cm 0cm 0cm 0cm">
<p><span lang="EN-US">Hello everyone,<br>
</span><span class="inline-comment-marker"><span lang="FR">Bonjour à tous,</span></span><span lang="EN-US"><o:p></o:p></span></p>
<p><span lang="EN-US">I'm Paulina from TomTom.<o:p></o:p></span></p>
<p><span class="inline-comment-marker"><span lang="EN-US">We would like to join your conversation and introduce our team to you.</span></span><span lang="EN-US"><o:p></o:p></span></p>
<p><span lang="EN-US">You might have read about TomTom’s OSM activities in this </span>
<a href="https://weeklyosm.eu/archives/14716"><span lang="EN-US">weekly OSM overview</span></a><span lang="EN-US">, or in our own blog posts (</span><a href="https://www.tomtom.com/blog/maps/tomtom-openstreetmaps-mapmetrics-map-editing/"><span lang="EN-US">this
one</span></a><span lang="EN-US"> and </span><a href="https://www.tomtom.com/blog/maps/the-battle-for-quality-maps/"><span lang="EN-US">this one</span></a><span lang="EN-US">). Our team is performing data analysis in OSM to identify issues worth fixing.<o:p></o:p></span></p>
<p><span class="inline-comment-marker"><span lang="EN-US">In Canada in particular, we've encountered an issue related to double inner polygons. The geometry of the multipolygon inner ring is duplicated: one is in a relation but without a tag and another has
tags but is not part of the relation (</span><a href="http://osmose.openstreetmap.fr/en/issues/open?item=1170&source=&class=1&username=&bbox="><span lang="EN-US">Osmose Rule 1170 Class 1</span></a></span><span class="inline-comment-marker"><span lang="EN-US">
"Double inner polygon"). </span></span><span lang="EN-US"><o:p></o:p></span></p>
<p><span class="inline-comment-marker"><span lang="EN-US">Following the </span><a href="https://wiki.openstreetmap.org/wiki/Automated_Edits_code_of_conduct"><span lang="EN-US">Automated Edits code of conduct</span></a></span><span class="inline-comment-marker"><span lang="EN-US">,
we have developed a bot that would be useful in solving this issue. All details about it (explanation of the algorithm, examples, etc.) are described on the dedicated wiki page
</span><a href="https://wiki.openstreetmap.org/wiki/Automated_edits/TTmechanicalupdates/Fix_issue_with_duplicated_inner_polygons_in_Canada"><span lang="EN-US">https://wiki.openstreetmap.org/wiki/Automated_edits/TTmechanicalupdates/Fix_issue_with_duplicated_inner_polygons_in_Canada</span></a></span><span class="inline-comment-marker"><span lang="EN-US">.</span></span><span lang="EN-US"><o:p></o:p></span></p>
<p><span class="inline-comment-marker"><span lang="EN-US">Our internal analysis has shown that this problem is primarily caused by an import of CanVec data. A<span style="color:#172B4D">ccording to the
</span></span><span style="color:#172B4D"><a href="https://wiki.openstreetmap.org/wiki/CanVec#Issues_found_in_OSM"><span lang="EN-US">CanVec OSM wiki documentation</span></a></span></span><span class="inline-comment-marker"><span lang="EN-US" style="color:#172B4D">,
the issue is already known by the community and mentioned there as "Duplicate land features". The bot is suitable for CanVec, but the double inner polygon issue appears in around 3,000 examples that do not have a source mentioned in their tags. For these issues,
we would like your opinion about whether we should also fix them (please see the
</span><span style="color:#172B4D"><a href="https://wiki.openstreetmap.org/wiki/Automated_edits/TTmechanicalupdates/Fix_issue_with_duplicated_inner_polygons_in_Canada#Discussion"><span lang="EN-US">Discussion</span></a></span></span><span class="inline-comment-marker"><span style="color:#172B4D">
<span lang="EN-US">part in the wiki documentation).</span></span></span><span lang="EN-US"><o:p></o:p></span></p>
<p><span class="inline-comment-marker"><span lang="EN-US" style="color:black">It is worth mentioning that in the past, we've already gained experience with mechanical updates in OSM by running a bot to update night-time urban speed limits in Poland (</span></span><span class="inline-comment-marker"><span lang="EN-US" style="color:#333333">see
the proposal mentioned in this </span><span style="color:black"><a href="https://weeklyosm.eu/archives/14709"><span lang="EN-US">weeklyOSM summary</span></a></span></span><span class="inline-comment-marker"><span lang="EN-US" style="color:black">, and the
</span><span style="color:black"><a href="https://forum.openstreetmap.org/viewtopic.php?id=73116"><span lang="EN-US">forum thread</span></a></span></span><span class="inline-comment-marker"><span lang="EN-US" style="color:black"> about this action).</span></span><span lang="EN-US"><o:p></o:p></span></p>
<p><span class="inline-comment-marker"><span lang="EN-US">We propose to do a test run by updating invalid polygons in Southwestern Ontario</span></span><span lang="EN-US" style="color:#202122">, where 800 cases are logged by the Osmose rule.</span><span lang="EN-US"><o:p></o:p></span></p>
<p><span class="inline-comment-marker"><span lang="EN-US">Per the Automated Code of Conduct, we will wait for your feedback before we begin. We look forward to building and improving OSM together with you!</span></span><span lang="EN-US"><o:p></o:p></span></p>
<p><span class="inline-comment-marker">Kind regards,</span><br>
<span class="inline-comment-marker">Paulina.</span><o:p></o:p></p>
</td>
</tr>
</tbody>
</table>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
</div>
</body>
</html>