Frayères, Eau, Nature et biodiversité, Office Français de la Biodiversité (OFB), Zones de gestion, de restriction ou de réglementation et unités de déclaration, Sites protégés, Environnement
An inventoried Frayère brings together the concepts of fish spawning grounds and crustaceans growing zone or feeding areas as defined in Article L.432-3 of the Environmental Code.
Article L.432-3 of the Environmental Code defines fish spawning grounds as:
— Any part of a watercourse that is included in an inventory established pursuant to I of Article R. 432-1-1 and the bed of which consists of a mineral substrate having the characteristics of the size specific to the reproduction of one of the fish species included in the first list provided for in Article R. 432-1,
— Or any part of watercourses included in an inventory established pursuant to Article II of Article R. 432-1-1.
A crustacean growing or feeding zone within the meaning of Article L. 432-3 corresponds to any part of watercourses included in an inventory established pursuant to III of Article R. 432-1-1.
The founding regulatory text of the inventoried Frayère is the decree issued by the Prefect of Department.
Two types of stream parts may be demarcated. Parts of “classical” watercourses delimited from the BD Carthage® hydrographic network. Parts of “out-of-grid” rivers BD Carthage®. The affluent and sub- tributary attributes add a level of detail to compensate for the lack of completeness of the hydrographic reference used. “Flow” means the consideration of first-level tributaries adjoining the demarcated part of watercourses. “sub tributary” means the consideration of watersheds adjacent to the demarcated part of watercourses.
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.