Building Data Import

The building data is the basis for the grid generation as the building data contains geographical information as well as the load that each consumer requires.

Without InfDB

The building data is available at TUM as a dataset comprised of .shp files for residential res and other oth buildings. The buildings are seperated by their Amtlicher Gemeindeschlüssel (AGS) a key for the municipalities in Germany. The building dataset containing of files is to be unzipped and put into the directory raw_data/buildings.

The files for Munich are thus named like this: Oth_9162000 and Res_9162000.

The task of importing the building data before further Grid Generation steps is handled by

Remark: The mapping of AGS with PLZ is not always unique. This might lead to unexpected building data import.

In this example, the PLZ for grid generation only overlapped with the AGS that buildings were imported in the most upper part of the PLZ area.

The imported buildings can be inspected using the QGIS visualisation QGIS Visualisation in the raw_data tab

With InfDB

When USE_INFDB: True is set in the config_data.yaml file, importing building data is handled differently. The source for the building data becomes the InfDB database.

The InfDB processor loads the Pylovo-relevant tables into the pylovo_input schema of the InfDB database. When a grid is generated in Pylovo, the building data for the specified postcode is imported directly from InfDB into temporary tables, which are then used for the grid generation process.

As a result, the buildings can ultimately be viewed in the buildings_result table of Pylovo. To view the raw building data, the pylovo_input.buildings table in InfDB can be used.