Area exposed to hazard Forest fires shown on the hazard maps “fire risk” used for the risk analysis of the RPP.
Hazard maps are the result of the study of hazards, the objective of which is to assess the intensity of each hazard at any point in the study area. The assessment method is specific to each type of hazard. It leads to the delimitation of a set of zones on the study perimeter constituting a graduated zoning according to the level of the hazard. The assignment 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 shown on the hazard maps are included. Areas protected by protective works must be represented (possibly in a specific way) because they are always considered subject to hazard (case of rupture or insufficiency of the structure).
Hazard zones can be described as elaborated data to the extent that they result from a synthesis using several calculated, modelled or observed hazard data sources. These source data are not concerned by this class of objects but by another standard dealing with the knowledge of hazards.
Some areas of the study perimeter are considered “zero or insignificant hazard areas”. These are the areas where the hazard has been studied and is zero. 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 PPRs, regulatory zoning may classify certain areas not exposed to hazard as a prescribing zone (see definition of ZonePPR 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.