Surface Hydrographic Entities — Meeting 2012 — CD Carthage

Open data API in a single place

Provided by International Office for Water (IOW)

Get early access to Surface Hydrographic Entities — Meeting 2012 — CD Carthage API!

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

Dataset information

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

Dataset description

The main concept of hydrographic cutting is the hydrographic entity defined by Circular No. 91-50. The hydrographic entity is a natural or managed watercourse, a natural or managed arm, an artificial waterway (channel,...), a body of water or a coastal line. The nature of a hydrographic entity is not constant throughout the entity. For example, a natural stream can be built on a part. All these changes can be identified by distinguishing sub-miliosities on the entity. Hydrographic entities are broken down into two types: — linear hydrographic entities or streams, — surface hydrographic entities corresponding to water bodies and linear entities whose wide areas (above 50 metres) are represented by surface elements. A surface hydrographic entity can be crossed by a watercourse, which will be named the main stream. Each entity is identified by a unique generic code at national level. This 8-position alphanumeric code consists of dashes and characters. For example, a watercourse that crosses several zones or subsectors will have a generic code in the format of the following generic codes “V12-4000” or “R5--0420” (see below for the construction rule). In addition, a hydrographic entity has a so-called principal name. Construction rule for the generic hydrographic entity code: Each hydrographic entity shall be assigned a unique 3-digit number (5, 6 and 7 characters) for the medium and the hydrographic area(s) to which it belongs: this is the number of the hydrographic entity. A hydrographic entity belonging to several zones shall retain its entity number in all the areas concerned. Two hydrographic entities of the same medium belonging to two different sub-mills will have separate entity numbers. The first four characters of the generic code correspond to all invariant codes of the hydrographic zones, the rest of the characters being replaced by ‘-’ dashes. For example, the “Viveronne” watercourse has the entity number: 050 and for middle code: 0. This watercourse is located within a single hydrographic area: P737. His generic code is therefore: P7370500 The entity number of the river “La Dronne” is: 025 and for middle code: 0. This stream crosses several hydrographic areas (even several subsectors): P746,P744, P742, P70, P734, P731, P730, P716, P715, P714, P711, P710, P702, P701, P700. Of these codes, only the two characters are invariant. His generic code is therefore: P7--0250 Similarly, Garonne has as its entity number: 000 and for middle code: 0. This course crosses several hydrographic sectors (while starting with “0”. Its generic code is: 0---00000 A surface hydrographic entity is a hydrographic entity consisting of water bodies and linear entities whose broad areas (above 50 metres) are represented by surface elements. A hydrographic entity is broken down into surface hydrographic elements. In some cases, a surface hydrographic entity may be crossed by one or more streams — water bodies. However, it is held that only one hydrographic entity, known as the main watercourse of the water body. On the other hand, a hydrographic entity may be crossed/contained by a set of elementary sections. The BDCarthage Guadeloupe is maintained by DEAL Guadeloupe. The structure of the database is identical to the metropolitan format.The Carthage Guadeloupe BD is a version validated by the EIS but not by the IGN and therefore problems of incompatibility with IGN referentials can occur (and that an update “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