Watercourses — Mayotte 2021 — BD topage ®

Open data API in a single place

Provided by International Office for Water (IOW)

Get early access to Watercourses — Mayotte 2021 — BD topage ® API!

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

Dataset information

Country of origin
Updated
Created
2021.10.27
Available languages
English
Keywords
mayotte, hvd, eaux de surface, BD Topage, france
Quality scoring

Dataset description

Mayotte BD topage ® version 2021 dataset There is no standardised definition of a river. The codification of water courses is the responsibility of the managers of the reference system (Water Agencies, in consultation with IGN-OFB-State). Coding choices are mainly influenced by a topographical approach, based on the toponymy of land where it exists. The criteria of drain length, flow rates and flow permanence may be used, in the absence of clear and convergent sources on the toponymy. One of the founding roles of the Water Information System is to propose the identification of hydrographic objects in the form of stable, consensual codes, which can be used to produce and maintain derived benchmarks, or to attach business data to them (purification stations, etc.). The choice of river is generally not influenced by one of these particular, sometimes contradictory, uses. Note: Transboundary watercourses are managed as follows: — Case of watercourses on the border (bordering): The geometry of the latter shall be fully integrated; — Case of watercourses crossing the border once: A common cross-border Hydrographic Node will be shared between the 2 countries (awaiting clear border demarcation); — Case of return rivers between the 2 countries: Its geometry will be fully integrated for the part between its first and last A/R on the border (even for the part located in the neighbouring country). Corresponds to Inspire’s Watercourse 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