Inundation Model J2000-Flood
From ILMS-Wiki
(Difference between revisions)
(→Adaption of the J2000 towards the J2000-Flood) |
(→Adaption of the J2000 towards the J2000-Flood) |
||
| Line 13: | Line 13: | ||
*Replace the JAMS component ''StandardEntityReader'' with the ''StandardEntityReaderUpstreamTopo'', which adds a two-directional linkage between entities to define flood direction from each river segment. | *Replace the JAMS component ''StandardEntityReader'' with the ''StandardEntityReaderUpstreamTopo'', which adds a two-directional linkage between entities to define flood direction from each river segment. | ||
| + | |||
*Add the component ''flooding.SubbasinFlooding'' at the ende of the ''ReachLoop''. In case of overflow of a river segment this component iterates over (elevation-sorted) HRUs and distributes the water as described above. | *Add the component ''flooding.SubbasinFlooding'' at the ende of the ''ReachLoop''. In case of overflow of a river segment this component iterates over (elevation-sorted) HRUs and distributes the water as described above. | ||
| + | |||
*Add a ''DoubleConditionalContext'' in the ''HRULoop'' and include the original soil module as well as a second one to allow different parametrizations for flooded and non-flooded HRUs (configuration: if ''floodVolume'' is zero the soil module for non-flooded HRUs will be executed and the other way around). | *Add a ''DoubleConditionalContext'' in the ''HRULoop'' and include the original soil module as well as a second one to allow different parametrizations for flooded and non-flooded HRUs (configuration: if ''floodVolume'' is zero the soil module for non-flooded HRUs will be executed and the other way around). | ||
| + | |||
*Add the component ''VariableAdder'' at the the beginning of the ''HRULoop'' to add the ''floodVolume'' to the depression storage (outVar:''actDPS''), which will hold the flood water and interacts with the ground and the atmosphere. A duplication of the ''VariableAdder'' (place it just below) could be useful (outVar: ''actDPS2'') to see the level of the depression storage (actual flood level) before it interacts with the ground and the atmosphere in each time step. | *Add the component ''VariableAdder'' at the the beginning of the ''HRULoop'' to add the ''floodVolume'' to the depression storage (outVar:''actDPS''), which will hold the flood water and interacts with the ground and the atmosphere. A duplication of the ''VariableAdder'' (place it just below) could be useful (outVar: ''actDPS2'') to see the level of the depression storage (actual flood level) before it interacts with the ground and the atmosphere in each time step. | ||
| + | |||
*Make sure that all new variables (''floodHeight, floodVolume, ...'') are set to zero at the beginning of each time step. | *Make sure that all new variables (''floodHeight, floodVolume, ...'') are set to zero at the beginning of each time step. | ||
Revision as of 12:42, 8 February 2017
Please note: UNDER CONSTRUCTION!
A floodplain simulation extension, characterized as a conceptual and easily transferable approach that is simultaneously not overly data and resource intensive, as well as easily parameterizable, was developed and integrated into the modelling process of the J2000 modelling system. This extension was developed with the goal of simulating wetland inundation within the model. Due to the data scarcity typical of remote catchments, the extension's parameters (HRU elevation and river width) could be obtained from remote sensing data only.
On an iterative basis the water height in each river segment is compared to the elevation of its neighboring HRU. In case flooding occurs, the HRU floods its topological connected model entities, until the flood level is too low to spread any further. Technically the distributed water volume is stored in the exceeded depression storage, which interacts with soil and atmosphere.
Fig.: Schematic concept of a J2000(-Flood) model (left) including the inundation extension (right)
Adaption of the J2000 towards the J2000-Flood
To apply the J2000-Flood modelling system the following components need to be replaced or added in the JAMS Builder:
- Replace the JAMS component StandardEntityReader with the StandardEntityReaderUpstreamTopo, which adds a two-directional linkage between entities to define flood direction from each river segment.
- Add the component flooding.SubbasinFlooding at the ende of the ReachLoop. In case of overflow of a river segment this component iterates over (elevation-sorted) HRUs and distributes the water as described above.
- Add a DoubleConditionalContext in the HRULoop and include the original soil module as well as a second one to allow different parametrizations for flooded and non-flooded HRUs (configuration: if floodVolume is zero the soil module for non-flooded HRUs will be executed and the other way around).
- Add the component VariableAdder at the the beginning of the HRULoop to add the floodVolume to the depression storage (outVar:actDPS), which will hold the flood water and interacts with the ground and the atmosphere. A duplication of the VariableAdder (place it just below) could be useful (outVar: actDPS2) to see the level of the depression storage (actual flood level) before it interacts with the ground and the atmosphere in each time step.
- Make sure that all new variables (floodHeight, floodVolume, ...) are set to zero at the beginning of each time step.
