<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=Windows-1252">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:Wingdings;
panose-1:5 0 0 0 0 0 0 0 0 0;}
@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;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
{mso-style-priority:34;
margin-top:0cm;
margin-right:0cm;
margin-bottom:0cm;
margin-left:36.0pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
.MsoChpDefault
{mso-style-type:export-only;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
{page:WordSection1;}
/* List Definitions */
@list l0
{mso-list-id:974987179;
mso-list-type:hybrid;
mso-list-template-ids:1222648554 -1 134807555 134807557 134807553 134807555 134807557 134807553 134807555 134807557;}
@list l0:level1
{mso-level-start-at:0;
mso-level-number-format:bullet;
mso-level-text:-;
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:20.4pt;
text-indent:-18.0pt;
font-family:"Calibri",sans-serif;
mso-fareast-font-family:"Times New Roman";}
@list l0:level2
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:56.4pt;
text-indent:-18.0pt;
font-family:"Courier New";}
@list l0:level3
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:92.4pt;
text-indent:-18.0pt;
font-family:Wingdings;}
@list l0:level4
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:128.4pt;
text-indent:-18.0pt;
font-family:Symbol;}
@list l0:level5
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:164.4pt;
text-indent:-18.0pt;
font-family:"Courier New";}
@list l0:level6
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:200.4pt;
text-indent:-18.0pt;
font-family:Wingdings;}
@list l0:level7
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:236.4pt;
text-indent:-18.0pt;
font-family:Symbol;}
@list l0:level8
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:272.4pt;
text-indent:-18.0pt;
font-family:"Courier New";}
@list l0:level9
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:308.4pt;
text-indent:-18.0pt;
font-family:Wingdings;}
ol
{margin-bottom:0cm;}
ul
{margin-bottom:0cm;}
--></style>
</head>
<body lang="EN-NZ" link="blue" vlink="#954F72" style="word-wrap:break-word">
<div class="WordSection1">
<p class="MsoNormal">Hi Eliot, cc the rest of the mailing list</p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">> I see the proposal excludes addresses "deprecated" (?deleted?) by LINZ<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Sorry, typo. ‘Deprecated’ should be ‘deleted’. I think you’re right – it does make sense to also delete addresses from OSM if LINZ says they no longer exist, but I think this may be controversial. How does the community feel about this?
<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">> I looked at this last year, with similar results<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">I don’t know how I missed that email while looking through the archives, sorry! I did see the emails from 2014-2018 on the imports mailing list though.<o:p></o:p></p>
<p class="MsoNormal">My thoughts on your question from that email thread:<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">> Two broad options for the data source:<o:p></o:p></p>
<p class="MsoNormal">> 1. Changeset from LINZ<o:p></o:p></p>
<p class="MsoNormal">> 2. Full data dump from LINZ, conflation with existing OSM How to process the changes, how to organise the updates (tasking manager?) etc. etc.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">As it stands, I’ve used option 2 to process the data, but if we want to include deletions then we’ll also need LINZ’s changeset.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">> Looking [through] the raw data reports, a couple of tweaks would make them more useful for manual review and cleanup<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Those txt reports will definitely be improved - I was hoping to get feedback on how this data could be best reviewed/processed.
<o:p></o:p></p>
<p class="MsoNormal">I think those are great ideas, some other thoughts I had were:<o:p></o:p></p>
<ul style="margin-top:0cm" type="disc">
<li class="MsoListParagraph" style="margin-left:-15.6pt;mso-list:l0 level1 lfo1">
Generate osmchange files that can be imported into JOSM or Level0 (but not iD sadly)<o:p></o:p></li><li class="MsoListParagraph" style="margin-left:-15.6pt;mso-list:l0 level1 lfo1">
Make some code changes to the RapiD editor to support updating or moving nodes, not just adding data.
<o:p></o:p></li></ul>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">> Perhaps with "wrong location" we'd still want a way to mark these as reviewed and OK from OSM perspective<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Good point. The StreetComplete editor adds an OSM field called check_date= when mappers confirm that post boxes still exist, or road closures are still ongoing. Perhaps we could add the check_date field to addresses that have been reviewed
but no change is required?<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div style="mso-element:para-border-div;border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal" style="border:none;padding:0cm"><b>From: </b><a href="mailto:eliot@blennerhassett.gen.nz">Eliot Blennerhassett</a><br>
<b>Sent: </b>Wednesday, 10 March 2021 11:49<br>
<b>To: </b><a href="mailto:K.y.l.e@outlook.co.nz">Kyle Hensel</a>; <a href="mailto:talk-nz@openstreetmap.org">
talk-nz</a><br>
<b>Subject: </b>Re: [Talk-nz] Continuing the Street Address Import</p>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Hi Kyle,<br>
<br>
I'm very glad to see someone else taking a look at this, and interested in contributing.<br>
<br>
On 9/03/21 10:08 pm, Kyle Hensel wrote:<br>
> Hi all,<br>
> <br>
> I had a look at how many street addresses are missing from OSM, which was rather simple thanks to the `ref:linz:address_id` tag which exists on most address points.<br>
> <br>
> Here are some stats:<br>
> <br>
> - 1.9 million address points in OSM are still ‘perfect’ since the initial import in 2017.<br>
> <br>
> - about 39,000 addresses in OSM almost perfectly match LINZ's data, but are just missing the `ref:linz:address_id` tag (the majority of these are in Te Anau and Napier where they were merged with buildings and the ref was removed)<br>
> <br>
> - about 17,000 addresses have been modified by LINZ, so the OSM data is now out-of-date (e.g. spelling corrected, suburb changed)<br>
> <br>
> - <300 addresses have been duplicated by mappers, so there are now two nodes with the same `ref:linz:address_id` tag<br>
> <br>
> - And finally, 161,000 new addresses are totally missing from OSM.<br>
<br>
I looked at this last year, with similar results. <a href="https://lists.openstreetmap.org/pipermail/talk-nz/2020/000221.html">
https://lists.openstreetmap.org/pipermail/talk-nz/2020/000221.html</a> my starting point was a changeset
<br>
from LINZ that contained changes since the import.<br>
<br>
> I'm a regular OSM contributor (username kylenz) and I've been thinking about how this dataset could be updated.<br>
> <br>
> Since the original import in 2017, the RapiD editor has emerged, which is a modified version of the iD editor, designed to speed up importing data in a controlled manner.<br>
> <br>
> I've created a detailed wiki page over at <a href="https://wiki.openstreetmap.org/wiki/Import/New_Zealand_Street_Addresses_(2021">
https://wiki.openstreetmap.org/wiki/Import/New_Zealand_Street_Addresses_(2021</a>) <<a href="https://wiki.openstreetmap.org/wiki/Import/New_Zealand_Street_Addresses_(2021">https://wiki.openstreetmap.org/wiki/Import/New_Zealand_Street_Addresses_(2021</a>)> which
documents a proposal to use a custom version of the RapiD editor to import the new addresses, and to fix incorrect data in addresses. I've also created a quick proof-of-concept which you can try out here:
<a href="https://linz-addr.kyle.kiwi">https://linz-addr.kyle.kiwi</a> <<a href="https://linz-addr.kyle.kiwi">https://linz-addr.kyle.kiwi</a>> - *NOTE:* it deliberately does not let you upload changesets (yet).<br>
> <br>
> I'd love to hear thoughts and feedback on this proposal, not least from those involved in the original import.<br>
<br>
<br>
<br>
It would be great to eventually catch up with the LINZ data so that the subsequent flow of changes was not overwhelming.<br>
<br>
I see the proposal excludes addresses "deprecated" (?deleted?) by LINZ. I think this needs to be in scope, as these are often replaced by different addresses, e.g. in
<br>
new subdivisions.<br>
<br>
The original import did not include updating existing addresses with the ref:linz:id, I agree with adding this to existing matching addresses.<br>
<br>
----------------------------<br>
Looking the the raw data reports, a couple of tweaks would make them more useful for manual review and cleanup<br>
* turning them into html so that the links are clickable.<br>
* making locations into references to the OSM map<br>
* making LINZ ID link to linz address data - I don't see an easy way to make this a link to linz website data itself<br>
<br>
<br>
E.g. wrong location<br>
2559 <a href="https://osm.org/node/5616392035">https://osm.org/node/5616392035</a> needs to move 834m to
<a href="https://www.openstreetmap.org/#map=17/-45.03458/168.67680">https://www.openstreetmap.org/#map=17/-45.03458/168.67680</a><br>
<br>
With these tweaks some of the errors (duplicate addresses, wrong location) could be knocked off fairly quickly.
<br>
Perhaps with "wrong location" we'd still want a way to mark these as reviewed and OK from OSM perspective. E.g. a house on a large block of land might be far from the nominal location of that address.<br>
<br>
-- <br>
Eliot<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</body>
</html>