Soil Hesse - Site typing _Biotope development _50000

Open data API in a single place

Provided by Hessisches Landesamt für Naturschutz, Umwelt und Geologie (HLNUG)

Get early access to Soil Hesse - Site typing _Biotope development _50000 API!

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

Dataset information

Catalog

Hessisches Landesamt für Naturschutz, Umwelt und Geologie (HLNUG) catalog

Country of origin

Germany

Updated

2025.07.25 00:00

Created

Available languages

English

Keywords

regional, BFD50, Boden, HLNUG, infoMapAccessService, Hessen, inspireidentifiziert, Bodenflächendaten, Biotopentwicklung, Soil, Standorttypisierung

Datasource

Official portal for European data link

Quality scoring

Dataset description

Soil overview maps Hessen 1:500.000 and 1:50.000 as well as soil area data 1:5.000.:Location typification for biotope development in Hessen (BFD50) - The soil area data 1:50 000 (BFD50, 2. Development stage) describe the soils, their properties and soil functions on a regional scale. The present typification shows areas with special or extreme location properties, which are mainly due to the water and nutrient balance. First of all, there are differences between wet and dry locations. For the wetlands, the nature of the water supply and the annual periodicity play an important role with regard to the site properties.

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