Development plan Wilhelmsburg 72 Hamburg

Open data API in a single place

Provided by Landesbetrieb Geoinformation und Vermessung

Get early access to Development plan Wilhelmsburg 72 Hamburg API!

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

Dataset information

Country of origin
Updated
2025.10.30 20:20
Created
2025.08.01
Available languages
English
Keywords
plis, öffentliche-pläne, baugesetzbuch--baugb, baunutzungsverordnung--baunvo
Quality scoring

Dataset description

The development plan Wilhelmsburg 72 for the area of application west of Wilhelmsburg Dove Elbe between railway facilities and Schönenfelder Straße (Harburg district, district 713) is established. The area is delimited as follows: Wilhelmsburg Dove Elbe - southeastern boundary of the parcel 1670 of the district Wilhelmsburg - Schönenfelder Straße - Korallusring - via parcels 6163 and 6612, southern boundary of the parcel 6612, via parcels 7363, 6604, 6853 (Korallusstraße), 7363, 6604, 7363 and 6607, western boundary of the parcel 6612, via parcel 6607, southern boundary of the Parcel 6612, via parcels 6236 and 7918, western boundaries of parcels 7918 and 1224, via parcels 9534 and 7878, western boundaries of parcels 7879, 7877 and 7875, northern boundary of parcel 7875, via parcel 1217 (Buscher Weg), northern boundary of parcel 1229, western and northern boundary of parcel 6805 of the Wilhelmsburg district.
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