Report Water Framework Directive 2010: summaries on the chemical status of groundwater bodies by WFD basin

Open data API in a single place

Provided by Système d'Information sur l'Eau

Get early access to Report Water Framework Directive 2010: summaries on the chemical status of groundwater bodies by WFD basin API!

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

Dataset information

Country of origin
Updated
Created
2012.05.01
Available languages
English
Keywords
reunion, adour-garonne, eau-superficielle, loire-bretagne, donnees-qualitatives, qualite-et-surveillance-de-leau-programmes-de-surveillance-reseaux-de-mesure, eaux-souterraines, france-entiere, zones-de-gestion-de-restriction-ou-de-reglementation-et-unites-de-declaration, rhone-mediterranee, substance-dangereuse, pesticide, hydrologie, pollution-des-cours-deau, pollution-par-lagriculture, france-metropolitaine, cadre-reglementaire-donnees-issues-de-rapportages-collecte-de-donnees-pour-les-indicateurs, hvd, guadeloupe, zone-protegee, eau-souterraine, substance-toxique, gouvernance-et-gestion-integree-de-leau-politique-publique, artois-picardie, cours-deau, corse, protection-de-lenvironnement, donnees-ouvertes, seine-normandie, polluant-de-leau, impact-sur-lenvironnement, qualite-de-lenvironnement, eaux-interieures, pollution-de-leau, mayotte, eau, donnees-descriptives, rhin-meuse, etat-du-milieu-qualite-quantite, guyane, observation-de-la-terre-et-environnement, politique-communautaire-de-lenvironnement, martinique
Quality scoring

Dataset description

These synthesis datasets provide information on the chemical status of groundwater bodies. For each body of water the table contains the fields: -EURBDCode: basin code, -EUGroundWaterBodyCode: water body code, -GWB_NAME: name of the body of water, -LinkSurfaceWaterBodies: link with bodies of surface water; -LinkTerrestrialEcosystems: link with terrestrial ecosystems; -ValueChemicalStatus: chemical status, -Objective_BE_chim: target date for good chemical status. It shall be indicated for each of the following elements if it is decommissioning for good chemical status: -environmental: failure to achieve environmental objectives in association with surface water bodies or significant decrease in the chemical or ecological status of such surface water bodies or significant decrease in the chemical or ecological status of such associated surface water bodies, -exceedance: non-compliance with one or more quality standards or threshold values, -human impairment: significant harm to human use, -saline intrusions: intrusion of salt water or other, -terrestrial: significant alterations in terrestrial ecosystems that are directly dependent on the groundwater body, -water quality: deterioration of the quality of water intended for human consumption, -pollutant risk: significant environmental risk due to pollutants passing through the water body, -QE1 -> QE3.9: quality elements determining the non-achievement of good chemical status, -OtherRelevantPollutantCASNumber: CAS code of other pollutants, -OtherRelevantPollutantName: names of other pollutants. Good chemical status is defined by principles equivalent to those defining good quantitative status of groundwater (paragraph 2.3.2 of Annex V to the WFD): " The chemical composition of the groundwater body shall be such that the concentrations of pollutants: – do not show effects of a salty or other invasion; – do not exceed the quality standards applicable under other relevant Community legislation in accordance with Article 17; – are not such as to prevent the achievement of the environmental objectives for the associated surface waters, to cause a significant decrease in the ecological or chemical quality of those bodies or to cause significant damage to terrestrial ecosystems directly dependent on the body of groundwater.’
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