Development plan Finkenwerder 32 Hamburg

Open data API in a single place

Provided by Landesbetrieb Geoinformation und Vermessung

Get early access to Development plan Finkenwerder 32 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

2026.04.08 19:28

Created

2026.04.07

Available languages

English

Keywords

geoinformation, baunutzungsverordnung--baunvo, raumbezogene-information, bauleitplanung, bebauungsplan, plis, baugesetzbuch--baugb, öffentliche-pläne

Datasource

Official portal for European data link

Quality scoring

Dataset description

The development plan Finkenwerder 32 for the area of application between the Finkenwerder Norderdeich and the Finkenwerder Landscheideweg and east of the Norderkirchenweg and the Bausenhof to the Norderschulweg (district Hamburg-Mitte, district 141) is established. The area is delimited as follows: Norderkirchenweg - Bausenhof - Nordmeertwiete - Norderkirchenweg - Finkenwerder Norderdeich - eastern boundary of parcels 2855, 4848, 2851 and 2595, eastern and southern boundary of parcel 2243, eastern boundary of parcel 4848, eastern and southern boundary of parcel 4813, southern boundary of parcel 4814, via parcel 3937, eastern boundary of parcels 4813, 1591 and 908 of the district Finkenwerder-Nord - Finkenwerder Landscheideweg.

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