Plan for the prevention of natural hazards of movement of land — Municipality of Montjoi — Area of hazard — Department of Tarn-et-Garonne
Open data API in a single place
Provided by etalab
Get early access to Plan for the prevention of natural hazards of movement of land — Municipality of Montjoi — Area of hazard — Department of Tarn-et-Garonne API!
Area exposed to one or more hazards shown on the hazard map used for PPR risk analysis.
The map d'random is the result of the study of hazards whose goal is to evaluate the intensity of each hazard at any point in the zone of study. The evaluation method is specific to each type of hazard. It leads to the delimitation of a set of zones on the perimeter d'study constituting a graduated zoning according to the level of l'aira. L' attribution of Â#x27;A level of #x27; hazard at a given point in the territory takes into account the probability of #x27; occurrence of the dangerous phenomenon and its degree of Â#x27; intensity.
For multi-random PPRNs, each zone is usually spotted on the d'aira map by a code for each hazard to which it is exposed.
All hazard zones shown on the hazard map are included. Areas protected by protective works must be represented (possibly specifically) because they are always considered subject to the hazard (case of rupture or d' inadequacy of the work).
Hazard zones can be described as elaborated data as they result from a synthesis using several calculated, modelled or observed data sources. These source data are not affected by this class of objects but by another standard dealing with the knowledge of hazards.
Some areas of the perimeter of the study are considered “zero or insignificant hazard zones”. It is the areas where the hazard has been studied and is zero. These zones are not included in class d'objects and n'are not to be represented as zones d'aira. However, in the case of natural PPRs, regulatory zoning may classify certain areas not exposed to the hazard zone as a prescribing zone (see ZonePPR class definition).
__Origin__
The geometric modeling of ' entity at ' origin of risk depends on the type of risk, the context of the PPR, the nature of the generator and its modeling in the data source or geographical repository from which it originates. For example, a water course may be represented by a polygon or a polyline according to its size and width, an ICPE by a point (if the location of its enclosure is not known) or by a polygon (especially from the grey area of the PPR).The geometry of this class d' objects is optional when: — this geometry is already carried by an object d'a geographical repository or d' an external data source, to which it is then recommended to refer to the ' help of its identifier (and thus avoid unnecessary duplication);- it does not exist because the origin of the risk cannot be precisely defined or localised (c' is the case of certain risks such as, for example, earthquakes, avalanches, sea submersions...)Nevertheless, as it is in practice rare to benefit from stable references to external objects, the geometry of l' origin of the risk will often result from the duplication of that of the #x27; object representing the #x27; origin of the risk.
__Partner organisations__
DDT Tarn-et-Garonne
__Links annexes__
* [XML metadata view](http://ogc.geo-ide.developpement-durable.gouv.fr/csw/all-dataset?REQUEST=GetRecordById&SERVICE=CSW&VERSION=2.0.2&RESULTTYPE=results&elementSetName=full&TYPENAMES=gmd:MD_Metadata&OUTPUTSCHEMA=http://www.isotc211.org/2005/gmd&ID=fr-120066022-jdd-67d8213d-0e81-4128-ac7c-e22a9f83d13a)
* [COVADIS data standard: One-off entity at the origin of the risk of a PPRN](http://geostandards.developpement-durable.gouv.fr/afficherPageStandard.do?jeu=N_ORIG_RISQ_PPRN_AAAANNNN_P)
[See this page on geo.data.gouv.fr](https://geo.data.gouv.fr/fr/datasets/c9f898214bf0b0ccfa183434643cc7cb292e58ca)
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.