Groundwater body HWRM-RL 2. cycle

Open data API in a single place

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

Get early access to Groundwater body HWRM-RL 2. cycle API!

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

Dataset information

Country of origin
Updated
2024.11.12 07:15
Created
2019.12.22
Available languages
English
Keywords
regional, hochwasserrisiko, gewässereinzugsgebiet, gefährdetes-gebiet, opendata, flood-directive, risikoanalyse, hwrm-rl, gefahrenabwehr, eu-hochwasserrisikomanagement-richtlinie, units-of-management, hochwasser, risikogebiet, risikomanagement, hochwassermodell
Quality scoring

Dataset description

The flood risk management guideline (HWRM-RL) 2. Cycle 2016 - 2021 identified potentially affected groundwater bodies for the flood load cases HQfrequently, HQ100, HQextrem. Cycle of the HWRM-RL.The catchment areas of the major rivers (river basin districts) have been subdivided into sub-basins. Within the sub-basins, the groundwater bodies were defined according to hydraulic boundaries and hydrogeological criteria. The above-ground watersheds were used as the above-current boundary and the relevant floodwaters as the under-current boundary. It was assumed that the watersheds of the above-ground waters also reflect the underground watersheds on a large scale.
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