Straßen und Hausnummern (NaviGeb) Kreis Viersen

Open data API in a single place

Provided by Kreis Viersen

Get early access to Straßen und Hausnummern (NaviGeb) Kreis Viersen API!

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

Dataset information

Catalog

Kreis Viersen catalog

Country of origin

Germany

Updated

2026.02.12 00:00

Created

2015.12.29

Available languages

English

Keywords

viersen, hausnummer, grefrath, nettetal, adressen, niederkrüchten, 05166000, straßennamen, brüggen, hausnummern, tönisvorst, adresse, willich, kempen, straßenverzeichnis, opendata, kreis-viersen, schwalmtal

Datasource

Official portal for European data link

Quality scoring

Dataset description

Die Adressdaten beinhalten je nach Format u.a. Rechts- und Hochwert (UTM), Gemeindekennziffer, Straßenschlüssel, ALKIS-Objektkennzeichen, Postleitzahl, Ort, Straße und Hausnummer sowie Hausnummernzusatz und ein Gültigkeitsdatum (entweder den 30.12.2015 für Beginn der Datenbank oder ein danach liegendes Freigabedatum). WMS und WFS sind tagesaktuell. Die Dateien zum Download werden wöchentlich neu erzeugt und werden in den Formaten shape, kml, csv, xls und json bereitgestellt. Die Daten decken das Gebiet des Kreis Viersen mit den Kommunen Brüggen, Grefrath, Kempen, Nettetal, Niederkrüchten, Schwalmtal, Tönisvorst, Viersen und Willich ab.

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