Skip to content
This repository has been archived by the owner on Oct 2, 2018. It is now read-only.

FOI Support

sensiasoft edited this page May 15, 2015 · 3 revisions

Some design decisions about FOI support in SensorHub.

Sensor/Data Producer API

Sensor and other data producers can send two types of FoI events:

  • NEW_FOI to notify that a new FoI is being targeted. The event can carry the feature description by reference or at least the feature ID, as well as the time at which the feature starts being observed.

  • END_FOI to notify that the FOI is not observed anymore.

Storage

NEW_FOI events typically trigger storage to save the Feature description (only simple feature supported for now) if it's the first time the feature has been seen. For next occurrences, only the feature ID is used to map to an existing feature.

The FoI ID is not included in each DataEvent (for efficiency) so the storage also has to prepare doing the necessary indexing on receiving the FoiEvent. All further measurements are to be associated with the latest FOI notified.

In PERST storage implementation, each FoI is associated to a list of time periods during which the FoI was observed.

SOS

FoI are also made available from the SOS service implementation:

A new FoI can be added through InsertSensor, InsertObservation or InsertResultTemplate request. In all 3 cases, the SOS implementation needs to be associated to a feature storage so that the feature description can be persisted.

Connection to SensorML

The current SensorML description will include only the last FOI being currently targeted by the sensor.

When generating a snapshot SensorML, the XML can include all the FOI targeted during the time period defined in validTime.

Clone this wiki locally