Area exposed to one or more hazards represented on the hazard maps used for risk analysis of the RPP.
Hazard maps are the result of the study of hazards whose objective is to assess the intensity of each hazard at any point in the study area. The evaluation method is specific to each hazard type. It leads to the delimitation of a set of areas on the study perimeter constituting a zoning graduated according to the level of the hazard. The allocation of a hazard level at a given point in the territory takes into account the probability of occurrence of the dangerous phenomenon and its degree of intensity.
For multi-random PPRNs, each zone is usually identified on the hazard maps by a code for each hazard to which it is exposed.
All hazard areas represented on the hazard maps are included. Areas protected by protective structures must be represented (possibly in a specific way) as they are always considered subject to hazard (case of breakage or inadequacy of the structure).
Hazard zones can be described as developed data to the extent that they result from a synthesis using multiple sources of calculated, modelled or observed hazard data. These source data are not concerned by this class of objects but by another standard dealing with the knowledge of hazards.
Some areas within the study area are considered “no or insignificant hazard zones”. These are the areas where the hazard has been studied and is nil. These areas are not included in the object class and do not have to be represented as hazard zones. However, in the case of natural RPPs, regulatory zoning may classify certain areas not exposed to hazard as prescribing areas (see definition of the PPR class).
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.