Development plan Langenhorn 35 Hamburg

Open data API in a single place

Provided by Landesbetrieb Geoinformation und Vermessung

Get early access to Development plan Langenhorn 35 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.03.01 19:11

Created

2026.02.28

Available languages

English

Keywords

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

Datasource

Official portal for European data link

Quality scoring

Dataset description

The development plan Langenhorn 35 for the area of application north and south of the Krohnstieg (district Hamburg-Nord, district 432) is established. The area is delimited as follows: Krohnstieg - peat piece - Pappelwisch - northern boundary of parcel 10235, western boundary of parcel 10252 of the Langenhorn district - Eekboomkoppel - via parcel 7828, western boundary of parcel 100, west and northeast boundary of parcel 7828 of the Langenhorn district - Eekboomkoppel - eastern boundary of parcels 118, 120 and 4670 of the Langenhorn district - Krohnstieg - Rodenkampweg - St. Jürgens Holz - eastern boundary of parcel 148 of the Langenhorn district - Cordesweg - via parcel 149 (Rodenkampweg) of the Langenhorn district - Jugendparkweg - western boundary of parcels 5561 (Neelsenweg) and 151, via parcel 155, southern boundary of parcel 111 (Krohnstieg) of the Langenhorn 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