Allegheny County, PA Import
- 1 About
- 2 Import Plan Outline
- 3 Goals
- 4 Schedule
- 5 Prior Art
- 6 Import Data
- 7 Data Preparation
- 8 Data Merge Workflow
- 9 QA
This project outline is intended to help ensure that your Import Plans covers as many of the common questions about imports as possible. Just create your own page and cut and paste the editing information from this page into it.
Please! If you identify ways that this outline didn't meet the needs of your import (key evidence of this: tons of questions or alarm bells on mailing lists!), please return and fix this page.
Import Plan Outline
- Create a more complete map of Pittsburgh
- Put existing high quality building footprint data to use for the OSM community
- Re-energize the Pittsburgh OSM community by working on a project with a shared vision
A group of OSM contributors interested in a building footprint import team came together at a MaptimePGH meetup to research process and plan for the import. Since we will not finish this wiki page in one meet up, we're collecting some examples of past imports and process documentation here to help guide the work moving forward.
Provide links to your sources.
Data license: https://website.tld/license
Type of license (if applicable): e.g. CC-BY-SA, Public Domain, Public Domain with Attribution, etc.
Link to permission (if required): e.g. link to mail list reference url - http://lists.openstreetmap.org/pipermail/imports/2012-December/001617.html
OSM attribution (if required): http://wiki.openstreetmap.org/wiki/Contributors#yourdataprovider
ODbL Compliance verified: yes/no
OSM Data Files
Link to your source data files that you have prepared for the import - e.g. the .osm files you have derived from the data sources.
Identify if this is a one-time or recurring import and whether you'll be doing it with automated scripts, etc.
Identify what method will be used for entering the imported data into the OSM database - e.g. API, JOSM, upload.py, etc.
Data Reduction & Simplification
Describe your plans, if any, to reduce the amount of data you'll need to import.
Examples of this include removing information that is already contained in OSM or simplifying shapefiles.
Describe your plan for mapping source attributes to OSM tags.
Describe how you'll use changeset tags in the import.
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
Post a link to your OSM XML files.
Data Merge Workflow
Describe if you'll be doing this solo or as a team.
List all factors that will be evaluated in the import.
Detail the steps you'll take during the actual import.
Information to include:
Step by step instructions Changeset size policy Revert plans
Identify your approach to conflation here.
Add your QA plan here.