Modeling of Regionalized Emissions (MoRE)

Developer and Visualizer user interfaces

Manual

May 2011

Karlsruhe Institute of Technologie, Institute for Water and River Basin Management Department of Aquatic Enviromental Engineering Stephan Fuchs Ramona Wander Tatyana Rogozina Stephan Hilgert

II

III

MoRE is continuously being developed. Please check http://isww.iwg.kit.edu/MoRE.php for an updated version of MoRE and the manual.

IV

Table of contents

1  Introduction ..................................................................................................................... 1 

2  Implementation of MoRE ................................................................................................ 3 2.1  System requirements ....................................................................................................................... 3 2.2  Technical implementation of MoRE ................................................................................................. 3 

2.2.1  Calculation engine ........................................................................................................... 4 2.2.2  The database ................................................................................................................... 4 

2.3  The graphical user interfaces .......................................................................................................... 5 2.3.1  MoRE Developer ............................................................................................................. 5 2.3.2  MoRE Visualizer .............................................................................................................. 5 

3  MoRE Developer .............................................................................................................. 6 3.1  Launch MoRE Developer ................................................................................................................ 6 3.2  Design of the MoRE Developer GUI ............................................................................................... 6 

3.2.1  Object tables .................................................................................................................... 7 3.2.2  Data grid .......................................................................................................................... 8 3.2.3  Attribute window .............................................................................................................. 9 3.2.4  Structure window ............................................................................................................. 9 3.2.5  MoRE Developer toolbars ............................................................................................. 10 

3.3  Implementation of input data and modeling approaches .............................................................. 11 3.3.1  Short overview of implementing modeling approaches in MoRE .................................. 12 3.3.2  Create new data records ............................................................................................... 12 3.3.3  Implement new input data in MoRE ............................................................................... 13 3.3.4  Implementation of new modeling approaches ............................................................... 16 3.3.5  Generate and export results .......................................................................................... 21 

3.4  Tools in MoRE ............................................................................................................................... 24 3.4.1  Finding data records ...................................................................................................... 24 3.4.2  Change data records ..................................................................................................... 25 3.4.3  Delete data records ....................................................................................................... 27 3.4.4  Export of data records ................................................................................................... 27 3.4.5  Statistical analysis of input data .................................................................................... 28 3.4.6  Define selection fields .................................................................................................... 28 3.4.7  Customizing the interface .............................................................................................. 28 3.4.8  Attachment of files (flow charts) .................................................................................... 29 3.4.9  Transparency and traceability ....................................................................................... 29 

4  Visualizer ....................................................................................................................... 30 4.1  Access and login ........................................................................................................................... 30 4.2  Menu navigation and interface ...................................................................................................... 30 

4.2.1  Overview ........................................................................................................................ 30 4.2.2  Main menu ..................................................................................................................... 32 4.2.3  Map display .................................................................................................................... 32 4.2.4  Status bar ...................................................................................................................... 33 

4.3  Task window .................................................................................................................................. 33 4.3.1  Display and properties ................................................................................................... 33 

V

4.3.2  Analysis display ............................................................................................................. 35 4.3.3  Annotations .................................................................................................................... 41 4.3.4  Print ............................................................................................................................... 42 

5  Appendix ........................................................................................................................ 44 5.1  Nomenclature of the variables ....................................................................................................... 44 5.2  Nomenclature calculation steps, algorithms and algorithm stacks................................................ 45 5.3  Parser tasks ................................................................................................................................... 45 

6  References ..................................................................................................................... 47 

VI

Figures Figure 1: Substance sources and emission pathways for water pollution (Fuchs et al., 2010) .............. 2 Figure 2: River basins (left) and detailed division in analytical units (right) ............................................ 2 Figure 3: System architecture of the open source tool MoRE ................................................................. 4 Figure 4: MoRE Developer GUI .............................................................................................................. 6 Figure 5: Object tables in MoRE ............................................................................................................. 7 Figure 6: Data grid in MoRE .................................................................................................................... 9 Figure 7: Selected data record in the data grid and the corresponding contents in the attribute window ................................................................................................................................................................. 9 Figure 8: Selected data record in the data grid and corresponding contents in the structure window . 10 Figure 9: Content of the structure window in the data grid .................................................................... 10 Figure 10: The data grid's toolbar .......................................................................................................... 11 Figure 11: Toolbar in the attribute window ............................................................................................ 11 Figure 12: Creation of a new variable regarding the according type of the variable. ............................ 13 Figure 13: Creation of further attributes of a variable ............................................................................ 14 Figure 14: Activation of the tool import input data ................................................................................. 15 Figure 15: Selection of an import file ..................................................................................................... 16 Figure 16: Formation of the modeling approaches in MoRE ................................................................. 17 Figure 17: Structure window with variants ............................................................................................. 17 Figure 18: Creation of an operation ....................................................................................................... 18 Figure 19: View of operations in the data grid ....................................................................................... 18 Figure 20: Create calculation steps ....................................................................................................... 19 Figure 21: Structure window: algorithm stack ....................................................................................... 20 Figure 22: Selection of analytical units to execute the MoRE calculation engine ................................. 21 Figure 23: Start calculation engine ........................................................................................................ 22 Figure 24: Technical data table results ................................................................................................. 23 Figure 25: Export of a protocol .............................................................................................................. 24 Figure 26: Filter tool: Filter data records (left), clear filter (right) ........................................................... 25 Figure 27: Filter rows ............................................................................................................................. 25 Figure 28: Search and replace .............................................................................................................. 27 Figure 29: Deleting data records ........................................................................................................... 27 Figure 30: Personally adjusting the data grid ........................................................................................ 29 Figure 31: Attachment of documents for calculation ............................................................................. 29 Figure 32: Login ..................................................................................................................................... 30 Figure 33: Overview of the MoRE Visualizer interface .......................................................................... 31 Figure 34: The tabs of the main menu .................................................................................................. 32 Figure 35: Menu bar .............................................................................................................................. 32 Figure 36: Legend ................................................................................................................................. 32 Figure 37: Data request progress bar ................................................................................................... 33 Figure 38: Progress bar within the menu bar ........................................................................................ 33 Figure 39: Status bar ............................................................................................................................. 33 Figure 40: Window of the mode "view" .................................................................................................. 34 Figure 41: Property window ................................................................................................................... 35 Figure 42: Selection of spatial display criteria ....................................................................................... 36 Figure 43: Selection of components and specifications ........................................................................ 37 Figure 44: Selection for the comparison of time .................................................................................... 38 Figure 45: Visualizer, main menu and additional tasks ......................................................................... 38 

VII

