Protection zone of a regulatoryly defined catchment feed (ACA), where programmes of #x27 must be implemented; action for farmers and landowners to protect all or part of the #x27; supply of catchments against pressures of #x27; agricultural origin (spread pollution or sampling for #x27; irrigation)
In response to the requirements of the Framework Directive on Water, the Law on Water and Aquatic Environments of 30/12/06 strengthened the control systems for diffuse pollution of #x27; agricultural origin through the creation of zones for the protection of the areas of #x27; supply of catchments. The implementation of this new resource protection system leads to the delimitation of catchment feeding areas (ACAs), sometimes also referred to as catchment ponds (CCBs) — layer #1011 - which include AAFC protection areas.
The protection zone is defined by the crossing of cartographic zoning of intrinsic vulnerability and zoning of agricultural pressures.
In the case of surface water catchments, the definition of a protection zone within the watershed upstream of the catches of water is based on the identification of flows (running, drainage, ditches of #x27; flow, exchanges between alluvial waters and rivers of #x27; water.) and on #x27; identification, by territorial diagnosis of agricultural pressures and areas likely to play the most important role in the degradation of the water resource.
Layer proposed in the directory N_ZONAGES_EAU while the \#x27;AAC is proposed in the directory N_AEP because it is \#x27;acts of regulatory zoning (similar to the layers of AEP sampling and protection perimeters)
The relationship between AAC and catchments is of type "1 for several;. It is therefore proposed to include the identifier of l’'AAC in the capture layer (#0000002).
Can be defined on an AAFC from 0 to multiple protection areas.
__Origin__
The Carto comic serves as a reference for the contour of the municipalities. This limit is never changed.
1/In the case of sub-communal zoning, zone boundaries are digitised from the BD Carto, PISC and BD Ortho repositories.
— When infracommunal zoning is defined in relation to a cadastral section, the limit is obtained from the PISC. In some cases, this limit may have been offset against BDOrtho.
— When infracommunal zoning is defined in relation to d' other limits, these limits are obtained from different documents or data (paper plans, cadastral boards, digitised cadastre, scan25...). They are still seized on BDOrtho funds.
2/Once the sub-communal zoning is digitised, each municipality or part of a commune is attached to a disadvantaged area.
__Partner organisations__
DDT Rhône
__Links annexes__
* [XML metadata view](http://ogc.geo-ide.developpement-durable.gouv.fr/csw/all-dataset?REQUEST=GetRecordById&SERVICE=CSW&VERSION=2.0.2&RESULTTYPE=results&elementSetName=full&TYPENAMES=gmd:MD_Metadata&OUTPUTSCHEMA=http://www.isotc211.org/2005/gmd&ID=fr-120066022-jdd-b4f420e2-f5e7-4b33-b646-117cbfb0812b)
[See this page on geo.data.gouv.fr](https://geo.data.gouv.fr/fr/datasets/35f6962c29a037ac9799d01069ae7f080fc1d4fa)
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.