A catchment area is demarcated in the territory following hydrological or hydrogeological studies (as the case may be: capture of surface water or groundwater) defining the area from which the water supplies a catchment intended for drinking water to populations, or several of such abstractions close to each other.
In response to the requirements of the Water Framework Directive, the Water and Aquatic Environments Act of 30/12/06 strengthened the control mechanisms for diffuse pollution of agricultural origin by creating protection zones for catchment feeding areas. The implementation of this new resource protection system leads to the delineation of catchment foraging areas (AAFCs, sometimes also referred to as catchment feeding basins or LACs) that include AAFC protection areas.
For surface water abstraction, the AAFC is the sub-watershed located upstream of the intake. For groundwater, a common national AAFC delineation methodology has been proposed. At the right of the methodological guide produced, the supply basin of an underground catchment is defined as the location of the points on the surface of the soil that contribute to the feeding of the catchment. Some catchment foraging areas are identified as priorities within the Water Management and Management Master Plans (WMPs) and measurement programs. A AAFC is thus defined, after a technical study, as the area from which the water supplies a close catchment or several catchments. It is therefore proposed to include the AAFC identifier as one of the attributes of the data standard locating drinking water sampling points (#0000002 N_PRELEV_AEP_P).
The relationship between AAFC and capture is “1 for multiple”. It is therefore proposed to include the AAFC identifier in the capture layer (#0000002).
Build on reliable and scalable technology
FAQ
Frequently Asked Questions
Some basic informations about API Store ®.
Operation and development of APIs are currently fully funded by company Apitalks and its usage is for free.
Yes, you can.
All important information such as time of last update, license and other information are in response of each API call.
In case of major update that would not be compatible with previous version of API, we keep for 30 days both versions so you will have enough time to transfer to new version. We will inform you about the changes in advance by e-mail.