Outflow development in the state of Brandenburg 1980-2009 and 1990-2009

Open data API in a single place

Provided by Landesamt für Umwelt Brandenburg (LfU)

Get early access to Outflow development in the state of Brandenburg 1980-2009 and 1990-2009 API!

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

Dataset information

Catalog

Landesamt für Umwelt Brandenburg (LfU) catalog

Country of origin

Germany

Updated

2026.02.16 00:00

Created

2011.06.30

Available languages

English

Keywords

pegel, wiski, opendata, abflussentwicklung

Datasource

Official portal for European data link

Quality scoring

Dataset description

The daily averages of outflows at a total of 59 levels were calculated for the outflow years 1976. taken from the LfU’s WISKI database until 2009. After cleaning the measurement data to fail, the annual mean value (outflow year November-October) of the outflow was calculated. For measuring points whose discharge is not yet recorded in the WISKI, other Sources, such as: German Water History Yearbook (DGJ), Water Information System (Pegelonline) and River Basin Community (FGG) Elbe, used. A trend was established from the annual averages of the outflow of the years 1980 to 2009. With the help of the trend function, a starting value for the year 1980 and a final value for the year Calculated in 2009. The calculation was also carried out for the period 1990 to 2009.

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