<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=utf-8">
<META NAME="Generator" CONTENT="MS Exchange Server version rmj.rmm.rup.rpr">
<TITLE>RE: [Imports] (Estonia) Maa-amet building geometry update</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/rtf format -->
<P DIR=LTR><SPAN LANG="et"></SPAN><SPAN LANG="et"></SPAN><SPAN LANG="en-gb"><FONT COLOR="#1F497D" FACE="Calibri">> </FONT></SPAN></P>
<P DIR=LTR><SPAN LANG="et"></SPAN><SPAN LANG="et"></SPAN><SPAN LANG="et"></SPAN><SPAN LANG="et"></SPAN><SPAN LANG="en-gb"><FONT COLOR="#1F497D" FACE="Calibri">></FONT></SPAN><SPAN LANG="et"></SPAN><SPAN LANG="en-gb"> <FONT SIZE=2 FACE="Courier New">I really, really, really dislike such debris on objects. Especially as it is often stale anyway - people</FONT></SPAN></P>
<P DIR=LTR><SPAN LANG="et"></SPAN><SPAN LANG="et"></SPAN><SPAN LANG="et"></SPAN><SPAN LANG="en-gb"><FONT SIZE=2 FACE="Courier New">> updating building shape based on aerial/survey rarely remove such tags.</FONT></SPAN></P>
<P DIR=LTR><SPAN LANG="en-gb"><FONT SIZE=2 FACE="Courier New">> </FONT></SPAN></P>
<P DIR=LTR><SPAN LANG="en-gb"><FONT SIZE=2 FACE="Courier New">> Though please ignore me if local community has a different preference. </FONT></SPAN></P>
<P DIR=LTR><SPAN LANG="en-gb"><FONT SIZE=2 FACE="Courier New">> </FONT></SPAN></P>
<P DIR=LTR><SPAN LANG="en-gb"><FONT SIZE=2 FACE="Courier New">> It is also a personal preference that is (I think) well motivated, not OSM rule.</FONT></SPAN></P>
<P DIR=LTR><SPAN LANG="et"></SPAN><SPAN LANG="et"></SPAN><SPAN LANG="en-gb"><FONT COLOR="#1F497D" FACE="Calibri">> </FONT></SPAN></P>
<P DIR=LTR><SPAN LANG="et"></SPAN><SPAN LANG="et"></SPAN><SPAN LANG="en-gb"><FONT COLOR="#1F497D" FACE="Calibri">Only reply from l</FONT></SPAN><SPAN LANG="et"></SPAN><SPAN LANG="et"></SPAN><SPAN LANG="en-gb"><FONT COLOR="#1F497D" FACE="Calibri">ocal mailing list agrees with you. I also sent clarifying question to</FONT></SPAN><SPAN LANG="et"></SPAN><SPAN LANG="et"></SPAN><SPAN LANG="en-gb"> <FONT COLOR="#1F497D" FACE="Calibri">Maa-amet / Land Board, but I don’t think they will reply anytime soon.</FONT></SPAN><SPAN LANG="et"></SPAN><SPAN LANG="et"></SPAN><SPAN LANG="en-gb"><FONT COLOR="#1F497D" FACE="Calibri"></FONT></SPAN><SPAN LANG="et"></SPAN><SPAN LANG="et"></SPAN><SPAN LANG="en-gb"> </SPAN></P>
<P DIR=LTR><SPAN LANG="et"></SPAN><SPAN LANG="et"></SPAN><SPAN LANG="en-gb"></SPAN></P>
<P DIR=LTR><SPAN LANG="en-gb"><FONT COLOR="#1F497D" SIZE=2 FACE="Courier New">> </FONT></SPAN></P>
<P DIR=LTR><SPAN LANG="en-gb"><FONT COLOR="#1F497D" SIZE=2 FACE="Courier New">></FONT></SPAN><SPAN LANG="et"></SPAN><SPAN LANG="et"></SPAN><SPAN LANG="en-gb"> <FONT SIZE=2 FACE="Courier New">For technical side: interrupt script after it made N edits, then restart it the next day?</FONT></SPAN></P>
<P DIR=LTR><SPAN LANG="et"></SPAN><SPAN LANG="et"></SPAN><SPAN LANG="en-gb"><FONT COLOR="#1F497D" SIZE=2 FACE="Courier New">></FONT></SPAN><SPAN LANG="et"></SPAN><SPAN LANG="et"></SPAN><SPAN LANG="en-gb"> <FONT SIZE=2 FACE="Courier New">Or sleep for N seconds after each edit?</FONT></SPAN></P>
<P DIR=LTR><SPAN LANG="et"></SPAN><SPAN LANG="et"></SPAN><SPAN LANG="en-gb"><FONT COLOR="#1F497D" SIZE=2 FACE="Courier New">></FONT></SPAN><SPAN LANG="et"></SPAN><SPAN LANG="et"></SPAN><SPAN LANG="en-gb"><FONT COLOR="#1F497D" SIZE=2 FACE="Courier New"></FONT></SPAN><SPAN LANG="et"></SPAN><SPAN LANG="et"></SPAN><SPAN LANG="en-gb"> </SPAN></P>
<P DIR=LTR><SPAN LANG="et"></SPAN><SPAN LANG="et"></SPAN><SPAN LANG="en-gb"><FONT COLOR="#1F497D" SIZE=2 FACE="Courier New">></FONT></SPAN><SPAN LANG="et"></SPAN><SPAN LANG="et"></SPAN><SPAN LANG="en-gb"> <FONT SIZE=2 FACE="Courier New">When I run bot edit it typically sleeps one minute after every changeset</FONT></SPAN></P>
<P DIR=LTR><SPAN LANG="et"></SPAN><SPAN LANG="et"></SPAN><SPAN LANG="en-gb"><FONT COLOR="#1F497D" SIZE=2 FACE="Courier New">></FONT></SPAN><SPAN LANG="et"></SPAN><SPAN LANG="et"></SPAN><SPAN LANG="en-gb"><FONT COLOR="#1F497D" SIZE=2 FACE="Courier New"> </FONT></SPAN></P>
<P DIR=LTR><SPAN LANG="et"></SPAN><SPAN LANG="et"></SPAN><SPAN LANG="en-gb"></SPAN></P>
<P DIR=LTR><SPAN LANG="et"></SPAN><SPAN LANG="et"></SPAN><SPAN LANG="en-gb"><FONT COLOR="#1F497D" FACE="Calibri">Uploading changeset of 10000 changes took around 20 min on local VM. I’m afraid delaying just</FONT></SPAN><SPAN LANG="et"></SPAN><SPAN LANG="et"></SPAN><SPAN LANG="en-gb"> <FONT COLOR="#1F497D" FACE="Calibri">1</FONT></SPAN><SPAN LANG="et"></SPAN><SPAN LANG="et"></SPAN><SPAN LANG="en-gb"><FONT COLOR="#1F497D" FACE="Calibri"> minute</FONT></SPAN><SPAN LANG="et"></SPAN><SPAN LANG="et"></SPAN><SPAN LANG="en-gb"><FONT COLOR="#1F497D" FACE="Calibri"> between sets</FONT></SPAN><SPAN LANG="et"></SPAN><SPAN LANG="et"></SPAN><SPAN LANG="en-gb"><FONT COLOR="#1F497D" FACE="Calibri"> is</FONT></SPAN><SPAN LANG="et"></SPAN><SPAN LANG="et"></SPAN><SPAN LANG="en-gb"> <FONT COLOR="#1F497D" FACE="Calibri">not enoug</FONT></SPAN><SPAN LANG="et"></SPAN><SPAN LANG="et"></SPAN><SPAN LANG="en-gb"><FONT COLOR="#1F497D" FACE="Calibri">h</FONT></SPAN><SPAN LANG="et"></SPAN><SPAN LANG="et"></SPAN><SPAN LANG="en-gb"><FONT COLOR="#1F497D" FACE="Calibri">.</FONT></SPAN><SPAN LANG="et"></SPAN><SPAN LANG="et"></SPAN><SPAN LANG="en-gb"><FONT COLOR="#1F497D" FACE="Calibri"></FONT></SPAN><SPAN LANG="et"></SPAN><SPAN LANG="et"></SPAN><SPAN LANG="en-gb"> <FONT COLOR="#1F497D" FACE="Calibri">F</FONT></SPAN><SPAN LANG="et"></SPAN><SPAN LANG="et"></SPAN><SPAN LANG="en-gb"><FONT COLOR="#1F497D" FACE="Calibri">or comparison, your bot made 100-300 changes per changeset in</FONT></SPAN><SPAN LANG="et"></SPAN><SPAN LANG="et"></SPAN><SPAN LANG="en-gb"> <FONT COLOR="#1F497D" FACE="Calibri">less than 2 minutes</FONT></SPAN><SPAN LANG="et"></SPAN><SPAN LANG="et"></SPAN><SPAN LANG="en-gb"><FONT COLOR="#1F497D" FACE="Calibri"> and then waited for 1 min. Waiting 0.</FONT></SPAN><SPAN LANG="et"></SPAN><SPAN LANG="et"></SPAN><SPAN LANG="en-gb"><FONT COLOR="#1F497D" FACE="Calibri">5-1</FONT></SPAN><SPAN LANG="et"></SPAN><SPAN LANG="et"></SPAN><SPAN LANG="en-gb"><FONT COLOR="#1F497D" FACE="Calibri"> sec per building (not</FONT></SPAN><SPAN LANG="et"></SPAN><SPAN LANG="et"></SPAN><SPAN LANG="en-gb"> <FONT COLOR="#1F497D" FACE="Calibri">node</FONT></SPAN><SPAN LANG="et"></SPAN><SPAN LANG="et"></SPAN><SPAN LANG="en-gb"> <FONT COLOR="#1F497D" FACE="Calibri">change)</FONT></SPAN><SPAN LANG="et"></SPAN><SPAN LANG="et"></SPAN><SPAN LANG="en-gb"><FONT COLOR="#1F497D" FACE="Calibri"> may double the time consume</FONT></SPAN><SPAN LANG="et"></SPAN><SPAN LANG="et"></SPAN><SPAN LANG="en-gb"><FONT COLOR="#1F497D" FACE="Calibri">d</FONT></SPAN><SPAN LANG="et"></SPAN><SPAN LANG="et"></SPAN><SPAN LANG="en-gb"><FONT COLOR="#1F497D" FACE="Calibri">, but</FONT></SPAN><SPAN LANG="et"></SPAN><SPAN LANG="et"></SPAN><SPAN LANG="en-gb"> <FONT COLOR="#1F497D" FACE="Calibri">seems to be more</FONT></SPAN><SPAN LANG="et"></SPAN><SPAN LANG="et"></SPAN><SPAN LANG="en-gb"><FONT COLOR="#1F497D" FACE="Calibri"> fair solution to delay edits.</FONT></SPAN><SPAN LANG="et"></SPAN><SPAN LANG="et"></SPAN><SPAN LANG="en-gb"><FONT COLOR="#1F497D" FACE="Calibri"> Also in that case uploading would start approaching full day, allowing to start import any time.</FONT></SPAN><SPAN LANG="et"></SPAN><SPAN LANG="et"></SPAN><SPAN LANG="en-gb"> <FONT COLOR="#1F497D" FACE="Calibri"> Honestly I’d prefer to run import</FONT></SPAN><SPAN LANG="et"></SPAN><SPAN LANG="et"></SPAN><SPAN LANG="en-gb"> <FONT COLOR="#1F497D" FACE="Calibri">overnight, but then leaving 2-4 hour chunk for next day doesn</FONT></SPAN><SPAN LANG="et"></SPAN><SPAN LANG="et"></SPAN><SPAN LANG="en-gb"><FONT COLOR="#1F497D" FACE="Calibri">’t make much sense.</FONT></SPAN><SPAN LANG="et"></SPAN><SPAN LANG="et"></SPAN><SPAN LANG="en-gb"><FONT COLOR="#1F497D" FACE="Calibri"> The</FONT></SPAN><SPAN LANG="et"></SPAN><SPAN LANG="et"></SPAN><SPAN LANG="en-gb"> <FONT COLOR="#1F497D" FACE="Calibri">python</FONT></SPAN><SPAN LANG="et"></SPAN><SPAN LANG="et"></SPAN><SPAN LANG="en-gb"> <FONT COLOR="#1F497D" FACE="Calibri">script does support splitting</FONT></SPAN><SPAN LANG="et"></SPAN><SPAN LANG="et"></SPAN><SPAN LANG="en-gb"> <FONT COLOR="#1F497D" FACE="Calibri">the upload.</FONT></SPAN><SPAN LANG="et"></SPAN><SPAN LANG="et"></SPAN><SPAN LANG="en-gb"></SPAN></P>
<P DIR=LTR><SPAN LANG="en-gb"><FONT COLOR="#1F497D" FACE="Calibri">My personal objective on the matter is to complete import by Friday morning</FONT></SPAN><SPAN LANG="et"></SPAN><SPAN LANG="et"></SPAN><SPAN LANG="en-gb"><FONT COLOR="#1F497D" FACE="Calibri">, but I probably don’t have time on Thursday</FONT></SPAN><SPAN LANG="et"></SPAN><SPAN LANG="et"></SPAN><SPAN LANG="en-gb"> <FONT COLOR="#1F497D" FACE="Calibri">evening to start it, meaning that import should be scheduled on Wednesay evening</FONT></SPAN><SPAN LANG="et"></SPAN><SPAN LANG="et"></SPAN><SPAN LANG="en-gb"><FONT COLOR="#1F497D" FACE="Calibri">.</FONT></SPAN><SPAN LANG="et"></SPAN><SPAN LANG="et"></SPAN><SPAN LANG="en-gb"></SPAN></P>
<P DIR=LTR><SPAN LANG="et"></SPAN><SPAN LANG="et"></SPAN><SPAN LANG="en-gb"><FONT COLOR="#1F497D" FACE="Calibri">></FONT></SPAN><SPAN LANG="et"></SPAN><SPAN LANG="en-gb"> Though I think that adding LIDAR based height data should be mentioned in summary</SPAN><SPAN LANG="et"></SPAN><SPAN LANG="en-gb"></SPAN><SPAN LANG="et"></SPAN><SPAN LANG="en-gb"> posted here</SPAN></P>
<P DIR=LTR><SPAN LANG="et"></SPAN><SPAN LANG="et"></SPAN><SPAN LANG="en-gb"></SPAN></P>
<P DIR=LTR><SPAN LANG="et"></SPAN><SPAN LANG="et"></SPAN><SPAN LANG="en-gb"><FONT COLOR="#1F497D" FACE="Calibri">Not much to comment here</FONT></SPAN><SPAN LANG="et"></SPAN><SPAN LANG="et"></SPAN><SPAN LANG="en-gb"> <FONT COLOR="#1F497D" FACE="Calibri">other</FONT></SPAN><SPAN LANG="et"></SPAN><SPAN LANG="et"></SPAN><SPAN LANG="en-gb"><FONT COLOR="#1F497D" FACE="Calibri"> than posting direct link to table:</FONT></SPAN><SPAN LANG="et"> </SPAN><A HREF="https://wiki.openstreetmap.org/wiki/Maa-amet_building_geometry_update#Tagging_Plans"><SPAN LANG="et"></SPAN><SPAN LANG="et"><U></U></SPAN><U><SPAN LANG="en-gb"><FONT COLOR="#0000FF" FACE="Calibri">https://wiki.openstreetmap.org/wiki/Maa-amet_building_geometry_update#Tagging_Plans</FONT></SPAN></U><SPAN LANG="et"></SPAN></A><SPAN LANG="et"></SPAN><SPAN LANG="et"></SPAN><SPAN LANG="en-gb"><FONT COLOR="#1F497D" FACE="Calibri"> and pasting table cell in question:</FONT></SPAN></P>
<P DIR=LTR><SPAN LANG="et"></SPAN><SPAN LANG="et"></SPAN><SPAN LANG="en-gb"><FONT COLOR="#1F497D" FACE="Calibri">></FONT></SPAN><SPAN LANG="et"></SPAN><SPAN LANG="et"></SPAN><SPAN LANG="en-gb"> <FONT COLOR="#1F497D" FACE="Calibri">Dataset also contains lidar-measured building height data for some buildings. Height is only added if any nodes of the building were modified, height=* is not</FONT></SPAN><SPAN LANG="et"></SPAN><SPAN LANG="et"></SPAN><SPAN LANG="en-gb"><FONT COLOR="#1F497D" FACE="Calibri"></FONT></SPAN><SPAN LANG="et"></SPAN><SPAN LANG="et"></SPAN><SPAN LANG="en-gb"> <FONT COLOR="#1F497D" FACE="Calibri">present yet and height recorded in dataset is at least 3 m.</FONT></SPAN><SPAN LANG="et"></SPAN><SPAN LANG="et"></SPAN><SPAN LANG="en-gb"></SPAN></P>
<P DIR=LTR><SPAN LANG="et"></SPAN><SPAN LANG="et"></SPAN><SPAN LANG="en-gb"></SPAN></P>
<P DIR=LTR><SPAN LANG="en-gb"><FONT COLOR="#1F497D" FACE="Calibri">There were concerns about StreetComplete not asking building:levels quest for buildings with height data, but Mateusz has already opened PR</FONT></SPAN><SPAN LANG="et"></SPAN><SPAN LANG="et"></SPAN><SPAN LANG="en-gb"><FONT COLOR="#1F497D" FACE="Calibri"> on SC’s repo</FONT></SPAN><SPAN LANG="et"></SPAN><SPAN LANG="et"></SPAN><SPAN LANG="en-gb"><FONT COLOR="#1F497D" FACE="Calibri"> to solve the</FONT></SPAN><SPAN LANG="et"></SPAN><SPAN LANG="et"></SPAN><SPAN LANG="en-gb"> <FONT COLOR="#1F497D" FACE="Calibri">problem</FONT></SPAN><SPAN LANG="et"></SPAN><SPAN LANG="et"></SPAN><SPAN LANG="en-gb"><FONT COLOR="#1F497D" FACE="Calibri"> from</FONT></SPAN><SPAN LANG="et"></SPAN><SPAN LANG="et"></SPAN><SPAN LANG="en-gb"> <FONT COLOR="#1F497D" FACE="Calibri">the other</FONT></SPAN><SPAN LANG="et"></SPAN><SPAN LANG="et"></SPAN><SPAN LANG="en-gb"><FONT COLOR="#1F497D" FACE="Calibri"></FONT></SPAN><SPAN LANG="et"></SPAN><SPAN LANG="et"></SPAN><SPAN LANG="en-gb"> <FONT COLOR="#1F497D" FACE="Calibri">end.</FONT></SPAN><SPAN LANG="et"></SPAN><SPAN LANG="et"></SPAN><SPAN LANG="en-gb"><FONT COLOR="#1F497D" FACE="Calibri"></FONT></SPAN><SPAN LANG="et"></SPAN><SPAN LANG="et"></SPAN><SPAN LANG="en-gb"> <FONT COLOR="#1F497D" FACE="Calibri">Height data</FONT></SPAN><SPAN LANG="et"></SPAN><SPAN LANG="et"></SPAN><SPAN LANG="en-gb"><FONT COLOR="#1F497D" FACE="Calibri"> is stored as integer, meaning</FONT></SPAN><SPAN LANG="et"></SPAN><SPAN LANG="et"></SPAN><SPAN LANG="en-gb"> <FONT COLOR="#1F497D" FACE="Calibri">1m precision.</FONT></SPAN><SPAN LANG="et"></SPAN><SPAN LANG="et"></SPAN><SPAN LANG="en-gb"><FONT COLOR="#1F497D" FACE="Calibri"> Also I’m planning to remove bit under 200 instances of</FONT></SPAN><SPAN LANG="et"></SPAN><SPAN LANG="et"></SPAN><SPAN LANG="en-gb"> <FONT COLOR="#1F497D" FACE="Calibri">undocumented (CityIdx), legacy (created_by) and duplicate tags (name == addr:housenumber)</FONT></SPAN><SPAN LANG="et"></SPAN><SPAN LANG="et"></SPAN><SPAN LANG="en-gb"><FONT COLOR="#1F497D" FACE="Calibri"> on buildings, where geometry is updated too</FONT></SPAN><SPAN LANG="et"></SPAN><SPAN LANG="et"></SPAN><SPAN LANG="en-gb"><FONT COLOR="#1F497D" FACE="Calibri">. Planning to add height data and</FONT></SPAN><SPAN LANG="et"></SPAN><SPAN LANG="et"></SPAN><SPAN LANG="en-gb"> <FONT COLOR="#1F497D" FACE="Calibri">previous</FONT></SPAN><SPAN LANG="et"></SPAN><SPAN LANG="et"></SPAN><SPAN LANG="en-gb"> <FONT COLOR="#1F497D" FACE="Calibri">local building import’s signature key maaamet:ETAK</FONT></SPAN><SPAN LANG="et"></SPAN><SPAN LANG="et"></SPAN><SPAN LANG="en-gb"><FONT COLOR="#1F497D" FACE="Calibri">.</FONT></SPAN><SPAN LANG="et"></SPAN><SPAN LANG="et"></SPAN><SPAN LANG="en-gb"></SPAN></P>
<P DIR=LTR><SPAN LANG="et"></SPAN><SPAN LANG="et"></SPAN><SPAN LANG="en-gb"></SPAN></P>
<P DIR=LTR><SPAN LANG="et"></SPAN><SPAN LANG="et"></SPAN><SPAN LANG="en-gb"><FONT COLOR="#1F497D" FACE="Calibri">I</FONT></SPAN><SPAN LANG="et"></SPAN><SPAN LANG="et"></SPAN><SPAN LANG="en-gb"><FONT COLOR="#1F497D" FACE="Calibri">’ve</FONT></SPAN><SPAN LANG="et"></SPAN><SPAN LANG="et"></SPAN><SPAN LANG="en-gb"><FONT COLOR="#1F497D" FACE="Calibri"> added two rows to</FONT></SPAN><SPAN LANG="et"></SPAN><SPAN LANG="et"></SPAN><SPAN LANG="en-gb"> <FONT COLOR="#1F497D" FACE="Calibri">Import/Catalogue</FONT></SPAN><SPAN LANG="et"></SPAN><SPAN LANG="et"></SPAN><SPAN LANG="en-gb"><FONT COLOR="#1F497D" FACE="Calibri">, but</FONT></SPAN><SPAN LANG="et"></SPAN><SPAN LANG="et"></SPAN><SPAN LANG="en-gb"> <FONT COLOR="#1F497D" FACE="Calibri">I</FONT></SPAN><SPAN LANG="et"></SPAN><SPAN LANG="et"></SPAN><SPAN LANG="en-gb"><FONT COLOR="#1F497D" FACE="Calibri"> also took liberty to unify</FONT></SPAN><SPAN LANG="et"></SPAN><SPAN LANG="et"></SPAN><SPAN LANG="en-gb"> <FONT COLOR="#1F497D" FACE="Calibri">date formatting of these 3 tables. That</FONT></SPAN><SPAN LANG="et"></SPAN><SPAN LANG="et"></SPAN><SPAN LANG="en-gb"> <FONT COLOR="#1F497D" FACE="Calibri">raised</FONT></SPAN><SPAN LANG="et"></SPAN><SPAN LANG="et"></SPAN><SPAN LANG="en-gb"><FONT COLOR="#1F497D" FACE="Calibri"> an odd question: How many days were in November 2009 (looking at</FONT></SPAN><SPAN LANG="et"></SPAN><SPAN LANG="et"></SPAN><SPAN LANG="en-gb"> <FONT COLOR="#1F497D" FACE="Calibri">„</FONT></SPAN><SPAN LANG="et"></SPAN><SPAN LANG="et"></SPAN><SPAN LANG="en-gb"><FONT COLOR="#1F497D" FACE="Calibri">Spanish administrative borders</FONT></SPAN><SPAN LANG="et"></SPAN><SPAN LANG="et"></SPAN><SPAN LANG="en-gb"><FONT COLOR="#1F497D" FACE="Calibri">“</FONT></SPAN><SPAN LANG="et"></SPAN><SPAN LANG="et"></SPAN><SPAN LANG="en-gb"><FONT COLOR="#1F497D" FACE="Calibri"> Import</FONT></SPAN><SPAN LANG="et"></SPAN><SPAN LANG="et"></SPAN><SPAN LANG="en-gb"><FONT COLOR="#1F497D" FACE="Calibri">)?</FONT></SPAN><SPAN LANG="et"></SPAN><SPAN LANG="et"></SPAN><SPAN LANG="en-gb"></SPAN></P>
<P DIR=LTR><SPAN LANG="en-gb"><FONT COLOR="#1F497D" FACE="Calibri">Fghj753</FONT></SPAN><SPAN LANG="et"></SPAN><SPAN LANG="et"></SPAN><SPAN LANG="en-gb"></SPAN></P>
<P DIR=LTR><SPAN LANG="et"></SPAN><SPAN LANG="et"></SPAN><SPAN LANG="en-gb"></SPAN></P>
<P DIR=LTR><SPAN LANG="et"><B></B></SPAN><SPAN LANG="et"><B></B></SPAN><B><SPAN LANG="en-gb"><FONT FACE="Calibri">From:</FONT></SPAN></B><SPAN LANG="et"></SPAN><SPAN LANG="et"></SPAN><SPAN LANG="en-gb"><FONT FACE="Calibri"> Mateusz Konieczny via Imports <imports@openstreetmap.org><BR>
</FONT></SPAN><SPAN LANG="et"><B></B></SPAN><SPAN LANG="et"><B></B></SPAN><B><SPAN LANG="en-gb"><FONT FACE="Calibri">Sent:</FONT></SPAN></B><SPAN LANG="et"></SPAN><SPAN LANG="et"></SPAN><SPAN LANG="en-gb"><FONT FACE="Calibri"> Monday, May 31, 2021 11:20 AM<BR>
</FONT></SPAN><SPAN LANG="et"><B></B></SPAN><SPAN LANG="et"><B></B></SPAN><B><SPAN LANG="en-gb"><FONT FACE="Calibri">Cc:</FONT></SPAN></B><SPAN LANG="et"></SPAN><SPAN LANG="et"></SPAN><SPAN LANG="en-gb"><FONT FACE="Calibri"> Imports <imports@openstreetmap</FONT></SPAN><SPAN LANG="et"></SPAN><SPAN LANG="et"></SPAN><SPAN LANG="en-us"><FONT FACE="Calibri">.org><BR>
</FONT></SPAN><SPAN LANG="et"><B></B></SPAN><SPAN LANG="et"><B></B></SPAN><B><SPAN LANG="en-us"><FONT FACE="Calibri">Subject:</FONT></SPAN></B><SPAN LANG="et"></SPAN><SPAN LANG="et"></SPAN><SPAN LANG="en-us"><FONT FACE="Calibri"> Re: [Imports] (Estonia) Maa-amet building geometry update</FONT></SPAN></P>
<P DIR=LTR><SPAN LANG="et"></SPAN></P>
<P DIR=LTR><SPAN LANG="et"></SPAN></P>
<P DIR=LTR><SPAN LANG="et">May 30, 2021, 23:10 by </SPAN><A HREF="mailto:fghj753@hot.ee"><SPAN LANG="et"><U><FONT COLOR="#0000FF">fghj753@hot.ee</FONT></U></SPAN><SPAN LANG="et"></SPAN></A><SPAN LANG="et">:</SPAN></P>
<P DIR=LTR><SPAN LANG="et"></SPAN><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.</SPAN><SPAN LANG="et"></SPAN></P>
<P DIR=LTR><SPAN LANG="et">I really, really, really dislike such debris on objects. Especially as it is often stale anyway - people</SPAN></P>
<P DIR=LTR><SPAN LANG="et">updating building shape based on aerial/survey rarely remove such tags.</SPAN></P>
<P DIR=LTR><SPAN LANG="et"></SPAN></P>
<P DIR=LTR><SPAN LANG="et">Though please ignore me if local community has a different preference. </SPAN></P>
<P DIR=LTR><SPAN LANG="et"></SPAN></P>
<P DIR=LTR><SPAN LANG="et">It is also a personal preference that is (I think) well motivated, not OSM rule.</SPAN></P>
<P DIR=LTR><SPAN LANG="et"></SPAN><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?</SPAN><SPAN LANG="et"></SPAN></P>
<P DIR=LTR><SPAN LANG="et">I suspect that reason for that is that it is easier to spot runaway script damaging data?</SPAN></P>
<P DIR=LTR><SPAN LANG="et"></SPAN></P>
<P DIR=LTR><SPAN LANG="et">For technical side: interrupt script after it made N edits, then restart it the next day?</SPAN></P>
<P DIR=LTR><SPAN LANG="et">Or sleep for N seconds after each edit?</SPAN></P>
<P DIR=LTR><SPAN LANG="et"></SPAN></P>
<P DIR=LTR><SPAN LANG="et">When I run bot edit it typically sleeps one minute after every changeset</SPAN></P>
<P DIR=LTR><SPAN LANG="et">(that are grouped into groups of close edits).</SPAN></P>
<P DIR=LTR><SPAN LANG="et"></SPAN></P>
<P DIR=LTR><SPAN LANG="et"></SPAN><SPAN LANG="en-gb">Are there some recommendations on how to improve import documentation?</SPAN><SPAN LANG="et"></SPAN></P>
<P DIR=LTR><SPAN LANG="et"></SPAN><A HREF="https://wiki.openstreetmap.org/wiki/Maa-amet_building_geometry_update"><SPAN LANG="et"><U><FONT COLOR="#0000FF">https://wiki.openstreetmap.org/wiki/Maa-amet_building_geometry_update</FONT></U></SPAN><SPAN LANG="et"></SPAN></A><SPAN LANG="et"> seems OK</SPAN></P>
<P DIR=LTR><SPAN LANG="et"></SPAN></P>
<P DIR=LTR><SPAN LANG="et">Though I think that adding LIDAR based height data should be mentioned in summary</SPAN></P>
<P DIR=LTR><SPAN LANG="et">posted here</SPAN></P>
<P DIR=LTR><SPAN LANG="et"></SPAN><SPAN LANG="en-gb">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.</SPAN><SPAN LANG="et"> </SPAN></P>
<P DIR=LTR><SPAN LANG="et"></SPAN></P>
<P DIR=LTR><SPAN LANG="et"></SPAN><SPAN LANG="en-gb">Should I add line for 2008 import as well?</SPAN><SPAN LANG="et"></SPAN></P>
<P DIR=LTR><SPAN LANG="et">Seems to be a good idea.</SPAN></P>
</BODY>
</HTML>