Landscape programme / Open Space Network Hamburg

Open data API in a single place

Provided by Behörde für Umwelt, Klima, Energie und Agrarwirtschaft (BUKEA)

Get early access to Landscape programme / Open Space Network Hamburg API!

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

Dataset information

Country of origin
Updated
2026.04.01 20:20
Created
2026.03.03
Available languages
English
Keywords
landschaftsachse, freiraumkonzept, grünesnetz, 2.-grüner-ring, grünesnetzhamburg, freiraumverbund, grüne-ringe, hamburgisches-naturschutzgesetz--hmbnatschg, öffentliche-pläne, freiraumverbundsystem, inspireidentifiziert
Quality scoring

Dataset description

The map "Landschaftprogramm Hamburg / Freiraumverbund" is part of the landscape program. Note: The "open space network system of the landscape program" is derived from the database of the current landscape program. The demarcations of landscape axes, green rings and other elements of the open space network thus correspond to the representation in the landscape program. An update is made once a quarter. The map describes the main development goals of the open space network for Hamburg's urban landscape: A green network of landscape axes, 2 green rings, wider green spaces and narrower green connections linking parks, playgrounds and sports areas, allotment gardens and cemeteries. Thus, it should be possible to move undisturbed from road traffic on footpaths and cycle paths in the countryside within the city and into the open countryside on the outskirts of the city. The exact course and demarcation of the 2. Green Rings were developed as a Thematic Development Plan only after the adoption of the Landscape Programme. The 2nd Grüne Ring runs about 8 - 10 km from the Hamburg City Hall in a length of about 90 km between the inner and outer city. It includes green and open spaces of various types: public green areas, such as parks, allotment parks, forests and agricultural cultural landscapes of the March. The landscape axes are extensively connected green and open spaces that extend between the settlement areas from the surrounding area to the city center. Its location is mainly determined by the still preserved natural spatial structures of Hamburg: The watercourses with accompanying green strips, (e.g. Elbe axis, Alster axis, Wandse axis), the field marks with arable and grassland use and the forests, (e.g. Eimsbüttel axis, Volkspark axis), the marsh areas with vegetable and flower crops in the Elbmarschen axis, the fruit growing area in the Süderelbe / Moorgürtel axis. On the outskirts of the city, the landscape axes consist of large-scale agricultural areas, forests and nature reserves, which are of great importance as urban recreational areas. The extensive landscapes on the outskirts of the city are followed by green areas consisting of parks, allotments, cemeteries and sports areas. The further the landscape axes drag into the densely built-up city, the narrower and more patchy they become. An important planning goal is therefore to close the remaining gaps in the landscape axes. The data is provided as a WMS rendering service and as a WFS download service. Note: Download currently only possible as gml file
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