Aquitaine: Sorting of Bordeaux (marine submersion hazard) — Geolocated data produced by the GIS Flooding Directive of Bordeaux at risk of flooding
Open data API in a single place
Provided by etalab
Get early access to Aquitaine: Sorting of Bordeaux (marine submersion hazard) — Geolocated data produced by the GIS Flooding Directive of Bordeaux at risk of flooding API!
The flood and flood maps of the TRI were approved on 03 December 2014 by Prefectural Decree No. 2014337-0002.
The Geostandard Flood Directive describes the basis of geographic data produced on territories at significant risk of flooding (TRI) and mapped for reporting purposes for the European Flood Directive. European Directive 2007/60/EC of 23 October 2007 on the risk assessment and management of risks in Europe (OJ L 288, 06-11-2007, p. 27) influences the flood prevention strategy in Europe by requiring the production of flood risk management plans on each river basin district. Article 1 of the Flood Directive specifies its objective of establishing a framework for the assessment and management of flood risks, which aims to reduce the negative consequences of flooding on human health, the environment, cultural heritage and economic activity. The objectives and requirements for achievement are given by the Law of 12 July 2010 on the National Commitment for the Environment (LENE) and the Decree of 2 March 2011. Within this framework, the main objective of the mapping of floodable surfaces and risks of ' flooding for IRRs is to contribute, by homogenising and objecting knowledge of the #x27th; exposure of issues to floods, to the drafting of flood risk management plans (FRPs), to the definition of the objectives of this plan and to the development of local strategies by TRI. Thus, this Geostandard aims to:
1. homogenise the production of data used for flood surface and flood risk maps,
2. facilitate the establishment of a GIS on each IRR.
This GIS Flood Directive should become a living reference for knowledge of the hazards and risks of flooding on these IRRs and will be used to establish flood risk management plans. IRR SGIs will be integrated into a national common GIS.
__Origin__
This dataset is the result of the process of mapping floodable surfaces and the risks of flooding on the TRI.
It includes geographic data for each scenario of flooding:
— floodable surfaces,
— flood protection works,
— zones subtracted from #x27; flooding by the presence of #x27; protective structure,
— the social challenges (number of inhabitants, number of jobs) measured for each IRR municipality,
— the issues relating to goods and services required by the Flood Directive.
Detailed genealogy information is provided in the report accompanying the maps and the GIS Flood Directive. This information explains the choices made on data and production methods.
__Partner organisations__
DREAL Nouvelle-Aquitaine/MiCAT/PIG
__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-ldd-4cad139d-342f-482a-877e-f0ddddfdc8c8)
* [webpage of the implementation of the IRR Flood Directive](http://www.aquitaine.developpement-durable.gouv.fr/tri-de-bordeaux-a1679.html)
* [dynamic mapping](http://carmen.developpement-durable.gouv.fr/6/carte_DI_TRI_BORD_S.map)
* [report d' accompaniment to the TRI](http://www.aquitaine.developpement-durable.gouv.fr/IMG/pdf/RAP-ACC_Bordeaux_sept2014-reduit_cle7c521a.pdf)
[See this page on geo.data.gouv.fr](https://geo.data.gouv.fr/fr/datasets/eb6571a93d7a678698669193303d6eb15983c2f2)
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.