The Non-Fundamental Natural Risk Prevention Plans (PPRNs) are the key instrument for natural hazards prevention. Their objective is to control development in areas at risk.
L' development of a risk prevention plan generates a series of spatial data organised into several datasets.
This series corresponds to the restricted areas of the plan once approved digitised at Scan25.
The PPR regulations generally distinguish between “zones d' prohibition to build”, so-called “red zones”, where the level of ' hazard is strong and the general rule is the “prohibition of construction”; the “prescription areas”, known as “blue zones” when the level of #x27; hazard is average and the projects are subject to requirements adapted to the type of #x27; issue and areas not directly exposed to risks but subject to prohibitions or prescriptions.
__Origin__
This dataset is the aggregation of all digitised PPRNs at the Scan25 scale of Isère. Several genealogies are possible to obtain the constitutive dataset of a PPR:
1- L' preparation of the PPR has taken place a posteriori of the publication of this standard. The master of the PPR was able to take into account the technical specifications of the PPR standard from the start of the procedure.
2- L' development of the PPR and the publication of this standard are concurrent. The geographical data had to be the subject of a “hot” standardisation during the procedure, taking advantage of the knowledge of all stakeholders in the file.
— Source of georeferencing according to the municipality:
Scan25 (IGN) (number and year different according to PPRN)
N_zone_ Regulation_pprn_s_038
__Partner organisations__
DDT Isère
[See this page on geo.data.gouv.fr](https://geo.data.gouv.fr/fr/datasets/89be396b73cd3916481aa2564f45f850a50edf09)
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.