Page History

...

requirements
- file extension: .sdi.tab
- decimal separator: . (point)
- column separator: \t (tab) → no tab in values or column headers
- column names need to be unique
notes
- white spaces are allowed both in cells and column names
- columns can be left out entirely if they do not keep any values (e.g. date_time_end)
- empty cells in non-value-mandatory columns are fine, if information is unknown
  - will default to NULL (≠ 0) internally
- rows with missing or invalid mandatory values will be ignored
- column order matters (although some columns might be left out)

column type/group	column order	column header	value is mandatory	description	example values
spatio-temporal location	1	date_time_start	yes	Date and time of measurement in ISO 8601 format notation, using UTC time zone, without fractions of seconds. Or start of time range.	valid: `2019-02-28T15:50:00` invalid: `2019-02-28T15:50:00.000`invalid: `2019-02-28 15:50:00`
	2	date_time_end	no	End of time range of measurement in ISO 8601 format notation, using UTC time zone, without fractions of seconds.	see above
	3	elevation [m]	no	Elevation in meter. A negative value means below sea level, while positive value means above sea level. See Pangaea Geocode definition. Note: This is not the height/depth of the measurement (unless it's taken on earth's surface) but the topographical elevation at the lat/lon position.
	4	z_value [m]	no	Vertical position of the measurement, in meter (third spatial dimension).
	5	z_type	yes, if `z_value [m]` is given	Pangaea Geocode to describe the type of `z_value [m]`.	valid: "DEPTH, water" valid: "DEPTH, sediment/rock" valid: "HEIGHT above ground" invalid: `"HEIGHT above aeroplane"`
metadata reference	6	event_name	yes	Name of event. Reference key for metadata. `event_name` must match one event name in metadata file (if metadata file is used).	PS1010-1
data		<parameter> [<unit>]	no	Arbitrary amount of columns (at least one) with (measurement) data. Each column name has to start with the parameter/phenomenon name followed by a unit in square brackets. `<parameter>` and `[<unit>]` are separated by a single whitespace. Reference key for metadata. `<parameter>` must match the parameter name in metadata file (if metadata file is used).
spatio-temporal location	last	geometry	yes	Geometry in WKT notation without third spatial dimension. The reference system needs to be EPSG:4326 and the unit is decimal degrees. Longitude comes first, latitude second. The geometry type can be chosen freely. However, a simple POINT is usually the best choice.	`POINT (7.33333 -20.12345)` `MULTILINESTRING ((8.58 53.55, 8.58 53.56, 8.57 53.55), (8.0 53.0, 9.0 54.0, 8.0 54.0))`

Beispiele

PANGAEA-inspired example

...

Also, please read the JSON specs to know about things like how to escape special characters.

top level keys	second level keys	mandatory	description	example values
version		yes	used O2A Spatial GeoCSV specification	`"2.0"`
events		yes
	name	yes	event name, serves as metadata reference to data file	`"PS01/00001"`
	alias		event alias
	expedition		name of expedition the event is part of, references entry in expeditions list	`"ANT-I/1"`
	platform		used platform, references entry in expeditions list	`"Polarstern"`
	device		used device	`"Radiosonde (RADIO)"`
	uri		URI/URL
	meta		key-value pairs for custom event metadata (see next table)
parameters		no
	name	yes	parameter name (reference key)	`"Temperature, air"`
	alias		parameter alias	`"TTT"`
	unit		unit of measurement	`"°C"`
	method
	uri		URI/URL
	meta		key-value pairs for custom parameter metadata (see next table)
expeditions		no
	name	yes	expedition name (reference key)	`"ANT-I/1"`
	alias		expedition alias	`"PS01"`
	uri		URI/URL	`"https://doi.org/10.2312/BzP_0014_1983"`
	meta		key-value pairs for custom metadata (see next table)
platforms		no
	name	yes	platform name (reference key)	`"Polarstern"`
	alias		platform alias
	uri		URI/URL	`"https://doi.org/10.17815/jlsrf-3-163"`
	meta		key-value pairs for custom metadata (see next table)
projects		no
	name	yes	project name (reference key)	`"Meteorological Long-Term Observations @ AWI"`
	alias		project alias	`"AWI_Meteo"`
	uri		URI/URL	`"http://www.awi.de/en/science/long-term-observations.html"`
	meta		key-value pairs for custom project metadata (see next table)
meta		no	key-value pairs for custom dataset metadata (see next table)

meta keys	description	example values
pi_name	name of principle investigator	`"König-Langlo, Gert"`
pi_email	mail of principle investigator	`"gert.koenig-langlo[at]awi.de"`
pi_url	homepage of principle investigator	`"http://www.awi.de/en/about-us/organisation/staff/gert-koenig-langlo.html"`
pi_orcid	ORCID of principle investigator	`"https://orcid.org/0000-0002-6100-4107"`
comment		`"Height of tropopause 11650 m"`
citation		`"König-Langlo, Gert (1983): Radiosonde PS01/00001 during POLARSTERN cruise ANT-I/1 on 1982-12-29 11:24h. Alfred Wegener Institute, Helmholtz Centre for Polar and Marine Research, Bremerhaven, PANGAEA, https://doi.org/10.1594/PANGAEA.382336,` `In: König-Langlo, G (1983): Upper air soundings during POLARSTERN cruise ANT-I/1. Alfred Wegener Institute, Helmholtz Centre for Polar and Marine Research, Bremerhaven, PANGAEA, https://doi.org/10.1594/PANGAEA.853633"`
project	references entry in projects list
license		`"Creative Commons Attribution 3.0 Unported (CC-BY-3.0)"`
metadata_url	link to metadata	`"https://doi.pangaea.de/10.1594/PANGAEA.382336?format=metadata_jsonld"`
data_url	link to data	`"https://doi.pangaea.de/10.1594/PANGAEA.382336?format=textfile"`
sop_url	link to SOP information

Examples

Minimal example

Code Block

language	js
title	valid example with two versions of same metadata
linenumbers	true

// Minimal example of a metadata file (.sdi.meta.json), only containing version and one event with an expedition name
{
    "version": "2.0",
    "events": [
        {
            "name": "foo",
            "expedition": "bar"
        }
    ]
}


// Less minimal representation of the same metadata. Both versions are valid.
{
    "version": "2.0",
    "events": [
        {
            "name": "foo",
            "expedition": "bar"
        }
    ],
    "expeditions: [
        {
            "name": "bar",
            "alias": ""
        }
    ],
}

...

Versions Compared

Old Version 4

New Version 5

Key

Beispiele

PANGAEA-inspired example

Examples

Minimal example