Hunting districts Texts Kreis Kleve

Open data API in a single place

Provided by Kreis Kleve - Der Landrat

Get early access to Hunting districts Texts Kreis Kleve API!

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

Dataset information

Catalog
Kreis Kleve - Der Landrat catalog
Country of origin
Germany
Updated
Created
2025.01.07
Available languages
English
Keywords
NW, AGRI, Rheurdt, Jagdrevier, Revier, Kalkar, NRW, Wallfahrtsstadt Kevelaer, Jagdbezirke, Rees, Jagdkataster, Weeze, Gebiet, Straelen, Jagdgenossenschaften, Jagd, Eigenjagd, Uedem, Kerken, Jagdgenossenschaft, Emmerich, Kranenburg, Jagdbezirk, Bedburg-Hau, Geldern, 05154, Kleve, Wachtendonk, Landesjagdgesetz, opendata, Kevelaer, Issum, Kreis Kleve, Bundesjagdgesetz, Nordrhein-Westfalen, Emmerich am Rhein, Goch
Datasource
Official portal for European data link
Quality scoring

Dataset description

The texts on the hunting districts in which the hunting may be carried out are the hunting district designations. They are either self-hunting districts or community hunting districts. The practice of hunting is regulated by the Federal Hunting Act (BJagdG) and the State Hunting Act (LJG). This dataset contains the names of the approximately 300 hunting districts. The boundaries of the hunting districts are not clearly defined in all areas. The data set is continued at irregular intervals with actual changes in the districts.
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.

api.storeBuilt by Apitalks

European data discovery with free evaluation access and production-grade API options.

About api.storePrivacyTerms of Service
Copyright © 2026. Made by Apitalks