(SRCE) Corridors Watercourses ensuring connections between biodiversity reservoirs

Open data API in a single place

Provided by DREAL Pays de la Loire

Get early access to (SRCE) Corridors Watercourses ensuring connections between biodiversity reservoirs API!

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

Dataset information

Country of origin
Updated
2026.03.31 20:11
Created
2026.03.31
Available languages
English
Keywords
environnement, teo, srce, trame-bleu, eau
Quality scoring

Dataset description

This table lists the different ecological corridors that ensure connections between reservoirs of biodiversity, offering species favourable conditions for their movement and the completion of their life cycle. (Article R. 317-19 III of the Environmental Code). These corridors represent principles of connection between biodiversity reservoirs. Their location must be specified at the local level. Origin Ecological corridors resulting from the second wave workshop consultation of stakeholders in the region. It was agreed that the “mesh envelopes” will be used as a medium for the identification of ecological corridors. However, level 4 forest envelopes are not retained by the expert committee. In addition, Level 3 envelopes are displayed in hatches to transcribe the diffuse character of the subtrame. The biodiversity reservoirs are represented in the same color, whether they belong to the Green Trame or the Blue Trame. Regarding the Blue Trame, the rivers of the CARTHAGE© comic strip and wetlands of national importance are proposed as ecological corridors. Fragmentation is represented in two ways: linear fragmentation (levels 1 to 3) and surface (urban task) for the Green Trame. For the Blue Trame, it is the Referential of Obstacles to the flow that is used.
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