Ballarat Building Import

Goals

Import a full map of buildings in Ballarat, from https://data.gov.au/dataset/ballarat-3d-buildings including Height and outline.

Status

Draft

Schedule

• December 2018 - planning, consultation
• Feb - import via JOSM in small batches via dedicated account.

Import Data

Background

Provide links to your sources.

Data source site: https://data.gov.au/dataset/ballarat-3d-buildings
Data license: http://creativecommons.org/licenses/by/3.0/au/
Type of license (if applicable): CC-BY-A
Link to permission (if required): http://wiki.openstreetmap.org/wiki/Attribution/data.gov.au_explicit_permission
OSM attribution (if required): http://wiki.openstreetmap.org/wiki/Attribution/data.gov.au_explicit_permission
ODbL Compliance verified:

OSM Data Files

https://drive.google.com/drive/folders/11wpnyswt7PYuxFiKk-K7JPQgZJOvcDly

Import Type

Using JOSM to upload new buildings, transformed from existing shapefiles.

The source data is from the local government authority.

Pending Questions

Posted as commentary to the data.gov.au page on 26-Dec-2018

Hi, thanks for publishing this - it's a great dataset!

I'm looking at importing the data into OpenStreetMap. and wanted to check a few things

1) How is the data derived? LIDAR? Submitted building plans? Other?

2) How is the data aligned to the ground? (It seems very accurate)

Also, I'd like to double check that the City of Ballarat is happy with this / other datasets licensed on data.gov.au would be acceptable to use with ODBL - it is conceptually similar to but slightly different to a CC BY A 3.0 license.

https://opendatacommons.org/faq/licenses/index.html#Why_Not_Use_a_Creative_Commons_or_FreeOpen_Source_Software_License_for_Databases talks a little about the differences.

Data Preparation

Data Reduction & Simplification

• Map 'Height_M' => "height"
• Add building=yes to new buildings
• Remove all other keys

Alignment

In general, the data aligns well with existing tracing:

In some areas, existing tracing is slightly offset:

Tagging Plans

• building=yes
• height=12.34

Changeset Tags

JOSM will handle the majority of this.

Changeset messages will be 'Building import from data.gov.au for Ballarat'

Data Transformation

Describe the transformations you'll need to conduct, the tools you're using, and any specific configurations or code that will be used in the transformation.

Data Transformation Results

See https://drive.google.com/open?id=11wpnyswt7PYuxFiKk-K7JPQgZJOvcDly

Data Merge Workflow

Team Approach

Team:

• User:CloCkWeRX (Import, misc armchair mapping)
• User:Pierce (Ballarat based mapper, verification of data, misc GPS data)
• Interested members of the talk-au mailing list.

References

List all factors that will be evaluated in the import.

Workflow

New buildings

• Download original shapefiles
• Transform to .osm via JOSM
• Manipulate xml with text editor
  • Remove <tag k='RoofElev' v='\d+\.\d+' />
  • Remove <tag k='GroundElev' v='\d+\.\d+' />
  • Remove <tag k='Area_m2' v='\d+\.\d+' />
  • Remove <tag k='GGIS_UNQID' v='\d+' />
  • Add building=yes tags
• Reload into JOSM
• Add openstreetmap-carto, bing as a background layer
• Import only new buildings by hand.
• JSOM validation and cleanup

Existing buildings

• Download buildings where height is not present (TODO: Precise overpass query) as new layer
• Conflation plugin to select existing geom, new height tag where suitable

Buildings

Conflation

Existing buildings will be either kept, merged, or discarded depending on the quality of mapping. The more metadata or if surveyed, the more likely it will be preferred over the lidar version.

QA

• Keepright and JOSM validations of the dataset for overlapping buildings.
• Verification of data from local knowledge