An element of the Fluvial Public Domain is either a part of Water Cours, or a Water Plan, or a works belonging to the public river domain.
The river public domain stems from a historical process that has evolved over time:
— the 1835 Ordinance establishing the “nomenclature of inland waterways”,
— watercourses referred to in subsequent acts of incorporation including international treaties,
— classified since 2003 by order of the district coordinator prefect or the local authority,
— in the DOMs, all waterways Water Police Services/MISE identified by the 2005 Circular.
These regulations are, according to the Element du Domaine Public Fluvial, the founding regulatory text of it.
An element of the Public Fluvial Domain belongs to the State except those which have been transferred to a community or group of communities by order of the PCB (including in the DOMs) and watercourses incorporated directly into the DPF by the competent authority of a community.
Originally the DPF was created for navigational purposes. Some elements have been removed from the “waterway nomenclature” and retained in the CFO without special purpose. Since 1964, it has been possible to assign elements to the CFO for purposes other than navigation.
The same reasoning in relation to the history applies to the decommissioning texts and makes it possible to identify the competent authority behind the decommissioning. Decommissioning implies the return of the segment to the ordinary law.
The transverse limit of the sea serves as the downstream limit of the Domaine Public Fluvial.
The Segment of the Public Fluvial Domain allows the link to the national hydrographic repository by allowing it to be divided for the purposes of the DPF theme.
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.