Presentation on theme: "Www.jrc.ec.europa.eu Serving society Stimulating innovation Supporting legislation Meeting on OGC Sensor Observation Service (SOS) for INSPIRE Michel Grothe,"— Presentation transcript:
www.jrc.ec.europa.eu Serving society Stimulating innovation Supporting legislation Meeting on OGC Sensor Observation Service (SOS) for INSPIRE Michel Grothe, Geonovum (NL)
Previous SOS experiences Scope: [Describe in which context you have been providing/consuming observation data through SOS and/or any other relevant SOS experience] Geonovum is not a INSPIRE data provider, but has experience with SOS for weather station data and is involved in INSPIRE air quality data project with RIVM. Delivered content: [Describe the kind of observation data you have provided/consumed - which thematic domain, but also what kind of observations (e.g. time series, point observations, profiles, trajectories, …)] Weather station data (Geonovum, KNMI) and air quality data (RIVM). Technologies / software used: [Describe the software products (servers and clients) you use for providing/consuming SOS] 52North SOS server and client software (Geonovum, RIVM). OpenLayers for a simple demonstrator (KNMI pilot in 2008) RIVM = National Institute for Public Health and the Environment KNMI = Royal Netherlands Meteorological Institute
Existing connections to INSPIRE Other download services available: [Describe if you are providing/consuming other observation-related services (WFS, Atom, …), e.g. for monitoring stations/networks or features of interest] RIVM will provide a WFS for (parts of) the data as well. For example on some stations offering data on water quality and on Air Quality. For Air Quality data like the zones will be offered through WFS. Information on the stations could be provided by WFS as well. KNMI provides INSPIRE compliant observation data through atom services and WMS. Observation data includes climate data series and near real-time weather data from our sensor network. Cross-reference of download services: [Describe if you are linking such services with SOS, and if so how] For RIVM still to be determined if and if so how to deal with this. KNMI has not linked the services yet. R&D on SOS services has been suspended since 2008 (due to inmaturity of the standards). The intention is to continue the research soon. Linking to SOS concerns near real- time weather data only.
Discussion: Why an INSPIRE/SOS? What would be the benefits of adding SOS as an additional option for implementing the INSPIRE download service is a good idea? SOS is designed and optimized for sensor data. Other types of download services like WFS might not fit very well on (some types of) sensor data. Interoperability between the services: ATOM feed is a (temporarily) work-around SOS is better suited to provide the sensor/measurement (meta)data. SOS offers the ability to select sensor data of interest (to the user).
Discussion: Technical issues We do not have (yet) technical issues to discuss. In the Netherlands there is limited experience with SOS. No operational systems exist. Experience is based on pilot projects. Most of these pilots were run some years ago (2008/2009) and worked with previous versions of OGC SOS. RIVM started working on SOS 2.0 for their air quality data (AQD IPR/INSPIRE). SOS is up and running, however data streams and data transformation are still work in progress (next workshop 7th of May).
Discussion: Download service TG options Do you see any problems (in terms of support in the MS) with defining yet another TG option (SOS in addition to Atom and WFS) for INSPIRE download services? In the Netherlands there is full support for OGC SOS. Several data providers see added value of OGC SOS for their INSPIRE sensor and temporal data. Not only from the domains of weather data and air quality data, but from water management perspective (FWD).
Discussion: Wish list Which features would you like to see in an INSPIRE download service for observation data? A more general remark: try to avoid defining extra non-standard requirements on top of existing specifications. Try to stay as close as possible to the base specification of SOS. This would make adoption a lot easier. Take into account the metadata XML overhead: describe what is minimal needed, not what might be needed (see complexity and overhead in SWE).
Additional information Please feel free to include any additional information to support the discussion (these will not be presented at the workshop, but shared with the other participants before the workshop and uploaded to the workshop page together with the minutes) Last week we started an open platform for sensor data in the Netherlands: “Making sense for Society; Living Lab for the Internet of Everything”. There was much interest in the use of OGC SOS and the new OGC SWE IoT standard. We expect that these two standards will be tested and adopted in several cases this year.