<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=utf-8">
<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;
margin-bottom:.0001pt;
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;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
span.EmailStyle22
{mso-style-type:personal-compose;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@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:342173204;
mso-list-type:hybrid;
mso-list-template-ids:-1038335142 -1322482752 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;
text-indent:-18.0pt;
font-family:"Calibri",sans-serif;
mso-fareast-font-family:Calibri;}
@list l0:level2
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:"Courier New";}
@list l0:level3
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:Wingdings;}
@list l0:level4
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
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;
text-indent:-18.0pt;
font-family:"Courier New";}
@list l0:level6
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:Wingdings;}
@list l0:level7
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
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;
text-indent:-18.0pt;
font-family:"Courier New";}
@list l0:level9
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:Wingdings;}
ol
{margin-bottom:0cm;}
ul
{margin-bottom:0cm;}
--></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="EN-GB" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span style="mso-fareast-language:EN-US">Hi Matheusz, Jo and all,
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US">The import will certainly not be an automatic dump. But it will not be done through the Tasking Manager, but by just coordinated between myself and some other experienced mappers from the Missing
Maps community directly through JOSM. But indeed by splitting up the data in chunks of 500 buildings we are able to check the data in detail before uploading it. The todo plugin is indeed a good suggestion.
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US">Further I am a bit confused, if we would have been able to digitize the data from the imagery we would have done so. We have done this already in the places surrounding the data we have available
here for the Lopa & Lingo area. See here: </span><a href="https://www.openstreetmap.org/way/820347035#map=14/1.7331/30.4503">https://www.openstreetmap.org/way/820347035#map=14/1.7331/30.4503</a> However now we have this good quality dataset that is created
on imagery of January 2020, which is several years more recent than we have available for usage on OpenStreetMap and we would not be able to use that on OpenStreetMap because we cannot verify this data with imagery on OpenStreetMap? <o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">So trying to convince you again why in my opinion it is a good quality dataset:
<o:p></o:p></p>
<ul style="margin-top:0cm" type="disc">
<li class="MsoListParagraph" style="margin-left:0cm;mso-list:l0 level1 lfo1">We have been working with Salzburg university for years and they have delivered good quality work for years to support our activities. Check some of their work here:
<a href="https://zgis.at/">https://zgis.at/</a><o:p></o:p></li><li class="MsoListParagraph" style="margin-left:0cm;mso-list:l0 level1 lfo1">The methodology Z gis has used is semi-automatic. This means that all automatic extracted buildings were validated by visual interpretation and buildings have been added manually to
the dataset where needed.<o:p></o:p></li><li class="MsoListParagraph" style="margin-left:0cm;mso-list:l0 level1 lfo1">Many of the buildings of the dataset do overlap exactly with buildings on the older imagery that we have available for usage on OpenStreetMap, and with the already existing buildings
onto OpenStreetMap. <o:p></o:p></li><li class="MsoListParagraph" style="margin-left:0cm;mso-list:l0 level1 lfo1">There is a very low risk in features ‘not representing anything real’. The exact geometry is mostly not that important for the usage of the data for us – this in contrary to the indication
of the existance of the building and the material it is made off. <o:p></o:p></li></ul>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">So yes, there might be a slight issue with the geometries of a small number of buildings, but this is thus because of written reasons in my opinion something we can fix by the manual treatment of the data.
<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">So what do others think? <o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Would the situation change if myself and the few volunteers working on uploading the data could have access to the initial imagery? I think that might be maybe possible… Of course if there are experienced mappers here who would like to
help out with the import, please let me know, you’re always welcome to join the effort!
<o:p></o:p></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US">Btw, thanks to challenge me. I hope we can come to a good solution here together?
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US">Thanks, <o:p></o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US">Jorieke<o:p></o:p></span></p>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-size:9.0pt;color:#A6A6A6"><br>
<br>
</span><span style="font-size:10.0pt;color:#A6A6A6"><o:p></o:p></span></p>
</div>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal"><b><span lang="EN-US">From:</span></b><span lang="EN-US"> Mateusz Konieczny via Imports <imports@openstreetmap.org>
<br>
<b>Sent:</b> 21 July 2020 13:04<br>
<b>Cc:</b> imports@openstreetmap.org<br>
<b>Subject:</b> Re: [Imports] Import building footprints Lopa & Lingo<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal">As I understand, the plan is to load the buildings in manageable sets from the tasking manager,<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">and person doing verification will skip solely clearly bizarre geometries and assume that everything<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">else is correct.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">I think that given presence of nonsense geometries means that seemingly OK ones cannot<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">be assumed to be valid ones, and only verified ones should be imported.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Jul 21, 2020, 11:53 by <a href="mailto:winfixit@gmail.com">winfixit@gmail.com</a>:<o:p></o:p></p>
</div>
<blockquote style="border:none;border-left:solid #93A3B8 1.0pt;padding:0cm 0cm 0cm 8.0pt;margin-left:3.75pt;margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<div>
<p class="MsoNormal">I get the impression Mateusz thinks the import will consist of an automatic dump of the data, whereas the actual plan is to load the buildings in manageable sets from the tasking manager and then a person does the verification, maybe by
using the todo plugin in JOSM?<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Polyglot<o:p></o:p></p>
</div>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<div>
<p class="MsoNormal">On Tue, Jul 21, 2020 at 10:25 AM Jorieke Vyncke <<a href="mailto:jorieke.vyncke@london.msf.org" target="_blank">jorieke.vyncke@london.msf.org</a>> wrote:<o:p></o:p></p>
</div>
<blockquote style="border:none;border-left:solid #CCCCCC 1.0pt;padding:0cm 0cm 0cm 6.0pt;margin-left:4.8pt;margin-right:0cm">
<div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">Hi Mateusz,
<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">Thanks for your feedback!
<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">There are really not that many of this type of buildings in the dataset, most of the buildings are nicely squared or circulized. By the manual verification of the data, we’ll of
course compare and adapt the building data with the latest imagery that we have available on OpenStreetMap – the Maxar Premium Imagery. We’ll correct with help of that imagery and of course in all cases nicely square corners of the weird shapes. There will
really not be a ‘soul-crushing cleanup’ needed after this import. <o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">Would you rather propose to leave these buildings out? We could do that as well, but I would prefer not to, since this means we will have an incomplete dataset in the area. I’d
rather choose for correcting the shapes with help of available imagery. <o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">Best wishes,
<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">Jorieke<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <o:p></o:p></p>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><o:p> </o:p></p>
</div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <o:p></o:p></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><b><span lang="EN-US">From:</span></b><span lang="EN-US"> Mateusz Konieczny via Imports <<a href="mailto:imports@openstreetmap.org" target="_blank">imports@openstreetmap.org</a>>
<br>
<b>Sent:</b> 20 July 2020 18:20<br>
<b>Cc:</b> '<a href="mailto:imports@openstreetmap.org" target="_blank">imports@openstreetmap.org</a>' <<a href="mailto:imports@openstreetmap.org" target="_blank">imports@openstreetmap.org</a>><br>
<b>Subject:</b> Re: [Imports] Import building footprints Lopa & Lingo</span><o:p></o:p></p>
</div>
</div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <o:p></o:p></p>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">Jul 20, 2020, 18:18 by
<a href="mailto:jorieke.vyncke@london.msf.org" target="_blank">jorieke.vyncke@london.msf.org</a>:<o:p></o:p></p>
</div>
<blockquote style="border:none;border-left:solid #93A3B8 1.0pt;padding:0cm 0cm 0cm 8.0pt;margin-left:3.75pt;margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">Q: Some buildings have strange trapezoidal shapes, how are you planning to correct them without accessing the imagery?<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">There are not that many of these. Since we are not able to check back with the original imagery, we’ll have to trust the dataset we want to import for this and will upload the data.
Of course by looking at the data manually we would be able to spot areas with real issues with this and then we can still decide to not upload that data.
<o:p></o:p></p>
</div>
</blockquote>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">So clearly suspicious shapes such as this trapeizodal ones will be skipped and<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">everything else without blatant mistakes will be imported without verification?<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">That seems to be a bad idea and I am opposed to such import. It will just burden<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">any community of mappers that may appear with soul-crushing cleanup.<o:p></o:p></p>
</div>
</div>
</div>
<div>
<p class="MsoNormal">_______________________________________________<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">Imports mailing list<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><a href="mailto:Imports@openstreetmap.org" target="_blank">Imports@openstreetmap.org</a><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><a href="https://lists.openstreetmap.org/listinfo/imports" target="_blank">https://lists.openstreetmap.org/listinfo/imports</a><o:p></o:p></p>
</div>
</blockquote>
</div>
</blockquote>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</div>
</body>
</html>