<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=us-ascii"><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;
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;}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
mso-fareast-language:EN-US;}
@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=ET link="#0563C1" vlink="#954F72"><div class=WordSection1><p class=MsoNormal><span lang=EN-GB>Hello. <o:p></o:p></span></p><p class=MsoNormal><span lang=EN-GB><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-GB>I was told in talk-ee that I should send single-paragraph notice to this mailing list, but I think you deserve bit longer message. There's old and long-lasting issue in Estonia with the 2008 building import by user Verbatium. Primarily it had remarkably low quality when it was made and awful quality by modern standards, but it also came from unknown source. Over the past decade, local community has discussed the import several times, but never reached definitive conclusion. For the past few months I have been researching on the matter and after consulting with various sides and analysing imported content, I’ve reached conclusion that buildings were vectorised from Estonian Land Board's WMS service’s Basic Map (1994-2007), which was source allowed to be used in OSM. <o:p></o:p></span></p><p class=MsoNormal><span lang=EN-GB><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-GB>I'd like to run a geometry import in Harjumaa, Estonia for buildings where all nodes were last modified at least 10 years ago. As you might know, geometry in OSM is defined via nodes and ways get their shape via links to nodes. Source dataset is Maa-amet's Estonian topographic dataset (ETAK), which has already been used for OSM building imports since 2019. Main focus and around 80% of modified buildings would be remains of Verbatium's import. Conflation is achieved by only attempting to update buildings where no nodes are shared with other ways, OSM version has less nodes than reference dataset and there are no tags on any of way's nodes. OSM and source's buildings are matched by comparing bounding boxes overlap - building is updated only if there's exactly 1 match with at least 15% overlap.<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-GB><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-GB>Wiki page for import is <a href="https://wiki.openstreetmap.org/wiki/Maa-amet_building_geometry_update">https://wiki.openstreetmap.org/wiki/Maa-amet_building_geometry_update</a> and account to be used is fghj753_import. Upload process to update 32000 out of 44000 buildings took on a testing VM around 10 hours. I should inform you that script uses not just writing, but also reading operations of API. Per every processed building WayFull and per every node NodeWays API functions are called. Thanks to OSM's new Prometheus server it looks like the best time to start import is around 7 PM UTC.<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-GB><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-GB>I have few finalizing questions. Should “source:*=Maa-amet 2021” tag be duplicated onto elements (buildings) and if so, under which subkey (source:geometry?), or would “source=Maa-amet 2021” on changeset suffice? Previous address imports have added source:addr to each building and also regular source tag on changeset. <o:p></o:p></span></p><p class=MsoNormal><span lang=EN-GB>Secondly import guidelines mentioned something about spreading import across wider timeframe, citing old Tiger imports. How important is that and how to achieve that? When i was running import on local VM, it averaged around 3000 buildings per hour, comparable pace as previous 2019 imports. 2008 import ran for over 25 hours straight, importing about 2000 buildings per hour. Should I maybe try to get it running on Raspberry, to throttle import by using Pi’s slow hardware?<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-GB>Are there some recommendations on how to improve import documentation? I wasn't sure what exactly to write into import documentation as wiki documentation of all previous Estonian imports combined have roughly length of this email. Currently I haven’t added row to Import/Catalogue yet. Should I add line for 2008 import as well? <o:p></o:p></span></p><p class=MsoNormal><span lang=EN-GB><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-GB>Best regards,<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-GB>Fghj753<o:p></o:p></span></p></div></body></html>