<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">2015-02-10 22:00 GMT+01:00 Michael Schnuerle <span dir="ltr"><<a href="mailto:mschnuerle@codeforamerica.org" target="_blank">mschnuerle@codeforamerica.org</a>></span>:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br><div bgcolor="#FFFFFF" text="#333333">
<div>Our plan is to follow in the footsteps
of the NOLA building/address import, which is currently in Task
Manager. <br>
<a href="http://tasks.openstreetmap.us/job/41" target="_blank">http://tasks.openstreetmap.us/job/41</a><br>
How/when can we get a similar task setup in Task Manager?<br></div></div></blockquote><div><br></div><div>That's operated by the OSM US Community, so you should ask them. <br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div bgcolor="#FFFFFF" text="#333333"><div>
<br>
We will use their same exact process, and in fact I did a ward in
the NOLA task to test out how it would work, which was awesome!<br>
<a href="http://wiki.openstreetmap.org/wiki/New_Orleans,_Louisiana/Building_Outlines_Import/Contributor_Guide" target="_blank">http://wiki.openstreetmap.org/wiki/New_Orleans,_Louisiana/Building_Outlines_Import/Contributor_Guide</a><br>
<br></div></div></blockquote><div>Looks like a very good process indeed.<br></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div bgcolor="#FFFFFF" text="#333333"><div>
Currently we are working with the city gov to get into and will
conflate the buildings and address data together, similar to this:<br>
<a href="https://github.com/mtoupsUNO/nola-buildings" target="_blank">https://github.com/mtoupsUNO/nola-buildings</a><br>
We'll put our final code on Github too.<br>
<br>
Since we'll be importing it in small chunks manually with JOSM,
then verifying the data by hand, hopefully we can catch most of
the error that may exist.<br></div></div></blockquote><div><br></div><div>Be sure to test this phase. When an import is too easy (completely automated in JOSM), any errors will be overlooked, when it's too hard, it will be as slow as regular mapping. Finding a good balance is important.<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div bgcolor="#FFFFFF" text="#333333"><div>
<br>
We have checked some of the areas qualitatively that we know that
have existing OSM data. Areas of the Downtown, Highlands and
Jtown. No one has found any issues yet. And while we won't be
overwriting any OSM building footprints from users, it does appear
that the city data is better in every case we can see (likely due
to access to higher-res satellite photography).<br>
<a href="http://wiki.openstreetmap.org/wiki/Louisville,_Kentucky/Building_Outlines_Import/OSMvsGISOverlapExamples" target="_blank">http://wiki.openstreetmap.org/wiki/Louisville,_Kentucky/Building_Outlines_Import/OSMvsGISOverlapExamples</a><br></div></div></blockquote><div><br></div><div>I don't think anyone is opposed to improving the existing building by using the better precision data (do make sure you copy all tags over, and preferably also the history). It's normal that governments with expensive equipment have better precision data than amateur mappers.<br><br></div><div>However, I am concerned about logical mistakes. In my region, I've seen a number of spelling mistakes in street names, and also some abbreviations. Next to that, there are the problems based on outdated data, like newly build, demolished, or changed buildings. When OSM already has building data on a certain spot, and it looks totally different from the governmental data, you should watch out. Similar when people tagged areas or roads under construction. <br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div bgcolor="#FFFFFF" text="#333333"><div>
<br>
For updatability, we will be adding a unique ID that comes from
the source data and will remain the same in updates. But really
any other updated data will be imported using this same method:
creating a Task and dividing it out into chunks to manually
compare and validate using our local volunteers.<br>
<br>
I hope we are on the right path with all this. Any more questions
or advice is welcome and thanks for everything so far! We hope to
have the data ready and Task Manager setup by early next week.<span class=""><br>
<div><br>
<div style="font-size:11px;color:#111;border-collapse:collapse;font-family:Verdana,Arial">
<b>Michael Schnuerle</b> | Code for America Louisville Brigade
Captain<br>
<i>e</i> <a href="http://mschnuerle@codeforamerica.org" style="color:#111;text-decoration:none" target="_blank">mschnuerle@codeforamerica.org</a>
| <a href="http://www.twitter.com/CivicDataAlly" style="color:#111;text-decoration:none" target="_blank">@CivicDataAlly</a>
<br>
<br>
<a href="http://www.civicdataalliance.org/" style="color:#0d5899" target="_blank">CivicDataAlliance.org</a> | <a href="http://data.civicdataalliance.org" style="color:#111" target="_blank">Open
Data Portal</a> </div>
<br></div></span><span class=""></span><br></div></div></blockquote><div><br></div><div>It certainly looks a lot clearer now, thanks for the explanation. <br><br></div><div>Regards,<br>Sander<br></div></div></div></div>