Difference between revisions of "Water balance outputs across tools"
m |
m |
||
(2 intermediate revisions by the same user not shown) | |||
Line 1: | Line 1: | ||
− | Modelling tools differ in the hydrological processes, or water balance elements (fluxes and storages), that they calculate individually, save, and allow users to export for further analyses. The table below covers what each software tool outputs, meaning what can be saved as a timeseries of flow rates, fluxes, or storage volumes or depths, and for what ''spatial scale'' or modelled units these can be output. Output file formats are | + | Modelling tools differ in the hydrological processes, or water balance elements (fluxes and storages), that they calculate individually, save, and allow users to export for further analyses. The table below covers what each software tool outputs, meaning what can be saved as a timeseries of flow rates, fluxes, or storage volumes or depths, and for what ''spatial scale'' or modelled units these can be output (e.g. output for each grid cell, HRU, subcatchment, or catchment total). Output file formats are covered [[Modelling tool user interfaces#Formats of input and output data|here]]. |
</br></br> | </br></br> | ||
− | '''Note:''' The table differentiates between the case in which a tool does not output its calculation of a certain flux or storage (Output = "no") and the case in which the tool does not explicitly model | + | The spatial scales at which the software can output values gives an indication of how much external calculation work a user may need to do in order to find out about a flux or store of particular interest. For example, we often wish to know the ET water use of a particular vegetation type, likely to compare with another type. ACRU and SWAT will output AET components for individual HRUs, however if there are multiple HRUs of the same land cover type within the model type, these tools will not compile an area-weighted average for the cover type across the whole modelled area. The user would need to do that manually outside the tool using the individual HRU outputs. MIKE-SHE can do this compilation within the software as the user can specify a polygon that covers the full area of a cover class and the tool will compile fluxes for that polygon. |
− | For cases where the tool does output a flux but uses a different name for it that has been used in the table row heading, this has been noted in brackets below. For more terminology comparison across tools, see further coverage [[Terminology#Hydrological process and parameter terms across tools|here]]. | + | </br></br> |
+ | '''Note:''' The table differentiates between the case in which a ''tool does not output'' its calculation of a certain flux or storage (Output = "no") and the case in which the ''tool does not explicitly model'' the listed process ("not modelled"), meaning it's not part of the model's calculations. In the case when a tool ''does model'' a process, but ''does not output'' the results of this calculation, the user could potentially consult the tools' user guide and attempt to calculate the process themselves using the algorithm that is applied in the software and other components that can be output. In cases where a calculation would be relatively simple, and based only on other outputs covered in the table, the calculation approach has been given in the table.</br> | ||
+ | For cases where the tool does output a flux but uses a different name for it that has been used in the table row heading, this has been noted in brackets below. For more terminology comparison across tools, see further coverage [[Terminology#Hydrological process and parameter terms across tools|here]]. </br> | ||
+ | Some of the fluxes listed in the table are net totals of component fluxes which are also listed in the table (e.g. total AET or total evaporation & transpiration = canopy interception evaporation + AET from soil + AET from GW + evaporation off water bodies, where applicable). Some tools model and output each separately and may or may not output each individually. Some provide outputs of the total and the components, some just the components and the user would need to sum them if the total was of interest. Some calculate a total of some or all in a single step and output the total. | ||
{| class="wikitable" | {| class="wikitable" | ||
! scope="col" style="width:15em" colspan="2" rowspan="2" |Flux or storage | ! scope="col" style="width:15em" colspan="2" rowspan="2" |Flux or storage | ||
− | ! colspan="6" | '''Tool output and/or calculation approach''' | + | ! colspan="6" | '''''Tool output and/or calculation approach''''' |
|- | |- | ||
− | ! scope="col" style="background: #F2CEE0; width:8em" |WRSM-Pitman </br>(Sami GW) | + | ! scope="col" style="background: #F2CEE0; width:8em" |WRSM-Pitman </br><small>(Sami GW) |
− | ! scope="col" style="background: #F2D4CE; width:8em" |SPATSIM-Pitman </br>(Hughes GW) | + | ! scope="col" style="background: #F2D4CE; width:8em" |SPATSIM-Pitman </br><small>(Hughes GW) |
! scope="col" style="background: #CEF2CE; width:8em" |ACRU4 | ! scope="col" style="background: #CEF2CE; width:8em" |ACRU4 | ||
! scope="col" style="background: #F2F2CE; width:8em" |SWAT2012 | ! scope="col" style="background: #F2F2CE; width:8em" |SWAT2012 | ||
! scope="col" style="background: #CEE6F2; width:8em" |MIKE-SHE, | ! scope="col" style="background: #CEE6F2; width:8em" |MIKE-SHE, | ||
− | [[Coverage of structural options within modelling tools#MIKE-SHE|semi-distributed,</br>more conceptual]] | + | [[Coverage of structural options within modelling tools#MIKE-SHE|<small>semi-distributed,</br>more conceptual]] |
! scope="col" style="background: #CEDAF2; width:8em" |MIKE-SHE, | ! scope="col" style="background: #CEDAF2; width:8em" |MIKE-SHE, | ||
− | [[Coverage of structural options within modelling tools#MIKE-SHE|fully-distributed,</br>more physical]] | + | [[Coverage of structural options within modelling tools#MIKE-SHE|<small>fully-distributed,</br>more physical]] |
|- | |- | ||
Line 100: | Line 103: | ||
| style="background: #F5FCFF; vertical-align: top; text-align:center;” | <small>subcatchment aquifer, catchment | | style="background: #F5FCFF; vertical-align: top; text-align:center;” | <small>subcatchment aquifer, catchment | ||
| style="background: #F5F8FF; vertical-align: top; text-align:center;” | <small>grid cell, polygon, catchment, (aquifer layer or all) | | style="background: #F5F8FF; vertical-align: top; text-align:center;” | <small>grid cell, polygon, catchment, (aquifer layer or all) | ||
+ | |- | ||
+ | | rowspan="2"; style="vertical-align: top"|'''Evaporation from surface water body''' | ||
+ | | style="vertical-align: top" | ''Output''<big></big> | ||
+ | | style="background: #FFF5FA; vertical-align: top; text-align:center;" |no | ||
+ | | style="background: #FFF7F5; vertical-align: top; text-align:center;" |'''YES'''<big></big> | ||
+ | | style="background: #F5FFF5; vertical-align: top; text-align:center;" |'''YES'''<big></big> | ||
+ | | style="background: #FFFFF5; vertical-align: top; text-align:center;" |'''YES'''<big></big> | ||
+ | | style="background: #F5FCFF; vertical-align: top; text-align:center;" |'''YES'''<big></big> | ||
+ | | style="background: #F5F8FF; vertical-align: top; text-align:center;" |'''YES'''<big></big> | ||
+ | |- | ||
+ | | style="vertical-align: top" | ''Scale''<big></big> | ||
+ | | style="background: #FFF5FA; vertical-align: top; text-align:center;” | | ||
+ | | style="background: #FFF7F5; vertical-align: top; text-align:center;” | <small>water body | ||
+ | | style="background: #F5FFF5; vertical-align: top; text-align:center;” | <small>water body | ||
+ | | style="background: #FFFFF5; vertical-align: top; text-align:center;” | <small>water body (includes river reaches) | ||
+ | | style="background: #F5FCFF; vertical-align: top; text-align:center;” | <small>water body (includes river reaches), surface ponding: grid cell, polygon, catchment | ||
+ | | style="background: #F5F8FF; vertical-align: top; text-align:center;” | <small>water body (includes river reaches), surface ponding: grid cell, polygon, catchment | ||
|- | |- | ||
| rowspan="2"; style="vertical-align: top"|'''Runoff (RO) total''' | | rowspan="2"; style="vertical-align: top"|'''Runoff (RO) total''' | ||
Line 173: | Line 193: | ||
| style="background: #F5F8FF; vertical-align: top; text-align:center;” | <small>grid cell, polygon, catchment, (aquifer layer or all) | | style="background: #F5F8FF; vertical-align: top; text-align:center;” | <small>grid cell, polygon, catchment, (aquifer layer or all) | ||
|- | |- | ||
− | | rowspan="2"; style="vertical-align: top"|'''Aquifer GW flow | + | | rowspan="2"; style="vertical-align: top"|'''Channel to aquifer''' |
+ | | style="vertical-align: top" | ''Output''<big></big> | ||
+ | | style="background: #FFF5FA; vertical-align: top; text-align:center;" |'''YES'''<big></big> | ||
+ | | style="background: #FFF7F5; vertical-align: top; text-align:center;" |'''YES'''<big></big> | ||
+ | | style= "vertical-align: top; text-align:center;" | <small> not modelled | ||
+ | | style="background: #FFFFF5; vertical-align: top; text-align:center;" |no | ||
+ | | style="background: #F5FCFF; vertical-align: top; text-align:center;" |'''YES'''<big></big> | ||
+ | | style="background: #F5F8FF; vertical-align: top; text-align:center;" |'''YES'''<big></big> | ||
+ | |- | ||
+ | | style="vertical-align: top" | ''Scale''<big></big> | ||
+ | | style="background: #FFF5FA; vertical-align: top; text-align:center;” | <small>river module | ||
+ | | style="background: #FFF7F5; vertical-align: top; text-align:center;” | <small>subcatchment | ||
+ | | style="background: "vertical-align: top; text-align:center;” | | ||
+ | | style="background: #FFFFF5; vertical-align: top; text-align:center;” | <small>''channel to "bank store", not output, need to back-calculate for reach | ||
+ | | style="background: #F5FCFF; vertical-align: top; text-align:center;” | <small>river reach | ||
+ | | style="background: #F5F8FF; vertical-align: top; text-align:center;” | <small>river reach; grid cell, polygon, catchment (aquifer layer) | ||
+ | |- | ||
+ | | rowspan="2"; style="vertical-align: top"|'''Aquifer GW flow, into or out of a model unit, remaining as GW''' | ||
| style="vertical-align: top" | ''Output''<big></big> | | style="vertical-align: top" | ''Output''<big></big> | ||
| style="background: #FFF5FA; vertical-align: top; text-align:center;" |no<big></big> | | style="background: #FFF5FA; vertical-align: top; text-align:center;" |no<big></big> | ||
Line 191: | Line 228: | ||
| style="background: #F5FCFF; vertical-align: top; text-align:center;” | <small> (subcatchment) | | style="background: #F5FCFF; vertical-align: top; text-align:center;” | <small> (subcatchment) | ||
| style="background: #F5F8FF; vertical-align: top; text-align:center;” | <small>grid cell, polygon, catchment, (aquifer layer or all) | | style="background: #F5F8FF; vertical-align: top; text-align:center;” | <small>grid cell, polygon, catchment, (aquifer layer or all) | ||
+ | |- | ||
+ | | rowspan="2"; style="vertical-align: top"|'''Water body storage''' | ||
+ | | style="vertical-align: top" | ''Output''<big></big> | ||
+ | | style="background: #FFF5FA; vertical-align: top; text-align:center;" |'''YES'''<big></big> | ||
+ | | style="background: #FFF7F5; vertical-align: top; text-align:center;" |'''YES'''<big></big> | ||
+ | | style="background: #F5FFF5; vertical-align: top; text-align:center;" |'''YES'''<big></big> | ||
+ | | style="background: #FFFFF5; vertical-align: top; text-align:center;" |'''YES'''<big></big> | ||
+ | | style="background: #F5FCFF; vertical-align: top; text-align:center;" |'''YES'''<big></big> | ||
+ | | style="background: #F5F8FF; vertical-align: top; text-align:center;" |'''YES'''<big></big> | ||
+ | |- | ||
+ | | style="vertical-align: top" | ''Scale''<big></big> | ||
+ | | style="background: #FFF5FA; vertical-align: top; text-align:center;” | | ||
+ | | style="background: #FFF7F5; vertical-align: top; text-align:center;” | <small>water body | ||
+ | | style="background: #F5FFF5; vertical-align: top; text-align:center;” | <small>water body | ||
+ | | style="background: #FFFFF5; vertical-align: top; text-align:center;” | <small>water body | ||
+ | | style="background: #F5FCFF; vertical-align: top; text-align:center;” | <small>water body, surface ponding: grid cell, polygon, catchment | ||
+ | | style="background: #F5F8FF; vertical-align: top; text-align:center;” | <small>water body, surface ponding: grid cell, polygon, catchment | ||
|- | |- | ||
| rowspan="2"; style="vertical-align: top"|'''Soil profile storage''' | | rowspan="2"; style="vertical-align: top"|'''Soil profile storage''' | ||
Line 228: | Line 282: | ||
| rowspan="2"; style="vertical-align: top"|'''Percolation out of soil storage''' | | rowspan="2"; style="vertical-align: top"|'''Percolation out of soil storage''' | ||
| style="vertical-align: top" | ''Output''<big></big> | | style="vertical-align: top" | ''Output''<big></big> | ||
− | | style="background: #FFF5FA; vertical-align: top; text-align:center;" |'''YES'''<big></big></br><small>(‘total recharge’) | + | | style="background: #FFF5FA; vertical-align: top; text-align:center;" |'''YES'''<big></big></br><small>(‘total recharge’ - lagged to aquifer, excess becomes interflow) |
− | | style="background: #FFF7F5; vertical-align: top; text-align:center;" |'''YES'''<big></big></br><small>(same as recharge) | + | | style="background: #FFF7F5; vertical-align: top; text-align:center;" |'''YES'''<big></big></br><small>(same as aquifer recharge below) |
− | | style="background: #F5FFF5; vertical-align: top; text-align:center;" |'''YES'''<big></big></br><small>(same as recharge) | + | | style="background: #F5FFF5; vertical-align: top; text-align:center;" |'''YES'''<big></big></br><small>(same as aquifer recharge below) |
− | | style="background: #FFFFF5; vertical-align: top; text-align:center;" |'''YES'''<big></big> | + | | style="background: #FFFFF5; vertical-align: top; text-align:center;" |'''YES'''<big></big></br><small>(lagged to aquifer) |
− | | style="background: #F5FCFF; vertical-align: top; text-align:center;" |'''YES'''<big></big> | + | | style="background: #F5FCFF; vertical-align: top; text-align:center;" |'''YES'''<big></big></br><small>(goes to 'interflow store') |
− | | style="background: #F5F8FF; vertical-align: top; text-align:center;" |'''YES'''<big></big> | + | | style="background: #F5F8FF; vertical-align: top; text-align:center;" |'''YES'''<big></big></br><small>(same as aquifer recharge below) |
|- | |- | ||
| style="vertical-align: top" | ''Scale''<big></big> | | style="vertical-align: top" | ''Scale''<big></big> | ||
Line 245: | Line 299: | ||
| rowspan="2"; style="vertical-align: top"|'''Aquifer recharge''' | | rowspan="2"; style="vertical-align: top"|'''Aquifer recharge''' | ||
| style="vertical-align: top" | ''Output''<big></big> | | style="vertical-align: top" | ''Output''<big></big> | ||
− | | style="background: #FFF5FA; vertical-align: top; text-align:center;" |'''YES'''<big></big></br><small>(‘aquifer recharge’) | + | | style="background: #FFF5FA; vertical-align: top; text-align:center;" |'''YES'''<big></big></br><small>(‘aquifer recharge’) |
| style="background: #FFF7F5; vertical-align: top; text-align:center;" |'''YES'''<big></big> | | style="background: #FFF7F5; vertical-align: top; text-align:center;" |'''YES'''<big></big> | ||
| style="background: #F5FFF5; vertical-align: top; text-align:center;" |'''YES'''<big></big></br><small>(B-horizon soil ‘SaturatedFlow’ + ‘UnsaturatedFlow’) | | style="background: #F5FFF5; vertical-align: top; text-align:center;" |'''YES'''<big></big></br><small>(B-horizon soil ‘SaturatedFlow’ + ‘UnsaturatedFlow’) |
Latest revision as of 09:50, 4 December 2023
Modelling tools differ in the hydrological processes, or water balance elements (fluxes and storages), that they calculate individually, save, and allow users to export for further analyses. The table below covers what each software tool outputs, meaning what can be saved as a timeseries of flow rates, fluxes, or storage volumes or depths, and for what spatial scale or modelled units these can be output (e.g. output for each grid cell, HRU, subcatchment, or catchment total). Output file formats are covered here.
The spatial scales at which the software can output values gives an indication of how much external calculation work a user may need to do in order to find out about a flux or store of particular interest. For example, we often wish to know the ET water use of a particular vegetation type, likely to compare with another type. ACRU and SWAT will output AET components for individual HRUs, however if there are multiple HRUs of the same land cover type within the model type, these tools will not compile an area-weighted average for the cover type across the whole modelled area. The user would need to do that manually outside the tool using the individual HRU outputs. MIKE-SHE can do this compilation within the software as the user can specify a polygon that covers the full area of a cover class and the tool will compile fluxes for that polygon.
Note: The table differentiates between the case in which a tool does not output its calculation of a certain flux or storage (Output = "no") and the case in which the tool does not explicitly model the listed process ("not modelled"), meaning it's not part of the model's calculations. In the case when a tool does model a process, but does not output the results of this calculation, the user could potentially consult the tools' user guide and attempt to calculate the process themselves using the algorithm that is applied in the software and other components that can be output. In cases where a calculation would be relatively simple, and based only on other outputs covered in the table, the calculation approach has been given in the table.
For cases where the tool does output a flux but uses a different name for it that has been used in the table row heading, this has been noted in brackets below. For more terminology comparison across tools, see further coverage here.
Some of the fluxes listed in the table are net totals of component fluxes which are also listed in the table (e.g. total AET or total evaporation & transpiration = canopy interception evaporation + AET from soil + AET from GW + evaporation off water bodies, where applicable). Some tools model and output each separately and may or may not output each individually. Some provide outputs of the total and the components, some just the components and the user would need to sum them if the total was of interest. Some calculate a total of some or all in a single step and output the total.
Flux or storage | Tool output and/or calculation approach | ||||||
---|---|---|---|---|---|---|---|
WRSM-Pitman (Sami GW) |
SPATSIM-Pitman (Hughes GW) |
ACRU4 | SWAT2012 | MIKE-SHE, | MIKE-SHE, | ||
AET total | Output | calculate: |
calculate: |
calculate: |
calculate: |
YES | YES |
Scale | (runoff module) | (subcatchment) | (HRU) | (HRU) | grid cell, polygon, catchment | grid cell, polygon, catchment | |
Canopy interception evaporation | Output | no | YES | YES | YES | YES | |
Scale | subcatchment | HRU | grid cell, polygon, catchment | grid cell, polygon, catchment | |||
AET from soil | Output | no | YES | YES | YES | YES | YES |
Scale | subcatchment | HRU | HRU, subcatchment, catchment | grid cell, polygon, catchment | grid cell, polygon, catchment | ||
AET from GW | Output | no | no | not modelled (exception: riparian HRU approximation) |
YES (‘Revap’) |
YES | YES |
Scale | HRU | subcatchment aquifer, catchment | grid cell, polygon, catchment, (aquifer layer or all) | ||||
Evaporation from surface water body | Output | no | YES | YES | YES | YES | YES |
Scale | water body | water body | water body (includes river reaches) | water body (includes river reaches), surface ponding: grid cell, polygon, catchment | water body (includes river reaches), surface ponding: grid cell, polygon, catchment | ||
Runoff (RO) total | Output | YES | YES | YES | YES | YES | YES |
Scale | runoff module, route (any scale) | subcatchment | HRU, subcatchment, catchment | HRU, subcatchment, catchment | river cross section | river cross section | |
Surface runoff | Output | calculate: |
YES | calculate: |
YES | YES | YES |
Scale | runoff module | subcatchment | HRU | HRU, subcatchment, catchment | grid cell, polygon, catchment | grid cell, polygon, catchment | |
Interflow | Output | YES | YES (‘soil moisture runoff’) |
YES (‘DelayedStormflow’) |
YES (‘Lateral Q’) |
YES | YES (saturated zone, upper layer) |
Scale | runoff module | subcatchment | HRU | HRU, subcatchment, catchment | subcatchment interflow reservoir | grid cell, polygon, catchment | |
Aquifer to channel | Output | YES | YES | YES | YES | YES | YES |
Scale | runoff module | subcatchment | HRU, subcatchment | HRU, subcatchment, catchment | subcatchment aquifer, catchment | grid cell, polygon, catchment, (aquifer layer or all) | |
Channel to aquifer | Output | YES | YES | not modelled | no | YES | YES |
Scale | river module | subcatchment | channel to "bank store", not output, need to back-calculate for reach | river reach | river reach; grid cell, polygon, catchment (aquifer layer) | ||
Aquifer GW flow, into or out of a model unit, remaining as GW | Output | no | YES | not modelled | GW can ‘leave’ catchment by recharging an inactive deep aquifer |
GW can ‘leave’ catchment by recharging an inactive deep aquifer or ‘dead storage’ |
YES |
Scale | subcatchment | (subcatchment) | (subcatchment) | grid cell, polygon, catchment, (aquifer layer or all) | |||
Water body storage | Output | YES | YES | YES | YES | YES | YES |
Scale | water body | water body | water body | water body, surface ponding: grid cell, polygon, catchment | water body, surface ponding: grid cell, polygon, catchment | ||
Soil profile storage | Output | YES | YES | YES | YES | YES | YES |
Scale | runoff module | subcatchment | soil layer in HRU | HRU, subcatchment, catchment | grid cell, polygon, catchment | grid cell, polygon, catchment | |
Aquifer storage | Output | YES | no | YES | YES | YES | YES |
Scale | runoff module | HRU, subcatchment | HRU, subcatchment | subcatchment aquifer, catchment | grid cell, polygon, catchment, (aquifer layer or all) | ||
Percolation out of soil storage | Output | YES (‘total recharge’ - lagged to aquifer, excess becomes interflow) |
YES (same as aquifer recharge below) |
YES (same as aquifer recharge below) |
YES (lagged to aquifer) |
YES (goes to 'interflow store') |
YES (same as aquifer recharge below) |
Scale | runoff module | subcatchment | HRU | HRU, subcatchment | grid cell, polygon, catchment | grid cell, polygon, catchment | |
Aquifer recharge | Output | YES (‘aquifer recharge’) |
YES | YES (B-horizon soil ‘SaturatedFlow’ + ‘UnsaturatedFlow’) |
YES | YES | YES |
Scale | runoff module | subcatchment | HRU, subcatchment | HRU, subcatchment | subcatchment aquifer, catchment | grid cell, polygon, catchment, (aquifer layer or all) |