Wiki Introduction

• Welcome page

Data sets

• Hotmaps data set: Method of data collection
• Hotmaps open data repositories

General tool functionalities & structure

• Introduction to user interface
• Layers section in the Hotmaps toolbox
• Select a region in the Hotmaps toolbox
• Retrieve indicators of a selected area
• Access to calculation modules
• Database behind the Hotmaps toolbox
• Data upload functionalities
• Data export functionalities

Calculation modules (CM)

• CM - Customized heat and gross floor area density maps
• CM - Scale heat and cool density maps
• CM - Demand projection
• CM - Heat load profiles
• CM - District heating potential areas: user-defined thresholds
• CM - District heating potential: economic assessment
• CM - District heating supply dispatch
• CM - Decentral heating supply
  
• CM - Solar thermal and PV potential
• CM - Shallow geothermal potential
• CM - Heat source potential
• CM - Biomass potential
• CM - Wind potential
• CM - Excess heat transport potential
• CM - Scenario assessment
• CM - Add industry plant
• CM - Vehicle stock at NUTS 2 level

How to apply Hotmaps toolbox

• Guideline: Hotmaps toolbox on local level
• Guideline: Hotmaps toolbox on national level
• Concept for using Hotmaps for district cooling
• Training material

For Developers

• Developers section
• Guidelines for defining indicators
• Guidelines for writing a Hotmaps Wiki page

CM Customized heat and gross floor area density maps

Table of Contents

• In a glance
• Introduction
• Inputs and outputs
• Method
• GitHub repository of this calculation module
• How to cite
• Authors and reviewers
• License
• Acknowledgement

In a glance

This module generates raster files both for a heat density and a floor area density map in the format required by the Hotmaps toolbox. The input data is provided in the form of a CSV file containing information on location, gross floor area and heat demand for each single building to be taken into account.

To Top

Introduction

This module generates both a heat density and a floor area density map in the form of raster files. The input to the module is a CSV file with certain column headers. It should contain the following data: the X- and the Y-coordinate of the centre of the buildings in EPSG:3035 coordinate reference system, the gross floor area and the annual heat demand of the buildings. The generated raster files follow required projection and resolution by the Hotmaps toolbox and therefore, can easily be uploaded to the user accounts.

This module is only available as a stand-alone module; it is not integrated in the online version of the Hotmaps toolbox. The users of this CM should be familiar with python programming and have installed required libraries (e.g. Numpy, Pandas, GeoPandas and GDAL).

To Top

Inputs and outputs

Inputs

The module accepts a CSV file as input. The following headers are expected in case of any of the input file types (should be available in the header of the CSV file):

• hotmaps_ID: provide a unique, integer ID for each feature (polygon)
• Type: Building type: set to 1 for service sector; other values are considered as residential (optional: can be left empty)
• Year_Construction: Year of construction (optional: can be left empty)
• Address: Address of the building (optional: can be left empty)
• GFA: Gross floor area in m²
• Footprint: footprint of the building in m² (required if values for GFA are not provided)
• NrFloor: number of floors (required if values for GFA are not provided)
• spec_demand: Specific heat demand of each feature (polygon) in kWh
• demand: Heat demand of each feature (polygon) in kWh
• X_3035: The X-Coordinate of the center of the feature (polygon) in EPSG 3035 projection (Mandatory for the CSV file: can be left empty)
• Y_3035: The Y-Coordinate of the center of the feature (polygon) in EPSG 3035 projection (Mandatory for the CSV file: can be left empty)

Important Note: The headers should be written as stated above. Otherwise, the code will break and returns an error.

Outputs

As output, two raster files are generated:

• A gross floor area density map with pixel values in m² per hectare
• A heat demand density map with pixel values in MWh per hectare

To Top

Method

To visualize an own raster file in the Hotmaps toolbox, it should respect the rules defined by the toolbox. Generally, a raster should:

1. have the CRS of ETRS89-extended / LAEA Europe - EPSG:3035;
2. The coordinate of the raster origin (top-left corner of the raster) should be a multiplicand of 100, e.g. (4334900, 3019700);
3. The resolution of the raster map should be 100x100m;
4. The raster should refer to a location in Europe.

Based on the above criteria and coordinates given in the input CSV file, each input coordinate is allocated to a certain pixel. Entries allocated to one single pixel are aggregated. The bottom-left pixel and top-right pixel determine the extent of the pixel. The resolution of the map is 100x100m. Accordingly, a heat density map and gross floor area map is generated.

To Top

GitHub repository of this calculation module

Here you get the bleeding-edge development for this calculation module.

To Top

How to cite

Mostafa Fallahnejad, in Hotmaps-Wiki, CM Customized heat and gross floor area density maps (September 2020)

To Top

Authors and reviewers

This page was written by Mostafa Fallahnejad (EEG - TU Wien).

☑ This page was reviewed by Marcul Hummel (e-think).

To Top

License

Copyright © 2016-2020: 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

To Top

Acknowledgement

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.

To Top

View in another language:

German^*

^* machine translated