AQD IPR pilot study programme on e-reporting

Transcription

1 AQD IPR pilot study programme on e-reporting Progress on UTD Jaume Targa 6 th pilot meeting Copenhagen 8-10 October May 2012

2 Introduction Important points on UTD Re-delivering UTD data Aggregation rules on UTD data Testing phase by EEA Progress by pilot countries

3 Important issues on UTD Naming convention on the XML Data repositories (FTP) Specifications on the DATA ARRAY encoding TimeStamp ISO standard Codelist for validity & verification status

4 Naming convention for UTD Data flow deliveries should be prepared for with a 3-part notation dataflowsuffix_countrycode_generictimereference.xml Using this convention during pilot: E2a_GB_ xml - relates to UTD dataflow for the 24-hour period specified E2a_SE_ xml E2_DK_ _Test.xml E2a_IT_ xml E2a_IT_Piedmont_ xml E2a_BE xml E2_IE xml

5 DATA repositories UTD to be delivered via FTP on hourly basis Re-delivery of UTD data will be dependant on data provider Current CDR repositories, not operationally viable for UTD data (ONLY to share testing files for UTD) CDR likely to be for delivery of fully verified datasets

6 Reporting hourly data T10:00:00z,1,2,110 Timestamp Validity Verification Value

7 Specifications of the encoding hourly data <om:result xsi:type="swe:dataarraytype">... <swe:encoding> <swe:textencoding decimalseparator="." tokenseparator=","/> </swe:encoding> </om:result>

8 Specifications of the encoding hourly data Number of hourly values included for this sampling point Specification of the end time of the result ValidityStatus VerificationStatus Pollutant and unit??

9 Timestamp (as per latest split guidance) - DECISION Timestamp on hourly resolution encoded in accordance with the extended ISO 8601:2004(E). Format YYYY-MM-DDThh:mm:ss±hh YYYY represents the year MM represents the month DD represent the day hh represents the hour mm represents the minute ss represents the second +hh represents the shift to UTC, so for CET it is +01 Hourly data in UTC -> T11:00:00z Hourly data in UTC+1 -> T11:00:00+01 Hourly data in UTC+2 -> T11:00:00+02

10 Data encoding & codelist T10:00:00z,1,2,110 Timestamp Validity Verification CODE LIST created Value

11 Data encoding & codelist T10:00:00z,1,2,110 vocabularies/observationsvalidity.rdf trunk/vocabularies/observationsverification.rdf

12 Data encoding & codelist T10:00:00z,1,2,110 vocabularies/observationsvalidity.rdf trunk/vocabularies/observationsverification.rdf

13 UTD XML what does it look like? How do we link the data array to the metainformation (D)? xlink to process xlink to SamplingPoint xlink to Feature of Interest

14 UTD XML what does it look like? Timeseries in this case 24hours When results where made available Xlink to PROCESS Pollutant Xlink to SamplingPoint Feature of Interest

15 Aggregation on UTD data EEA & ETC focusing on the following aggregation on UTD data: NO 2 Alert Threshold SO 2 Alert Threshold O 3 Alert Threshold O 3 Information Threshold & O 3 Long Term Objective Important note during meeting: Need to look in to At locations representative of air quality over at least 100 km2 or an entire zone or agglomerations, which ever is smaller

16 Aggregation on UTD data KEY ASPECTS Required proportion of valid data an hourly averaged concentra0on - > at least 45 valid minute values - MS need to ensure! a 8- hourly averaged concentra0on - > at least 6 valid hourly values a daily maximum 8- hour mean - > at least 18 valid hourly running 8- hour averages per day

17 Problems for testing Metadata D doesn t exist ETC/ACM has created dataset D for you Next year ETC/ACM to: Create dataset D from 2012 EoI delivery Provide guidance on gml:id Need pilot countries to operationally delivery UTD using Their own metadata D Metadata D from AirBase

18 Other problems from pilot countries

19 Testing phase at EEA Operational delivery via FTP Upload to database (EEA) Perform QA/QC checks & calculate initial statistics (EEA) Publish via AQ viewers (EEA) UTD XML delivered by pilot MS

20 Any Questions?