1. 1 Proposal for reporting of air quality management zone boundaries Version 2.0

2. 2 Current situation 2004/461/EC laying down a questionnaire to be used for annual reporting on ambient air quality assessment under Council Directives 96/62/EC and 1999/30/EC and under Directives 2000/69/EC and 2002/3/EC of the European Parliament and of the Council Form 2 Delimitation of zones and agglomerations

3. 3 Form 2 Delimitation of zones and agglomerations (96/62/EC Articles 5 and 11(1b)) Full zone name Zone code Pollutant(s), possibly separate protection targets, to which the zone applies Type (ag/nonag) Area (km 2 ) Population Border coordinate pairs

4. 4 Notes to Form 2: (1) The Member State should give not only the zone name, but also a unique zone code. (2) The Member State should indicate the pollutant(s) to which the zone applies using the codes: ‘S’ for SO2, ‘N’ for NO2/NOx, ‘P’ for PM10, ‘L’ for lead, ‘B’ for benzene, ‘C’ for carbon monoxide and ‘O’ for ozone, separated by a semicolon, or ‘A’ if the zone applies to all these pollutants.

5. 5 Notes to Form 2: If zones have been separately defined for health, ecosystem and vegetation protection, the Member State should use the following codes: ‘SH’ for SO2 health protection, ‘SE’ for SO2 ecosystem protection, ‘NH’ for NO2 health protection, ‘NV’ for NOx vegetation protection. (3) It should be indicated whether the zone is an agglomeration (code: ‘ag’) or not (code:‘nonag’). (4) Optionally, the Member States may add the area and population size of the zone for further processing of the data at European level.

6. 6 Notes to Form 2: (5) For further processing, the Member State is requested to fill in the zone borders in a standard format (polygons, using the geographical coordinates according to ISO 6709: geographical longitude and latitude). The Member State is requested to provide separately a map of the zones (as an electronic file or on paper) to facilitate the correct interpretation of the zone data. The Member State must provide at least either the zone borders in Form 2 or a map.

7. 7 Guideline referring to Commission Decision 2001/839/EC (January 28th 2002) provides additional guidance on: Allocation of zone names and codes National naming methods for zones may differ strongly between Member States. Because of this, an additional zone code is needed to unambiguously identify zones. The zone code is defined as CCxxxx, where CC is the abbreviation of the Member State’s name as given in Table A of this guideline and xxxx a serial number to be given to each zone by the Member State. The Member State is entirely free in allocating serial numbers to the zones.

8. 8 And on: Information on zone borders It is mandatory to provide information on the zone borders. There are several ways in which these borders can be provided: Maps printed on paper Bitmaps Zone borders coordinates in electronic form

9. 9 The most exact and flexible form of reporting how the zone territories have been defined is inthe form of coordinates of zone borders In view of the anticipated use, a very high resolution of the zone borders is not needed. A good balance between file size and spatial detail is a resolution of about 1 km. For correct interpretation the Member State is requested in Note 5 to add a map of the zones; this is essential if the zone borders consist of more than one closed curves (e.g. two combined separate areas or a “hole” in the zone).

10. 10 Form 2: Example of delivery

11. 11 Zones for SO 2 Mecklenburg-Vorpommern Brandenburg Berlin Sachsen Sachsen-Anhalt Bayern Baden-Württemberg Saarland Rheinland-Pfalz Hessen Nordrhein-Westfalen Niedersachsen Bremen Schleswig-Holstein Thüringen Hamburg Brandenburg3Mecklenburg-Vorpommern3 Berlin1Nordrhein-Westfalen12 Baden-Württemberg8Rheinland-Pfalz6 Bayern5Saarland3 Bremen + Niedersachsen7Sachsen9 Hessen5Sachsen-Anhalt7 Hamburg + Schleswig-Holstein4Thüringen3

12. 12 Form 2: Example of delivery Form 2 Delimitation of zones and agglomerations (96/62/EC Articles 5 and 11(1b)) Zones Full zone name Tallinn Harjumaa Hiiumaa Zone code EE0010 EE0011 EE0012 Border coordinate pairs +24.905146+59.459885 +23,73092+59,23665+59,23665+22,455143+58,835068 Border coordinate pairs +24.926905+59.435551 +23,73079+59,23693 +22,443073+58,854748 Border coordinate pairs +24.868286+59.422176 +23,73135+59,27361 +22,417639+58,877346 Border coordinate pairs +24.819933+59.409546 +23,77742+59,2736 +22,376984+58,895641

13. 13 Processing at the European level: overview presented at 10 th EIONET WS For presentation of air quality information by Commission and EEA, an EU-wide zone map is needed. Half of the EU15 Member States have sent digital zone border coordinates: as border polygones or as GIS files. But hard to rework to a consistent EU map! Consistency of zone borders between Member States is important; proposal for exchange to be developed soon.

14. 14 Proposal for exchange for: Zone borders based on administrative units Zone borders with a different basis

15. 15 Case 1: Zone borders based on national administrative units 1.For each AQ zone, the data supplier provides the national administrative units code(s) which the zone covers. 2.EEA/ETC adds the zone code as an attribute to the European data set of administrative boundaries. The geographical boundaries of national administrative units are maintained by MS national mapping organisations.(EuroBoundaryMap formerly known as SABE) 3.The zones and the characteristics reported in the AQ questionnaire can be displayed as maps at European level. An illustrated example for Case 1 follows.. Proposed steps:

