Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: drop deprecated version 1.1

...

column
type/group
column ordercolumn headervalue is
mandatory
descriptionexample values
spatio-temporal location1

date_time_start

yesDate 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

 

2date_time_endno

End of time range of measurement in ISO 8601 format notation, using UTC time zone, without fractions of seconds.

see above
3elevation [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.


4z_value [m]noVertical position of the measurement, in meter (third spatial dimension).
5z_typeyes, 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 reference6event_nameyesName 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 locationlastgeometryyes

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 (123.45678 -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))

...

Code Block
languagebash
titlethree valid examples
./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

Version 1.1 (deprecated)

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))

  • restrictions for column names
    • all column names (except datetime) 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.tab
  • decimal 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)

Data from www.pangaea.de

...

...