Presentation is loading. Please wait.

Presentation is loading. Please wait.

Data specifications and e-Reporting for the E1b data flow

Published byJulianna Roberts Modified over 6 years ago

Similar presentations

Presentation on theme: "Data specifications and e-Reporting for the E1b data flow"— Presentation transcript:

1 Data specifications and e-Reporting for the E1b data flow
EEA-ETC/ACM | of November 2017| 3rd IPR Technical meeting, Copenhagen Data specifications and e-Reporting for the E1b data flow Modelled data and objective estimation

2 Agenda Recap on reporting models & objective estimation information
How to report model & objective estimation methods & data It’s not the same as fixed & indicative measurements Describing your method / technique Reporting your observed / predicted data Revised framework of model configuration flags Plans for handling multiple file formats Examples

3 Recap on using models & objective estimation
Modelled & objective estimation are forms of supplementary assessment data as set out by Articles 6, 7 and 10 of 2008/50/EC Article 4 of 2004/107/EC Guidelines on usage To supplement high quality fixed measurements To improve the spatial coverage of assessments Use as a sole source of information when levels are generally lower & can be assessed using methods with a greater uncertainty budget To support AQ Plans preparation e.g. source apportionment & evaluation senarios

4 Model & objective estimation types
Predictions along a vector / trajectories Roads Railways Rivers Predictions on a regular / irregular grid Raster / gridded data Receptor locations Predictions at a point / polygon Receptor modelling Hot spot modelling Expert judgement Historical trends & emissions inventory analysis Shared / combined measurement time-series NS & WSS contributions

5 Reporting model & objective estimation data
If you are reporting models or objective estimation PLEASE DO NOT report in the D & E1a data flows, these data flows are reserved for fixed & indicative measurements Description of assessment method / metadata delivered in D Modelled & objective estimation observational data / predictions delivered in E1a D data flow E1a data flow

6 Reporting model & objective estimation data
If you are reporting models or objective estimation i.e. anything other than fixed or indicative measurements, you must report with the framework below Description of assessment method / metadata delivered in D1b Modelled & objective estimation observational data / predictions delivered in E1b D1b data flow E1b data flow

7 Reporting model & objective estimation descriptions
D1b for models D1b for objective estimation High-level description of the model in the AQD_Model class Simple description of model domain in the AQD_ModelArea class e.g. a bounding box or point location Summary information on model configuration in the AQD_ModelProcess class using flags to indicate important model inputs & citations to external report(s) on model set-up Simplified high-level description of the model in the AQD_Model class Simple description of model domain in the AQD_ModelArea class e.g. a bounding box or point location Simplified summary information on model configuration in the AQD_ModelProcess class – level of information is more descriptive & can make heavy use of citations of external report(s) on method

8 New guidelines for reporting & benefits
D1b provides a high-level description of how the model has been configured E1b provides the actual configuration information & results Emissions inventory used Meteorology used Chemistry used Interpolation technique used etc. Emissions inventory version Meteorology year Chemistry scheme Interpolation technique e.g. bilinear Data encoding & data formats New guidance on reporting model configuration D1b can be static Reusable for many years Less updating for countries Parameters that will change the results, travel with the results E1b is by definition dynamic & generally needs updating each year

9 Example model configuration - emissions
<ompr:processParameter> <ompr:ProcessParameter> <ompr:name xlink:href=" <ompr:description>The emissions inventory used to configure the model including as appropriate the year, version and summary of post processing required</ompr:description> </ompr:ProcessParameter> </ompr:processParameter> D1b declaration <om:parameter> <om:NameValue> <om:name xlink:href=" <om:value> NAEI2011 data, scaled forward to 2012 by linear interpolation between 2011 and projected (UEP45) 2012 data </om:value> </om:NameValue> </om:parameter> E1b definition

10 Example model configuration - meteorology
<ompr:processParameter> <ompr:ProcessParameter> <ompr:name xlink:href=" <ompr:description>A description of the meteorological dataset used to configure the model including name, year, version and citation (as appropriate)</ompr:description> </ompr:ProcessParameter> </ompr:processParameter> D1b declaration <om:parameter> <om:NameValue> <om:name xlink:href=" <om:value> Waddington met station for 2012 (data acquired from the Met Office). Other met sites may be used for more detailed modelling studies where the national scale modelling/monitoring highlights potential problems</om:value> </om:NameValue> </om:parameter> E1b definition

