Note: This is documentation for version 4.9 of Source. For a different version of Source go to the Space Directory.
Page tree
Skip to end of metadata
Go to start of metadata

The Australian Water Balance Model (AWBM) is a catchment water balance model that relates daily rainfall and evapotranspiration to runoff, and calculates losses from rainfall for flood hydrograph modelling. The model contains five stores; three surface stores to simulate partial areas of runoff, a base flow store and a surface runoff routing store.

Scale

AWBM operates at the functional unit scale and at a daily time-step.

The model can be applied at sub-daily intervals, provided the values of the recession values are appropriate to the chosen timestep.

Principal developer

Cooperative Research Centre for Catchment Hydrology. The original model was developed by Dr Walter Boughton (Boughton, 2004).

Scientific provenance

AWBM has been applied in many Australian catchments by the original author (Boughton) and by several other hydrologists. The extent of its use outside Australia is unknown but it is not expected to have been widely applied outside of Australia. There is nothing particularly unique to Australia in the conceptual structure of AWBM but it would require calibration and testing to catchments outside of Australia to confirm its suitability.

Version

Source v3.8.10

Rainfall Runoff Library v1.0.5, June 25, 2004

http://www.toolkit.net.au/Tools/RRL

Dependencies

None.

Availability and conditions

AWBM is automatically installed with Source. AWBM is also available through the Rainfall Runoff Library on eWater Toolkit: http://www.toolkit.net.au/Tools/RRL.

Structure and processes

AWBM uses three surface stores (C1, C2 and C3) to simulate three partial areas (A1, A2 and A3) of runoff. The water balance of each surface store is calculated independently of the others (Figure 1).

 

Figure 1. Structure of the AWBM rainfall-runoff model

 

By default, the model calculates the moisture balance of each partial area at daily time-steps. At each time-step, rainfall is added to each of the three surface moisture stores and evapotranspiration is subtracted from each store. If the value of moisture in the store becomes negative, it is reset to zero, as the evapotranspiration demand is superior to the available moisture. If the value of moisture in the store exceeds the capacity of the store, the moisture in excess of the capacity becomes runoff and the store is reset to the capacity.

The catchment area is divided into 3 subareas: A1, A2 and A3, each representing e.g. user defined land use or soil classifications as proportions of the area of the catchment. The sum of A1, A2 and A3 must be 1. Only A1 and A2 are set by the user and the remaining area proportion, A3, is calculated internally as A3 = 1 - (A1 + A2). Default area parameter values are:

  • A1 = 0.134
  • A2 = 0.433 and, therefore
  • A3 = 0.433

 

If the user enters values of A1 and A2 that do not satisfy the constraint of adding up to less than 1, then the AWBM model will rescale these parameters to ensure that A1 + A2 + A3 = 1. These rescaled values are not reported to the user.

The rescaling method used by AWBM is:

where:

A1 and A2 are the original values entered by the user, and

A1new, A2new and A3 are the new values used by AWBM

 

Part of total surface runoff becomes recharge of the base flow store. The fraction of the runoff used to recharge the base flow store is:

BFI • runoff

where:

BFI = base flow index, ie. the ratio of base flow to total flow in the stream flow

The remainder of the runoff, ie. ((1.0 - BFI• runoff), becomes surface runoff.

 

The base flow store is depleted at the rate of (1.0 - K) • BS where:

BS = the current moisture in the base flow store, and

K = the base flow recession constant of the time-step being used (typically daily).

 

The surface runoff can be routed through a store if required to simulate the delay of surface runoff reaching the outlet of a medium to large catchment. The surface runoff store acts in the same way as the base flow store, and is depleted at the rate of (1.0 - KS)•SS, where SS is the current moisture in the surface runoff store and KS is the surface runoff recession constant of the time-step being used.

Input data

The model requires daily rainfall and potential evapotranspiration data (PET). As with other rainfall-runoff models in Source, the rainfall and PET data sets need to be continuous and overlapping.

Note: Initial tests have shown that AWBM can be used at sub-daily time-steps in Source.

 

Compared to rainfall, evapotranspiration has little influence on the water balance at a daily time scale and thus areal potential evapotranspiration is used (Boughton & Chiew 2003).

Daily rainfall data may be obtained from rain gauges as time series or from rainfall represented as a spatial layers, eg. rainfall grids per time step. Note that the time that rainfall data is collected may be important. Very often rainfall data is collected in the morning, the usual time is 9am, and may be more representative of the previous day’s rainfall.

Daily PET is an estimate of the spatially averaged areal potential evapotranspiration rate of the catchment being modelled. This estimate is subject to a number of climatic and land use/land cover variables. it may be estimated by applying a crop/land use factor to daily pan data or extracted directly from maps of calculated areal potential evapotranspiration data.

Climate grids can be imported into Source using the Climate Data Import Tool.

Selecting stream flow data to use in a river-basin-scale simulation study needs information about the reliability of the data. It is best to use data which are most representative of the stream flow from the catchment. Observed data would normally be selected, except where the data are of poor quality or of unknown reliability.

Parameters or settings

Table 1. Model parameters

Parameter

Description

Units

Default

Min

Max

A1

Partial area of surface store 1 (Proportion of the catchment)

 

0.134

0.000

1.000

A2

Partial area of surface store 2 (Proportion of the catchment)

 

0.433

0.000

1.000

C1

Capacity surface store 1

mm

7

0

50

C2

Capacity surface store 2

mm

70

0

200

C3

Capacity surface store 3

mm

150

0

500

BFI

Base flow index
(proportion of excess runoff going into the base flow store)

 

0.35

0.000

1.000

KBase

Base flow recession constant

(proportion of moisture depth remaining per time-step)

 

0.95

0.000

1.000

KSurf

Surface flow recession constant
(proportion of moisture depth remaining per time-step)

 

0.35

0.000

1.000

The relative sensitivity of parameters will vary between catchments but generally the model is most sensitive to the recession constants and base flow index.

Output data

The model outputs daily surface flow and base flow. This may be saved in ML/day, m3/s or mm/day.

The variables listed in Table 2 can also be recorded.

Table 2. Recorded variables

Variable

Parameter

Frequency

Baseflowrecharge

Baseflow recharge in each time step

time step

Baseflowstore

Baseflow store contents in each time step

time step

Effectiverainfall

Effective rainfall at each time step

time step

Routedsurfacerunoff

Routed surface runoff at each time step

time step

Surfacestore

Surface store contents in each time step

time step

Excess

Rainfall excess in each time step

time step

PartialExcess

Partial excess in each time step

time step

S1

Soil moisture contents in first surface store

time step

S2

Soil moisture contents in second surface store

time step

S3

Soil moisture contents in third surface store

time step

Surfacerunoff

Surface runoff in current time step – before routing

time step

Configuration

Daily observed flow data in ML/day, m3/s or mm/day is required to calibrate the model.

This model requires calibration and validation.

References

Boughton, W & Chiew, F 2003, Calibrations of the AWBM for use on ungauged catchments, Technical Report 03/15, Cooperative Research Centre for Catchment Hydrology, Canberra.

Boughton, W.J. (2004) The Australian water balance model, Environmental Modelling & Software, vol. 19, pp. 943-956.