Risk Prevention Plans (RPPs) are the key government instrument for risk prevention. Their objective is to control development in areas at risk.
The development of a risk prevention plan generates a set of spatial data organised into several data sets. The same PPR may include spatial datasets containing:
— main scopes of the RPP;
— restricted areas of the plan once approved. RPP regulations generally distinguish between ‘construction ban areas’, so-called ‘red areas’, where the hazard level is high and where the general rule is the construction ban; ‘areas subject to requirements’, known as ‘blue zones’ where the hazard level is medium and projects are subject to requirements adapted to the type of issue and areas not directly exposed to risks but subject to prohibitions or prescriptions;
— hazard areas represented on the map of hazards used for risk analysis by crossing with the stakes, specifying for each zone the level of the hazards to which it is exposed;
— issues which are persons, property, activities and elements of cultural or environmental heritage threatened by a hazard and likely to be affected or damaged by it;
— origins of risk, i.e. the entity of the real world which, through its presence, represents a potential risk. This entity may be characterised by a name, a reference to an external object or a geographical object that locates the actual entity causing the risk.
Each element in the same PPRN dataset is bound by the GASPAR format identifier “ddd[PREF|DDT|DDT|DREAL]aaaannnn” (AAAA and NNNN correspond to the reference year and the order number of the PPR procedure associated in GASPAR) to a single object in the PPRN document table described by the N_DOCUMENT_PPRN metadata sheet.
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.