1. Eric Delory eric.delory@plocan.eu PLOCAN
Task 2.6
Eric Delory
PLOCAN
Partners: PLOCAN, MARUM, UPC, SLR, HCMR, 52°NORTH, IFM-GEOMAR, IFREMER, OGS
WP leaders: Please prepare
General Assembly 2017
Vilanova i la Geltrú, Spain; 27 – 29 June 2017

2. Core to T2.6: SensorML, a component of the SWE Standards suite
Current OGC Standards in the SWE framework are:
Observations & Measurements (O&M) –The general models and XML encodings for observations and measurements.
PUCK Protocol Standard – Defines a protocol to retrieve a SensorML description, sensor "driver" code, and other information from the device itself, thus enabling automatic sensor installation, configuration and operation.
Sensor Model Language (SensorML) – Standard models and XML Schema for describing the processes within sensor and observation processing systems.
Sensor Observation Service (SOS) – Open interface for a web service to obtain observations and sensor and platform descriptions from one or more sensors.
Sensor Planning Service (SPS) – An open interface for a web service by which a client can 1) determine the feasibility of collecting data from one or more sensors or models and 2) submit collection requests.
SWE Common Data Model – Defines low-level data models for exchanging sensor related data between nodes of the OGC® Sensor Web Enablement (SWE) framework.
SWE Service Model ­– Defines data types for common use across OGC Sensor Web Enablement (SWE) services. Five of these packages define operation request and response types.

3. Example of SWE Architecture
Sensor System

4. Objectives and outcomes of T2
Objectives and outcomes of T2.6: Eased and harmonised standard sensor description
Need: A tool for facilitating the creation of sensor and sensor platform descriptions
Approach
OGC SensorML 2.0 is an OGC standard for providing metadata about sensors and sensor systems
Currently in development: Marine Sensor Web Profile  define which elements of SensorML are relevant for marine sensors
Idea: Build an editor for SensorML  smle
Builds on ESONET development (SML 1.0) and integrates FixO3
Graphical user interface
Ensure that the users provide valid inputs

5. Objectives and outcomes of T2
Objectives and outcomes of T2.6: Eased and harmonised standard sensor description
smle has been completed in a first full version:
Linked to ESONET-FIxO3 yellow-pages for automated template generation (Task 2.5)
Sync with FixO3 Observatory credentials
Developed as a cooperation of FixO3 and NeXOS
Available as open source software:

6. If a user wants to create a new sensor description it is possible to select the type of the sensor from the Yellow Pages so that the description is initialised with the metadata that are common for all sensors of the selected type.

7. After selecting a sensor type, the user first gets a short description of the sensor to decide if this is the correct sensor type description.

8. Editing the contact information for the sensor.

9. Editing the classifiers describing a sensor.

10. Treeview showing the current content of the sensor description in a more compact way.

11. Remaining Activity Task partners to beta-test the tool
WP No – WP title
Task partners to beta-test the tool
Feedback to Github

12. T2.6 Legacy Open OGC-SWE SensorML editor
Sync-ed with FixO3 observatory credentials
Sync-ed ESONET-FixO3 Yellow Pages

13. Future for infra development
Train users create a standard inventory
Bind SOS services to FixO3 existing database
Demonstrate benefits to operators and users