Christian Ansorge 28 th March 2017 Ghent Environmental

Christian Ansorge 28 th March 2017, Ghent Environmental Reporting reusing INSPIRE Linked Approach & CDDA 2018 EU Registry

Reportnet – EEA view Deliveries per day

Data reporting – Reporters view Link to presentation by J. Melles

Reporting obligation Reporting obligation INSPIRE Directive Reporting obligations Legally mandated organisation

INSPIRE and Reporting concept – basic assumptions: Future • MS shall provide data in the scope of INSPIRE (harmonized, interoperable, via network services) by 2020 latest. • Data provided under INSPIRE shall be reused and MS aim to avoid multiple provision of data. • For better support of environmental policies more direct, frequent and timely access to the environmental data is needed • e. Reporting concept should be a pragmatic, generic and reusable design • Minimun demands on provider as well as on consumer side

INSPIRE and Reporting • Strategy paper: – „The future of e. Reporting and the link to INSPIRE“ – Data Typology as one main element Future Current reporting obligations Type 1 Geospatial reference data Type 2 Environmental data Type 3 Textual or contextual data and information

INSPIRE and Reporting Data typology in practice (more on that in the ”CDDA follow-up”) 7

INSPIRE and Reporting EU Registry data model 8

INSPIRE and Reporting concept to be developed: Present • Need for a systematic approach towards e. Reporting • More coherent and streamlined • Reduce fragmentation of approaches and technical solutions

INSPIRE and Reporting • 3 possible Reporting & Extension approaches – Integration • Multiple INSPIRE Themes (Type 1) and environmental data (Type 2) in one ”super schema” • E. g. Air Quality e. Reporting – Extension • Singular INSPIRE Theme (Type 1) is extended by environmental data (Type 2) • E. g. EU Registry comes later – Linking (”Linked Approach”) • Environmental data (Type 2) is pointing towards multiple INSPIRE Themes but provided seperately • E. g. CDDA 2018 comes later

INSPIRE and Reporting Questions so far. . more is coming! *WFS harvesting will come later

INSPIRE and e. Reporting Linked Approach and CDDA 2018

Linked Approach and CDDA 2018 CDDA • Common Database on Designated Areas • Nationally designated protected areas (e. g. nature reserve, national parks, etc. ) • EIONET core data flow • Not part of the environmental legislation • Rather simple data model

LINKED APPROACH Two ways of re-using INSPIRE models (general application) Alternative A via (INSPIRE compliant) file INSPIRE model • Geometry and core elements • GML file common identifier Tabular data Upload as package (without elements included in the INSPIRE data models) Reportnet CDR Alternative B via INSPIRE download service (WFS) • • INSPIRE model Geometry and core elements Web feature service link common identifier Tabular data (without elements included in the INSPIRE data models) Step 2 – Harvest gml file from INSPIRE web service Step 1 - Upload

Current reporting approach in CDDA Geometry (Shapefiles) common identifier Tabular data (XML/MS Access files) Upload as package Reportnet CDR CDDA 2018 approach re-using INSPIRE Protected Sites Tabular data INSPIRE model Protected Sites (GML file) • Geometry and core elements • • • CDDA match Geometry of site Site name Designation date Designation type IUCN category common identifier (XML/XLS files) • Elements NOT included in the INSPIRE data models CDDA Designated Area • Various IDs • Designated area type • Official area (ha) • Major ecosystem type • Marine percentage • Metadata fields Upload as package Reportnet CDR

Linked Approach and CDDA 2018 Type 1 Type 2 Dataset level Protected Site 1 Designation A Object level Protected Site 2 Designation B Designation C

Linked Approach and CDDA 2018 Type 1 data Link – Dataset level (file or WFS) Link – Record level (Inspire. ID) Type 2 data

Linked Approach and CDDA 2018 CDDA ’ 18 roadmap • • • April 2017 - Webinar with EIONET NRCs (INSPIRE PS experts are welcome as well) June 2017 – Consultation on the draft reporting guidelines for CDDA & NRC biodiversity workshop at EEA July – September 2017 - Testing phase with interested countries October 2017 - Final reporting guidelines December 2017 - Call for 2018 data collection March 2018 – Reporting deadline for CDDA reporting • • Additional webinars on request (e. g. on data transformation using HALE) WFS harvesting tests decoupled from the official reporting •

