# Introduction ## Re-Submission and submission control through legacy/reference data The data will be provided within 4 data flows: - comprehensive AQ data flow working in ‘continuous’ (re)submission mode (ex all data flows), - compliance validation with deadline of 30 of September (ex B to G data flows), - AQ plans validation with deadline of 31 of December (ex H to K data flows), - confirmation of provisional assessment regimes with deadline of 31 of December (ex pB and pC data flows). ## Comprehensive AQ data flow working in ‘continuous’ (re)submission mode This is the only data flow where the actual reporting of data takes place. All data should be allowed for submissions at any time, providing that they passed QC. The same applies for resubmissions. The countries have to submit well in advance all data necessary for validation and confirmation at deadlines. This is to allow for data processing at the EEA, so that the tools provided by the Agency for the purpose of the validation and/or confirmation are ready on time. The data submission should allow ‘management by change’, i.e. only reporting data which is new. ## Validation and confirmation at deadlines The idea is that this will not be ‘real’ reporting data flow but will only require the country to validate/confirm what EEA concludes from data submitted within the ‘Comprehensive AQ data flow’. All tables will be pre-filled, based on information collected so far and countries will be asked to validate it by releasing. The pre-filled tables will not be editable. The pre-filling could be happening ‘real time’ and be visible for countries as they deliver data in the ‘Comprehensive AQ data flow’ - with particular emphasis on `ComplianceAssessmentMethod` and `CompliancePlanLink` tables. However, the validation/confirmation data flows will open for release for period of 30 - 45 days before the deadline. This will also allow countries to validate/confirm their resubmissions. The validation/confirmation at deadlines will be allowed (Technical Acceptance) only if `ComplianceAssessmentMethod` and `CompliancePlanLink` tables are complete or if their incompleteness does not originate from technical issues with data. There will be other tools (outside R3) provided for countries for assessing completeness and quality of their data (re)submitted in the ‘Comprehensive AQ data flow’. These external tools as well as the pre-filling will be fed from EEA’s data base collecting data (re)submitted in the ‘Comprehensive AQ data flow’ and integrating it with the historical information. EEA will have a parallel database with a snapshot of the legacy/reference data set taken at each deadline. It will serve as the main source of data for products as well as reference to compare with data processed after resubmissions. The resubmitted data will be allowed for validation/confirmation only if they do not affect previous compliance status. ## Reference data set The reference data set will be wider than legacy data from AQ e-Reporting, it will include: - legacy data from AQ e-Reporting, - vocabularies, - gridded NUTS regions (100m) - to be generated by the EEA, - gridded AQ zones (100/1000 m) - to be generated by the EEA (and a process to automatically grid new zone geometries should be established), - gridded E1b results from the current e-Reporting system - to be generated by the EEA, - gridded sampling point locations - to be generated by the EEA, - gridded SRs - European coverage (100m) - to be generated by the EEA. ## Legacy data cleansing for the reference data flow The legacy data collected within the current system will have to be reviewed and cleaned before it can be used for QC as reference. The best way to achieve clean and consistent data set will be following these steps: 1. complete work on QC rules, iteratively improving the set of QCs (EEA) 2. generate full set of legacy data per country and run through the QCs (EEA) 3. ask country reporters to fix critical issues and upload the corrected legacy data to R3 to run through the QC rules 4. once this is done successfully, clean and consistent data set should be established for each country ## Maintenance of spatial coherence using common grid The spatial coherence of the data will be maintained through common grid approach. The common grid approach is understood as use of the EEA INSPIRE grid in Europe LAEA (SRID 3035) projection and recommended resolution steps (10, 100, 1000, 10000 m) for: - locations of sampling points, - zone geometries (reported by countries as polygons and gridded by the EEA), - exceedance extents, - modelling results (to be reported by countries on common grid), - SRs (although harmonised European SRs may be provided by the EEA, it can be overwritten by countries - reporting their own results on common grid). Reporting in other resolutions will be allowed, fulfilling these conditions: - For resolutions < 100 m: integer multiple of 10, e.g.: 20, 30, 40, 50 m, etc. - For resolutions > 100 m: integer multiple of 100, e.g.: 200, 300, 400, … , 2500 m, 5000 m, etc. ### The benefits of using the common grid approach - harmonised spatial reference for several elements: sampling points, representativeness areas, modelling results, exceedance extent (also AQ zones can be represented as grid), - simplified reporting of modelling results (flat table, geometry not needed), - efficient processing of reported data, e.g.: locations of sampling points (in zones, countries, NUTS regions), compliance statistics from modelling results, MQI calculations (sampling points vs modelling results), etc. - extending operational capacity of AQ e-Reporting, e.g.: processing of data reported for adjustments (natural sources, WSS), possibly - also from scenario modelling, - direct link to EEA's assessments: common grid with EEA's data on environmental burden of disease from air pollution, population data, AQ maps, - readiness for products: much less processing efforts needed to deliver products (online viewers, maps, etc).