Looking at the development during the past years, starting back in 2006, the OX-Framework (OWS Access Framework) was designed to be usable as a basis for Java applications providing easy access to all kinds of OGC Web Services. With the re-design of the OX-Framework to its current 1.12 version, we shifted the perspective of the OX-Framework more to a collection of API modules. These modules represent re-usable middleware components and focus on the interaction with Sensor Web services. Thereby, the OX-Framework still greatly facilitates the development of client as well as server applications. Today, 52°North’s latest SPS implementation, the SOS Importer and our various Sensor Web clients already utilize the OX-Framework 1.12.
The final sprint towards the end of the Google Summer of Code (GSoC) is over now. After fixing bugs, working on documentation and actually producing time-series in different formats, the “Exchangeable Encodings for SOS” project met most of its ambitious goals – and it is demonstrated on the 52°North Google summer of Code Demo Server. Users and developers documenation on the encoding mechanism has also found a place in the 52°North wiki.
We have integrated a plugin mechanism into an SOS server (source code branch), which is based on the main 52°North SOS development line (source code trunk). As a proof of the concept, two basic plugins are provided:
- Plain CSV (comma separated values) response format, which tries to stick to recommended NOAA IOOS Data Integration Framework CSV output,
- WaterML 2.0 (OGC WaterML 2.0 and Hydro DWG). I acquired a recent version of the WaterML 2.0 encoding profile, which is already adopted as a (candidate) standard. The schemas are not yet officially published and rumours have it that there might be last minute changes. The change request contains an extension regarding empty time-series responses which should not interfere with the existing implementation.
In the world of many diverse forms of observation types for natural phenomena, the two plugins demonstrated both rely on point-based measurement data.
Where to go from here?more >
Being at the FOSS4G conference in Denver, I just hold a presentation about our Thin SWE Client for the OGC Sensor Observation Service. The functionality of the client is focused on the display of time series data. This comprises a diagram view with comfortable navigation mechanisms (e.g. an overview time series, panning, zooming, etc.). In addition a table view showing all measured values belonging to a selected time series, as well as a map overview for displaying the sensor locations are included. This display functionality is complemented by further features like an export function (CSV, XLS and PDF export) and comfortable menus that help users to select the data they are interested in.
Besides giving the presentation (please find it below), I demonstrated the software successfully 🙂 If you are keen to see the application in action yourself, please visit our demo deployment.
I’m happy to announce that a comprehensive review article on the current design of the Sensor Web Enablement specification framework (‘SWE 2.0’) and on Sensor Web research in general has just been published by the journal ‘sensors’!
The article describes much of the work that has been developed within OGC’s SWE group in the past years and can now be seen under the umbrella of a ‘New Generation SWE’ (or SWE 2.0).