Water bodies catchment areas (WRRL) Lower Saxony and Bremen

Open data API in a single place

Provided by Niedersächsischer Landesbetrieb für Wasserwirtschaft, Küsten- und Naturschutz (NLWKN)

Get early access to Water bodies catchment areas (WRRL) Lower Saxony and Bremen API!

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

Dataset information

Catalog

Niedersächsischer Landesbetrieb für Wasserwirtschaft, Küsten- und Naturschutz (NLWKN) catalog

Country of origin

Germany

Updated

2024.11.12 13:50

Created

2005.01.01

Available languages

English

Keywords

übergangsgewässer, oberflächenwasserkörper, bewirtschaftung-von-wassereinzugsgebieten, flusseinzugsgebiet, opendata, river-basin-district, oberflächen--und-küstengewässer, flussgebietseinheit, eg-wasserrahmenrichtlinie

Datasource

Official portal for European data link

Quality scoring

Dataset description

The smallest delimited hydrological viewing level of the WFD is the water body. These are primary/direct catchment areas of the water frame guideline water bodies of above-ground waters (WFD rivers, lakes, transitional and coastal waters) on a basic scale. Each point of Lower Saxony can be assigned exactly to a water body into which the resulting surface water drains according to terrain relief.

European data infrastructure with broad catalog discovery, free evaluation access and production-grade API options.

190K+

indexed dataset pages

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.

api.store Built by Apitalks

European data discovery with free evaluation access and production-grade API options.

About api.storePrivacy Terms of Service