Disclaimer: The explanation provided on this website (Hotmaps Wiki) are indicative and for research purposes only. No responsibility is taken for the accuracy of the provided information, explanations and figures or for using them for unintended purposes.
Data privacy: By clicking OK below, you accept that this website may use cookies.
Within the scope of the Hotmaps project, data has been collected at various levels (national, regional and local levels). These data have been generated for four different sectors: residential (single-family houses, multifamily houses, and apartment blocks), service (offices, trade, education, health, hotels and restaurants, and other non-residential buildings), industry (iron and steel, non-ferrous metals, paper and printing, non-metallic minerals, chemical industry, food, drink and tobacco, engineering and others not classified), and transport (passenger transport -public, private, rail and freight transport -heavy goods and light commercial vehicles).
All the above-mentioned data sets are stored in Hotmaps data repositories on GitLab and can be accessed and downloaded from there. The Hotmaps data repositories are extensive and composed of more than 70 repositories. In order to provide a better overview of all Hotmaps repositories, here, we clustered them into different classes and provided the direct link to them. For detailed explanations on data collection, methodologies, references, assumptions and limitations of Hotmaps data sets refer to this report [1].
Useful energy demand for space heating and domestic hot water at different NUTS levels
🔺 The data is coming from ESPON Project. I guess it should be final energy demand instead of useful energy demand.
Share of gross floor area in construction periods:
Monthly solar radiation on optimally inclined surfaces at global scale
🔺 Readme is misleading. in the table within the readme file, it is written annual value. However, in the explanation, it is written monthly values!
Average heating degree days (HDD) and cooling degree days (CDD) at NUTS 3 level
Heating degree days (HDD) for the reference period 2002-2012 on hectare level
🔺 Reference period in the title and in the description within the readme file does not match
Cooling degree days (CDD) for the reference period 1999-2014 on hectare level
🔺 Reference period in the title and in the description within the readme file does not match
🔺 The unit of the data set has not been mentioned in the Readme file nor in the data package file.
🔺 The unit of the data set has not been mentioned in the Readme file nor in the data package file.
Biomass energy potential - forest biomass potential (raster)
🔺 In the readme file, explanation of agricultural residues and livestock effluents are provided; but, no data is available for this two.
Biomass energy potential - Agricultural residues, livestock effluents and forestry residues
Create your own profile:
🔺 `This information should be provided in the GitLab and load profile CM rather than here.`
Generic files are supposed to enable the user to produce load profiles of his own using his own data and a structure year of her/his own choice. For the industrial load profiles, we provided a yearlong profile for the year 2018 (in which the type days are set in the order of this year). For tertiary and residential load profiles, we provided a yearlong profile for the year 2010. However, we want to give the user the opportunity to use a structure year of his/her choice (Structure year in this context means the order of days in the course of the year).
The profiles provided here are unitless since they must be scaled during the generation of yearlong profiles.
Please refer to the individual profiles in this wiki or to the respective dataset repositories for more information on the generation of profiles from the generic profiles.
For heating, cooling and hot water, we provided a yearlong profile for the year 2010. However, if users have access to location-specific hourly temperature profiles or to temperature profiles for years other than 2010, we want to give the user the opportunity to use this data in order to generate load profiles with a different structure year or higher precision. Therefore, the generic profiles are supposed to enable the user to produce load profiles of his/her own using his own data and a structure year of her/his own choice.
For hot water provision, we assume that demand and thus the corresponding load profile depends on seasonal, weekly and daily influences.
The columns “day type” refers to the type of day in the week:
To integrate a seasonal influence into the demand profile, the column “season” is used.
Yearlong profiles for hot water can be generated from the generic profiles provided here following the following steps:
allocating the respective load value for the typeday/season tuple to each hour - scaling the total sum of the annual yearlong profile (i.e. the integral of the profile) according to the annual total demand
Generic hourly profiles on NUTS 2 level in the residential sector - space heating demand
🔺 The title of the repository does not match with the title of the readme file and is misleading!
Generic hourly profiles on NUTS 2 level in residential sector - space cooling
For heating and cooling, we assume that demand does not depend on the type of day but only on the hour of the day itself and the outside temperature in the respective hour (for this reason, the columns “type day” and “season” are not relevant for heating and cooling profiles).
Yearlong profiles can be generated from the generic profiles provided in this repository following the following steps:
The tertiary sector profile consists of demand from multiple subsectors. The configuration is different for each country. For the respective subsectoral shares per country, we refer to the hotmaps WP2 report, section 2.7.3 (https://www.hotmaps-project.eu/wp-content/uploads/2018/03/D2.3-Hotmaps_for-upload_revised-final_.pdf).
For hot water demand we assume that demand is independent of outside temperature, but depends on the type of day in a week and the hour of the day. The column “day type” refers to the type of day in the week:
Yearlong profiles can be generated from the generic profiles provided here following the following steps: 1. determining the structure year for which the profiles are generated 2. ordering the typeday according to the selected year 3. allocating the respective load value for the type days to each hour 4. scaling the total sum of the annual yearlong profile (i.e. the integral of the profile) according to the annual total demand
For heating and cooling in the tertiary sector, we provided a yearlong profile for the year 2010. However, we want to give the user the opportunity to use a year of his/her choice. Additionally, if users have access to location-specific hourly temperature profiles, we want to give the user the opportunity to use this data in order to generate load profiles with higher precision. Therefore, the generic profiles are supposed to enable the user to produce load profiles of his/her own using his own data and a structure year of her/his own choice.
We assume that demand for heating and cooling in the tertiary sector depends on the type of day, the hour of the day itself and the outside temperature in the respective hour.
The profiles provided here are unitless since they must be scaled during the generation of yearlong profiles. For the generic profiles for heating and cooling, they are driven by the differences between hours and temperature levels. Additionally, since the tertiary sector is driven by a weekly rhythm, the profiles for heating and cooling in the tertiary sector depend also on the day type. The column “day type” refers to the type of day in the week:
Yearlong profiles can be generated from the generic profiles for tertiary heating and cooling provided in this repository following the following steps:
For the industrial load profiles, we provided a yearlong profile for the year 2018 (in which the type of days are set in the order of this year). However, we want to give the user the opportunity to use a structure year of his/her choice. Structure year in this context means the order of days in the course of the year. The columns “day type” refers to the type of day in the week:
The column “month” refers to the month of the year. 1 = January, 2 = February etc. Yearlong profiles can be generated from the generic profiles provided here following the following steps:
scaling the total sum of the annual yearlong profile (i.e. the integral of the profile) according to the annual total demand
The year specific (yearlong) profiles provided here are generated on the basis of synthetic hourly profiles for typical days. In this context we emphasize, that profiles are not measured but modelled taking into consideration different factors depending on the profile type:
Using the structure of the days in a year, the profiles are assembled to a yearlong demand profile.
All profiles provided here are unitless and normalised to 1 000 000.
In order to a profile, it is to be scaled according to the annual demand of the respective region (i.e. so that the profiles integral equals the annual demand per region).
For detailed explanations and a graphical illustration of the dataset please see the Hotmaps WP2 report (section 2.7).
Hourly profile on NUTS 2 level in the tertiary sector in the year 2010 for sanitary hot water
🔺 In the readme file title, it is written domestic hot water. Since this is for the tertiary sector, it should be amended!
Hourly profile on NUTS 2 level in the tertiary sector in the year 2010 for space heating
🔺 In the readme file title, it is written domestic hot water. Since this is for the tertiary sector, it should be amended!
Hourly profile on NUTS 2 level in the tertiary sector in the year 2010 for space cooling
Vehicle stock and projections at NUTS 0 level
🔺 The README file of this repository is incomplete.
🔺 The README file of this repository is incomplete.
🔺 License from EC is missing in this repository.
[1] Simon Pezzutto, Stefano Zambotti, Silvia Croce, Pietro Zambelli, Giulia Garegnani, Chiara Scaramuzzino, Ramón Pascual Pascuas, Alyona Zubaryeva, Franziska Haas, Dagmar Exner (EURAC), Andreas Müller (e‐think), Michael Hartner (TUW), Tobias Fleiter, Anna‐Lena Klingler, Matthias Kühnbach, Pia Manz, Simon Marwitz, Matthias Rehfeldt, Jan Steinbach, Eftim Popovski (Fraunhofer ISI) Reviewed by Lukas Kranzl, Sara Fritz (TUW); Online Access
Mostafa Fallahnejad, in Hotmaps-Wiki, Hotmaps-data-repository-structure (May 2019)
This page is written by Mostafa Fallahnejad*.
* Energy Economics Group - TU Wien
Institute of Energy Systems and Electrical Drives
Gusshausstrasse 27-29/370
1040 Wien
Copyright © 2016-2019: Mostafa Fallahnejad
Creative Commons Attribution 4.0 International License
This work is licensed under a Creative Commons CC BY 4.0 International License.
SPDX-License-Identifier: CC-BY-4.0
License-Text: https://spdx.org/licenses/CC-BY-4.0.html
We would like to convey our deepest appreciation to the Horizon 2020 Hotmaps Project (Grant Agreement number 723677), which provided the funding to carry out the present investigation.
Last edited by fallahnejad, 2021-01-29 16:09:05