<div dir="auto">As "Frederick Ramm" would say having external IDs is pointless when you can do a spatial join to see what is there and what is not</div><div class="gmail_extra"><br><div class="gmail_quote">On Nov. 5, 2018 3:05 p.m., "John Whelan" <<a href="mailto:jwhelan0112@gmail.com">jwhelan0112@gmail.com</a>> wrote:<br type="attribution"><blockquote class="quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div style="font-family:Verdana;font-size:12pt" bgcolor="#FFFFFF" text="#000000"><div style="font-size:12pt;font-family:Verdana">Something that has come up in the
Netherlands is they did an import then
try to update the buildings once a month. By having some sort of id
tag on the building their feeling is it makes it much easier to pick out
new buildings.<br>
<br>
On the technical side would we have such an id on the building outline
if we should wish to separate out new buildings and import them later.
Currently I don't think we do and someone maybe able to work it out from
the position but is it something we should think about?<div class="quoted-text"><br><br>Cheerio
John<br><br><span>John Marshall wrote on 2018-11-04 6:40 PM:</span><br></div><div class="elided-text"><blockquote type="cite"><div dir="auto">Great idea John<div dir="auto"><br></div><div dir="auto">John</div></div><br><div class="gmail_quote"><div dir="ltr">On Sun, Nov 4, 2018, 16:48 john
whelan <<a href="mailto:jwhelan0112@gmail.com" target="_blank" rel="noreferrer">jwhelan0112@gmail.com</a>
wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="auto">I've
started the process off by an introductory post to the import mailing
list and we are working on a wiki page which will be based on the Stat
Canada City of Ottawa import wiki page.<div dir="auto"><br></div><div dir="auto">Cheerio John</div></div><br><div class="gmail_quote"><div dir="ltr">On Fri, 2 Nov 2018, 7:34 pm James <<a href="mailto:james2432@gmail.com" rel="noreferrer noreferrer" target="_blank">james2432@gmail.com</a> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="auto">if anyone needs a TM or micro
data service, I'm available for this</div><br><div class="gmail_quote"><div dir="ltr">On Fri., Nov. 2, 2018, 7:32 p.m. John Whelan <<a href="mailto:jwhelan0112@gmail.com" rel="noreferrer noreferrer noreferrer" target="_blank">jwhelan0112@gmail.com</a> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="font-family:Verdana;font-size:12pt" bgcolor="#FFFFFF" text="#000000"><div style="font-size:12pt;font-family:Verdana">This approach seems very
sensible however
Pierre has raised the issue of poorly mapped buildings and we are aware
that some were mapped in a mapathon environment so whilst Ottawa used a<font face="Helvetica, Arial, sans-serif"> "leave existing buildings alone"
approach is this an area where some judgement should be used? and yes I
am aware that the official party line is to correct what is there to
retain the history which means taking the "Ottawa" approach is less
controversial but would probably give us more inaccuracies on the map.<br><br>An
alternative might be to import all the buildings with a different tag
than building=yes then leave it to mappers to inspect each before
turning the switch or change the tags to building=yes. Those that
overlap poorly mapped buildings could be left to some sort of clean up
phase.<br><br>Thanks John<br></font><br><span>Matthew Darwin wrote on
2018-11-02 7:07 PM:</span><br><blockquote type="cite"><p><font face="Helvetica, Arial, sans-serif">I think we should
identify who would like to be involved in import for each
municipality. (on a wiki page). On the page, identify
roles, like:</font></p>
<ul>
<li><font face="Helvetica, Arial, sans-serif">coordinator</font></li>
<li><font face="Helvetica, Arial, sans-serif">import data
preparation</font></li>
<li><font face="Helvetica, Arial, sans-serif">QA</font></li>
<li><font face="Helvetica, Arial, sans-serif">import execution<br>
</font></li>
<li><font face="Helvetica, Arial, sans-serif">data enrichment
(commercial, residential, etc... tagging)<br>
</font></li>
<li><font face="Helvetica, Arial, sans-serif">etc..<br>
</font></li>
</ul>
<p><font face="Helvetica, Arial, sans-serif">Then we can see where
we have gaps and how to fill them. Perhaps some municipalities
have local mappers who will be happy to do the tagging of
building type (and can do some validation if the buildings look
right), but no technical capability to execute the actual
import. And maybe some folks who did imports before will help
areas where we have no technical expertise.<br>
</font></p>
<p><font face="Helvetica, Arial, sans-serif"><br>
</font></p>
<div class="m_2890630142525739317m_-6384074295555930325m_-2780880843006209261m_-6586725405408947374moz-cite-prefix">On
2018-11-02 6:58 p.m., John Whelan
wrote:<br>
</div>
<blockquote type="cite">
<div style="font-size:12pt;font-family:Verdana"><br>
<br>
So to paraphrase your reply. A centralised import plan in the
wiki which says the data is approved for import and should be
tackled in chunks of some sort of region since we are a
decentralized organization. Which I think is similar to the way
Task Manager works. The project is broken into tiles and each
tile is tackled completed separately. The 'Tiles' would of
course be somewhat larger in area and there is a technical
limitation as to how big an area can be downloaded from the OSM
server.<br>
<br>
The local mappers certainly have a role to play and because the
goal is not only to import the buildings but to enrich the tags
with commercial etc so the tag enrichment would be a task that a
mapathon could tackle. I personally don't think a new mapper
using iD in a mapathon has a role to play in importing the
building outlines into OSM.<br>
<br>
The plan should include the technical steps to import the data.<br>
<br>
Thanks<br>
<br>
Cheerio John<br>
<br>
<span>Pierre Béland wrote on 2018-11-02 6:35 PM:</span><br>
<blockquote type="cite"><div>Pour le
Québec, je retrouve les données de plusieurs
municipalités</div>
<div>Montréal, Longueuil, Repentigny, Shawinigan, Québec et
Rimouski.</div>
<div><br>
</div>
<div>Première observation rapide, aussi, elles sont de bonne
qualité et proviennent je suppose des cadastres des
municipalités. En milieu urbain, cela facilite beaucoup
l'identification des immeubles juxtaposés.</div>
<div><br>
</div>
<div>Je vois ailleurs, aux États-Unis notamment avec les
données de Microsoft, que les projets sont par région ou
municipalité. <br>
</div>
<div><br>
</div>
<div>Je pense qu'il faut éviter un projet trop centralisé tant
pour assurer un meilleur contrôle du déroulement dans chaque
municipalité, région que pour permettre aux communautés des
provinces et communautés locales de s'impliquer. <br>
</div>
<div><br>
</div>
<div>La rédaction d' une page wiki pour l'ensemble du Canada
peut répondre aux exigences du groupe Import de OSM. Mais
l'organisation doit être décentralisée.</div>
<div><br>
</div>
<div><span>Le rôle de cette liste doit être un forum pour
supporter les communautés des provinces et communautés
locales. C'est une occasion de dynamiser ces communautés
avec un projet très intéressant. De là, ils auront le goût
de compléter la carte pour y décrire les infrastructures
locales. <br>
</span></div>
<div><span><br>
</span></div>
<div><span>Si trop de tâches sont initiées en parallèle sur un
gestionnaire de tâches, il sera très difficile de
coordonner, assurer le suivi, une progression coordonnée.
Il faut éviter que des mapathons ou organisations externes
s'invitent pour collaborer à de telles tâches avec les
milliers et milliers de personnes qui viennent jardiner
quelques heures sans organisation / formation réelle et
laissent ensuite le tout sans dessus, dessous.</span></div></blockquote>
<br>
<div class="m_2890630142525739317m_-6384074295555930325m_-2780880843006209261m_-6586725405408947374moz-signature">--
<br>
<div>Sent from <a href="https://www.postbox-inc.com/?utm_source=email&utm_medium=siglink&utm_campaign=reach" rel="noreferrer noreferrer noreferrer noreferrer" target="_blank"><span style="color:rgb(0,157,247)">Postbox</span></a></div>
</div>
</div>
<br>
<fieldset class="m_2890630142525739317m_-6384074295555930325m_-2780880843006209261m_-6586725405408947374mimeAttachmentHeader"></fieldset>
<pre class="m_2890630142525739317m_-6384074295555930325m_-2780880843006209261m_-6586725405408947374moz-quote-pre">_______________________________________________
Talk-ca mailing list
<a class="m_2890630142525739317m_-6384074295555930325m_-2780880843006209261m_-6586725405408947374moz-txt-link-abbreviated" href="mailto:Talk-ca@openstreetmap.org" rel="noreferrer noreferrer noreferrer noreferrer" target="_blank">Talk-ca@openstreetmap.org</a>
<a class="m_2890630142525739317m_-6384074295555930325m_-2780880843006209261m_-6586725405408947374moz-txt-link-freetext" href="https://lists.openstreetmap.org/listinfo/talk-ca" rel="noreferrer noreferrer noreferrer noreferrer" target="_blank">https://lists.openstreetmap.org/listinfo/talk-ca</a>
</pre></blockquote>
<br><fieldset class="m_2890630142525739317m_-6384074295555930325m_-2780880843006209261m_-6586725405408947374mimeAttachmentHeader"></fieldset><br><pre>_______________________________________________
Talk-ca mailing list
<a class="m_2890630142525739317m_-6384074295555930325m_-2780880843006209261m_-6586725405408947374moz-txt-link-abbreviated" href="mailto:Talk-ca@openstreetmap.org" rel="noreferrer noreferrer noreferrer noreferrer" target="_blank">Talk-ca@openstreetmap.org</a>
<a class="m_2890630142525739317m_-6384074295555930325m_-2780880843006209261m_-6586725405408947374moz-txt-link-freetext" href="https://lists.openstreetmap.org/listinfo/talk-ca" rel="noreferrer noreferrer noreferrer noreferrer" target="_blank">https://lists.openstreetmap.org/listinfo/talk-ca</a>
</pre></blockquote><br><div class="m_2890630142525739317m_-6384074295555930325m_-2780880843006209261m_-6586725405408947374moz-signature">--
<br>
<div>Sent from <a href="https://www.postbox-inc.com/?utm_source=email&utm_medium=siglink&utm_campaign=reach" rel="noreferrer noreferrer noreferrer noreferrer" target="_blank"><span style="color:rgb(0,157,247)">Postbox</span></a></div></div></div></div>
_______________________________________________<br>
Talk-ca mailing list<br>
<a href="mailto:Talk-ca@openstreetmap.org" rel="noreferrer noreferrer
noreferrer noreferrer" target="_blank">Talk-ca@openstreetmap.org</a><br>
<a href="https://lists.openstreetmap.org/listinfo/talk-ca" rel="noreferrer noreferrer noreferrer noreferrer noreferrer" target="_blank">https://lists.openstreetmap.org/listinfo/talk-ca</a><br></blockquote></div></blockquote></div>
_______________________________________________<br>
Talk-ca mailing list<br>
<a href="mailto:Talk-ca@openstreetmap.org" rel="noreferrer noreferrer" target="_blank">Talk-ca@openstreetmap.org</a><br>
<a href="https://lists.openstreetmap.org/listinfo/talk-ca" rel="noreferrer noreferrer noreferrer" target="_blank">https://lists.openstreetmap.org/listinfo/talk-ca</a><br></blockquote></div>
</blockquote><br><div class="m_2890630142525739317moz-signature">-- <br>
<div>Sent from <a href="https://www.postbox-inc.com/?utm_source=email&utm_medium=siglink&utm_campaign=reach" target="_blank" rel="noreferrer"><span style="color:rgb(0,157,247)">Postbox</span></a></div></div></div></div></div><div class="elided-text">
_______________________________________________<br>
Talk-ca mailing list<br>
<a href="mailto:Talk-ca@openstreetmap.org" target="_blank" rel="noreferrer">Talk-ca@openstreetmap.org</a><br>
<a href="https://lists.openstreetmap.org/listinfo/talk-ca" rel="noreferrer noreferrer" target="_blank">https://lists.openstreetmap.org/listinfo/talk-ca</a><br>
</div></blockquote></div><br></div>