For natural PPRs, the code of l'environment defines two categories of zones (L562-1): risk-exposed areas and areas that are not directly exposed to risks but where measures may be planned to avoid d’#x27; exacerbate the risk.
Depending on the level of d'aira, each zone is the subject of an opposable regulation. Regulations generally distinguish three types of zones:
1- “zones d' prohibition to build”, so-called “red zones”, when the level of #x27; hazard is strong and the general rule is #x27; prohibition to build;
2- “prescription zones”, so-called “blue zones”, where the level of #x27; hazard is average and projects are subject to requirements adapted to the type of #x27; issue;
3- areas not directly exposed to risks but where constructions, structures, development or agricultural, forestry, artisanal, commercial or industrial operations could aggravate or cause new risks, subject to prohibitions or requirements (see Article L562-1 of the Code of the Environment). The latter category is only applicable to natural PPRs.
__Origin__
Background on provenance: the perimeter of a prescribed PPR is usually provided in the prefect’s prescription order. The perimeter d' exposure to risks corresponds to the perimeter regulated by the approved PPR and also corresponds to the envelope in which the hazards have been studied.
__Partner organisations__
DDT Ardèche
__Links annexes__
* [basketDownloadFrontalParametrage](https://catalogue.datara.gouv.fr/geosource/panierDownloadFrontalParametrage?LAYERIDTS=52628)
* [direct download of data](https://catalogue.datara.gouv.fr/rss/atomfeed/atomdataset/3cd7f455-e3af-4c74-99ab-19c4d3e496cb)
[See this page on geo.data.gouv.fr](https://geo.data.gouv.fr/fr/datasets/8e8f9eeea901e45b2ad305ae8ae16d75f4b2235e)
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.