Preface
In context of MareHUB and the Viewer on marine-data.org data from different sources gets processed and provided as OGC Web Services. Mapping incoming data to unified names (target vocabulary) is part of this process. This page offers technical file specifications used during this process. It is not about the process (however, if in special cases there is process information, it is marked as such). For general information on processes, see the page on Standard Operating Procedures.
Most important related reading might be this page about Data Harmonization and the Mapping Principle.
Tables are color-coded. Input for the Mapping Algorithm has a light yellow, output a light blue background.
Version 0.1
There are two "types" of files. Those adding mapping rules and those introducing target vocabulary data can be mapped to. Mapping rules do not work without the according target vocabulary. Both are tab-separated files, only differing in column names.
Base specs as follows
- tab-separated text file
- UTF-8-encoding
- file extension: .sdi.mapping.tab
- order of columns matter
- columns without values (e.g.
sphere_name) can be dropped - custom columns can be appended but will get ignored (might be useful for future verification, for example)
Target Vocabulary Files
Units
column | column header | value is mandatory | description | example values (all valid) |
|---|---|---|---|---|
| 1 | unit_name | yes | name of unit | degree Celsius Kelvin meter per second |
| 2 | unit_symbol | yes | symbol of unit | °C K m/s |
| 3+ | <whatever_you_like> | no | can be used for comments or notes/reminders – will get ignored technically |
Examples
Parameters
Column header for parameter vocabulary is parameter_group because currently it is used as rough grouping instead of precise mapping. However, both would be possible.
column | column header | value is mandatory | description | example values (all valid) |
|---|---|---|---|---|
| 1 | parameter_group | yes | name of parameter or parameter group | Temperature Total Organic Carbon |
| 2 | parameter_sdn | no | SDN of parameter | |
| 3 | parameter_nerc_uri | no | NERC URI of parameter | |
| 2+ | <whatever_you_like> | no | can be used for comments or notes/reminders – will get ignored technically |
Examples
Methods
Column header for method vocabulary is method_group because currently it is used as rough grouping instead of precise mapping. However, both would be possible.
column | column header | value is mandatory | description | example values (all valid) |
|---|---|---|---|---|
| 1 | method_group | yes | name of method or method group | direct count electric |
| 2+ | <whatever_you_like> | no | can be used for comments or notes/reminders – will get ignored technically |
Examples
Spheres
Process information: Status Quo is NERC spheres. Please consult AG Ocean Obs (Norbert Anselm) and AG Viewer (Peter Konopatzky) before introducing other sphere vocabulary.
column | column header | value is mandatory | description | example values (all valid) |
|---|---|---|---|---|
| 1 | sphere_name | yes | name of sphere | atmosphere water body |
| 2 | sphere_sdn | no | SDN of sphere | |
| 3 | sphere_nerc_uri | no | NERC URI of sphere | |
4+ | <whatever_you_like> | no | can be used for comments or notes/reminders – will get ignored technically |
Status Quo
sphere_name | sphere_sdn | sphere_nerc_uri |
|---|---|---|
atmosphere | SDN:S21::S21S001 | |
water body | SDN:S21::S21S027 | |
surface ice | SDN:S21::S21S009 | |
rock | SDN:S21::S21S038 | |
biota | SDN:S21::S21S037 | |
not applicable | SDN:S21::S21S017 | |
Earth | SDN:S21::S21S006 | |
bed | SDN:S21::S21S003 | |
cave atmosphere | SDN:S21::S21S033 | |
experiment water sample | SDN:S21::S21S011 | |
geological sample | SDN:S21::S21S039 | |
groundwater | SDN:S21::S21S005 | |
peat | SDN:S21::S21S019 | |
rainwater | SDN:S21::S21S020 | |
sediment | SDN:S21::S21S022 | |
sediment pore water | SDN:S21::S21S023 | |
snow | SDN:S21::S21S024 | |
stalactite | SDN:S21::S21S034 | |
stalagmite | SDN:S21::S21S025 | |
suspended particulate material | SDN:S21::S21S026 | |
water body plus atmosphere | SDN:S21::S21S028 | |
wet sediment | SDN:S21::S21S031 |
Examples
Mapping Rules Files
Output columns (light blue) need to hold target vocabulary established via target vocabulary files.
Unit Mapping
column | column header | value is mandatory | description | example values (all valid) |
|---|---|---|---|---|
| 1 | unit_string | yes | mapping input, any string that should get mapped | °C ◦C degC |
| 2 | unit_name | yes | mapping output: unit name (see Unit Vocabulary) | degree Celsius |
| 3+ | <whatever_you_like> | no | can be used for comments or notes/reminders – will get ignored technically |
Examples
Parameter Mapping
column | column header | value is mandatory | description | example values (all valid) |
|---|---|---|---|---|
| 1 | parameter_string | yes | mapping input, any string that should get mapped | Temperature Temperature, air WaterTemp_FSI |
| 2 | parameter_group | yes | mapping output: any known method name/group (see Parameter Vocabulary) | Temperature |
| 3 | sphere_name | no | mapping output: any known sphere name (see Sphere Vocabulary) | atmosphere |
| 4+ | <whatever_you_like> | no | can be used for comments or notes/reminders – will get ignored technically |
Examples
Method Mapping
column | column header | value is mandatory | description | example values |
|---|---|---|---|---|
| 1 | parameter_group | yes | mapping input: any known parameter name (see Mapping Names) | valid: Temperature invalid: WaterTemp_FSI |
| 2 | method_string | yes | mapping input: any string that should get mapped | valid: Mercury thermometer |
| 3 | method_group | yes | mapping output: any known method name/group (see Method Vocabulary) | valid: direct valid: unspecified valid: electrical |
| 4 | sphere_name | no | mapping output: any known sphere name (see Sphere Vocabulary) | valid: atmosphere valid: water body valid: sediment |
| 5+ | <whatever_you_like> | no | can be used for comments or notes/reminders – will get ignored technically |
Examples
Combined Example
Imagine you have the following data you want to have integrated into our SDI. It already comes in handy O2A GeoCSV format, including metadata files. Two data files (and two metadata files) with comparable datausing different vocabulary, and almost none of them using the vocabulary you want.
The following Mapping Files would be good solution to properly add above data to our SDI and have it integrated into VEF-based viewers. The most important part is the parameter mapping. Without this, data cannot be integrated into our parameter measurement layers. Unit and method mapping are recommended for proper filtering but can be left out. In any case both source strings/names and mapping results will be shown/accessible in viewers.
Overview
Content Tools