Groundwater bodies - Martinique - State of the Places Version 2013

Open data API in a single place

Provided by International Office for Water (IOW)

Get early access to Groundwater bodies - Martinique - State of the Places Version 2013 API!

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

Dataset information

Country of origin
Updated
2014.06.18 00:00
Created
Available languages
English
Keywords
VEDL, données ouvertes, FRANCE, EAU SOUTERRAINE, HYDROGEOLOGIE, MARTINIQUE, hvd
Quality scoring

Dataset description

A body of groundwater is a separate volume of groundwater within one or more aquifers, constituting the basic delineation of aquatic environments intended to be the unit of assessment for the WFD. It makes it possible to define environmental objectives, to assess the state of the environment and subsequently to verify the achievement of these objectives. Groundwater bodies, based on the work carried out on the BDRHF V1 hydrogeological repository, were identified and delineated for the first time in 2004 and were updated in 2010. They were the subject of a report to the European Commission on the implementation of the WFD on 22 March 2010, followed by a corrective report in February 2011, taking into account the latest updates. At the beginning of 2013, work was carried out to bring the European version of February 2011 into line with the Sandre format. This version is still published on the SANDRE website; however, it contains a number of anomalies, present in the reported data, and highlighted in report BRGM/RP-62141-EN. These anomalies have been corrected in this version of the Water mass reference system: The "internal 2013 water body repository" in its version results from the update of the State of Places, in accordance with the Sandre data models and consolidated at the national level, on the website www.sandre.eaufrance.fr. This version of the reference system comes from the State of Places 2013 and is not reported to the European Commission. This version used at national level makes it possible to prepare the SDAGE 2016-2021. Layers shall be disseminated in a format compliant with the SANDRE Data Dictionary of the Water Body Repository, version 1.2. The water bodies are divided according to the following main principles: Water bodies shall be demarcated on the basis of geological and hydrogeological criteria. Redistribution of water bodies to take account of the effects of anthropogenic pressures must remain limited. Boundaries of water bodies must be stable and sustainable Like bodies of surface water, the delimitation of bodies of groundwater is organised on the basis of a typology. This typology is largely inspired by the one developed for hydrogeological entities defined in the context of the revision of the HFR DB. It is based on the geological nature and hydrodynamic behavior or "large" operation of aquifer systems (nature, flow velocity). It includes two levels of characteristics, primary and secondary. Water bodies can trade with each other. All abstractions for drinking water supply, supplying more than 10 m3/day of drinking water or used for the supply of water to more than 50 persons, must be included in a body of water. Deep groundwater, unrelated to rivers and surface ecosystems, from which no abstraction takes place and which is not likely to be used for drinking water because of its quality (salinity, temperature, etc.), or for technical and economic reasons (disproportionate cost of abstraction) may not constitute water bodies. Given its size, a body of water may have a certain spatial heterogeneity in terms of both its hydrogeological characteristics and its qualitative and quantitative status. At any point several water bodies may overlap.
European data infrastructure with broad catalog discovery, free evaluation access and production-grade API options.
190K+
indexed dataset pages
32
countries and EU institutions
2019
API-first since
Free API quota
for evaluation and prototypes
SLA
history and push on production APIs
FAQ

Questions before production use

Practical answers on evaluation, licensing, freshness, versioning and support.

api.store is built and operated by Apitalks s.r.o. Company details and a direct contact path are linked in the footer for vendor checks and procurement review.
Yes. Selected APIs include a free API quota, so your team can validate coverage, freshness, response shape and workflow fit before asking for a production plan.
Often yes, but usage rights depend on the source license and dataset. We surface source, license and update metadata where available, and can help review terms before a production integration.
Maintained APIs include update metadata where available. For production integrations, we can add history, monitoring and push updates so changes are easier to detect and act on.
Production APIs can add SLA, stable identifiers, versioning support, history, push updates and direct support around the data your product or AI workflow depends on.

Didn't find the API you need?

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

European data discovery with free evaluation access and production-grade API options.

Copyright © 2026. Made by Apitalks