Guidelines for O&M in INSPIRE

1. Guidelines for O&M in INSPIRE

2. Overview • Goals • Thematic areas involved • Basic O&M design patterns • Common elements defined

3. Goals • Determine requirements for O&M within INSPIRE • Provide recommendations for • Observations on INSPIRE features • Referencing of observations from INSPIRE features • Use of elements of Sensor Web Enablement D2.9 Guidelines for the use of Observations & Measurements and Sensor Web Enablement-related standards in INSPIRE Annex II and III data specification development

4. Overview Thematic Areas • Geology (GE) • Oceanographic geographical features (OF) • Atmospheric conditions and Meteorological geographical features (AC-MF) • Environmental monitoring facilities (EF) • Soil (SO)

5. Other Thematic Areas • Area management/restriction/regulation zones and reporting units: Not mentioned but relevant for reporting • Land cover: Mentions observation date for LC type • Natural risk zones: Not in model, but use case states: "Monitoring data: • Type of monitoring instrumentation • Location of sampling measurements • Type and record of measurements" • Human Health: Health determinants • Production and industrial facilities: Not mentioned but relevant for E-PRTR • Statistical units & Population distribution, demography: StatisticalDataValue looks a bit like OM_Observation, SU would also make sense • Utility and governmental services: Statement "Non-geographic data (e.g. information on flow in m³/s) is also out of scope of this specification" • Habitats and biotopes & Species distribution: Observation Aggregation can be data source, no direct link to observations

12. Design Patters by Result Type • Result/Coverage-centric view • Coverages are “first class citizens” • Description of observation process metadata of result • Provide Observation information as metadata • MI_Metadata: acquisition source • OM_Observation • ObservingCapability • Observation-centric view • observations are “first-class citizens” • result ~ “metadata” • Use O&M

13. Observation refers to Feature • EnvironmentalFeatureReferenceClass • Can be used in the Observation Parameter

14. Grouping Observations • ObservationCollection Class

15. Feature of Interest • Often sampling features are defined without a sampled feature to put the feature in reference • Recommendation: provide sampled feature • High level sampling features: could be taken from the Sweet realms ontology

16. Procedure • Options: • INSPIRE_OM_Process • SensorML

17. Procedure - Process Parameters • Observation can carry parameters • Define which parameters in INSPIRE_OM_Process • “Informal” constraint that all Observation parameters should be specified as process parameters in the procedure Note: not formal constraint because would modify O&M

18. Procedure - Process Parameters • Results of related "observations": • water hardness of river • width of river at measurement point • Temporal information • Analysis Time • Forecast period • Instrument settings • sampling rate • minimum & maximum offset • Ensemble Member

19. Observed Property • Complex Properties required

20. Result Encoding • Allow for industry standards for result encoding • i.e. NetCDF, SEG-Y, LAS, WITSML • Result should include basic information on type of external result + link to result • Use design pattern from CSML

21. Observing Capability Requirement to attach information on measurements to a feature • Class ObservingCapability Provide information on • What • Where • How

22. Observing Capability

23. Referencing Observations from INSPIRE Features I

24. Referencing Observations from INSPIRE Features II

25. Data Provision • Recommendation to include Sensor Observation Service for Download Service • Strong recommendation for Registers/Registries/Codelists