Import/Catalogue/Remarkable Trees Import Luxembourg

Remarkable Trees Import Luxembourg is an import of remarkable trees covering Luxembourg. As of 25.07.2019, this import has been performed, and all remarkable trees from the dataset were added to OSM.

Goals

As of 13 June 2019, there are currently 8 remarkable trees mapped in Luxembourg. The proposed dataset contains 535 trees.

Schedule

Phase 1 - Planning

Goal: Get community approval, write documentation and tools, prepare data.

Phase 2 - Prepare & Import

Goal: Conversion of data, Manual conflation of existing trees, followed by the actual import of all the remaining trees.

Import Data

Background

The dataset can be found on the Luxembourgish Open Data Portal.

Data source site: https://data.public.lu/en/datasets/remarkable-trees/
Data license: https://creativecommons.org/publicdomain/zero/1.0/
Type of license: CC0 1.0 Universal (CC0 1.0)
ODbL Compliance verified: yes

Import Type

The import will be a one-time import. Validation and uploading will be performed in JOSM.

Data Preparation

Data Reduction & Simplification

Using ogr2osm with a custom translation script, the original feature information will be mapped to the OSM tagging scheme. As the original data set does have some special cases, the output of this translation will not immediately be uploadable to OpenStreetMap. The goal is to reduce the manual workload as much as possible.

Tagging Plans

A remarkable tree is tagged with denotation=natural_monument, heritage=2 and heritage:operator=anf.

To decide whether natural=tree or natural=tree_row is used, we have to differentiate between the 4 types of features contained within the data set:

Different types of features

Type	natural=*	Additional Information
Einzelbaum	tree	Denotes a single tree
Allee	tree_row
Reihe	tree_row
Gruppe	tree	Multiple trees
Baumreihe	tree_row	Appears only once in the data set

Furthermore, the feature names are not standardized, i.e. the amount of information stored varies from feature to feature.

The full name will be tagged in taxon=*. If the feature name only contains the genus, it will be set in genus=*. If it also contains the species, species=* will be used instead.

Different scientific names variants

Example	OSM Tags (with regards to scientific name)
Quercus sp.	genus=Quercus taxon=Quercus sp.
Fagus sylvatica sp.	species=Fagus sylvatica taxon=Fagus sylvatica sp.
Fraxinus excelsior	species=Fraxinus excelsior taxon=Fraxinus excelsior
Fagus sylvatica Purpurea	species=Fagus sylvatica taxon=Fagus sylvatica Purpurea
Pinus nigra ssp. ARNOLD	species=Pinus nigra taxon=Pinus nigra ssp. ARNOLD
Pseudotsuga menz.	genus=Pseudotsuga taxon=Pseudotsuga menz.

To assist in the manual process, the raw features will be added as temporary tags prefixed with "debug:". These tags must be removed before uploading the changeset!

Changeset Tags

• comment=Import of remarkable trees in Luxembourg, this upload has been looked over by a human! Nevertheless, if something is wrong, please add a comment to this changeset!
• source=https://data.public.lu/fr/datasets/remarkable-trees/
• source:date=YYYY-MM-DD
• documentation=https://wiki.openstreetmap.org/wiki/Import/Catalogue/Remarkable_Trees_Import_Luxembourg
• type=import

Data Transformation

Prerequisites: Install ogr2osm, and GDAL.

wget https://github.com/DavidMoraisFerreira/ogr2osm-translations-luxembourg/blob/master/LU_remarkable_trees.py
wget https://download.data.public.lu/resources/remarkable-trees/20170718-224136/anf_remarkable_trees.geojson
python ogr2osm.py anf_remarkable_trees.geojson -t LU_remarkable_trees.py

Data Merge Workflow

Team Approach

Currently this import is being organized by dmlu (on osm).

References

The pages natural=tree and species=* will be used as a reference.

The tagging scheme is based on the discussion in talk-fr

Link to talk-lu announcement: https://lists.openstreetmap.org/pipermail/talk-lu/2019-June/000192.html

Workflow and Conflation

• Download the data set from the Luxembourgish Open Data Portal
• Download and execute the conversion utility
• Conflate using JOSM and Conflation Plugin
• Manually tag features that could not be automatically converted
• Once done:
  • Remove all the debug tags
  • Upload the changeset
• In the event that something does goes wrong, revert the whole changeset using the JOSM Reverter Plugin

Conflation

Identify your approach to conflation here.