The COVADIS data standard on risk prevention plans includes all the technical and organisational specifications for storing geographical data in digital format as represented in the Risk Prevention Plans (RPPs).
Major risks include the eight foreseeable main natural hazards in the national territory: floods, earthquakes, volcanic eruptions, field movements, coastal hazards, avalanches, forest fires, cyclones and storms, and four technological risks: nuclear risk, industrial risk, risk of transport of hazardous materials and risk of dam failure.
The Risk Prevention Plans (RPPs) were established by the law of 2 February 1995 on strengthening the protection of the environment. The PPR tool is inserted in the framework of the law of 22 July 1987 on civil security organisation, forest protection against fire and the prevention of major hazards. L' development of a PPR is the responsibility of the State. It is decided by the Prefect.Qu' they are natural, technological or multi-hazard, the risk prevention plans have similarities.
They contain three categories of information:
— Regulatory mapping results in a geographical delimitation of the territory concerned by the risk. This delimitation defines areas in which specific regulations apply. These regulations have easement value and impose requirements varying according to the level of hazard to which the area is exposed. The zones are represented on a zoning plan that fully covers the perimeter of the study.
— The hazards to the origin of the risk appear in documents d' hazard which may be inserted in the submission report or annexed to the PPR. These documents are used to map the different levels of ' intensity of each hazard taken into account in the risk prevention plan.
— The issues identified at the time of the development of the RPP can also be annexed to the approved document in the form of maps.
These similarities between the different types of PPR and the desire to achieve a good level of standardisation of PPR data have led COVADIS to opt for a single data standard, sufficiently generic to treat the different types of risk prevention plan (PPRN natural risk prevention plans, PPRT technological risk prevention plans)
This data standard does not consist of a complete modelling of a risk prevention plan file. The scope of this document is limited to the geographical data contained in the PPRs that are regulatory or not. The PPR standard is also not intended to standardise the knowledge of hazards.
The challenge is to have a description for a homogeneous storage of the geographical data of the PPRs because these data are of interest to several occupations within the ministries responsible for agriculture, on the one hand, and of the #x27; ecology, and sustainable development, on the other hand.
__Origin__
Genealogy not provided
__Partner organisations__
DDTM Landes
__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-ldd-d922992b-2c91-4407-9798-a1b629e3c756)
* [services of the State of Haute-Savoie](http://www.haute-savoie.gouv.fr/Politiques-publiques/Environnement-risques-naturels-et-technologiques/Prevention-des-risques-naturels/Donnees-communales-plans-de-prevention-des-risques-naturels/SAINT-GERVAIS-LES-BAINS)
* [COVADIS data standard: Risk Prevention Plan PPRN PPRT](http://geostandards.developpement-durable.gouv.fr/afficherPageStandard.do?lot=Plan-de-prevention-des-risques-PPRN-PPRT)
[See this page on geo.data.gouv.fr](https://geo.data.gouv.fr/fr/datasets/2e4eff4ce7069ae6c5dfad33b598fdca7d65a79f)
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.