Linked Approach and CDDA 2018 Web service harvesting for reporting • • • EEA not ready to accept data from web-services for obligatory reporting right now EEA Reportnet undergoes major update project ( Reportnet 2. 0, 2017 -2019) Reporting via web-services is legally/procedurally challenging 1. Within CDDA ‘ 18 we will ask countries to provides us with WFS nodes (in parallel) if available for testing 2. 2018 EEA will analyze the web-service reporting together with EIONET a) b) c) d) Technical and legal challenges needs to be addressed Business case has to be analyzed & implementation plan developed INSPIRE requirements as input to Reportnet 2. 0 project EEA to plan activities to operationalize the conclusions in a development activity 3. 2020 as target to be ready for web service based reporting for agreed data flows

Linked Approach & Next steps? Commonalities in protected sites reporting data * presented on Nature reporting expert group, March 2017, by EEA (Mette Lund) • • Natura 2000 data flow CDDA data flow geometry site name designation date designation type

Linked Approach and CDDA 2018 Questions so far. . more is coming!

Linked Approach and CDDA 2018 EU Registry on industrial emissions (thanks to Daniel Montalvo, EEA & Mark Gibbs, Aether)

The overarching picture Slide 23

Objectives of the project 1. To simplify and clarify industrial emissions reporting, reducing the administrative burden where possible 2. To provide a robust reporting structure for the EU Registry and for thematic information 3. To generate a coherent and consistent EU dataset 4. To comply with INSPIRE – ensuring countries’ investments are useful for their own compliance 5. To provide sound guidance to member states 6. To establish an integrated reporting channel for LCP and E-PRTR emissions data that references the EU Registry. Slide 24

Project overview: In addition, the EU Registry will act as a reference dataset to which thematic data reporting would refer to. This webinar details the development of the EU Registry data model which facilitates the process highlighted with the red box. Industrial pollution data flows Member states Administrative data Public EEA EU Registry (all industrial sites) EU Registry On Industrial Sites Crosslinked databases The EU Registry on Industrial Sites is planned to centralise the collection of identification and administrative data for: • E-PRTR facilities • IED installations • Large combustion plants (LCPs) • Waste incineration plants (WI) Internal Systems E-PRTR & LCP Data Thematic data E-PRTR facility and emissions data LCP installation part and emissions data 2

Definitions and legislative basis: The EU Registry on Industrial Sites data model needs to ensure: • Consistency with the underlying legislation (2006 E-PRTR Regulation and 2010 IED) • Compliance with INSPIRE guidance (D 2. 8. III. 8 Data Specification on Production and Industrial Facilities – Technical Guidelines) • Reporting requirements are simplified wherever possible • Term INSPIRE E-PRTR IED Site ‘A Production Site represents the geographical location of the facility or a piece of land where the facility was, is, or is intended to be located. ’ ‘Site means the geographical location of the facility. ’ No definition Facility ‘A Facility represents something designed, built, installed to serve a specific function, comprehending the complete equipment or apparatus for a particular process or operation. A facility groups together one or more installations that are operated on the same site by the same natural or legal person’ ‘Facility’ means one or more installations on the same site that are operated by the same natural or legal person. ’ No definition Installation ‘A Production Installation represents something installed, such as machinery, an apparatus, a device, a system, or a piece of equipment placed in position or connected for use. ’ ‘Installation means a stationary technical unit where one or more activities listed in Annex I [of the EPRTR] are carried out, and any other directly associated activities which have a technical connection with the activities carried out on that site and which could have an effect on emissions and pollution’ ‘Installation means a stationary technical unit within which one or more activities listed in Annex I or in Part 1 of Annex VII [of the IED] are carried out, and any other directly associated activities on the same site which have a technical connection with the activities listed in those Annexes and which could have an effect on emissions and pollution’ Installation Part ‘A Production Installation Part represents a specific technical part of the installation, developing a representative functionality that should be registered under the legislation. ’ No definition Equivalent to: ‘combustion plant’ (Article 3 [25]) ‘waste incineration plant’ (Article 3 [40]) ‘waste co-incineration plant’ (Article 3 [41]) MS views are taken into account properly The underlying legislation has differences in scope. These differences must be considered in order to provide a coherent data structure. 3

