Difference between revisions of "Model units & connections"
Line 14: | Line 14: | ||
{| class="wikitable" | {| class="wikitable" | ||
|+<span id = "structure overview - Table Anchor"> <big>Model structure overviews by tool</big></span> | |+<span id = "structure overview - Table Anchor"> <big>Model structure overviews by tool</big></span> | ||
− | ! scope="col" style="width:10%"| Element | + | ! scope="col" style="width:10%"| Level / Element |
− | ! scope="col" style="background: #F2CEE0; width:15%" |WRSM-Pitman (Sami GW) | + | ! scope="col" style="background: #F2CEE0; width:15%" |WRSM-Pitman |
− | ! scope="col" style="background: #F2D4CE; width:15%" |SPATSIM-Pitman (Hughes GW) | + | (Sami GW) |
+ | ! scope="col" style="background: #F2D4CE; width:15%" |SPATSIM-Pitman | ||
+ | (Hughes GW) | ||
! scope="col" style="background: #CEF2CE; width:15%" |ACRU4 | ! scope="col" style="background: #CEF2CE; width:15%" |ACRU4 | ||
! scope="col" style="background: #F2F2CE; width:15%" |SWAT2012 | ! scope="col" style="background: #F2F2CE; width:15%" |SWAT2012 | ||
− | ! scope="col" style="background: #CEE6F2; width:15%" |MIKE-SHE, semi-distributed, more conceptual | + | ! scope="col" style="background: #CEE6F2; width:15%" |MIKE-SHE, |
− | ! scope="col" style="background: #CEDAF2; width:15%" |MIKE-SHE, fully-distributed, more physical | + | semi-distributed, more conceptual |
+ | ! scope="col" style="background: #CEDAF2; width:15%" |MIKE-SHE, | ||
+ | fully-distributed, more physical | ||
|- | |- | ||
| style="vertical-align: top" |'''Catchments''' | | style="vertical-align: top" |'''Catchments''' | ||
Line 27: | Line 31: | ||
'''(subcats)''' | '''(subcats)''' | ||
− | | style="background: #FFF5FA; vertical-align: top" | | + | | style="background: #FFF5FA; vertical-align: top" |WRSM catchments are composed of ‘modules’ linked in a user-specified network. |
Module types: | Module types: | ||
− | + | * runoff modules, | |
+ | * special area modules (see below) | ||
+ | * channel modules | ||
+ | * reservoir modules | ||
− | + | “Subcatchments” are not explicitly input. Runoff modules and sets of linked modules are effectively subcats. | |
− | + | | style="background: #FFF7F5; vertical-align: top" |SPATSIM catchments are composed of subcatchments. | |
− | |||
− | |||
− | |||
− | |||
− | |||
− | “Subcatchments” are not | ||
− | | style="background: #FFF7F5; vertical-align: top" | | ||
Line 49: | Line 49: | ||
− | | style="background: #F5FFF5; vertical-align: top" | | + | | style="background: #F5FFF5; vertical-align: top" |ACRU4 catchments are composed of subcatchments. |
Line 59: | Line 59: | ||
− | | style="background: #FFFFF5; vertical-align: top" | | + | | style="background: #FFFFF5; vertical-align: top" |SWAT catchments are composed of subcatchments. |
− | |||
+ | Subcats are linked in a spatially determined flow network (delineated from input <!-- Digital elevation model (DEM): gridded dataset in which each grid cell has an elevation value. --> by tool or given as a map input) | ||
− | | style="background: #F5FCFF; vertical-align: top" | | + | |
+ | | style="background: #F5FCFF; vertical-align: top" |MIKE catchments can be composed of subcatchments. | ||
Subcats are linked in spatially determined flow network (map input). | Subcats are linked in spatially determined flow network (map input). | ||
− | | style="background: #F5F8FF; vertical-align: top" | | + | | style="background: #F5F8FF; vertical-align: top" |MIKE catchments can be composed of 3D grid units. The surface is uniformly sized grid cells. Each cell has a column beneath: input layers of soil, sediment, rock. |
− | |||
− | The surface is uniformly sized grid cells. Each cell has a column beneath: | ||
Line 82: | Line 81: | ||
'''subcatchments''' | '''subcatchments''' | ||
− | | style="background: #FFF5FA; vertical-align: top" |A ‘runoff module’ with no linked special | + | | style="background: #FFF5FA; vertical-align: top" |A WRSM ‘runoff module’ with no linked special areas functions as a subcat. If special area modules are linked, then a set of modules functions as a subcat. |
Special area modules that can be added are: | Special area modules that can be added are: | ||
− | + | * tree plantations, | |
− | + | * alien vegetation, | |
− | + | * irrigation | |
− | + | * mines | |
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | + | These appear as separate units, but function as sub-areas inside a specified linked runoff module. | |
− | + | Runoff modules can also have internally specified subareas: | |
+ | * impervious area | ||
+ | * riparian area (ET from GW). | ||
− | + | | style="background: #FFF7F5; vertical-align: top" |SPATSIM subcatchments all contain a river channel and may have specified special sub-areas. Subcats can optionally include either a wetland or a reservoir/lake on the channel at the subcat outlet. | |
− | |||
− | |||
− | + | A special sub-area can be defined for any, or all, of the following in a subcat: | |
− | + | * impervious area | |
+ | * riparian area (ET from GW) | ||
+ | * area with a higher ET land cover (forest, tree plantation, IAP) | ||
+ | * area with irrigation from dams | ||
+ | * area with irrigation from river | ||
+ | * small dams internal to subcat (lumped) | ||
− | + | Impervious, high ET cover, and irrigation areas do not have defined spatial locations within the subcat. | |
+ | | style="background: #F5FFF5; vertical-align: top" |ACRU4 subcatchments are composed of one or more HRUs. Non-headwater subcats must contain a river channel. Subcats can optionally include additional channels and reservoir units. Units are linked in a user-specified network. | ||
− | |||
− | |||
− | + | There are special HRUs for: | |
+ | * impervious areas, | ||
+ | * irrigated areas, | ||
+ | * riparian areas | ||
+ | * wetlands. | ||
− | |||
+ | For most HRUs, all runoff is routed directly to a channel, reservoir, or subcat outlet node (in parallel). | ||
+ | ''Optional exceptions:'' For ‘riparian HRUs’, ‘baseflow’ output from other HRUs can be routed to the riparian HRU soil. | ||
− | + | For ‘adjunct-impervious HRUs’, runoff is routed to the surface of another HRU. | |
+ | | style="background: #FFFFF5; vertical-align: top" |SWAT subcatchments are composed of: | ||
− | + | * HRUs (many) | |
+ | * shallow aquifer unit, | ||
+ | * deep aquifer unit, | ||
+ | * tributary channel unit | ||
+ | * main river channel unit. | ||
− | + | Subcats can include an internal pond or wetland and a reservoir/lake on the channel at the subcat outlet. | |
− | |||
− | + | HRU surface & ‘lateral’ runoff output is routed directly to the subcat channel (in parallel). This passes via the tributary channel, where delays & infiltration can occur, to the main channel. | |
− | |||
− | + | Groundwater is modelled at the subcat scale. Aquifers are recharged by all subcat HRUs. Shallow aquifer outflow goes to the subcat main channel. | |
− | |||
+ | | style="background: #F5FCFF; vertical-align: top" |MIKE-SHE subcatchments are composed of: | ||
− | + | * grid cells (veg & soil) | |
+ | * ‘overland flow zones’, | ||
+ | * ‘interflow reservoirs’ | ||
+ | * ‘baseflow reservoirs’ | ||
+ | * river channel links | ||
− | Surface runoff is lumped for cells | + | Surface runoff is lumped for grid cells within an overland flow zone & routed across zones in a downslope series to the channel (potential for infiltration on route). |
− | Interflow reservoirs receive percolation from overlying grid cells. Interflow | + | Interflow reservoirs receive percolation from overlying grid cells. Interflow is laterally routed through a downslope series to the channel (potential for loss to recharge on route). Baselfow reservoirs are recharged by overlying interflow reservoirs and outflow to the channel in parallel. |
− | | style="background: #F5F8FF; vertical-align: top" | | + | | style="background: #F5F8FF; vertical-align: top" |Using fully distributed MIKE-SHE, no subcat boundaries are input; water surface elevations on the surface and in the 3D grid drive flow directions. |
Revision as of 14:04, 7 June 2021
The table below and schematic diagrams describe the overall discretisation approach used in each tool. This page describes how modelling tools allow users to discretise catchments into modelled units in order to represent and calculate hydrological processes. Differentiating the catchment into separate components or units, such as subcatchments, patches of similar land cover, soil layers with distinct properties, allows hydrological processes to be modelled by algorithms that have been developed for that scale and type of unit.
Each modelling tool has a unique way of describing a catchment in terms of:
- The types surface and subsurface model units that can be included
- The connections that can be defined between these different units
- The process algorithms that are used to calculate inflows, storage, and outflows for each unit
This page summarises the unit types and connection options available across the tools, while their process algorithms are described here. Although described on separate pages the discretisation and process algorithms are inextricably linked. This page also summarises some implications of the structural differences across the tools, which are dealt with in more detail for some specific model application contexts here.
Overarching approaches by tool
The schematic diagrams and tables below describe the overall discretisation approaches used in each tool and for two generalised set-up approaches in MIKE-SHE (rationale and description of these found here).
Level / Element | WRSM-Pitman
(Sami GW) |
SPATSIM-Pitman
(Hughes GW) |
ACRU4 | SWAT2012 | MIKE-SHE,
semi-distributed, more conceptual |
MIKE-SHE,
fully-distributed, more physical |
---|---|---|---|---|---|---|
Catchments
& subcatchments (subcats) |
WRSM catchments are composed of ‘modules’ linked in a user-specified network.
Module types:
“Subcatchments” are not explicitly input. Runoff modules and sets of linked modules are effectively subcats. |
SPATSIM catchments are composed of subcatchments.
|
ACRU4 catchments are composed of subcatchments.
|
SWAT catchments are composed of subcatchments.
Subcats are linked in a spatially determined flow network (delineated from input by tool or given as a map input)
|
MIKE catchments can be composed of subcatchments.
|
MIKE catchments can be composed of 3D grid units. The surface is uniformly sized grid cells. Each cell has a column beneath: input layers of soil, sediment, rock.
|
Units within
subcatchments |
A WRSM ‘runoff module’ with no linked special areas functions as a subcat. If special area modules are linked, then a set of modules functions as a subcat.
Special area modules that can be added are:
These appear as separate units, but function as sub-areas inside a specified linked runoff module.
|
SPATSIM subcatchments all contain a river channel and may have specified special sub-areas. Subcats can optionally include either a wetland or a reservoir/lake on the channel at the subcat outlet.
A special sub-area can be defined for any, or all, of the following in a subcat:
Impervious, high ET cover, and irrigation areas do not have defined spatial locations within the subcat. |
ACRU4 subcatchments are composed of one or more HRUs. Non-headwater subcats must contain a river channel. Subcats can optionally include additional channels and reservoir units. Units are linked in a user-specified network.
There are special HRUs for:
For ‘adjunct-impervious HRUs’, runoff is routed to the surface of another HRU. |
SWAT subcatchments are composed of:
Subcats can include an internal pond or wetland and a reservoir/lake on the channel at the subcat outlet.
|
MIKE-SHE subcatchments are composed of:
Surface runoff is lumped for grid cells within an overland flow zone & routed across zones in a downslope series to the channel (potential for infiltration on route).
|
Using fully distributed MIKE-SHE, no subcat boundaries are input; water surface elevations on the surface and in the 3D grid drive flow directions.
|
River channels | Channels are modules in the network with multiple inflow and outflow links possible.
Channel modules can have an associated wetland storage/area. |
Channels are units linked to subcats (one per subcat).
They receive the local (incremental) subcat runoff & upstream subcat channel outflows. |
Channels are necessary units in non-headwater subcats. Subcats can have multiple channel units.
Channels receive runoff from linked HRUs, reservoirs, & upstream subcat outflows. |
Channels are units linked to subcats (one main channel per subcat).
They receive the local (incremental) subcat runoff & upstream subcat channel outflows. |
Channels are composed of spatially explicit reaches between node points. Reaches with nodes mapped inside a subcat exchange water with the subcat. | Channels are composed of spatially explicit reaches between node points. Reaches can exchange water with grid cells that border them. |
Specific units & connections
Links between discretisation and process representation
The scale of discretisation of the landscape influences which hydrological processes are individually represented and the algorithms and the timesteps that are appropriate (discussed in more detail here). In general, for larger spatial/vertical units, longer timesteps, more lumped process representation, and different property parameters are applicable compared to modelling with smaller units. This has to do with how long it’s likely to take for water to move through a unit. For example, it may take a week for interflow to move through the 10 km long hillslope of subcatchment, but a day to move through the 1 km slope length of a patch of grassland within that subcatchment. Speeds vary by process. This also has to do with the fact that what we may model as one process at a larger spatial scale can be the result of several different processes occurring at smaller scales. For example, rain falling on a steep, rocky cliff may form surface runoff, but if this surface runoff then flows across an area of permeable and unsaturated soil before reaching a stream channel, some may infiltrate and not reach the stream as surface flow. If one models a subcatchment where this is happening as a single unit, the equation and parameters for estimating ‘surface runoff generation’ would account for the net outcome of surface runoff reaching the stream, i.e. the combined impact of the cliff and permeable toeslope on surface runoff reaching the channel. If modelling the cliff and the toeslope as separate units, surface runoff on the cliff unit could be calculated and then surface flow and infiltration on the toeslope unit could be calculated as a separate set of processes.