Bebauungsplan Lokstedt 62 Hamburg

Open data API in a single place

Provided by Landesbetrieb Geoinformation und Vermessung (LGV) Hamburg

Get early access to Bebauungsplan Lokstedt 62 Hamburg API!

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

Dataset information

Catalog

Landesbetrieb Geoinformation und Vermessung (LGV) Hamburg catalog

Country of origin

Germany

Updated

Created

2016.12.20

Available languages

English

Keywords

ENVI, REGI, opendata

Datasource

Official portal for European data link

Quality scoring

Dataset description

Der vorhabenbezogene Bebauungsplan Lokstedt 62 für den Geltungsbereich nördlich der Süderfeldstraße und westlich der Lottestraße (Bezirk Eimsbüttel, Ortsteil 317) wird festgestellt. Das Gebiet wird wie folgt begrenzt: Süderfeldstraße - Westgrenzen der Flurstücke 1334 und 5152, Süd- und Westgrenzen der Flurstücke 5164 und 1341, Westgrenze des Flurstücks 1340, West- und Südgrenzen des Flurstücks 3602 der Gemarkung Lokstedt - Wiben-Peter-Straße - Ost- und Nordgrenze des Flurstücks 3602, Nordgrenzen der Flurstücke 3600 und 3598, Nord- und Westgrenzen der Flurstücke 5164 und 5155, Nordgrenze des Flurstücks 5156, West- und Nordgrenze des Flurstücks 5162, Nordgrenzen der Flurstücke 5231, 5157 und 5158 - Lottestraße - Südgrenzen der Flurstücke 5159, 5160 und 5161, Ost- und Südgrenzen des Flurstücks 5164 der Gemarkung Lokstedt.

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