Inputs Swatplus
Inputs Swatplus
CHAPTER FILE.CIO
File management is performed with the master watershed file (file.cio). The master watershed file
contains the file names for the simulation run.
The master watershed file is divided into several sections. A brief description of the variables in
the master watershed file follows. They are grouped by section and listed in the order they appear within
the file.
1
2 SWAT+ INPUT/OUTPUT FILE DOCUMENTATION, VERSION 2016
SWAT+ Model:
Over the past 20 years, the Soil and Water Assessment Tool (SWAT) has become widely
used across the globe. The large numbers of applications across the globe have also revealed
limitations and identified model development needs. Numerous additions and modifications of
the model and its individual components have made the code increasingly difficult to manage
and maintain. In order to face present and future challenges in water resources modeling
SWAT code has undergone major modifications over the past few years, resulting in SWAT+, a
completely revised version of the model. Even though the basic algorithms used to calculate
the processes in the model have not changed, the structure and organization of both the code
(object based) and the input files (relational based) have undergone considerable modification.
This is expected to facilitate model maintenance, future code modifications, and foster
collaboration with other researchers to integrate new science into SWAT modules. SWAT+
provides a more flexible spatial representation of interactions and processes within a watershed.
Descriptions of the SWAT+ input data files are listed and described in this document.
X.1 FILE.CIO
PRINT.PRT
The print file controls the occurrence of the output files and is space delimited. Below is a sample PRINT.PRT
file. Some pointers:
The user will input the actual start and stop julian day for daily printing.
NYSKIP will not print until NYSKIP is over.
When time crosses the end of the year, the print will continue to increment the print INTERVAL.
Daily printing of all files could cause very large output files (exceeding hard drive capabilities)
4 SWAT+ INPUT/OUTPUT FILE DOCUMENTATION, VERSION 2016
Examples: If NYSKIP =2, the model will skip printing the first
two years regardless of the starting year. In other words, if
YRC_START = 2000, we start printing in 2002. If YRC_START
= 2005, printing starts in 2007.
Notes: The daily print start and end time has nothing to do with
NYSKIP. If the daily print time is skipped, it simply won’t print
the daily output.
The start year of printing is max(YRC_START+NYSKIP).
HEADER Header
CSVOUT Code to print .csv files n=no print; y = print
DBOUT Code to print database (db) files n=no print; y = print (not
currently active)
CDFOUT Code to print netcdf (cdf) files n=no print; y = print (not
currently active)
HEADER Header
SNUTC Soil nutrients carbon output file (soil_nutcarb_out.txt); input should be
character - d(daily; m/(monthly); y(yearly); aa(ave annual);
MGTOUT Management output file (print codes apply) (mgt_out.txt)
HYDCON Hydrograph connect output file (hydcon.out)
FDCOUT Flow duration curve output file (flow_duration_curve.out)
n=no print; avann=print
HEADER Header.
All of the following codes are entered as : ‘y’ (yes) or ‘n’ (no)
to print on a daily, monthly, yearly or avann timestep.
BASIN_WB Water balance BASIN output variables
BASIN_NB Nutrient balance BASIN output variables
BASIN_LS Losses BASIN output variables
BASIN_PW Plant weather BASIN output variables
BASIN_AQU Aquifer BASIN output variables
BASIN_RES Reservoir BASIN output file variables
BASIN_CHA Channel BASIN output file variables
BASIN_SD_CHA CHANDEG BASIN output file variables
BASIN_PSC Point source BASIN output file variables
REGION_WB Water balance REGION output variables
REGION_NB Nutrient balance REGION output variables
REGION_LS Losses REGION output variables
REGION_PW Plant weather REGION output variables
REGION_AQU Aquifer REGION output variables
SWAT+ INPUTS 7
REGION_RES Reservoir REGION output variables
REGION_CHA Channel REGION output variables
REGION_SD_CHA SWATDEG Channel REGION output variables
REGION_PSC Point source REGION output variables
LSUNIT_WB Water balance ROUTING UNIT output variables
LSUNIT_NB Nutrient balance ROUTING UNIT output variables
LSUNIT_LS Losses ROUTING UNIT output variables
LSUNIT_PW Plant weather ROUTING UNIT output variables
HRU_WB Water balance HRU output variables
HRU_NB Nutrient balance HRU output variables
HRU_LS Losses HRU output variables
HRU_PW Plant weather HRU output variables
HRU_LTE_WB Water balance HRU-LTE output variables
HRU_LTE_NB Nutrient balance HRU-LTE output variables
HRU_LTE_LS Losses HRU-LTE output variables
HRU_LTE_PW Plant weather HRU-LTE output variables
CHANNEL Channel output variables
CHANNEL_SD SWAT DEG (lte) channel output variables
AQUIFER Aquifer output variables
RESERVOIR Reservoir output variables
RECALL Recall output variables
HYD Hydin output and hydout_output variables
RU Routing Unit output variables
OBJECT.PRT
The object print file allows the user to define output and is space delimited. Below is a sample OBJECT.PRT file:
object.prt:
NUMB OBTYP OBTYPNO HYDTYP FILENAME
1 sdc 1 tot two_stage.out
OBJECT.CNT
The object count file contains the total counts for the watershed simulation and is space delimited. Below is a
sample OBJECT.CNT file:
object.cnt:
NAME AREA_LS_HAREA_TOT_HA OBJ HRU LTE RU MODFLOW AQU CHA RES REC EXCO DR CANAL PUMP OUT CHANDEG 2DAQU
2_stage 30 33 3 0 0 0 0 0 0 0 1 1 1 0 0 0 0 0
constituents.cs
4 !pesticides
aatrex banvel prowl roundup
2 !pathogens
fecal_col_form e_coli
1 !metals
mercury
2 !salts
sodium magnesium
BASIN – General watershed attributes are defined in the basin input file. These attributes control a diversity
of physical processes at the watershed level. The interfaces will automatically set these parameters to the
“default” or recommended values listed in the variable documentation. Users can use the default values or
change them to better reflect what is happening in a given watershed. Variables governing bacteria or pesticide
transport need to be initialized only if these processes are being modeled in the watershed. Even if nutrients are
not being studied in a watershed, some attention must be paid to these variables because nutrient cycling
impacts plant growth which in turn affects the hydrologic cycle.
CODES.BSN
Below is a partial sample CODES.BSN FILE:
codes.bsn: Basin control -
PETFILE WWQFILE PET EVENT CRK SUBWQ SED_DET RTE DEG WQ RTPEST CN CFAC CSWAT BF_FLG UHYD SED_CH TDRN WTDN_P_MODEL ABSTR ATMO SMAX I_SUBHW
test.pet test.wwq 1 0 0 1 1 1 0 0 0 0 0 2 0 0 0 0 0 0 0 0 0 0
10 SWAT+ INPUT/OUTPUT FILE DOCUMENTATION, VERSION 2016
Variable name Definition
TITLE The first line is reserved for user comments. This line is not
processed by the model and may be left blank.
Optional.
HEADER Headers for the codes.bsn file.
PETFILE Potential ET filename
WWQFILE Watershed stream water quality filename
PET Potential evapotranspiration (PET) method.
There are four options for potential ET calculations:
0 Priestley-Taylor method
1 Penman/Monteith method
2 Hargreaves method
3 read in potential ET values
Numerous methods exist to calculate potential evapotranspiration.
Three of the most popular or widely-used are included in SWAT.
However, if a method other than Priestley-Taylor,
Penman/Monteith, or Hargreaves is recommended for the area in
which the watershed is located, the user can calculate daily PET
values with the recommended method and import them into SWAT.
A discussion of Priestley-Taylor, Penman-Monteith and Hargreaves
PET methods is found in Chapter 2:2 of the theoretical
documentation.
Required.
EVENT Rainfall/runoff/routing option:
0 daily rainfall/curve number runoff/daily routing
1 sub-daily rainfall/Green & Ampt infiltration/sub-daily routing
Option 0 is the default option.
Required.
CRK Crack flow code.
There are two options:
0 do not model crack flow in soil
1 model crack flow in soil
Crack, or bypass, flow is a newer feature in SWAT and has been
tested on a limited basis in simulations of some areas in Texas. This
type of flow should be modeled only on soils classified as Vertisols.
The default option is to model the watershed without crack flow.
Required.
SWAT+ INPUTS 11
SUBWQ Subbasin water quality code.
The algorithms used to calculate loadings of algae, organic
carbonaceous biological oxygen demand and dissolved oxygen to
the stream network (see Chapter 4:4 in Theoretical Documentation)
were derived from results of limited studies and are still in the
testing phase. ISUBWQ allows the user to choose to apply or not
apply the algorithms.
0 do not calculate algae/CBOD loadings and set dissolved
oxygen to saturated oxygen concentration
1 calculate algae/CBOD/dissolved oxygen loadings using
algorithms documented in Theoretical Documentation
The default option is ISUBWQ=0.
Required.
SED_DET Code governing calculation of daily maximum half-hour rainfall
value:
0 generate daily value using triangular distribution
1 use monthly maximum half-hour rainfall value for all days
in month
The user has the option of using the monthly maximum half-hour
rainfall for all days in the month. The randomness of the triangular
distribution used to generated daily values causes the maximum
half-hour rainfall value to jump around. For small plots or
microwatersheds in particular, the variability of the triangular
distribution is unrealistic.
Required.
RTE Channel water routing method:
0 variable storage method
1 Muskingum method
The user must be careful to define MSK_CO1, MSK_CO2 and
MSK_X when the Muskingum method is chosen.
The default option is IRTE=0.
Required.
DEG Channel degradation code.
There are two options:
0 channel dimensions are not updated as a result of degradation
(the dimensions remain constant for the entire simulation)
1 channel dimensions are updated as a result of degradation
Traditionally, channel dimensions remain fixed, or constant,
throughout the simulation. The change in channel dimensions with
time is a new feature in SWAT that is still in the testing phase. The
recommended option is to keep the channel dimensions constant.
Required.
12 SWAT+ INPUT/OUTPUT FILE DOCUMENTATION, VERSION 2016
WQ In-stream water quality code.
The variable identifies whether in-stream transformation of
nutrients using the QUAL2E algorithms and in-stream
transformation of pesticides is allowed to occur.
0 do not model in-stream nutrient and pesticide transformations
1 model in-stream nutrient and pesticide transformations
The default option is IWQ=0.
Required.
RTPEST Redefined to the sequence number -- changed to no nutrient stress
of pest in NPNO( : )to be routed through the watershed
CN Daily curve number calculation method:
0 calculate daily CN value as a function of soil moisture
1 calculate daily CN value as a function of plant
evapotranspiration
2 use traditional SWAT method which bases CN on soil
moisture but retention is adjusted for mildly-sloped tiled-
drained watersheds
Option 0 was the only method used to calculate the daily CN value
in versions of SWAT prior to SWAT2012. Calculation of the daily
CN value as a function of plant evapotranspiration was added
because the soil moisture method was predicting too much runoff
in shallow soils. By calculating daily CN as a function of plant
evapotranspiration, the value is less dependent on soil storage and
more dependent on antecedent climate.
Required.
CFAC = 0 for C-factor calculation using Cmin.
CFAC
= 1 for new C-factor calculation. (0-1)
Code for new carbon routines:
CSWAT
0 = original routines
1 = new carbon routines
Baseflow distribution factor during the day for subdaily runs.
BF_FLG
0 = baseflow evenly distributed to each time step during the day
0.5 = even weights between even distribution and rainfall
pattern
1= profile of baseflow in a day follows rainfall pattern
Unit hydrograph method:
UHYD
1 = triangular UH
2 = gamma function UH
Instream sediment model, 0=Bagnold model, 1=Brownlie model,
SED_CH
2=Yang model
SWAT+ INPUTS 13
Tile drainage equations flag/code
TDRN
Tile drainage routines flag/code: 1 = DRAINMOD tile equations
(Subroutine DRAINS)
1 simulate tile flow using subroutine drains(wt_shall)
0 simulate tile flow using subroutine origtile(wt_shall,d)
water table depth algorithms flag/code
WTDN
1 simulate wt_shall using subroutine new water table depth
routine
0 simulate wt_shall using subroutine original water table depth
routine
Soil phosphorus model
SOL_P_MODEL
0 = original soil phosphorus model
1 = new soil phosphorus model
ABSTR Initial abstraction on impervious cover (mm)
Atmospheric deposition interval (character)
ATMO
‘m’ = monthly
‘y’ = yearly
‘a’ = annual
Maximum depressional storage code; 1=dynamic stmaxd
SMAX
computed as a function of random roughness and rain intensity by
depstor.f; 0 = static stmaxd from .bsn for global value or .sdr for
specific HRU’s
I_SUBHW Code for routing headwaters
PARAMETERS.BSN
General watershed attributes are defined in the basin input file. These attributes control a diversity of
physical processes at the watershed level. The interfaces will automatically set these parameters to the “default”
or recommended values listed in the variable documentation. Users can use the default values or change them to
better reflect what is happening in a given watershed. Variables governing bacteria or pesticide transport need to
be initialized only if these processes are being modeled in the watershed. Even if nutrients are not being studied
in a watershed, some attention must be paid to these variables because nutrient cycling impacts plant growth
which in turn affects the hydrologic cycle.
EVLAI Leaf area index at which no evaporation occurs from water surface.
EVLAI is used in HRUs where a plant is growing in a ponded
environment (e.g. rice). Currently, this is simulated only in HRUs
defined as depressional areas/potholes.
Evaporation from the water surface is allowed until the leaf area of
the plant reaches the value specified for EVLAI. Chapter 8:1 in the
Theoretical Documentation provides more detail on the use of this
parameter.
EVLAI should be set between 0.0 and 10.0. If no value for EVLAI
is entered, the model will set EVLAI = 3.0.
Required if depressional areas/potholes are modeled in the
watershed.
FFCB Initial soil water storage expressed as a fraction of field capacity
water content.
All soils in the watershed will be initialized to the same fraction.
FFCB should be between 0.0 and 1.0. If FFCB is not set to a value,
the model will calculate it as a function of average annual
precipitation. The default method is to allow the model to calculate
FFCB (set FFCB = 0.0).
We recommend using a 1 year equilibration period for the model
where the watershed simulation is set to start 1 year prior to the
period of interest. This allows the model to get the water cycling
properly before any comparisons between measured and simulated
data are made. When an equilibration period is incorporated, the
value for FFCB is not going to impact model results.
Required.
SWAT+ INPUTS 15
SURLAG Surface runoff lag coefficient.
In large subbasins with a time of concentration greater than 1 day, only a portion
of the surface runoff will reach the main channel on the day it is generated.
SWAT incorporates a surface runoff storage feature to lag a portion of the
surface runoff release to the main channel.
SURLAG controls the fraction of the total available water that will be allowed to
enter the reach on any one day. Figure 4-7 plots the fraction of total available
water entering the reach at different values for surlag and tconc.
Note that for a given time of concentration, as surlag decreases in value more
water is held in storage. The delay in release of surface runoff will smooth the
streamflow hydrograph simulated in the reach.
If no value for SURLAG is entered, the model will set SURLAG =
4.0.
Required.
ADJ_PKR Peak rate adjustment factor for sediment routing in the subbasin
(tributary channels).
Sediment routing is a function of peak flow rate and mean daily
flow. Because SWAT originally could not directly calculate the sub-
daily hydrograph due to the use of precipitation summarized on a
daily basis, this variable was incorporated to allow adjustment for
the effect of the peak flow rate on sediment routing. This factor is
used in the MUSLE equation and impacts the amount of erosion
generated in the HRUs.
If no value for ADJ_PKR is entered, the model will set
ADJ_PKR=1.0.
Required.
16 SWAT+ INPUT/OUTPUT FILE DOCUMENTATION, VERSION 2016
PRF Peak rate adjustment factor for sediment routing in the main
channel.
Sediment routing is a function of peak flow rate and mean daily
flow. Because SWAT originally could not directly calculate the
sub-daily hydrograph, this variable was incorporated to allow
adjustment for the effect of the peak flow rate on sediment routing.
This variable impacts channel degradation.
If no value for PRF is entered, the model will set PRF = 1.0.
Required.
SPCON Linear parameter for calculating the maximum amount of sediment
that can be reentrained during channel sediment routing.
The maximum amount of sediment that can be transported from a
reach segment is calculated conc sed ,ch ,mx = c sp ⋅ v ch , pk
spexp
where
concsed,ch,mx is the maximum concentration of sediment that can
be transported by the water (ton/m3 or kg/L), csp is a coefficient
defined by the user, vch,pk is the peak channel velocity (m/s), and
spexp is an exponent defined by the user.
SPCON should be between 0.0001 and 0.01. If no value for
SPCON is entered, the model will set SPCON = 0.0001.
Required.
SPEXP Exponent parameter for calculating sediment reentrained in
channel sediment routing
The maximum amount of sediment that can be transported from a
reach segment is calculated conc sed ,ch ,mx = c sp ⋅ v ch , pk
spexp
where
concsed,ch,mx is the maximum concentration of sediment that can
be transported by the water (ton/m3 or kg/L), csp is a coefficient
defined by the user, vch,pk is the peak channel velocity (m/s), and
spexp is an exponent defined by the user.
The exponent, spexp, normally varies between 1.0 and 2.0 and was
set at 1.5 in the original Bagnold stream power equation (Arnold et
al., 1995). If no value for SPEXP is entered, the model will set
SPEXP = 1.0.
Required.
CMN Rate factor for humus mineralization of active organic nutrients (N
and P).
Chapters 3:1 and 3:2 of the Theoretical Documentation describe the
use of this parameter in the mineralization calculations.
If no value for CMN is specified, the model will set CMN = 0.0003.
Required.
SWAT+ INPUTS 17
N_UPDIS Nitrogen uptake distribution parameter.
Root density is greatest near the surface, and plant nitrogen uptake
in the upper portion of the soil will be greater than in the lower
portion. The depth distribution of nitrogen uptake is controlled by
βn, the nitrogen uptake distribution parameter.
The importance of the nitrogen uptake distribution parameter lies in
its control over the maximum amount of nitrate removed from the
upper layers. Because the top 10 mm of the soil profile interacts with
surface runoff, the nitrogen uptake distribution parameter will
influence the amount of nitrate available for transport in surface
runoff. The model allows lower layers in the root zone to fully
compensate for lack of nitrate in the upper layers, so there should
not be significant changes in nitrogen stress with variation in the
value used for βn.
If no value for N_UPDIS is entered, the model will set N_UPDIS =
20.0.
Figure 4-9 illustrates nitrogen uptake as a function of depth for four
different uptake distribution parameter values.
Required.
18 SWAT+ INPUT/OUTPUT FILE DOCUMENTATION, VERSION 2016
Phosphorus uptake distribution parameter.
P_UPDIS
This parameter controls plant uptake of phosphorus from the
different soil horizons in the same way that UBN controls nitrogen
uptake. The illustration of nitrogen uptake as a function of depth
for four different uptake distribution parameter values in Figure 4-
9 is valid for phosphorus uptake as well.
Phosphorus removed from the soil by plants is taken from the solution
phosphorus pool. The importance of the phosphorus uptake distribution
parameter lies in its control over the maximum amount of solution P removed
from the upper layers. Because the top 10 mm of the soil profile interacts with
surface runoff, the phosphorus uptake distribution parameter will influence the
amount of labile phosphorus available for transport in surface runoff. The model
allows lower layers in the root zone to fully compensate for lack of solution P in
the upper layers, so there should not be significant changes in phosphorus stress
with variation in the value used for βp.
If no value for P_UPDIS is entered, the model will set P_UPDIS =
20.0.
Required.
NPERCO Nitrate percolation coefficient.
NPERCO controls the amount of nitrate removed from the surface
layer in runoff relative to the amount removed via percolation.
The value of NPERCO can range from 0.01 to 1.0. As NPERCO →
0.0, the concentration of nitrate in the runoff approaches 0. As
NPERCO → 1.0, surface runoff has the same concentration of
nitrate as the percolate.
If no value for NPERCO is entered, the model will set NPERCO =
0.20.
Required.
PPERCO Phosphorus percolation coefficient (10 m3/Mg).
The phosphorus percolation coefficient is the ratio of the solution
phosphorus concentration in the surface 10 mm of soil to the
concentration of phosphorus in percolate.
The value of PPERCO can range from 10.0 to 17.5 If no value for
PPERCO is entered, the model will set PPERCO = 10.0.
Required.
SWAT+ INPUTS 19
PHOSKD Phosphorus soil partitioning coefficient (m3/Mg).
The phosphorus soil partitioning coefficient is the ratio of the
soluble phosphorus concentration in the surface 10 mm of soil to the
concentration of soluble phosphorus in surface runoff.
The primary mechanism of phosphorus movement in the soil is by
diffusion. Diffusion is the migration of ions over small distances (1-
2 mm) in the soil solution in response to a concentration gradient.
Due to the low mobility of solution phosphorus, surface runoff will
only partially interact with the solution P stored in the top 10 mm of
soil.
If no value for PHOSKD is entered, the model will set PHOSKD =
175.0.
Required.
20 SWAT+ INPUT/OUTPUT FILE DOCUMENTATION, VERSION 2016
PSP Phosphorus availability index.
Many studies have shown that after an application of soluble P
fertilizer, solution P concentration decreases rapidly with time due
to reaction with the soil. This initial “fast” reaction is followed by a
much slower decrease in solution P that may continue for several
years (Barrow and Shaw, 1975; Munns and Fox, 1976; Rajan and
Fox, 1972; Sharpley, 1982). In order to account for the initial rapid
decrease in solution P, SWAT assumes a rapid equilibrium exists
between solution P and an “active” mineral pool. The subsequent
slow reaction is simulated by the slow equilibrium assumed to exist
between the “active” and “stable” mineral pools. The algorithms
governing movement of inorganic phosphorus between these three
pools are taken from Jones et al. (1984).
Equilibration between the solution and active mineral pool is
governed by the phosphorus availability index. This index specifies
the fraction of fertilizer P which is in solution after an incubation
period, i.e. after the rapid reaction period.
A number of methods have been developed to measure the
phosphorus availability index. Jones et al. (1984) recommends a
method outlined by Sharpley et al. (1984) in which various amounts
of phosphorus are added in solution to the soil as K2HPO4. The soil
is wetted to field capacity and then dried slowly at 25°C. When dry,
the soil is rewetted with deionized water. The soil is exposed to
several wetting and drying cycles over a 6-month incubation period.
At the end of the incubation period, solution phosphorus is
determined by extraction with anion exchange resin.
The P availability index is then calculated:
Psolution , f − Psolution ,i
pai =
fert minP
where pai is the phosphorus availability index, Psolution,f is the
amount of phosphorus in solution after fertilization and incubation,
Psolution,I is the amount of phosphorus in solution before fertilization,
and fertminP is the amount of soluble P fertilizer added to the sample.
If no value for PSP is entered, the model will set PSP = 0.40.
Required.
RSDCO Residue decomposition coefficient.
The fraction of residue which will decompose in a day assuming
optimal moisture, temperature, C:N ratio and C:P ratio.
If no value for RSDCO is entered, the model will set RSDCO = 0.05.
Required.
SWAT+ INPUTS 21
PERCOP Pesticide percolation coefficient.
PERCOP controls the amount of pesticide removed from the surface
layer in runoff and lateral flow relative to the amount removed via
percolation. The value of PERCOP can range from 0.01 to 1.0. As
PERCOP → 0.0, the concentration of pesticide in the runoff and
lateral flow approaches 0. As PERCOP → 1.0, surface runoff and
lateral flow has the same concentration of pesticide as the percolate.
If no value for PERCOP is entered, the model will set PERCOP =
0.50.
Required if pesticide transport is of interest.
MSK_CO1 Calibration coefficient used to control impact of the storage time
constant (Km) for normal flow (where normal flow is when river is
at bankfull depth) upon the Km value calculated for the reach.
Required only if IRTE = 1.
MSK_CO2 Calibration coefficient used to control impact of the storage time
constant (Km) for low flow (where low flow is when river is at 0.1
bankfull depth) upon the Km value calculated for the reach.
Required only if IRTE = 1.
MSK_X MSK_X is a weighting factor that controls the relative importance
of inflow and outflow in determining the storage in a reach.
The weighting factor has a lower limit of 0.0 and an upper limit of
0.5. This factor is a function of the wedge storage. For reservoir-
type storage, there is no wedge and X = 0.0. For a full-wedge, X =
0.5. For rivers, X will fall between 0.0 and 0.3 with a mean value
near 0.2.
If no value for MSK_X is entered, the model will set MSK_X = 0.2.
Required only if IRTE = 1.
TRNSRCH Fraction of transmission losses from main channel that enter deep
aquifer. The remainder if the transmission losses enter bank storage.
In arid watersheds, transmission losses from the main channel
network may be permanently lost due to transmission to aquifers
that do not contribute flow back to the stream network. This variable
allows the user to specify the fraction of transmission losses from
the channel network that is permanently lost.
TRNSRCH varies between 0.00 and 1.00. The default value for
TRNSRCH is 0.00.
Required.
22 SWAT+ INPUT/OUTPUT FILE DOCUMENTATION, VERSION 2016
EVRCH Reach evaporation adjustment factor.
The evaporation coefficient is a calibration parameter for the user
and is allowed to vary between 0.0 and 1.0. This coefficient was
created to allow reach evaporation to be dampened in arid regions.
The original equation tends to overestimate evaporation in these
areas.
If no value for EVRCH is entered, the model will set EVRCH =
1.00.
Required.
CNCOEF Plant ET curve number coefficient.
ET weighting coefficient used to calculate the retention coefficient
for daily curve number calculations dependent on plant
evapotranspiration.
This value can vary between 0.5 and 2.0. If no value is entered for
CNCOEF, the model will set CNCOEF = 1.0.
Required if ICN = 1.
CDN Denitrification exponential rate coefficient.
This coefficient allows the user to control the rate of denitrification.
Acceptable values for CDN range from 0.0 to 3.0. If no value for
CDN is specified, the model will set CDN = 1.4.
Required.
SWAT+ INPUTS 23
SDNCO Denitrification threshold water content.
Fraction of field capacity water content above which denitrification
takes place.
Denitrification is the bacterial reduction of nitrate, NO -3 , to N2 or
N2O gases under anaerobic (reduced) conditions. Because SWAT
does not track the redox status of the soil layers, the presence of
anaerobic conditions in a soil layer is defined by this variable. If the
soil water content calculated as fraction of field capacity is ≥
SDNCO, then anaerobic conditions are assumed to be present and
denitrification is modeled. If the soil water content calculated as a
fraction of field capacity is < SDNCO, then aerobic conditions are
assumed to be present and denitrification is not modeled.
If no value for SDNCO is specified, the model will set SDNCO =
1.10.
Required.
BACT_SWF Fraction of manure applied to land areas that has active colony
forming units.
If no value for BACT_SWF is specified, the model will set
BACT_SWF = 0.15.
Required if bacteria processes are of interest.
TB_ADJ New variable in testing.
Adjustment factor for subdaily unit hydrograph basetime.
CN_FROZ Parameter for frozen soil adjustment on infiltration/runoff.
If no value for CNFROZ_BSN is entered, the model will set
CNFROZ_BSN = 0.000862.
Optional.
DORM_HR Time threshold used to define dormancy (hours). The maximum
day length minus DORM_HR is equal to when dormancy occurs.
Optional.
SMXCO Adjustment factor for maximum curve number S factor. Coefficient
curve number method that uses antecedent climate.
Optional.
FIXCO Nitrogen fixation coefficient. (0.0 – 1.0)
1.0 = fixes 100% of nitrogen demand. 0.0 = fixes none of nitrogen
demand.
NFIXMX Maximum daily-n fixation (kg/ha). (1.0 – 20.0)
DECR_MIN Minimum daily residue decay (fraction 0.0 – 0.05)
RSD_COVCO Residue cover factor for computing fraction of cover. (0.1 – 0.5)
24 SWAT+ INPUT/OUTPUT FILE DOCUMENTATION, VERSION 2016
VCRIT Critical velocity
RES_STR_CO Reservoir sediment settling coefficient (0.09 – 0.27)
UHALPHA Alpha coefficient for gamma function unit hydrograph. Required
if iuh = 2 is selected
EROS_SPL Splash erosion coefficient (0.9 – 3.1)
RILL_MULT Rill erosion coefficient – multiplier to USLE_K for soil susceptible
to rill erosion (0.5-2.0)
EROS_EXPO Exponential coefficient for overland flow – (1.5-3.0)
C_FACTOR Scaling parameter for cover and management factor for overland
flow erosion (0.03/0.001/0.45)
CH_D50 Median particle diameter of main channel (mm) (50/10/100)
SIG_G Geometric standard deviation of particle size (1.57/1.0/5.0)
R2ADJ Curve number retention parameter adjustment for low gradient,
non-draining soils (dimensionless) (0-3)
Random generator seed code.
A set of random numbers is needed by SWAT to generate weather
data. SWAT has a set of default random numbers embedded in the
code. To use the default random numbers, the user should set IGN
= 0. This is the default value for IGN.
In some situations, a user may wish to vary the weather sequence
between runs. One method to do this is to set IGN to a different
number every time the model is run. This code will activate a
random number generator, which will replace the default set of
random numbers with a new set. The value to which IGN is set
determines the number of times the random number generator is
cycled before the simulation begins. The seeds produced by the
random number generator are then utilized by the weather generator
instead of the default values.
Measured weather data read into the model is not affected by this
variable. However, if the measured data contains missing values, the
weather generator is activated to produce data to replace the missing
values. The data produced to replace missing values will be affected
by this variable.
Required.
Randon generator code 0 = use default number; 1 = generate new
IGEN
numbers in every simulation
SWAT+ INPUTS 25
CLIMATE – The CLIMATE section of file.cio contains filenames for the entire simulation
run. The list of the filenames are listed below with a brief description of the inputs within each
file.
WEATHER-STA.CLI
The weather station climate file contains the weather stations that will be included in the simulation and is space
delimited. Below is a sample WEATHER-STA.CLI file:
weather-sta.cli
NAME WGN PGAGE TGAGE SGAGE HGAGE WGAGE WNDIR ATMODEP
wea1 wgn001 mentone.pcp mentone.tmp sim sim sim null atmo_2
wea2 wgn001 warsaw.pcp warsaw.tmp sim sim sim null atmo_3
WEATHER-WGN.CLI
The weather generator climate file contains the weather generator stations that will be included in the simulation
and is space delimited. Below is a sample WEATHER-WGN.CLI file:
26 SWAT+ INPUT/OUTPUT FILE DOCUMENTATION, VERSION 2016
weather-wWeather
wgn001 43.07 -94.3 374.9 31
TMPMX TMPMN TMPSTDM TMPTDMNPCPMM PCPSTD PCPSKW PR_WD PR_WW PCPD RAINHMX SOLARAV DEWPT WINDAV
-3.9 -13.52 6.76 7.5 18.5 4.01 2.09 0.12 0.32 4.48 3.35 7.12 -11.06 5.61
-1.22 -10.79 7.04 7.72 18 4.6 2.72 0.12 0.25 3.83 4.43 10.81 -8.92 5.59
5.8 -4.3 7.36 6.22 43.4 8.24 1.81 0.15 0.33 5.6 6.5 15 -3.91 5.8
14.81 2.12 7.32 4.87 80.4 9.58 1.69 0.22 0.39 7.83 18.45 17.93 0.87 6.04
21.53 8.87 5.64 4.55 107.3 11.83 2.31 0.25 0.46 9.9 24.11 20.78 4.12 5.47
26.52 14.38 4.49 3.74 128.6 17.15 2.84 0.28 0.39 9.47 40.11 22.84 6.66 4.78
28.12 16.55 3.58 3.16 107.4 12.61 1.59 0.25 0.32 8.37 35.16 23.21 15.92 3.89
26.69 15.22 3.67 3.48 105.3 18 4.34 0.21 0.36 7.77 39.17 20.41 15.27 3.57
23.15 10.25 5.33 4.86 72.6 12.77 2.61 0.2 0.33 6.8 15.72 15.92 5.13 4.22
15.74 3.41 6.44 5.13 59.2 9.29 1.59 0.15 0.41 6.44 12.93 11.1 1.54 4.9
6.07 -3.99 7.17 5.86 39.8 8.97 2.6 0.13 0.36 5.17 5.93 7.16 -3.25 5.42
-2.17 -11.12 7.07 7.4 24.6 4.88 1.77 0.13 0.23 4.62 3.21 5.66 -8.88 5.48
∑T mx ,mon
µmx mon = d =1
N
where µmxmon is the mean daily maximum temperature for
the month (°C), Tmx,mon is the daily maximum temperature
on record d in month mon (°C), and N is the total number of
daily maximum temperature records for month mon.
Required.
28 SWAT+ INPUT/OUTPUT FILE DOCUMENTATION, VERSION 2016
TMPMN(MON) Average or mean daily minimum air temperature for month
(ºC).
This value is calculated by summing the minimum air
temperature for every day in the month for all years of record
and dividing by the number of days summed:
N
∑T mn ,mon
µmnmon = d =1
N
where µmnmon is the mean daily minimum temperature for the
month (°C), Tmn,mon is the daily minimum temperature on
record d in month mon (°C), and N is the total number of daily
minimum temperature records for month mon.
Required.
TMPSTDMX(MO Standard deviation for daily maximum air temperature in
N)
month (ºC).
This parameter quantifies the variability in maximum
temperature for each month. The standard deviation is
calculated:
N 2
∑ (Tmx ,mon − µmx mon )
σmx mon = d =1
N −1
where σmxmon is the standard deviation for daily maximum
temperature in month mon (ºC), Tmx,mon is the daily maximum
temperature on record d in month mon (°C), µmxmon is the
average daily maximum temperature for the month (°C), and N
is the total number of daily maximum temperature records for
month mon.
Required.
SWAT+ INPUTS 29
TMPSTDMN(MO Standard deviation for daily minimum air temperature in
N)
month (ºC).
This parameter quantifies the variability in minimum
temperature for each month. The standard deviation is
calculated:
N 2
∑ (Tmn ,mon − µmnmon )
σmnmon = d =1
N −1
where σmnmon is the standard deviation for daily minimum
temperature in month mon (ºC), Tmn,mon is the daily minimum
temperature on record d in month mon (°C), µmnmon is the
average daily minimum temperature for the month (°C), and N
is the total number of daily minimum temperature records for
month mon.
Required.
PCPMM(MON) Average or mean total monthly precipitation (mm H2O).
N
∑R day ,mon
Rmon = d =1
yrs
where Rmon is the mean monthly precipitation (mm H2O),
Rday,mon is the daily precipiation for record d in month mon (mm
H2O), N is the total number of records in month mon used to
calculate the average, and yrs is the number of years of daily
precipitation records used in calculation.
Required.
30 SWAT+ INPUT/OUTPUT FILE DOCUMENTATION, VERSION 2016
PCPSTD(MON) Standard deviation for daily precipitation in month (mm
H2O/day ).
This parameter quantifies the variability in precipitation for
each month. The standard deviation is calculated:
N 2
∑ (Rday ,mon − Rmon )
σ mon = d =1
N −1
where σmon is the standard deviation for daily precipitation in
month mon (mm H2O), Rday,mon is the amount of precipitation
for record d in month mon (mm H2O), Rmon is the average
precipitation for the month (mm H2O), and N is the total
number of daily precipitation records for month mon. (Note:
daily precipitation values of 0 mm are included in the standard
deviation calculation).
Required.
PCPSKW(MON) Skew coefficient for daily precipitation in month.
This parameter quantifies the symmetry of the precipitation
distribution about the monthly mean. The skew coefficient is
calculated:
g mon = d =1
(N − 1) ⋅ (N − 2) ⋅ (σ mon )3
where gmon is the skew coefficient for precipitation in the
month, N is the total number of daily precipitation records for
month mon, Rday,mon is the amount of precipitation for record d
in month mon (mm H2O), Rmon is the average precipitation for
the month (mm H2O), and σmon is the standard deviation for
daily precipitation in month mon (mm H2O). (Note: daily
precipitation values of 0 mm are included in the skew
coefficient calculation).
Required.
SWAT+ INPUTS 31
PR_WD(MON) Probability of a wet day following a dry day in the month.
This probability is calculated:
daysW
Pi (W D ) =
D ,i
days dry ,i
∑H day ,mon
µrad mon = d =1
N
where µradmon is the mean daily solar radiation for the month
(MJ/m2/day), Hday,mon is the total solar radiation reaching the
earth’s surface for day d in month mon (MJ/m2/day), and N is
the total number of daily solar radiation records for month mon.
Required.
DEWPT(MON) Average daily dew point temperature for each month (ºC) or
relative humidity (fraction) can be input.
If all twelve months are less than one, the model assumes
relative humidity is input. Relative humidity is defined in
equation 1:3.5.1 in the SWAT Theoretical documentation as
the amount of water vapor in the air as a fraction of saturation
humidity. If any month has a value greater than 1.0, the model
assumes dewpoint temperature is input.
Dew point temperature is the temperature at which the actual
vapor pressure present in the atmosphere is equal to the
saturation vapor pressure. This value is calculated by summing
the dew point temperature for every day in the month for all
years of record and dividing by the number of days summed:
N
∑T dew ,mon
µdewmon = d =1
N
where µdewmon is the mean daily dew point temperature for the
month (ºC), Tdew,mon is the dew point temperature for day d in
month mon (ºC), and N is the total number of daily dew point
records for month mon. Dew point is converted to relative
humidity using equations 1:3.5.1 and
1:3.5.2 in the Theoretical Documentation.
Required for Penman-Monteith potential evaporation equation.
SWAT+ INPUTS 33
WINDAV(MON) Average daily wind speed in month (m/s).
This value is calculated by summing the average or mean wind
speed values for every day in the month for all years of record
and dividing by the number of days summed:
N
∑µ wnd ,mon
µwnd mon = d =1
N
where µwndmon is the mean daily wind speed for the month
(m/s), µwnd,mon is the average wind speed for day d in month
mon (m/s), and N is the total number of daily wind speed
records for month mon.
Required.
WIND-DIR.CLI
This file contains the wind direction values that will be included in the simulation and is space delimited.
Below is a sample WIND-DIR.CLI file:
wind-dir.cl
2
AL_BAN
0 0
3.46 3.47 3.64 3.3 2.55 2.26 2.09 2.06 2.44 2.37 2.8 3.11
10 10 8 7 8 7 6 9 13 14 12 11
4 5 4 4 4 4 4 6 9 8 6 5
4 4 4 4 6 6 6 8 9 8 6 5
3 4 4 4 5 6 6 7 9 8 5 4
5 6 5 5 6 8 8 9 12 10 6 7
5 5 5 4 5 6 6 5 7 6 4 7
9 7 7 7 7 7 7 6 7 6 8 8
9 7 8 9 7 7 7 5 5 5 6 7
12 9 11 13 11 10 12 8 6 5 7 8
7 6 7 9 8 8 9 5 4 3 5 4
3 4 4 5 6 6 7 5 3 2 3 3
2 3 3 4 4 5 5 4 2 2 3 3
3 4 5 4 5 5 6 5 2 3 4 5
6 7 7 7 5 5 4 4 2 4 7 6
9 8 8 7 6 6 4 6 4 7 10 8
7 8 8 7 6 5 4 6 7 9 9 8
pcp.cli
FILENAME
mentone.pcp
warsaw.pcp
PCP_FILENAME
The pcp_filename is input in the pcp.cli file. The description of the ‘pcp_filename’ contains the daily
precipitation amounts for the simulation and is space delimited. A path has been added to file.cio to enable the
daily files to be present in another folder; if path is null daily is in same project folder as other data. Below is a
sample of the file (partial listing):
mentone.pcp
NBYR TSTEP LAT LONG ELEV
114 0 41.14 -85.98 268
1900 1 0.3
1900 2 0
1900 3 0
1900 4 0
1900 5 0
1900 6 0.6
1900 7 0.5
1900 8 0
1900 9 3.6
1900 10 3.5
1900 11 2.3
SWAT+ INPUTS 35
Variable name Definition
TITLE Description of the precipitation file (may be blank)
HEADER
NBYR The header information for the file
TSTEP Timestep of the simulation
LAT Latitude of the precipitation gage
LONG Longitude of the precipitation gage
ELEV Elevation of the precipitation gage
IYR The year of the precipitation amount
ISTEP The step (day, sub-daily) of the precipitation amount
PCP The amount of precipitation amount (mm) for istep (enter -99.0
for missing days)
TMP.CLI
This file contains information on the maximum and minimum temperatures included in the simulation and is
space delimited. A path has been added to file.cio to enable the daily files to be present in another folder; if
path is null daily is in same project folder as other data. Below is a sample TMP.CLI file:
tmp.cli
FILENAME
mentone.tmp
warsaw.tmp
TMP_FILENAME
The tmp_filename is input in the tmp.cli file. The description of the ‘tmp_filename’ contains the daily
maximum and minimum temperatures for the simulation and is space delimited. Below is a sample of the file:
36 SWAT+ INPUT/OUTPUT FILE DOCUMENTATION, VERSION 2016
mentone.tmp
NBYR LAT LONG ELEV
114 41.14 -85.98 268
1900 1 -99 -99
1900 2 -99 -11.5
1900 3 -99 -7.5
1900 4 3.1 -9.4
1900 5 5.7 -0.2
1900 6 6.8 -0.1
1900 7 11.2 2.6
1900 8 7.7 -99
1900 9 8 -3.4
1900 10 4.9 1.3
1900 11 -99 -1.2
SLR.CLI
This file contains the information on the solar radiation daily data included in the simulation and is space
delimited. A path has been added to file.cio to enable the daily files to be present in another folder; if path is
null daily is in same project folder as other data. Below is a sample SLR.CLI file:
slr.cli
NUMB FILENAME
1 gage1.slr
SWAT+ INPUTS 37
Variable name Definition
TITLE Description of the solar radiation file (may be blank)
HEADER The header information for the slr.cli file
SLR_FILENAME The name of the solar radiation file containing values of solar
radiation
SLR_FILENAME
The slr_filename is input in the slr.cli file. The description of the ‘slr_filename’ contains the daily solar
radiation values for the simulation and is space delimited. Below is a sample of the file (partial listing):
gage1.slr
NBYR LAT LONG ELEV
25 0.0 0.0 0.0
1988 1 12.9
1988 2 27.4
1988 3 22.7
1988 4 0
1988 5 9.7
HMD.CLI
This file contains the information on the relative humidity stations included in the simulation and is space
delimited. A path has been added to file.cio to enable the daily files to be present in another folder; if path is
null daily is in same project folder as other data. Below is a sample HMD.CLI file:
HMD.CLI
NUMB FILENAME
1 gage1.hmd
38 SWAT+ INPUT/OUTPUT FILE DOCUMENTATION, VERSION 2016
HMD_FILENAME
The hmd_filename is input in the hmd.cli file. The description of the ‘hmd_filename’ contains the daily relative
humidity values for the simulation and is space delimited. Below is a sample of the file (partial listing):
gage1.HMD
NBYR LAT LONG ELEV
25 0.0 0.0 0.0
1988 1 1
1988 2 0.8
1988 3 0.7
1988 4 1
1988 5 0.5
WND.CLI
NUMB FILENAME
1 gage1.wnd
SWAT+ INPUTS 39
Variable name Definition
TITLE Description of the wnd.cli file (may be blank)
HEADER The header information for the wnd.cli file
WND_FILENAME The name of the precipitation file containing daily windspeed
input data
WND_FILENAME
The wnd_filename is input in the wnd.cli file. The description of the ‘wnd_filename’ contains the daily wind
values for the simulation and is space delimited. Below is a sample of the file (partial listing):
gage1.WND
NBYR LAT LONG ELEV
25 0.0 0.0 0.0
1988 1 3.8
1988 2 4.4
1988 3 2.8
1988 4 2
1988 5 3.1
ATMO.CLI
The ATMO.CLI file contains the input variables for atmospheric deposition. The atmospheric deposition input file
contains annual average atmospheric nitrogen deposition values including ammonium, nitrate, dry ammonium
and dry nitrate and can be read in as average annual, yearly or monthly. This file is optional. An example annual
file is listed below:
40 SWAT+ INPUT/OUTPUT FILE DOCUMENTATION, VERSION 2016
atmo_annual.dat
NUM_STA TIMESTEP MO_INIT YR_INIT NUM_AA
3 aa 0 0 0
atmo_1 desc_not read
0.35 (NH4_RF)
3.24 (NO3_RF)
0.13 (NH4_DRY)
0.12 (NO3_DRY)
atmo_2
0.35 (NH4_RF)
3.24 (NO3_RF)
0.13 (NH4_DRY)
0.12 (NO3_DRY)
atmo_3
0.35 (NH4_RF)
3.24 (NO3_RF)
0.13 (NH4_DRY)
0.12 (NO3_DRY)
HEADER The second line is the header for the inputs. This line is not
processed by the model.
TIMESTEP There are three different timesteps for the file to be read and
should be character.
‘aa’ = annual average (constant)
‘mo’ = monthly
‘yr’ = yearly
MO_INIT Initial month of the input data (applies to month option only)
input 0 for other options;
YR_INIT Initial year of the input data (applies to year and monthly
option only) input 0 for annual;
NAME Initial month of the input data (applies to month option only)
input 0 for other options;
SWAT+ INPUTS 41
Ammonia in rainfll (mg/l)
NH4_RF
Nitrate in rainfall (mg/l)
NO3_RF
Ammonia deposition (kg/ha/yr)
NH4_DRY
Nitrate dry deposition (kg/ha/yr)
NO3_DRY
CONNECT – The CONNECT section of file.cio contains the filenames for the object
connectivity for the simulation run. All connect (.con) files read in the same input variables,
only differing in the connect units (HRU, HRU-LTE, ROUT_UNIT, modflow, aquifer,
aquifer2d, channel, reservoir, recall, exco, delivery ratio, outlet and chandeg).
42 SWAT+ INPUT/OUTPUT FILE DOCUMENTATION, VERSION 2016
EXPLANATION OF SPATIAL OBJECTS
SUBBASIN
The subbasin is defined by the DEM in the GIS interface as it always has been. All flow within the subbasin drains to the
subbasin outlet.
LANDSCAPE UNIT
A landscape unit is defined as a collection of HRU’s and can be defined as a subbasin, or it could be a flood plain or
upland unit, or it could be a grid cell with multiple HRU’s. The landscape unit is not routed, it only used for output. The
landscape unit output files (waterbal, nutbal, losses, and plant weather) are output for HRU’s, landscape units, and for
the basin. Two input files are required: 1) landscape elements and, 2) landscape define. The elements file includes
HRU’s and their corresponding LSU fraction and basin fractions. The define file specifies which HRU’s are contained in
each LSU.
ROUTING UNIT
A routing unit is a collection of hydrographs that can be routed to any spatial object. The routing unit can be configured
as a subbasin, then total flow (surface, lateral and tile flow) from the routing unit can be sent to a channel and all
recharge from the routing unit sent to an aquifer. This is analogous to the current approach in SWAT. However, SWAT+
gives us much more flexibility in configuring a routing unit. For example, in CEAP, we are routing each HRU (field)
through a small channel (gully or grass waterway) before it reaches the main channel. In this case, the routing unit is a
collection of flow from the small channels. We also envision simulating multiple representative hillslopes to define a
routing unit. Also, we are setting up scenarios that define a routing unit using tile flow from multiple fields and sending
that flow to a wetland.
The routing unit is the spatial unit SWAT+ that allows us to lump outputs and route the outputs to any other spatial
object. It gives us considerably more flexibility than the old subbasin lumping approach in SWAT, and will continue to be
a convenient way of spatial lumping until we can simulate individual fields or cells in each basin.
SWAT+ INPUTS 43
HRU.CON
The HRU.CON file contains the connectivity for the HRU spatial objects within the watershed that will be
included in the simulation and is space delimited. Below is a sample HRU.CON file:
hru.con
NUMB NAME GIS_ID AREA LAT LONG ELEV HRU WST CONST_TYPE OVERFLOW RULESET OUT_TOT
1 bench 1 0.48 0 0 0 1 wea1 0 0 0 0
2 field 2 495.27 0 0 0 2 wea2 0 0 0 0
SPATIAL OBJECTS
HRU HYDROLOGIC RESPONSE UNIT
HLT HRU LITE
RU ROUTING UNIT
MFL MODFLOW
AQU AQUIFER
44 SWAT+ INPUT/OUTPUT FILE DOCUMENTATION, VERSION 2016
CHA CHANNEL
RES RESERVOIR
REC RECALL
EXC EXPORT COEFFICIENTS
DR DELIVERY RATIO
CAN CANAL
PUM PUMP
OUT OUTLET
SDC SWAT DEG CHANNEL
OBTYPNO_OUT Outflow object type name
HTYP_OUT Outflow hydrograph (1=’tot’;
2=’rhg’;3=’sur’;4=’lat’;5=’til’;
(default = ‘null’)
OUTFLOW HYDROGRAPHS
TOT TOTAL
RHG RECHARGE
SUR SURFACE
LAT LATERAL
TIL TILLAGE
FRAC_OUT Fraction of hydrograph
SWAT+ INPUTS 45
CHANNEL – The CHANNEL section of file.cio contains the filenames for simulation of a
channel in the model. In order to simulate the physical processes affecting the flow of water and transport of
sediment in the channel network of the watershed, SWAT requires information on the physical characteristics of
the main channel within each subbasin. The channel input files summarizes the physical characteristics of the
channel which affect water flow and transport of sediment, nutrients and pesticides.
INITIAL.CHA
The INITIAL.CHA file contains the input variables for the initialization of a channel. Below is a partial sample
INITIAL.CHA file:
HYDROLOGY.CHA
The HYDROLOGY.CHA file contains the input variables for the hydrology inputs of a channel. Below is a sample
HYDROLOGY.CHA file:
SWAT+ INPUTS 47
hydrology.cha
CHA_HYD_NAME CHA_WD CHA_DP CHA_SLP CHA_LEN CHA_MANN CHA_K CHA_WDR ALPHA_BNK SIDE_SLP
cha1 3.29 0.338 0.002 0.794 0.075 0 9.73 0 0
cha2 2.719 0.301 0.008 0.474 0.075 0 9.026 0 0
cha3 4.286 0.397 0.004 3.042 0.075 0 10.802 0 0
cha4 2.566 0.291 0.004 0.48 0.075 0 8.82 0 0
cha5 3.254 0.336 0.006 1.474 0.075 0 9.688 0 0
cha6 2.729 0.302 0.005 0.674 0.075 0 9.038 0 0
cha7 2.881 0.312 0.005 0.764 0.075 0 9.234 0 0
cha8 3.038 0.322 0.006 1.444 0.075 0 9.429 0 0
cha9 4.254 0.395 0.004 2.63 0.075 0 10.77 0 0
cha10 2.536 0.289 0.005 0.517 0.075 0 8.78 0 0
cha11 3.288 0.338 0.003 1.693 0.075 0 9.728 0 0
SEDIMENT.CHA
The SEDIMENT.CHA file contains the input variables for the sediment inputs of a channel. Below is a sample
SEDIMENT.CHA file:
sediment.cha:
CHA_SED_NAMSED_EQN ER_FACT COV_FACT BNK_BD BED_BD BNK_KD BED_KD BNK_D50 BED_D50 BNK_CSS BED_CSS EROD1 EROD2
null 0 0 0 1.5 1.5 0.5 0.5 1.5 1.5 0.05 0.05 0 0
48 SWAT+ INPUT/OUTPUT FILE DOCUMENTATION, VERSION 2016
Variable name Definition
TITLE Description of the sediment channel file
HEADER The header information for the sediment channel file
NAME Name of the sediment channel
EQN Sediment routine methods:
0 = original SWAT method;
1 Bagnold’s
2 Kodatie
3 Molinas WU
4 Yang
COV1 Channel erodibility factor (0.0-1.0)
COV2 Channel cover factor (0.0-1.0)
BNK_BD Bulk density of channel bank sediment (g/cc)
BED_BD Bulk density of channel bed sediment (g/cc)
BNK_KD Erodibility of channel bank sediment by jet test
BED_KD Erodibility of channel bed by jet test
BNK_D50 D50 (median) particle size diameter of channel bank
BED_D50 D50 (median) particle size diameter of channel bed
TC_BNK Critical shear stress of channel bank (N/m^2)
TC_BED Critical shear stress of channel bed (N/m^2)
EROD1-12 Value of 0.0 indicates a non-erosive channel while a value of
1.0 indicates no resistance to erosion
SWAT+ INPUTS 49
NUTRIENTS.CHA
The NUTRIENTS.CHA file contains the input variables for the nutrients of a channel. Below is a sample partial
NUTRIENTS.CHA file:
nutrients.cha:
NAME ONCO OPCO RS1 RS2 RS3 RS4 RS5 RS6 RS7 RK1 RK2 RK3 RK4 RK5 RK6 BC1 BC2 BC3 BC4 LAO IGROPT AI0 AI2 AI3 AI4 AI5 AI6 MUMAX RHOQ TFACT K_l K_N K_P LAMBDA0 LAMBDA1 LAMDA2 P_N
nut_cha1 0 0 1 0.05 0.5 0.05 0.05 2.5 2.5 1.71 1 2 0 1.71 1.71 0.55 1.1 0.21 0.35 2 2 AI1 0.08 0.01 1.6 2 3.5 1.07 2 2.5 0.4 0.75 0.02 0.025 1 0.03 0.054
κ 2, 20 = 294 ⋅
(Dm ⋅ vc )0.5
depth1.5
where κ2,20 is the reaeration rate at 20°C (day-1), Dm is the
molecular diffusion coefficient (m2/day), vc is the average
stream velocity (m/s), and depth is the average stream
depth (m). For streams with high velocities and
nonisotropic conditions,
D ⋅ slp 0.25
0.5
κ 2, 20 = 2703 ⋅ m
depth1.25
where κ2,20 is the reaeration rate at 20°C (day-1), Dm is the
molecular diffusion coefficient (m2/day), slp is the slope of
the streambed (m/m), and depth is the average stream depth
(m). The molecular diffusion coefficient is calculated
PESTICIDE.CHA
The PESTICIDE.CHA file contains the input variables for the nutrients of a channel. Below is a sample partial
PESTICIDE.CHA file:
pesticide.cha
CHA_PST_NAME PST_REAC PST_VOLAT PST_KOC PST_MIX PST_RSP PST_STL SEDPST_ACT SEDPST_BUR SEDPST_CONC SEDPST_REAC
cha_pst1 0.007 0.01 0 0.001 0 1 0.03 0.002 0 0.05
SWAT+ INPUTS 59
Variable name Definition
TITLE This line is reserved for the pesticide section title. This line
is not processed by the model and may be left blank.
HEADER Headings
NAME Name of the pesticide channel
PST_REA Pesticide reaction coefficient in reach (day-1).
The rate constant is related to the aqueous half-life:
0.693
k p ,aq =
t1 / 2,aq
where kp,aq is the rate constant for degradation or removal
of pesticide in the water (1/day), and t1/2,aq is the aqueous
half-life for the pesticide (days).
If no value for CHPST_REA is entered, the model will set
CHPST_REA = 0.007 day-1.
Required if in-stream pesticide cycling is being modeled.
PST_VOL Pesticide volatilization coefficient in reach (m/day).
The volatilization mass-transfer coefficient can be
calculated based on Whitman’s two-film or two-resistance
theory (Whitman, 1923; Lewis and Whitman, 1924 as
described in Chapra, 1997). While the main body of the gas
and liquid phases are assumed to be well-mixed and
homogenous, the two-film theory assumes that a substance
moving between the two phases encounters maximum
resistance in two laminar boundary layers where transfer is
a function of molecular diffusion. In this type of system the
transfer coefficient or velocity is:
He
vv = K l ⋅
H e + R ⋅ TK ⋅ (K l K g )
where vv is the volatilization mass-transfer coefficient
(m/day), Kl is the mass-transfer velocity in the liquid
laminar layer (m/day), Kg is the mass-transfer velocity in
the gaseous laminar layer (m/day), He is Henry’s constant
(atm m3 mole-1), R is the universal gas constant (8.206 ×
10-5 atm m3 (K mole)-1), and TK is the temperature (K).
For rivers where liquid flow is turbulent, the transfer
coefficients are estimated using the surface renewal theory
(Higbie, 1935; Danckwerts, 1951; as described by Chapra,
1997). The surface renewal model visualizes the system as
60 SWAT+ INPUT/OUTPUT FILE DOCUMENTATION, VERSION 2016
Variable name Definition
PST_VOL, cont. consisting of parcels of water that are brought to the surface
for a period of time. The fluid elements are assumed to
reach and leave the air/water interface randomly, i.e. the
exposure of the fluid elements to air is described by a
statistical distribution. The transfer velocities for the liquid
and gaseous phases are calculated:
K l = rl ⋅ Dl K g = rg ⋅ Dg
where Kl is the mass-transfer velocity in the liquid laminar
layer (m/day), Kg is the mass-transfer velocity in the
gaseous laminar layer (m/day), Dl is the liquid molecular
diffusion coefficient (m2/day), Dg is the gas molecular
diffusion coefficient (m2/day), rl is the liquid surface
renewal rate (1/day), and rg is the gaseous surface renewal
rate (1/day).
O’Connor and Dobbins (1956) defined the surface renewal
rate as the ratio of the average stream velocity to depth.
86400 ⋅ vc
rl =
depth
where rl is the liquid surface renewal rate (1/day), vc is the
average stream velocity (m/s) and depth is the depth of flow
(m).
If no value for CHPST_VOL is entered, the model will set
CHPST_VOL = 0.01.
Required if in-stream pesticide cycling is being modeled.
PST_KOC Pesticide partition coefficient between water and sediment
in reach (m3/g).
The pesticide partition coefficient can be estimated from
the octanol-water partition coefficient (Chapra, 1997):
K d = 3.085 × 10 −8 ⋅ K ow
METALS.CHA(NEEDS ADDRESSING)
The METALS.CHA file contains the input variables for the nutrients of a channel. Below is a sample partial
METALS.CHA file:
CHANNEL-LTE.CHA
The CHANNEL-LTE.CHA file contains the input variables for the nutrients of a channel. Below is a sample
CHANNEL-LTE.CHA file:
channel-lte.cha
NAME ORDER RTE_DB CHW CHD CHS CHL CHN CHK CHEROD CHCOV HC_COV CHSEQ D50 CLAY BD CHSS BEDLD TCHEAR_BNK HC_KH HC_HGT HC_INI
BcGully_MainTrib null null 8.373 3.8 0.0231 0.229 0.05 1 0.2 0.05 0.95 0.0115 0.005 46 1.87 0.53 0.2 39 0.75 0.188 1 0
64 SWAT+ INPUT/OUTPUT FILE DOCUMENTATION, VERSION 2016
Figure 25-1: Stream-groundwater relationships: a) gaining stream receiving water from groundwater
flow; b) losing stream connected to groundwater system; c) losing stream perched above
groundwater system; and d) flow-through stream (After Dingman, 1994).
Typical values for Kch for various alluvium materials are given in Table 25-2. For
perennial streams with continuous groundwater contribution, the effective
conductivity will be zero.
SWAT+ INPUTS 67
Variable name Definition
CHK cont.
Table 25-2: Example hydraulic conductivity values for various bed materials (from Lane, 1983).
Bed material group Bed material Hydraulic
characteristics conductivity
1 Very clean gravel and large
Very high loss rate sand > 127 mm/hr
2 Clean sand and gravel, field
High loss rate conditions 51-127 mm/hr
3 Sand and gravel mixture
Moderately high loss with low silt-clay content 25-76 mm/hr
rate
4 Sand and gravel mixture
Moderate loss rate with high silt-clay content 6-25 mm/hr
5 Consolidated bed material;
Insignificant to low loss high silt-clay content 0.025-2.5 mm/hr
rate
If CH_EQN ≠ 0:
Channel bank vegetation coefficient for critical shear stress
(Julian and Torres, 2006)
Bank Vegetation CH_COV1
None 1.00
Grassy 1.97
Sparse trees 5.40
Dense trees 19.20
Required.
68 SWAT+ INPUT/OUTPUT FILE DOCUMENTATION, VERSION 2016
Variable name Definition
HC_COV Head cut cover factor
CHSEQ Equilibrium channel slope (m/m)
D50 Channel median sediment size (%)
CLAY Clay percent of bank and bed (%)
BD Dry bulk density (t/m3)
CHSS Channel side slope
BEDLDCOEF Percent of sediment entering the channel that is bed
material
TC Time of concentration
SHEAR_BNK Bank shear coefficient – fraction of bottom shear
HC_KH Headcut erodibility
HC_HGT Headcut height (m)
HC_INI Initial channel length for gullies (km)
RESERVOIR – The RESERVOIR section of file.cio contains the filenames for simulation of a
reservoirs in the model. Reservoirs are impoundments located on the main channel network of
the watershed. Reservoirs receive loadings from all upstream subbasins. The reservoir input file
(.res) contains input data to simulate water and sediment processes.
INITIAL.RES
The INITIAL.RES file contains the input variables for the initialization of a channel. Below is a sample partial
INITIAL.RES file:
initial.res:
NAME VOL SED ORGN NO3 NO2 NH3 ORGP SOLP SECI SAN SIL CLA SAG LAG GRA CHLA PST_MASSSPST_MASS BACTLP BACTP
res_init1 0.9 200 10 2 0.2 0.1 1 0.1 1 0 1 9 0 0 0 0.1 0.01 0 0 0
SWAT+ INPUTS 69
RESERVOIR.RES
The reservoir input file (.res) contains input data to simulate water and sediment processes while the lake water
quality file (.lwq) contains input data to simulate nutrient and pesticide cycling in the water body.
Below is a sample RESERVOIR.RES file:
reservoir.res
RES_NUMB RES_NAME RES_INI RES_HYD RELEASE RES_SED RES_NUT RES_PST
1 pnd1 res001 pnd1 lrew_sm_res res001 res001 res001
2 pnd2 res001 pnd2 lrew_sm_res res001 res001 res001
3 pnd3 res001 pnd3 lrew_sm_res res001 res001 res001
4 pnd4 res001 pnd4 lrew_sm_res res001 res001 res001
5 pnd5 res001 pnd5 lrew_sm_res res001 res001 res001
HYDROLOGY.RES
Reservoirs are impoundments located on the main channel network of the watershed. Reservoirs receive loadings
from all upstream subbasins. The reservoir input file (.res) contains input data to simulate water and sediment
processes while the lake water quality file (.lwq) contains input data to simulate nutrient and pesticide cycling in
the water body.
Below is a sample HYDROLOGY.RES file:
hydrology.res
RES_HYD_NAME YR_OP MON_OP AREA_PS VOL_PS AREA_ES VOL_ES RES_K EVAP_CO SHP_CO_1 SHP_CO_2
pnd1 0 0 4.95 12.375 5.445 13.613 0 1 0 0
pnd2 0 0 4.41 11.025 4.851 12.128 0 1 0 0
pnd3 0 0 3.06 7.65 3.366 8.415 0 1 0 0
pnd4 0 0 8.55 21.375 9.405 23.513 0 1 0 0
pnd5 0 0 2.16 5.4 2.376 5.94 0 1 0 0
pnd6 0 0 2.52 6.3 2.772 6.93 0 1 0 0
72 SWAT+ INPUT/OUTPUT FILE DOCUMENTATION, VERSION 2016
Definition
Variable name
TITLE The first line is reserved for user comments. This line is not
processed by the model and may be left blank.
Optional.
HEADER Headers for the hydrology.res file.
The name of the reservoir
NAME
Year the reservoir became operational (eg 1980).
IYRES
NUTRIENTS.RES
While water quality is a broad subject, the primary areas of concern are nutrients, organic chemicals—both
agricultural (pesticide) and industrial, heavy metals, bacteria and sediment levels in streams and large water
bodies. SWAT is able to model processes affecting nutrient, pesticide and sediment levels in the main channels
and reservoirs.
Below is a sample partial NUTRIENTS.RES file:
nutrients.res:
RES_NUT_NAME MID_BEG MID_END MID_N_STL N_STL MID_P_STL P_STL CHLA_CO SECCI_CO THETA_N THETA_P CONC_NMIN CONC_PMIN
res001 4 10 0.5 2 1 0.5 1 1 1 1 0.1 0.01
PESTICIDE.RES
SWAT+ INPUTS 77
Reservoirs are impoundments located on the main channel network of the watershed. Reservoirs receive
loadings from all upstream subbasins. The reservoir input file (.res) contains input data to simulate water and
sediment processes while the lake water quality file (.lwq) contains input data to simulate nutrient and pesticide
cycling in the water body.
Below is a sample partial PESTICIDE.RES file:
pesticide.res:
RES_PST_NAME PST_CON PST_KOC PST_MIX PST_REA PST_RSP PST_STL PST_VOL SEDPST_ACT SEDPST_BRYEDPST_CONC SEDPST_REA
res001 0 0.5 0.01 0.02 0.01 0.2 0.01 0.2 0.05 0.01 1
SEDIMENT.RES
Reservoirs are impoundments located on the main channel network of the watershed. Reservoirs receive loadings
from all upstream subbasins. The reservoir input file (.res) contains input data to simulate water and sediment
processes while the lake water quality file (.lwq) contains input data to simulate nutrient and pesticide cycling in
the water body. Below is a sample SEDIMENT.RES file:
sediment.res:
RES_SED_NAME SED_AMT RES_D50 SED_STL STL_VEL
res001 100 20 10 2
m m m
d 50 = exp 0.41 ⋅ c + 2.71 ⋅ silt + 5.7 ⋅ s
100 100 100
where d50 is the median particle size of the sediment (µm), mc is percent
clay in the surface soil layer, msilt is the percent silt in the surface soil
layer, ms is the percent sand in the surface soil layer.
Because reservoirs are located on the main channel network and receive
sediment from the entire area upstream, defaulting the sand, silt, and
clay fractions to those of a single subbasin or HRU in the upstream area
is not appropriate. Instead the user is allowed to set the median particle
size diameter to a representative value.
If no value is defined for the median particle diameter, the model will
set RES_D50 = 10 µm.
Required.
WEIR.RES
Below is a sample WEIR.RES file:
weir.res:
WEIR_NAME NUM_STEPS C K W BCOEF CCOEF
shape001 24 1 15000 2 1.75 1
SWAT+ INPUTS 85
Variable name Definition
TITLE The first line is reserved for user comments. This
line is not processed by the model and may be left
blank.
Optional.
HEADER Headers for the weir.res file.
NAME The name of the reservoir
NUM_STEPS The number of time steps in day for weir routing
C Weir discharge coefficient
K Energy coefficient (broad_crested-147,000’
sharp crested=153,000)
W The width of the weir (m)
BCOEF Velocity exponent coefficient for bedding
material
CCOEF Depth exponent coefficient for bedding material
WETLAND.WET
Below is a sample WETLAND.WET file:
wetland.wet
NUMB NAME INIT HYD RELEASE SED NUT PST
1 wetland1 wetland001 pnd1 null res001 res001 res001
2 wetland2 wetland001 pnd1 null res001 res001 res001
3 wetland3 wetland001 pnd1 null res001 res001 res001
4 wetland4 wetland001 pnd1 null res001 res001 res001
5 wetland5 wetland001 pnd1 null res001 res001 res001
6 wetland6 wetland001 pnd1 null res001 res001 res001
HYDROLOGY.WET
Below is a sample HYDROLOGY.WET file:
hydrology.wet
NAME PSA PVOL ESA EVOL K EVRSV ACOEF BCOEF CCOEF FRAC
pnd1 0.5 12.25125 0.9 14.82401 0.02 0.6 0 0 1 0.5
ROUTING UNIT
The subbasin general input file contains information related to a diversity of features within the subbasin. Data
contained in the subbasin input file can be grouped into the following categories: subbasin size and location,
specification of climatic data used within the subbasin, the amount of topographic relief within the subbasin and
its impact on the climate, properties of tributary channels within the subbasin, variables related to climate change,
the number of HRUs in the subbasin and the names of HRU input files.
ROUT_UNIT.DEF
SWAT+ INPUTS 87
The rout_unit.def file contains data that defines HRU’s in the subbasin.
Below is a sample rout_unit.def file:
rout_unit.def
RTU_NUMB TU_NAMEELEM_TOT ELEM1 ELEM2
1 sub1 2 1 -21
2 sub2 2 22 -28
3 sub3 2 29 -39
4 sub4 2 40 -42
5 sub5 2 43 -62
6 sub6 2 63 -67
7 sub7 2 68 -87
8 sub8 2 88 -92
ROUT_UNIT.ELE
Below is a sample ROUT_UNIT.ELE file:
Rout_unit.ele
NUMB NAME OBTYP OBTYPNO HTYP FRAC IDR
1 hru1 hru 1 tot 0.082 0
2 hru2 hru 2 tot 0.005 0
3 hru3 hru 3 tot 0.478 0
4 hru4 hru 4 tot 0.003 0
5 hru5 hru 5 tot 0.016 0
6 hru6 hru 6 tot 0.011 0
ROUT_UNIT.RTU
Below is a sample ROUT_UNIT.RTU file:
rout_unit.rtu
NUMB NAME ELEM_DEF ELEM_DR TOPOSUB_DB FIELD_DB
1 sub1 sub1 null top1 fld1
2 sub2 sub2 null top2 fld2
3 sub3 sub3 null top3 fld3
4 sub4 sub4 null top4 fld4
5 sub5 sub5 null top5 fld5
6 sub6 sub6 null top6 fld6
Variable name Definition
TITLE The title of the rout_unit.rtu file
HEADER Headers for the rout_unit.rtu file.
NUMB Number of the subbasin
NAME The name of the parm unit
ELEM_DEF Points to define.sub
ELEM_DR Delivery ratio definition
TOPOSUB_DB Topography link
FIELD_DB Field database definition (points to field.fld)
ROUT_UNIT.DR
HRU – HRU’s are now defined by weather, topography, soil, landuse, operational management, potholes,
subsurface drainage, structural operations, septic systems, plant community, initial soil chemistry, pesticides,
bacteria, impoundments, snow and atmospheric deposition. Each HRU points to objects in each of the associated
data files. HRU’s consist of plants and soils on the landscape and now are not associated with aquifers and ponds
and wetlands. HRUs are defined as contiguous areas (ie fields or grid cells) and a delivery from edge-of-field to
subbasin outlet is computed in the subbasin module. This is not necessary when landscape units or grid cells are
used. Several inputs for each HRU are required in addition to pointing to data files, including drainage area.
These variables may be moved to a calibration file.
HRU-DATA.HRU
Below is a sample HRU-DATA.HRU file:
90 SWAT+ INPUT/OUTPUT FILE DOCUMENTATION, VERSION 2016
hru-data.h
NUMB NAME TOPO HYD SOILAND_USE_MGTOIL_NUTR_INIT URF_STOR SNOW FIELD
1 hru1 top1 hyd1 soil003 lrew_ag04 soilnut001 null snow001 null
2 hru2 top2 hyd2 soil004 lrew_ag04 soilnut001 null snow001 null
3 hru3 top3 hyd3 soil005 lrew_ag03 soilnut001 null snow001 null
4 hru4 top4 hyd4 soil006 lrew_ag01 soilnut001 null snow001 null
5 hru5 top5 hyd5 soil008 lrew_ag04 soilnut001 null snow001 null
6 hru6 top6 hyd6 soil009 lrew_ag04 soilnut001 null snow001 null
HRU-LTE.HRU
Tropics (character):
TROPICAL
‘non_trop’ = non-tropical
‘trop’ = tropical
m
0.7 ⋅ 1 −
1
f hisand = 1 −
m
1 − s + exp − 5.51 +
100
where ms is the percent sand content
(0.05-2.00 mm diameter particles),
msilt is the percent silt content (0.002-
0.05 mm diameter particles), mc is
the percent clay content (< 0.002 mm
diameter particles), and orgC is the
percent organic carbon content of the
layer (%).
Required.
EXCO.EXC
The EXCO.EXC file contains the input variables for the nutrients of a channel. Below is a sample EXCO.EXC file:
exco.exc
NAME OM PEST PATH HMET SALT
exco1 exco_om1 exco_pest1 exco_path1 exco_hmet1 exco_salt1
exco2 exco_om2 exco_pest2 exco_path2 exco_hmet2 exco_salt2
EXCO_OM_EXC
The EXCO_OM_EXC file contains the input variables for the nutrients of a channel. Below is a sample
EXCO_OM.EXC file:
exco_om.exc
flo sed orgn sedp no3 solp psol psor chla nh3 no2 cbod dox bacp bacpl met1 met2 met3 san sil cla sag lag grv temp
exco_om1 12.5 100 90 80 70 60 50 40 30 20 10 9 8 7 6 5 4 3 2 1 100 90 80 70 60
exco_om2 22.5 110 99 88 77 66 55 44 33 22 11 19 28 37 46 55 64 73 82 91 190 98 87 76 65
EXCO_PEST.EXC
exco_pest.exc
aatrex_sol aatrex_sor banvel_sol banvel_sor prowl_sol prowl_sor roundup_sol roundup_sor
exco_pest1 12.5 100 90 80 70 60 50 40
exco_pest2 22.5 110 99 88 77 66 55 44
The EXCO_PEST.EXC file contains the input variables for the nutrients of a channel. Below is a sample
EXCO_PEST.EXC file:
SWAT+ INPUTS 101
Variable name Definition
TITLE The title of the exco_pest.exc file
HEADER Headers for the exco_pest.exc file
NAME Name of the pesticide (exco.exc file)
EXCO_PEST_SOL Pesticide soluble constituent mass
EXCO_PEST_SOR Pesticide sorbed constituent mass
EXCO_PATH.EXC
The EXCO_PATH.EXC file contains the input variables for the nutrients of a channel. Below is a sample
EXCO_PATH.EXC file:
exco_path.exc
fecals_sol fecals_sor e_coli_sol e_coli_sor
exco_path1 12.5 100 90 80
exco_path2 22.5 110 99 88
EXCO_HMET.EXC
The EXCO_HMET.EXC file contains the input variables for the nutrients of a channel. Below is a sample
EXCO_HMET.EXC file:
exco_hmet.exc
mercury_sol mercury_sor
exco_hmet1 12.5 100
exco_hmet2 22.5 110
EXCO_SALT.EXC
The EXCO_SALT.EXC file contains the input variables for the nutrients of a channel. Below is a sample
EXCO_SALT.EXC file:
exco_salt.exc
sodium_sol sodium_sor magnesium_sol magnesium_sor
exco_salt1 12.5 100 90 80
exco_salt2 22.5 110 99 88
RECALL
RECALL.REC
The RECALL.REC file contains the input variables for the nutrients of a channel. Below is a sample RECALL.REC
file:
recall.rec
NUMB NAME TYP FILENAME
1 daily 1 recall_day.rec
DR –Delivery Ratio
DELRATIO.DEL
The DELRATIO.DEL file contains the input variables for the nutrients of a channel. Below is a sample
DELRATIO.DEL file:
delratio.del
NAME OM_FILE PEST_FILE PATH_FILE HMET_FILE SALTS_FILE
dr01 dr_om.del dr_pest.del dr_path.del dr_hmet.del dr_salt.del
SWAT+ INPUTS 105
Variable name Definition
TITLE The title of the delratio.del file
HEADER Headers for the delratio.del file
NAME Name of the export coefficient (in delratio.con file)
OM_NAME Name of the organic matter (in dr_om.del file)
PEST_NAME Name of the pesticides (in dr_pest.del file)
PATH_NAME Name of the pathogens (in dr_path.del file)
SALT_NAME Name of the salt (in dr_salt.del file)
DR_OM.DEL
The DR_OM.DEL file contains the input variables for the nutrients of a channel. Below is a sample DR_OM.DEL
file:
dr_om.del
flo sed orgn sedp no3 solp psol psor chla nh3 no2 cbod dox bacp bacpl met1 met2 met3 san sil cla sag lag grv temp C
dr_om1 0.125 0.1 0.9 0.8 0.7 0.6 0.5 0.4 0.3 0.2 0.1 0.9 0.8 0.7 0.6 0.5 0.4 0.3 0.2 0.1 0.1 0.9 0.8 0.7 0.6 0.5
dr_om2 0.225 0.11 0.99 0.88 0.77 0.66 0.55 0.44 0.33 0.22 0.11 0.19 0.28 0.37 0.46 0.55 0.64 0.73 0.82 0.91 0.19 0.98 0.87 0.76 0.65 0.54
DR_PEST.DEL
The DR_PEST.DEL file contains the input variables for the nutrients of a channel. Below is a sample
DR_PEST.DEL file:
dr_pest.del
aatrex_sol aatrex_sor banvel_sol banvel_sor prowl_sol prowl_sor roundup_sol roundup_sor
dr_pest1 0.125 0.1 0.9 0.8 0.7 0.6 0.5 0.4
dr_pest2 0.225 0.11 0.99 0.88 0.77 0.66 0.55 0.44
SWAT+ INPUTS 107
The DR_PEST.DEL file contains the input variables for the nutrients of a channel. Below is a sample partial
DR_PEST_DEL file:
DR_PATH.DEL
The DR_PATH.DEL file contains the input variables for the nutrients of a channel. Below is a sample
DR_PATH.DEL file:
dr_path.del
fecals_sol fecals_sor e_coli_sol e_coli_sor
dr_path1 0.125 0.1 0.9 0.8
dr_path2 0.225 0.11 0.99 0.88
DR_HMET.DEL
The DR_HMET.DEL file contains the input variables for the nutrients of a channel. Below is a sample
DR_HMET.DEL file:
dr_hmet.del
mercury_sol mercury_sor
dr_hmet1 0.125 0.1
dr_hmet2 0.225 0.11
108 SWAT+ INPUT/OUTPUT FILE DOCUMENTATION, VERSION 2016
Variable name Definition
TITLE The title of the dr_hmet.exc file
HEADER Headers for the dr_hmet.exc file
NAME Name of the heavy metals (delratio.del file)
DR_HMET_SOL Heavy metal soluble constituent mass
DR_HMET_SOL Heavy metal sorbed constituent mass
DR_SALT.DEL
The DR_SALT.DEL file contains the input variables for the nutrients of a channel. Below is a sample
EXCO_DR_SALT.DEL file:
dr_salt.del
sodium_sol sodium_sormagnesium_solmagnesium_sor
dr_salt1 0.125 0.1 0.9 0.8
dr_salt2 0.225 0.11 0.99 0.88
AQUIFER –
AQUIFER.AQU
The fraction of percolation from the root zone which recharges the
deep aquifer. The value for RCHRG_DP should be between 0.0 and
1.0.
Required.
SPYLD Specific yield of the shallow aquifer (m3/m3).
Specific yield is defined as the ratio of the volume of water that drains by gravity
HERD.HRD
RANCH.HRD
ELEMENT.WRO
WATER_RIGHTS.WRO
LINK –
CHAN-SURF.LIN
SWAT+ INPUTS 113
Below is a sample CHAN_SURF.LIN FILE:
chan-surf.l
1
NUMB NAME NSPU OBTYP OBTYP_NO OBTYP OBTYP_NO
1 chan1 1 hru 1
2 chan2 1 sub 1
8 chan3 2 sub 3 sub 4
9 chan4 2 hru 5 hru 6
CHAN-AQU.LIN
Below is a sample CHAN-AQU.LIN FILE:
chan-aqu.lin
4
NUMB NAME NSPU AQU1 AQU2 AQU3
1 chan1 3 1 2 3
2 chan2 1 4
8 chan3 2 5 6
9 chan4 2 8 9
TOPOGRAPHY.HYD
Data contained in the topo.dat data file can be grouped into the following categories: topographic characteristics,
water flow, erosion, land cover, and depressional storage areas.
FIELD.FLD
STRUCTURAL –
TILEDRAIN.STR
Tile drains remove excess water for an area to optimize plant growth. Drains may be added at the
beginning of the simulation in the .mgt file. To account for the installation of tile drains mid-simulation, the
option was included as a schedulable operation.
tiledrain.str
NAME DEPTH TIME LAG RADIUS DIST DRAIN_CO PUMPCAP LATKSAT
mw24_1000 1000 24 96 100 30 10 1 2
SEPTIC.STR
The Onsite Wastewater Systems (OWSs) input file contains information related to a diversity of features of OWSs
within the subbasin. Data contained in the septic.dat data file are: type of septic system, geometry of biozone,
characteristics of biomass, and bio-physical reaction coefficients occurring in the biozone (Adapted from Siegrist
et al., 2005).
Below is a partial sample SEPTIC.STR FILE: (ALL VARIABLES NOT INCLUDED IN SAMPLE):
septic.str
NAME TYP YR OPT CAP AREA TFAIL DEPTH THK STRM_DISTDENSITY BD
standard 1 0 0 2.5 100 70 500 50 0.5 1.5 1000
failing 1 0 0 2.5 100 1 500 50 0.5 1.5 1000
TITLE The first line of the file is reserved for user comments. The
comments may take up to 80 spaces. The title line is not processed
by the model and may be left blank.
HEADER Headings for variables
NAME Name
122 SWAT+ INPUT/OUTPUT FILE DOCUMENTATION, VERSION 2016
TYP The type of septic system
Type Definition
1 Generic type conventional system
2 Generic type advanced system
3 Septic tank with conventional drainfield
4 Septic tank with SASa type 1
5 Septic tank with SAS type 2
6 Septic tank with in-tank N removal and SAS
7 Septic tank with effluent N removal recycle
8 Septic tank with corrugated plastic trickling
Filter
9 Septic tank with open-cell form trickling filter
10 Single pass sand filter 1
11 Single pass sand filter 2
12 Single pass sand filter 3
13 Single pass sand filter 4
14 At grade recirculating sand filter
15 Maryland style RSFb
16 RSF
17 Septic tank w/ constructed wetland
and surface water discharge
18 Municipal wastewater w/ constructed wetland
and surface water discharge 1
19 Municipal wastewater w/ constructed wetland
and surface water discharge 2
20 Municipal wastewater w/ constructed wetland
21 Municipal wastewater w/ lagoon and
constructed wetland
22 Waterloo biofilter (plastic media) 1
23 Waterloo biofilter (plastic media) 2
24 Peat biofilter
25 Recirculating textile filter
26 Foam or textile filter effluent
27 Septic, recirculating gravel filter,
UV disinfection
28 Untreated Effluent - Texas A&M reference
Year the septic system became operational (eg 1980).
YR
If 0 is input for isep_iyr, the model assumes the septic system is in
operation at the beginning of the simulation
SWAT+ INPUTS 123
OPT Initial septic HRU operational condition. User can define the default
condition of a septic HRU as either active (sep_opt=1), failing
(sep_opt=2), or non-septic (sep_opt=0). An active system
automatically becomes failing as biozone layer gets clogged over
time. A failing system turns to an active system after user specified
“number of days for rehabilitation” defined by isep_tfail.
FILTERSTRIP.STR
A filter strip is a strip of dense vegetation located to intercept runoff from upslope pollutant sources and
filter it. Filter strips remove contaminants by reducing overland flow velocity which results in the deposition of
SWAT+ INPUTS 125
particulates. The filter strip area also acts as an area of increased infiltration, reducing both the runoff volume
and non-particulate contaminants. The filter strip used algorithm used in SWAT was derived from White and
Arnold (2009). Filter strips reduce sediment, nutrients, bacteria, and pesticides, but do not affect surface runoff
in SWAT. The variables which may be entered on the pesticide application line are listed and described below.
filterstrip.str
NAME VFSRATIO VFSCON VFSCH
field_border 0.1 0.003 0.2 Field_border
high_engineered 0.1 0.001 0.05 Highly_engineered_low_channelized
GRASSEDWW.STR
Grassed waterways are vegetated channels which transport runoff from a field. Vegetation within the
waterways reduces flow velocities, and protects the waterway from the scouring potential of concentrated flow.
These are generally broad and shallow channels; the channel simulated in SWAT has a side slope of 8:1. Grasses
waterways trap sediment and other contaminants by reducing flow velocities which increases deposition of
particulate contaminates.
BMPUSER.STR
There are many conservation practices for which approximate removal efficiencies have been established
which are unsupported by SWAT or any other existing model. To allow these practices to be included, this generic
conservation practice operation allows fixed removal efficiencies to be specified by constituent.
HRU_PARM_DB– The parameters database files are supplied with the model containing
Input parameters for most of the common plants, fertilizers, pesticides, urban, are included in
the database files with the option for the user to add new parameters to each file.
PLANTS.PLT
Information required to simulate plant growth is stored by plant species in the plant growth database file. This
database file is supplied with the model. The plant growth database distributed with SWAT includes parameters
for most of the common plant species. If a user needs to model a land use or plant not included in the database,
please feel free to contact the SWAT development team for assistance in determining plant parameters. Appendix
A documents the source of parameter values in the distributed database file. Below is a partial sample PLANTS.PLT
file (see plants.plt in example input dataset directory for complete file):
plants.plt:
name plnt_typ plnt_hu bm_e harv_idx lai_pot frac_hu1 lai_max1 frac_hu2 lai_max2 hu_lai_deccan_ht_mart_dp_max
agrl warm_ann 2000 33.5 0.45 3 0.15 0.05 0.5 0.95 0.64 1 2
agrr warm_ann 2000 39 0.5 3 0.15 0.05 0.5 0.95 0.7 2.5 2
agrc cold_annua 2000 30 0.4 4 0.05 0.05 0.45 0.95 0.5 0.9 1.3
orcd trees 2000 15 0.1 4 0.1 0.15 0.5 0.75 0.99 3.5 2
hay perennial 2000 35 0.9 4 0.05 0.05 0.49 0.95 0.99 0.5 2
frst trees 2000 15 0.76 5 0.05 0.05 0.4 0.95 0.99 6 3.5
frsd trees 2000 15 0.76 5 0.05 0.05 0.4 0.95 0.99 6 3.5
frse trees 2000 15 0.76 5 0.15 0.7 0.25 0.99 0.99 10 3.5
wetl perennial 2000 47 0.9 6 0.1 0.2 0.2 0.95 0.7 2.5 2.2
wetf trees 2000 15 0.76 5 0.05 0.05 0.4 0.95 0.99 6 3.5
wetn perennial 2000 47 0.9 6 0.1 0.2 0.2 0.95 0.7 2.5 2.2
Figure 14-2: Leaf area index as a function of fraction of growing season for Alamo switchgrass
134 SWAT+ INPUT/OUTPUT FILE DOCUMENTATION, VERSION 2016
Variable name Definition
BLAI, cont. To identify the leaf area development parameters, record
the leaf area index and number of accumulated heat units
for the plant species throughout the growing season and
then plot the results. For best results, several years worth of
field data should be collected. At the very minimum, data
for two years is recommended. It is important that the
plants undergo no water or nutrient stress during the years
in which data is collected.
The leaf area index incorporates information about the
plant density, so field experiments should either be set up
to reproduce actual plant densities or the maximum LAI
value for the plant determined from field experiments
should be adjusted to reflect plant densities desired in the
simulation. Maximum LAI values in the default database
correspond to plant densities associated with rainfed
agriculture.
The leaf area index is calculated by dividing the green leaf
area by the land area. Because the entire plant must be
harvested to determine the leaf area, the field experiment
needs to be designed to include enough plants to
accommodate all leaf area measurements made during the
year.
Although measuring leaf area can be laborious for large
samples, there is no intrinsic difficulty in the process. The
most common method is to obtain an electronic scanner and
feed the harvested green leaves and stems into the scanner.
Older methods for estimating leaf area include tracing of
the leaves (or weighed subsamples) onto paper, the use of
planimeters, the punch disk method of Watson (1958) and
the linear dimension method of Duncan and Hesketh
(1968).
Chapter 5:1 in the Theoretical Documentation reviews the
methodology used to calculate accumulated heat units for a
plant at different times of the year as well as determination
of the fraction of total, or potential, heat units that is
required for the plant database.
SWAT+ INPUTS 135
Variable name Definition
BLAI, cont. The values for BLAI in the plant growth database are based
on average plant densities in dryland (rainfed) agriculture.
BLAI may need to be adjusted for drought-prone regions
where planting densities are much smaller or irrigated
conditions where densities are much greater.
Required.
FRGRW1 Fraction of the plant growing season or fraction of total
potential heat units corresponding to the 1st point on the
optimal leaf area development curve.
Please see Figure 14-2 and the explanation given for
parameter BLAI to obtain additional information about this
parameter and methods used to measure it.
Required.
LAIMX1 Fraction of the maximum leaf area index corresponding to
the 1st point on the optimal leaf area development curve.
Please see Figure 14-2 and the explanation given for
parameter BLAI to obtain additional information about this
parameter and methods used to measure it.
Required.
FRGRW2 Fraction of the plant growing season or fraction of total
potential heat units corresponding to the 2nd point on the
optimal leaf area development curve.
Please see Figure 14-2 and the explanation given for
parameter BLAI to obtain additional information about this
parameter and methods used to measure it.
Required.
LAIMX2 Fraction of the maximum leaf area index corresponding to
the 2nd point on the optimal leaf area development curve.
Please see Figure 14-2 and the explanation given for
parameter BLAI to obtain additional information about this
parameter and methods used to measure it.
Required.
136 SWAT+ INPUT/OUTPUT FILE DOCUMENTATION, VERSION 2016
Variable name Definition
DLAI Fraction of growing season when leaf area begins to decline.
Please see Figure 14-2 and the explanation given for
parameter BLAI to obtain additional information about this
parameter and methods used to measure it.
Required.
CHTMX Maximum canopy height (m).
Maximum canopy height is a straightforward measurement.
The canopy height of non-stressed plants should be recorded
at intervals throughout the growing season. The maximum
value recorded is used in the database.
Required.
RDMX Maximum root depth (m).
To determine maximum rooting depth, plant samples need to
be grown on soils without an impermeable layer. Once the
plants have reached maturity, soil cores are taken for the
entire depth of the soil. Each 0.25 meter increment is washed
and the live plant material collected. Live roots can be
differentiated from dead roots by the fact that live roots are
whiter and more elastic and have an intact cortex. The
deepest increment of the soil core in which live roots are
found defines the maximum rooting depth.
Required.
T_OPT Optimal temperature for plant growth (ºC).
Both optimal and base temperatures are very stable for
cultivars within a species.
Optimal temperature for plant growth is difficult to measure
directly. Looking at Figure 14-3, one might be tempted to
select the temperature corresponding to the peak of the plot
as the optimal temperature. This would not be correct.
SWAT+ INPUTS 137
Variable name Definition
T_OPT, cont. The peak of the plot defines the optimal temperature for
leaf development—not for plant growth.
If an optimal temperature cannot be obtained through a
review of literature, use the optimal temperature listed for
a plant already in the database with similar growth habits.
Review of temperatures for many different plants have
provided generic values for base and optimal temperatures
as a function of growing season. In situations, where
temperature information is unavailable, these values may
be used. For warm season plants, the generic base
temperature is ~8ºC and the generic optimal temperature is
~25ºC. For cool season plants, the generic base temperature
is ~0ºC and the generic optimal temperature is ~13ºC.
Required.
T_BASE Minimum (base) temperature for plant growth (ºC).
SWAT uses the base temperature to calculate the number
of heat units accrued every day. The minimum or base
temperature for plant growth varies with growth stage of
the plant. However, this variation is ignored by the
model—SWAT uses the same base temperature throughout
the growing season.
Base temperature is measured by growing plants in growth
chambers at several different temperatures. The rate of leaf
tip appearance as a function of temperature is plotted.
Extrapolating the line to the leaf tip appearance rate of 0.0
leaves/day gives the base or minimum temperature for
plant growth. Figure 14-3 plots data for corn. (Note that the
line intersects the x-axis at 8°C.)
Required.
138 SWAT+ INPUT/OUTPUT FILE DOCUMENTATION, VERSION 2016
Variable name Definition
T_BASE, cont.
Figure 14-3: Rate of leaf tip appearance as a function of temperature for corn (after Kiniry et
al, 1991)
Figure 14-4: Response of radiation-use efficiency to mean daily vapor pressure deficit for grain
sorghum (after Kiniry, 1999).
vertically
oriented
leaf
fertilizer.fr
FERT_NAMFR_MINN FR_MINP FR_ORGN FR_ORGP FR_NH3n BACT_PER BACT_LPERBACT_KD FR_WEP FERT_TYPE
elem-n 1 0 0 0 0 0 0 0 0 0
elem-p 0 1 0 0 0 0 0 0 0 0
anh-nh3 0.82 0 0 0 1 0 0 0 0 0
150 SWAT+ INPUT/OUTPUT FILE DOCUMENTATION, VERSION 2016
Variable name Definition
TITLE The first line is reserved for user comments. This line is not
processed by the model and may be left blank.
Optional.
HEADER Headers for the fertilizer.frt file.
FERTNM Name of fertilizer/manure (up to 8 characters allowed).
Required.
FMINN Fraction of mineral N (NO3 and NH4) in fertilizer (kg min-
N/kg fertilizer).
Value should be between 0.0 and 1.0.
Required.
FMINP Fraction of mineral P in fertilizer (kg min-P/kg fertilizer).
Value should be between 0.0 and 1.0.
Required.
FORGN Fraction of organic N in fertilizer (kg org-N/kg fertilizer).
Value should be between 0.0 and 1.0.
Required.
FORGP Fraction of organic P in fertilizer (kg org-P/kg fertilizer).
Value should be between 0.0 and 1.0.
Required.
FNH3N Fraction of mineral N in fertilizer applied as ammonia (kg
NH3-N/kg min-N).
Value should be between 0.0 and 1.0.
Required.
BACTPDB Concentration of persistent bacteria in manure/fertilizer (#
cfu/g manure).
Optional.
SWAT+ INPUTS 151
Variable name Definition
BACTLPDB Concentration of less-persistent bacteria in
manure/fertilizer (# cfu/g manure).
Optional.
BACTKDDB Fraction of bacteria in solution.
Value should be between 0.0 and 1.0. As the bacteria
partition coefficient approaches 0.0, bacteria is primarily
sorbed to soil particles. As the bacteria partition coefficient
approaches 1.0, bacteria is primarily in solution.
Optional.
152 SWAT+ INPUT/OUTPUT FILE DOCUMENTATION, VERSION 2016
TILLAGE.TIL
Tillage operations redistribute nutrients, pesticide and residue in the soil profile. Appendix A documents the
source of parameter values in the database file provided with the model.
Below is a partial listing of the tillage.til file.
tillage.til:
TILLNM EFFMIX DEPTIL RANRNS RIDGE_HT RIDGE_SP Description
fallplow 0.95 150 75 0 0 genericfallplowingoperation
sprgplow 0.5 125 50 0 0 genericspringplowingoperation
constill 0.25 100 40 0 0 genericconservationtillage
zerotill 0.05 25 10 0 0 genericno-tillmixing
duckftc 0.55 100 15 0 0 duckfootcultivator
fldcult 0.3 100 20 0 0 fieldcultivator
furowout 0.75 25 15 0 0 furrow-outcultivator
marker 0.45 100 15 0 0 marker(cultivator)
rollcult 0.5 25 15 0 0 rollingcultivator
rowcult 0.25 25 15 0 0 rowcultivator
discovat 0.5 25 15 0 0 discovator
leveler 0.5 25 15 0 0 leveler
SWAT+ INPUTS 153
Variable name Definition
TITLE The first line is reserved for user comments. This line is not
processed by the model and may be left blank.
Optional.
HEADER Headers for the tillage.til.res file.
TILLNM Name of fertilizer/manure (up to 8 characters allowed).
Required.
EFFMIX Mixing efficiency of tillage operation.
The mixing efficiency specifies the fraction of materials
(residue, nutrients and pesticides) on the soil surface which
are mixed uniformly throughout the soil depth specified by
DEPTIL. The remaining fraction of residue and nutrients is
left in the original location (soil surface or layer).
Required.
DEPTIL Depth of mixing caused by the tillage operation (mm).
Required.
RANRNS Random roughness (mm)
Required.
RIDGE_HT Ridge height (mm)
Required.
RIDGE_SP Ridge interval (mm)
Required.
PESTICIDE.PST
The pesticide database contains parameters that govern pesticide fate and transport in the HRUs. Appendix A
documents the source of parameter values in the database file provided with the model. Below is a partial listing
of the pesticide.pst file.
pesticide.p
PESTNM SKOC PST_WOF HLIFE_F HLIFE_S AP_EF PST_WSOL Description
245-tp 2600 0.4 5 20 0.75 2.5 Silvex Amine
2plus2 20 0.95 10 21 0.75 660000 Mecoprop
aatrex 171 0.45 5 60 0.75 33 Atrazine
abate 100000 0.65 5 30 0.75 0 Abate
acaraben 2000 0.05 10 20 0.75 13 Chlorobenzilate Salt
accelera 20 0.9 7 7 0.75 100000 Endothall
acclaim 9490 0.2 5 9 0.75 0.8 Fenoxaprop-Ethyl Sodium Salt
alanap 20 0.95 7 14 0.75 231000 Naptalam
alar 10 0.95 4 7 0.75 100000 Daminozide
aldrin 300 0.05 2 28 0.75 0.1 Aldrin
154 SWAT+ INPUT/OUTPUT FILE DOCUMENTATION, VERSION 2016
Variable name Definition
TITLE The first line is reserved for user comments. This line is not
processed by the model and may be left blank.
Optional.
HEADER Headers for the pestidide.pst file.
PESTNM Name of pesticide/toxin. (up to 17 characters allowed)
Required.
SKOC Soil adsorption coefficient normalized for soil organic
carbon content (mg/kg)/(mg/L).
Pesticide in the soil environment can be transported in
solution or attached to sediment. The partitioning of a
pesticide between the solution and soil phases is defined by
the soil adsorption coefficient for the pesticide. The soil
adsorption coefficient is the ratio of the pesticide
concentration in the soil or solid phase to the pesticide
concentration in the solution or liquid phase:
C
K p = solidphase
C solution
where Kp is the soil adsorption coefficient ((mg/kg)/(mg/L)
or m3/ton), Csolidphase is the concentration of the pesticide
sorbed to the solid phase (mg chemical/kg solid material or
g/ton), and Csolution is the concentration of the pesticide in
solution (mg chemical/L solution or g/ton). The definition
of the soil adsorption coefficient in this equation assumes
that the pesticide sorption process is linear with
concentration and instantaneously reversible.
Because the partitioning of pesticide is dependent upon the
amount of organic material in the soil, the soil adsorption
coefficient input to the model is normalized for soil organic
carbon content. The relationship between the soil
adsorption coefficient and the soil adsorption coefficient
normalized for soil organic carbon content is:
orgC
K p = K oc ⋅
100
SWAT+ INPUTS 155
Variable name Definition
SKOC, cont. where Kp is the soil adsorption coefficient
((mg/kg)/(mg/L)), Koc is the soil adsorption coefficient
normalized for soil organic carbon content
3
((mg/kg)/(mg/L) or m /ton), and orgC is the percent
organic carbon present in the soil.
Required.
PST_WOF Wash-off fraction.
The wash-off fraction quantifies the fraction of pesticide on
the plant canopy that may be dislodged. The wash-off
fraction is a function of the nature of the leaf surface, plant
morphology, pesticide solubility, polarity of the pesticide
molecule, formulation of the commercial product and
timing and volume of the rainfall event.
Required.
HLIFE_F Degradation half-life of the chemical on the foliage (days).
The half-life for a pesticide defines the number of days
required for a given pesticide concentration to be reduced
by one-half. The half-life entered for a pesticide is a lumped
parameter that includes the net effect of volatilization,
photolysis, hydrolysis, biological degradation and
chemical reactions.
For most pesticides, the foliar half-life is much less than the
soil half-life due to enhanced volatilization and
photodecomposition. If the foliar half-life is available for
the pesticide this value should be used. If the foliar half-life
is not available, the foliar half-life can be estimated using
the following rules:
1) Foliar half-life is assumed to be less than the soil half-
life by a factor of 0.5 to 0.25, depending on vapor
pressure and sensitivity to photodegradation.
2) Foliar half-life is adjusted downward for pesticides with
vapor pressures less than 10-5 mm Hg.
3) The maximum foliar half-life assigned is 30 days.
Required.
156 SWAT+ INPUT/OUTPUT FILE DOCUMENTATION, VERSION 2016
Variable name Definition
HLIFE_S Degradation half-life of the chemical in the soil (days).
The half-life for a pesticide defines the number of days
required for a given pesticide concentration to be reduced
by one-half. The soil half-life entered for a pesticide is a
lumped parameter that includes the net effect of
volatilization, photolysis, hydrolysis, biological
degradation and chemical reactions.
Required.
AP_EF Application efficiency.
The fraction of pesticide applied which is deposited on the
foliage and soil surface (0.1-1.0). The remainder is lost.
The application efficiency for all pesticides listed in the
database is defaulted to 0.75. This variable is a calibration
parameter.
Required.
PST_WSOL Solubility of the chemical in water (mg/L or ppm)
The water solubility value defines the highest concentration
of pesticide that can be reached in the runoff and soil pore
water. While this is an important characteristic, researchers
have found that the soil adsorption coefficient, Koc, tends to
limit the amount of pesticide entering solution so that the
maximum possible concentration of pesticide in solution is
seldom reached.
Reported solubility values are determined under laboratory
conditions at a constant temperature, typically between
20°C and 30°C.
Required.
PATHOGENS.PTH
URBAN.URB
The urban database summarizes parameters used by the model to simulate different types of urban areas.
Appendix A documents the source of parameter values in the database file provided with the model. Below is a
partial listing of the urban.urb file.
urban.urb:
urbnm fimp fcimp curbden urbcoef dirtmx thalf tnconc tpconc tno3conc urbcn2
residen_high_den 0.6 0.44 0.24 0.18 225 0.75 550 223 7.2 98 Residentia Density
residen_med_den 0.38 0.3 0.24 0.18 225 0.75 550 223 7.2 98 Residentia Density
residen_ml_den 0.2 0.17 0.24 0.18 225 0.75 460 196 6 98 Residentia Density
residen_low_den 0.12 0.1 0.24 0.18 225 0.75 460 196 6 98 Residentia Density
commercial 0.67 0.62 0.28 0.18 200 1.6 420 240 5.5 98 Commercial
industrial 0.84 0.79 0.14 0.18 400 2.35 430 104 5.6 98 Industrial
transportation 0.98 0.95 0.12 0.18 340 3.9 480 212 6.3 98 Transportation
institutional 0.51 0.47 0.12 0.18 340 3.9 480 212 6.3 98 Institutional
residential 0.38 0.3 0.24 0.18 225 0.75 550 223 7.2 98 Residential
SWAT+ INPUTS 159
Variable name Definition
TITLE The first line of the file is reserved for user comments. The
comments may take up to 80 spaces. The title line is not
processed by the model and may be left blank.
HEADER Headings for the variables
URBNM 4-character code for urban land type.
The 4-letter codes in the plant growth and urban databases
are used by the GIS interfaces to link land use/land cover
maps to SWAT plant types. This code is printed to the
output files.
When adding a new urban category, the four letter code
for the new urban land type must be unique.
Required.
FIMP Fraction total impervious area in urban land type. This
includes directly and indirectly connected impervious
areas.
Urban areas differ from rural areas in the fraction of total
area that is impervious. Construction of buildings, parking
lots and paved roads increases the impervious cover in a
watershed and reduces infiltration. With development, the
spatial flow pattern of water is altered and the hydraulic
efficiency of flow is increased through artificial channels,
curbing, and storm drainage and collection systems.
Required.
FCIMP Fraction directly connected impervious area in urban land
type.
160 SWAT+ INPUT/OUTPUT FILE DOCUMENTATION, VERSION 2016
Variable name Definition
FCIMP, cont. Impervious areas can be differentiated into two groups—
the area that is hydraulically connected to the drainage
system and the area that is not directly connected. As an
example, assume there is a house surrounded by a yard
where runoff from the roof flows into the yard and is able
to infiltrate into the soil. The rooftop is impervious but it
is not hydraulically connected to the drainage system. In
contrast, a parking lot whose runoff enters a storm water
drain is hydraulically connected.
When modeling urban areas the connectedness of the
drainage system must be quantified. The best methods for
determining the fraction total and directly connected
impervious areas is to conduct a field survey or analyze
aerial photographs.
Required.
CURBDEN Curb length density in urban land type (km/ha).
Curb length may be measured directly by scaling the total
length of streets off of maps and multiplying by two. To
calculate the density, the curb length is divided by the area
represented by the map.
Required.
URBCOEF Wash-off coefficient for removal of constituents from
impervious area (mm-1).
Wash off is the process of erosion or solution of
constituents from an impervious surface during a runoff
event. The original default value for urbcoef was calculated
as 0.18 mm-1 by assuming that 13 mm of total runoff in one
hour would wash off 90% of the initial surface load (Huber
and Heaney, 1982). Using sediment transport theory,
Sonnen (1980) estimated values for the wash-off
coefficient ranging from 0.002-0.26 mm-1. Huber and
Dickinson (1988) noted that values between 0.039 and
0.390 mm-1 for the wash-off coefficient give sediment
concentrations in the range of most observed values. This
variable is used to calibrate the model to observed data.
Required.
DIRTMX Maximum amount of solids allowed to build up on
impervious areas (kg/curb km).
Required.
SWAT+ INPUTS 161
Variable name Definition
THALF Number of days for amount of solids on impervious areas
to build up from 0 kg/curb km to half the maximum
allowed, i.e. 1/2 DIRTMX (days).
Required.
TNCONC Concentration of total nitrogen in suspended solid load
from impervious areas (mg N/kg sed).
Required.
TPCONC Concentration of total phosphorus in suspended solid load
from impervious areas (mg P/kg sed).
Required.
TNO3CONC Concentration of nitrate in suspended solid load from
impervious areas (mg NO3-N/kg sed).
Required.
URBCN2 Curve number for moisture condition II in impervious areas
of urban land type.
Required.
SEPTIC.SEP
Information of water quality or effluent characteristics required to simulate different types of Onsite Wastewater
Systems (OWSs) is stored in the septic water quality database. The database file distributed with SWAT includes
water quality data for most of conventional, advanced, and failing septic systems. Information contained in the
septic water quality database is septic tank effluent flow rate for per capita and effluent characteristics of various
septic systems. The database is developed based on the field data summarized by Siegrist et al. (2005), McCray
et al. (2005) and OWTS 201 (2005). Below is a partial listing of the septic.sep file.
septic.sep -
SEPNM QSBODCONCS TSSCONCSNH4CONCSNO3CONCSNO2CONCSRGNCONCS MINPS ORGPS FCOLIS
GCON 0.227 170 75 42.4 0 0 10 6 1 10000000
GADV 0.227 22 14 18.9 9.6 0 3 5.1 0.9 543
COND 0.227 170 75 58 0.2 0 14 9 1 10000000
SAS1 0.227 170 75 60 0 0 10 8.5 1.5 10000000
SAS2 0.227 170 75 0 0 0 0 9 1 10000000
162 SWAT+ INPUT/OUTPUT FILE DOCUMENTATION, VERSION 2016
Variable name Definition
TITLE The first line is reserved for user comments. This line is not
processed by the model and may be left blank.
Optional.
HEADER Headers for the septic.sep file.
SWAT+ INPUTS 163
SEPNM Abridged name of a septic system
sptname Definition
GCON Generic type conventional system
GADV Generic type advanced system
COND Septic tank with conventional drainfield
SAS1 Septic tank with SASa type 1
SAS2 Septic tank with SAS type 2
SAS3 Septic tank with in-tank N removal and SAS
SAS4 Septic tank with effluent N removal recycle
Septic tank with corrugated plastic trickling
SAS5
Filter
SAS6 Septic tank with open-cell form trickling filter
SPF1 Single pass sand filter 1
SPF2 Single pass sand filter 2
SPF3 Single pass sand filter 3
SPF4 Single pass sand filter 4
RCF1 At grade recirculating sand filter
RCF2 Maryland style RSFb
RCF3 RSF
Septic tank w/ constructed wetland
CWT1
and surface water discharge
Municipal wastewater w/ constructed wetland
CWT2
and surface water discharge 1
Municipal wastewater w/ constructed wetland
CWT3
and surface water discharge 2
CWT4 Municipal wastewater w/ constructed wetland
Municipal wastewater w/ lagoon and
CWT5
constructed wetland
BFL1 Waterloo biofilter (plastic media) 1
BFL2 Waterloo biofilter (plastic media) 2
BFL3 Peat biofilter
TXF1 Recirculating textile filter
TXF2 Foam or textile filter effluent
Septic, recirculating gravel filter,
GFL1
UV disinfection
USPT Untreated Effluent - Texas A&M reference
a: Sand absorption system
b: Recirculating sand filter
164 SWAT+ INPUT/OUTPUT FILE DOCUMENTATION, VERSION 2016
QS Septic tank effluent (STE) flow rate (m3/capita/day).
McCray et al. (2005) proposed 0.227 m3/capita/day as the
median value for USA based on the data collected from
various sources.
100
90
Cumulative Frequency, %
80
70
60 - 414878.3 + 100.16x 3.63
y=
50 2949092.6 + x 3.63
40
R2=0.99987
30
20
10
0
0 50 100 150 200 250
Mean Residential flow (gal/cap/d)
SNOW.SNO
The SNOW.SNO file contains the input variables for snow. Below is a partial listing of the snow.sno file.
snow.sno
NAME FALLTMP MELTTMP MELTMX MELTMN TIMP COVMX COV50 INIT_MM
snow001 1.0 2.0 6.0 3.0 1.0 0.0 0.0 0.0
OPS– The OPS files contain management operations for fertilizer, pesticide, grazing, harvest,
irrigation and sweep.
HARV.OPS
The inputs for grazing are found in the HARV.OPS file. This operation harvests the portion of the plant designated
as yield and removes the yield from the HRU, but allows the plant to continue growing. This operation is used
for hay cuttings. A sample HARV.OPS file is listed below.
harv.ops
NAME TYP HI_OVR EFF BM_MIN
grain grain 0 0.95 0
grass_mulch biomass 0.5 0 2000
grass_bag biomass 0.5 1 2000
silage biomass 0.9 0.95 0
forest_cut tree 0.95 0.99 0
stover_high residue 0.9 1 1000
stover_med residue 0.6 1 2000
stover_los residue 0.3 1 3000
hay_cut_high biomass 0.8 1 3000
hay_cut_low biomass 0.8 1 1000
potatoes tuber 1.1 0.95 0
peanuts tuber 1.1 0.95 0
GRAZE.OPS
The inputs for grazing are found in the GRAZE.OPS file. This operation removes plant biomass at a specified rate
and allows simultaneous application of manure. A sample GRAZE.OPS file is listed below.
graze.ops
NAME FERTNM DAYS EAT TRAMP MANURE BIO_MIN
fr_gr dairy_fr 365 10 5 5 500
fr_congr dairy_fr 365 10 5 5 4000
IRR.OPS
The inputs for irrigation are found in the IRR.OPS file. This operation applies water to the HRU on the specified
day. A sample IRR.OPS file is listed below:
irr.ops
IRR_OP_NAME IRR_EFF RQ_RATIO DEPTH IRR_SALT IRR_NO3 IRR_PO4
surface 0.5 0.4 0 0 0 0
sprinkler 0.7 0.1 0 0 0 0
drip 0.9 0 0 0 0 0
subsurface 1 0 150 0 0 0
CHEM_APP.OPS
The inputs for sweeping operations are found in the CHEM_APP.OPS file. A sample CHEM_APP.OPS file is listed
below:
chem_app.ops
PEST_OP_NAME FORM OPERATION APP_EFF FOLIAR_EFF INJECT_DEP SURF_FRAC DRIFT_POT AERIAL_UNIF
broadcast solid spread 0.9 0 0 1 0 1
band solid spread 0.9 0 0 1 0 0.5
foliar liquid spray 0.8 0.7 0 1 0 1
inject liquid inject 0.95 0 150 0.2 0 1
aerial_liquid liquid spray 0.7 0.7 0 1 0.5 1
aerial_solid solid spread 0.9 0 0 1 0.1 1
drill solid inject 0.95 0 50 0.05 0 1
side_dress solid spread 0.9 0 0 1 0 0.5
fertigate liquid spray 0.9 0.5 0 1 0.2 1
basal liquid spread 0.9 0 0 1 0 0.1
rope_wick liquid direct 1 0.95 0 1 0 1
tree_inject liquid inject 0.95 0 300 0 0 0.01
FIRE.OPS
The inputs for sweeping operations are found in the FIRE.OPS file. A sample FIRE.OPS file is listed below.
fire.ops
NAME CN2_UPD FRAC_BURN
grass 8 1
tree_intense 8 0.9
tree_low 6 0.7
SWEEP.OPS
The inputs for sweeping operations are found in the SWEEP.OPS file. A sample SWEEP.OPS file is listed below:
sweep.ops
SWP_OP_NAME SWP_EFF FR_CURB
high_eff 0.8 0.9
174 SWAT+ INPUT/OUTPUT FILE DOCUMENTATION, VERSION 2016
Variable name Definition
TITLE The first line of the file is reserved for user comments. The
comments may take up to 80 spaces. The title line is not
processed by the model and may be left blank.
HEADER Headings for the variables
NAME Street sweeping operation name
EFF Removal efficiency of sweeping operation
The removal efficiency of street sweeping is a function of
the type of sweeper, whether flushing is a part of the
street cleaning process, the quantity of total solids, the
frequency of rainfall events and the constituents
considered. Removal efficiency can vary depending on the
constituent being considered, with efficiencies being
greater for particulate constituents. The removal
efficiencies for nitrogen and phosphorus are typically less
than the solid removal efficiency (Pitt, 1979).
Because SWAT assumes a set concentration of nutrient
constituents in the solids, the same removal efficiency is in
effect used for all constituents. Table 20-7 provides
removal efficiencies for various street cleaning programs.
SWEEPEFF is a fraction that ranges between 0.0 and 1.0.
A value of 0.0 indicates that none of the built-up sediments
are removed while a value of 1.0 indicates that all of the
built-up sediments are removed.
Required.
LANDUSE.LUM
MANAGEMENT.SCH
The inputs management operations are found in the MANAGEMENT.SCH file. A sample MANAGEMENT.SCH file is
listed below:
management.sch
NAME NUM_OPS OP MON DAY HUSC OP_DATAP_METHOD OP_OVER
csoy_ai_nt 7 1
autoirr_str.8
fert 0 0 0.14 anh-nh3 inject 200 FERTILIZER
plnt 0 0 0.15 corn null 0 PLANT CORN BEGIN
hvkl 10 30 1.2 corn grain 0 HARVKILL
skip 0 0 0 null null 0 SKIP_YEAR
plnt 0 0 0.15 soyb null 0 PLANT SOYBEANS
hvkl 10 30 1.2 soyb grain 0 HARVKILL
skip 0 0 0 null null 0 SKIP_YEAR
canary_nomgt 0 0
180 SWAT+ INPUT/OUTPUT FILE DOCUMENTATION, VERSION 2016
SWAT will simulate different types of management operations. The variables for the different operations will
be defined in separate sections. The type of operation simulated is identified by the code given for the variable
MGT_OP.
The different codes for MGT_OP are:
PCO plant community: this operation initializes the plant
community in the HRU
PLNT planting/beginning of growing season: this operation
initializes the growth of a specific land cover/plant type in the
HRU
HARV harvest only operation: this operation harvests the portion of
the plant designated as yield and removes the yield from the
HRU, but allows the plant to continue growing. This operation
is used for hay cuttings.
HVKL harvest and kill operation: this operation harvests the
portion of the plant designated as yield, removes the yield
from the HRU and converts the remaining plant biomass to
residue on the soil surface.
TILL tillage operation: this operation mixes the upper soil layers
and redistributes the nutrients/chemicals/etc. within those
layers
IRRM irrigation operation: this operation applies water to the HRU
on the specified day. (IRROPS.DAT)
FERT fertilizer application: this operation adds nutrients to the soil
in the HRU on the specified day (FERTOPS.DAT)
PEST pesticide application: this operation applies a pesticide to the
plant and/or soil in the HRU on the specified day
GRAZ grazing operation: this operation removes plant biomass at a
specified rate and allows simultaneous application of manure.
BURN burn operation: the burn operation records the biomass,
residue and phosphorus that is burned.
SWEP street sweeping operation: this operation removes sediment
and nutrient build-up on impervious areas in the HRU. This
operation can only be used when the urban build up/wash off
routines are activated for the HRU (see IURBAN).
SKIP skip operation: this operation skips to the end of the year.
For each year of management operations provided, the operations must be listed in chronological
order starting in January.
For simulations where a certain amount of crop yield and biomass is required, the user can force
the model to meet this amount by setting a harvest index target and a biomass target. These targets are
effective only if a harvest and kill operation is used to harvest the crop. Variables are listed below.
SWAT+ INPUTS 181
Variable name Definition
TITLE Title for the management.sch file. Optional (may be
blank)
HEADER Header for the management.sch variables
NAME Name of the operations
NUM_OPS Number of operations following
NUM_AUTOS Number of auto schedule
OP Management operation name:
pcom = plant community
plnt = beginning of growing season
harv = harvests the portion of the plant designated as
yield and removes the yield from the HRU, but allows the
plant to continue to grow.
hvkl = harvests the portion of the plant designated as
yield, removes the yield from the HRU and converts the
remaining plant biomass to residue on the soil surface.
till = mixed the upper soil layers and redistributes the
nutrients/chemicals, etc within thos layers
irrm = applies water to the HRU on the specified day
fert = adds nutrients to the soil in the specified day
pest = applies a pesticide to the plant and/or soil in the
HRU on a specified day
graz = removes plant biomass at a specified rate and
allows simultaneous application of manure
burn = burning
swep = removes sediment and nutrient build up on
impervious areas in the HRU. This operation can only be
used when the urban build up/wash off routines are
activated for the HRU (see IURBAN)
skip
MON Month operation takes place.
Either MONTH/DAY or HUSC is required.
DAY Day operation takes place.
Either MONTH/DAY or HUSC is required.
HUSC Fraction of total base zero heat units at which operation
takes place.
Heat unit scheduling is explained in Chapter 5:1 of the
Theoretical Documentation. If MONTH and DAY are not
provided, HUSC must be set to a value.
Either MONTH/DAY or HUSC is required.
182 SWAT+ INPUT/OUTPUT FILE DOCUMENTATION, VERSION 2016
OP_CHAR Operation type character
OP_PLANT Plant name in community
OP3 Harvest index override
OBJECT.CNT FILE
object.cnt: Spatial object counts – (2-stage)
OBJ HRU LTE SUB MODFL AQU CHA RES REC EXCO DR CANAL PUMP OUT CHDEG 2DAQU
4 1 0 0 0 0 0 0 1 0 0 0 0 1 1 0
HRU.CON FILE
hru.con (2-stage)
NUMB NAME AREA LAT LONG ELEV HRU WST CON_TYP OVERFLOW RULESET OUT_TOT
1 bench 0.480 0.000 0.000 0.000 1 wea1 0 0 0 0
184 SWAT+ INPUT/OUTPUT FILE DOCUMENTATION, VERSION 2016
HRU-DATA.HRU
hru-data.hru: HRU properties – (2-stage)
NUM NAM TOPO HYD SOIL LU_MGT SOLN_INI SURF_STOR SNOW FLD SCH_UPD
1 hru0010104 hru00101 hru0010104 IN025 agriculture IN025 null snow01 null null
CONS_PRACTICE.LUM
Below is a sample CONS_PRACTICE.LUM FILE:
SWAT+ INPUTS 187
cons_practice.lum
NAME P_FACTOR OPE_LEN_MAX DESCRIPTION
up_down_slope 1 121 Up_and_down_slope
cross_slope 0.75 121 Cross_slope_tillage
contour_farming 0.5 121 Contour_tillage
strip_cros_slope 0.37 121 Strip_cropping_cross_slope
strip_contour 0.25 121 Strip_cropping_contour
contour_1-2 0.3 121 Contour_tillage_1-2%_slopes
contour_3-5 0.5 91 Contour_tillage_3-5%_slopes
contour_6-8 0.5 61 Contour_tillage_6-8%_slopes
contour_9-12 0.6 36 Contour_tillage_9-12%_slopes
contour_13-16 0.7 24 Contour_tillage_13-16%_slopes
contour_17-20 0.8 18 Contour_tillage_17-20%_slopes
contour_21-25 0.9 15 Contour_tillage_21-25%_slopes
strip_1-2_past 0.3 244 Strip_cropping_1-2%_slopes_with-pasture
strip_1-2_row 0.6 244 Strip_cropping_1-2$_slopes_with-rowcrops
strip_3-5_past 0.25 183 Strip_cropping_3-5%_slopes_with-pasture
strip_3-5_row 0.5 183 Strip_cropping_3-5%_slopes_with-rowcrops
strip_6-8_past 0.25 122 Strip_cropping_6-8%_slopes_with-pasture
strip_6-8_row 0.5 122 Strip_cropping_6-8%_slopes_with-rowcrops
strip_9-12_past 0.3 73 Strip_cropping_9-12%_slopes_with-pasture
strip_9-12_row 0.6 73 Strip_cropping_9-12%_slopes_with-rowcrops
strip_13-16_past 0.35 49 Strip_cropping_13-16%_slopes_with-pasture
strip_13-16_row 0.7 49 Strip_cropping_13-16%_slopes_with-rowcrops
strip17-20_past 0.4 36 Strip_cropping_17-20%_slopes_with-pasture
strip_17-20_row 0.8 36 Strip_cropping_17-20%_slopes_with-rowcrops
strip_21-25_past 0.45 30 Strip_cropping_21-25%_slopes_with-pasture
strip_21-25_row 0.9 30 Strip_cropping_21-25%_slopes_with-rowcrops
ter_1-2_sodout 0.12 121 terraces_1-2%_slopes_sod-outlet
ter_1-2_undout 0.05 121 terraces_1-2%_slopes_underflow-outlet
ter_3-8_sodout 0.5 76 terraces_3-8%_slopes_sod-outlet
ter_3-8_undout 0.25 76 terraces_3-8%_slopes_underflow--outlet
ter_9-12_sodout 0.6 61 terraces_9-12%_slopes_sod-outlet
ter_9-12_undout 0.3 61 terraces_9-12%_slopes_underflow--outlet
ter_13-16_sodout 0.7 45 terraces_13-16%_slopes_sod-outlet
ter_13-16_undout 0.35 45 terraces_13-16%_slopes_underflow--outlet
ter_17-20_sodout 0.8 45 terraces_17-20%_slopes_sod-outlet
ter_17-20_undout 0.4 45 terraces_17-20%_slopes_underflow--outlet
ter_21-25_sodout 0.9 30 terraces_21-25%_slopes_sod-outlet
ter_21-25_undout 0.45 30 terraces_21-25%_slopes_underflow--outlet
188 SWAT+ INPUT/OUTPUT FILE DOCUMENTATION, VERSION 2016
Variable name Definition
TITLE The first line of the cons_practice.lum file is reserved for
user comments. The comments may take up to 80 spaces.
The title line is not processed by the model and may be left
blank.
HEADER Headings for cons_practice.lum variables
NAME Name of conservation practice
PFAC Usle P factor
SL_LEN_MX Maximum slope length (m)
OVN_TABLE.LUM
ovn_table.lum:
OVN_ID MANN_N MIN MAX DESCRIPTION
fallow_nores 0.01 0.008 0.012 Fallow_no_residue
convtill_nores 0.09 0.06 0.12 Conventional_tillage_no_residue
convtill_res 0.19 0.16 0.22 Conventional_tillage_residue
chisplow_nores 0.09 0.06 0.12 Chisel_plow_no_residue
chisplow_res 0.13 0.1 0.16 Chisel_plow_residue
falldisk_res 0.4 0.3 0.5 Fall_disking_residue
notill_nores 0.07 0.04 0.1 No_till_no_residue
notill_0.5-1res 0.12 0.07 0.17 No_till_0.5-1_t/ha_residue
notill_2-9res 0.3 0.17 0.47 No_till_2-9_t/ha_residue
range_sparse 0.13 0.13 0.13 Rangeland_sparse_cover
range_20cover 0.6 0.6 0.6 Rangeland_20%_cover
shortgrass 0.15 0.1 0.2 Short_grass_prairie
densegrass 0.24 0.17 0.3 Dense_grass
bermudagrass 0.41 0.3 0.48 Bermudagrass
forest_light 0.4 0.3 0.5 Forest_light_fair
forest_med 0.6 0.5 0.7 Forest_medimum_good
forest_heavy 0.8 0.7 0.9 Forest_heavy
urban_asphalt 0.11 0.11 0.11 Urban_asphalt
urban_concrete 0.012 0.012 0.012 Urban_concrete
urban_rubble 0.024 0.024 0.024 Urban_rubble
SWAT+ INPUTS 189
Variable name Definition
TITLE The first line of the ovn_table.lum file is reserved for user
comments. The comments may take up to 80 spaces. The
title line is not processed by the model and may be left
blank.
HEADER Headings for ovn_table.lum variables
NAME Name of conservation practice
OVN Overland flow mannings n – mean
OVN_MIN Overland flow mannings n – min
OVN_MAX Overland flow mannings n - max
CHG – The change section includes the files for soft calibration simulation runs in SWAT+.
CODES.CAL
The CODES.CAL file contains the input variables for the characteristics of the calibration update properties.
Below is a sample CODES.CAL file:
codes.cal
HYD_HRUHYD_HRULTE PLT SED NUT CHSED CHNUT RES
y n n n n n n n
CAL_PARMS.CAL
The CAL_PARMS.CAL file contains the input variables for the characteristics of the calibration update properties.
Below is a sample CAL_PARMS.CAL file:
190 SWAT+ INPUT/OUTPUT FILE DOCUMENTATION, VERSION 2016
cal_parms.upd
187
NAME OBJ_TYP ABSMIN ABSMAX UNITS
cn2 hru 25 98 null
usle_p hru 0 1 null
ovn hru 0.01 30 null
elev hru 0 5000 m
slope hru 0 1 m/m
slope_len hru 10 150 m
lat_ttime hru 0 180 days
lat_sed hru 0 5000 g/L
lat_len hru 0 150 m
CALIBRATION.CAL
The CALIBRATION.CAL file contains the input variables for the characteristics of the calibration update
properties. Below is a sample CALIBRATION.CAL file:
calibratio
8
NAME CHG_TYPE VAL CONDS LYR1 LYR2 YEAR1 YEAR2 DAY1 DAY2 NUM_TOT
k pctchg 25 0 1 1 0 0 0 0 0
k pctchg 20 0 1 2 0 0 0 0 0
k pctchg 20 0 4 6 0 0 0 0 0
k pctchg 27 0 0 0 0 0 0 0 0
k pctchg 25 1 1 2 0 0 0 0 0
hsg = 0 D
k pctchg 25 1 1 1 0 0 0 0 0
texture = 0 fsl
k pctchg 25 2 1 1 0 0 0 0 0
texture = 0 fsl
landuse = 0 past
k pctchg 25 2 1 1 0 0 0 0 6 1 -3 4 -8 12 -18
texture = 0 FSL
landuse = 0 past
SWAT+ INPUTS 191
Variable name Definition
TITLE The first line of the calibration.cal file is reserved for user
comments. The comments may take up to 80 spaces. The
title line is not processed by the model and may be left blank.
MCAL Total number of calibration updates in the file
NAME Name of SWAT+ variable (NAME column from
cal_parms.upd file)
CHG_TYPE Type of change (‘absval’, ‘abschg’, ‘pctchg’)
VAL Value of change
CONDS Number of conditions in following lines
LYR1 First layer in range for soil variables (input == 0 assumes all
layers)
LYR2 Last layer in range for soil variables
YEAR1 First year of update (for precip and temp)
YEAR2 Last year of update (for precip and temp)
DAY1 First day in range (for precip and temp)
DAY2 Last day in range (for precip and temp)
NUM_TOT Total number of objects to follow
ELEM_CNT1 Number of elements modified
192 SWAT+ INPUT/OUTPUT FILE DOCUMENTATION, VERSION 2016
LS_PARMS.CAL
The LS_PARMS.CAL file contains the input variables for the characteristics of the calibration parameter
properties. Below is a sample LS_PARMS.CAL file:
ls_parms.cal
10
NAME CHG_TYP NEG POS LO UP
cn2 abschg -8 8 0 0
esco absval 0 1 0 0
k pctchg -30 30 0 0
k_lo pctchg -99 30 0 0
slope pctchg -25 25 0 0
tconc pctchg -30 30 0 0
etco absval 0.8 1.2 0 0
perco absval -0.99 10 0 0
revapc absval 0 0.4 0 0
cn3_swf abschg 0 1 0 0
LS_REGIONS.CAL
The LS_REGIONS.CAL file contains the input variables for the characteristics of land use regions parameter
properties for HRUs. Below is a sample LS_REGIONS.CAL file:
SWAT+ INPUTS 193
ls_regions.cal
1
NAME LUM_NUM NPSU ELEM_CNT
region_1 15 0
NAME SRR ETR TFR SED ORGN ORGP NO3 SOLP
landuse001 0.1 0.7 0 3 0 0 0 0
landuse002 0.1 0.7 0 3 0 0 0 0
landuse003 0.1 0.7 0 3 0 0 0 0
landuse004 0.1 0.7 0 3 0 0 0 0
landuse005 0.1 0.7 0 3 0 0 0 0
landuse006 0.1 0.7 0 3 0 0 0 0
corn_noprac 0.15 0.7 0 3 0 0 0 0
corn_conprac 0.15 0.7 0 3 0 0 0 0
oats_noprac 0.15 0.7 0 3 0 0 0 0
oats_conprac 0.1 0.7 0 3 0 0 0 0
past_noprac 0.1 0.7 0 3 0 0 0 0
past_conprac 0.1 0.7 0 3 0 0 0 0
forest_graze 0.1 0.7 0 3 0 0 0 0
forest_congraze 0.1 0.7 0 3 0 0 0 0
farmstead 0.15 0.7 0 3 0 0 0 0
194 SWAT+ INPUT/OUTPUT FILE DOCUMENTATION, VERSION 2016
Variable name Definition
TITLE The first line of the ls_regions.cal file is reserved for user
comments. The comments may take up to 80 spaces. The
title line is not processed by the model and may be left blank.
MLSCAL Total number of regions updates in the file
NAME Regions calibration name
LUM_NUM Total number of land use regions in following lines
NUM_REG The number of elements in following lines
REG Elements count
NAME2 Name of the land use management regions
SRR Surface runoff ratio – surface runoff/precip
LFR Lateral flow ratio – soil lat flow/precip
PCR Percolation ratio – perc/precip
ETR ET ratio – ET/precip
TFR Tile flow ratio – tile flow/total runoff
SED Sediment yield (t/ha or t)
ORGN Organic N yield (kg/ha or kg)
ORGP Organic P yield (kg/ha or kg)
NO3 Nitrate yield (kg/ha or kg)
SOLP Soluble P yield (kg/ha or kg)
CH_ORDERS.CAL
The CH_ORDERS.CAL file contains the input variables for the characteristics of channel orders parameter
properties for
SWAT HRUs. Below is a sample CH_ORDERS.CAL file:
chan_orders.cal
1
NAME ORD_NUM NPSU ELEM_CNT
region_1 8 0
ORDER CHW CHD FPD
gully 100 100 0.0
tributary 25 10 0.0
main_upper_c 10 10 0.0
main_lower_c 5 5 0.0
gully_c 0 0 0.0
tributary_c 1 1 0.0
main_upper_c 1 1 0.0
main_lower_c 0.58 0 0.0
SWAT+ INPUTS 195
CH_PARMS.CAL
The CH_PARMS.CAL file contains the input variables for the characteristics of land use parameter properties for
SWAT HRUs. Below is a sample CH_PARMS.CAL file:
INIT – The initial files includes initialization data for pesticide and plants.
196 SWAT+ INPUT/OUTPUT FILE DOCUMENTATION, VERSION 2016
PLANT.INI
The PLANT.INI file contains the input variables for the characteristics of the plant community properties. Below
is a sample PLANT.INI file:
plant.ini
NAME LANTS_COM CPNM IGRO LAI BIOMS PHUACC POP YRMAT RSDIN
frst_mixed 1
frst y 0 0 0 0 0 10000
pasture 1 1
past n 0 0 0 0 0 3000
agriculture_land_gen 1 1
agrl n 0 0 0 0 0 1000
urban_residential 1 1
berm n 0 0 0 0 0 3000
corn_soybean 2 2
corn n 0 0 0 0 0 2000
soyb n 0 0 0 0 0 2000
ryegrass 1 1
ryeg y 0 500 0 0 0 2000
canary_grass 1 1
cana y 0 500 0 0 0 2000
SWAT+ INPUTS 197
Variable name Definition
TITLE The first line of the file is reserved for user comments. The
comments may take up to 80 spaces. The title line is not
processed by the model and may be left blank.
HEADER Headings for the variables
NAME Name of plant community
NUMB Number of plants in this community
NAME2 Name of plant in this community
PLANTS_COM Number of plants in the community
SOIL_PLANT.INI
The SOIL_PLANT.INI file contains the input variables for the characteristics of the pesticide properties. Below is
a sample SOIL_PLANT.INI file:
soil_plant.ini
NAME SW_FRAC NUTRIENT PESTICIDES PATHOGENS HEAVY_METALS SALTS
no_init 0.2 in25 no_ini no_ini null null
low_init 0.7 in25 low_ini low_ini null null
PEST_WATER.INI
PATH_WATER.INI
HMET_SOIL.INI
SALT_SOIL.INI
SOILS – The soils data used by SWAT+ can be divided into two groups, physical
characteristics and chemical characteristics. The physical properties of the soil govern the
movement of water and air through the profile and have a major impact on the cycling of water
within the HRU. Inputs for chemical characteristics are used to set initial levels of the different
chemicals in the soil. While the physical properties are required, information on chemical
properties is optional. The soil input (.sol) file defines the physical properties for all layers in
the soil.
SOILS.SOL
The SOILS.SOL file contains the input variables for the characteristics of the soil properties. Below is a partial
sample SOILS.SOL file (four layer soil):
soils.sol
SNAM NLY HYD_GRP ZMX ANION_EXCRK TEXTURE DEPTH BD AWC K CBN CLAY SILT SAND ROCK ALB USLE_K EC CAL PH
IN025 4B 1524 0.5 0.5 sandy-loam
355.6 1.6 0.13 83 1.74 15 19.09 65.91 1.52 0.01 0.2 0 0 0
812.8 1.7 0.1 65 0.35 12.5 19.65 67.85 1.62 0.12 0.2 0 0 0
1219.2 1.8 0.07 180 0.15 7.5 9.02 83.48 1.71 0.17 0.15 0 0 0
1524 1.8 0.04 300 0.05 6 1.88 92.11 1.71 0.21 0.15 0 0 0
202 SWAT+ INPUT/OUTPUT FILE DOCUMENTATION, VERSION 2016
TITLE The first line of the .sol file is reserved for user comments.
The comments may take up to 80 spaces. The title line is
not processed by the model and may be left blank.
HEADER
SNAM Soil name
NLY Number of layers in the soil
HYDGRP Soil hydrologic group (A, B, C, or D).
Required only for the SWAT ArcView interface.
The U.S. Natural Resource Conservation Service (NRCS)
classifies soils into four hydrologic groups based on
infiltration characteristics of the soils. NRCS Soil Survey
Staff (1996) defines a hydrologic group as a group of soils
having similar runoff potential under similar storm and
cover conditions. Soil properties that influence runoff
potential are those that impact the minimum rate of
infiltration for a bare soil after prolonged wetting and when
not frozen. These properties are depth to seasonally high
water table, saturated hydraulic conductivity, and depth to
a very slowly permeable layer. The definitions for the
different classes are:
A Soils having high infiltration rates even when
thoroughly wetted, consisting chiefly of sands or
gravel that are deep and well to excessively drained.
These soils have a high rate of water transmission (low
runoff potential).
B Soils having moderate infiltration rates when
thoroughly wetted, chiefly moderately deep to deep,
moderately well to well drained, with moderately fine
to moderately coarse textures. These soils have a
moderate rate of water transmission.
SWAT+ INPUTS 203
Variable name Definition
HYDGRP, cont. C Soils having slow infiltration rates when thoroughly
wetted, chiefly with a layer that impedes the
downward movement of water or of moderately fine
to fine texture and a slow infiltration rate. These soils
have a slow rate of water transmission (high runoff
potential).
D Soils having very slow infiltration rates when
thoroughly wetted, chiefly clay soils with a high
swelling potential; soils with a high permanent water
table; soils with a clay pan or clay layer at or near the
surface; and shallow soils over nearly impervious
materials. These soils have a very slow rate of water
transmission.
Permeability is defined as the capacity of the soil to transmit water and air through
the most restricted horizon (layer) when moist. The profile permeability classes
are based on the lowest saturated hydraulic conductivity in the profile. The codes
assigned to cperm are:
7 rapid (> 150 mm/hr)
8 moderate to rapid (50-150 mm/hr)
9 moderate (15-50 mm/hr)
10 slow to moderate (5-15 mm/hr)
11 slow (1-5 mm/hr)
12 very slow (< 1 mm/hr)
f cl − si =
mc + msilt
0.0256 ⋅ orgC
f orgc = 1 −
orgC + exp[3.72 − 2.95 ⋅ orgC ]
m
0.7 ⋅ 1 − s
100
f hisand = 1 −
m m
1 − s + exp − 5.51 + 22.9 ⋅ 1 − s
100 100
where ms is the percent sand content (0.05-2.00 mm diameter particles), msilt is the
percent silt content (0.002-0.05 mm diameter particles), mc is the percent clay
content (< 0.002 mm diameter particles), and orgC is the percent organic carbon
content of the layer (%).
EC(layer #) Electrical conductivity (dS/m).
CAL(layer #) Soil CaCo3 (%). (0 – 50%)
PH(layer #) Soil Ph (3-10)
NUTRIENTS.SOL
The NUTRIENTS.SOL file Soil nutrient parameters.
Below is a sample NUTRIENTS.SOL file:
nutrients.sol:
NAME EXP_CO TOTALN INORGN ORGN TOTALP INORGP ORGP WATERSOL_P H3A_P MEHLICH_P BRAY_STRONG_
lrew01 0.001 13 6.85 3.34 3.22 3.66 0.39 0.16 0.26 1.22 0.85
lrew02 0.001 13 6.85 3.34 3.22 3.66 0.39 0.16 0.26 1.22 0.85
lrew03 0.001 13 6.85 3.34 3.22 3.66 0.39 0.16 0.26 1.22 0.85
lrew04 0.001 13 6.85 3.34 3.22 3.66 0.39 0.16 0.26 1.22 0.85
lrew05 0.001 13 6.85 3.34 3.22 3.66 0.39 0.16 0.26 1.22 0.85
lrew06 0.001 13 6.85 3.34 3.22 3.66 0.39 0.16 0.26 1.22 0.85
lrew07 0.001 13 6.85 3.34 3.22 3.66 0.39 0.16 0.26 1.22 0.85
lrew08 0.001 13 6.85 3.34 3.22 3.66 0.39 0.16 0.26 1.22 0.85
lrew09 0.001 13 6.85 3.34 3.22 3.66 0.39 0.16 0.26 1.22 0.85
lrew10 0.001 13 6.85 3.34 3.22 3.66 0.39 0.16 0.26 1.22 0.85
lrew11 0.001 13 6.85 3.34 3.22 3.66 0.39 0.16 0.26 1.22 0.85
lrew12 0.001 13 6.85 3.34 3.22 3.66 0.39 0.16 0.26 1.22 0.85
SWAT+ INPUTS 211
TITLE The first line of the nutrients.sol file is reserved for user
comments. The comments may take up to 80 spaces. The
title line is not processed by the model and may be left
blank.
HEADER
NAME Nutrient name
EXP_CO Depth coefficient to adjust concentrations for depth
TOTALN Total N in soil (ppm)
INORGN Inorganic N in soil surface (ppm)
ORGN Organic N in soil surface (ppm)
TOTALP Total P in soil surface (ppm)
INORGP Inorganic P in soil surface (ppm)
ORGP Organic P in soil surface (ppm)
WATERSOL_P Water soluble P in soil surface (ppm)
H3A_P H3a P in soil surface (ppm)
MEHLICH_P Mehlich P in soil surface (ppm)
BRAY_STRONG_P Bray P in soil surface (ppm)
D_TABLE – Decision tables are a precise yet compact way to model complex rule sets and their
corresponding actions.
Decision tables, like flowcharts and if-then-else and switch-case statements, associate conditions with actions to
perform, but in many cases do so in a more elegant way (see Wikipedia – ‘Decision table’)
STRUCTURE OF DECISION TABLES
I. Conditions
II. Condition alternatives
III. Actions
IV. Action entries
Each decision corresponds to a variable, relation or predicate whose possible values are listed among the
condition alternatives. Each action is a procedure or operation to perform, and the entries specify whether (or in
what order) the action is to be performed for the set of condition alternatives the entry corresponds to. Many
decision tables include in their condition alternatives the ‘don’t care’ symbol, a hyphen. Using ‘don’t cares’ can
simply decision tables, especially when a given condition has little influence on the actions to be performed. In
some cases, entire conditions thought to be important initially are found to be irrelevant when none of the
conditions influence which actions are performed.
Decision tables, especially when coupled with the use of a domain-specific language, allow developers and
policy experts to work from the same information, the decision tables themselves.
212 SWAT+ INPUT/OUTPUT FILE DOCUMENTATION, VERSION 2016
Tools to render nested if statements from traditional programming languages into decision tables can also be
used as a debugging tool.
Decision tables have proven to be easier to understand and review than code, and have been used extensively
and successfully to produce specifications for complex systems.
d_table.dtl
2
REGIONS–
LS_UNIT.ELE
The LS_UNIT.ELE file contains the input variables
Below is a sample LS_UNIT.ELE:
SWAT+ INPUTS 215
ls_unit.ele:
NUMB NAME OBTYP OBTYPNO BSN_FRAC LSU_FRAC REG_FRAC
1 hru1 hru 1 0.00026108 0.0817 0
2 hru2 hru 2 1.67E-05 0.0052 0
3 hru3 hru 3 0.00153037 0.4791 0
4 hru4 hru 4 8.33E-06 0.0026 0
5 hru5 hru 5 5.00E-05 0.0157 0
6 hru6 hru 6 3.61E-05 0.0113 0
7 hru7 hru 7 5.55E-06 0.0017 0
8 hru8 hru 8 0.00012221 0.0383 0
9 hru9 hru 9 7.50E-05 0.0235 0
10 hru10 hru 10 0.00012221 0.0383 0
11 hru11 hru 11 9.44E-05 0.0296 0
12 hru12 hru 12 0.00027497 0.0861 0
13 hru13 hru 13 0.00016665 0.0522 0
14 hru14 hru 14 0.0001472 0.0461 0
LS_UNIT.DEF
The LS_UNIT.DEF file contains the input variables. Below is a sample LS_UNIT.DEF:
216 SWAT+ INPUT/OUTPUT FILE DOCUMENTATION, VERSION 2016
ls_unit.def
LSU_NUMB LSU_NAME LSU_AREA ELEM_TOT ELEM1 ELEM2
1 lcu1 103.5 2 1 -21
2 lcu2 6.21 2 22 -28
3 lcu3 61.92 2 29 -39
4 lcu4 3.06 2 40 -42
5 lcu5 73.8 2 43 -62
6 lcu6 2.07 2 63 -67
7 lcu7 63.36 2 68 -87
8 lcu8 3.42 2 88 -92
9 lcu9 78.57 2 93 -111
10 lcu10 3.33 2 112 -118
11 lcu11 66.51 2 119 -139
12 lcu12 0.72 2 140 -143
13 lcu13 83.25 2 144 -164
14 lcu14 5.04 2 165 -174
Variable Definition
name
TITLE Description of the LS_UNIT.DEF file
MLSU Number of regions
HEADER
NUMB The sequential number of the LS_UNIT.DEF
NAME
AREA Surface area
NSPU Total number of elements to follow
ELEM_CNT Element counts
Variable Definition
name
SWAT+ INPUTS 217
TITLE Description of the LS_REG.DEF file
MREG Number of regions
MLUG Number of landuse groups
HEADER
NUMB The sequential number of the LS_REG.DEF
NAME
AREA_HA Surface area
NSPU
ELEM_CNT
CH_CATUNIT.DEF
The CH_CATUNIT.DEF file contains the input variables
Below is a sample CH_CATUNIT.DEF
Ch_catunit.def Subbasin
2
NUMB NAME AREA_HA NSPU ELEM1 ELEM2
1 lcu1 493.38 1 1 2
Variable Definition
name
TITLE Description of the CH_CATUNIT.DEF file
MREG Number of regions
HEADER
NUMB The sequential number of the CH_CATUNIT.DEF
NAME
AREA_HA Surface area
NSPU
ELEM_CNT
CH_REG.DEF
The CH_REG.DEF file contains the input variables
Below is a sample CH_REG.DEF
TITLE Description of the CH_REG.DEF file
MREG Number of regions
HEADER
NUMB The sequential number of the CH_REG.DEF
NAME
AREA_HA Surface area
218 SWAT+ INPUT/OUTPUT FILE DOCUMENTATION, VERSION 2016
NSPU
ELEM_CNT
AQU_CATUNIT.ELE
The AQU_CATUNIT.ELE file contains the input variables
Below is a sample AQU_CATTUNIT.ELE
Aqu_catunit.ele
NUMB NAME OBTYP OBTYPNO BSN_FRAC SUB_FRAC REG_FRAC
1 hru1 hru 1 0.500 0.5 0
2 hru2 hru 2 0.500 0.5 0
AQU_CATUNIT.DEF
The AQU_CATUNIT.DEF file contains the input variables
Below is a sample AQU_CATUNIT.DEF
Aqu_catunit.def Subbasin
2
NUMB NAME AREA_HA NSPU ELEM1 ELEM2
1 lcu1 493.38 1 1 2
AQU_REG.DEF
The AQU_REG.DEF file contains the input variables
Below is a sample AQU_REG.DEF
aqu_reg.def Subbasin
2
NUMB NAME AREA_HA NSPU ELEM1 ELEM2
1 lcu1 493.38 1 1 2
Variable Definition
name
TITLE Description of the AQU_REG.DEF file
MREG Number of regions
HEADER
NUMB The sequential number of the AQU_REG.DEF
NAME
AREA_HA Surface area
NSPU
ELEM_CNT
RES_CATUNIT.ELE
The RES_CATUNIT.ELE file contains the input variables
Below is a sample RES_CATTUNIT.ELE
res_catunit.ele
NUMB NAME OBTYP OBTYPNO BSN_FRAC SUB_FRAC REG_FRAC
1 hru1 hru 1 0.500 0.5 0
2 hru2 hru 2 0.500 0.5 0
Variable Definition
name
TITLE Description of the RES_REG.DEF file
MREG Number of regions
HEADER
NUMB The sequential number of the RES_REG.DEF
NAME
AREA_HA Surface area
NSPU
ELEM_CNT
RES_CATUNIT.DEF
The RES_CATUNIT.DEF file contains the input variables
Below is a sample RES_CATUNIT.DEF
res_catunit.def Subbasin
2
NUMB NAME AREA_HA NSPU ELEM1 ELEM2
1 lcu1 493.38 1 1 2
REC_CATUNIT.ELE
The REC_CATUNIT.ELE file contains the input variables
Below is a sample REC_CATTUNIT.ELE
rec_catunit.ele
NUMB NAME OBTYP OBTYPNO BSN_FRAC SUB_FRAC REG_FRAC
1 hru1 hru 1 0.500 0.5 0
SWAT+ INPUTS 221
2 hru2 hru 2 0.500 0.5 0
REC_CATUNIT.DEF
The REC_CATUNIT.DEF file contains the input variables
Below is a sample REC_CATUNIT.DEF
rec_catunit.def Subbasin
2
NUMB NAME AREA_HA NSPU ELEM1 ELEM2
1 lcu1 493.38 1 1 2
REC_REG.DEF
The REC_REG.DEF file contains the input variables
Below is a sample REC_REG.DEF
rec_reg.def Subbasin
2
NUMB NAME AREA_HA NSPU ELEM1 ELEM2
1 lcu1 493.38 1 1 2
222 SWAT+ INPUT/OUTPUT FILE DOCUMENTATION, VERSION 2016
Variable Definition
name
TITLE Description of the REC_REG.DEF file
MREG Number of regions
HEADER
NUMB The sequential number of the REC_REG.DEF
NAME
AREA_HA Surface area
NSPU
ELEM_CNT
PATH_PCP/PATH_TMP/PATH_SLR/PATH_HMD/PATH_WND
The PATH weather files contain the daily values for the simulation run. The data files can be present in the same
directory as the other input data OR in a separate sub-directory. If they are copied to a sub-directory, the following
should be input so the model will read from the files during runtime.
In the following example, the data directory is: c:\LREW and the weather will be read from c:\LREW\weather.