Groundwater bodies – Guadeloupe – Version Reporting 2016

Open data API in a single place

Provided by International Office for Water (IOW)

Get early access to Groundwater bodies – Guadeloupe – Version Reporting 2016 API!

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

Dataset information

Country of origin
Updated
Created
2017.04.23
Available languages
English
Keywords
données ouvertes, VRAP, hvd, Données de références (référentiels, vocabulaire contrôlé), Eaux souterraines (nappes d’eau), GLP, DCE, FRANCE, GUADELOUPE
Quality scoring

Dataset description

A groundwater body is a separate volume of groundwater within one or more aquifers, constituting the elemental division of aquatic environments intended to be the assessment unit of the WFD. It makes it possible to define environmental objectives, assess the state of the environment and subsequently verify the achievement of these objectives. Groundwater bodies, based on the work carried out on the BDRHF V1 hydrogeological benchmark, were first identified and demarcated in 2004 and then updated in 2010. They were the subject of a report to the European Commission on the implementation of the WFD on 22 March 2010, then a corrective report in February 2011, taking into account the latest updates. A draft version defined for the 2013 inventory was published in 2015. The version now available on the SANDRE website is in line with the 2016 report. The next version of the Water mass repository (temporary water mass, defined for the State of the Places) is planned for 2019. The layers are distributed in a format conforming to the SANDRE Data Dictionary of the Reference Water Body, version 1.3. The cut-off for water bodies meets the following key principles: Water bodies are delimited on the basis of geological and hydrogeological criteria, The redistribution of water bodies to take into account the effects of anthropogenic pressures must remain limited. The boundaries of water bodies must be stable and durable Like surface water bodies, the delimitation of groundwater bodies is organised from a typology. This typology is largely inspired by that developed for hydrogeological entities defined as part of the revision of the RHF DB. It is based on the geological nature and the hydrodynamic or “large” behavior of aquifer systems (nature, flow rate). It includes two levels of characteristics, principal and secondary. Water bodies can have exchanges between them. All Potable Water Supply Captures, providing more than 10 m³/day of drinking water or used for the water supply of more than 50 people, must be included in a water body. Deep groundwater, unrelated to watercourses and surface ecosystems, in which no sampling takes place and which is not likely to be used for drinking water because of its quality (salinity, temperature, etc.), or for technical-economic reasons (cost of disproportionate 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 bodies of water can be superimposed.
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