Replication Data for: Optimal Heat Storage Sizing for District Heating Networks to Maximize Electricity Revenue from Combined Heat and Power Units

Open data API in a single place

Provided by Catholic University of Leuven

Get early access to Replication Data for: Optimal Heat Storage Sizing for District Heating Networks to Maximize Electricity Revenue from Combined Heat and Power Units API!

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

Dataset information

Catalog

Catholic University of Leuven catalog

Country of origin

Belgium

Updated

2025.12.12 10:41

Created

2025.12.12

Available languages

English

Keywords

Optimal storage sizing, District heating network, Combined heat and power

Datasource

Official portal for European data link

Quality scoring

Dataset description

A dataset containing the district heating network structure and the (aggregated) time series used in the case study of the paper "Optimal Heat Storage Sizing for District Heating Networks to Maximize Electricity Revenue from Combined Heat and Power Units". The optimization results can be replicated using the methodology and formulations described in the paper together with the provided dataset. File 01 contains the network structure (nodes and edges) of the studied district heating network. Files 02 to 04 contain the time series used for the heat demand, electricity sales price, and outside temperature. Unless otherwise stated, units are given in SI.

European data infrastructure with broad catalog discovery, free evaluation access and production-grade API options.

190K+

indexed dataset pages

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.store Built by Apitalks

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

About api.storePrivacy Terms of Service