Figure 46: Reports and export ............................................................................................................... 39 Figure 47: Chart view ............................................................................................................................ 40 Figure 48: Range of values and color scheme ...................................................................................... 41 Figure 49: Deposition of name and description of the new layer .......................................................... 42 Figure 50: Set checkmark to show a layer ............................................................................................ 42 Figure 51: Buttons for selecting items for the annotation ...................................................................... 42 Figure 52: Annotation - sub menu ......................................................................................................... 42 Figure 53: Print layout ........................................................................................................................... 43   

1

1 Introduction The Directive 2008/105/EC (on environmental quality standards) of the European Parliament and the Commission asks the Member States for an inventory of emissions of priority substances for all river basin districts (EU, 2008). This task requires appropriate data and approaches for the description of the current state of surface water bodies and the evaluation of appropriate measures for the reduction of emissions into the surface water bodies to achieve a good ecological state of surface waters and to meet the quality standards set. Based on these requirements the proven MONERIS concept that was developed for modeling of nutrient emissions into the water bodies (Behrendt et al., 2000), was adapted as MoRE system (Modeling of Regionalized Emissions) for the pollutant emissions. Besides the technical implementation (section 2.2), a full documentation of input data, model approaches and results as well as a high grade of transparency and flexibility of the model system were further goals of the implementation. According to the land use, different pollutant sources and emission pathways are considered. Processes which lead to a change in mass flows during transport are modeled using empirical approaches. The following emission pathways are implemented in MoRE (s. Figure 1): Municipal wastewater treatment plants, industrial direct dischargers and emissions of historic mining as pathways related to point sources and the following emission pathways related to diffuse sources: sewer systems, surface runoff, erosion, groundwater, tile drainage, direct atmospheric deposition onto water surfaces and inland navigation. In addition to the modeling of emissions into the water bodies an estimation of the river load on the basis of total emissions and a substance-specific retention is carried out. The modeling approaches and sources of input data are described in detail in Fuchs et al. (2010). The investigation area encompasses Germany’s large river basins as well as their catchment areas outside Germany and covers an area of 650,000 km². It is divided into 3,456 analytical units (of which 2,759 are in Germany) with an average catchment area size of 190 km² (in Germany: 135 km² (Figure 2). The emissions can be modeled in individual annual steps for certain periods between 1983-20051. For the evaluation of temporal trends and for the estimation of river loads the results were usually aggregated for the balancing periods 1983-1987 („1985“), 1993-1997 („1995“), 1998-2002 („2000“) and 2003-2005 („2005“)1 to soften the impact of hydrological influences.

1 Please note: the download version of MoRE comprises just the years 2003-2005

2

Figure 1: Substance sources and emission pathways for water pollution (Fuchs et al., 2010)

Figure 2: River basins (left) and detailed division in analytical units (right)

Below, at first the implementation of MoRE is explained (section 2). This regards to the technical realization as well as an illustration of the user interfaces. Section 3 describes the design of the MoRE Developer user interface and the procedure for embedding input data and modeling approaches and for generating results. Section 4 introduces the MoRE Visualizer user interface for mapping the modeling results.

3

2 Implementation of MoRE The MoRE system is based on two different operative graphical user interfaces (GUI): the MoRE Developer GUI and the MoRE Visualizer GUI. In the following section, the system requirements for working with MoRE and the technical implementation of the MoRE system are illustrated. Furthermore, the registration procedure and the design of both the MoRE Developer and the MoRE Visualizer are explained.

2.1 System requirements Following system requirements must be fulfilled to work with MoRE Developer:

− -Hardware: o Processor: Core2 or higher (i3-i7) respectively Athlon II or Phenom CPU o 2 GB main storage o At least 5 GB of free disk space

− Software: o Windows-OS with.NET-Framework 3.5 SP1

For working with MoRE Visualizer you need a broadband internet connection.

2.2 Technical implementation of MoRE The MoRE system is based on an open source PostgreSQL database and two different graphical user interfaces (GUI): the MoRE Developer GUI and the MoRE Visualizer GUI (Figure 3). The GUIs have been developed for user interaction with the PostgreSQL database. The PostgreSQL database content can be easily read, changed and extended via the MoRE Developer GUI. Also, modeling can be launched via a calculation engine which is incorporated in the Developer GUI with a dynamic linkage to the PostgreSQL database. Modeling results can be visualized via a GIS-browser (MoRE Visualizer). Users can access the MoRE system either via internet on a multi-user basis or via a single user application for PC.

4

Figure 3: System architecture of the open source tool MoRE

2.2.1 Calculation engine One of the main goals of MoRE development was the provision of a flexible modeling tool. New modeling approaches can be integrated in a flexible way using the calculation engine and tested easily in the Developer GUI. This feature is possible because the calculation engine is integrated but unit independent of the database. That means the calculation engine does not include any equations but only the logic structure of the model and doesn’t have to be adapted to changes in approaches, as long as the structure of the MoRE database will be maintained. The user does not need to have programming skills.

2.2.2 The database The fundamental database contains all data and metadata for the spatially and temporally variables, and for the model constants. This means, for example, that each record is assigned a unique origin and additional information like pathway specification and substance reference. Furthermore, the empirical approaches are defined in the database. After modeling, the results can again be written to and stored in the database or exported for further analysis to MS Excel.

5

2.3 The graphical user interfaces

2.3.1 MoRE Developer Using the MoRE Developer GUI, new input data can be added to the database and algorithms for approaches can be readjusted. Additionally, MoRE Developer owns a powerful calculation engine for calculating emissions and river loads for selected analytical units. MoRE is modular, so that the approaches of individual pathways can be independently adjusted. Thus, alternative input data and modeling approaches can be implemented as variants of a basic variant. The results can be compared to evaluate the quality of the considered input data and approaches.

2.3.2 MoRE Visualizer In addition to the MoRE Developer GUI the MoRE Visualizer offers the opportunity of presenting and analyzing the computed data. The Visualizer is a browser based application which can be executed at any place with an internet connection. The MoRE Visualizer works via a direct connection with the MoRE database. All certified changes applied in the MoRE Developer GUI will have a direct effect on results depicted in the MoRE Visualizer. The main use of the Visualizer is to create maps of data from the MoRE database. The data can be selected by different options regarding administrative borders, catchment areas, substances, years and further more. A special feature is the selective comparison of different periods. After the selection and visualization of the data, it can also be presented as reports which can be exported to MS Excel. The MoRE Visualization automatically summarizes results and shows additional metadata for the selected pathway, substances and aggregation levels. Further options are functions for direct print and a user defined classification of shown values. An overview of the system's architecture is given in Figure 3.

6

3 MoRE Developer

3.1 Launch MoRE Developer MoRE usually starts in reading mode. In this mode, no adjustments but the interface configuration can be made. To add, change or delete variables, input data or other items, the activation of the writing mode is necessary.

Change to writing mode by single-clicking

3.2 Design of the MoRE Developer GUI The MoRE Developer GUI (Figure 4) contains an overview of all object tables (on the left, section 3.2.1) and a data grid (in the middle, section 3.2.2) in which records from a selected object table are displayed. On the right side an attribute window (section 3.2.3) and a structure window (section 3.2.4), are arranged, both of them showing additional information about a selected record in the data grid. MoRE also features two toolbars (section 3.2.5) that appear in the title bar of the data grid, as well as in the title bar of the attribute window. These toolbars comprise additional functions and special features.

Figure 4: MoRE Developer GUI

7

All components mentioned are explained closer in the following.

3.2.1 Object tables With the MoRE Developer GUI, data from the PostgreSQL data base can be accessed. This data is summarized in object tables like metadata, input data, calculation and results (Figure 5).

Figure 5: Object tables in MoRE

Object tables can be selected by clicking on the name of the desired object table. A red arrow appears in front of the name of the selected object table and the name is highlighted with blue color (Figure 5). Only one object table can be selected at once.

8

The object table metadata contains information about input data. The table all variables lists names, type and reference of all variables and constants as well as the number of formulas they are used in. The object table input data contains all (preprocessed) data which are necessary for the modeling. These are on the one hand analytical units with their corresponding area properties. On the other hand, there are the values aggregated onto the analytical unit of all spatial and spatial and periodical variables and constants for all years. Depending on their type, variables and constants can have spatial or spatial and periodical reference. The object table metadata arranges variables of different type in different tables and also lists further attributes like description, family membership, unit, substance (group) reference or pathway. Besides, an assignment of substances to certain substance groups and the allocation of years in balancing periods are made. The object table calculation contains the model's algorithms for the determination of substance emissions into surface waters via different emission pathways. An algorithm stack usually represents a balancing approach for a pathway of water or substance flow. Each algorithm stack consists of one or more algorithms or algorithm stacks. Algorithms consist of multiple numbered calculation steps that are represented by individual formulas (according to these calculation steps) (Figure 16). The object table calculation in addition contains the variables aggregated along the runoff model (table runoff model). The folder overview contains the tables operations and calculation steps. The calculation steps indicates, which algorithm has a calculation step assigned to and in what order the calculation steps are being executed. The object table results contains all generated results as preliminary calculation runs or as a detailed protocol verified results stored in the object tables results sets as well as the data for reproducing the runoff model.

3.2.2 Data grid By clicking on object table, its content is displayed in the data grid as a table in the middle of the screen (Figure 6). The heading of the window corresponds with the data record selected in the data grid. Clicking on the data grid's left margin selects a data record of the object table listed. The selected data record is highlighted with blue color.

9

Figure 6: Data grid in MoRE

3.2.3 Attribute window In the top right window, further details to the selected entries of an object table are displayed additionally (Figure 7). The heading of the window corresponds with the data record selected in the data grid. New data records may be created (section 3.3.3.1) and changed (section 3.4.2) in the attribute window.

Figure 7: Selected data record in the data grid and the corresponding contents in the attribute window

3.2.4 Structure window In the bottom right window, the structure of the data record selected in the data grid is displayed (Figure 8). This window is especially helpful for the following entries from the object table calculation. If the table formulas is opened, the variants are displayed under the

10

structure window. The table algorithms shows the individual calculation steps and the table algorithm stacks lists the individual algorithms.

Figure 8: Selected data record in the data grid and corresponding contents in the structure window

Clicking on entries (< n variant >, < n calculation steps >, < n algorithms >) in the structure window shows further information about them in the data grid (Figure 9).

Figure 9: Content of the structure window in the data grid

3.2.5 MoRE Developer toolbars In MoRE, two toolbars are implemented which allow interaction with the PostgreSQL data base as well as creating and changing data records. In addition, the data grid's and the attribute window's view can be changed. Lists can be exported to Excel, too. Finally, the calculation can be launched via the toolbars.

3.2.5.1 Toolbar in the data grid

MoRE has a toolbar in the data grid which offers different tools depending on the object table selected. (Figure 10). Here,

− data records can be filtered (see section 3.4.1)

− the data grid's content can be exported to Excel (see section 3.4.4)

− data records can be deleted (see section 3.4.3)

− searching and replacing (see section 3.4.2.4) allows it to change multiple entries at once

− diagrams can be created by the tool define statistics

11

− some special functions of the calculation engine can be executed

Figure 10: The data grid's toolbar

3.2.5.2 Toolbar in the attribute window

In the attribute window, another toolbar is implemented (Figure 11). Here,

− entries of the attribute window can be ordered

− new data record can be created

− the content of an attribute window can be exported and

− .pdf-documents can be uploaded to the data record .

Figure 11: Toolbar in the attribute window

3.3 Implementation of input data and modeling approaches Model approaches of selected areas which already have been implemented can be manipulated using the Developer Interface of MoRE. In addition, new modeling approaches can be defined as variations apart from existing approaches. If other (often more detailed) input data is available for an area, it can be imported to MoRE. When appropriate and depending of the data basis, modeling approaches can be adjusted. Eventually, the achieved results can be exported to Excel and/or displayed with a GIS-Browser. If there is a new approach for substance emissions to water bodies, in a first step it should be defined on a Flowchart which individual steps of calculating should be taken. This can serve as an orientation or draft for generating the individual components of the MoRE system. In the following, the strategy for generating results will be shown schematically (section 3.3.1). Then, the fundamental strategy for creating new data records will be introduced (section 3.3.2). An introduction of implementing new input data (section 3.3.3) and modeling approaches (section 3.3.4) follows. Finally, it is demonstrated how modeling results can be generated and exported (section 3.3.5).

12

3.3.1 Short overview of implementing modeling approaches in MoRE First, writing mode has to be launched in MoRE (section 3.1Fehler! Verweisquelle konnte nicht gefunden werden.). After that, new input data can be implemented (section 3.3.3) as well as new calculation approaches with their calculation steps can be defined (section 3.3.4). Eventually, calculations can be made and exported (section 3.3.5).

1. Launch MoRE (see section 3.1). 2. Implement new input data (see section 3.3.3) 3. Implement new calculation approaches (see section 3.3.4) 4. Generate and export results (see section 3.3.5)

3.3.2 Create new data records The fundamental strategy for creating new data records follows:

1. Select the accordant data table in the left window. It will now become visible in the data grid.

2. Create a new data record using the toolbar of the attribute window.

3. Fill in all needed information. 4. Transfer the data record to the data base.

There is also the possibility to discard the data record.

5. If necessary, attach documents with additional information.

6. Check if the transfer was successful.

13

3.3.3 Implement new input data in MoRE To implement new input data in MoRE, at first the accordant variables have to be created in the system (section 3.3.3.1). Afterwards, the input data can be imported to MoRE (section 3.3.3.3).

3.3.3.1 Create variables

Having created a variable, there needs to be - apart from the variable name, which should be conform to the nomenclature of the variables (see section 5.1) - further miscellaneous information created as metadata (e.g. description, unit, source, substance reference, pathway etc.). Depending on the type of metadata, either a free text can be inserted or the accordant entry of a dropdown panel can be selected.

3.3.3.1.1 Creation of a variable under metadata > all variables

A new Variable has to be created in the object table metadata > all variables. First, a new data record is created analog to section 3.3.2. Apart from the name, the type of the variable (constants, spatial data, spatial and periodical data) as well as the source (reference) have to be declared.

3.3.3.1.2 Creation of a variable under metadata > table according to the type of the variable

After that, according to the type of the variable, a new variable has to be defined under constants, spatial data, spatial and periodical data. In the object table metadata, the type of variable has to be selected (Figure 12, left) and once more a data record created using the attribute window (Figure 12, right).

Figure 12: Creation of a new variable regarding the according type of the variable.

Now, the variable created earlier has to be selected in the dropdown menu field name. Fill in all panels at 02-substance reference and 03-general information and add the data record (Figure 13).

14

Figure 13: Creation of further attributes of a variable

3.3.3.2 Create family variables

The creation of a family variable is reasonable, if the same modeling approach is used for several substances. The formulas then only have to be written for the family of variable, but have effect on every member of the family. In MoRE, this is realized for the group of heavy metals so far. The family variable always has the lesser specific and by that higher-ranking name. The names of the families of variable in this case end on _HM for heavy metals. If a family variable's name for example is AD_RATE_HM (atmospheric deposition rate of heavy metals), the individual member's names could be AD_RATE_HM_CD, AD_RATE_HM_CR etc. Family variables are created like variables (sections 3.3.3.1 and 3.3.3.1.2). If individual members are created, its family variable has to be specified additionally under metadata.

3.3.3.3 Import of new data to MoRE

After creating a new variable, the values have to be imported to MoRE. Please note: The import of values for a variable is only possible after defining a variable in the metadata.

3.3.3.3.1 Preparation of the import files in Excel

For the import of input data to MoRE a template file is available. The file contains three worksheets for an import of constants, spatial data or spatial and periodical data and is delivered with the system (File „MoRE import template.xls“). MoRE is able to import several variables in one operation; however, they have to be of the same type. This is the reason why in the import file only one worksheet (constants or spatial data or spatial and periodical data) can be filled out. Every non-used worksheet may not contain any entries but the headings. A constant is characterized by having the same value for all analytical units. Therefore it is sufficient for constants to enter the name of the variable, its value and its reference in the import file. The spatial data may have different values for each analytical unit. However, they do not have a time reference. An example is the size of the analytical unit. It is therefore sufficient to create a row with the variable's name, its value and its reference for each analytical unit (allocable via ID).

15

There is a sum of 3456 rows for all analytical units or accordingly less, if the input data for a smaller catchment area is imported. The spatial and periodical variables on the other hand have different values for each year as well as for each analytical unit. Hence, for every analytical unit the year, the name of the variable, the value of the variable and the reference is needed.

3.3.3.3.2 Import into the system

If the object table input data > analytical unit is selected, the special function input data import in the data grid's toolbar can be used to integrate new data records in MoRE (Figure 14). Choose the prepared Excel-file (Figure 15). The checkmark at overwriting existing values is set by default. By clicking on start data import, the data is being imported.

Figure 14: Activation of the tool import input data

16

Figure 15: Selection of an import file

3.3.4 Implementation of new modeling approaches All modeling approaches are listed in the object table calculation. Here,

− formulas (calculation steps), − algorithms as an aggregation of several calculation steps and − algorithm stacks as a modeling approach for water and substance flow

are defined. Each algorithm stack consists of one or more algorithms or algorithm stacks. Algorithms consist of several numbered calculation steps, which are mapped by particular formulas (accordant to the calculation steps) (Figure 16).

17

Figure 16: Formation of the modeling approaches in MoRE

3.3.4.1 Create formulas

First, the result variable of a formula has to be created under the object table metadata > all variables (see section 3.3.3.1). After that, in the object table calculation, the table formulas is activated. Now, a new data record can be created in the attribute window. In this step, only the result variable is selected which corresponds to the variable created before. The new data record now has to be added to the data base. (see section 3.3.2) In a third step, the operations for the calculation of these variables are entered. For this purpose, click on < 0 variants > in the structure window (Figure 17).

Figure 17: Structure window with variants

In the data grid, the table calculation > formulas > operations now opens (Figure 18). In the column operation, the formula is entered as plain text in a text editor. Clicking on OK leads to the formula being displayed in the data grid (Figure 19).

18

Figure 18: Creation of an operation

Figure 19: View of operations in the data grid

To use the interface, knowledge of a programming language is not necessary. Please take account of the operators for creating operations in section 0.

3.3.4.2 Create variants

To compare two different modeling approaches for a variable, a calculation variant can be used. They are created analogically to the procedure in section 3.3.4.1 by adding a new data record at the object table calculation > formulas. The variant is displayed apart from variant 1 as variant 2 in the data grid.

3.3.4.3 Create algorithms

After having entered a formula, an appropriate algorithm can be created. Therefore, the table calculation > algorithms needs to be selected and a new data record to be created and saved (analog to the procedure in section 3.3.2). Please note: in the field 02-properties you have to define whether the algorithm can be calculated for single years or for balancing periods. Now, calculation steps need to be assigned to the algorithms in a defined order.

3.3.4.4 Create a calculation step

The object table algorithms needs to be activated. All calculation algorithms that have already been implemented appear in the data grid. As a next step, the desired algorithm is selected. The detail window structure shows the number of already implemented calculation steps. For the assignment of calculation steps to an algorithm, click on < 0 calculation steps > in the structure window (Figure 20). Now, the object table calculation > algorithms > calculation steps opens, where a new data record can be created and the desired formula can be entered as a calculation step. The order of the calculation steps may be changed later with the help of the special function renumber algorithm (section 3.4.2.5).

19

Figure 20: Create calculation steps

3.3.4.5 Copy algorithm

While working with MoRE, it might become reasonable to save time by copying algorithms. Algorithms that are similar to each other or ought to exist in different variants may be multiplied that way without much effort. Copying creates an exact copy of the algorithm. To avoid confusion, the copy's name starts with "copy x" followed by the original name of the algorithm. However, this name may be changed arbitrarily (section 3.4.2). To copy an algorithm, the accordant algorithm is selected and the special function algorithm > copy from the toolbar is used. Because the listed algorithms are displayed in alphabetical order by default, the created copy of the algorithm is not displayed next to the original (starts with "copy x").

3.3.4.6 Create algorithm stacks

Algorithm stacks in general represent a modeling approach for water and substance flow. They can be composed of one or more algorithms. The order of the algorithms that need to be regarded is essential for a correct execution. A new algorithm stack is created corresponding to the procedure in section 3.3.2. Please note: in the field 02-properties you have to define whether the algorithm can be calculated for single years or for balancing periods.

20

Afterwards, individual steps have to be assigned as algorithms to the algorithm stack. This can be done by clicking on < 0 calculation steps > in the structure window (Figure 21). After that, the attribute window opens to select a new algorithm. First, a new data record is created. At 02-algorithm, an algorithm has to be selected in the dropdown menu. The number of the calculation step can be entered at step. Note that the number has to be double-digit (i.e. 01 for the first, 02 for the second calculation step etc.). Lastly, the new data record is added to the data base by accepting the settings.

Figure 21: Structure window: algorithm stack

Please note: An algorithm stack may consist of several algorithm stacks that have been created earlier. However, they are described and sorted in as an algorithm within the algorithm stack. For example, the algorithm stack water balance > groundwater runoff is applied as algorithm in the algorithm stack emissions > emissions via groundwater, but also exists as an independent algorithm stack for the calculation of groundwater runoff. If an algorithm stack is an algorithm within another algorithm stack, there needs to be regard of selecting an algorithm stack at 02-algorithm when creating an algorithm.

3.3.4.6.1 Algorithm stacks created in MoRE

In MoRE, the following algorithm stacks are applied by default: − Inhabitants: connected and non-connected inhabitants as well as inhabitants

connected to a separate/combined sewer system − Areas: for calculation of

o impervious areas: connected and non-connected areas as well as areas connected to a separate/combined sewer system

o arable areas o tile drained areas o water surfaces o areas that contribute to groundwater recharge

− Water balance o precipitation onto water surfaces o tile drainage runoff o urban runoff o surface runoff o groundwater runoff o total runoff

− Emissions: for all emission pathways and substance groups: o wastewater treatment plants

21

o industrial direct dischargers o abandoned mining o atmospheric deposition o tile drainage o erosion o groundwater o sewer systems o surface runoff o inland navigation o total emissions

− River load Apart from these algorithm stacks, further algorithm stacks can be created by the procedure mentioned above.

3.3.5 Generate and export results MoRE executes calculations on the basis of algorithm stacks (section 3.3.5.1). The results of a calculation run are saved in the object table results. According to the explanation of section 3.3.5.1.3, the last step of an algorithm stack can be saved and output as the final result of a calculation run. Another option is to write a detailed protocol with all calculated variables.

3.3.5.1 Execute calculations in MoRE

For calculation, in the object table input data > analytical unit an arbitrary number of analytical units (e. g. 10001 to 10010,Figure 22) has to be selected. The selection of the desired areas can be facilitated by the filter function. (section 3.4.1).

Figure 22: Selection of analytical units to execute the MoRE calculation engine

3.3.5.1.1 Calculation for individual years

All algorithm stacks that refer to the inhabitants, areas, water balances and emissions can be calculated on the basis of individual years. For this purpose, the tool special function execute calculation run > calculation for single years from the toolbar is activated after having selected the analytical units. The window MoRE: Calculation engine is being opened for the

22

calculation, where all algorithm stacks are listed that can be calculated for single years (Figure 23). The algorithm stack, the substances and the years of calculation have to be selected here. Start calculation engine starts the calculation.

Figure 23: Start calculation engine

3.3.5.1.2 Calculation for balance periods

The algorithm stack river load is calculated on the basis of balancing periods. The balancing periods implemented in MoRE are “2000” as arithmetic mean of the years 1998 to 2002 and “2005” as arithmetic mean of the years 2003 to 2005.

23

For the calculation of the river load, the total emissions are calculated for each analytical unit and reduced by a retention factor. Then, the reduced river loads of each analytical unit are aggregated according to the runoff model. To calculate river loads, the special function execute calculation run > calculation for balancing periods from the toolbar has to be activated after having selected the analytical units. The window MoRE: Calculation of balancing periods opens for the calculation, where all algorithm stacks are listed with reference to a balancing period. The algorithm stack, the substances and the balance periods have to be selected here. OK confirms the selection. Start calculation engine starts the calculation.

3.3.5.1.3 Calculation run vs. detailed protocol

By default, executing a calculation run in MoRE carries out all operations, but only writes defined variables and their values. By that, the duration of the calculation is minimized. The results of the calculation runs are listed in the object table results > preliminary > calculation runs. If additional variables are wanted, this can be selected in the object table metadata > spatial and periodical variables in the column output. MoRE offers the possibility of creating a detailed protocol of calculation runs. In this detailed protocol, every calculated variable is listed with its value as well as the proper formulas and input data. However, the speed of the calculation is reduced considerably.

3.3.5.1.4 Calculations after changes in the system

To execute modified calculations with MoRE, the accordant steps for the creation of new variables, input data, formulas, algorithms and algorithm stacks have to be taken. This may either be accomplished by recreating the mentioned MoRE-components (see section 3.3.3 and 3.3.4) or by the creation of different variants (section 3.3.4.2).

3.3.5.2 Export results

Results are either saved as a calculation run (protocol without details) or as a detailed protocol in the object table results > preliminary > calculation runs and results > preliminary > protocols (Figure 24). In the data grid, they are displayed with a consecutive ID.

Figure 24: Technical data table results

3.3.5.2.1 Export of calculation runs

Calculation runs are displayed in the object table results > temporary > calculation runs in the data grid. Thereby detailed information on the last executed calculation run is displayed in the structure window and the attribute window.

24

To export, the desired calculation run needs to be selected and exported to Excel with the special function results Excel export just final results or results Excel export all results.

3.3.5.2.2 Export of protocols

For the export of a protocol, click on < xx calculation steps > in the structure window (Figure 25). Afterwards, the object table results > protocols > details shows the overview of the executed calculation steps of the calculation run in the datagrid. With the tool writing to Excel, the protocol can be exported (Figure 25).

Figure 25: Export of a protocol

3.4 Tools in MoRE In the following, some of the tools which ought to facilitate the work with MoRE are described. On the one hand, this refers to searching and finding, changing and deleting of existing data records. (sections 3.4.1– 3.4.13.4.3). On the other hand, the proceeding on exporting object tables, input data and results is explained (section 3.4.4).

3.4.1 Finding data records With the filter function in data grid's toolbar, MoRE contains a tool for browsing data records. With this tool, the content of an activated object table can be searched through for entries. Depending on the type of data in a column (integer, description field, etc.), default search tasks called operators2 can be used (Figure 26). Furthermore, there is the option to link multiple criteria by an and/or selection. Data records can be searched through quickly and easily and the display can be customized to the current interest by that. The filter function may be multiplied.

2 Figure panels: equal, unequal, lesser, greater, contained in, is empty; text panels: beginns with, ends with, contains, as well as all operators from the figure panels

25

Figure 26: Filter tool: Filter data records (left), clear filter (right)

In an example, the procedure of filtering content shall be explained. Often it can be useful to know in which formulas a certain variable is used. Under the object table calculation > formulas, the filter is activated. At field name, the desired content and operator are selected (in this case equal). At value, the search text is entered (Figure 27). By clicking on the green arrow add condition to list, the defined filter appears below. Clicking on OK displays the filtered entries. If all entries ought to be shown again, the button clear filter needs to be activated.

Figure 27: Filter rows

The filter function is also helpful at selecting analytical units. Under the object table input data > analytical units, they can be filtered by administrative borders (country, state) or by catchment area borders (river name, coordination area, sub-unit, river basin district, marine area).

3.4.2 Change data records After having created data records, metadata as well as values can be changed later without much effort. This may occur often with metadata of variables, formulas, algorithms and

26

algorithm stacks. Depending on the type of metadata, either a free text can be entered or the corresponding entry from a selection field can be selected. The changes always have to be confirmed. For editing, the writing mode in MoRE has to be activated (section 3.3.1, point 2). Input data can be added to or be overwritten as well. The data base automatically updates the remaining entries connected to the changed value after a change has been made. If names of variables have been altered, the changes have to be manually inserted to the formulas.

3.4.2.1 Change metadata in the data grid

The corresponding object table has to be selected for this. By double-clicking on the desired panel in the data grid, a change can be made now. Alternatively the magnifier symbol can be selected after the double-click; the text then appears in an editor window. With pre-defined entry panels, a selection from a drop down menu can be made.

3.4.2.2 Change metadata in the attribute window

If an object table is activated, an entry can be changed using the attribute window

3.4.2.3 Adding to and overwriting input data

In general, this is only possible for constants, spatial variables and spatial and periodical variables. New data has to be imported for this like described in section 3.3.3.3. If desired, the data records are overwritten or just being added to.

3.4.2.4 Search and replace

MoRE also offers the opportunity to replace certain phrases by others (Figure 28). This for example may be helpful after the name of a variable has been changed. The new name then also has to be changed in the operations. At first, the object table calculation > data management > operations has to be activated. Afterwards, the replace button from the data grid's toolbar must be applied and the desired changes entered.

27

Figure 28: Search and replace

3.4.2.5 Renumber algorithms and calculation steps

Sometimes it is necessary, to alter the order of existing algorithms. The special function renumber algorithms from the data grid's toolbar is helpful for this. At first, the corresponding algorithm or algorithm stack must be selected. Using < x algorithms > or < x calculation steps > from the structure window shows a detailed view of the saved algorithms or calculation steps. Not all entries need to be numbered manually. If for example step 3 now ought to be behind step 5, it is sufficient to renumber it as step 5a. Then, the order can be adjusted using the special function renumber algorithm or renumber algorithm stacks.

3.4.3 Delete data records Data records of an object table can be deleted with the tool delete selected rows (Figure 29).

Figure 29: Deleting data records

3.4.4 Export of data records With the user interface of MoRE, contents of object table as well as input data or results can be exported to MS Excel.

3.4.4.1 Technical data tables

An activated object table is imported to Excel by using the button writing table to Excel in the data grid's toolbar.

28

3.4.4.2 Export of input data

Working with MoRE, sometimes it is neccesary to check input data on their accuracy and completeness. To accomplish this, a task for exporting input data has been integrated. Under the object tables input data > spatial variables and input data > spatial and periodical variables there is the special function export input data. With this Task, an Excel file is created which contains a data record analog to the data already imported.

3.4.4.3 Export of results

As described in section 3.3.5.2, calculated results can be exported to Excel. For further details see section 3.3.5.2.

3.4.5 Statistical analysis of input data MoRE offers the opportunity to statistically analyze spatial as well as spatial and periodical input data. Within the object table input data, there is a folder statistics. Minimum, maximum, arithmetical mean and standard deviation of all variables are to be found here. Please note that the value “-999” is used by default for data gaps.

3.4.6 Define selection fields In the object table metadata and calculation, new selection fields can be defined. This is done by creating a new data record at metadata > administration > selection fields or calculation > administration > selection fields. This may be relevant, if the user for example wants to embed a new unit. In name, the table is stated followed by the column's name (e.g. spatial variable > unit). At value, the unit is entered. The unit of the constant is created under spatial and periodical variables.

3.4.7 Customizing the interface Personal adjustments like the order of columns or hiding columns can be made by using checkmarks. These adjustments are saved for the corresponding user in excess of the current session and will be recalled in the next session. At the left top in the middle section of the MoRE Developer GUI, the table attributes can be displayed by right-clicking and then adjusted individually (Figure 30).

29

Figure 30: Personally adjusting the data grid

3.4.8 Attachment of files (flow charts) To gain a better overview of the basic principles of modeling, there is a flow chart attached to every algorithm stack as a .pdf-file in MoRE. Besides input data (including metadata) and formulas, the individual algorithms are also displayed on the flow chart. In principle, documents can also be attached to algorithms, formulas and input data. The document's format reaches from pictures over .pdf-files to video files. With the accordant button, all files may be attached. The file can also be saved by using drag & drop.

Figure 31: Attachment of documents for calculation

The attached symbol turns blue, when a document has been attached. With the same button, the attached file can be deleted again later.

3.4.9 Transparency and traceability The MoRE system was developed and realized under the intention of transparency and traceability. To keep the overview of possible changes while using MoRE, a protocol task was integrated. It does not work automatically and is not mandatory. However, it is recommended to register important and permanent adoptions accordingly. That way, other users can retrace them and reconstruct them after a longer time of development where required. Therefore, the individual alteration steps should be entered in metadata > administration > change

30

4 Visualizer The MoRE Visualizer graphical user interface (GUI) is a browser-based interface which enables the user to access the MoRE system's data base over the internet. The MoRE Visualizer GUI can be launched by any computer with internet access. Only an access authorization is required. In the MoRE data base, there are calculation results saved from the last certified MoRE version. This version contains modeled results for the period from 1983 to 2005. The MoRE Visualizer is an application used solely for presentation and analysis. The MoRE Visualizer enables the user to filter, analyze and display existing data for selected areas, periods and substances or substance groups. It is impossible to change or recalculate data in the data base with this application. Influence can be exerted rather on the way of the visualization. Selected data records can either be displayed directly on the map as a table or a diagram.

4.1 Access and login The link http://iswwpc-61.bau-verm.uni-karlsruhe.de/more/ opens the webpage of the MoRE Visualizer. The first step is the login with a registered user name and password (Figure 32) as well as the language selection. English and German are available.

Figure 32: Login

4.2 Menu navigation and interface

4.2.1 Overview Having logged in successfully, the MoRE Visualizer interface appears (Figure 33).

31

1

2 4 3

5 Figure 33: Overview of the MoRE Visualizer interface

The Visualizer interface is divided in five different parts. The top part contains the calendar

date and access information plus four tile tabs in the main menu bar 1 . In the main menu, a submenu containing additional preferences is opened corresponding to the tab selected.

The calibration window for view and properties is in the interface's left part . Two buttons at the very bottom of the calibration window enable the user to switch between these two domains (Figure 33). The calibration window's counterpart on the right side contains the workspace. For this

domain, the items Analysis, Notations and Print 3 are selected by the tab selection of the main menu. In the interface's center, a map with the larger rivers and important German cities is displayed by default. The level of displayed information changes depending on the zoom

factor. A menu bar for navigation is integrated in the top part of the map 4 . The status bar at the very bottom contains information about navigation and currently

selected items 5 . In essence, the interface can be divided in three major parts: The left window is for displaying and selecting the permanent view and the displayed properties, in the center, the information is visualized in a map and in the right window (work domain) criteria for analysis are being selected.

32

4.2.2 Main menu

Figure 34: The tabs of the main menu

The main menu is divided into four superordinate tabs (view, analysis, notations, print). Via these tabs the user may select which information respectively which tasks are displayed left and right in the interface. In addition the according submenu appears after selecting a tab (Figure 34). The tab "view" puts forward the information column displayed on the right. The tabs analysis, notations and print show the according submenu underneath the main menu bar and further options in the right window. With the tabs it is possible, to switch between these three windows by keeping the selected configuration.

4.2.3 Map display In the interface's center, a map with customized information and properties is displayed. There is a menu bar in the top center of the map (Figure 35). All tasks of this menu bar only apply to the map display. In the lower left part, a legend is displayed after the data request (Figure 36). The legend's properties are customized to the user and can be adjusted under properties.

Figure 35: Menu bar

Figure 36: Legend

33

Having selected the properties (section 4.3.2.1), the system requests the according

information from the data base 1 (Figure 37). The requesting process takes between seconds and minutes, depending on the size of the data record. After loading the new data record it is displayed on the centered map. The map is updated after any change in properties like zoom, pan etc. While the system is busy, a progress bar is displayed in the menu bar of the map (Figure 38).

Figure 37: Data request progress bar

Figure 38: Progress bar within the menu bar

4.2.4 Status bar The status bar gives basic information about the coordinates of the cursor position, the number of selected features as well as the zoom factor (Figure 39).

Figure 39: Status bar

Both side windows can be hidden to gain a better view of the map. While the tab display is selected, the view and properties window (left side) reappear. By selecting the tab analysis the corresponding information window comes to the foreground.

4.3 Task window

4.3.1 Display and properties The Visualizer interface's left window is divided into two different display modes. There are

the modes view and properties 2 to choose from. Two buttons at the very bottom of the calibration window enable the user to switch between these two domains.

4.3.1.1 Display properties

With the mode view (Figure 40), basic properties of the map display can be defined. They are displayed independent of the properties in the work domain (right menu window) and act as a general background to the requested data. Cities, rivers, analytical units, countries and

34

the global map can be selected and displayed. Additionally, administrative units can be selected.

.

1

Figure 40: Window of the mode "view"

4.3.1.2 Properties

After the execution of an analysis, the property window (Figure 41) automatically informs with a summarized overview of all analytical units or about a selection of them. The properties of the analytical units, of the discharge, of the emissions and of the area are displayed. Under the item area, the number of analytical units, the involved states and coordination areas, hierarchy information, the total inhabitant count and the total calculated area are displayed. The sub-item discharge shows all calculated discharge components individually. Emission summarizes all substance-specific emissions of selected areas and lays them out either for every emission pathway individually or as an added value. In area the shares of area of different land use types are is added up and displayed for all analytical units. In addition, the total area of selected analytical units is issued.

35

Figure 41: Property window

4.3.2 Analysis display

4.3.2.1 Analysis properties

The core function of the MoRE Visualizer resides under the tab "analysis" and is displayed in the right window. Via three menu selection fields "analytical units", "components and substances" as well as "comparison of time" the criteria for the selection of data to be visualized can be defined.

1. Analytical units The selection's spatial localization of data to be displayed can be defined by four different criteria (Figure 42). Each individual way can be selected via a drop down menu. Only the criterion currently opened has effect on the visualization of the data.

36

After clicking on the corresponding heading, the possible options are displayed. Figure 42 exemplary shows options for possible spatial criteria. The selection "analytical units" may never be zero.

Figure 42: Selection of spatial display criteria

37

2. Components and substances

Via the selection field components (Figure 43) six different parameters can be configured. The properties are linked hierarchal so the superordinate selection field has effects on the options of the field below. With the first drop down menu the desired component can be chosen. Possible components are discharge, emission or area. The selection of one of these options determines the content of the next selection field. If for example emission was chosen, the drop down menu specification only shows the ten possible emission pathways. A calculation of discharge components or the area is then not possible any more. Having chosen one or all (sum) emission pathways, the substance is defined. A substance can only be chosen after an emission pathway has been selected for not every pathway is relevant for each substance. For the pathway inland navigation, only PAH-emissions can be calculated. Now there are nine substances to be selected, PAH and eight different heavy metals. By selecting initial and final year, the period for the calculation is set. Using the drop down menu assignment the properties of the distribution are defined. The options auto, quantile and user are to choose from. Note that user can only be selected after the data has been displayed in auto or quantile first and a new value range has been defined. It is very important that the selected data can only be displayed if it lies within the defined value range. Analytical units with a value higher or lower will not be displayed in the map. By these selections, the results can be classified to different ranges of values and by that displayed in different manners. The option user allows it to customize the ranges of values, the color scale and the used colors and save it as a profile (Figure 48). The assigned configurations then are available for later analysis and do not need to be redone.

Figure 43: Selection of components and specifications

38

Figure 44: Selection for the comparison of time

3. Comparison of time The task comparison of time enables the user to compare data of two different years or periods (Figure 44). A checkmark at apply comparison of time has to be set. This enables the following drop down menus. Under comparison, the option period is selected followed by the according initial and final year for the relevant period. As a last adjustment, the unit of the comparison can be selected via the drop down menu value. The differences may be issued percental or as absolute values. After all relevant properties have been set, the button execute can be used to start the data request. After a short calculation time, the data is displayed in the map.

4.3.2.2 Submenu

The submenu -analysis contains four additional tasks (Figure 45).

Figure 45: Visualizer, main menu and additional tasks

The task field Fade in/out analysis, the last generated analysis can be hidden and brought back to the foreground again. The task Open reports is a more extensive tool to evaluate visualized or selected data. The drop down menu reports makes different versions of reports available. Under entries, a detailed configuration of the current visualization is given. The report summarized analytical units contains the common spatial properties of all analytical units to be found in the selection. The task analytical unit > individual lists the total metadata of selected analytical units. A display of the results > by component gives an overview of all relevant balance components and specification with their absolute and relative shares. The last menu item results > detailed lists part of the metadata as well as results for each analytical unit and calculation period. With the task field Export to Excel, every report can be saved as an Excel table and used for further analysis.

39

As a supplement to the reports the values of all or of a selection of selected analytical units can be shown as a bar chart using the task field diagrams. Possible input parameters and units are selected in the drop down menu Reports. The area, the discharge and the emissions can be issued (Figure 46). Like with the reports, charts can be exported here (Figure 47). After clicking an export diagram, a new browser window is opened. With the task "save picture as..." an exported graphic can be saved at any place. •

Figure 46: Reports and export

•

40

• Figure 47: Chart view

The task field range of values and color scheme opens a new window which enables the user to customize the configuration of color schemes and the ranges of values (Figure 48). With these task fields, saved configurations can be loaded or custom ones created and saved. After these properties have been adopted, the changes are effective for the current map view. •

41

Figure 48: Range of values and color scheme

4.3.3 Annotations A task within the tab Notations enables it to incorporate graphic items in the data on the map. These items can improve the visualization of the data. At first a new layer is created by clicking on create new layer. A menu window then asks for a name and description of the new layer (Figure 49). After the new layer has been created it appears in the right menu window. In addition to the displayed layer name and the time of creation a selection box and a pen symbol are selectable. If a checkmark is set in the box, the layer becomes visible on the map (Figure 50). An unchecked box hides the layer. With the pen the attribute window of the layer selected can be expanded. The layer's properties and additional information can be defined here subsequently. By double-clicking on the layer the corresponding graphic menu can be accessed. With the help of five buttons, different geometrical shapes can be generated or text can be written on the map (Figure 51). All created items are to find in their corresponding layer and are listed in the graphic mode under the graphic menu. By clicking on a graphic item the item is automatically centered and zoomed at on the map. Created items can be shown or hidden by assigning them to different layers.

42

Figure 49: Deposition of name and description of the new layer

Figure 50: Set checkmark to show a layer

Figure 51: Buttons for selecting items for the annotation

4.3.3.1 Sub menu

The sub menu offers tasks to handle different layers (Figure 52). New layers can be created or copied. A selected layer is copied by clicking on the copy button. The generated layer carries the default name "(1)" and does not contain any further information. In addition, the existing layers and annotations can be shown or hidden.

Figure 52: Annotation - sub menu

4.3.4 Print With the tab "print", the print layout can be modified in the right window (Figure 53). Upright or landscape format can be chosen and a caption be entered. The scale may be chosen between 1:500,000 and 1:1,700,000. If desired, a frame can be set for this print layout. The area to be printed can be set under Printable Area. It can be set on set on analytical area, set

43

to center and define via window. The last options allows to define any area for printing by drawing a rectangle on the map. The third option under printing

Figure 53: Print layout

44

5 Appendix

5.1 Nomenclature of the variables The names of the variables are composed of different abbreviations which are connected by underlines. The abbreviations are deduced from the English language. The first letter either stands for the category of the data (BI, PD, CD: Input data; IM: Intermediary result) or for the emission pathway (Table 1). Table 1: Abbreviation for the type of input data and the emission pathway

Abbre-viation

English term

BI basic info

PD periodical data

IM intermediate

CD country data

ER erosion

SR surface runoff

TD tile drainage

GW groundwater

AM abandoned mining

US urban systems

ID Industrial dischargers

WWTP Waste water treatment plant Following the first abbreviation and the underline, a more detailed definition of the variable follows. Abbreviations used for general terms are listed in Table 2. Table 2: Abbreviations for general terms

Abbre-viation

English term

A Area

Q Discharge/Runoff

PREC Precipitation

yr Yearly

s Summer

lt long term

E Emission

45

HM heavy metals

PAH polycyclic aromatic hydrocarbons

CONC Concentration

CONT Content With emissions, the end of the variable is composed like this: …_E_<substance group> <substance> e.g. ER_E_HM_CD, or SR_E_HM_ZN Whilst following abbreviations are used: Family Substance group Individual substances

or sum parameters Nutrients *_HM heavy metals CD, CR, CU, HG, NI,

PB, ZN *_PAH polycyclic aromatic

hydrocarbons PAK

5.2 Nomenclature calculation steps, algorithms and algorithm stacks The name of calculation steps, algorithms and algorithm stacks is composed like this: Calculation steps carry the algorithm's name and are only distinguished by their number. Algorithms on the other hand have distinct names, which are composed like the following: Component > assigned algorithm stack > name of the algorithm e.g.: Emissions > emissions via erosion > enrichment factor Algorithm stacks: Component > specification e.g..: Areas > areas contributing to groundwater recharge water balance > groundwater runoff Emissions > heavy metal emissions via groundwater

5.3 Parser tasks Table 3 embraces the most important symbols and operators which are needed when entering formulas. To integrate a formula functional into the system, the regard of these tasks is essential.

46

Table 3: Parser tasks in MoRE

47

6 References Behrendt, H., Huber, P., Kornmilch, M, Ley, M., Opitz, D., Schmoll, O., Scholz, G. & Uebe,R. (2000): Nutrient Emissions into River Basins. UBA-Texte, 23/00 European Parliament and the Council of the European Union (EP) (2008): Directive 2008/105/EC of the European Parliament and of the Council of 16 December 2008 on environmental quality standards in the field of water policy Fuchs, S., Scherer, U., Wander, R., Behrendt, H., Venohr, M., Opitz, D., Hillenbrand, Th., Marscheider-Weidemann, F., Götz, Th. (2010): Calculation of Emissions into Rivers in Germany using the MONERIS Model. Nutrients, heavy metals and polycyclic aromatic hydrocarbons. UBA-Texte 46/2010, Dessau