Bend Parks Import Plan

From OpenStreetMap Wiki
Jump to: navigation, search

About

Bend Parks and Rec District (BPRD) informed me on a phone call that the data for the park boundaries and trails was available, and I was free to import it into OSM.

The data consists of about 30-40 park boundaries with misc tagging. There are about 5 parks already in OSM from other contributors.

Steve Jorgensen <Steve@bendparksandrec.org> provided me with shapefiles for the import via email. He also informed me over the phone that there were no restrictions on the data.

Import Plan Outline

Goals

Parks are underrepresented in OSM data in Bend. The goal is to map all the parks that were provided by BPRD.

Schedule

Short-term.

Import Data

Background

Data source site: Shapefile data was provided in an email; a copy is here: http://beej.us/osm/bend_parks_import/bprd_parks_2014.zip
Type of license: Public Domain
ODbL Compliance verified: yes

OSM Data Files

http://beej.us/osm/bend_parks_import/bprd_parks_2014_import_v4.osm

Import Type

This is a one-time import via JOSM.

Data Preparation

Data Reduction & Simplification

Ways will be simplified using JOSM's Simplify Way tool with a max error of 0.25 meters.

Tagging Plans

Tags to be Changed

Park_Name will be changed to name.

Tags to be removed

All other existing tags will be removed.

Tags to be added

Will also add tag leisure=park to any element with a Park_Name tag.

Changeset Tags

comment
Bend OR Parks Import
source
Bend OR Parks and Recreation Department, 2014 parks export
source:license
Public Domain
bot
no
type
import

Data Transformation

Shapefile will be loaded into JOSM using the OpenData plugin.

An OSM XML export will be performed from JOSM.

A custom Python script will do tag manipulation, producing the final OSM XML.

Data Transformation Results

http://beej.us/osm/bend_parks_import/bprd_parks_2014_import_v4.osm

Data Merge Workflow

Team Approach

Solo.

Workflow

After the transformation is done, above, the import will take place in a single changeset. The dataset size is small.

Conflation

OSM data will be used except when it obviously contradicts BPRD data. Since park boundaries aren't obvious, BPRD will be given some value as the authority.

QA

Every park will be manually inspected.