Soil hazard — water erosion hazard according to DIN 19708

Open data API in a single place

Provided by Landesamt für Umwelt des Landes Schleswig-Holstein (LfU)

Get early access to Soil hazard — water erosion hazard according to DIN 19708 API!

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

Dataset information

Catalog

Landesamt für Umwelt des Landes Schleswig-Holstein (LfU) catalog

Country of origin

Germany

Updated

2026.03.26 23:00

Created

2026.02.24

Available languages

English

Keywords

din-19708, bodengefährdung, bodenerosion, erosionsgefärdung, wassererosion, erosion, karten, bodenabtrag, wassererosionsgefährdung, envi

Datasource

Official portal for European data link

Quality scoring

Dataset description

Natural (potential) water erosion hazard according to DIN 19708 (2005-02) relative to the net field block area (excluding landscape elements (usually kinks or small woods) and without ineligible areas (often ponds or similar)) in t/ha/a, calculation based on the K = soil erodibility factor (takes into account the upper soil type), S = slope inclination factor and R = surface runoff and rain erosivity factor (flat 50). The card is distributed in three scales: Field block (up to 1:199.999), overview maps in the scale ranges 1:200.000-999.999, and from 1:1 million.

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