- 1 Goals
- 2 Schedule
- 3 Import Data
- 4 Data Preparation
- 5 Data Merge Workflow
To get more and/or better quality landuse data, mostly natural and water related
The Swedish parts of the EU Natura 2000
Data source site: Links in feed
Data license: metria.nu/miljodataportalen
Type of license : CC-0
ODbL Compliance verified: yes
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.
|KARTERINGS||Review status: keep in transformation to aid in conflation (remove before upload?)|
|KOMMENTAR||Comment: keep in transformation to aid in conflation (remove before upload?)|
|KOMPLEX||Parent type (ie lake in bog or beach in islet): ignore|
|NATURTYP||Class: base for transformation see table keep in transformation to aid in conflation (remove before upload?)|
|NNK_KOMMEN||Comment: keep in transformation to aid in conflation (remove before upload?)|
|OBJECTID||Id: ignore most features are going to be merged anyway|
|NATURTYPKO||Class of parent type: ignore|
Describe how you'll use changeset tags in the import.
Parsing source shp files with ogr2osm todo put transformation script on git hub
Note that several codes are defined as uncertain in the source material and need to be classified be the user doing the conflation.
Data Transformation Results
First example draft (2017-04-07 end result is post-conflation)
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.
Use the official interpretations as guides for uncertain areas
Detail the steps you'll take during the actual import.
Information to include:
- Step by step instructions
- Changeset size policy
- Revert plans
Remember to open adjacent files when working near Län borders
There are no duplicates across the shp files so some large features are missing of you only use data from one file.
Note that the quality varies a lot from orthophoto (normal and IR) traced and field verified on the high end to ~30x30m resolution semiautomatic classified from aerial /satellite imagery on the low end.
Line data quality is good for position but poor for connectivity and direction, ie every way need verifying.
Select appropriate size data, inc any relations
copy (control + c) - new layer (control + n) - paste at source position (control + alt + v)remove small areas, jsom filter
check fixme and comments, remove fixme when done
join adjacent areas with the same tags (shift + j)
merge in existing osm data
use replace geometry (control + shift + g) when replacing objects