Heat register Hamburg – B plans with energy requirements

Open data API in a single place

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

Get early access to Heat register Hamburg – B plans with energy requirements API!

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

Dataset information

Country of origin
Updated
2026.03.28 22:17
Created
2026.03.28
Available languages
English
Keywords
baunutzungsverordnung--baunvo, geodaten, quartierskonzepte, baupolizeiverodnung-vom-08.06.1938--bpvo, wärmeplanung, wärmenetze, erneuerbare, wärmeversorgungskonzept, wärme, baugesetzbuch--baugb, hamburgisches-wärmekatastergesetz---hmbwktg
Quality scoring

Dataset description

zoning plans are legally binding plans, which include zoning plans, partial zoning plans, implementation plans and, since 1962, today's zoning plans under the Federal Building Act (BBauG) or, from 1986, under the Building Code (BauGB). In a series of development plans drawn up over the last 20 or so years, a provision was made for the supply of heat for heating and hot water to the new buildings. Usually, the heat supply from a heat network (connection and use requirement) was determined. Differences are mainly due to different quality requirements for the heating network. These are shown in different colours in stages. Detailed information can be found in the heat register manual.
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