Development Plan Groß Borstel 10 (2nd Amendment) Hamburg

Open data API in a single place

Provided by Landesbetrieb Geoinformation und Vermessung

Get early access to Development Plan Groß Borstel 10 (2nd Amendment) 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.04.08 16:24
Created
2026.04.07
Available languages
English
Keywords
öffentliche-pläne, baugesetzbuch--baugb, baunutzungsverordnung--baunvo
Datasource
Official portal for European data link
Quality scoring

Dataset description

The scope is limited by: Path by the hunter - via the parcels 2468 and 2289 - the northern boundary of the parcel 2282 - via the parcels 2282, 2248, 2239 of the district Groß Borstel - Obenhauptstraße - Path by the hunter - Alsterkrugchaussee - Hindenburgstraße - the southern boundary of the parcels 1770, 8289 and 2466 of the district Groß Borstel - Sportallee - the southern boundary of the parcels 1531, 2083, via the parcels 2074 and 2341 - the eastern boundary of the parcels 2341, 594, 2005, via the parcel 2005, the eastern and south-eastern boundary of the parcel 2005, the eastern boundary of the parcels 837, 2161 of the district Groß Borstel - Alsterkrugchaussee - Katharina-Jacob-Weg - Paeplowwegeplow - Palowepstieg.
European data infrastructure with broad catalog discovery, free evaluation access and production-grade API options.
190K+
indexed dataset pages
32
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.storeBuilt by Apitalks

European data discovery with free evaluation access and production-grade API options.

About api.storePrivacyTerms of Service
Copyright © 2026. Made by Apitalks