Development plan Barmbek-Süd 30 Hamburg

Open data API in a single place

Provided by Landesbetrieb Geoinformation und Vermessung

Get early access to Development plan Barmbek-Süd 30 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 20:37

Created

2025.08.02

Available languages

English

Keywords

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

Datasource

Official portal for European data link

Quality scoring

Dataset description

The development plan Barmbek-Süd 30 for the area of application between Weidestraße, former Flotowstraße, Osterbekstraße and the core area use Alstercity an der Weidestraße (district Hamburg-Nord, district 419) is established. The area is delimited as follows: Osterbekkanal - via parcels 1406, 5870 and 5859 of the district Barmbek - Weidestraße - via parcel 5734, western boundary of parcel 5734, southern boundary of parcel 6135, via parcel 5935, western boundary of parcels 6135 and 6136, via parcel 1406 (Osterbekstraße) of the district Barmbek.

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