Page History
...
| 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: |
| 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, ifz_value is given | Pangaea Geocode to describe the type of z_value [m]. | valid: "DEPTH, water" | |
| 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. Reference key for metadata. | ||
| 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. |
|
...
Examples
PANGAEA-inspired example
| Code Block | ||
|---|---|---|
| ||
date_time_start z_value [m] z_value_type event_name Pressure, at given altitude [hPa] Temperature, air [°C] geometry 1982-12-29T11:02:00 10 Altitude PS01/00001 1035.0 8.3 POINT(-4.3 49.6) 1982-12-29T11:45:00 956 Altitude PS01/00001 921.4 0.9 POINT(-4.3 49.6) 1982-12-29T13:21:00 1035 Altitude PS01/00001 912.4 0.2 POINT(-4.3 49.6) |
...
| 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 | ||||||
|---|---|---|---|---|---|---|
| ||||||
// 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": ""
}
],
} |
...
All data files with the same <basename> are associated with the corresponding metadata file. The @<handle> can be used to have multiple data files with the same <basename>. Files can only have up to one handle, and '@' cannot be used anywhere else in filenames.
Examples
| Code Block | ||||
|---|---|---|---|---|
| ||||
./path/to/data |-- foo.sdi.meta.json |-- foo@1999.sdi.tab `-- foo@2000.sdi.tab ./path/to/data |-- foo.sdi.meta.json |-- foo.sdi.tab |-- bar.sdi.meta.json `-- bar.sdi.tab ./path/to/data |-- foo.sdi.meta.json |-- foo@part1.sdi.tab |-- foo@part2.sdi.tab |-- bar.sdi.meta.json `-- bar.sdi.tab |
...
restrictions for column namesall column names (exceptdatetime) need to end with square brackets, containing a unit (or a geometry type)if there's no unit, the square brackets should be left empty
no spaces (except between<column_name>and[<unit>])
file extension:.sdi.tabdecimal separator:.(point)
Examples
Data from sensor.awi.de
datetime longitude [deg] latitude [deg] elevation [m] vessel:polarstern:tsk1:salinity [psu] geometry [point]2019-02-28T15:50:00 -14.17956 34.03449 -1 34.1234 POINT(-14.17956 34.03449)2019-02-28T15:50:01 -14.17956 34.03449 -2 34.1345 POINT(-14.17956 34.03449)2019-02-28T15:50:02 -14.17956 34.03449 -3 34.1456 POINT(-14.17956 34.03449)
...
Overview
Content Tools