Management
Change/Add Scenarios#
All Scenarios are located in the reenact/reenact/scenarios folder.
Scenario with ID 00 is reserved for status quo scenario, which is only shown on the tab 2024.
All scenarios starting from ID 01 are shown on the tab Szenarien 2045.
Every scenario contains some basic information like name, title and description.
Additionally, every scenario contains static data to build related charts:
- data from production and demand are used in chart Energiebilanz (einfach),
- data from el_in and el_out are used in chart Strom-Bilanz (vollständig),
- data from potentials is used to generate Genutzte Energieerzeugungsflächen and
- data from boxes is used to show values in Klimaziele, Kosten and Erlöse.
To make use of predefined colors, change or use the technology labels listed in reenact/reenact/config/colors.json.
The first tab (2024) only shows a single scenario as baseline - the status quo today. When it comes to KPIs, only greenhouse gas emissions and costs are shown. Scenarios in the second tab (Szeanrien 2045) contain more KPIs as well as a complete electricity balance.
Change Slider Properties#
Unless otherwise stated, all config JSON files can be found in the folder reenact/reeanct/config.
The Sliders are used to set the component capacities in the energy system model. They also alter the basic bar plot,
which shows the amount of produced energy, as well as household consumption. In sliders.json you can change the slider
properties, for example its label, min and max value as well as step size.
The conversion factor from sliders setting to amount of energy in the bar plot can be found in full_load_hours.json.
For most of the production (like wind and pv) this means full load hours, others like biomass of mobility are more
complex. Biomass in tonnes has to be multiplied by heating value and the CHP efficiency. Mobility as is shown here,
consists of the energy amount for the electrified mobility share, as well as the rest, which is still fossil based
and thus less efficient.
A special case is Wiedervernässung Moore which is the requirement for PV - Moor as well as Biomasse Moor, and on
top of that, those two are partly competing for the rewetted marshland. These dependencies can be found in
marsh_dependencies.json.
The slider settings also create the used areas. For the area amount the slider setting is multiplied by the factor in
potential_areas.json.
Change Background Information#
The background information pages are stored as HTML files in reenact/templates/reenact and can be altered there.
Change map layers and legend#
Geodata import#
Geodata used in the application is stored as geopackages (.gpkg) in folder reenact/data/geodata.
In order to import this data into the database, a related database model has to be set up in module reeneact/reenact/models.py.
The minimum configuration to set up a model is to define the corresponding geopackage filename (without .gpkg suffix) as data_file and
which layer shall be imported from this geopackage as layer.
After setting up migrations and migrating models to database via python manage.py makemigrations and python manage.py migrate
(see Django Migrations for further information),
the geodata can be imported to the database using following command:
make load_data
This command automatically scans each model defined in models.py, reads-in data from geopackage and imports the data into related table.
Map configuration#
Map configuration is handled in config/settings/base.py.
There, the map setup at startup can be defined by setting the center of the map, the zoom factor and the maximum bounds of the map.
In the MAP_ENGINE_API_MVTS configuration, the layers of the map are defined by setting the layer_id and which model should be used
(additional details can be set as well).
In order to (de-) activate the layers on the map, a legend entry must be added for each layer not present at startup.
The legend entry can be added under reenact/config/geodata_config_exported.
The following fields from this config file are used in map legend:
- name references geopackage and layer_id (used in MAP_ENGINE_API_MVTS)
- title is used as legend title
- category is used to group layers in legend
- layer_in_category_order can be used to define an order for each layer per category
- tooltp_text is shown when a user hovers to legend info icon next to a layer title
- color is used for legend entry and map layer coloring