11 Handling multiple data types
Multiple possible data types are numerous Conceptual data types we can expect Regular grids Irregular grids Points Polygons Vector / trajectory data 3-dimensional arrays Multiple possible data formats are numerous

12 Handling multiple data formats
Focus on familiar, common external encoding formats for 2017 Vectors / trajectories External - Shapefile Inline - GML Regular / irregular grids External – ascii-grid, GeoTiff, NetCDF, WCS Inline – GML Coverage Points / Polygons External – Shapefile Inline – SWE array Remote measurements E1a ESRI shapefile (points, line & polygons) ASCII GRID for regular grids GeoTiff for regular grids SWE data array for simple cases Possible to extend to inline encodings - GML coverage, NetCDF, WCS etc. in the future (not a priority for 2017).

13 Encoding in the E1b XML deliverable
Very similar to E1a reporting E1a framework has been extended using model specific content flags via the om:parameter class om:parameter is used to define important content e.g. model inputs data, configuration, result location etc. This framework supports data harvesting needs & QA checks

14 Encoding in the E1b XML deliverable
Result encoding / location flags <om:parameter> <om:NamedValue> <om:name xlink:href=" <om:value xlink:href=" </om:NamedValue> </om:parameter> <om:name xlink:href=" <om:value xlink:href="

15 Encoding in the E1b XML deliverable
Result file format flags <om:parameter> <om:NamedValue> <om:name xlink:href=" "/> <om:value xlink:href=" </om:NamedValue> </om:parameter> <om:value xlink:href="

16 Encoding in the E1b XML deliverable
External result file declaration <gml:File> <gml:rangeParameters> <swe:Quantity definition=" <swe:label>annual mean</swe:label> <swe:description>annual mean at background locations on a 1x1km regular grid</swe:description> <swe:uom xlink:href=" </swe:Quantity> </gml:rangeParameters> <gml:fileReference> rence> <gml:compression >LZ77</gml:compression> /gml:File>

17 Encoding in the E1b XML deliverable
Inline SWE data array results for expert judgement or objective estimation results Single SWE record for whole domain provide in E1b <om:result> <swe:DataArray> … <swe:encoding> <swe:TextEncoding decimalSeparator="." tokenSeparator="," </swe:encoding> </swe:DataArray> </om:result> Model/method descriptor provided in D1b (AQD_Model) Model/method domain described in D1b (AQD_ModelArea) Model/method configuration described in D1b (AQD_ModelProcess)

18 Encoding in the E1b XML deliverable
Don’t forget your spatial reference system information Where the external file is in a proprietary or open GIS file format e.g. Shapefile or an open alternative e.g. ASCII grid or GeoTiff, it is mandatory to include information on the spatial reference system applicable as part of a projection file (.prj), world file (.twf) or similar. All spatial reference systems declared in D1b, E1b & in any external .prj or .twf files must be internally consistent in order to pass QA

19 Encoding in the E1b XML deliverable
What are the benefits? The D1b & E1b reporting framework enables XML deliveries to be easily checked with QA Facilitates harvesting into a data store Facilitates cross checks against Attainment statement in data flow G

20 Questions & Answers EEA-ETC/ACM contact: Tony Bush
Director of Apertum Consulting m e. skype. tony_bush1

Download ppt "Data specifications and e-Reporting for the E1b data flow"

Similar presentations

The Next Generation Network Enabled Weather (NNEW) SWIM Application Asia/Pacific AMHS/SWIM Workshop Chaing Mai, Thailand March 5-7, 2012 Tom McParland,

The Next Generation Network Enabled Weather (NNEW) SWIM Application Asia/Pacific AMHS/SWIM Workshop Chaing Mai, Thailand March 5-7, 2012 Tom McParland,
Office of Coast Survey IHO S-100 and S-101 21st Century Framework Data Structure for Hydrographic and Related Data.

Office of Coast Survey IHO S-100 and S st Century Framework Data Structure for Hydrographic and Related Data.
Attribution of Haze Phase 2 and Technical Support System Project Update AoH Meeting – San Francisco, CA September 14/15, 2005 Joe Adlhoch - Air Resource.

Attribution of Haze Phase 2 and Technical Support System Project Update AoH Meeting – San Francisco, CA September 14/15, 2005 Joe Adlhoch - Air Resource.
Requirements Engineering n Elicit requirements from customer  Information and control needs, product function and behavior, overall product performance,

