1. Darja Lihteneger, 25 - 26 November 2015, Copenhagen, Denmark INSPIRE Data Modelling for Reporting Data Flows – WISE SoE Monitoring Stations Eionet NRC Environmental Information Systems (EIS) Meeting 2015

2. Scope WFD and WISE freshwater and marine monitoring stations INSPIRE theme & application schema Mapping and extensions Lessons learnt Outline

3. Reporting obligations: several data flows WFD River Basin Management Plans reporting in 2016 – every 6 years (2010, 2016, 2022,...) WISE SoE (State of environment): nutrients, organic matter, hazardous substances, general physico- chemical parameters, etc. / covers fresh waters and marine waters Reporting under Regional Sea Conventions, e.g. HELCOM, OSPAR, others http://rod.eionet.europa.eu/obligations/715 http://cdr.eionet.europa.eu/help/WFD/WFD_521_2016/

4. Water/marine monitoring stations: data models WFD monitoring sites for surface and ground water bodies ? Common conceptual data model (UML) WISE SoE monitoring stations for freshwater and marine waters Regional Sea Conventions monitoring stations (HELCOM, OSPAR) – ICES stations dictionary INSPIRE Environmental monitoring facilities – general data model for monitoring stations 2-steps reporting: (1)Stations information > stations dictionary (2)Measurements observations, aggregated data at stations 6777 Eionet stations part of this: 1515 WFD stations

5. History of (some!) activities INSPIRE EF (general monitoring stations model): part of the Implementing Rules adopted in October 2013 / available: TG, UML data models, GL schemas, INSPIRE registry WFD – WISE SoE freshwater: data model of WFD monitoring sites is aligned with INSPIRE EF for the WFD RBMP reporting in 2016 and it is aligned with the WISE SoE reporting for freshwater Data model for WISE SoE marine monitoring stations and reporting is aligned with the WFD – SoE monitoring sites / prepared for the reporting in 2016 ICES marine station dictionary is under revision looking into better alignment with WISE SoE monitoring stations (supporting reporting in 2016) EEA project (2015-2016): approach to one common data model? Keep compliance!Common data model

6. Water/marine monitoring stations: one data model? INSPIRE EF Environmental Monitoring Facility – monitoring station WFD + WISE SoE freshwater + WISE SoE marine monitoring stations requirements: Point geometry Water body name: international (en) & national (language code) Codes of monitoring stations (international, national, Eionet) Management of changes in data Monitoring site purpose / type Other specific thematic attributes and code lists Superseding of monitoring sites Relationship between the WFD monitoring sites and WISE SoE monitoring stations Explicit reference to water bodies (1 or many) + = Compliant with ICES stations dictionary

7. INSPIRE data model extensions rules NOT ALLOWED! ALLOWED! CHECK with all requirements (IR, TG, GCM) and encoding rules (GML)

8. Concept: adding feature type + reusing INSPIRE concepts + adding thematic properties Change information: based on INSPIRE SU Evolution Type Name: INSPIRE GN – GeographicalName data type Codes of stations: INSPIRE base type thematic identifier Electronic object information: INSPIRE life cycle information + other thematic properties Added feature type

9. Concept: thematic constraints Thematic requirements Geometry is required: Geometry attribute is mandatory Point geometry is required Purpose of collection is required: Purpose could include one or many values [1..*] Additional business rules – thematic constraints are defined! Multiplicity of INSPIRE attributes cannot be changed! However, multiplicity is not in IR!

10. Concept: adding code lists – extending INSPIRE code lists http://inspire.ec.europa.eu/codelist/ EvolutionTypeValue/ http://inspire.ec.europa.eu/codelist/PurposeOf CollectionValue/ INSPIRE Extensibility: Empty code list Code list in EEA vocabulary

11. Concept: reference to water bodies (by thematic identifier) Monitoring site has to point to water body (one or several): Mst1 ---> A The water bodies are provided according to the INSPIRE AM applications schema. ? Open question -Using INSPIRE observing capability and feature of interest -Including a simple pointer / reference to water body (water body code – thematic identifier) Monitoring station Mst1 Water body A Water body B Lake X

12. Concept: INSPIRE monitoring station, observing capabilities and feature of interest Water body???

13. Concept: INSPIRE voidable attributes – not required by the reporting obligation Following INSPIRE requirements: provide voidable reason if data is not provided Data quality check of the reported data for the reporting obligations: will not exclude data that are provided according to INSPIRE but not required directly in the reporting obligation GML schema example:

14. Concept: packaging data packages Extended content Importing several INSPIRE application schemas (feature types, attributes, data types, code lists) New common application schema!

15. Lessons learnt INSPIRE EF EMF data model needs extensions to fit into the reporting obligation – proposed to use existing INSPIRE concepts: Lifecycle information Thematic identifier Management of changes – evolution type More information is needed: Coherent approach in referencing to other objects (spatial or non- spatial, INSPIRE or non-INSPIRE) is needed! Clear guidelines on extending INSPIRE code lists! More examples on encoding (in GML) of reflexive associations (links can exist between instances of the same class) Could INSPIRE EF EMF be updated?

16. Thanks Darja Lihteneger Thanks to project team – working hard on all issues! European Environment Agency