Mapping between SOS standard specifications and INSPIRE legislation. Relationship between SOS and D2.9 Matthes Rieke, Dr. Albert Remke (m.rieke, 52°North GmbH Workshop - INSPIRE Download service based on SOS 8 th April 2014, Joint Research Centre – European Commission

2 Agenda 1.SOS and relevant standards 2.Mapping between INS NS Implementing Rules and SOS 3.SOS in relation to D2.9 O&M Guidelines

3 OGC SENSOR OBSERVATION SERVICE AND RELEVANT STANDARDS

4 Relevant Standards OGC Sensor Observation Service (SOS) –Interface for accessing data –Pull based –Request of measurement data (most likely as O&M) –Request of sensor or general metadata –Current IS version: 2.0 Application Domains –Hydrology –Air quality –Weather monitoring –Humans as Sensors

5 Relevant Standards ISO/OGC Observations & Measurements (O&M) –Data model + XML encoding –What forms a measurement? –Current IS version: 2.0 –Application Profiles WaterML 2.0 / GroundWaterML 2.0 AQD e-Reporting Profile OGC SensorML –Data model + XML encoding –Focus: describe sensor and measurement processes –Current IS version: 2.0

6 Notes (hidden) SOS Interface Standard is independent from the underlying O&M dialect (e.g. AQD) –Encodings can be listed in the capabilities Need an offering? Yes, as this is the “spatial data set”

7 MAPPING INSPIRE IMPLEMENTING RULES TO SOS

8 Direct Access Download Pre-defined Dataset Download Download Services as of INS NS INSPIRE Network Services Regulation specifies abstract concept of Download Service Mandatory Get Download Service Metadata Get Spatial Dataset Describe Spatial Dataset Link Download Service Optional Get Spatial Object Describe Spatial Object Type Additional Search capabilities: Spatial Dataset URI Attributes Bounding Box

9 Pre-defined Dataset Download - Mandatory Get Download Service Metadata –Scope: information about service, its capabilities and available spatial datasets –SOS Request: GetCapabilities –SOS Response: extended SOS Capabilities document (including INSPIRE DS metadata) Get Spatial Data Set –Scope: retrieval of a spatial dataset –Proposal for TG update: spatial dataset = observation offering –SOS Request: GetObservation using observation offerings (as provided in the capabilities) –SOS Response: set of observations encoded in a suitable data format (covered later)

10 Pre-defined Dataset Download - Mandatory Describe Spatial Dataset –Scope: retrieval of the description of all types of spatial objects of the given spatial dataset –SOS Request: GetCapablities – all spatial datasets are described in the response –SOS Response: capabilities response containing the observation offerings (= spatial datasets) Link Download Service –Not a direct SOS operation –Achieved by uploading Service metadata to an INSPIRE compliant discovery service (PublishMetadata)

11 Pre-defined Dataset Download – Optional Get Spatial Object –Scope: retrieval of a spatial object based upon a query –Spatial object = observation –SOS Request: GetObservation with a set of query parameters (e.g. procedure, observedProperty, featureOfInterest), GetObservationByID –SOS Response: a set of observations encoded in a suitable data format (covered later) Link Download Service Describe Spatial Object Type –Scope: retrieval of the description of the given spatial object types –SOS Request: GetCapabilities –SOS Response: Capabilties containing the list of observation types (Contents section)

12 Direct Access Download Get Spatial Object with Search Criteria –Scope: subsetting of a spatial dataset using Attributes (URI of object, temporal dimension) Bounding Box –SOS Request: GetObservation with query parameters: Observed property Feature of interest Procedure Spatial filter (bounding box) Temporal filter Additional: GetObservationByID –SOS Response: a set of observations encoded in a suitable data format (covered later)

13 Concept Overview INS NS Spatial DatasetSpatial Object Spatial Object Type SOS Observation Offering Observation Observation Type

14 SOS IN RELATION TO D2.9 - O&M GUIDELINES

15 SOS IS 2.0 and O&M SOS Requirement Class ‘Core’: “…O&M v2.0 XML encoding (OMXML 2.0) is the only mandatory format for observation data…” –Every SOS 2.0 implementation must provide data encoded as O&M 2.0 –Other encodings are possible, but require specification work (e.g. as an extension document for SOS IS 2.0)

16 INSPIRE D2.9 Guidelines D2.9 Guidelines for the use of Observations & Measurements and Sensor Web Enablement-related standards in INSPIRE Annex II and III data specification development (state: 1.0) Relevant identified INSPIRE themes –Geology –Oceanographic geographical features –Atmospheric conditions and Meteorological geographical features –Environmental monitoring facilities –Soil

17 INSPIRE O&M Design Patterns No custom specialization (= Profile) for INSPIRE But: requirements for further on observational process within the observation (not only the procedure) –Use “parameter” attribute for KVP-encoded information Requirement for collection of observations –No structural element like in O&M 1.0 (ObservationCollection) –Atmospheric conditions –Oceanographic features –Recommendation: Re-introduce a collection class

18 Feature of Interest INSPIRE relevant types of features –Feature of Interest Station/Location sampling point –Feature of Interest Trajectory: sampling curve –Feature of Interest Extensive Feature sampling surface –Feature of Interest Sample/Specimen Ex-situ analyzation (after a sample or specimen was taken) Sampling feature vs. sampled feature –FoI mostly provided as a samplingFeature Lack of related Sampled Feature

19 Procedure SensorML vs OM_INSPIRE_Process –SensorML has advantage: compliancy with wider SWE scope –A specific OM_INSPIRE_Process would allow lightweight procedure definitions

20 Observed Property Pure O&M: simple phenomenon stored in an observedProperty –Additional information to be defined in the procedure Domain users expect additional information –E.g. averaging period, precipitation types –  proposal for complex properties to be used within INSPIRE

21 Observation Result Result encoding options –SWE Common types –GML coverages –sufficient?  Allow well-established industry standards (NetCDF, SEQ-Y, LAS, …) in the result –Include via XML metadata and xlink...encode domain inline e.g. x, y, z, t axes.....encode inline using swe:DataRecord...xlink to the file containing the values..

22 Data Specifications INSPIRE Data specifications already considering O&M –Environmental Monitoring Facilities –Geology –Atmospheric Conditions and Meteorological Geographical Features –…

23 Provision of O&M encoded data It is possible to serve the various O&M related classes via OGC services –WFS –WCS Not very convenient for time series data  D2.9 explicitly recommends to include the SOS 2.0 into the Network Services Guidance