Moorböden Kreis Kleve

Open data API in a single place

Provided by Kreis Kleve - Der Landrat

Get early access to Moorböden Kreis Kleve API!

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

Dataset information

Country of origin
Updated
2026.02.12 00:00
Created
2026.02.06
Available languages
English
Keywords
alkis, kleve, kevelaer, straelen, kataster, bedburg-hau, kranenburg, rees, issum, bodenschätzung, wallfahrtsstadt-kevelaer, moorboden, schätzung, goch, weeze, opendata, uedem, kalkar, nrw, emmerich, kreis-kleve, wachtendonk, rheurdt, liegenschaftskataster, nw, boden, bodenart, kerken, geldern, moorböden, emmerich-am-rhein, nordrhein-westfalen
Quality scoring

Dataset description

Der Layer "Moorböden Kreis Kleve" beinhaltet Moorböden für den Kreis Kleve. Die Daten stammen aus den Alkis Bodenschätzungsflächen und wurden folgendermaßen nach Moorböden unterteilt. - 5000 Moor (Mo) - 6110 Sand mit Moor (SMo) - 6120 Lehmiger Sand mit Moor (lSMo) - 6130 Lehm mit Moor (LMo) - 6140 Ton mit Moor (TMo) - 6210 Moor mit Sand (MoS) - 6240 Moor mit Ton (MoT) - 8110 Sand auf Moor (S/Mo) - 8120 Lehmiger Sand auf Moor (lS/Mo) - 8130 Lehm auf Moor (L/Mo) - 8140 Ton auf Moor (T/Mo) - 8210 Moor auf Sand (Mo/S) - 8220 Moor auf lehmigem Sand (Mo/lS) - 8240 Moor auf Ton (Mo/T) Bodenschätzungsergebnisse im Liegenschaftskataster geführt. Der Dienst ist tagesaktuell.
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