Geographische Namen 1:250 000

Open data API in a single place

Provided by Bundesamt für Kartographie und Geodäsie (BKG)

Get early access to Geographische Namen 1:250 000 API!

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

Dataset information

Catalog
Bundesamt für Kartographie und Geodäsie (BKG) catalog
Country of origin
Germany
Updated
2026.03.13 00:00
Created
1996.12.30
Available languages
English
Keywords
landgemeindeteil, opendata, berg, hügelland, verwaltungseinheit, strom, watt, landgemeinde, advmis, sitz-der-verwaltung, binnensee, hügel, stadtgemeinde, kanal, fluss, stadt-, stausee, teich, gebirge
Datasource
Official portal for European data link
Quality scoring

Dataset description

Die Geographischen Namen umfassen die Namen folgender Objektbereiche: Siedlung, Verkehr, Vegetation, Gewässer, Relief, Gebiete mit Attributen zu: -Administrative Gliederung (statistische Schlüsselzahl) -Flusssystem (Gewässerkennzahl nach LAWA) -Einwohnerzahl -Ortsvorwahl -Größe (Fläche, Länge) -Höhe (Höhe in Metern über NN) -Lage (Geometriedaten aus dem Digitalen Landschaftsmodell im Maßstab 1:250 000) -Status des geographischen Namens -Sprache des geographischen Namens Der Datensatz GN250 orientiert sich am Maßstab 1:250 000 und umfasst ca. 160 000 Einträge. Die Lage der Objekte wird jeweils als Punktgeometrie über eine einzelne Koordinate und über kleinste umschreibende Rechtecke (Bounding Boxes) beschrieben.
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