Streamlining of Reporting on Industral Emissions Ian:

Extension of INSPIRE PF requirements The final Reporting workflows Overview Background Project Overview Extension of INSPIRE PF requirements The final Reporting workflows Next Steps Questions? Ian:

Background Ian:

Greenhouse gas inventory Background: Why initiate this process? Many datasets on the various facets of environment pressures from industry Inventory on Large Combustion Plants Annual EU Greenhouse gas inventory Ian:

Background: Main Drivers Why the integration of reporting? European Commission decision in 2014 E-PRTR and LCP fit well together – good starting point Immediate QA/QC cross-checks can improve data quality Reduce the cost of data management and review, both for data providers and the EEA Address key problems: Different identifiers assigned for different reporting requirements Different rules on handling changes over time (splits, mergers, etc.) Duplications and inconsistencies Reduce reporting burden Ian:

Background: Key objectives To simplify and clarify industrial emissions reporting, reducing the administrative burden where possible Provide a robust reporting structure for the EU Registry on Industrial Sites and for thematic (emissions) information Establish integrated reporting channel for E-PRTR and LCP emissions data Develop a coherent view of reporting facilities Generate consistent & reliable EU thematic datasets Comply with INSPIRE requirements Ian:

Project Overview Ian:

Project overview Harry: Harry to discuss the overview diagram, highlighting the intention of the EEA to create public data products.

EU Registry geographical hierarchy: Site 1 Site INSPIRE ID Facility 1 Facility INSPIRE ID Facility 2 Facility INSPIRE ID :E-PRTR+LCP INSPIRE connectivity Installation 1 Installation INSPIRE ID Facility INSPIRE ID E-PRTR thematic data reported at this level Installation Part 1 Installation Part INSPIRE ID Harry: to mention Geographical hierarchy, and INSPIRE connectivity LCP thematic data reported at this level Installation Part INSPIRE ID

Extension of INSPIRE PF Requirements Ian:

Correlation: EU Registry INSPIRE E-PRTR IED ProductionSite Correlation No definition provided ProductionFacility ProductionInstallation ProductionInstallationPart Harry: Harry to highlight the cross analysis of entity definitions within the fundamental legal instruments. Harry to mention the good alignment with the INSPIRE PF, and the benefit that this structure is INSPIRE compliant.

Production Facilities (PF) and INSPIRE: PF Data Specification Harry: Harry to discuss how the fundamental PF structure is not solely fit for purpose despite good alignment.

Extending the INSPIRE data model: Data modelling exercise: Removed unnecessary feature types Added extensions to include fields specific to the reporting legislation INSPIRE PF UML overview with feature types simplified Harry: Harry to discuss the INSPIRE extensions

Production Installation extension Populating Extensions Each extension requires new fields to be defined Certain fields were derived to collect key information defined in the 2006 E-PRTR Regulation and the 2010 Industrial Emissions Directive In addition, by considering information critical to the data flow and the QA/QC of data, other fields were defined. Constraints are added to make certain attributes mandatory Detailed view Simplified view Production Installation extension

EU Registry: Final streamlined view Harry: Harry to discuss streamlined view, the fundamental view of the EU Registry which clearly displays the geographical hierarchy.

Compliant GML generated by MS The workflow: XML or Access Route 1 Member state internal systems Compliant GML generated by MS Uploaded to Central data repository Route 2 Member state internal systems Access database template EEA Conversion service Harry: Harry to discuss the two reporting routes and how these reflect differences in MS. Uploaded to Central data repository Compliant GML

Next Steps Ian:

EEA Hosted Conversion Service for Access Files

EU Registry Now Open for Testing by Reporters

Currently Under Development…….. Harry: Harry to discuss the overview diagram, highlighting the intention of the EEA to create public data products.

Testing EU Registry – from November 2017 Next steps Additional GML validation step to be introduced to supplement XML validation Testing EU Registry – from November 2017 Ongoing development of thematic reporting elements Legal Basis required to support the collection of some data fields which are not currently mandatory. Ian

Dr. Ian Marnane Project manager - Industrial pollution Contact details Dr. Ian Marnane Project manager - Industrial pollution                  ian.marnane@eea.europa.eu Phone: +45 3336 7228 Ian