Overview tile names Hamburg

Open data API in a single place

Provided by Landesbetrieb Geoinformation und Vermessung

Get early access to Overview tile names Hamburg API!

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

Dataset information

Country of origin
Updated
2026.01.23 21:01
Created
2026.01.22
Available languages
English
Keywords
250m, hamburgisches-geodateninfrastrukturgesetz--hmbgdig, 2km, blattwerk, 500m, hamburgisches-vermessungsgesetz--hmbvermg--vom-20.-april-2005, raster, hamburgisches-transparenzgesetz--hmbtg, 20km, geodaten, 10km, maschenraster, gitternetz, blattübersicht, kachelübersicht, 4km, utm, 1km, 12km, 1km-x-1km
Quality scoring

Dataset description

With the overview of tile designations, area squares are displayed for various basic geodata of the regional company Geoinformation and Surveying. The dataset and the data to be downloaded are available in ETRS89 UTM unless otherwise specified. As an explanatory supplement to this service, there are tile overviews of the respective data sets as a PDF (see links). The following data to be downloaded in the standard data package and partly in the transparency portal are displayed with their file names: ALKIS: maps 500m x 500m tiles, which contain the file names of the ALKIS data. DK5 maps 1km x 1km tiles showing the filenames of the Digital Map 1: 5000 (DK5). DK5 foliage in Gauss-Krüger maps 2km x 2km tiles showing the sheet numbers and names of the analogue map map of Hamburg 1: 5000 (DK5). The data is available in DHDN GK. DK5 foliage in UTM maps 2km x 2km tiles showing the sheet numbers and names of the analogue map map of Hamburg 1: 5000 (DK5). DOP5 maps 250m x 250m tiles, which contain the file names of the digital orthophotos with 5cm ground resolution (DOP5). DOP10 maps 500m x 500m tiles, which contain the file names of the digital orthophotos with 10cm ground resolution (DOP10). DOP20 maps 1km x 1km tiles, which hold the file names of the digital orthophotos with 20cm ground resolution (DOP20). DOP40 maps 2km x 2km tiles, which contain the file names of the digital orthophotos with 40cm ground resolution (DOP40). DGM in Gauß-Krüger maps 2km x 2km tiles, which contain the file names of the Digital Terrain Models (DGM). There are DGM1, DGM10 and DGM25, where the number indicates the distance between the elevation points in the point grid. The data is available in DHDN GK. DGM in UTM maps 2km x 2km tiles, which contain the file names of the Digital Terrain Models (DGM). There are DGM1, DGM10 and DGM25, where the number indicates the distance between the elevation points in the point grid. DISK20 maps 4km x 4km tiles showing the filenames of the Digital Map 1: 20 000 (DISK20). DISK60 maps 12km x 12km tiles showing the filenames of the Digital Map 1: 60 000 (DISK60). DTK25 maps the tiles representing the file names of the Digital Topographic Map 1: 25 000 (DTK25). The extension of the tiles corresponds to a maximum of 10km x 10km. Due to the small area of Hamburg, they vary in size. DTK50 maps the tiles representing the file names of the Digital Topographic Map 1: 50,000 (DTK50). The extension of the tiles corresponds to a maximum of 20km x 20km. Due to the small area of Hamburg, they vary in size. MRH250 maps 20km x 20km tiles showing the file names of the Digital Map of the Metropolitan Region 1: 250 000 (MRH250).
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