<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
</head>
<body>
<div><br></div><div><br></div><div><br></div><div>Oct 24, 2021, 03:45 by K.y.l.e@outlook.co.nz:<br></div><blockquote class="tutanota_quote" style="border-left: 1px solid #93A3B8; padding-left: 10px; margin-left: 5px;"><div class=""><p class="">> How crevasses can be in rock outside glacier?<br></p><p class=""> <br></p><p class="">I think the extent of the glaciers from the ADD import don’t quite match the glaciers that LINZ has surveyed.<br></p><p class="">There seem to be only a few cases like this, right at the edge of the glacier, we can delete these if you like.<br></p></div></blockquote><div dir="auto">The question is <br></div><div dir="auto">- is glacier area data incorrect?<br></div><div dir="auto">- is remaining creevace data of the same low quality? Just not obviously detectable?<br></div><div dir="auto">If this was missed - what else was not properly reviewed?<br></div><blockquote class="tutanota_quote" style="border-left: 1px solid #93A3B8; padding-left: 10px; margin-left: 5px;"><div class=""><p class="">> How you plan to update this data?<br></p><p class=""> <br></p><p class="">Using the same system as the ongoing address update, you can try it yourself from <a target="_blank" rel="noopener noreferrer" href="https://osm-nz.github.io/RapiD">https://osm-nz.github.io/RapiD</a><br></p><p class="">It can handle the complex aspects like moving, editing, and deleting data.<br></p></div></blockquote><div dir="auto">So OSM would be reduced to mirroring some official dataset? <br></div><div dir="auto">With the most glaring errors hidden but remaining data hidden?<br></div><blockquote class="tutanota_quote" style="border-left: 1px solid #93A3B8; padding-left: 10px; margin-left: 5px;"><div class=""><div dir="auto">> Primary effect is to make this area uneditable.<br></div><p class=""> <br></p><p class="">Not sure what you mean by this. This area is just as editable as any other part of the world, bearing in mind the lack of good quality aerial imagery.<br></p></div></blockquote><div dir="auto">Primary problems caused by low quality imports range from<br></div><div dir="auto">- many mappers especially new are unaware that low quality data mismatching reality,<br></div><div dir="auto">especially imported data, can be freely deleted<br></div><div dir="auto">- even if they aware of this - it is often very tedious to do this, especially for new people<br></div><div dir="auto">- in general people are often far more motivated by mapping something new<br></div><div dir="auto">over repairing garbage<br></div><div dir="auto"><br></div><div dir="auto">Obviously all of that applies only to bad imported data, imports of data that is as <br></div><div dir="auto">good as people would map are extremely helpful.<br></div><div dir="auto"><br></div><div dir="auto">But I was editing in some places where for example people imported massive <br></div><div dir="auto">forest multipolygons (thousands of elements) or import of the same features was done<br></div><div dir="auto">multiple times or import utterly mismatched reality or someone imported data that<br></div><div dir="auto">actually no longer existed.<br></div><div dir="auto"><br></div><div dir="auto">It was confusing and miserable experience and for someone new it would be <br></div><div dir="auto">likely enough to completely discourage them from contributing.<br></div><div dir="auto"><br></div><div dir="auto">I also encountered many requests, even from long term mappers to<br></div><div dir="auto">help with areas especially affected by imports that made editing nearly impossible<br></div><div dir="auto">in a given area.<br></div><div dir="auto"><br></div><div dir="auto"><div dir="auto">If you are unaware that bad import can heavily damage editability and<br></div><div dir="auto">you are not taking this into account then I would strongly encourage<br></div><div dir="auto">to avoid doing this Hydrographic data import from LINZ.<br></div></div><blockquote class="tutanota_quote" style="border-left: 1px solid #93A3B8; padding-left: 10px; margin-left: 5px;"><div class=""><p class="">> Also, I want to repeat request for linking specific posting on mailing list that announced plan to import this features.<br></p><p class="">> Changesets that mass added this features miss links to relevant import documentation.<br></p><p class=""> <br></p><p class="">I think I answered all this in our other conversation, in addition, here is the link to talk-nz which I didn’t include <a target="_blank" rel="noopener noreferrer" href="https://lists.openstreetmap.org/pipermail/talk-nz/2021/thread.html">https://lists.openstreetmap.org/pipermail/talk-nz/2021/thread.html</a><br></p><p class="">All changesets made after 6/10/21 have source=<a target="_blank" rel="noopener noreferrer" href="https://wiki.osm.org/LINZ">https://wiki.osm.org/LINZ</a>, in addition to attribution=<a target="_blank" rel="noopener noreferrer" href="https://wiki.openstreetmap.org/wiki/Contributors#LINZ"><span style="color: rgb(34, 68, 221);"><span style="font-family:"Segoe UI", sans-serif" class=""><span style="font-size:10.5pt" class="">https://wiki.openstreetmap.org/wiki/Contributors#LINZ</span></span></span></a> which they always had. I hope this addresses that problem.<br></p></div></blockquote><div dir="auto">I am asking about announcement on imports mailing list. It is obligatory and gives<br></div><div dir="auto">people to stop harmful imports. And as far as I know imports that failed this requirement<br></div><div dir="auto">can be freely reverted.<br></div><div dir="auto"><br></div><div dir="auto">(I understand that small local and uncontroversial imports are often not doing this,<br></div><div dir="auto">and in such case such reverts would be unhelpful, but it is not one of such cases)<br></div> </body>
</html>