Simple download service (Atom) of the dataset: Perimeter of the Flood Risk Territories (TRI) — Cycle 1 (2012) of the Rhine-Meuse Basin
Open data API in a single place
Provided by BUREAU DE RECHERCHES GÉOLOGIQUES ET MINIÈRES
Get early access to Simple download service (Atom) of the dataset: Perimeter of the Flood Risk Territories (TRI) — Cycle 1 (2012) of the Rhine-Meuse Basin API!
The identification of areas with significant flood risk (TRI) is based on the results of the Preliminary Flood Risk Assessment (EPRI), carried out at the level of each river basin district. It is also based on the national criteria for characterising the importance of the flood risk, as defined in the Ministerial Order of 27 April 2012, and takes into account, where appropriate, local particularities, such as the dangerous nature of the flood and any other local factors likely to aggravate the potential negative consequences associated with floods for human health, the environment, property including cultural heritage and economic activity. The list of IRRs drawn up by the competent authority at this scale, the Basin Coordinating Prefect.
With a high urban population density, IRRs receive special attention from public authorities to reduce the cost of flood damage.
To this end, the 12 IRRs identified in 2012 (cycle 1 of the Flood Directive) in the Rhine-Meuse Basin are subject to:
— a mapping of the risks to flood phenomena characterising the territory;
— local flood risk management strategies at the level of the watersheds concerned
A “DISTRICT” field has been added to the GIS layer so that the different river basin districts including IRRs can be discerned.
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.