Simple download service (Atom) of the dataset: Risk — TRI Loir — IsoClasses Height Zones (ICZ) for a water level of 1.70 in Chateaudun en Loir-et-Cher
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: Risk — TRI Loir — IsoClasses Height Zones (ICZ) for a water level of 1.70 in Chateaudun en Loir-et-Cher API!
Tables of areas in which a hazard of a certain type under a certain scenario causes a rise of water whose height is within a fixed range of values.
Spatial data set produced by the GIS High Flood Risk Land Flood Directive (TRI) of... and mapped for reporting purposes for the European Flood Directive.
European Directive 2007/60/EC of 23 October 2007 on the assessment and management of flood risks (OJ L 288, 06-11-2007, p. 27) influences the flood prevention strategy in Europe. It requires the production of flood risk management plans to reduce the negative consequences of flooding on human health, the environment, cultural heritage and economic activity.
The objectives and implementation requirements are set out in the Law of 12 July 2010 on the National Commitment for the Environment (LENE) and the Decree of 2 March 2011. In this context, the primary objective of flood and flood risk mapping for IRRs is to contribute, by homogenising and objectivating knowledge of flood exposure, to the development of flood risk management plans (WRMs).
This dataset is used to produce flood surface maps and flood risk maps that represent flood hazards and issues at an appropriate scale, respectively. Their objective is to provide quantitative evidence to further assess the vulnerability of a territory for the three levels of probability of flooding (high, medium, low).
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.