<html 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 15 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
line-height:normal;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
p.MsoNoSpacing, li.MsoNoSpacing, div.MsoNoSpacing
{mso-style-priority:1;
margin:0cm;
margin-bottom:.0001pt;
line-height:normal;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
.MsoChpDefault
{mso-style-type:export-only;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:70.85pt 70.85pt 70.85pt 70.85pt;}
div.WordSection1
{page:WordSection1;}
--></style></head><body lang=EN-GB link=blue vlink="#954F72"><div class=WordSection1><p style='margin-bottom:0cm;margin-bottom:.0001pt;line-height:normal'>When multiple errors appear in the same location the question is what to do? </p><p class=MsoNoSpacing>The simplest option is, nothing. Wait until a mapper is correcting all the related errors. </p><p class=MsoNoSpacing>Most of the detectors, inspectors, renderers, data preparation tools… select this option today. Consequently, all publicly available maps repeat the same errors what is, of course, wrong. </p><p class=MsoNoSpacing>Let us take an illustrative example here <a href="https://osm.org/go/cCcWZjGW">https://osm.org/go/cCcWZjGW</a> . </p><p class=MsoNoSpacing>A careful analyses shows that there are several serious errors in this location. Let us mention some.</p><p class=MsoNoSpacing>1.There are two radically different partly overlapping lakes in the location.</p><p class=MsoNoSpacing>2.None of the lakes are close to fit into the hole in the forest area.</p><p class=MsoNoSpacing>3.The forest and any of the lakes overlap considerably.</p><p class=MsoNoSpacing>4.The island in one of the lakes is just partly invisible (overwritten by the other lake).</p><p class=MsoNoSpacing>5.The obsolete natural=land tag is used for several node objects in the lakes.</p><p class=MsoNoSpacing>6.The place=islet tag is used for several nodes without the name tag and value (so, meaningless).</p><p class=MsoNoSpacing>If there were just a few cases like described one could contact the corresponding mappers or just make a note description on the location. Unfortunately the number of cases like the illustrated is so large that neither of the mentioned source data correction models is feasible. Yet, it is worth to mention that some data preparation chains perfectly resolves this complex error issue in their GIS or map-making systems.</p><p class=MsoNoSpacing>Sandor</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Sent from <a href="https://go.microsoft.com/fwlink/?LinkId=550986">Mail</a> for Windows 10</p><p class=MsoNormal><o:p> </o:p></p></div></body></html>