1 / 22

Mapping INSPIRE Legislation to SOS: OGC Standards Relationship

Explore the connection between SOS and INSPIRE legislation, INS NS Implementing Rules, and D2.9 Guidelines. Learn about OGC Sensor Observation Service and relevant standards, application domains, data models, and more. Understand how to map INSPIRE Implementing Rules to SOS Download Services and the concept overview of SOS in relation to O&M Guidelines. Dive into the specifics of mandatory and optional elements when accessing spatial datasets and spatial objects, including direct access downloads. Gain insights into INSPIRE D2.9 Guidelines and O&M Design Patterns for observational processes.

charde-deleon
Download Presentation

Mapping INSPIRE Legislation to SOS: OGC Standards Relationship

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Mapping between SOS standard specifications and INSPIRE legislation. Relationship between SOS and D2.9Matthes Rieke, Dr. Albert Remke(m.rieke, a.remke)@52north.org52°North GmbHWorkshop - INSPIRE Download service based on SOS8th April 2014, Joint Research Centre – European Commission

  2. Agenda • SOS and relevant standards • Mapping between INS NS Implementing Rules and SOS • 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 foraccessingdata • Pull based • Request ofmeasurementdata (mostlikelyas O&M) • Request ofsensororgeneralmetadata • Current IS version: 2.0 • Application Domains • Hydrology • Air quality • Weathermonitoring • Humansas Sensors

  5. Relevant Standards • ISO/OGC Observations & Measurements (O&M) • Data model + XML encoding • Whatforms a measurement? • Current IS version: 2.0 • ApplicationProfiles • WaterML 2.0 / GroundWaterML 2.0 • AQD e-Reporting Profile • OGC SensorML • Data model + XML encoding • Focus: describesensorandmeasurementprocesses • Current IS version: 2.0

  6. Mapping INSPIRE Implementing Rules to SOS

  7. Download Services as of INS NS • INSPIRE Network Services Regulation specifiesabstractconceptofDownload Service Pre-defined Dataset Download Direct Access Download

  8. Pre-defined Dataset Download - Mandatory • Get Download Service Metadata • Scope: informationaboutservice, itscapabilitiesandavailablespatialdatasets • SOS Request: GetCapabilities • SOS Response: extended SOS Capabilitiesdocument (including INSPIRE DS metadata) • GetSpatial Data Set • Scope: retrievalof a spatialdataset • Proposalfor TG update: spatialdataset = observationoffering • SOS Request: GetObservationusingobservationofferings (asprovided in thecapabilities) • SOS Response: setofobservationsencoded in a suitabledataformat (coveredlater)

  9. Pre-defined Dataset Download - Mandatory • DescribeSpatialDataset • Scope: retrievalofthedescriptionof all typesofspatialobjectsofthegivenspatialdataset • SOS Request: GetCapablities – all spatialdatasetsaredescribed in theresponse • SOS Response: capabilitiesresponsecontainingtheobservationofferings(= spatialdatasets) • Link Download Service • Not a direct SOS operation • Achieved by uploading Service metadata to an INSPIRE compliant discovery service (PublishMetadata)

  10. Pre-defined Dataset Download– Optional • GetSpatialObject • Scope: retrievalofa spatialobjectbased upon a query • Spatialobject = observation • SOS Request: GetObservationwith a setofqueryparameters (e.g. procedure, observedProperty, featureOfInterest), GetObservationByID • SOS Response: a setofobservationsencoded in a suitabledataformat (coveredlater) Link Download Service • Describe Spatial Object Type • Scope: retrievalofthedescriptionofthegivenspatialobjecttypes • SOS Request: GetCapabilities • SOS Response: Capabiltiescontainingthelistofobservationtypes (Contents section)

  11. 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 setofobservationsencoded in a suitabledataformat (coveredlater)

  12. Concept Overview

  13. SOS in relation to D2.9 - O&M Guidelines

  14. 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)

  15. 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

  16. 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

  17. 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-situanalyzation (after a sample or specimen was taken) • Sampling feature vs. sampled feature • FoI mostly provided as a samplingFeature • Lack of related Sampled Feature

  18. Procedure • SensorMLvsOM_INSPIRE_Process • SensorML has advantage: compliancy with wider SWE scope • A specific OM_INSPIRE_Process would allow lightweight procedure definitions

  19. 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

  20. 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 <Coverage> <domain>...encode domaininlinee.g. x, y, z, t axes .. </domain> <rangeType>...encode inline using swe:DataRecord </rangeType> <rangeSet>...xlinkto the file containing the values.. </rangeSet> </Coverage>

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

  22. 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

More Related