Natural or technological risk prevention plans are one of the tools of the State’s risk prevention policy. The RPP is a regulatory prevention record that communicates risk areas to populations and planners and identifies measures to reduce vulnerability. A PPR contains geographic data on a given territory that is very useful for crisis management, land or real estate management and urban planning. However, a PPR is not an operational crisis management document. Approved planning documents must include an annex to the RPP’s zoning plan as soon as the RPP is approved. The Risk Prevention Plan (RPP) standard should be used for data exchange between actors in these different areas. The data standard shall improve the availability of spatial data produced under the PPRT or PPRN procedures.
A few simple use cases have been identified:
• define a PPR data exchange scenario using shared structuring rules;
• homogenise service practices and improve the exchange of data between actors in their different fields of application;
• propose technical specifications to structure the spatial data produced at the time of the development of the RPP;
• facilitate mapping of prescribed or approved major hazard prevention plans in a given territory;
• distribute to the public maps of the regulatory areas of the RPPs and the areas subject to hazard in a homogeneous manner;
• keep track of the hazards and issues that have been used to develop the zoning plan and RPP regulations.
These data are interesting, especially in the case of a revision of the RPP. While this data is required in the departmental data infrastructure, another issue of this standard is to facilitate the transfer of RPP data to risk awareness and risk prevention policy monitoring applications.
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.