Riverside County, California/Address Point Import
- 1 Goals
- 2 Schedule
- 3 Import Data
- 4 Data Preparation
- 5 Data Merge Workflow
- 6 QA
Identify the goals of the import.
Be sure to list the general timeframe of your project.
Provide links to your sources.
Data source site: http://website.tld
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.