<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>May 30, 2021, 23:10 by fghj753@hot.ee:<br></div><blockquote class="tutanota_quote" style="border-left: 1px solid #93A3B8; padding-left: 10px; margin-left: 5px;"><div class=""><p class=""><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><br></p></div></blockquote><div dir="auto">I really, really, really dislike such debris on objects. Especially as it is often stale anyway - people<br></div><div dir="auto">updating building shape based on aerial/survey rarely remove such tags.<br></div><div dir="auto"><br></div><div dir="auto">Though please ignore me if local community has a different preference. <br></div><div dir="auto"><br></div><div dir="auto">It is also a personal preference that is (I think) well motivated, not OSM rule.<br></div><blockquote class="tutanota_quote" style="border-left: 1px solid #93A3B8; padding-left: 10px; margin-left: 5px;"><div class=""><p class=""><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><br></p></div></blockquote><div dir="auto">I suspect that reason for that is that it is easier to spot runaway script damaging data?<br></div><div dir="auto"><br></div><div dir="auto">For technical side: interrupt script after it made N edits, then restart it the next day?<br></div><div dir="auto">Or sleep for N seconds after each edit?<br></div><div dir="auto"><br></div><div dir="auto">When I run bot edit it typically sleeps one minute after every changeset<br></div><div dir="auto">(that are grouped into groups of close edits).<br></div><div dir="auto"><br></div><blockquote class="tutanota_quote" style="border-left: 1px solid #93A3B8; padding-left: 10px; margin-left: 5px;"><div class=""><div dir="auto"><span lang="EN-GB"> Are there some recommendations on how to improve import documentation?</span><br></div></div></blockquote><div dir="auto"><a href="https://wiki.openstreetmap.org/wiki/Maa-amet_building_geometry_update">https://wiki.openstreetmap.org/wiki/Maa-amet_building_geometry_update</a> seems OK<br></div><div dir="auto"><br></div><div dir="auto">Though I think that adding LIDAR based height data should be mentioned in summary<br></div><div dir="auto">posted here<br></div><blockquote class="tutanota_quote" style="border-left: 1px solid #93A3B8; padding-left: 10px; margin-left: 5px;"><div class=""><div dir="auto"><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><br></div><div dir="auto"><br></div><div dir="auto"><span lang="EN-GB">Should I add line for 2008 import as well?</span><br></div></div></blockquote><div dir="auto">Seems to be a good idea.<br></div> </body>
</html>