Development Plan HafenCity 11 Hamburg

Open data API in a single place

Provided by Landesbetrieb Geoinformation und Vermessung

Get early access to Development Plan HafenCity 11 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 17:52

Created

2025.08.01

Available languages

English

Keywords

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

Datasource

Official portal for European data link

Quality scoring

Dataset description

The HafenCity 11 development plan for the area on the northern shore of the Baakenhafen (district of Hamburg-Mitte, district 104) is adopted. The area is delimited as follows: About the parcels 2348 (old: 2236 - Pillar railway), 1635, 1637 (Versmannstraße) and 2367 (old: 1639) of the district Altstadt Süd - Baakenhafen - via parcel 2367, western boundary of parcel 2361, via parcel 2358 (old: 1021 - Versmannstraße), northern boundaries of the parcels 2358 and 1636 (Versmannstraße), via the parcel 1634 (Versmannstraße) of the district Altstadt Süd.

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