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 on which measures can be foreseen to avoid d’#x27; aggravate the risk.Depending on the level of #x27; hazard, each zone is the subject of an opposable settlement.
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__
Thematic source: state of the heritage of the geographical data used in the port-to-know of l’'State
__Partner organisations__
DDT Loir-et-Cher
__Links annexes__
* [XML metadata view](http://ogc.geo-ide.developpement-durable.gouv.fr/csw/all-dataset?REQUEST=GetRecordById&SERVICE=CSW&VERSION=2.0.2&RESULTTYPE=results&elementSetName=full&TYPENAMES=gmd:MD_Metadata&OUTPUTSCHEMA=http://www.isotc211.org/2005/gmd&ID=fr-120066022-jdd-f0318d11-eef2-4801-bb0b-862ed3ff0745)
* [COVADIS data standard: Easement of public utility (SUP)(http://geostandards.developpement-durable.gouv.fr/afficherPageStandard.do?id=11)
[See this page on geo.data.gouv.fr](https://geo.data.gouv.fr/fr/datasets/4ecffccc918428ae154f8bf9485c45f090b08169)
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.