TEC Energy Data HH-Bergedorf

Open data API in a single place

Provided by Hochschule für Angewandte Wissenschaften (HAW Hamburg)

Get early access to TEC Energy Data HH-Bergedorf API!

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

Dataset information

Country of origin
Updated
2026.01.22 19:47
Created
2026.01.21
Available languages
English
Keywords
energie-campus, geodaten, cc4eenergiedaten, competence-centers-für-erneuerbare-energien-und-energieeffizienz, frost-server, echtzeitdaten, sensordaten, haw
Quality scoring

Dataset description

At the plants of the Competence Center for Renewable Energies and Energy Efficiency (CC4E) for the generation of heat and electricity, the operating states are continuously recorded. This data set contains the time trajectories of the power data of the generators such as the photovoltaic system (PV) and the combined heat and power plant (CHP) (heat and electricity) as well as the (electricity) consumers such as the heat pump and the electric car charging station. In addition, the power of the power-side house connection is measured. In this way, reference and feed-in of different systems or measuring points can be traced over time. For example, the data provides information about when the building's PV system produced how much electricity. In conjunction with the data of the house connection, it can be traced whether the electricity was fed from PV or consumed in the building. The measuring points are located in facilities and rooms of the CC4E of the HAW-Hamburg and are used for research. More information about the real-time service: The real-time data service contains the location of the Competence Center for Renewable Energies and Energy Efficiency (CC4E) as well as the measurement results of various energy generation and consumption measurements in JSON format provided in the SensorThings API (STA). In the STA, the entity "Thing" stands for this location. There is a data stream for each energy consumption or generation measurement. The respective energy generation or consumption (real-time data) is obtained via the entity "Observations". All times are given in Coordinated Universal Time (UTC). In the Datastreams entity, there are additional key-value pairs under the "key" "properties" in the JSON object. Following the service and layer structure in GIS, we have introduced service and layer as additional "key-value pairs" under the JSON property. { "properties":{ "serviceName": "HH_STA_TEC_Energiedaten_HH-Bergedorf", "layerName": "Total yield_pv_electric", "key":"value"} } Available layers in the layerName are: * Generation_pv_electric * Consumption_house connection_electric * Generation_CHP_electric * Consumption_wp_thermal * Generation_CHP_thermal * Consumption_km_electric * Consumption_km_thermal * Consumption_el_electric * Consumption_ma_electric * Temperature_storage_heating rods * Consumption_eautocharging station_electric * Total yield_pv_electric With the help of these "key-value pairs", filters can then be defined for the REST request, e.g. https://iot.hamburg.de/v1.0/Datastreams?$filter=properties/serviceName eq 'HH_STA_TEC_Energiedaten_HH-Bergedorf',' and properties/layerName eq 'Gesamtertrag_pv_Elektrorisch' The real-time data can also be obtained through an MQTT broker. The necessary IDs can be obtained via a REST request and then used for the subscription to a data stream: MQTT broker: iot.hamburg.de Topic: v1.0/Datastream({id})/Observations
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