Bend building import
- 1 About
- 2 Import Plan Outline
- 3 Goals
- 4 Schedule
- 5 Import Data
- 6 Data Preparation
- 7 Data Merge Workflow
The city of Bend, Oregon has offered a complete building footprints layer with an OSM-acceptable license. The current building footprint layer in OSM contains about 1,100 buildings (as of 9/26/16), mostly traced by hand from satellite imagery. The building footprints file available from the city contains more than 36,000 features. In addition, building heights and addresses can be derived for each building from publicly-available data sets.
Import Plan Outline
[x] Acquire data from city
[x] Determine OSM tags to be included
[x] Process data
[ ] Divide data into discrete tasks
[ ] Complete import
Add an extensive building footprints layer for Bend, Oregon to OpenStreetMap with tags for addresses and building heights.
Planning meeting with interested volunteers scheduled for Oct. 6, 2016.
Generation of height and address fields was completed in February 2017.
Building footprints shapefile: https://github.com/MaptimeBend/bend_buildings/tree/master/data
Deschutes County open data taxlot file: http://data.deschutes.org/datasets/28019431cced49849cb4b1793b075bf1_2
Deschutes County open data assessor info (for addresses): http://data.deschutes.org/datasets/aea94004ae8c49e6a6dec394522677ad_1
Oregon DOGAMI lidar data: https://coast.noaa.gov/htdata/lidar1_z/geoid12a/data/1452/
OSM Data Files
Not yet created.
Data Reduction and Simplification
Probably not necessary. Most buildings are basic rectangles with few points that could be removed.
The buildings shapefile contains several fields that will be eliminated as they are artifacts of the file's CAD origins.
We'll include new tags for
addr:street. In addition, we'll retain existing tags for nodes and areas that will be updated with our import. We'll use the Replace Geometry tool in JOSM as needed to retain existing tags and history.
- Buildings acquired from city loaded into POSTGIS database (Software: psql)
- Taxlots acquired from county loaded into POSTGIS database (Software: psql)
- Assessor table (with addresses) loaded into POSTGIS database (Software: psql)
- Raw lidar .laz file processed to use only first returns, converted to elevation x/y/z .txt file, loaded into POSTGIS (Software: liblas, laszip, psql)
- Existing OSM buildings exported using Overpass Turbo, loaded into POSTGIS database (Software: Overpass Turbo, psql)
- Perform union of existing OSM buildings and Buildings?
- This is where we'll need to make some decisions and do some data-wrangling.
- Many existing OSM buildings might be newer than the Buildings, and should be kept
- However, many OSM buildings that already exist in the Buildings data are of inferior quality to the professionally-produced Buildings footprints
- Existing OSM buildings will have some tags that we will want to preserve
- Perform a join between Addresses table and Taxlots table using taxlot id (this is a one-to-one relationship). (Software: psql)
- Perform a spatial join between Buildings and Taxlots tables, adding specific address fields to Buildings table (Software: psql)
- Extract Buildings heights from Elevation table following similar steps as those outlined in this tutorial.
- Convert final fields from Buildings table to appropriate OSM tags.
Data Transformation Results
Data Merge Workflow
To be discussed at Oct. 6 meeting.