Table of contents
- 2. REPORTING AT SURFACE WATER BODY LEVEL (SCHEMA SWB)
- 2.3. Pressures and impacts on surface waters
- 2.4. Ecological status and exemptions
- 2.5. Chemical status of surface waters, exemptions and Mixing Zones
- 3. REPORTING AT GROUNDWATER BODY LEVEL (SCHEMA GWB)
- 3.3. Pressures and impacts on groundwater
- 3.4. Quantitative status of groundwater and exemptions
- 3.5. Chemical status of groundwater and exemptions
- 4. MONITORING (SCHEMA MONITORING)
- 5. PROTECTED AREAS (SCHEMAS SWB AND GWB)
- 6. REPORTING AT MS LEVEL: COMPETENT AUTHORITIES, RBDS AND SUB-UNITS (SCHEMA RBDSUCA)
- 7. REPORTING AT RBD/SUB-UNIT LEVEL FOR SURFACE WATER (SCHEMA SWMET)
- 7.3. Methodologies classification ecological status and potential
- 7.4. Methodologies classification chemical status
- 7.5. Overall management objectives (nutrients, river continuity)
- 7.6. Definition of significant pressures and impacts
- 7.7. Methodologies exemptions
- 8. REPORTING AT RBD/SUB-UNIT LEVEL FOR GROUNDWATER (SCHEMA GWMET)
- 8.4. Definition of significant pressures and impacts
- 8.5. Methodologies exemptions
- 9. REPORTING AT RBD/SUB-UNIT LEVEL FOR RBMP (SCHEMA RBMPPOM)
- 9.4. Water abstractions and exploitation of water resources
- 10. PROGRAMME OF MEASURES REPORTED AT RBD/SUB-UNIT LEVEL (SCHEMA RBMPPOM)
- 10.2. Targeted questions on basic measures and other aspects
- 10.3. Estimates of cost of measures
- 10.4. Co-ordination of measures in international RBDs
- 10.5. Progress with and achievements of the programme of measures for the first planning cycle
- 11. REPORTING AT RBD/SUB-UNIT LEVEL FOR ECONOMIC ANALYSIS AND COST RECOVERY (SCHEMA RBMPPOM)
- Overview of comments presented at WG DIS
- WISE spatial data presentation at WG DIS
3. REPORTING AT GROUNDWATER BODY LEVEL (SCHEMA GWB)
3.1. Overview of the structure of the 2016 reporting contents
Reporting at groundwater body level is done for each RBD. For the purpose of presentation in this guidance, the contents of reporting are structured according to the following sub-chapters:
- Groundwater body characterisation
- Pressures and impacts on groundwater bodies
- Quantitative status of groundwater bodies
- Chemical status of groundwater bodies
The following sections describe the contents of reporting. The UML diagram of the GWB schema is found in Annex 10.3.
3.2. Characterisation of groundwater
3.2.1. Introduction
Article 5 and Annex II of the WFD requires Member States to identify the location and boundaries of groundwater bodies.
Class: GroundWaterBody - Schema element:
- Please include here any comments which apply to all the schema elements in this Class.
- In addition to those general schema element level comments, we welcome your views on: a) whether you think this Class can be simplified; and b) whether you think the linkages with other reporting Classes or Schemas can be improved, and how;
-
Comments which should apply to all the schema elements in this Class:
There is no real connection between GML and XML schemas thus some information should duplicate, some are missing as basic information from XML. We would prefer if all data in GML would be included in XML as a view from GML schema element.In addition to those general schema element level comments:
This XML should be linked with other GML GWB schemas and add a new element whether the water body has really changed or not, because in GML all changes will be registered without knowledge on reality (some very small changes because of the base map corrections either transformations between coordinate systems or joint point negotiations at country borders, etc.)
This ensures that there is no conflict between the two types of data service (GML, XML).
euGroundWaterBodyCode - Required.
Unique EU code of the groundwater body. Prefix the groundwater body’s national, unique code with the Member State’s 2-alpha character ISO country code
-
The explanatory text should include a reference to the identifier specifications included in GIS guidance (reproduced below)
The specification has changed in the current reporting. The identifiers must:
- Start with the ISO 3166-1 alpha-2 country code, except for Greece ('EL') and the United Kingdom ('UK');
- Be followed by the national code, with a maximum of 40 characters;
- Use only upper case letters [A to Z] and digits [0 to 9].
The underscore character ('_') or the hyphen character ('-') may be used as separators within the code (but not to separate the country code from the national code, and not in the end of the code).
This means that the comma character (',') and the period character ('.') can no longer be used.
The reason for this change is that each identifier will be associated with a stable URL in the WISE system (e.g. http://dd.eionet.europa.eu/vocabulary/wise/SpatialUnit/euRBDCode.ES030).
A regular expression may be used for a preliminary check the syntax of the identifiers. Adapt the following pattern to the specific country: ^[A-Z]{2}[0-9A-Z]{1}([0-9A-Z_-]{0,38}[0-9A-Z]{1}){0,1}$
groundwaterBodyName - Required.
Readily understandable name of the groundwater body in English that is meaningful outside of the RBD or Member State.
-
The name of the groundwater body should be in the national language, as it is a proper name.
-
The name of the surfacewater body should be in the national language, as it is a proper name and it is linked to our legislation. All legal references to the name will not be found when using the name in English.
Maybe a new field with the name in English could be included as an optional field. In the GIS Guidance the nameText (name in national language) is mandatory and nameTextInternational is optional (English version of name).
-
Groundwater body names should be in the national language
-
We suggest that the Member States have the opportunity to report the names of the Groundwater bodies on national language, either in the current fields or in additional column.
-
We would also suggest to report the names of the WBs in the national language as these names are also used in the RBMPs.
-
BE supports : Groundwater body names should be in the national language
Layered – Required.(YesNoNoInformation_Union_Enum)
Indicate whether the groundwater body is layered.
-
The information is useless.
-
With the introduction of reporting of horizons in the spatial data set, "Layered" could be excluded from reporting. Suggestion to remove.
-
This information could be excluded from reporting.
linkSurfaceWaterBody – Required.(YesNoCode_Enum)
Indicate whether the groundwater body is associated with one or more surface water bodies.
linkSurfaceWaterBodyCode - Conditional.
If the groundwater body is associated with one or more surface water bodies, report the surface water body codes of the associated surface water bodies.
linkTerrestrialEcosystem - Required.(YesNoCode_Enum)
Indicate whether a terrestrial ecosystem is directly dependent on the groundwater body.
-
In the Schema element: linkTerrestrialEcosystem there is only information about the dependence of terrestrial ecosystem on the groundwaterbody. Maybe there should be added some information about the number or type/s of these ecosystems.
geologicalFormation - Required.(GeologicalFormation_Enum)
Describe the main geological formation of the aquifer type.
groundwaterBodyTransboundary – Required.(YesNoCode_Enum)
The Directive requires coordination among Member States for the management of transboundary Water Bodies. Transboundary water bodies are those crossing the border between countries or constituting part of the border between two countries for a certain length.
-
Relation with transboundary monitoring was included only in the GML schema thus relation was not clear for EU Assessors.
gwAssociatedProtectedArea – Required.(YesNoCode_Enum)
Indicate whether the groundwater body is associated to any protected area.
-
We would suggest to delete this schema element.
Detailled information on protected areas had to be reported under the class "SWAssociatedProtectedArea". If this schema element will be kept, we suggest to highlight the difference between the information to be reported here and under the protected areas schema (e.g. should protected areas designated on the basis of national laws be reported here?).
-
In the Schema element: gwAssociatedProtectedArea there is only information about the dependence of terrestrial ecosystem on the groundwaterbody. Maybe there should be added some information about the number or names of these areas.
In the recent and ongoing review of the implementation of the directives by the European commission there seem to be concerns about grouping of groundwater bodies. Statistics in the reports on eg monitoring coverage do not consider grouping. At the same time grouping is explained to be the key for increasing monitoring coverage in the case when MS have a very large number of GWBs due to the natural hydrogeological conditions. Grouping must therefore be reported and presented in a different manner.
The cause of confusion about grouping is probably due to unclear reporting schemas. In the first management cycle reporting of grouping was much more straight forward, where each GWB were related to a group identification number. This coming cycle it is necessary that this reporting is re-introduced with a possibility to have different groups for chemical and quantitative purposes, i.e. each GWB could relate to different group identifiers.