Pull Sample Clauses

Pull the SEDS Data Repository actively pulls data from the sensor data provider network. This can be done periodically or in (near) real‐time. Which mechanism, push or pull, to use depends very much on the capabilities that the sensor data provider network can provide. In the CITI‐SENSE project both mechanisms proved to be required to deploy. Geotech/AQMesh Pull Data provider provides an external FTP server on which datasets are stored. The Sensor Data Ingest service periodically harvests the data from this FTP server. AirMonitors Pull Data Provider provides an external FTP server on which datasets are stored. The Sensor Data Ingest service periodically harvests the data from this FTP server. SensApp Push Data Provider provides a web service that pushes data as SenML in a HTTP POST operation to the SEDS Platform. City Air Push Data Provider provides a web service that pushes data as XML in a HTTP POST operation to the SEDS Platform JSI Push Data Provider provides a web service that pushes data as XML in a HTTP POST operation to the SEDS Platform. CVUT Push Data Provider provides a web service that pushes data as JSON in a HTTP POST operation to the SEDS Platform. U‐▇▇▇▇▇▇ Push Data Provider provides a web service that pushes data as XML in a HTTP POST operation to the SEDS Platform. ▇▇▇/Atekne Push Data Provider provides a web service that pushes data as XML in a HTTP POST operation to the SEDS Platform. One of the key assumptions in the CITI‐SENSE SEDS Platform is that it should adopt 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 Web Feature Standard (WFS) is used. A WFS web service endpoint has been made available that allow sensor data providers to post their datasets against. Data tends to be modelled to meet a specific purpose, such as data ingestion, data storage and data publication. In the CITI‐SENSE Platform data plays a vital role for a variety of purposes. Instead of developing a generic, one‐size‐fits‐all, model that meets all the project's requirements is undesirable, a number specific data models have been developed and data translation processes ensure that data is exchanged between these models. One of the benefits of this de‐coupling of individual specific processes is that each process can be highly optimised to meets its purpose. Also, as each process may require a particular expertise and skill‐set, multiple team...