Municipal boundaries KR KLE VIE WES

Open data API in a single place

Provided by Kreis Wesel

Get early access to Municipal boundaries KR KLE VIE WES API!

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

Dataset information

Catalog

Kreis Wesel catalog

Country of origin

Germany

Updated

Created

Available languages

English

Keywords

Tönisvorst, Gemeinde, Kamp-Lintfort, Kranenburg, Kreis Viersen, REGI, Niederkrüchten, Rees, Uedem, Nettetal, Viersen, Kerken, Goch, Bedburg-Hau, Neukirchen-Vluyn, Wesel, Rheinberg, Willich, Gemeinden, 05166000, Hamminkeln, Alpen, Geldern, Emmerich am Rhein, Kevelaer, Kalkar, Brüggen, Voerde, Schermbeck, Xanten, Weeze, Wallfahrtsstadt Kevelaer, opendata, Schwalmtal, Kleve, Sonsbeck, Straelen, GemeindegrenzenKreis, Kreis, Grefrath, Hünxe, Wachtendonk, Kempen, Dinslaken, Emmerich, Issum, Rheurdt, Krefeld, Moers

Datasource

Official portal for European data link

Quality scoring

Dataset description

This dataset contains the municipal boundaries for the municipalities of the districts Kleve, Viersen and Wesel, as well as the city of Krefeld. These municipal boundaries are created weekly (Saturdays) from the data of the property register.

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