Development plan Rahlstedt 109 Hamburg

Open data API in a single place

Provided by Landesbetrieb Geoinformation und Vermessung

Get early access to Development plan Rahlstedt 109 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 19:35

Created

2025.08.01

Available languages

English

Keywords

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

Datasource

Official portal for European data link

Quality scoring

Dataset description

The development plan Rahlstedt 109 for the area of application north of the Sieker Landstraße between the road Höltigbaum and the state border (district Wandsbek, district 526) is established. The area is delimited as follows: Via parcel 1174 (Höltigbaum), western and southern boundary of parcel 1175, southern boundary of parcel 1178, via parcel 1178, northern boundary of parcel 1178, via parcels 1178 and 1175, western boundary of parcels 1178, 1175, 1221 and 1222 of the Neurahlstedt district - western boundary of parcel 3760, via parcels 3761, 3652, 3654, 2179, 2180 and 2184 of the Oldenfelde district - national boundary - southern boundary of parcels 2182 and 2181, via parcel 2180 of the Oldenfelde district - southern boundary of parcels 1233 and 1175 of the Neurahlstedt district.

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