16. 16 Case 1: Zone borders based on national administrative units. Example 1/3 Czech Republic 2003 questionnaire Zone code: CZ062 Full zone name: Jihomoravský Corresponds to national administrative unit: Jihomoravsky kraj with the boundary shown here.

17. 17 Case 1: Zone borders based on national administrative units. Example 2/3 Austria 2003 questionnaire Zone code AT_03 Full zone name: Niederösterreich Zone code AT_09 (agglomeration) Full zone name:Wien Correspond to national administrative units: Niederösterreich AT12 and Wien AT13 with the boundaries shown here.

18. 18 Case 1: Zone borders based on national administrative units. Example 3/3 Zones CZ062 and AT_03 share a common international border. No time consuming “geometrical fitting” between countries is required during the processing of the air quality zones.

19. 19 Case 1: A zone border can be based on several national administrative units AT_O3_1 Nordostösterreich ohne AG Wien AT_O3_2 Südostösterreich ohne AG Graz AT_O3_3 Oberösterreich und nördliches Salzburg ohne AG Linz AT_O3_4 "Pinzgau, Pongau und Steiermark nördlich des Alpenhauptkamms" AT_O3_5 Nordtirol AT_O3_6 Vorarlberg AT_O3_7 Kärnten und Osttirol AT_O3_8 Lungau und oberes Murtal Example: AT_O3_7 = Kärnten AT21+ Osttirol AT333 Austria 2003 questionnaire

20. 20 Case 1: How would data suppliers provide the information on national administrative units? EEA/ETC would prepare a standard template containing the hierarchical list of all national administrative units for their country. The data supplier would indicate on the template the administrative unit(s) on which the zone is based. The data supplier would choose whether to use just the smallest administrative units or to use highest appropriate level in the hierarchy A separate template would be completed for each zone identified in the air quality questionnaire. All MS regularly supply information on administrative units to Eurostat under REGULATION (EC) No 1059/2003 http://europa.eu.int/eur- lex/pri/en/oj/dat/2003/l_154/l_15420030621en00010041.pdf http://europa.eu.int/eur- lex/pri/en/oj/dat/2003/l_154/l_15420030621en00010041.pdf The template provided to data suppliers would be based on the lists of national administrative units and their codes regularly published by Eurostat at: http://europa.eu.int/comm/eurostat/ramon/nuts/home_regions_en.html http://europa.eu.int/comm/eurostat/ramon/nuts/home_regions_en.html

21. 21 Case 1: Example of administrative units for Austria published by Eurostat

22. 22 Case 1: EuroBoundaryMap overview Geometry of the boundaries of the administrative units of 36 countries/regions in Europe Linkage to the corresponding NUTS codes Names and codes of administrative units on the basis of the national nomenclature and representing the national administrative hierarchy Unified coding system for all the administrative levels including also names of different national administrative levels and the relations between them Location of residences of authorities of the units for the countries (not for all countries) Coastline information for the countries where the physical and administrative boundaries do not coincide. Contents: Reference: http://www.eurogeographics.org/eng /04_sabe.asp http://www.eurogeographics.org/eng /04_sabe.asp

23. 23 Case 2: Zone borders not based on national administrative units 1.EEA/ETC prepares a geographical template for each MS. The template is derived from the EuroBoundaryMap data set and consists of The national boundary Spatial reference data Pre-filled meta information 2.For each AQ zone, the data supplier imports the geographical coordinates for the zone boundaries into the template. The zone code must also be provided in order to link the geographical information with the AQ questionnaire information 3.EEA/ETC aggregates the geographical templates into the European data set 4.The zones and their characteristics can be displayed as a map at European level. An illustrated example for Case 2 follows.. Proposed steps:

24. 24 Case 2: Zone borders not based on national administrative units. Example 1/3 The data supplier can use the provided GIS template with default spatial reference information or convert to another documented reference system.

25. 25 Case2: Zone borders not based on national administrative units. Example 2/3 The data supplier can import prepared geographical coordinates for the zone boundaries into the geographical template. Existing GIS files (e.g. shape files) of the zone boundaries can also be imported into the geographical template.

26. 26 Case 2: Zone borders not based on national administrative units. Example 3/3 Quality of the reported zone boundaries with respect to the national boundary can be checked in GIS software before delivery by the data supplier.

27. 27 Case 2: Why should the data supplier use the geographical template? The geographical template allows the data supplier to see how the national zones appear in the European context. The data supplier is best placed to recognise good quality and resolve any problems. In case of difficulties, it is more efficient to provide support to the data supplier during the reporting process rather than to return back weeks or months later to find out “what happened”. Many of the zone boundary coordinates provided under the current procedure cannot be used because they lack spatial reference information needed for aggregation. Zones made up of more than one polygon (e.g. offshore islands) are very hard to process under the current procedure.

28. 28 Delivery of the zone boundary information – proposal for pilot in 2006 MS would delivery the boundary information for all their zones during Q4 2006. Delivery point would be same as for AQ questionnaire in CDR Delivery would comprise either the completed administrative units templates and/or the completed GIS template(s) A draft European map showing the zone boundaries would become available in spring 2007

29. 29 AQ zones in Austria, CR, and Slovakia

30. 30 Zone codes & Admin codes

31. 31 Zone codes & Admin codes

32. 32 Zone codes & Admin codes