Water bodies Watercourses — Version Reportage 2016 — France Whole

Open data API in a single place

Provided by International Office for Water (IOW)

Get early access to Water bodies Watercourses — Version Reportage 2016 — France Whole API!

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

Dataset information

Country of origin
Updated
Created
2021.06.09
Available languages
English
Keywords
FRA, VRAP, Données de références (référentiels, vocabulaire contrôlé), données ouvertes, Eaux intérieures de surface (rivières et lacs), DCE, hvd, FRANCE
Quality scoring

Dataset description

A river water body is a distinct and significant part of surface waters such as a river, river or canal, part of a river, river or canal, constituting the elementary division of aquatic environments intended to be the WFD assessment unit. River bodies are derived from the BDCarthage® v3 hydrographic theme of BDCarto®. The criteria for the realisation of river water bodies are: — A body of water belongs to a single hydroecoregion — The dominant fish stand based on the fish context (Salmonicole, cypriniculture, Intermediate) — Size class (strahler confluence band) The water body code is structured as follows: Water body type code + Basin code (district as defined in dce) + Increment DCE reporting correspondence: this entity corresponds to WISE’s River Water Body (RWBODY) concept.
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