Data batch direct download service (WFS): Plan for the Prevention of Natural Risks of the Alpes de Haute-Provence (PPRN) — Data package: multi-risk + IF + RGA + IVD + PSS Durance
Open data API in a single place
Provided by BUREAU DE RECHERCHES GÉOLOGIQUES ET MINIÈRES
Get early access to Data batch direct download service (WFS): Plan for the Prevention of Natural Risks of the Alpes de Haute-Provence (PPRN) — Data package: multi-risk + IF + RGA + IVD + PSS Durance API!
Regulatory zoning of approved PPRNs, digitised to the parcel.
A PPRN may consist of one or more different paper plan(s): 1 multi-hazard plan + 1 IF plan (forest fire) + 1 RGA plan (removal of clays)+ 1 IVD plan (other miscellaneous risks).
Each paper plan resulted in the production of a geographical layer, which corresponds to zoning by hazard type.
4 different layers were produced:
— N_ZONE_REG_PPRN_S_004 for the multi-risk plan
— N_ZONE_REG_PPRN_IF_S_004 for forest fire risk when treated on a separate paper plan,
— N_ZONE_REG_PPRN_RGA_S_004 for clay removal/swelling risk when treated on a separate paper plan,
— N_ZONE_REG-PPRN_DIV_S_004 for another risk when treated on a separate paper plan,
There can therefore be between 1 and 4 layers that overlap depending on the municipality.
It is necessary to download the 4 layers to have all the regulatory information.
Layer structuring is in accordance with the COVADIS standard.
Some municipalities along the Durance are also concerned by the Durance submersible surface plan (PSS approved on 01/04/1961), which is PPRN and remains applicable as long as a new PPRN taking into account flood risk has not been approved in the municipality.
This layer was also associated with the data batch.
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.