Removing unnecessary feature types: INSPIRE PF UML overview, with nonessential feature types highlighted for removal <Voidable> • The feature types: • Production plot • Production building • Building base <Voidable> were identified as non-essential to the EU Registry data model. These are highlighted by using yellow boxes in the diagram to the right. As these are ‘voidable’ according to INSPIRE guidance, these feature types can be removed in their entirety. <Voidable> 7

Adding extensions: • For the purposes of visualisation the diagram to the right is simplified to show only the feature types of the INSPIRE PF UML • In addition, the INSPIRE ‘activity complex’ has been added, of which a Production Facility is a subtype • To adapt the INSPIRE PF schema for the purposes of the EU Registry, multiple extensions can be added. • This enables additional fields to be added to feature types. INSPIRE PF UML overview with feature types simplified Report data Productio n site Activity complex Production facility Productio n Installatio n Production Installation part Productio n site extension Production facility extension Production installation part extension 8

Final streamlined view: • • Once all extensions and INSPIRE feature types have been combined a final streamlined view is produced This represents the format and structure in which data will be required to be transmitted from member states to the EEA «feature Type» Report. Data Streamlined view of the data model + country. ID: Country. Code. Value + reporting. Year: Year - From INSPIRE PF - Added by extension Production. Site «feature Type» Production. Site + inspire. Id: Identifier + Location: GM_Point + confidentiality: Confidentiality «voidable» + name: Character. String [0. . *] Constraints {nameis. Mandatory. And. One} «feature Type» Production. Facility Production. Facility + competent. Authority. EPRTR: Competent. Authority [0. . 1] + confidentiality: Confidentiality + dateof. Start. Of. Operation: Date + EPRTRAnnex. IActivity: EPRTRAnnex. IActivity. Type + name. Of. Owner: Character. String + river. Basin. District: River. Basin. District. Value [0. . 1] + inspire. Id: Identifier + function: Function [1. . *] + geometry: GM_Object «voidable» + owner. URL: any. URL [0. . 1] + remarks: Character. String [0. . *] + number. Of. Installations: Integer + status: Status. Type [1. . *] + address: Adress. Details + name: Character. String [0. . 1] Constraints {one. Hosting. Site} {geometry. Is. Kind. Of. GM_Point} {only. One. Status. And. Not. Void} {name. Is. Mandatory. And. One} Production. Installatio «feature Type» n Production. Installation <Voidable> + baseline. Report. Article 22: Boolean + bat. Article 15 -4: Boolean + competent. Authority. Permits: Competent. Authority [0. . *] + competent. Authority. Inspections: Competent. Authority [0. . *] + confidentiality: Confidentiality + date. Of. Start. Of. Operation: Date + Inspections: Integer + other. Relevant. Chapters: Relevant. Chapter. Value [0. . *] + permits: Permit. Details + IEDAnnex. IActivity: IEDAnnex. IActivity. Type + inspire. Id: Identifier + point. Geometry: GM_Point [0. . 1] «voidable» + espir. Id: Character. String [0. . *] + ets. Id: Character. String [0. . *] + name: Character. String [0. . *] + status: Status. Type [1. . *] Constraints {only. One. Status. And. Not. Void} {name. Is. Mandatory. And. One} {point. Geometry. Is. Mandatory} Production. Installation. Part «feature Type» Production. Installation <Voidable> + plant. Type: Plant. Type. Value + confidentiality: Confidentiality + date. Of. Start. Of. Operation: Date + derogations: Derogation. Value [0. . *] + nominal. Capacity: Capacity. SIWI [0. . 1] + specific. Conditions: Article 51 Value [0. . *] + MWth: Integer [0. . 1] + inspire. Id: Identifier + point. Geometry: GM_Point [0. . 1] «voidable» + name: Character. String [0. . *] + status: Status. Type [1. . *] Constraints {only. One. Status. And. Not. Void} {name. Is. Mandatory. And. One} {point. Geometry. Is. Mandatory} 12

Next steps for data model • Member state consultation was running till 24 th March – preliminary view on the feedback • Final approval will be communicated by DG ENV in early April 2017 • Member states can then begin their IT development/integration Slide 30

Next steps for the project • Member states will next be consulted on: – QA/QC procedures for the EU Registry – Guidance for the EU Registry – The E-PRTR/LCP Data Model • Please engage in testing of the EU Registry in October this year • See project plan for more details Slide 31

EU Registry on industrial emissions Questions. . the end is close!

Thanks Christian Ansorge European Environment Agency