Hydrographic subsectors — Martinique 2004 — BD Carthage

Open data API in a single place

Provided by International Office for Water (IOW)

Get early access to Hydrographic subsectors — Martinique 2004 — BD Carthage API!

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

Dataset information

Country of origin
Updated
2014.03.11 00:00
Created
Available languages
English
Keywords
MARTINIQUE, données ouvertes, EAU DE SURFACE, FRANCE, BD Carthage, hvd
Quality scoring

Dataset description

The hydrographic division is the set of four hierarchical partitions of the French territory carried out according to descending hydrographic areas: — hydrographic region (1st order), — hydrographic sector (2nd order), — hydrographic subsector (3 rd order), hydrographic area (4th order). A hydrographic region is divided into a maximum of 10 sectors. The list of hydrographic regions was adopted in Circular No. 91-50 of 12 February 1991 but the determination of their boundaries is under the responsibility of the Water Agencies. Geometry is close to the IGN BDTopo which was used for its realisation.BDCarthage Réunion is maintained by DEAL Réunion.The Carthage Réunion BD is a version validated by the SIE but not by the IGN and therefore problems of incompatibility with IGN referentials can occur (and that an update will “officialise” the Carthage BD with IGN validation).
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