Risk prevention plan PPRN field movement of Val de Creuse Val d'Anglin

Open data API in a single place

Provided by DDT Indre

Get early access to Risk prevention plan PPRN field movement of Val de Creuse Val d'Anglin API!

Let us know and we will figure it out for you.

Dataset information

Country of origin
Updated
2017.08.31 22:00
Created
2017.08.31
Available languages
English
Keywords
inspire, zones-de-gestion-de-restriction-ou-de-reglementation-et-unites-de-declaration, donnees-ouvertes
Quality scoring

Dataset description

The COVADIS data standard on risk prevention plans includes all technical and organisational specifications for storing spatial data represented in the risk prevention plans (RPPs) in digital format. The main risks comprise the eight main natural risks foreseeable on the national territory: floods, earthquakes, volcanic eruptions, land movements, coastal risks, avalanches, forest fires, cyclones and storms, and four technological risks: nuclear risk, industrial risk, the risk of transport of dangerous goods and the risk of dam failure.The risk prevention plans (PPR) were established by the Act of 2 February 1995 on the strengthening of environmental protection. The PPR tool is part of the law of 22 July 1987 on the organization of civil security, the protection of the forest against fire and the prevention of major risks. The development of a PPR falls within the competence of the State. It is decided by the Prefect.Whether natural, technological or multi-hazard, 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 the value of easement and impose requirements that vary according to the level of hazard to which the area is exposed. Areas are represented on a zoning plan that fully covers the study area.• The hazards causing the risk are listed in hazard documents that can be included in the submission report or appended to the RPP. 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 during the development of the PPR 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 deal with 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 modeling of a risk prevention plan file. The scope of this document is limited to the geographic data contained in the RPPs, whether regulatory or not. The PPR standard is also not intended to standardize knowledge of hazards.The challenge is to have a description for a homogeneous storage of PPR geographical data because these data concern several professions within the ministries in charge of agriculture, on the one hand, and ecology, and sustainable development, on the other hand.
European data infrastructure with broad catalog discovery, free evaluation access and production-grade API options.
190K+
indexed dataset pages
32
countries and EU institutions
2019
API-first since
Free API quota
for evaluation and prototypes
SLA
history and push on production APIs
FAQ

Questions before production use

Practical answers on evaluation, licensing, freshness, versioning and support.

api.store is built and operated by Apitalks s.r.o. Company details and a direct contact path are linked in the footer for vendor checks and procurement review.
Yes. Selected APIs include a free API quota, so your team can validate coverage, freshness, response shape and workflow fit before asking for a production plan.
Often yes, but usage rights depend on the source license and dataset. We surface source, license and update metadata where available, and can help review terms before a production integration.
Maintained APIs include update metadata where available. For production integrations, we can add history, monitoring and push updates so changes are easier to detect and act on.
Production APIs can add SLA, stable identifiers, versioning support, history, push updates and direct support around the data your product or AI workflow depends on.

Didn't find the API you need?

Let us know and we will figure it out for you.

European data discovery with free evaluation access and production-grade API options.

Copyright © 2026. Made by Apitalks