Bebauungsplan Lemsahl-Mellingstedt 10 Hamburg

Open data API in a single place

Provided by Landesbetrieb Geoinformation und Vermessung (LGV) Hamburg

Get early access to Bebauungsplan Lemsahl-Mellingstedt 10 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

1981.07.01

Available languages

English

Keywords

PLIS, REGI, Öffentliche Pläne, opendata, hmbtg

Datasource

Official portal for European data link

Quality scoring

Dataset description

Der Bebauungsplan Lemsahl-Mellingstedt 10 für den Geltungsbereich Eichelhäherkamp-Westgrenze des Flurstücks 193, über das Flurstück 1784, Westgrenzen der Flurstücke 256, 269, 270 (Tannenhof), 1834, 344 und 345, über das Flurstück 134 (Bilenbarg), Westgrenzen der Flurstücke 346 und 405 der Gemarkung Lemsahl-Mellingstedt-Fiersbarg-über die Flurstücke 1828 und 1833, Ostgrenzen der Flurstücke 1827 und 1829, Südgrenzen der Flurstücke 1829 und 1827, Ostgrenzen der Flurstücke 404 und 361 der Gemarkung Lemsahl-Mellingstedt-Huulkamp-über das Flurstück 270 (Tannenhof), Ostgrenzen der Flurstücke 232 und 222 der Gemarkung Lemsahl-Mellingstedt-Seebarg-Ostgrenze des Flurstücks 209 der Gemarkung Lemsahl-Mellingstedt (Bezirk Wandsbek, Ortsteil 521) wird festgestellt.

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