Bebauungsplan Kirchwerder 33 Hamburg

Open data API in a single place

Provided by Landesbetrieb Geoinformation und Vermessung (LGV) Hamburg

Get early access to Bebauungsplan Kirchwerder 33 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

2020.04.01

Available languages

English

Keywords

REGI, ENVI, opendata

Datasource

Official portal for European data link

Quality scoring

Dataset description

Gebiet nördlich Kirchenheerweg 91 und östlich Kirchheerweg 74 - 90 Das Plangebiet wird wie folgt begrenzt: Kirchenheerweg - Nordostgrenze des Flurstücks 8426, Nordost- und Südostgrenze des Flurstücks 8427, Nordostgrenze des Flurstücks 10694, Nordwest-, Nordost- und Südostgrenze des Flurstücks 10696, Südostgrenze des Flurstücks 1247, über das Flurstück 4472 (Südlicher Kirchwerder Sammelgraben), Nordost, Südost- und Südwestgrenze des Flurstücks 4471, über das Flurstück 1508 (Kirchwerder Marschbahndamm), Südwest-, Südost-, Südwest-, Nordwest und Südwestgrenzen des Flurstücks 1508 der Gemarkung Kirchwerder - Kirchwerder Marschbahdamm -, über das Flurstück 9764 (Kirchenheerweg), Südwest-, Nordwest- und Nordostgrenze des Flurstücks 10204 der Gemarkung Kirchwerder

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