Development plan Rahlstedt 39 Hamburg

Open data API in a single place

Provided by Landesbetrieb Geoinformation und Vermessung

Get early access to Development plan Rahlstedt 39 Hamburg API!

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

Dataset information

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

Dataset description

The Rahlstedt 39 development plan for the area of application of Bargteheider Straße-Meiendorfer Straße-Krögerstraße- northern boundary of parcel 1653, eastern boundary of parcels 1653, 2926, 2927, 1652 to 1650 of the district Meiendorf- northern and eastern boundary of parcel 2036, over parcels 2039 and 2624 of the district Oldenfelde-over parcels 1521, 1979 (Bundesbahn), 1517 to 1515, 1512 and 397/58 (Wandse) of the district Meiendorf-over parcels 3073 (Wandse), 2159 to 2161 (Eichberg), 2162 and 2163 of the district Oldenfelde-Eichberg-eastern boundary of parcel 2164, over parcel 2164, eastern boundary of parcels 2163 and 2162, South and southwest boundary of parcel 2162, over parcels 2162 and 2987 of the district Oldenfelde-Eichberg-Reetwischendamm-Warnemünder Weg-over parcel 1979 (Bundesbahn) of the district Oldenfelde-Delingsdorfer Weg-Oldenfelder Straße (district Wandsbek, district 526) is established.
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