copy Lousiville's wiki page to lexington's
New page
'''This needs to be updated to reflect Lexington's progress'''
==Work In Progress==
{| width=100%
| style="font-size:18px; line-height:25px" | '''Data import is COMPLETE!''' Track our import progress here and help out at task tracker (link offline now): http://tasks.openstreetmap.us/job/50
|}
'''Note that Task Manager US had a massive server failure and all data for all projects was lost.''' Version 2 is now live, but with no data.
We have created a detailed discussion on the OSM mailing lists ([https://lists.openstreetmap.org/listinfo/imports-us imports-us@] and [https://lists.openstreetmap.org/listinfo/imports imports@]) in January and February of 2015. The lists seem to agree on our direction and process, following in the footsteps of NOLA's work.
This process will be in accordance with OSM's [[Import/Guidelines|Import Guidelines]].
==How to get involved==
{| width=100%
| style="font-size:18px; line-height:25px" | Everything that mappers need to know to get involved should be found in our live [[Louisville,_Kentucky/Building_Outlines_Import/Contributor_Guide|Contributor Guide]].
|}
'''Read about our recap and progress on [http://www.civicdataalliance.org/gis-open-data-american-printing-house-open-street-map/ our website]!'''
Everything else found below on this page is background/technical information on the import which was prepared while this project was under consideration. It is not necessary to read on unless you want to learn more about how this project began.
==Historic Overview==
Louisville's [http://www.aph.org/ American Printing House for the Blind] is an international institution. Using open data, they have created an app that helps blind and visually impaired people navigate cities safely!
APH uses Open Street Map (OSM) standardized layer data to import into their app. They load data into OSM from open data portals that have an open data license. The app uses audio to announce important locations as visually impaired people walk around.
Right now they either don't have, or have to pay for, good data about buildings, street addresses, parcels, sewer drains, manholes, power poles, parking meters, and street crossings.
The app is called [https://play.google.com/store/apps/details?id=org.aph.avigenie Nearby Explorer] and is a $99 Andoid App.
With the data they can 1) improve walking and driving safety of visually impaired people, 2) possibly charge less for the app, 3) serve as a model for other US city's open data, thereby increasing their coverage area.
The CDA has volunteered to help APH work with OSM to import the data properly, a process that is both technical and bureaucratic (mass data imports need much coordination with the OSM community). We also want to host Code for America's national [http://www.codeforamerica.org/events/codeacross-2015/ Code Across] hackathon February 20-22 at the APH facilities and make it the focus of [http://www.meetup.com/Louisville-Civic-Data-Alliance/events/219829803/ Louisville's Code Across] event.
Additionally, if successful, APH employees are happy to speak this summer at the national Code for America Summit and share this great open data success for APH, Louisville, and the CDA!
[http://www.civicdataalliance.org/forum/?place=msg%2Fcivicdataalliance%2FJDkgh-uc2so%2FFoQZuypzZZEJ More Details]
==About the data==
The [https://data.louisvilleky.gov City of Louisville Metro] provides us with a public domain shapefile with high-quality [http://portal.louisvilleky.gov/dataset/buildings-data building outlines] (412,375 buildings, based on imagery updated in 2012, due for an update in 2015) and a shapefile of [ftp://ftp.lojic.org/pub/federal/ addresses] (398,982 points, commercial and residential, updated daily, through January 2015).
===License===
According to the [http://portal.louisvilleky.gov/content/terms-use-accessibility-data-policy Data Policy page] on data.louisvilleky.gov, the data is licensed free and without restriction. (Public domain)
''"Data available through Louisville’s Open Data Portal is offered free and without restriction."''
===Data to Import===
====Building Outlines====
* Source Data: http://portal.louisvilleky.gov/dataset/buildings-data
[[File:LouisvilleKYExistingVSNewBuildings.png|300px]]
412,375 official buildings vs 5,800 existing OSM user contributions (<1.5%).
====Street Addresses====
* Source Data: ftp://ftp.lojic.org/pub/federal/
[[File:LouisvilleKYAddressesInOSM.png|300px]]
Bright green = address mapped. Bright red = no address mapped. Everything else has no address in OSM. See http://qa.poole.ch/ for details.
398,982 official address point data vs almost no existing data.
====Buildings Plus Addresses====
Our solution might be to load buildings with address data associated with it already, where possible.
[[File:LouisvilleKYAddressAndBuildingSample.png|300px]]
Sample of address data overlayed on building data. Note that addresses are centered over the center of the building footprint, if there is a building. Then they are centered on the parcel (parcels not shown in this image). In the case of condos, they are stacked and slightly offset.
[[Louisville,_Kentucky/Building_Outlines_Import/OSMvsGISOverlapExamples|OSM vs GIS Overlap Examples]]
===Data Analysis===
Qualitative analysis manually comparing existing OSM data to city data in neighborhoods (Jtown, Highlands, Downtown) well known by contributers shows that the address and building data is of high quality. We will still be examining things closely during the import but we are confident that this will be a useful addition to the OSM community.
===Tagging===
* building = yes
If building only contains one address, the following will be added to the area.
* addr:housenumber = HOUSE_NUMB
* addr:street = DIR (expanded: N->North) + STREET + TYPE (expanded: ST->Street)
* addr:state = KY or IN, since both are in the coverage area
* addr:city = Louisville has 50 or so smaller 2nd-6th class independent cities within the county, so these will be added.
* addr:postcode = 5 digit post code
In the case with multiple addresses in different locations within the same building footprint, these tags will go on separate nodes with unit numbers:
* addr:unit = for individual address points, all placed withing building footprints. Eg, 1, 201, C.
Every building also has a special unique identifier:
* lojic:bgnum = Numerical ID, eg, 246958.
This is used to later add height data to buildings when we get that sorted, to allow the supporting data organization (LOJIC) grab citizen OSM edits an import changes into their system, and also help with future updates.
===Reconciliation with existing buildings in OSM===
There are not a lot of buildings already in OSM for Louisville, KY. As of January 2014 there are less than 5,800, which is about 1.5% of the total. Where there is overlap, we will preserver the OSM edits, unless the city data is obviously better on a case by case basis.
===Conflation with existing addresses in OSM===
398,982 official address point data vs almost no existing data in OSM. We will manually compare any overlap and choose the best address locations based on our conflation with the building data and local knowledge.
==Participants==
* [[User:Yourmapper|Michael Schnuerle]]: Project lead. longtime local mapper and resident. Co-captain of [http://www.civicdataalliance.org/ Louisville's Code for America Brigade].
* [https://www.openstreetmap.org/user/APHTECH American Printing House for the Blind]: APH tech team helping with data load. APH is the reason we want to do this project!
* [https://www.openstreetmap.org/user/CivicData Civic Data Alliance]: OSM account for Civic Data Alliance (CDA)
* [https://www.openstreetmap.org/user/Jeff%20McAdams Jeff McAdams]: Active local OSM editor
* [https://www.openstreetmap.org/user/metromapper Metro Mapper]: Local mapping website and OSM editor
* [https://www.openstreetmap.org/user/CityCollab Patrick Smith] Co-captain of [http://www.civicdataalliance.org/ Louisville's Code for America Brigade].
* [https://www.openstreetmap.org/user/Lazarus%20LLC Chris Harrell]: CDA member
* [https://www.openstreetmap.org/user/Brian%20Herbert Brian Herbert]: Ushahidi Guy
==Process==
===User accounts===
In accordance with [[Import/Guidelines|Import Guidelines]], each uploader will use a separate user account specifically for this import. The user name will follow the pattern: <regularusername>_louisvilleimport
===Task Manager===
Here is where you can import the data area by area: http://tasks.openstreetmap.us/job/50
===Workflow===
See the [[Louisville,_Kentucky/Building_Outlines_Import/Contributor_Guide|Contributor Guide]] for all the details!
===Resources===
We're starting to collect info from previous imports that may be helpful to our volunteers:
* [http://www.youtube.com/watch?v=CuYVmMCBKiU Video: How to set up JOSM to integrate with task manager]
* [http://www.youtube.com/watch?v=DQPz0Qt-7bA&list=UU7finIieWNix2qRsSeIOt-A Video: creating an account for import]
* [http://www.openstreetmap.org/user/Richard/diary/16951 How to review and upload data from .osm files using Potlatch 2]
The folks who ran the NYC building import used a very similar process, and have a nice step-by-step video guide for getting started:
* [https://www.youtube.com/watch?v=DQPz0Qt-7bA&list=UU7finIieWNix2qRsSeIOt-A OSM NYC Building and Address Import (playlist of several ~2 minute video screencasts)] (one note: we will have a different OSM tasking manager URL than in the NYC case. Otherwise the same steps should work fine.)
QA tools:
* [http://tools.geofabrik.de/osmi/?view=addresses&lon=-90.04027&lat=29.96704&zoom=13&overlays=no_addr_street,street_not_found,nodes_with_addresses_defined Geofabrik tool for checking address tags]
==Source Code==
[https://github.com/civicdata/louisville-buildings Github Source code]
This is based on work from the [[DC_Buildings_%26_Addresses_Import|DC]] and [[Import/Catalogue/NYC_Buildings_Addresses|NYC]] and [https://github.com/mtoupsUNO/nola-buildings| NOLA] building imports, thanks to the folks who made that possible.
[[Category:Import from the United States|Louisville]]
[[Category:Kentucky]]