<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#333333">
<div class="moz-cite-prefix">Our plan is to follow in the footsteps
of the NOLA building/address import, which is currently in Task
Manager. <br>
<a class="moz-txt-link-freetext" href="http://tasks.openstreetmap.us/job/41">http://tasks.openstreetmap.us/job/41</a><br>
How/when can we get a similar task setup in Task Manager?<br>
<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 class="moz-txt-link-freetext" href="http://wiki.openstreetmap.org/wiki/New_Orleans,_Louisiana/Building_Outlines_Import/Contributor_Guide">http://wiki.openstreetmap.org/wiki/New_Orleans,_Louisiana/Building_Outlines_Import/Contributor_Guide</a><br>
<br>
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 class="moz-txt-link-freetext" href="https://github.com/mtoupsUNO/nola-buildings">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>
<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 class="moz-txt-link-freetext" href="http://wiki.openstreetmap.org/wiki/Louisville,_Kentucky/Building_Outlines_Import/OSMvsGISOverlapExamples">http://wiki.openstreetmap.org/wiki/Louisville,_Kentucky/Building_Outlines_Import/OSMvsGISOverlapExamples</a><br>
<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.<br>
<div class="moz-signature"><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="mschnuerle@codeforamerica.org"
style="color: #111; text-decoration: none;">mschnuerle@codeforamerica.org</a>
| <a href="http://www.twitter.com/CivicDataAlly"
style="color: #111; text-decoration: none;">@CivicDataAlly</a>
<br>
<br>
<a href="http://www.civicdataalliance.org/" style="color:
#0d5899">CivicDataAlliance.org</a> | <a
href="http://data.civicdataalliance.org" style="color: #111">Open
Data Portal</a> </div>
<br>
</div>
On 1/31/15 9:46 AM, Sander Deryckere wrote:<br>
</div>
<blockquote
cite="mid:CABUOUO9idj6kxCa85XbDQLUMJAUtd7B=K1=7PwpnGEgfv=g05Q@mail.gmail.com"
type="cite">
<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>
</blockquote>
On 1/28/15 4:36 PM, Clifford Snow wrote:<br>
> Are you going to conflate the addresses with the buildings
ahead of time? I usually take the following approach:<br>
> o If one address inside a building outline, conflate the
address to the building outline<br>
> o Multiple addresses inside individual buildings are kept as
individual nodes. One city I'm working on now actually include unit
numbers and main building number. In this case the main address is
conflated with the building outline and the units are kept as nodes<br>
> o everything else is kept as delivered.<br>
> Sounds like a good project. Good luck,<br>
> Clifford<br>
<br>
<br>
<blockquote
cite="mid:CABUOUO9idj6kxCa85XbDQLUMJAUtd7B=K1=7PwpnGEgfv=g05Q@mail.gmail.com"
type="cite">
<div class="gmail_extra">
<div class="gmail_quote">2015-01-28 20:55 GMT+01:00 Michael
Schnuerle <span dir="ltr"><<a moz-do-not-send="true"
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 moz-do-not-send="true"
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 moz-do-not-send="true"
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 moz-do-not-send="true"
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 moz-do-not-send="true"
href="http://mschnuerle@codeforamerica.org"
style="color:#111;text-decoration:none"
target="_blank">mschnuerle@codeforamerica.org</a>
| <a moz-do-not-send="true"
href="http://www.twitter.com/CivicDataAlly"
style="color:#111;text-decoration:none"
target="_blank">@CivicDataAlly</a> <br>
<br>
<a moz-do-not-send="true"
href="http://www.civicdataalliance.org/"
style="color:#0d5899" target="_blank">CivicDataAlliance.org</a>
| <a moz-do-not-send="true"
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 moz-do-not-send="true"
href="mailto:Imports@openstreetmap.org">Imports@openstreetmap.org</a><br>
<a moz-do-not-send="true"
href="https://lists.openstreetmap.org/listinfo/imports"
target="_blank">https://lists.openstreetmap.org/listinfo/imports</a><br>
<br>
</blockquote>
</div>
<br>
</div>
</blockquote>
<br>
</body>
</html>