Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.


O2A data is archived. The data structure for archiving is described here.

The SENSOR's parameter codes (URNs, Uniform Resource Names), e.g. vessel:polarstern:hydrosweep_ds3 describes the base storage directory for this specific device. This base directory is defined by the metadata description in  

Examples for base directory:  

Code Block



Subdevices of a base device are described in the sensor urn URN by adding the sub devices "Short Name" to the base device URN. E.g. For example

Code Block

. Base device and subdevices are named items for simplicity reasons. Any nesting of items is possible. There is no restriction for nesting.

Examples for different level of nesting in Sensor URNs:

Code Block
(type:item:item)         vessel:polarstern:hydrosweep_ds3
(type:item:item:item)    vessel:polarstern:tsk1:sbe38




:item)              towed_systems:loki_10001_02


(type:item:item)         towed_systems:loki_10001_02:microflu-chl_1228

Sensor URNs describe the data storage location in our archive. E.g. temperature data from the sbe38 sensor, from termosalinograph keel 1 tsk1, on vessel polarstern, are stored unter the root directory  directory /vessel/polarstern/tsk1/sbe38/.    Picture data from loki_10001_02 are archived under /towed_systems/loki_10001_02/. This is the base-directory.

Datastructure Data structure below Sensor URN base directory

The base-directory is given by the sensor urnURN. Expedition data is located under /the base - directory and an "/exdata   /" marker directory. The level below "/exdata/" describes the expedition and if applicable the science activity and device operation. Following schema shall  Following schema have to be used for naming this subdirectory:  (

Code Block

For example "  e.g. PS85_444-2  " describes expedition or event related data for expedition PS85  PS85 from science activity 444 and device operation 2).  This shall not be splitted into two directories!examples: . Splitting these information in nesting folders is not supported.


Code Block




(warning) Hint: underscore (_)        TODO: _ is ambiguous if used for "expedition_legvs " vs. "expedition_scienceactivity". _ shall therefore Therefore underscore (_) has not be used in the expedition name for legs.  "." has to be used  Use point (.) instead instead for splitting defining expeditions into with several legs. Examples for expeditions: PS120, For example PS122.1 (Expedition instead of PS122 leg 1), MSM09_3, HE_400,_1.