Simple download service (Atom) of the dataset: Regulatory zoning of the flood risk prevention plan by overflow of the rivers Marne and Blaise de Vitry-le-François — Marne-Blaise sector
Open data API in a single place
Provided by BUREAU DE RECHERCHES GÉOLOGIQUES ET MINIÈRES
Get early access to Simple download service (Atom) of the dataset: Regulatory zoning of the flood risk prevention plan by overflow of the rivers Marne and Blaise de Vitry-le-François — Marne-Blaise sector API!
For natural PPRs, the Environmental Code defines two categories of zones (L562-1): risk-exposed areas and areas that are not directly exposed to risks but where measures can be foreseen to avoid exacerbating the risk.
Depending on the level of hazard and the issues, each area is subject to an enforceable regulation that sets out, in a clear and operational manner, the regulatory measures that apply to each of the restricted areas. The Regulation generally distinguishes five types of zones:
1. ‘Building prohibited areas’, referred to as ‘red areas’ or ‘pink areas’, depending on the level of hazard, in an area with little or no construction, or in an agricultural or natural area, then the general rule is the prohibition on construction;
2. “areas subject to requirements”, called “magentas zones” or “blue zones”, depending on the level of hazard in a built area, then the projects are subject to requirements adapted to the type of issue;
3. “white areas” not defined in the Regulation and for which the RPIP does not apply, as they are not subject to hazard.
The identification of these homogeneous areas results in the development of a mapping of the regulatory zoning of the PPRi.
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.