[Imports] Importing official Buildings/Addresses in Louisville KY

[Sander Deryckere]

2015-02-10 22:00 GMT+01:00 Michael Schnuerle <mschnuerle at codeforamerica.org>
:

>
> Our plan is to follow in the footsteps of the NOLA building/address
> import, which is currently in Task Manager.
> http://tasks.openstreetmap.us/job/41
> How/when can we get a similar task setup in Task Manager?
>

That's operated by the OSM US Community, so you should ask them.

>
> 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!
>
> http://wiki.openstreetmap.org/wiki/New_Orleans,_Louisiana/Building_Outlines_Import/Contributor_Guide
>
> Looks like a very good process indeed.


> Currently we are working with the city gov to get into and will conflate
> the buildings and address data together, similar to this:
> https://github.com/mtoupsUNO/nola-buildings
> We'll put our final code on Github too.
>
> 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.
>

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.

>
> 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).
>
> http://wiki.openstreetmap.org/wiki/Louisville,_Kentucky/Building_Outlines_Import/OSMvsGISOverlapExamples
>

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.

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.

>
> 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.
>
> 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.
>
>  *Michael Schnuerle* | Code for America Louisville Brigade Captain
> *e* mschnuerle at codeforamerica.org | @CivicDataAlly
> <http://www.twitter.com/CivicDataAlly>
>
> CivicDataAlliance.org <http://www.civicdataalliance.org/> | Open Data
> Portal <http://data.civicdataalliance.org>
>
>
>
It certainly looks a lot clearer now, thanks for the explanation.

Regards,
Sander
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/imports/attachments/20150212/3673966c/attachment-0001.html>