GEOSS Banner

Section 3: Use Cases of the Sensor Observation Service

<<Prev T.O.C Next>>


3.1 Publishing Sensors and Sensor Data

3.1.1 Introduction of Use Case

This use case is mainly relevant for software developers that want to interface between data acquisition systems and OGC Sensor Observation Service (SOS) servers. It focuses on the standards based publication of sensors and sensor data which can for example be executed by software components.

3.1.2 Description of Use Case

A typical scenario of this use case is that a developer wants to forward the output of a sensor directly into a SOS server. In this case the developer will register first his sensor at the SOS and provide within this registration message all relevant metadata about the sensor. This is a one-time operation which is only executed once per sensor.

Afterwards the sensor is known within the SOS, the developer can start to push new observation data from the sensor into the SOS. Each time the SOS receives a new observation it is automatically put into the SOS database so that it can be queried by users of the SOS.

3.1.3 References to Relevant Tutorial Sections

A description how this use case can be implemented is provided in section 4.3.1.

3.2 Publishing Legacy Datasets Using an Import Tools

3.2.1 Introduction of Use Case

This use case addresses a way how existing sensor data sets (available as comma-separated values (CSV) files) can be imported into OGC Sensor Observation Service (SOS) servers. In this tutorial an approach is shown how an import tool can be used to hide the specifics of the SOS interface from users in order to make the publication of sensor data easier.

3.2.2 Description of Use Case

A typical scenario for this use case is a researcher who wants to publish sensor data through a SOS. On the one hand he might want to make it accessible to other researchers in a commonly understandable way. On the other hand he could be interested to make his data accessible through the SOS interface in order to open it with SOS clients and to benefit from existing analysis and visualisation functionality. Usually one can expect that the user in this case is a domain expert and not a person who has in-depth knowledge of the SOS standard. Thus, it is necessary to provide a tool which allows the expert to describe the structure of the data set without dealing with the details of the SOS requests and responses. This tutorial introduces a tool that is capable of facilitating such an import of sensor data archives into SOS servers.

3.2.3 References to Relevant Tutorial Sections

A description how this use case can be implemented is provided in section 4.3.2.

<<Prev T.O.C Next>>

Tag
none

Files (0)

 
You must login to post a comment.