Versions Compared

Old Version 3

changes.mady.by.user Peter Konopatzky

Saved on

compared with

New Version Current

changes.mady.by.user Peter Konopatzky

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: updated to version 1.1 (changed timezone specs)

...

Its main purpose are single-source layers where data is coming in a harmonized table structure and vocabulary.

Version 1.

...

1

This specification comprises three different file types. The two Layer Definition Files play a role when using O2A GeoCSV files inside a standardised O2A SDI SOP dataflow They define the target structure of the database table fueling a WMS/WFS. Data Files and Join Files contain the actual data that should be provided as WMS/WFS. Join Files are an optional feature to reduce data redundancy during data exchange. Data Files can be chunked to organise your data. See the subsections, especially the examples for further understanding.

...

Column TypeExplanationComment
Integer(Boolean)booleanValues need to be 0 (meaning false) or 1 (meaning true).
Integernatural number
Realdecimal numeral
Stringstring/textCould contain lists/dictionaries formatted as strings (see examples)
DateTimetimestamp (UTC)
WKTgeometry in WKT format

...

Not every O2A GeoCSV file needs to contain all columns (except for those mandatory) of the target layer (as described in the Layer Definition Files). All unmentioned columns will hold null values for all rows of O2A GeoCSV data files not containing them.

Column Name Conventions

column
type/group		column
header		column
data type		column+value
mandatory?		descriptionexample values
space/time
metadata

date_time_start

DateTime

yesDate and time of data point in ISO 8601 format
notation, using UTC time zone, Or
notation or start of time range. Since version 1.1: time zone specification (e.g. +00 for UTC) is mandatory but could be different from UTC.

valid:


 2019-02-28T15:50:00+00:00
valid:

  

2019-02-28T15:50:00.000+00

valid


invalid: 2019-02-28T15:50:00

.000+00


invalid: 2019-02-28 15:50:00

 

date_time_end

DateTime


End of time range of measurement(s) in ISO 8601 format notation, using UTC time zone.

see above
elevation

Real


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/observation (unless it's taken on earth's surface) but the topographical elevation at the lon/lat position.

valid: 200.1
valid: -200

invalid: -200m

z_value

Real


Vertical position of the measurement, in meter (third spatial dimension).
z_type

String

yes,
if z_value
is given		Pangaea Geocode to describe the type of z_value.

valid: "DEPTH, water"
valid: "DEPTH, sediment/rock"
valid: "HEIGHT above ground"

invalid: "HEIGHT above aeroplane"

geometry

WKT

yes

Geometry in WKT notation without third/vertical spatial dimension. The reference system needs to be EPSG:4326 and the unit decimal degrees. Longitude first, latitude second. The geometry type can be chosen freely. However, a simple POINT is usually the best choice.

valid: POINT (123.45678 -20.12345)
valid: 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))

invalid: POINT (-20.12345 123.45678)

data, other metadata ** 
no

Arbitrary amount of data and/or metadata columns. For some metadata columns specific vocabulary needs to be used (see section).

valid: "pressure"
valid: "pressure_unit"
valid: "license"
valid: "sample_type"
valid: "exposure_time"

join
functionality		csv_join
none
no

Used to hold join keys for the use of join files. Must not appear in layer defintion files!

 

Metadata Vocabulary

This is a list of compulsory and encouraged vocabulary to use for column headers (if columns with corresponding meaning are used). Compulsory vocabulary does not mean that the column itself is compulsory. Some vocabulary is encouraged to foster consistency among AWI-hosted OWS. but may be deviated from (e.g. basis instead of platform).

...