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.3. Pressures and impacts on groundwater
3.3. Pressures and impacts on groundwater
3.3.1. Introduction
Article 5 of the WFD requires Member States to identify the significant pressures present in the RBD likely to cause groundwater bodies to be of less than good status. It also requires Member States to assess the impacts on groundwater bodies to support the determination of status.
Class: GroundWaterBody
- 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;
gwSignificantPressureType - Required.(SignificantPressureType_Enum)
Indicate the significant pressure type(s) from the enumeration list .
-
Similar comment to SWsignificantPressureType
The codelist of Annex 1a shouldn't be splitted by drivers as usually the relation pressure- driver is 1:n
-
Since the guidance says 'Significant pressures should only be reported for those water bodies which have been identified as being at risk'
we propose to extend the quality check (not only check consistency with status but with risk aswell)
Within-schema check: If (SWB/GroundWaterBody/gwChemicalStatusValue is ‘3’ or GWB/GroundWaterBody/gwChemicalStatusExpectedGoodIn2015=No), at least one significant pressure type must be selected from the enumeration list (can include ‘8 Unknown pressures’). The option ‘No significant pressure’ is not a valid selection.
and the same check for quantitative status/risk
-
List of pressure types and impact types should be announced in an early stage of the management cycle. Befor the analysis has been done. No midcycle change.
-
See comment submitted for "swSignificantPressureType".
-
The pick up list could be filtered on types for GW og SW in the Access tool
-
List of pressure types and impact types should be announced in an early stage of the management cycle. Befor the analysis has been done.
gwSignificantPressureOther - Conditional.
If ‘7 – Anthropogenic pressure - Other’ is selected from the enumeration list and reported under gwSignificantPressureType, provide details of any other anthropogenic pressures which are relevant in this element. This element should only be reported if the pressure type is not included in the enumeration list under gwSignificantPressureType.
gwSignificantImpactType - Required.(SignificantImpactType_Enum)
Indicate the impact type(s) from the enumeration list.
-
Since the guidance says 'Therefore, a pressure or impact should only be reported if it is significant, alone or in combination with others, because it puts the Environmental Objectives at risk
we propose to extend the quality check (not only check consistency with status but with risk aswell)
Within-schema check: If (GWB/GroundWaterBody/gwChemicalStatusValue is ‘3’ or GWB/GroundWaterBody/gwChemicalStatusExpectedGoodIn2015=No), at least one significant impact type or the option ‘UNKN - Unknown impact type’ must be selected from the enumeration list. The option ‘NOSI - No significant impact’ is not a valid selection.
and the same check for quantitative status (risk/status)
-
The table in Annex 1b needs revision. There is a mix of impacts for surface waters and groundwaters that originates from different objectives in the directives. In general, some of the impacts directed towards surface waters may also be relevant for groundwaters, eg acidification, but is not a focus area in the directive. This table should either 1) be split into two (sw/gw), 2) revised accordning to actual possible impacts for the two water types, or 3) a reference to eg directive articles should be given for all impact types.
List of pressure types and impact types should be announced in an early stage of the management cycle. Befor the analysis has been done. No midcycle change.
-
See comment submitted for "swSignificantImpactType"
-
The pick up list could be filtered on GW and SW in the Access tool
gwSignificantImpactOther - Conditional.
If ’ OTHE - Other significant impact type’ is selected from the enumeration list under gwSignificantImpactType, provide details of any other impact types which are relevant in this element. This element should only be reported if the impact type is not included in the enumeration list under gwSignificantImpactType.
test