Bothell import

From OpenStreetMap Wiki
Jump to: navigation, search

Goals

Import building and address data for the city of Bothell, WA

Schedule

  • Planning: Spring 2018
  • Import: Spring/Summer 2018
    • Data Translation In Progress
    • Announce Import
    • Data Import
  • QA: Summer/Fall 2018

Import Data

Background

Data source site: [1]
Data license: The City makes no representation or warranty that the GIS data provided by this FTP site is accurate, true or correct. In using the data, it’s understood and agreed the information provided may be subject to error. GIS Data produced by the City of Bothell is intended for internal purposes only. The Data is made available on an "as is" condition with no representation or guarantee made concerning the accuracy, currency, or completeness of the information provided.

Import Type

This will be a one time import.

JOSM will be used to upload data in 153 parts, data will be split by voting district and uploaded under the user bothell_wa_import.

Data Preparation

Data Reduction & Simplification

Data that is already in OSM will not be overwritten unless it's clear that the OSM data is outdated. This should only be an issue in retail/commercial areas as residential areas are unmapped. Kirkland Addresses will be removed since they have been previously imported.

Tagging Plans

Buildings to building = yes unless building type is provided in which case it will be translated to appropriate building tag.

Address attributes of housenumber, street, city and zip for all addresses. Unit will be added where applicable.

See ogr2osm translation files for details.

Changeset Tags

Edits will be marked with source = Bothell WA GIS


Data Transformation

  1. Data source files are .shp and will be pulled into postgres db using sql scripts called from bash script
  2. Address conflation done using sql scripts on postgres with postgis
  3. Data output from postgres db to shp using pgsql2shp called from bash script that outputs data into many files corresponding to voting district
  4. shp files converted and tags translated to OSM xml using ogr2osm and corresponding translation files for buildings and addresses

Scripts in scripts folder of import repository

Data Transformation Results

OSM xml files in osm folder of import repository

Data Merge Workflow

Team Approach

TBD

References

Data will be checked using the following:

  • Local Knowledge
  • Mapbox Satellite View
  • Existing OSM Data

Workflow

Initial Translation

  1. Transform data using scripts in code repository

Import

  1. Load single OSM xml file into JOSM
  2. Check sat view and existing data to ensure data is reasonable
  3. Commit changes and update tasking manager
  4. Repeat steps 2, 3 and 4 with next OSM xml file
  5. Second QA pass using data downloaded from OSM, preferably by different person and update tasking manager

Conflation

Buildings with one address will have address added to building. Buildings with multiple addresses will not be combined. This will be done using scripts before the actual import starts.


QA

HOT tasking manager will be used to keep track of which areas have been checked. Data will be checked for:

  • overlapping buildings
  • out of date buildings
  • redundant addresses