Development plan Altona-Nord 26 Hamburg

Open data API in a single place

Provided by Landesbetrieb Geoinformation und Vermessung

Get early access to Development plan Altona-Nord 26 Hamburg API!

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

Dataset information

Catalog

Landesbetrieb Geoinformation und Vermessung catalog

Country of origin

Germany

Updated

2025.10.30 21:51

Created

2025.08.25

Available languages

English

Keywords

plis, baunutzungsverordnung--baunvo, öffentliche-pläne, baugesetzbuch--baugb

Datasource

Official portal for European data link

Quality scoring

Dataset description

The development plan Altona-Nord 26 for the area west of Harkortstraße and Theodor-Haubach-Schule (district Altona, district 210) is established. The planned area is limited as follows: Western boundaries of parcels 4979, 4978, 5177, 4945, 4944, 4839 and 4838, northwest boundary of parcel 4630, via parcels 5164 and 1809, eastern boundary of parcel 1809 (Harkortstraße) of the Ottensen district - via parcels 1408 and 1406, eastern boundary of parcel 42 (Gerichtstraße), via parcels 39 and 1406, eastern and southern boundary of parcel 40, via parcel 42 (Gerichtstraße), western and southern boundary of parcel 42 (Gerichtstraße) of the Altona-Nordwest district - eastern boundary of parcel 1809 (Harkortstraße), via parcel 1809 (Harkortstraße) of the Ottensen district.

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