Sensor Data Ingest Clause Samples
Sensor Data Ingest. Once a sensor has been successfully registered in the CITI‐SENSE SEDS Platform, it can start ingesting sensor data. The SEDS Data Repository stores and manages the ingested sensor data in a centralised and structured way. Within the CITI‐SENSE project various sensor data providers are active. Many of them already have processes and technology in place that exchange data from their sensor network, however quite often these processes and technology are optimised to work only within their individual ecosystems. The challenge is to connect these disparate federated sensor networks to the single, centralised Data Repository. One of the cornerstones of the CITI‐SENSE SEDS Platform is the fact that it adopts Open Standards by default. This allows the CITI‐SENSE SEDS Platform to be interoperable, flexible and future‐proof. For ingesting sensor data into the SEDS Platform the ISO/OGC compliant, Web Feature Standard (WFS) is used. A WFS‐T, transactional web service endpoint is available and allows sensor data providers to post their datasets against. This can be done periodically or in real time. Two data ingestion web service patterns are identified:
Sensor Data Ingest. Once a sensor has been successfully registered in the CITI‐SENSE SEDS Platform, it can start feeding sensor data into the SEDS Platform. The SEDS Platform stores and manages the ingested sensor data in a centralised and structured way. Within the CITI‐SENSE project various sensor data providers are active. Many of them already have processes and technology in place that exchange data from their sensor network, however quite often these processes and technology are optimised to work only within this bounded ecosystem. The challenge is to connect these disparate federated sensor network ecosystems to the single, centralised Data Repository. There are two main mechanisms to ingest data from the sensor data provider networks into the SEDS Data Repository:
1. Push ‐ the sensor data provider network actively pushes data to the SEDS Data Repository. This can be done periodically or in (near) real‐time.