Skip to content

Latest commit

 

History

History
156 lines (139 loc) · 4.06 KB

06-Marine-SWE.md

File metadata and controls

156 lines (139 loc) · 4.06 KB

Use Case Description “marine SWE group”

Robert Huber et al.
May 2018

Introduction

Over the last years, marine organisations, projects and communities have been working towards standardisation of sensor data and metadata by implementing OGC Sensor Web Enablement (SWE) standards. To avoid interoperability issues in OGC SWE implementations within the marine community, an agreement was needed on how to apply SWE concepts and how to use vocabularies in a common way that would be shared by different projects, implementations, and users.

The SWE Marine Profiles group was created as a solution to the above mentioned need. The group involves partners from several projects and initiatives (AODN, BRIDGES, EMSO, ENVRIplus, EUROFLEETS/EUROFLEETS2, FixO3, FRAM, IOOS, Jerico/Jerico-Next, NeXOS, ODIP/ODIP II, RITMARE, SeaDataNet, SenseOcean, X-DOMES) who joined forces to develop common marine profiles of OGC SWE standards that can be used in multiple projects and organizations.

Use Case

The group has identified some key areas in sensor descriptions of platform models, their instances, sensor models and sensor instances. One of the main foci was the provision of key vocabularies that cover six SensorML sections, namely the History, Capabilities, Characteristics, Classification, Identification and Contacts.

Identification of sensors is of key importance for the marine SWE group. A dedicated vocabulary has been agreed on and published at http://vocab.nerc.ac.uk/collection/W07/current/ in order to allow to distinguish between the different levels of identifications for sensors, platforms and their instances such as ‘Model number’, ‘Serial number’ and ‘Unique ID’. The latter illustrates the interest of this WG.

The particular challenge we identify is to agree on and introduce a common persistent identifier system for marine sensors and platforms within the marine community and at the same time agree on a core set of metadata elements which allow full compatibility with other communities.

Essential metadata

Property Occurrence Definition Datatype In metadata of
Identifier 1 The Identifier is a unique

string that identifies the instrument instance

PID IP
Inventory Number 0..1 The identifier registered in the owner institution’s device or asset catalogs or management systems String or PID
Local Name 0..1 The title of the instrument instance used within the institution e.g. ‘John’s CTD’’ String
Manufacturer 1 The manufacturer name String or PID
Manufacturer Identifier 0..1 The number/id given to the sensor product by the manufacturer.

Aka: manufacturer part number

Model Name 1 The model name given by the instrument’s manufacturer String
Serial Number 1 Serial number issued to the instrument instance by the manufacturer String
Instrument Category 0..n A category for the instrument such as ‘CTD’. Preferred PID is from the SDN vocabulary for instruments PID
Observable Property 0..n Aka: Measurable Property String