Requirements Engineering n Elicit requirements from customer  Information and control needs, product function and behavior, overall product performance,
QARTOD 2: Remote Currents Working Group Definitions: Level 1 – refers to radials Level 2 – refers to total vectors Level 3 – refers to higher level data.

QARTOD 2: Remote Currents Working Group Definitions: Level 1 – refers to radials Level 2 – refers to total vectors Level 3 – refers to higher level data.
Air quality e-Reporting basics Concepts, data model & resources to support users Tony Bush ETC/ACM AQ e-Reporting task leader 18th EIONET Workshop - Dublin,

Air quality e-Reporting basics Concepts, data model & resources to support users Tony Bush ETC/ACM AQ e-Reporting task leader 18th EIONET Workshop - Dublin,
Metadata (for the data users downstream) RFC GIS Workshop July 2007 NOAA/NESDIS/NGDC Documentation.

Metadata (for the data users downstream) RFC GIS Workshop July 2007 NOAA/NESDIS/NGDC Documentation.
NR 422- Project Management Jim Graham Spring 2010.

NR 422- Project Management Jim Graham Spring 2010.
Project “European CDDA and INSPIRE”: scope, transformation workflow and mapping rules INSPIRE Conference 2014 Workshop: Implementing Existing European.

Project “European CDDA and INSPIRE”: scope, transformation workflow and mapping rules INSPIRE Conference 2014 Workshop: Implementing Existing European.
Requirements Analysis

Requirements Analysis
David Blasby The Open Planning Project New York. Goals Explain what a WFS and WMS are, and when to use them Be able to create simple spatial web applications.

David Blasby The Open Planning Project New York. Goals Explain what a WFS and WMS are, and when to use them Be able to create simple spatial web applications.
Mapping between SOS standard specifications and INSPIRE legislation. Relationship between SOS and D2.9 Matthes Rieke, Dr. Albert Remke (m.rieke,

Mapping between SOS standard specifications and INSPIRE legislation. Relationship between SOS and D2.9 Matthes Rieke, Dr. Albert Remke (m.rieke,
PM2.5 Model Performance Evaluation- Purpose and Goals PM Model Evaluation Workshop February 10, 2004 Chapel Hill, NC Brian Timin EPA/OAQPS.

PM2.5 Model Performance Evaluation- Purpose and Goals PM Model Evaluation Workshop February 10, 2004 Chapel Hill, NC Brian Timin EPA/OAQPS.
Artur Gsella, Michel Houssiau, presented by Stefan Jensen European Environment Agency Transition to e-Reporting and the spirit of INSPIRE EEA, 4 th of.

Artur Gsella, Michel Houssiau, presented by Stefan Jensen European Environment Agency Transition to e-Reporting and the spirit of INSPIRE EEA, 4 th of.
1 Collection Specific Vocabularies March 2004. 2 Terminology CB - abbreviation for collection builder CV - abbreviation for controlled vocabulary.

1 Collection Specific Vocabularies March Terminology CB - abbreviation for collection builder CV - abbreviation for controlled vocabulary.
Malé Declaration 2 nd emissions inventory workshop AIT, Bangkok, 26 th – 28 th February 2007 Session 5 – Quality assurance and Quality control (QA/QC)

Malé Declaration 2 nd emissions inventory workshop AIT, Bangkok, 26 th – 28 th February 2007 Session 5 – Quality assurance and Quality control (QA/QC)
1 Interoperability of Spatial Data Sets and Services Data quality and Metadata: what is needed, what is feasible, next steps Interoperability of Spatial.

1 Interoperability of Spatial Data Sets and Services Data quality and Metadata: what is needed, what is feasible, next steps Interoperability of Spatial.
EPA’s DRAFT SIP and MODELING GUIDANCE Ian Cohen EPA Region 1 December 8, 2011.

EPA’s DRAFT SIP and MODELING GUIDANCE Ian Cohen EPA Region 1 December 8, 2011.
Artur Gsella European Environment Agency Transition to e-Reporting and the new process flows at the EEA 18th EIONET Workshop on Air Quality Assessment.

Artur Gsella European Environment Agency Transition to e-Reporting and the new process flows at the EEA 18th EIONET Workshop on Air Quality Assessment.
Implementing air quality e-Reporting Data deliverables in 2013 and 2014 and the process of reporting Tony Bush ETC/ACM AQ e-Reporting task leader 18th.

Implementing air quality e-Reporting Data deliverables in 2013 and 2014 and the process of reporting Tony Bush ETC/ACM AQ e-Reporting task leader 18th.

Similar presentations

Ads by Google