Hazard Zones of the Saône Flood Risk Prevention Plan — Sector 2

Open data API in a single place

Provided by etalab

Get early access to Hazard Zones of the Saône Flood Risk Prevention Plan — Sector 2 API!

Let us know and we will figure it out for you.

Dataset information

Country of origin
Updated
2020.02.29 06:56
Created
2015.06.27
Available languages
French
Keywords
ddt-54, geoscientific-information, passerelle-inspire, donnees-ouvertes, risque-technologique
Quality scoring
145

Dataset description

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' Assignment of'A level of #x27;aira 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 map d'a 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 to be subject to the hazard (case of rupture or d' inadequacy of l’' structure). 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 null 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 unknown) or by a polygon (especially from the grey area of the PPRT). 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?#x27; using its identifier (and thus avoid unnecessary duplication); — it does not exist because the origin of the risk cannot be precisely defined or localised (e.g. earthquakes, avalanches, marine submersions, etc.). However, as it is in practice rare to benefit from stable references to external objects, the geometry of the risk will often result from the duplication of that of l’' object representing l' origin of risk. __Partner organisations__ DDT Saône-et-Loire, DDT Meurthe-et-Moselle __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-a2fa282e-78a3-4c18-a795-5b16353f6951) * [Consulta Map'Risks](http://carto.geo-ide.application.developpement-durable.gouv.fr/595/RISQ_CONSULT.map) [See this page on geo.data.gouv.fr](https://geo.data.gouv.fr/fr/datasets/cfe3fadf78a0d85f5e14313fa971618e637c9094)
Build on reliable and scalable technology
Revolgy LogoAmazon Web Services LogoGoogle Cloud Logo
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.

Didn't find the API you need?

Let us know and we will figure it out for you.

API Store provides access to European Open Data via scalable and reliable REST API interface.
Copyright © 2024. Made with ♥ by Apitalks