Development plan Farmsen-Berne 16 Hamburg

Open data API in a single place

Provided by Landesbetrieb Geoinformation und Vermessung

Get early access to Development plan Farmsen-Berne 16 Hamburg API!

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

Dataset information

Country of origin
Updated
2025.10.30 19:45
Created
2025.08.01
Available languages
English
Keywords
öffentliche-pläne, baunutzungsverordnung--baunvo, baugesetzbuch--baugb, plis
Quality scoring

Dataset description

The Farmsen-Berne 16 development plan for the area of application north and south of the Eckerkoppel road between the Berner Heerweg and Tegelweg roads (Wallsbek district, district 514) is adopted. The area is delimited as follows: Tegelweg - northern boundary of parcel 3495 (Ebeersreye), via parcels 3495 and 4582, western boundary of parcel 165, via parcels 684, 683 and 4464, eastern boundary of parcel 235, southern boundary of parcels 235, 100, 101, 1468 and 1868, western boundary of parcel 1868, via parcel 160 (Eckerkoppel), northern boundary of parcel 160, western boundary of parcel 398, northern boundary of parcels 398, 397, 404, 405, 4071, 4073, 4072, 408 to 412, eastern boundary of parcel 412, via parcel 160 (Eckerkoppel), southern boundary of parcel 160, eastern and southern boundary of parcel 1995, southern boundary of parcel 1994 and 1993, via parcel 171, eastern boundary of parcel 4582, northern boundary of parcel 4582 Western boundary of parcel 2722 (Berner Heerweg), via parcel 2722, eastern boundary of parcel 2722, northern boundary of parcel 3828 (Ebeersreye), via parcel 3828, southern boundary of parcel 3828, southeast boundary of parcel 2722 (Berner Heerweg), via parcel 2722 of the Farmsen-Berne district.
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.

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

Copyright © 2026. Made by Apitalks