<div dir="ltr"><div><div><div><div><div><div>Hi,<br></div><div><br>I think a more elaborate documentation is needed before it can actually be judged.<br></div><div><br></div>The workflow is unknown. What tools will you use to split up the task, what tools will you use to detect conflicts, how will you handle conflicts (f.e. the same address on a different position when you compare OSM with city data)...<br><br></div>Next to that, you also need to do some research about data quality. The building outline precision is hard to check with amateur hardware, thus only a quick check is useful there. However, address databases may contain many different logical mistakes. In our Flemish dataset, I've encountered housenumbers being assigned to the wrong street (sometimes a neighbouring street, sometimes a street with a similar name), numbers where no building exists, new houses that were not yet numbered, spelling mistakes in streetnames, overlapping housenumbers that should go on different houses... You should do qualitative research on an area you know, or that's well mapped in OSM already. Quantitative research is hard here, because there's no data to compare it too.<br><br></div>As a final note, you must also think about updatability. Once the data is in, people will build on it, and you can't just swipe it out and replace with a newer dataset once that's released. So if you import a 2012 dataset now, what will you do when the next dataset comes out? You say that the housenumbers are updated daily, but how will you handle that? As imports require a smaller community than normal mapping, updatability is quite important when doing an import, since there's about nobody left to do the job.<br><br></div>Updatability can be achieved by adding an id to the imported objects (that id must be permanent in the source DB), but it's also possible without id when you develop algorithms to compare OSM data with the official data.<br><br></div>Thanks for working on this,<br></div>Sander<br></div><div class="gmail_extra"><br><div class="gmail_quote">2015-01-28 20:55 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">
<div bgcolor="#FFFFFF" text="#333333">
<font size="-1"><font face="Verdana">Hi all,<br>
<br>
</font></font><font size="-1"><font face="Verdana"><font size="-1"><font face="Verdana">Louisville KY's Code for America brigade has
volunteered to help the </font></font><font size="-1"><font face="Verdana"><font size="-1"><font face="Verdana">American
Printing House for the Blind </font></font> work with
the OSM community to import the building footprint and
address data properly.</font></font><br>
<br>
</font></font><font size="-1"><font face="Verdana">I'm
coordinating the effort and wanted to reach out to this list,
per the Import Guildelines. I've created some OSM Wiki pages as
a start to compile all the info publicly.<br>
<br>
Main Import page:<br>
<a href="https://wiki.openstreetmap.org/wiki/Louisville,_Kentucky/Building_Outlines_Import" target="_blank">https://wiki.openstreetmap.org/wiki/Louisville,_Kentucky/Building_Outlines_Import</a><br>
<br>
Added to this list: <br>
<a href="https://wiki.openstreetmap.org/wiki/Import/Catalogue" target="_blank">https://wiki.openstreetmap.org/wiki/Import/Catalogue</a><br>
<br>
We've got a number of members who have made some OSM edits over
the last few years. We are reaching out to more active local
OSM editors too. If there is anyone on this list who is an
active editor locally we'd love to have your support and help!<br>
<br>
You can read more about the project here on our forum:<br>
<a href="http://www.civicdataalliance.org/forum/?place=msg%2Fcivicdataalliance%2FJDkgh-uc2so%2FFoQZuypzZZEJ" target="_blank">http://www.civicdataalliance.org/forum/?place=msg%2Fcivicdataalliance%2FJDkgh-uc2so%2FFoQZuypzZZEJ</a><br>
<br>
I'd like to ask for help with making sure we do everything
correctly, and next steps. We want to follow in the footsteps
of NYC, LA, Chicago and NOLA who have all recently done
something similar.<br>
<br>
We have a technically competent team of volunteers (programmers,
mappers, GIS, coders), and our short term goal is to get things
setup for a hackathon we are hosting Feb 21 called CodeAcross.
At CodeAcross we'll have a day to really get people focused on
loading the data in chunks into OSM.<br>
<br>
I'm also sending this to the imports-us@ list. If I should
focus my communications there just let me know.<br>
<br>
Thanks,</font></font><span class="HOEnZb"><font color="#888888"><br>
<br>
<div>-- <br>
<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>
</font></span></div>
<br>_______________________________________________<br>
Imports mailing list<br>
<a href="mailto:Imports@openstreetmap.org">Imports@openstreetmap.org</a><br>
<a href="https://lists.openstreetmap.org/listinfo/imports" target="_blank">https://lists.openstreetmap.org/listinfo/imports</a><br>
<br></blockquote></div><br></div>