...
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. |
|
...
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 |
It is a GeoCSV using the WKT notation for the description of the geometry. However, there are additional requirements regarding columns, their names, their order and some other details.
...
valid: 2019-02-28T15:50:00
invalid: 2019-02-28T15:50:00.000
invalid: 2019-02-28 15:50:00.000
...
Elevation in meter. A negative value means below sea level, while positive means above sea level.
Note: Depth, and maybe altitude as well, must be converted!
...
Data from sensor.awi.de:
valid: vessel:polarstern:tsk1:salinity [psu]
valid: vessel:polarstern:tsk1:principal_investigator []
invalid: vessel:polarstern:tsk1:principal_investigator[]
invalid: vessel:polarstern:tsk1:principal_investigator
invalid: vessel:polarstern:tsk1:principal investigator []
Data from www.pangaea.de:valid: pangaea:12345:sal [psu]
...
Geometry in WKT notation. <type>
can be one of the following:
point → geometry [point]
multipoint
→ geometry [multipoint]
linestring
→ geometry [linestring]
multilinestring
→ geometry [
multilinestring
]polygon → ...
multipolygon
geometrycollection
Column and values are mandatory. <type>
defaults to point
. Rows with missing values will be ignored.
...
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))
datetime
) need to end with square brackets, containing a unit (or a geometry type)<column_name>
and [<unit>]
).sdi.tab
.
(point)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)
...
...