...
Return type: (dictionary)
2.8 Open Water
Open Water in the Urbanwb model refers to all controlled Open Water bodies, e.g. ditches, canals and ponds. In the Urbanwb model the open water has a fixed target level. Above this level, water will be discharged to outside water, limited by a user defined discharge capacity. In the Urbanwb model, the minimum open water level is the defined target water level. If evaporation losses result in water level below the target level, water will be let in (with unlimited capacity) from outside water to maintain the target water level. Open Water can be deemed as an abstract term reflecting system storage capacity. By assumption, all runoff from Unpaved and all sewer overflow into the street flow directly to the Open Water. Also, sewer system outflow and groundwater drainage will recharge the Open Water. During simulation, under successive heavy rain events, Open Water level may exceed the target level due to insufficient storage capacity and discharge capacity, indicating there is excessive water that the urban water system cannot handle. This can represent all kinds of real urban flood phenomena. In the current version of the Urbanwb model water above surface elevation level cannot flow (directly) to the other surface areas and cause flooding in these areas. Hence the maximum water level in the Open Water is not limited. The storage height above the target Open Water level is calculated to understand the storage requirements of the water system. Maximum storage height on Open Water for a certain flood event multiplied with the Open Water area reflects the required storage capacity for the total study area for that event. To sum up, Open Water component is an abstract recipient water body that indicates the required storage capacity of the system. Figure 13 shows the schematic overview of the Open Water.
Figure 13 Schematic overview of Open Water (OW) in Urbanwb
2.8.1 Assumptions
- All runoff from UP in a time step flows to OW in that same time step.
- All sewer overflow into the street from SWDS and MSS in a time step flows directly to OW in that same time step.
- A target OW level is defined as a level below the surface level. This is the lower limit of the OW level. For instance, the target OW level is set 1.5 m-SL, then the computed OW level x can only be higher than this level (x ≤ 1.5). Above this level (x < 1.5), discharge from OW to outside water starts. The outside water is not part of the model, and discharge from OW to outside is only limited by a predefined pumping capacity. Note, this pumping capacity can be applied as the discharge capacity in the Storage-Discharge-Frequency (SDF) curves, where the storages are calculation results of the Urbanwb.
2.8.2 Calculation order
- Determine total runoff from UP to OW for the current time step.
- Determine drainage from GW to OW for the current time step.
- Determine total outflow from SWDS and MSS to OW and the total sewer overflow into the street from SWDS and MSS to OW for the current time step.
- Determine inflow from measure (if applicable) to OW for the current time step.
- Determine discharge from OW to outside water for the current time step.
- Determine OW level at the end of the current time step.
2.8.3 Code and input arguments
class urbanwb.openwater.OpenWater(ow_no_meas_area, q_ow_out_cap, ow_level, **kwargs) [source]
Bases: object
Creates an instance of OpenWater class with given initial states and properties, iterates sol() function to compute states and fluxes of Open Water at each time step.
Parameters:
- ow_no_meas_area (float) – area of Open Water without measure [m^2]
- q_ow_out_cap (float) – discharge capacity from Open Water (internal) to outside water (external) [mm/d]
- ow_level (float) – predefined target Open Water level, also the initial Open Water level (at t=0) [m-SL]
sol(p_atm, e_pot_ow, r_up_ow, d_gw_ow, q_swds_ow, q_mss_ow, so_swds_ow, so_mss_ow, meas_ow, up_no_meas_area, gw_no_meas_area, swds_no_meas_area, mss_no_meas_area, tot_meas_area, tot_area, delta_t=0.041666666666666664) [source]
Calculates states and fluxes on Open Water during current time step.
Parameters:
- p_atm (float) – rainfall during current time step [mm]
- e_pot_ow (float) – potential Open Water evaporation during current time step [mm]
- r_up_ow (float) – runoff from Unpaved to Open Water during current time step [mm]
- d_gw_ow (float) – drainage from groundwater to Open Water during current time step [mm]
- q_swds_ow (float) – Outflow from storm water drainage system (SWDS) to Open Water during current time step [mm]
- q_mss_ow (float) – Outflow from combined sewer system (MSS) to Open Water during current time step [mm]
- so_swds_ow (float) – Sewer overflow of storm water drainage system (SWDS) during current time step [mm]
- so_mss_ow (float) – Sewer overflow of combined sewer system (MSS) during current time step [mm]
- meas_ow (float) – inflow from measure (if applicable) to Open Water during current time step [mm]
- up_no_meas_area (float) – area of Unpaved without measure [m^2]
- gw_no_meas_area (float) – area of groundwater without measure [m^2]
- swds_no_meas_area (float) – area of storm water drainage system (SWDS) without measure [m^2]
- mss_no_meas_area (float) – area of combined sewer system (MSS) without measure [m^2]
- tot_meas_area (float) – total area of measure [m^2]
- tot_area (float) – total area of study area [m^2]
- delta_t (float) – length of time step [d]
Returns: A dictionary of computed states and fluxes of Open Water during current time step:
- prec_ow – Direct rainfall on Open Water during current time step [mm]
- e_atm_ow – Evaporation from Open Water during current time step [mm]
- sum_r_ow – Total runoff from Unpaved to Open Water during current time step [mm]
- sum_d_ow – Drainage from groundwater to Open Water during current time step [mm]
- sum_q_ow – Total outflow from sewer systems to Open Water during current time step [mm]
- sum_so_ow – Total sewer overflow from sewer systems to Open Water during current time step [mm]
- r_meas_ow – Inflow from measure (if applicable) to Open Water during current time step [mm]
- q_ow_out – Discharge from Open Water to outside water during current time step [mm]
Return type: (dictionary)
2.9 Measure
Urban flooding is usually attributed to three types: pluvial flooding, fluvial flooding and coastal flooding. Pluvial flooding occurs when an extremely heavy rainfall saturates the storage capacity of the water system and excess water cannot be absorbed. Fluvial flooding occurs when rivers burst their bank as a result of sustained or intense rainfall. Coastal flooding occurs in coastal area as a result of extreme tidal conditions like storm surges. Unlike other types of flooding, pluvial flooding is a direct, quick and localized consequence of rainfall, and it is a predominantly urban phenomenon as it is in urban area where the effects are most pronounced and damaging (Susana). The Urbanwb model simulates only the pluvial flooding in urban water systems through two indicators, sewer overflow into the street and storage height above the target open water level. Climate change is predicted to increase the intensity and frequency of extreme rainfall events. Together with further urbanization and rapid growing population, this may result in increased urban pluvial flood risks. To effectively adapt to increasing flood risks, a combination of intervention strategies is required, including structural infrastructure, nature-based solutions, early warning system, risk financing instrument, etc. The Urbanwb model is capable of modelling all kinds of physical adaptation measures. Physical measures can be categorized into artificial structural infrastructure and nature-based solutions. Structural infrastructure refers to grey infrastructure are considered to be engineering projects that use concrete and steel, while nature-based solutions refer to blue-green infrastructure that depend on water, plants and ecosystem services. Blue-green infrastructure is the strategic use of networks of natural lands, working landscapes, and other open spaces to conserve ecosystem values and functions and provide associated benefits to human populations (Benedict & McMahon, 2006). Blue-green infrastructure is generally decentralized. Water is captured and treated where it falls, rather than being transported to a treatment facility. Blue-green infrastructure terminology can also be used in the context of low impact development (LID). Grey infrastructure refers to the human-engineered infrastructure for water resources such as water and wastewater treatment plants, pipelines, and reservoirs. Grey infrastructure typically refers to components of a centralized approach to water management. Examples of grey infrastructure are canals, levees, ditches, raised curbs, underground off-line tanks, etc. Examples of blue-green infrastructure are rainwater harvesting, water squares, urban wetlands, green roofs, bioswales, etc. A module named Measure is creatively developed in the Urbanwb model to model the physical urban adaptation measures. With the ingenious setup of this module, underlying mechanisms of these physical measures are simulated and incorporated into the dynamics of the entire modelling of water system. The next sections provide detailed descriptions on the structure of the Measure module.
Measures mitigate urban flooding by means of creating extra storage, encouraging evapotranspiration, facilitating infiltration, increasing drainage and the combination of these interventions. Consequently, despite many types/terms of urban adaptation measures, they can be categorized and modelled under certain framework with specific settings. The underlying idea and fundamental principle of this Measure module is to provide a general adaptive framework that represents the measures’ physical dimensions and that mimics the measures’ predominant functionality.
Measures in the Urbanwb model can be defined in a 1-layer, 2-layer or 3-layer structure (Figure 14 ).
Figure 14 Layer principle of measures in Urbanwb
1-layer structures contain only an interception layer (layer no. 1), which can represent the type of measures that creates storage and allows evaporation. A typical example of a 1-layer measure is a blue roof.
2-layer structures consist of 2 layers, an interception layer (layer no. 1) and a bottom storage layer (layer no.3). The bottom storage layer is the most sophisticated part of the measure module. In the bottom storage layer, evapotranspiration, percolation to groundwater and controlled runoff (to anywhere) can be defined by the user. Controlled runoff means the runoff volume that is first stored in the measure is discharged in a controlled way. Basically, controlled runoff implies either “continuously delayed released” to the urban water system or “instantaneously released at a much later time”, when the urban water system is able to handle this runoff again, most likely by means of real time control systems. Urban water system is referring to the entire water system, hence incorporating all elements described in the sections above. In the current Urbanwb model real time control is not incorporated and is simulated by a small constant discharge over a large number of time steps to one of the subsystems SWDS, GW, OW. Continuous slow release is defined as a dynamically-computed flux that dependents on a head difference and a flow resistance. Examples of 2-layer measures are rain barrel, wet pond, infiltration box, etc.
3-layer structures consist of 3 layers, an interception layer (layer no. 1), a top storage layer (layer no. 2) and a bottom storage layer (layer no.3). Extra, compared to the 2-layer measures is the top storage layer. This layer is especially added to model measures like green roofs and bioswales. These measures have a growing medium that encourages evapotranspiration and a drainage layer beneath the growing medium that drains excessive water to the sewer system. Some examples are provided in next paragraph to inspire the user how to conceptualize a measure into this Measure module.
The setup of the measures involves expert judgement: “the model is only as good as the modeler”.
Below some examples of how to conceptualize measures are provided:
- Blue roof
Blue roofs (without drainage) create extra water storage on buildings from where water can evaporate. A blue roof can be considered as a storage installation. In the Urbanwb model, it can be simulated with the basic model or with the Measure module. Simulating a blue roof with the basic model can be done by increasing the PR interception capacity. However, then interception capacity of the entire PR area increases. To simulate that in only part of the PR area blue roofs are applied, the Measure module can be used. A blue roof can be conceptualized as a 1-layer structure of which an interception layer with certain storage capacity is defined from where only evaporation is possible. Exceedance of the storage capacity results in overflow. Overflow from a blue roof is considered to be uncontrolled runoff and will be drained to the SWDS. - Wet pond:
Figure 15 shows the schematic view of how wet pond is conceptualized. An artificial wet pond can be seen as a 2-layer structure, of which the interception layer is a pseudo layer that has no storage capacity and infinite infiltration capacity, allowing all water (precipitation and inflow runoff from contributing area) to flow directly into the bottom storage layer. A wet pond usually has a sealed concrete bottom to prevent it from falling dry thus percolation is defined not possible. The wet pond has a certain threshold (drainage level) above which the excess water is slowly drained. This runoff is called controlled runoff. The higher the water level in the pond above this threshold, the faster it drains. In addition, a drainage resistance has to be defined by the user to determine how fast it drains. Evaporation from the pool is possible and is limited by Penman evaporation. In case of very extreme rainfall events, incoming runoff may completely fill the storage capacity of wet pond, hence overflow from the wet pond occurs. Unlike controlled runoff from bottom storage layer, this overflow is an uncontrolled runoff, and will be drained eventually to SWDS.
Figure 15 Conceptualization of a wet pond. Source left figure: [LID].
- Bioswale and green roof
Figure 16 shows the schematic view of how bioswale is conceptualized. A bioswale is an infiltration installation. An bioswale can be thought as a 3-layer structure, of which the surface vegetated soil is the interception layer that provides limited storage capacity and facilitates infiltration to the growing medium. The growing medium is the top storage layer where plant transpiration and soil evaporation occur. After evapotranspiration, excessive water infiltrates into the bottom drainage layer. Below the growing medium is the gravel drainage layer encouraging water percolating into the groundwater reservoir. Here the percolation flux can be modelled either as percolation to groundwater limited by saturated permeability of soil, or as a controlled runoff to groundwater dependent on predefined drainage level and resistance to mimic the water jamming. Evaporation from the bottom drainage layer is possible when potential evapotranspiration rate exceeds the transpiration from growing medium (top storage layer), to simulate that the plant roots can uptake water from drainage layer for further transpiration. Overflow from the bottom drainage layer and surface overflow from interception layer together form the uncontrolled runoff, which will be drained to the SWDS. Similar to a bioswale, a green roof is also modelled as a 3-layer structure. However, there are two major differences: 1. A green roof is installed on the building roof, thus controlled runoff directs to the SWDS instead of to GW; 2. The calculation formula for green roofs is specifically modified to make sure no surface submergence from green roof is possible because a normally functioning green roof should have no water logging on the surface.
Figure 16 Conceptualization of a bioswale. Source left figure: [LID].
2.9.1 Assumptions
- A measure can be defined as 3-layer. Even though the area of each layer of measure can be defined different, it is not recommended to do so because it has not been fully tested yet.
- The measure inflow area does not necessarily come from one source. For instance, if a measure is defined in the OP area, it is possible to define the measure inflow area not only in the OP area but also in the PR and the CP area. However, these possibilities have not been fully developed and tested yet. It’s users’ responsibility to pay attention to the boundary conditions of the model.
- Not all measures can be implemented with Measure module or implemented with the Urbanwb model. The user should understand the correct way of using this Urbanwb model and should be careful with the limitations of this model.
2.9.2 Calculation order
- Determine the rainfall on the measure for the current time step.
- Determine the runoff from the measure inflow area to the measure for the current time step.
- Determine the initial interception storage of measure. Initial interception water budge includes interception storage at the end of previous time step + rainfall + runoff from measure inflow area in case runoff is defined to flow to interception layer.
- Determine the evaporation from the interception layer of the measure, limited by Penman evaporation.
- Determine the downward infiltration from the interception layer. Downward infiltration from the interception layer is only possible when the measure structures contain at least 2 layers.
Note: Downward infiltration calculation for a green roof is separately defined. - Determine the surface overflow from the interception layer of the measure.
- Determine the final interception storage on the interception layer of the measure.
- Determine initial storage in top storage layer of measure. When measure structure contains only 2 layers. This storage is zeros (when 2 layer — no top storage layer is involved, all the variable related to top storage layer will be zero.) When 3 layer, initial storage in top storage layer of measure is storage at previous time step + downward infiltration from interception layer.
- Determine transpiration from top storage layer of measure, limited by water availability and Penman evaporation multiplied with a predefined reduction factor.
- Determine the percolation from the top storage layer of the measure to the bottom storage layer of the measure.
Note: This variable is separately defined for green roof type measures. - Determine the final storage in the top storage layer of the measure, limited by the predefined storage capacity of the top storage layer of the measure.
- Determine the initial storage in the bottom storage layer of the measure.
- Determine the evapotranspiration from the bottom storage layer of the measure. Transpiration from the bottom storage layer can only occur when defined possible and when the transpiration capacity exceeds the transpiration from the top storage layer in case of 3 layers.
- Determine the percolation from the bottom storage layer of the measure to the groundwater. Specify whether this percolation is limited by the groundwater level or not. If not, the limitation will only be the saturated permeability. It is recommended to specify percolation being not limited by the groundwater level.
- Determine the controlled runoff from the bottom storage level of the measure. The controlled runoff can be modelled as either a constant flux or as a dynamically-computed flux that depends on a user defined drainage level and resistance.
- Determine the final storage of the bottom storage layer of the measure.
- Determine the overflow from the bottom storage layer of the measure if the bottom layer is completely filled.
- Determine the outflow from the measure to OW, UZ, GW, SWDS, MSS, Out
2.9.3 Code and input arguments
class urbanwb.measure.Measure(tot_meas_area, runoff_to_stor_layer, intstor_meas_t0, EV_evaporation, num_stor_lvl, infilcap_int_meas, storcap_top_meas, storcap_btm_meas, stor_top_meas_t0, stor_btm_meas_t0, storcap_int_meas, top_meas_area, ET_transpiration, evaporation_factor_meas, IN_infiltration, infilcap_top_meas, btm_meas_area, btm_meas_transpiration, connection_to_gw, limited_by_gwl, k_sat_uz, btm_level_meas, btm_discharge_type, runoffcap_btm_meas, dischlvl_btm_meas, c_btm_meas, surf_runoff_meas_OW, ctrl_runoff_meas_OW, overflow_meas_OW, surf_runoff_meas_UZ, ctrl_runoff_meas_UZ, overflow_meas_UZ, surf_runoff_meas_GW, ctrl_runoff_meas_GW, overflow_meas_GW, surf_runoff_meas_SWDS, ctrl_runoff_meas_SWDS, overflow_meas_SWDS, surf_runoff_meas_MSS, ctrl_runoff_meas_MSS, overflow_meas_MSS, surf_runoff_meas_Out, ctrl_runoff_meas_Out, overflow_meas_Out, greenroof_type_measure, **kwargs) [source]
Bases: object
Creates an instance of Measure class with given initial states and properties, iterates sol() function to compute states and fluxes of measure at each time step.
Parameters:
- tot_meas_area (float) – total area of measure [m^2]
- num_stor_lvl (int) – predefined number of storage layers [1, 2 or 3]
- runoff_to_stor_layer (int) – predefined selection at which measure layer runoff from other area is stored, inflow runoff can only take place at interception layer (1) or at bottom storage layer (3) [1 or 3]
- Active processes (#) –
- EV_evaporation (int) – predefined selection if evaporation from measure interception layer is possible (1) or not (0) [0 or 1]
- ET_transpiration (int) – predefined selection if evapotranspiration from measure is possible (1) or not (0) [0 or 1]
- IN_infiltration (int) – predefined selection if infiltration from measure is possible (1) or not (0) [0 or 1]
- SD_delay (int) – predefined selection if slow drainage from measure is possible (1) or not (0) [0 or 1]
- FD_pumping (int) – predefined selection if fast drainage from measure is possible (1) or not (0) [0 or 1]
- RTC_realtime (#) – predefined selection if real- me-control release from measure is possible (1) or not (0) [0 or 1]
- Interception layer (#) –
- storcap_int_meas (float) – predefined storage capacity of interception layer of measure [mm]
- infilcap_int_meas (float) – predefined infiltration capacity of interception layer of measure [mm/d]
- stor_int_meas_t0 (float) – initial storage in interception layer of measure (at t=0) [mm]
- Top storage layer (#) –
- top_meas_area (float) – predefined area of top storage layer of measure [m^2]
- storcap_top_meas (float) – predefined storage capacity of top storage layer of measure [mm]
- infilcap_top_meas (float) – predefined infiltration capacity of top storage layer of measure [mm/d]
- stor_top_meas_t0 (float) – initial storage in top storage layer of measure (at t=0) [mm]
- Bottom storage layer (#) –
- btm_meas_area (float) – predefined area of bottom storage layer of measure [m^2]
- storcap_btm_meas (float) – predefined storage capacity of bottom storage layer of measure [mm]
- connection_to_gw (int) – predefined percolation (connection) from measure bottom storage layer to groundwater is possible (1) or not (0) [0 or 1]
- limited_by_gwl (int) – predefined limitation of percolation from measure to groundwater if groundwater level is below measure bottom level, limited (1) or unlimited (0) [0 or 1]
- btm_level_meas (float) – predefined bottom level of measure [m-SL]
- btm_meas_transpiration (int) – predefined selection if transpiration from bottom storage layer of measure is possible (1) or not (0) [0 or 1]
- btm_discharge_type (int) – predefined discharge type from bottom storage layer of measure [0:flux or 1:level]
- runoffcap_btm_meas (float) – predefined runoff capacity from bottom storage layer of measure [mm/d]
- dischlvl_btm_meas (float) – predefined discharge level from bottom storage layer of measure [mm]
- c_btm_meas (float) – predefined hydraulic resistance for level induced discharge from bottom storage layer of measure [d]
- k_sat_uz (float) – saturation permeability of soil [mm/d]
- evaporation_factor_meas (float) – predefined evaporation factor of measure [-]
- stor_btm_meas_t0 (float) – initial storage in bottom storage layer of measure (at t=0) [mm]
- Runoff from measure flows to (#) –
- surf_runoff_meas_OW (int) – predefined definition of surface runoff from measure storage 1 (interception level) to Open Water (0 = no, 1 = yes)
- ctrl_runoff_meas_OW (int) – predefined definition of controlled runoff from measure storage 3 (bottom level) to Open Water (0 = no, 1 = yes)
- overflow_meas_OW (int) – predefined definition of overflow from measure storage 3 (bottom level) to Open Water (0 = no, 1 = yes)
- surf_runoff_meas_UZ (int) – predefined definition of surface runoff from measure storage 1 (interception level) to Unsaturated Zone (0 = no, 1 = yes)
- ctrl_runoff_meas_UZ (int) – predefined definition of controlled runoff from measure to Unsaturated Zone (0 = no, 1 = yes)
- overflow_meas_UZ (int) – predefined definition of overflow from measure to Unsaturated Zone (0 = no, 1 = yes)
- surf_runoff_meas_GW (int) – predefined definition of surface runoff from measure to groundwater (0 = no, 1 = yes)
- ctrl_runoff_meas_GW (int) – predefined definition of controlled runoff from measure to groundwater (0 = no, 1 = yes)
- overflow_meas_GW (int) – predefined definition of overflow from measure to groundwater (0 = no, 1 = yes)
- surf_runoff_meas_SWDS (int) – predefined definition of surface runoff from measure to storm water drainage system (0 = no, 1 = yes)
- ctrl_runoff_meas_SWDS (int) – predefined definition of controlled runoff from measure to storm water drainage system (0 = no, 1 = yes)
- overflow_meas_SWDS (int) – predefined definition of overflow from measure to storm water drainage system (0 = no, 1 = yes)
- surf_runoff_meas_MSS (int) – predefined definition of surface runoff from measure to mixed sewer system (0 = no, 1 = yes)
- ctrl_runoff_meas_MSS (int) – predefined definition of controlled runoff from measure to mixed sewer system (0 = no, 1 = yes)
- overflow_meas_MSS (int) – predefined definition of overflow from measure to mixed sewer system (0 = no, 1 = yes)
- surf_runoff_meas_Out (int) – predefined definition of surface runoff from measure to outside water (0 = no, 1 = yes)
- ctrl_runoff_meas_Out (int) – predefined definition of controlled runoff from measure to outside water (0 = no, 1 = yes)
- overflow_meas_Out (int) – predefined definition of overflow from measure to outside water (0 = no, 1 = yes)
sol(p_atm, e_pot_ow, r_pr_meas, r_cp_meas, r_op_meas, r_up_meas, pr_no_meas_area, cp_no_meas_area, op_no_meas_area, up_no_meas_area, gw_no_meas_area, gwl_prevt, delta_t) [source]
Calculates states and fluxes in measure during current time step.
Parameters:
- p_atm (float) – rainfall during current time step [mm]
- e_pot_ow (float) – potential Open Water evaporation during current time step [mm]
- r_pr_meas (float) – runoff from Paved Roof to measure during current time step [mm]
- r_cp_meas (float) – runoff from Closed Paved to measure during current time step [mm]
- r_op_meas (float) – runoff from Open Paved to measure during current time step [mm]
- r_up_meas (float) – runoff from Unpaved to measure during current time step [mm]
- pr_no_meas_area (float) – area of Paved Roof without measure [m^2]
- cp_no_meas_area (float) – area of closed pave without measure [m^2]
- op_no_meas_area (float) – area of Open Paved without measure [m^2]
- up_no_meas_area (float) – area of Unpaved without measure [m^2]
- gw_no_meas_area (float) – area of groundwater without measure [m^2]
- gwl_prevt (float) – groundwater level at previous time step [m-SL]
- delta_t (float) – length of time step [d]
Returns: A dictionary of computed states and fluxes of measure during current time step:
- prec_meas – Direct rainfall on measure during current time step [mm]
- sum_r_meas – Total runoff from Paved Roof, Closed Paved, Open Paved, Unpaved to measure during current time step [mm]
- int_meas – Interception storage on interception layer of measure after rainfall at the beginning of current time step [mm]
- e_atm_meas – Evaporation form interception layer of measure during current time step [mm]
- interc_down_meas – Downward flow from interception layer of measure during current time step [mm]
- surf_runoff_meas – Surface runoff from interception layer of measure during current time step [mm]
- intstor_meas – Remaining interception storage on interception layer of measure during current time step [mm]
- ini_stor_top_meas – Storage in top storage layer of measure at the beginning of current time step [mm]
- t_atm_top_meas – Transpiration from top storage layer of measure during current time step [mm]
- perc_top_meas – Percolation from top layer of measure at the current time step [mm]
- fin_stor_top_meas – top layer storage at the end of current time step [mm]
- ini_stor_btm_meas – bottom layer storage at the beginning of current time step [mm]
- t_atm_btm_meas – transpiration from bottom layer of measure at the current time step [mm]
- p_gw_btm_meas – percolation from bottom layer of measure to groundwater during current time step [mm]
- runoff_btm_meas – runoff from the bottom layer of the measure during current time step [mm]
- fin_stor_btm_meas – bottom storage at the end of the current time step [mm]
- overflow_btm_meas – bottom storage overflow during current time step [mm]
- q_meas_ow – Measure outflow to Open Water during current time step [mm]
- q_meas_uz – Measure outflow to Unsaturated Zone during current time step [mm]
- q_meas_gw – Measure outflow to groundwater during current time step [mm]
- q_meas_swds – Measure outflow to storm water drainage system during current time step [mm]
- q_meas_mss – Measure outflow to mixed sewer system during current time step [mm]
- q_meas_out – Measure outflow to outside water during current time step [mm]
Return type: (dictionary)