Right-of-way of a freshwater body
Water bodies refer to a surface, open, natural or anthropogenic surface freshwater area of varying depths. The term “water body” covers a number of situations commonly referred to as lake, containment, pond, gravel, quarry or marsh.
By convention, water bodies corresponding to gravel or quarries during the period in which they fall under the mining code are not included in this layer.
Water bodies are described by their use(s) according to a predefined usage typology.
By convention, for the sake of consistency with Cascade, the typology ‘pisciculture’ shall apply, irrespective of the species produced, to a use of the water body covered by:
either the rules on ICPEs (heading 2130 of Decree 206-942 of 27 July 2006) when regular feeding and production exceeding 20T/year;
Article L431-6 of the Code de l’environnement et de la police de l’eau (section 3.2.7.0 of Decree 206-881 of 17 July 2006) if there is no regular feeding or production less than 20T/year.
A similar layer N_PLAN_EAU_P (#47) describes the centroids of water bodies.
A N_AUTRE_PISCI_S layer describes off-water fish farms.
1)Nomenclature of the types of use of the water body: A: storage for irrigation/B: storage for AEP/C: storage for energy production/D: storage for navigation/E: flood capping/F: stretch support (fishing life)/G: storage for crop/H snow production: fish farming with regular feeding and production of more than 20T/year/I: fish farming without regular feeding or with a production of less than 20T/yr
* The above list of possible uses is not exhaustive.
The services must ask the CNV Secretariat for a code for non-present uses: [email protected]
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.