VERSION 2000

S.L. NEITSCH, J.G. ARNOLD, J.R. KINIRY, R. SRINIVASAN, J.R. WILLIAMS 2002

GRASSLAND, SOIL AND WATER RESEARCH LABORATORY AGRICULTURAL RESEARCH SERVICE 808 EAST BLACKLAND ROAD TEMPLE, TEXAS 76502 BLACKLAND RESEARCH CENTER TEXAS AGRICULTURAL EXPERIMENT STATION 720 EAST BLACKLAND ROAD TEMPLE, TEXAS 76502

Grassland, Soil & Water Research Laboratory, Temple, Texas GSWRL Report 02-02

Blackland Research and Extension Center, Temple, Texas BRC Report 02-06

Published 2002 by Texas Water Resources Institute, College Station, Texas TWRI Report TR-192

CONTENTS

CHAPTER 1 OVERVIEW
1.1 WATERSHED CONFIGURATION
SUBBASINS HYDROLOGIC RESPONSE UNITS REACH/MAIN CHANNELS TRIBUTARY CHANNELS PONDS/WETLANDS/RESERVOIRS POINT SOURCES

1.2 1.3

OVERVIEW OF INPUT FILES MODEL INPUTS BY TYPE

1 2 2 2 4 4 4 5 6 9

CHAPTER 2 SWAT INPUT: WATERSHED CONFIGURATION

2.1 2.2 DISCRETIZATION SCHEMES WATERSHED CONFIGURATION FILE (.FIG) INCORPORATION OF COMMENTS COMMAND LINES REFERENCES

2.3

29 30 30 31 31 48

CHAPTER 3 SWAT INPUT: FILE.CIO

3.1 3.2 3.3 3.4 TITLE SECTION GENERAL INPUT/OUTPUT SECTION CLIMATE INPUT SECTION SUBBASIN SECTION

49 50 51 52 54

CHAPTER 4 SWAT INPUT: .COD CHAPTER 5 SWAT INPUT: .BSN CHAPTER 6 SWAT INPUT: .SUB CHAPTER 7 SWAT INPUT: .PCP
6.1 6.2 DAILY PRECIPITATION DATA SUB-DAILY PRECIPITATION DATA

59

73

91

101 102 104

CHAPTER 8 SWAT INPUT: .TMP CHAPTER 9 SWAT INPUT: .SLR CHAPTER 10 SWAT INPUT: .WND

109

113

115

CHAPTER 11 SWAT INPUT: .HMD CHAPTER 12 SWAT INPUT: .PET CHAPTER 13 SWAT INPUT: .WGN CHAPTER 14 SWAT INPUT: CROP.DAT CHAPTER 15 SWAT INPUT: TILL.DAT CHAPTER 16 SWAT INPUT: PEST.DAT CHAPTER 17 SWAT INPUT: FERT.DAT CHAPTER 18 SWAT INPUT: URBAN.DAT CHAPTER 19 SWAT INPUT: .HRU

119

123

125

137

157

159

163

167

171

CHAPTER 20 SWAT INPUT: .MGT

20.1 GENERAL MANAGEMENT VARIABLES 20.2 SCHEDULED MANAGEMENT OPERATIONS PLANTING/BEGINNING OF GROWING SEASON IRRIGATION OPERATION FERTILIZER APPLICATION PESTICIDE APPLICATION HARVEST & KILL OPERATION TILLAGE OPERATION HARVEST OPERATION KILL OPERATION GRAZING OPERATION AUTO IRRIGATION INITIALIZATION AUTO FERTILIZER INITIALIZATION STREET SWEEPING OPERATION RELEASE/IMPOUND OPERATION END OF YEAR OPERATION

185 186 193 195 198 200 202 203 204 206 208 209 211 212 215 218 219

CHAPTER 21 SWAT INPUT: .WUS CHAPTER 22 SWAT INPUT: .SOL CHAPTER 23 SWAT INPUT: .CHM CHAPTER 24 SWAT INPUT: .GW CHAPTER 25 SWAT INPUT: .RTE

221

227

241

247

253

CHAPTER 26 SWAT INPUT: .WWQ CHAPTER 27 SWAT INPUT: .SWQ CHAPTER 28 SWAT INPUT: .PND CHAPTER 29 SWAT INPUT: .RES
29.1 RESERVOIR INPUT FILE (.RES) 29.2 DAILY RESERVOIR OUTFLOW FILE 29.3 MONTHLY RESERVOIR OUTFLOW FILE

261

269

279

287 288 293 294

CHAPTER 30 SWAT INPUT: .LWQ CHAPTER 31 SWAT INPUT: MEASURED

31.1 31.2 31.3 31.4 DAILY RECORDS (RECDAY) DATA FILE MONTHLY RECORDS (RECMON) DATA FILE ANNUAL RECORDS (RECYEAR) DATA FILE AVERAGE ANNUAL RECORDS (RECCNST) DATA FILE

295

303 304 306 309 311

CHAPTER 32 SWAT OUTPUT FILES

32.1 32.2 32.3 32.4 32.5 32.6 32.7 INPUT SUMMARY FILE (INPUT.STD) STANDARD OUTPUT FILE (OUTPUT.STD) HRU OUTPUT FILE (.SBS) SUBBASIN OUTPUT FILE (.BSB) MAIN CHANNEL OUTPUT FILE (.RCH) HRU IMPOUNDMENT OUTPUT FILE (.WTR) RESERVOIR OUTPUT FILE (.RSV)

313 314 314 315 323 326 331 336

CHAPTER 33 SWAT OUTPUT ANALYSIS

33.1 33.2 33.3 33.4 STREAM FLOW CALIBRATION SEDIMENT CALIBRATION NUTRIENT CALIBRATION CALIBRATION TECHNIQUES

341

APPENDIX A MODEL DATABASES

A.1 A.2 A.3 A.4 A.5 A.6 LAND COVER/PLANT GROWTH DATABASE TILLAGE DATABASE PESTICIDE DATABASE FERTILIZER DATABASE URBAN LAND TYPE DATABASE REFERENCES

355 356 386 389 397 401 406

APPENDIX B EXAMPLE WATERSHED CONFIGURATIONS

B.1 SUBWATERSHED DISCRETIZATION SUBWATERSHED DISCRETIZATION: 3 SUBBASINS SUBWATERSHED DISCRETIZATION: SAVING RESULTS FOR DOWNSTREAM RUNS SUBWATERSHED DISCRETIZATION: INCORPORATING POINT SOURCE/UPSTREAM SIMULATION DATA

413

B.2

B.3

SUBWATERSHED DISCRETIZATION: INCORPORATING RESERVOIRS SUBWATERSHED DISCRETIZATION: SAVING SIMULATION RESULTS FOR ONE LOCATION HILLSLOPE DISCRETIZATION HILLSLOPE DISCRETIZATION: MODELING A DAIRY OPERATION HILLSLOPE DISCRETIZATION: COMBINING WITH SUBWATERSHED DISCRETIZATION GRID CELL DISCRETIZATION GRID CELL DISCRETIZATION: 9 CELLS

CHAPTER 1

SWAT INPUT DATA:

OVERVIEW

SWAT is a comprehensive model that requires a diversity of information in order to run. Novice users may feel a little overwhelmed by the variety and number of inputs when they first begin to use the model. However, many of the inputs are used to simulate special features that are not common to all watersheds. This chapter provides an overview of model inputs. The inputs are organized by topic and emphasis is given to differentiating required inputs from optional inputs. This chapter focuses on assisting the user in identifying inputs that must be defined for their particular dataset. The remaining chapters list variables by file and discuss methods used to measure or calculate values for the input parameters.

SWAT USERS MANUAL, VERSION 2000

1.1 WATERSHED CONFIGURATION

The first step in setting up a watershed simulation is to partition the watershed into subunits. SWAT allows several different subunits or objects to be defined within a watershed. Subbasins unlimited number of HRUs (1 per subbasin required) one pond (optional) one wetland (optional) Reach/main channel segments (1 per subbasin) Impoundments on main channel network (optional) Point sources (optional)

1.1.1 SUBBASINS
The first level of subdivision is the subbasin. Subbasins possess a geographic position in the watershed and are spatially related to one another, e.g. outflow from subbasin #5 enters subbasin #7. The subbasin delineation may be obtained from subwatershed boundaries that are defined by surface topography so that the entire area within a subbasin flows to the subbasin outlet. Alternatively, the subbasin delineation may be obtained from grid cell boundaries. Since most spatial input is grid-based (i.e. DEM, NEXRAD, LULC), grid cells are an appealing approach for subbasin delineation. However unlike the subwatershed discretization, grid cells do not preserve routing reaches and topographic flow paths. A subbasin will contain at least one HRU, a tributary channel and a main channel or reach. Two types of impoundments, a pond and/or wetland, may also be defined in a subbasin. These features are reviewed in the following sections.

1.1.2 HYDROLOGIC RESPONSE UNITS

The land area in a subbasin may be divided into hydrologic response units (HRUs). Hydrologic response units are portions of a subbasin that possess unique landuse/management/soil attributes. HRUs were incorporated into SWAT as part of the HUMUS (Hydrologic Unit Model for the United States) project. HUMUS used U.S.G.S. 2-digit hydrologic boundaries to divide the contiguous United

CHAPTER 1: SWAT INPUTOVERVIEW

States into watersheds while 8-digit hydrologic boundaries were used to define subbasins within the watersheds. Only percentages of soil and landuse were known within the 8-digit hydrologic units. The geographic location of the landuse and soils within each subbasin was unknown. To capture the diversity of land use and soils that could be encompassed in an 8-digit hydrologic unit, a method was needed to account for the complexity of the landscape within the boundaries of the subbasins. The inclusion of HRUs allowed SWAT to account for this diversity. Prior to the HUMUS project, only one landuse/management/soil combination could be defined per subbasin in SWAT. An HRU is not synonymous to a field. Rather it is the total area in the subbasin with a particular landuse, management and soil. While individual fields with a specific landuse, management and soil may be scattered throughout a subbasin, these areas are lumped together to form one HRU. HRUs are used in most SWAT runs since they simplify a run by lumping all similar soil and land use areas into a single response unit. It is often not practical to simulate individual fields. Implicit in the concept of the HRU is the assumption that there is no interaction between HRUs in one subbasin. Loadings (runoff with sediment, nutrients, etc. transported by the runoff) from each HRU are calculated separately and then summed together to determine the total loadings from the subbasin. If the interaction of one landuse area with another is important, rather than defining those landuse areas as HRUs they should be defined as subbasins. It is only at the subbasin level that spatial relationships can be specified. The benefit of HRUs is the increase in accuracy it adds to the prediction of loadings from the subbasin. The growth and development of plants can differ greatly among species. When the diversity in plant cover within a subbasin is accounted for, the net amount of runoff entering the main channel from the subbasin will be much more accurate. As a general rule, a given subbasin should have 1-10 HRUs. For those wishing to incorporate more complexity into a dataset, we would recommend that

SWAT USERS MANUAL, VERSION 2000

the user define a greater number of subbasins in the watershed rather than many HRUs within a few subbasins. Of course, there are exceptions to this rule. An example of such an exception would be the requirement that the project uses a particular subbasin delineation that doesnt allow the user to capture landuse diversity without the incorporation of many HRUs.

1.1.3 REACH/MAIN CHANNELS

One reach or main channel is associated with each subbasin in a watershed. Loadings from the subbasin enter the channel network of the watershed in the associated reach segment. Outflow from the upstream reach segment(s) will also enter the reach segment. Processes involved in routing water, sediment and other constituents through the reach are reviewed in Section 7 of the theoretical documentation.

1.1.4 TRIBUTARY CHANNELS

The term tributary channel is used to differentiate inputs for channelized flow of surface runoff generated in a subbasin. Tributary channel inputs are used to calculate the time of concentration for channelized flow of runoff generated within the subbasin and transmission losses from runoff as it flows to the main channel. Tributary channel inputs define the longest flow path in the subbasin. For some subbasins, the main channel may be the longest flow path. If so, tributary channel dimensions will be the same as those for the main channel. In other subbasins, the tributary channel dimensions will be significantly different than the main channel.

1.1.5 PONDS/WETLANDS/RESERVOIRS
In order to process USGS landuse maps, the GIS interfaces will allow HRUs to be created with water as the land use. If at all possible this should be avoided. Water bodies within a watershed should be modeled as ponds, wetlands or reservoirs.

CHAPTER 1: SWAT INPUTOVERVIEW

Water bodies located on the stream network of the watershed are modeled as reservoirs. While the term reservoir is commonly used for man-made structures and lake for naturally occurring water bodies, the use of the term reservoir in SWAT is not meant to imply that the water body is man-made. With the terms reservoir and pond we are differentiating impoundments by location. Because impoundments on the main channel network tend to be larger than impoundments off the main channel network, a difference in size is also implied with the use of these terms. It would probably be more appropriate to refer to the different types of water bodies as main channel impoundments and subbasin impoundments, but the need for different file extensions to store inputs makes the use of these two terms convenient. Two water bodies (pond/wetlands) may be defined in each subbasin. Water entering these impoundments is generated within the subbasinthey cannot receive water originating in other subbasins. In contrast, reservoirs receive water contributed to the channel network from all upstream subbasins.

1.1.6 POINT SOURCES

SWAT directly models the loading of water, sediment and nutrients from land areas in a watershed. However, some watersheds will have loadings to the stream network from sources not associated with a land area. These are referred to as point sources. The most common point source is a sewage treatment plant. In order to account for the loadings from a point source, SWAT allows users to add daily or average daily loading data for point sources to the main channel network. These loadings are then routed through the channel network along with the loadings generated by the land areas.

With the GIS interfaces, the interface produces a map of the subbasins which allows the user to easily see the spatial relationship between subbasins. In the Windows (non-GIS) interface, the user can set up the spatial positioning of subbasins with drag and drop objects and connecting arrows to show direction of flow. The core SWAT program is not able to access maps or displays. Instead, it

SWAT USERS MANUAL, VERSION 2000

uses the information provided in the watershed configuration file (.fig) to link the individual subbasins together in the watershed. The watershed file is an ASCII or text file. The file format is described in Chapter 2 and example watershed configurations are provided in Appendix B.

1.2 OVERVIEW OF INPUT FILES

Input for SWAT is defined at one of several different levels of detail: watershed, subbasin, or HRU. Unique features such as reservoirs or point sources must have input data provided for each individual feature included in the watershed simulation. Watershed level inputs are used to model processed throughout the watershed. For example, the method selected to model potential

evapotranspiration will be used in all HRUs in the watershed. Subbasin level inputs are inputs set at the same value for all HRUs in the subbasin if the input pertains to a process modeled in the HRU. Because there is one reach per subbasin, input data for main channels is defined at the subbasin level also. An example of subbasin level data is rainfall and temperature information. The same rainfall and maximum and minimum temperature are used for all HRUs, the main channel and any ponds or wetlands located within the subbasin. HRU level inputs are inputs that can be set to unique values for each HRU in the watershed. An example of an HRU input is the management scenario simulated in an HRU. An attempt was been made to organize input information according to the type of input. However, there are a few files that have had to serve as catch-alls. These files contain input data for various processes modeled in the watershed that do not fit into any of the specialized files.

Input files for SWAT include: .fig

(watershed level file)

file.cio
(watershed level file)

Watershed configuration file. This required file defines the routing network in the watershed. Control input/output file. This required file contains names of input files for all watershed level variables and subbasin level variables.

CHAPTER 1: SWAT INPUTOVERVIEW

.cod
(watershed level file)

.bsn
(watershed level file)

.pcp
(watershed level file)

.tmp
(watershed level file)

.slr
(watershed level file)

.wnd
(watershed level file)

.hmd
(watershed level file)

.pet
(watershed level file)

crop.dat
(watershed level file)

till.dat
(watershed level file)

Input control code file. This required file specifies the length of the simulation, the printing frequency, and selected options for various processes. Basin input file. Required file for watershed level parameters. Catch-all file. Precipitation input file. This optional file contains daily measured precipitation for a measuring gage(s). Up to 18 precipitation files may be used in each simulation and each file can hold data for up to 300 stations. The data for a particular station is assigned to a subbasin in file.cio. Temperature input file. This optional file contains daily measured maximum and minimum temperatures for a measuring gage(s). Up to 18 temperature files may be used in each simulation and each file can hold data for up to 150 stations. The data for a particular station is assigned to a subbasin in file.cio. Solar radiation input file. This optional file contains daily solar radiation for a measuring gage(s). The solar radiation file can hold data for up to 300 stations. The data for a particular station is assigned to a subbasin in file.cio. Wind speed input file. This optional file contains daily average wind speed for a measuring gage(s). The wind speed file can hold data for up to 300 stations. The data for a particular station is assigned to a subbasin in file.cio. Relative humidity input file. This optional file contains daily relative humidity values for a measuring gage(s). The relative humidity file can hold data for up to 300 stations. The data for a particular station is assigned to a subbasin in file.cio. Potential evapotranspiration input file. This optional file contains daily PET values for the watershed. Land cover/plant growth database file. This required file contains plant growth parameters for all land covers simulated in the watershed. Tillage database file. This required file contains information on the amount and depth of mixing caused by tillage operations simulated in the watershed.

SWAT USERS MANUAL, VERSION 2000

pest.dat

Pesticide database file. This required file contains information on mobility and degradation for all pesticides simulated in the watershed. fert.dat Fertilizer database file. This required file contains (watershed level file) information on the nutrient content of all fertilizers and manures simulated in the watershed. urban.dat Urban database file. This required file contains (watershed level file) information on the build-up/wash-off of solids in urban areas simulated in the watershed. .sub Subbasin input file. Required file for subbasin level (subbasin level file) parameters. Catch-all file. .wgn Weather generator input file. This required file (subbasin level file) contains the statistical data needed to generate representative daily climatic data for the subbasins. .pnd Pond/wetland input file. This optional file contains (subbasin level file) information for impoundments located within the subbasin. .wus Water use input file. This optional file contains (subbasin level file) information for consumptive water use in the subbasin. .rte Main channel input file. This required file contains (subbasin level file) parameters governing water and sediment movement in the main channel of the subbasin. .wwq Watershed water quality input file. This optional file (watershed level file) contains parameters used to model QUAL2E transformations in the main channels. .swq Stream water quality input file. This optional file (subbasin level file) contains parameters used to model pesticide and QUAL2E nutrient transformations in the main channel of the subbasin. .hru HRU input file. Required file for HRU level (HRU level file) parameters. Catch-all file. .mgt Management input file. This required file contains (HRU level file) management scenarios and specifies the land cover simulated in the HRU. .sol Soil input file. This required file contains information (HRU level file) about the physical characteristics of the soil in the HRU. .chm Soil chemical input file. This optional file contains (HRU level file) information about initial nutrient and pesticide levels of the soil in the HRU.
(watershed level file)

CHAPTER 1: SWAT INPUTOVERVIEW

.gw
(HRU level file)

.res
(reservoir file)

.lwq
(reservoir file)

recday.dat recmon.dat recyear.dat reccnst.dat

(point source file)

Groundwater input file. This required file contains information about the shallow and deep aquifer in the subbasin. Because land covers differ in their interaction with the shallow aquifer, information in this input file is allowed to be varied at the HRU level. Reservoir input file. This optional file contains parameters used to model the movement of water and sediment through a reservoir. Lake water quality input file. This optional file contains parameters used to model the movement of nutrients and pesticides through a reservoir. Point source input file. These optional files contain information about loadings to the channel network from a point source. The type of file used to store the data depends on how the data is summarized (daily, monthly, yearly, or average annual).

1.3 MODEL INPUTS BY TYPE

The following tables group inputs by type. Detailed explanations of the variables are given in the input file chapter. Please keep in mind that in the GIS interfaces, some of these variables are automatically set by the interface and users will not be allowed to edit them. Watershed Dimensions Variable DA_KM HRUTOT HRU_FR

.bsn .sub .hru

File Chapter 5 Chapter 6 Chapter 19

Length of Simulation Variable NBYR IYR IDAF IDAL

.cod .cod .cod .cod

File Chapter 4 Chapter 4 Chapter 4 Chapter 4

10

SWAT USERS MANUAL, VERSION 2000

Output Print Options/Output Summary Options Variable File IPD .cod Chapter 4 NYSKIP .cod Chapter 4 IPRN .cod Chapter 4 ILOG .cod Chapter 4 IPRP .cod Chapter 4 IPDVAR(1-20) .cod Chapter 4 IPDVAB(1-20) .cod Chapter 4 IPDVAS(1-20) .cod Chapter 4 TITLE file.cio Chapter 3 BIGSUB file.cio Chapter 3 SBSOUT file.cio Chapter 3 RCHOUT file.cio Chapter 3 RSVOUT file.cio Chapter 3 LWQOUT file.cio Chapter 3 WTROUT file.cio Chapter 3 PESTOUT file.cio Chapter 3 EVENT file.cio Chapter 3

Random Number Generator Variable IGN

.cod

File Chapter 4

Special Project Flag Variable ISPROJ

.cod

File Chapter 4

CLIMATE
Precipitation Variable PCPSIM IDT IDIST REXP IEVENT NRGAGE NRTOT NRGFIL RFILE(1-18) File Chapter 4 Chapter 4 Chapter 4 Chapter 4 Chapter 4 Chapter 3 Chapter 3 Chapter 3 Chapter 3

.cod .cod .cod .cod .cod file.cio file.cio file.cio file.cio

CHAPTER 1: SWAT INPUTOVERVIEW

11

Precipitation, cont. Variable IRGAGE RAIN_YRS PCPMM(1-12) PCPSTD(1-12) PCPSKW(1-12) PR_W(1,1-12) PR_W(2,1-12) PCPD(1-12) RAINHHMX(1-12) PRECIPITATION PLAPS RFINC(1-12)

file.cio .wgn .wgn .wgn .wgn .wgn .wgn .wgn .wgn .pcp .sub .sub

File Chapter 3 Chapter 13 Chapter 13 Chapter 13 Chapter 13 Chapter 13 Chapter 13 Chapter 13 Chapter 13 Chapter 7 Chapter 6 Chapter 6

Snow Processes Variable SFTMP SMTMP SMFMX SMFMN TIMP SNOCOVMX SNO50COV SNO_SUB SNOEB(1-10)

.bsn .bsn .bsn .bsn .bsn .bsn .bsn .sub .sub

File Chapter 5 Chapter 5 Chapter 5 Chapter 5 Chapter 5 Chapter 5 Chapter 5 Chapter 6 Chapter 6

Temperature Variable TMPSIM NTGAGE NTTOT NTGFIL TFILE(1-18) ITGAGE TMPMX(1-12) TMPMN(1-12) TMPSTDMX(1-12) TMPSTDMN(1-12) MAX TEMP MIN TEMP

.cod file.cio file.cio file.cio file.cio file.cio .wgn .wgn .wgn .wgn .tmp .tmp

File Chapter 4 Chapter 3 Chapter 3 Chapter 3 Chapter 3 Chapter 3 Chapter 13 Chapter 13 Chapter 13 Chapter 13 Chapter 8 Chapter 8

12

SWAT USERS MANUAL, VERSION 2000

Temperature, cont. Variable TLAPS TMPINC

.sub .sub

File Chapter 6 Chapter 6

Solar Radiation Variable SLRSIM NSTOT SLRFILE ISGAGE SOLARAV(1-12) SOL_RAD LATITUDE RADINC(1-12)

.cod file.cio file.cio file.cio .wgn .slr .sub .sub

File Chapter 4 Chapter 3 Chapter 3 Chapter 3 Chapter 13 Chapter 9 Chapter 6 Chapter 6

Relative Humidity Input Variable RHSIM NHTOT RHFILE IHGAGE DEWPT(1-12) RHD HUMINC(1-12)

.cod file.cio file.cio file.cio .wgn .hmd .sub

File Chapter 4 Chapter 3 Chapter 3 Chapter 3 Chapter 13 Chapter 11 Chapter 6

Wind Speed Input Variable WNDSIM NWTOT WNDFILE IWGAGE WNDAV(1-12) WND_SP

.cod file.cio file.cio file.cio .wgn .wnd

File Chapter 4 Chapter 3 Chapter 3 Chapter 3 Chapter 13 Chapter 10

CHAPTER 1: SWAT INPUTOVERVIEW

13

Elevation Bands Variable WELEV ELEVATION ELEVATION ELEVB(1-10) ELEV_FR(1-10) SNOEB(1-10) PLAPS TLAPS

.wgn .pcp .tmp .sub .sub .sub .sub .sub

File Chapter 13 Chapter 7 Chapter 8 Chapter 6 Chapter 6 Chapter 6 Chapter 6 Chapter 6

Climate Change Variable CO2 RFINC(1-12) TMPINC(1-12) RADINC(1-12) HUMINC(1-12) CO2HI BIOEHI

.sub .sub .sub .sub .sub crop.dat crop.dat

File Chapter 6 Chapter 6 Chapter 6 Chapter 6 Chapter 6 Chapter 14 Chapter 14

HYDROLOGIC CYCLE
Potential and Actual Evapotranspiration Variable IPET .cod PETFILE file.cio ESCO .bsn, .hru EPCO .bsn, .hru PET_MEAS .pet ELEV .sub CANMX .hru SOL_ALB .sol GW_REVAP .gw REVAPMN .gw File Chapter 4 Chapter 3 Chapter 5, 19 Chapter 5, 19 Chapter 12 Chapter 6 Chapter 19 Chapter 22 Chapter 24 Chapter 24

14

SWAT USERS MANUAL, VERSION 2000

Surface Runoff Variable IEVENT SURLAG CN2 CNOP (plant operation) CNOP (harv & kill op) CNOP (tillage operation)

.cod .bsn .mgt .mgt .mgt .mgt

File Chapter 4 Chapter 5 Chapter 20 Chapter 20 Chapter 20 Chapter 20

Time of Concentration Variable CH_L(1) CH_S(1) CH_N(1) SLSUBBSN OV_N

.sub .sub .sub .hru .hru

File Chapter 6 Chapter 6 Chapter 6 Chapter 19 Chapter 19

Crack Flow Variable ICRK SOL_CRK

.cod .sol

File Chapter 4 Chapter 22

Transmission Losses from Surface Runoff Variable File CH_L(1) .sub Chapter 6 CH_W(1) .sub Chapter 6 CH_K(1) .sub Chapter 6

Soil Water Variable FFCB SOL_Z SOL_BD SOL_AWC SOL_K irrigation operation auto-irrigation operation

.bsn .sol .sol .sol .sol .mgt .mgt

File Chapter 5 Chapter 22 Chapter 22 Chapter 22 Chapter 22 Chapter 20 Chapter 20

CHAPTER 1: SWAT INPUTOVERVIEW

15

Lateral Flow Variable SLOPE LAT_TTIME SLSOIL Groundwater Variable SHALLST DEEPST GW_DELAY ALPHA_BF GWQMN GW_REVAP REVAPMN RCHRG_DP WUSHAL(1-12) WUDEEP(1-12)

.hru .hru .hru

File Chapter 19 Chapter 19 Chapter 19 File Chapter 24 Chapter 24 Chapter 24 Chapter 24 Chapter 24 Chapter 24 Chapter 24 Chapter 24 Chapter 21 Chapter 21

.gw .gw .gw .gw .gw .gw .gw .gw .wus .wus

SEDIMENT
Sediment Erosion Variable APM SLSUBBSN SLOPE LAT_SED FILTERW CLAY SILT SAND ROCK USLE_K USLE_P USLE_C File Chapter 5 Chapter 19 Chapter 19 Chapter 19 Chapter 19 Chapter 22 Chapter 22 Chapter 22 Chapter 22 Chapter 22 Chapter 20 Chapter 14

.bsn .hru .hru .hru .hru .sol .sol .sol .sol .sol .mgt crop.dat

16

SWAT USERS MANUAL, VERSION 2000

NUTRIENTS
Nitrogen Cycle/Runoff Variable RCN CMN UBN NPERCO RSDCO ANION_EXCL SOL_NO3 SOL_ORGN SOL_CBN ERORGN FILTERW BIOMIX fertilizer application FMINN FORGN FNH3N tillage operation EFFMIX DEPTIL grazing operation auto-fertilization operation BN(1) BN(2) BN(3) GWNO3 File Chapter 5 Chapter 5 Chapter 5 Chapter 5 Chapter 5 Chapter 22 Chapter 23 Chapter 23 Chapter 22 Chapter 19 Chapter 19 Chapter 20 Chapter 20 Chapter 17 Chapter 17 Chapter 17 Chapter 20 Chapter 15 Chapter 15 Chapter 20 Chapter 20 Chapter 14 Chapter 14 Chapter 14 Chapter 24

.bsn .bsn .bsn .bsn .bsn .sol .chm .chm .sol .hru .hru .mgt .mgt fert.dat fert.dat fert.dat .mgt till.dat till.dat .mgt .mgt crop.dat crop.dat crop.dat .gw

Phosphorus Cycle/Runoff Variable UBP PPERCO PHOSKD PSP RSDCO SOL_LABP SOL_ORGP ERORGP FILTERW BIOMIX

.bsn .bsn .bsn .bsn .bsn .chm .chm .hru .hru .mgt

File Chapter 5 Chapter 5 Chapter 5 Chapter 5 Chapter 5 Chapter 23 Chapter 23 Chapter 19 Chapter 19 Chapter 20

CHAPTER 1: SWAT INPUTOVERVIEW

17

Phosphorus Cycle/Runoff, cont. Variable fertilizer application .mgt FMINP fert.dat FORGP fert.dat tillage operation .mgt EFFMIX till.dat DEPTIL till.dat grazing operation .mgt auto-fertilization operation .mgt BP(1) crop.dat BP(2) crop.dat BP(3) crop.dat GWSOLP .gw

File Chapter 20 Chapter 17 Chapter 17 Chapter 20 Chapter 15 Chapter 15 Chapter 20 Chapter 20 Chapter 14 Chapter 14 Chapter 14 Chapter 24

PESTICIDE
Pesticide in Soil/Runoff Variable PERCOP PESTNUM PLTPST SOLPST FILTERW PSTENR BIOMIX pesticide application SKOC WOF HLIFE_F HLIFE_S AP_EF WSOL tillage operation EFFMIX DEPTIL File Chapter 5 Chapter 23 Chapter 23 Chapter 23 Chapter 19 Chapter 23 Chapter 20 Chapter 20 Chapter 16 Chapter 16 Chapter 16 Chapter 16 Chapter 16 Chapter 16 Chapter 20 Chapter 15 Chapter 15

.bsn .chm .chm .chm .hru .chm .mgt .mgt pest.dat pest.dat pest.dat pest.dat pest.dat pest.dat .mgt till.dat till.dat

18

SWAT USERS MANUAL, VERSION 2000

BACTERIA
Bacteria in Soil/Runoff Variable WDPQ WGPQ WDLPQ WGLPQ WDPS WGPS WDLPS WGLPS BACTKDQ THBACT FILTERW BIOMIX tillage operation EFFMIX DEPTIL fertilizer application BACTPDB BACTLPDB BACTKDDB auto-fertilization operation File Chapter 5 Chapter 5 Chapter 5 Chapter 5 Chapter 5 Chapter 5 Chapter 5 Chapter 5 Chapter 5 Chapter 5 Chapter 19 Chapter 20 Chapter 20 Chapter 15 Chapter 15 Chapter 20 Chapter 17 Chapter 17 Chapter 17 Chapter 20

.bsn .bsn .bsn .bsn .bsn .bsn .bsn .bsn .bsn .bsn .hru .mgt .mgt till.dat till.dat .mgt fert.dat fert.dat fert.dat .mgt

PLANTS
Plant Growth Variable SOL_ZMX PHU/HEAT UNITS plant operation harvest & kill operation harvest operation kill operation grazing operation IDC BIO_E HVSTI BLAI FRGRW1 LAIMX1 FRGRW2 LAIMX2 File Chapter 22 Chapter 20 Chapter 20 Chapter 20 Chapter 20 Chapter 20 Chapter 20 Chapter 14 Chapter 14 Chapter 14 Chapter 14 Chapter 14 Chapter 14 Chapter 14 Chapter 14

.sol .mgt .mgt .mgt .mgt .mgt .mgt crop.dat crop.dat crop.dat crop.dat crop.dat crop.dat crop.dat crop.dat

CHAPTER 1: SWAT INPUTOVERVIEW

19

Plant Growth, cont. Variable DLAI CHTMX RDMX T_OPT T_BASE CNYLD CPYLD BN(1) BN(2) BN(3) BP(1) BP(2) BP(3) WSYF GSI VPDFR FRGMAX WAVP

crop.dat crop.dat crop.dat crop.dat crop.dat crop.dat crop.dat crop.dat crop.dat crop.dat crop.dat crop.dat crop.dat crop.dat crop.dat crop.dat crop.dat crop.dat

File Chapter 14 Chapter 14 Chapter 14 Chapter 14 Chapter 14 Chapter 14 Chapter 14 Chapter 14 Chapter 14 Chapter 14 Chapter 14 Chapter 14 Chapter 14 Chapter 14 Chapter 14 Chapter 14 Chapter 14 Chapter 14

Residue Variable RSDIN RSDCO harvest & kill operation harvest operation kill operation grazing operation RSDCO_PL

.hru .bsn .mgt .mgt .mgt .mgt crop.dat

File Chapter 19 Chapter 5 Chapter 20 Chapter 20 Chapter 20 Chapter 20 Chapter 14

MANAGEMENT
Management-Land Cover Variable IGRO NROT NCRP ALAI BIO_MS PHU BIO_MIN File Chapter 20 Chapter 20 Chapter 20 Chapter 20 Chapter 20 Chapter 20 Chapter 20

.mgt .mgt .mgt .mgt .mgt .mgt .mgt

20

SWAT USERS MANUAL, VERSION 2000

Management-Land Cover, cont. Variable plant operation .mgt HEAT UNITS .mgt NCR .mgt HITAR .mgt BIO_TARG .mgt ALAINIT .mgt BIO_INIT .mgt harvest & kill operation .mgt harvest operation .mgt HIOVR .mgt HARVEFF .mgt kill operation .mgt grazing operation .mgt BMEAT .mgt NDGRAZ .mgt BMTRMP .mgt

File Chapter 20 Chapter 20 Chapter 20 Chapter 20 Chapter 20 Chapter 20 Chapter 20 Chapter 20 Chapter 20 Chapter 20 Chapter 20 Chapter 20 Chapter 20 Chapter 20 Chapter 20 Chapter 20

Management-Nutrients Variable fertilizer application FRT_LY1 FERT_ID FERT_KG tillage operation TILLAGE_ID grazing operation WMANURE IGFTYP auto-fertilization operation AUTO_NSTR FERT_ID AUTO_NMXS AUTO_NMXA AUTO_EFF AFRT_LY1

.mgt .mgt .mgt .mgt .mgt .mgt .mgt .mgt .mgt .mgt .mgt .mgt .mgt .mgt .mgt .mgt

File Chapter 20 Chapter 20 Chapter 20 Chapter 20 Chapter 20 Chapter 20 Chapter 20 Chapter 20 Chapter 20 Chapter 20 Chapter 20 Chapter 20 Chapter 20 Chapter 20 Chapter 20 Chapter 20

CHAPTER 1: SWAT INPUTOVERVIEW

21

Management-Pesticide Variable pesticide application PEST_ID FERT_KG tillage operation TILLAGE_ID

.mgt .mgt .mgt .mgt .mgt

File Chapter 20 Chapter 20 Chapter 20 Chapter 20 Chapter 20

Management-Water Variable IRR IRRNO FLOWMIN DIVMAX FLOWFR DDRAIN TDRAIN GDRAIN IPOT POT_FR POT_TILE POT_VOLX POT_VOL EVLAI irrigation operation IRR_AMT auto-irrigation operation AUTO_WSTR release/impound operation IREL_IMP

.hru .hru .hru .hru .hru .hru .hru .hru .hru .hru .hru .hru .hru .bsn .mgt .mgt .mgt .mgt .mgt .mgt

File Chapter 19 Chapter 19 Chapter 19 Chapter 19 Chapter 19 Chapter 19 Chapter 19 Chapter 19 Chapter 19 Chapter 19 Chapter 19 Chapter 19 Chapter 19 Chapter 5 Chapter 20 Chapter 20 Chapter 20 Chapter 20 Chapter 20 Chapter 20

Management-Urban Variable IURBAN URBLU street sweeping operation SWEEPEFF AVWSP FIMP FCIMP CURBDEN URBCOEF

.hru .hru .mgt .mgt .mgt urban.dat urban.dat urban.dat urban.dat

File Chapter 19 Chapter 19 Chapter 20 Chapter 20 Chapter 20 Chapter 18 Chapter 18 Chapter 18 Chapter 18

22

SWAT USERS MANUAL, VERSION 2000

Management-Urban, cont. Variable DIRTMX THALF TNCONC TPCONC TNO3CONC

urban.dat urban.dat urban.dat urban.dat urban.dat

File Chapter 18 Chapter 18 Chapter 18 Chapter 18 Chapter 18

CHANNEL PROCESSES
Channel Water Routing Variable IEVENT IRTE EVRCH MSK_CO1 MSK_CO2 MSK_X CH_W(2) CH_D CH_S(2) CH_L(2) CH_N(2) CH_K(2) ALPHA_BNK WURCH(1-12) File Chapter 4 Chapter 4 Chapter 5 Chapter 5 Chapter 5 Chapter 5 Chapter 25 Chapter 25 Chapter 25 Chapter 25 Chapter 25 Chapter 25 Chapter 25 Chapter 21

.cod .cod .bsn .bsn .bsn .bsn .rte .rte .rte .rte .rte .rte .rte .wus

Channel Sediment Routing Variable IDEG PRF SPCON SPEXP CH_W(2) CH_D CH_S(2) CH_EROD CH_COV CH_WDR

.cod .bsn .bsn .bsn .rte .rte .rte .rte .rte .rte

File Chapter 4 Chapter 5 Chapter 5 Chapter 5 Chapter 25 Chapter 25 Chapter 25 Chapter 25 Chapter 25 Chapter 25

CHAPTER 1: SWAT INPUTOVERVIEW

23

Channel Nutrient Routing Variable IWQ AI1 AI2 P_N RS2 RS3 RS4 RS5 BC1 BC2 BC3 BC4

.cod .wwq .wwq .wwq .swq .swq .swq .swq .swq .swq .swq .swq

File Chapter 4 Chapter 26 Chapter 26 Chapter 26 Chapter 27 Chapter 27 Chapter 27 Chapter 27 Chapter 27 Chapter 27 Chapter 27 Chapter 27

Channel Water Quality Indices Variable IWQ .cod LAO .wwq IGROPT .wwq AI0 .wwq AI1 .wwq AI2 .wwq AI3 .wwq AI4 .wwq AI5 .wwq AI6 .wwq MUMAX .wwq RHOQ .wwq TFACT .wwq K_L .wwq K_N .wwq K_P .wwq LAMBDA0 .wwq LAMBDA1 .wwq LAMBDA3 .wwq RS1 .swq RK1 .swq RK2 .swq RK3 .swq RK4 .swq

File Chapter 4 Chapter 26 Chapter 26 Chapter 26 Chapter 26 Chapter 26 Chapter 26 Chapter 26 Chapter 26 Chapter 26 Chapter 26 Chapter 26 Chapter 26 Chapter 26 Chapter 26 Chapter 26 Chapter 26 Chapter 26 Chapter 26 Chapter 27 Chapter 27 Chapter 27 Chapter 27 Chapter 27

24

SWAT USERS MANUAL, VERSION 2000

Channel Pesticide Routing Input Variable IRTPEST .bsn CHPST_REA .swq CHPST_VOL .swq CHPST_KOC .swq CHPST_STL .swq CHPST_RSP .swq CHPST_MIX .swq SEDPST_CONC .swq SEDPST_REA .swq SEDPST_BRY .swq SEDPST_ACT .swq

File Chapter 5 Chapter 27 Chapter 27 Chapter 27 Chapter 27 Chapter 27 Chapter 27 Chapter 27 Chapter 27 Chapter 27 Chapter 27

IMPOUNDMENT PROCESSES
Impoundment Water RoutingPond Variable PND_FR .pnd PND_PSA .pnd PND_PVOL .pnd PND_ESA .pnd PND_EVOL .pnd PND_VOL .pnd PND_K .pnd IFLOD1 .pnd IFLOD2 .pnd NDTARG .pnd WUPND(1-12) .wus File Chapter 28 Chapter 28 Chapter 28 Chapter 28 Chapter 28 Chapter 28 Chapter 28 Chapter 28 Chapter 28 Chapter 28 Chapter 21

Impoundment Water RoutingWetland Variable WET_FR .pnd WET_NSA .pnd WET_NVOL .pnd WET_MXSA .pnd WET_MXVOL .pnd WET_VOL .pnd WET_K .pnd

File Chapter 28 Chapter 28 Chapter 28 Chapter 28 Chapter 28 Chapter 28 Chapter 28

CHAPTER 1: SWAT INPUTOVERVIEW

25

Impoundment Water RoutingPothole Variable IPOT .hru POT_FR .hru POT_TILE .hru POT_VOLX .hru POT_VOL .hru EVLAI .bsn Impoundment Water RoutingReservoir Variable RES_SUB .res MORES .res IYRES .res RES_ESA .res RES_EVOL .res RES_PSA .res RES_PVOL .res RES_VOL .res RES_K .res IRESCO .res OFLOWMX(1-12) .res OFLOWMN(1-12) .res RES_RR .res RESMONO .res IFLOD1R .res IFLOD2R .res NDTARGR .res STARG(1-12) .res RESDAYO .res WURESN(1-12) .res WURTNF .res RES_OUTFLOW resdayo.dat RESOUT resmono.dat

File Chapter 19 Chapter 19 Chapter 19 Chapter 19 Chapter 19 Chapter 5

File Chapter 29 Chapter 29 Chapter 29 Chapter 29 Chapter 29 Chapter 29 Chapter 29 Chapter 29 Chapter 29 Chapter 29 Chapter 29 Chapter 29 Chapter 29 Chapter 29 Chapter 29 Chapter 29 Chapter 29 Chapter 29 Chapter 29 Chapter 29 Chapter 29 Chapter 29 Chapter 29

26

SWAT USERS MANUAL, VERSION 2000

Impoundment Sediment Routing Variable PND_SED .pnd PND_NSED .pnd WET_SED .pnd WET_NSED .pnd POT_NSED .hru RES_SED .res RES_NSED .res

File Chapter 28 Chapter 28 Chapter 28 Chapter 28 Chapter 19 Chapter 29 Chapter 29

Impoundment Nutrient RoutingPond Variable PSETL1 .pnd PSETL2 .pnd NSETL1 .pnd NSETL2 .pnd PND_NO3 .pnd PND_SOLP .pnd PND_ORGN .pnd PND_ORGP .pnd IPND1 .pnd IPND2 .pnd

File Chapter 28 Chapter 28 Chapter 28 Chapter 28 Chapter 28 Chapter 28 Chapter 28 Chapter 28 Chapter 28 Chapter 28

Impoundment Nutrient RoutingWetland Variable PSETLW1 .pnd PSETLW2 .pnd NSETLW1 .pnd NSETLW2 .pnd WET_NO3 .pnd WET_SOLP .pnd WET_ORGN .pnd WET_ORGP .pnd IPND1 .pnd IPND2 .pnd

File Chapter 28 Chapter 28 Chapter 28 Chapter 28 Chapter 28 Chapter 28 Chapter 28 Chapter 28 Chapter 28 Chapter 28

CHAPTER 1: SWAT INPUTOVERVIEW

27

Impoundment Nutrient RoutingReservoir Variable File IRES1 .lwq Chapter 30 IRES2 .lwq Chapter 30 PSETLR1 .lwq Chapter 30 PSETLR2 .lwq Chapter 30 NSETLR1 .lwq Chapter 30 NSETLR2 .lwq Chapter 30 RES_ORGP .lwq Chapter 30 RES_SOLP .lwq Chapter 30 RES_ORGN .lwq Chapter 30 RES_NO3 .lwq Chapter 30 RES_NH3 .lwq Chapter 30 RES_NO2 .lwq Chapter 30

Impoundment Water Quality Indices Variable CHLA .pnd SECCI .pnd CHLAW .pnd SECCIW .pnd CHLAR .lwq SECCIR .lwq

File Chapter 28 Chapter 28 Chapter 28 Chapter 28 Chapter 30 Chapter 30

Impoundment Pesticide RoutingReservoir Variable File LKPST_CONC .lwq Chapter 30 LKPST_REA .lwq Chapter 30 LKPST_VOL .lwq Chapter 30 LKPST_KOC .lwq Chapter 30 LKPST_STL .lwq Chapter 30 LKPST_RSP .lwq Chapter 30 LKPST_MIX .lwq Chapter 30 LKSPST_CONC .lwq Chapter 30 LKSPST_REA .lwq Chapter 30 LKSPST_BRY .lwq Chapter 30 LKSPST_ACT .lwq Chapter 30

28

SWAT USERS MANUAL, VERSION 2000

CHAPTER 2

SWAT INPUT DATA:

WATERSHED CONFIGURATION

The first step in setting up a watershed simulation is to define the relative arrangement of the parts or elements, i.e. the configuration, of the watershed. If the watershed has only one primary channel and there is very little variation in topography and climate across the watershed, there may not be a need to partition the watershed into smaller units. However, the majority of watersheds will exhibit enough complexity in the stream network, topography or climate to warrant subdivision for modeling purposes. There are several techniques used to discretize a watershed. In the past, models could only apply one type of discretization scheme to a watershed. This

29

30

SWAT USERS MANUAL, VERSION 2000

resulted in the development of several models that differ only in the watershed discretization scheme used.

2.1 DISCRETIZATION SCHEMES

The three most common techniques used to discretize a watershed are: Grid cell. This configuration allows the user to incorporate significant spatial detail into a simulation. Models which use this technique include AGNPS (Young et al., 1987), ANSWERS (Beasley et al., 1980) and the WEPP grid version (Foster, 1987). Representative hillslope. This configuration is useful for modeling hillslope processes. This technique is used in APEX (Williams, et al., 1998) and the WEPP hillslope version (Lane and Nearing, 1989). Subwatershed. This configuration preserves the natural channels

and flow paths of the watershed. This technique is used in the WEPP watershed version (Foster, 1987), HYMO (Williams and Hann, 1973) and SWRRB (Arnold et al., 1990).

All of these schemes have strengths and weaknesses and applications for which they are most appropriate. SWAT uses the subwatershed configuration as the primary discretization scheme for a watershed. However, because of the routing command language utilized in SWAT, it is possible to use any of these three, alone or in combination, to model a watershed.

2.2 WATERSHED CONFIGURATION FILE (.FIG)

The watershed configuration file contains information used by SWAT to simulate processes occurring within the HRU/subbasin and to route the stream loadings through the channel network of the watershed. A reach routing command structure, similar to that developed for HYMO (Williams and Hann, 1973), is utilized to route and add flows through the watershed. The following sections review the different features of the watershed configuration file.

CHAPTER 2: SWAT INPUTWATERSHED CONFIGURATION

31

2.2.1 INCORPORATION OF COMMENTS

To assist the user in interpreting the watershed configuration file, an unlimited number of comment lines are allowed. These comments can be used to isolate the routing commands for different reaches, etc. To included comments in the watershed configuration file, a line must have an asterisk (*) in the 1st space on the line. When SWAT reads the asterisk, it will skip to the next line.

2.2.2 COMMAND LINES

Thirteen different commands may be used in the watershed configuration file. The commands, along with their numeric codes, are: finish subbasin route routres transfer add recmon recyear save recday reccnst structure saveconc 0 1 2 3 4 5 7 8 9 10 11 12 14

The format of the commands is illustrated in Figure 2-1. The most commonly used commands are: subbasin, route, add, and finish. In brief, these commands simulated the land phase of the hydrologic cycle and determine the loadings to the reach (subbasin), model the movement and transformations occurring in the reach (route), allow the output from different subbasins to be summed together (add), and identify the end of the routing command sequence (finish). The remaining commands are utilized to model more unique configurations. This set of commands can be divided several subgroups: routing of water through a reservoir (routres), humanly contrived movement of water (transfer), aeration of water resulting from flow through structures along the channel (structure), incorporation of point source data (rechour, recday, recmon,

32

SWAT USERS MANUAL, VERSION 2000

recyear, reccnst), formatting of watershed outflow for input into a different SWAT simulation (save), and formatting of water quality simulation results at specified points in the reach network (saveconc).
Figure 2-1: Commands included in watershed configuration file

The watershed configuration file is a fixed format file. With fixed format, the model looks for data only in a particular location on a command line. Spaces not allocated to variable inputs for a specific command are not processed by the model. The interfaces commonly use the extra space to write other data or they insert zeros in the unused columns. Appendix B steps through the set up of example watershed configuration files and will be very helpful to users trying to familiarize themselves with the logic of this file.

CHAPTER 2: SWAT INPUTWATERSHED CONFIGURATION

33

2.2.2.1 SUBBASIN COMMAND (1)

The subbasin command simulates all processes involved in the land phase of the hydrologic cycle and computes runoff, sediment, and chemical loadings from each HRU within the subbasin. Variables required on the subbasin command line are: Variable name COMMAND HYD_STOR Definition The command code = 1 for the subbasin command. The hydrograph storage location number. After a command is executed, the results are stored in an array at the position defined by this number. It is crucial that all hydrograph storage location numbers are unique. If the same number is used twice, output from one command line will be overwritten by that from another and simulation results will be incorrect. Subbasin number. This number is assigned in file.cio. Every subbasin in the watershed has a different number. GIS code printed to output files (optional)

SUB_NUM GIS_CODE

The format of the subbasin command line is:

Variable name COMMAND HYD_STOR SUB_NUM GIS_CODE Position space 11-16 space 17-22 space 23-28 space 47-55 Format 6-digit integer 6-digit integer 6-digit integer 9-digit integer F90 Format i6 i6 i6 i9

34

SWAT USERS MANUAL, VERSION 2000

2.2.2.2 ROUTE COMMAND (2)

The route command routes the water, sediment, and chemical loadings through a main channel or reach. Variables required on the route command line are: Variable name COMMAND HYD_STOR Definition The command code = 2 for the route command. The hydrograph storage location number. After a command is executed, the results are stored in an array at the position defined by this number. It is crucial that all hydrograph storage location numbers are unique. If the same number is used twice, output from one command line will be overwritten by that from another and simulation results will be incorrect. Reach number. The reach number is the same as the subbasin number. Inflow hydrograph storage location number. The data that is to be routed through the reach. Fraction of overland flow (0.000 to 1.000). If flow leaving a subbasin is completely channelized, FLOW_OVN = 0.000. In cases where a hillslope is being simulated, overland flow from one subbasin to another occurs and the value of FLOW_OVN can be increased to account for the amount of non-channelized overland flow taking place between the subbasins. The overland flow to the next subbasin is added to the rainfall of the receiving subbasin and allowed to infiltrate or run off. The sediment and chemical loadings associated with the overland flow are assumed to be deposited on the upper soil layer of the receiving subbasin. The fraction of the flow in the channel is routed directly to the reach of the receiving subbasin.

RCH_NUM HYD_NUM FLOW_OVN

The format of the route command line is:

Variable name COMMAND HYD_STOR RCH_NUM HYD_NUM FLOW_OVN Position space 11-16 space 17-22 space 23-28 space 29-34 space 41-46 Format 6-digit integer 6-digit integer 6-digit integer 6-digit integer decimal (xx.xxx) F90 Format i6 i6 i6 i6 f6.3

CHAPTER 2: SWAT INPUTWATERSHED CONFIGURATION

35

2.2.2.3 ADD COMMAND (5)

The add command is used to sum the water, sediment, and chemical loadings of any two flows. Variables required on the add command line are: Variable name COMMAND HYD_STOR HYD_NUM1 HYD_NUM2 Definition The command code = 5 for the add command. The hydrograph storage location number for the results. The hydrograph storage location number of the 1st set of data to be added. The hydrograph storage location number of the 2nd set of data to be added.

The format of the add command line is:

Variable name COMMAND HYD_STOR HYD_NUM1 HYD_NUM2 Position space 11-16 space 17-22 space 23-28 space 29-34 Format 6-digit integer 6-digit integer 6-digit integer 6-digit integer F90 Format i6 i6 i6 i6

36

SWAT USERS MANUAL, VERSION 2000

2.2.2.4 FINISH COMMAND (0)

The last command line in the .fig file must be a finish command line. The finish command notifies the model that the end of the command lines in the watershed configuration file has been reached. Variables required on the finish command line are: Variable name COMMAND Definition The command code = 0 for the finish command

The format of the finish command line is:

Variable name COMMAND Position space 11-16 Format 6-digit integer F90 Format i6

CHAPTER 2: SWAT INPUTWATERSHED CONFIGURATION

37

2.2.2.5 ROUTRES COMMAND (3)

The routres command routes water, sediment, and chemical loadings through a reservoir. The routres command requires two lines. Variables required on the routres command lines are: Variable name COMMAND HYD_STOR RES_NUM Definition The command code = 3 for the routres command. The hydrograph storage location number for results. Reservoir number. Each reservoir modeled in the watershed must be assigned a unique consecutive number beginning at 1. Inflow hydrograph storage location number. The data that is to be routed through the reservoir. Name of reservoir input file (.res) Name of reservoir water quality input file (optional) (.lwq)

HYD_NUM RESFILE LWQFILE

The format of the routres command lines is:

Variable name COMMAND HYD_STOR RES_NUM HYD_NUM RESFILE LWQFILE Line # 1 1 1 1 2 2 Position space 11-16 space 17-22 space 23-28 space 29-34 space 11-23 space 24-36 Format 6-digit integer 6-digit integer 6-digit integer 6-digit integer character character F90 Format i6 i6 i6 i6 a13 a13

38

SWAT USERS MANUAL, VERSION 2000

2.2.2.6 TRANSFER COMMAND (4)

While water is most typically removed from a water body for irrigation purposes, SWAT also allows water to be transferred from one water body to another. This is performed with a transfer command in the watershed configuration file. The transfer command can be used to move water from any reservoir or reach in the watershed to any other reservoir or reach in the watershed. The user must input the type of water source, the location of the source, the type of water body receiving the transfer, the location of the receiving water body, and the amount of water transferred. Three options are provided to specify the amount of water transferred: a fraction of the volume of water in the source; a volume of water left in the source; or the volume of water transferred. The transfer is performed every day of the simulation. Originally, the transfer command was the only method available to irrigate an HRU. While the irrigation scenarios are now handled primarily in the management files, the transfer command was retained for flexibility. This command should not be used with hourly stream routing. Variables required on the transfer command line are: Variable name COMMAND DEP_TYPE Definition The command code = 4 for the transfer command. Water source type: 1 reach 2 reservoir Water source number. The number of the reach or reservoir from which the flow will be diverted. Destination type. Defines the receiving body. 1 reach 2 reservoir

DEP_NUM DEST_TYPE

CHAPTER 2: SWAT INPUTWATERSHED CONFIGURATION

39

Variable name DEST_NUM TRANS_AMT TRANS_CODE

Definition Destination number. Number of reach or reservoir receiving the water. The flow amount transferred. (defined by TRANS_CODE) The rule code governing the transfer of water: 1 A fraction of the flow or volume to be transferred out of the reach or reservoir is specified 2 A minimum flow (reach) or volume (reservoir) to leave in the reach or reservoir is specified (m3/day) 3 An exact amount of water to be transferred is specified (m3/day)

The format of the transfer command line is:

Variable name COMMAND DEP_TYPE DEP_NUM DEST_TYPE DEST_NUM TRANS_AMT TRANS_CODE Position space 11-16 space 17-22 space 23-28 space 29-34 space 35-40 space 41-46 space 47-55 Format 6-digit integer 6-digit integer 6-digit integer 6-digit integer 6-digit integer decimal (xx.xxx) 9-digit integer F90 Format i6 i6 i6 i6 i6 f6.3 i9

40

SWAT USERS MANUAL, VERSION 2000

2.2.2.7 STRUCTURE COMMAND (12)

The structure command simulates aeration caused by the tumbling of water as it moves over weirs or other structures along the stream network. In highly polluted streams, the aeration of the stream by this method is a significant source of oxygen. The structure command alters the dissolved oxygen content based on the aeration coefficient input by the user. Variables required on the structure command line are: Variable name COMMAND HYD_STOR HYD_NUM Definition The command code = 12 for the structure command. The hydrograph storage location number for data. Inflow hydrograph storage location number. The data that is to be adjusted to reflect aeration. (Dissolved oxygen content is the only value that is altered with this command.) Aeration coefficient. Butts and Evans (1983) documents the following relationship that can be used to estimate the reaeration coefficient:

AERATION_COEF

rea = 1 + 0.38 coef a coef b h fall (1 0.11 h fall ) (1 + 0.046 Twater ) where rea is the reaeration coefficient, coefa is an empirical water quality factor, coefb is an empirical dam aeration coefficient, hfall is the height through which water falls (m), and Twater is the average water temperature (C). The empirical water quality factor is assigned a value based on the condition of the stream:
coefa = 1.80 in clean water coefa = 1.60 in slightly polluted water coefa = 1.00 in moderately polluted water coefa = 1.00 in moderately polluted water coefa = 0.65 in grossly polluted water

The empirical dam aeration coefficient is assigned a value based on the type of structure:
coefb = 0.70 to 0.90 for flat broad crested weir coefb = 1.05 for sharp crested weir with straight slope face coefb = 0.80 for sharp crested weir with vertical face coefb = 0.05 for sluice gates with submerged discharge

CHAPTER 2: SWAT INPUTWATERSHED CONFIGURATION

41

The format of the structure command is:

Variable name COMMAND HYD_STOR HYD_NUM AERATION_COEF Position space 11-16 space 17-22 space 23-28 space 41-46 Format 6-digit integer 6-digit integer 6-digit integer decimal (xx.xxx) F90 Format i6 i6 i6 f6.3

42

SWAT USERS MANUAL, VERSION 2000

2.2.2.8 RECMON COMMAND (7)

The recmon command is one of five routing commands that reads in flow, sediment and chemical loading records from a file and routes the input through the watershed. The recmon command is used to read in data summarized by month. The recmon command requires two lines. Variables required on the recmon command lines are:
Variable name Definition

COMMAND HYD_STOR FILEMON_NUM

The command code = 7 for the recmon command. The hydrograph storage location number for data. The file number. Unique file numbers should be used for each recmon command. Name of the file containing the monthly records

DRAINAGE_AREA Drainage area associated with records (km2) (optional) FILE_MON

The format of the recmon command lines is:

Variable name COMMAND HYD_STOR FILEMON_NUM DRAINAGE_AREA FILE_MON Line # 1 1 1 1 2 Position space 11-16 space 17-22 space 23-28 space 41-46 space 11-23 Format 6-digit integer 6-digit integer 6-digit integer decimal (xx.xxx) character F90 Format i6 i6 i6 f6.3 a13

CHAPTER 2: SWAT INPUTWATERSHED CONFIGURATION

43

2.2.2.9 RECYEAR COMMAND (8)

The recyear command is one of five routing commands that reads in flow, sediment and chemical loading records from a file and routes the input through the watershed. The recyear command is used to read in annual output. The recyear command requires two lines. Variables required on the recyear command lines are:
Variable name Definition

COMMAND HYD_STOR FILEYR_NUM

The command code = 8 for the recyear command. The hydrograph storage location number for data. The file number. Unique file numbers should be used for each recyear command. Name of file containing annual output.

DRAINAGE_AREA Drainage area associated with records (km2) (optional) FILE_YR

The format of the recyear command lines is:

Variable name COMMAND HYD_STOR FILEYR_NUM DRAINAGE_AREA FILE_YR Line # 1 1 1 1 2 Position space 11-16 space 17-22 space 23-28 space 41-46 space 11-23 Format 6-digit integer 6-digit integer 6-digit integer decimal(xx.xxx) character F90 Format i6 i6 i6 f6.3 a13

44

SWAT USERS MANUAL, VERSION 2000

2.2.2.10 RECDAY COMMAND (10)

The recday command is one of four routing commands that reads in flow, sediment and chemical loading records from a file and routes the input through the watershed. This command is useful for reading in point source data or data from simulations of upstream areas. The recday command is used to read in data summarized on a daily basis. The recday command requires two lines. Variables required on the recday command lines are:
Variable name Definition

COMMAND HYD_STOR FILEDAY_NUM

The command code = 10 for the recday command. The hydrograph storage location number for data. The file number. Unique file numbers should be used for each recday command. Name of file containing daily records.

DRAINAGE_AREA Drainage area associated with records (km2) (optional) FILE_DAY

The format of the recday command lines is:

Variable name COMMAND HYD_STOR FILEDAY_NUM DRAINAGE_AREA FILE_DAY Line # 1 1 1 1 2 Position space 11-16 space 17-22 space 23-28 space 41-46 space 11-23 Format 6-digit integer 6-digit integer 6-digit integer decimal (xx.xxx) character F90 Format i6 i6 i6 f6.3 a13

CHAPTER 2: SWAT INPUTWATERSHED CONFIGURATION

45

2.2.2.11 RECCNST COMMAND (11)

The reccnst command is one of five routing commands that reads in flow, sediment and chemical loading records from a file and routes the input through the watershed. This command is useful for reading in point source data. The reccnst command is used to read in average annual data. The reccnst command requires two lines. Variables required on the reccnst command lines are:
Variable name Definition

COMMAND HYD_STOR FILECNST_NUM

The command code = 11 for the reccnst command. The hydrograph storage location number for data. The file number. Unique file numbers should be used for each reccnst command. Name of file containing average annual records.

DRAINAGE_AREA Drainage area associated with records (km2) (optional) FILE_CNST

The format of the reccnst command lines is:

Variable name COMMAND HYD_STOR FILECNST_NUM DRAINAGE_AREA FILE_CNST Line # 1 1 1 1 2 Position space 11-16 space 17-22 space 23-28 space 41-46 space 11-23 Format 6-digit integer 6-digit integer 6-digit integer decimal(xx.xxx) character F90 Format i6 i6 i6 f6.3 a13

46

SWAT USERS MANUAL, VERSION 2000

2.2.2.12 SAVE COMMAND (9)

The save command allows the user to print daily SWAT output to the event output file specified in file.cio. This output file can then be read into another SWAT run using the recday command. Variables required on the save command line are:
Variable name Definition

COMMAND HYD_NUM

The command code = 9 for save command. The hydrograph storage location number of the data to be printed to file.

The format of the save command line is:

Variable name COMMAND HYD_NUM Position space 11-16 space 17-22 Format 6-digit integer 6-digit integer F90 Format i6 i6

CHAPTER 2: SWAT INPUTWATERSHED CONFIGURATION

47

2.2.2.13 SAVECONC COMMAND (14)

The saveconc command saves flow, sediment and water quality indicator information from a specified point on the reach network to a file. The water quality information is reported as concentrations. This command is useful for isolating reach information at a particular point on the channel network. Up to 50 saveconc commands can be specified in the watershed configuration file. The saveconc command requires two lines. Variables required on the saveconc command lines are:
Variable name Definition

COMMAND HYD_NUM FILECONC_NUM PRINT_FREQ

The command code = 14 for the saveconc command. The hydrograph storage location number of the data to be printed to file. The file number. Unique file numbers should be used for each saveconc command. Printing frequency. For simulations using a sub-daily time step, water quality information may be summarized and printed for every hour or every day. Simulations using a daily time step will always print daily average values. 0 report daily averages 1 report hourly averages (currently not operational) If no printing frequency is specified, the model will print daily averages.

FILE_CONC

Name of file to which the water quality information is written.

The format of the saveconc command lines is:

Variable name COMMAND HYD_NUM FILECONC_NUM PRINT_FREQ FILE_CONC Line # 1 1 1 1 2 Position space 11-16 space 17-22 space 23-28 space 29-34 space 11-23 Format 6-digit integer 6-digit integer 6-digit integer 6-digit integer character F90 Format i6 i6 i6 i6 a13

48

SWAT USERS MANUAL, VERSION 2000

2.3 REFERENCES
Arnold, J.G., J.R. Williams, A.D. Nicks, and N.B. Sammons. 1990. SWRRB, a basin scale simulation model for soil and water resources management. Texas A&M University Press, College Station, TX. Beasley, D.B., L.F. Huggins, and E.J. Monke. 1980. ANSWERS: A model for watershed planning. Trans. of the ASAE 23(4): 938-944. Butts, T.A. and R.L. Evans. 1983. Small stream channel dam aeration characteristics. Journal, Environmental Engineering Division, ASAE 109:555-573. Foster, G.R. 1987. User requirements: USDA-Water erosion prediction project. Lane, L.J. and M.A. Nearing (ed.). 1989. USDA-Water erosion prediction project: hillslope profile model documentation. NSERL Report No. 2. National Soil Erosion Research Laboratory. USDA-Agricultural Research Service. W. Lafayette, IN. Williams, J.R. J.G. Arnold, R. Srinivasan, and T.S. Ramanarayanan. 1998. Chapter 33. APEX: a new tool for predicting the effects of climate and CO2 changes on erosion and water quality. p. 441-449. In J. Boardman and D. Favis-Mortlock (ed.) Modeling soil erosion by water. Springer-Verlag, Berlin. Williams, J.R. and R.W. Hann. 1973. HYMO: Problem oriented computer language for hydrologic modeling. USDA ARS-S-9. 76 pp. Young, R.A. et al. 1987. AGNPS, Agricultural non-point source pollution model: a watershed analysis tool. USDA Agricultural Research Service.

CHAPTER 3

SWAT INPUT DATA:

FILE.CIO

File management is performed with the control input/output file (file.cio). The control input/output file contains the name of files associated with the subbasins, database files, climate files and watershed-level input files accessed by SWAT during a simulation as well as the name of the files in which output will be stored. While the user may adopt any file naming scheme, we recommend that the file extensions listed in the manual are used to facilitate identification of the different file types. Files required by the model that are not listed in the control input/output file include HRU files listed in the subbasin general input (.sub) file, reservoir and
49

50

SWAT USER'S MANUAL, VERSION 2000

point source input files listed in the watershed configuration (.fig) file and "unique" files which contain input for uncommon or specialized processes not typically simulated. The control input/output file can be divided into a number of different sections. Figure 3.1 illustrates the different groupings of files within file.cio.

Figure 3.1: General organization of control input/output files

Following is a brief description of the variables in the control input/output file. They are listed in the order they appear within the file.

3.1 TITLE SECTION

Variable name TITLE Definition The first three lines of file.cio are reserved for a description of the simulation run. The description may take up to 80 spaces per line. The title given in file.cio is printed to every output file. (optional)

CHAPTER 3:SWAT INPUTFILE.CIO

51

3.2 GENERAL INPUT/OUTPUT SECTION

Variable name BIGSUB Definition Name of subbasin output file (.bsb). Loadings to the reach (water, sediment and nutrients) are summarized for each subbasin. Name of hydrologic response unit (HRU) output file (.sbs). Loadings to the reach (water, sediment and nutrients) and crop growth are summarized for each HRU. Name of main channel, or reach, output file (.rch). Summarizes the amount of water, sediment and pollutants entering and leaving the reach and provides data on in-steam processes (e.g. sediment deposition, evaporation occurring in the channel) Name of reservoir output file (.rsv). Summarizes the amount of water, sediment and pollutants entering and leaving the reservoir and quantifies processes occurring in the reservoir (e.g. sediment deposition). Name of subbasin/HRU impoundment output file (.wtr). Summarizes the amount of water, sediment and pollutants entering and leaving ponds, wetlands and depressional areas (potholes) and quantifies processes occurring in the different impoundments. Name of pesticide output file (.pso). The movement and transformation of the different pesticides used in the simulation are summarized for each HRU. Name of event output file (.eve). When very large basins are being simulated, it is often easier to split them into several SWAT runs. This file writes daily output which can be read into a different SWAT run. Name of watershed configuration file (.fig). Contains the commands to add and route flows through the watershed. Name of input control code file (.cod). The input control code file summarizes information that affects the operation of SWAT (e.g. print codes, weather generator codes, number of years being simulated, number of subbasins being simulated) Name of basin input file (.bsn). Contains inputs for processes modeled at the watershed level. Name of watershed water quality input file (.wwq)

SBSOUT

RCHOUT

RSVOUT

WTROUT

PESTOUT

EVENT

ROUTIN CODEDAT

BASNDAT WATQAL

52

SWAT USER'S MANUAL, VERSION 2000

Variable name CROPDB

Definition Name of land cover/plant growth database file (crop.dat). This file contains growth parameters for the different land covers. Name of tillage database file (till.dat). This file contains mixing efficiencies for different tillage implements. Name of pesticide database file (pest.dat). This file contains parameters governing movement and degradation of pesticides. Name of fertilizer/manure database file (fert.dat). This file contains nutrient content data for fertilizers. Name of urban land type database file (urban.dat). This file contains data required to model build-up/wash-off in urban areas.

TILLDAT PESTIDAT

FERTDAT URBDAT

3.3 CLIMATE INPUT SECTION

Variable name NRGAGE NTGAGE NRTOT Definition Number of precipitation gage (.pcp) files used in the simulation. Up to 18 files may be used. Number of temperature gage (.tmp) files used in the simulation. Up to 18 files may be used. Total number of precipitation gage records used in the simulation. If each .pcp file contains only one precipitation gage record, NRTOT = NRGAGE. Otherwise, NRTOT > NRGAGE. A maximum of 5400 precipitation gage records may be used in a simulation. Total number of temperature gage records used in the simulation. If each .tmp file contains only one temperature gage record, NTTOT = NTGAGE. Otherwise, NTTOT > NTGAGE. A maximum of 2700 temperature gage records may be used in a simulation. Number of precipitation gage records within each .pcp file. A maximum of 300 precipitation gage records may be placed in each .pcp file. Number of temperature gage records within each .tmp file. a maximum of 150 temperature gage records may be placed in each .tmp file

NTTOT

NRGFIL

NTGFIL

CHAPTER 3:SWAT INPUTFILE.CIO

53

Variable name NSTOT

Definition Number of solar radiation records within the .slr file. A maximum of 300 solar radiation records may be placed in the .slr file. Number of relative humidity records within the .hmd file. A maximum of 300 relative humidity records may be placed in the .hmd file. Number of wind speed records within the .wnd file. A maximum of 300 wind speed records may be placed in the .wnd file. Name of measured precipitation input file #1 (.pcp). Name of measured precipitation input file #2 (.pcp). Name of measured precipitation input file #3 (.pcp). Name of measured precipitation input file #4 (.pcp). Name of measured precipitation input file #5 (.pcp). Name of measured precipitation input file #6 (.pcp). Name of measured precipitation input file #7 (.pcp). Name of measured precipitation input file #8 (.pcp). Name of measured precipitation input file #9 (.pcp). Name of measured precipitation input file #10 (.pcp). Name of measured precipitation input file #11 (.pcp). Name of measured precipitation input file #12 (.pcp). Name of measured precipitation input file #13 (.pcp). Name of measured precipitation input file #14 (.pcp). Name of measured precipitation input file #15 (.pcp). Name of measured precipitation input file #16 (.pcp). Name of measured precipitation input file #17 (.pcp). Name of measured precipitation input file #18 (.pcp). Name of measured temperature input file #1 (.tmp). Name of measured temperature input file #2 (.tmp). Name of measured temperature input file #3 (.tmp). Name of measured temperature input file #4 (.tmp). Name of measured temperature input file #5 (.tmp).

NHTOT

NWTOT

RFILE(1) RFILE(2) RFILE(3) RFILE(4) RFILE(5) RFILE(6) RFILE(7) RFILE(8) RFILE(9) RFILE(10) RFILE(11) RFILE(12) RFILE(13) RFILE(14) RFILE(15) RFILE(16) RFILE(17) RFILE(18) TFILE(1) TFILE(2) TFILE(3) TFILE(4) TFILE(5)

54

SWAT USER'S MANUAL, VERSION 2000

Variable name TFILE(6) TFILE(7) TFILE(8) TFILE(9) TFILE(10) TFILE(11) TFILE(12) TFILE(13) TFILE(14) TFILE(15) TFILE(16) TFILE(17) TFILE(18) SLRFILE RHFILE WNDFILE PETFILE

Definition Name of measured temperature input file #6 (.tmp). Name of measured temperature input file #7 (.tmp). Name of measured temperature input file #8 (.tmp). Name of measured temperature input file #9 (.tmp). Name of measured temperature input file #10 (.tmp). Name of measured temperature input file #11 (.tmp). Name of measured temperature input file #12 (.tmp). Name of measured temperature input file #13 (.tmp). Name of measured temperature input file #14 (.tmp). Name of measured temperature input file #15 (.tmp). Name of measured temperature input file #16 (.tmp). Name of measured temperature input file #17 (.tmp). Name of measured temperature input file #18 (.tmp). Name of measured solar radiation input file (.slr). Name of measured relative humidity input file (.hmd). Name of measured wind speed input file (.wnd). Name of potential evapotranspiration input file (.pet).

3.4 SUBBASIN INPUT SECTION

Variable name ISB SUBDAT RTEDAT PNDDAT WUSDAT WGNDAT SWQDAT Definition Subbasin number. Subbasins are numbered consecutively. Name of subbasin general input data file (.sub). Name of subbasin routing input data file (.rte). This file contains parameters for the main channel. Name of subbasin pond input data file (.pnd). Name of subbasin water use management data file (.wus). Name of subbasin weather generator data file (.wgn). Name of subbasin stream water quality data file (.swq).

CHAPTER 3:SWAT INPUTFILE.CIO

55

Variable name IRGAGE ITGAGE ISGAGE IHGAGE IWGAGE

Definition Number of the measured precipitation record used within subbasin. Optional. Number of the measured temperature record used within the subbasin. Optional. Number of the solar radiation record used within the subbasin. Optional. Number of the relative humidity record used within the subbasin. Optional. Number of the wind speed record used within the subbasin. Optional.

56

SWAT USER'S MANUAL, VERSION 2000

The format of file.cio is:

Variable name TITLE BIGSUB SBSOUT RCHOUT RSVOUT empty location WTROUT PESTOUT EVENT ROUTIN CODEDAT BASNDAT WATQAL CROPDB TILLDAT PESTIDAT FERTDAT URBDAT NRGAGE NTGAGE NRTOT NTTOT NRGFIL NTGFIL NSTOT NHTOT NWTOT RFILE(1) RFILE(2) RFILE(3) RFILE(4) RFILE(5) Line # 1-3 4 4 4 4 4 4 5 5 5 5 5 5 6 6 6 6 6 7 7 7 7 7 7 7 7 7 8 8 8 8 8 Position space 1-80 space 1-13 space 14-26 space 27-39 space 40-52 space 53-65 space 66-78 space 1-13 space 14-26 space 27-39 space 40-52 space 53-65 space 66-78 space 1-13 space 14-26 space 27-39 space 40-52 space 53-65 space 1-4 space 5-8 space 9-12 space 13-16 space 17-20 space 21-24 space 25-28 space 29-32 space 33-36 space 1-13 space 14-26 space 27-39 space 40-52 space 53-65 Format character character character character character character character character character character character character character character character character character character integer integer integer integer integer integer integer integer integer character character character character character F90 Format a80 a13 a13 a13 a13 a13 a13 a13 a13 a13 a13 a13 a13 a13 a13 a13 a13 a13 i4 i4 i4 i4 i4 i4 i4 i4 i4 a13 a13 a13 a13 a13

CHAPTER 3:SWAT INPUTFILE.CIO Variable name RFILE(6) RFILE(7) RFILE(8) RFILE(9) RFILE(10) RFILE(11) RFILE(12) RFILE(13) RFILE(14) RFILE(15) RFILE(16) RFILE(17) RFILE(18) TFILE(1) TFILE(2) TFILE(3) TFILE(4) TFILE(5) TFILE(6) TFILE(7) TFILE(8) TFILE(9) TFILE(10) TFILE(11) TFILE(12) TFILE(13) TFILE(14) TFILE(15) TFILE(16) TFILE(17) TFILE(18) SLRFILE RHFILE WNDFILE PETFILE Line # 8 9 9 9 9 9 9 10 10 10 10 10 10 11 11 11 11 11 11 12 12 12 12 12 12 13 13 13 13 13 13 14 14 14 14 Position space 66-78 space 1-13 space 14-26 space 27-39 space 40-52 space 53-65 space 66-78 space 1-13 space 14-26 space 27-39 space 40-52 space 53-65 space 66-78 space 1-13 space 14-26 space 27-39 space 40-52 space 53-65 space 66-78 space 1-13 space 14-26 space 27-39 space 40-52 space 53-65 space 66-78 space 1-13 space 14-26 space 27-39 space 40-52 space 53-65 space 66-78 space 1-13 space 14-26 space 27-39 space 40-52 Format character character character character character character character character character character character character character character character character character character character character character character character character character character character character character character character character character character character F90 Format a13 a13 a13 a13 a13 a13 a13 a13 a13 a13 a13 a13 a13 a13 a13 a13 a13 a13 a13 a13 a13 a13 a13 a13 a13 a13 a13 a13 a13 a13 a13 a13 a13 a13 a13

57

58

SWAT USER'S MANUAL, VERSION 2000 Line # Position Format F90 Format

Variable name

The remaining lines provide input data for all of the subbasins. Two lines are devoted to each subbasin's input data. In the equation for the line number, i is the subbasin number. ISB SUBDAT RTEDAT PNDDAT WUSDAT WGNDAT SWQDAT IRGAGE ITGAGE ISGAGE IHGAGE IWGAGE 13 + 2i 13 + 2i 13 + 2i 13 + 2i 13 + 2i 14 + 2i 14 + 2i 14 + 2i 14 + 2i 14 + 2i 14 + 2i 14 + 2i space 1-5 space 7-19 space 21-33 space 35-47 space 49-61 space 7-19 space 21-33 space 49-52 space 53-56 space 57-60 space 61-64 space 65-68 integer character character character character character character integer integer integer integer integer i5 a13 a13 a13 a13 a13 a13 i4 i4 i4 i4 i4

CHAPTER 4

SWAT INPUT DATA:

.COD

The input control code file regulates the general operation of SWAT. In addition to setting output file formats, the input control code file defines which processes are/are not modeled in the SWAT simulation.

59

60

SWAT USER'S MANUAL, VERSION 2000

Following is a brief description of the variables in the input control file. They are listed in the order they appear within the file. Variable name TITLE Definition The first line of the .cod file is reserved for user comments. The comments may take up to 80 spaces. The title is never used by the model and is an optional input. Number of calendar years simulated. The number of years simulated in a SWAT run can vary from 1 to 9,999 years. If a simulation is begun on August 1st of the year 1995 and ends July 30th of the year 1997, the model will be simulating 3 calendar years (1995, 1996 and 1997). IYR Beginning year of simulation (for example, 1980). The value entered for this variable is not important unless measured data (e.g. weather) is used in the run. When measured data is used, the model uses this variable to locate the beginning year within the data file. Beginning julian day of simulation. With this variable, SWAT is able to begin a simulation at any time of the year. If the variable is left blank or set to zero, the model starts the simulation on January 1st. Ending julian day of simulation. With this variable, SWAT will end the simulation on the date specified. If the variable is left blank or set to zero, the model ends the simulation on December 31st. Print code. This variable governs the frequency that model results are printed to output files. There are three options: 0 1 2 Monthly Daily Annually

NBYR

IDAF

IDAL

IPD

If you choose to print results on a daily basis, the number of years simulated should be limited and/or the variables printed to the output file should be restricted. If these precautions are not taken, the output files will be too large to view.

CHAPTER 4:SWAT INPUT.COD FILE

61

Variable name NYSKIP

Definition Number of years to not print output. The options are 0 print output for all years of the simulation 1 print output after the first year of simulation 2 print output after the second year of simulation $ nbyr no output will be printed Some simulations will need a warm-up or equilibration period. The use of an equilibration period becomes more important as the simulation period of interest shortens. For 30-year simulations, an equilibrium period is optional. For a simulation covering 5 years or less, an equilibrium period is recommended. An equilibration period of one year is usually adequate to get the hydrologic cycle fully operational. NYSKIP allows the user to exclude data generated during the equilibration period from output summaries. In addition to not writing data to the output files, annual averages are not computed for the skipped years. Averages for the entire simulation period will also exclude data from the skipped years. The default value for NYSKIP is 0.

IPRN

Print code for input.std file. There are two options: 0 1 entire input.std file is printed condensed version of input.std file is printed

ILOG

Streamflow print code. This variable allows the user to take the log10 of the flow prior to printing streamflow values to the .rch file. There are two options: 0 1 print streamflow in .rch file print log of streamflow in .rch file

In large basins (for example, the Mississippi River basin), streamflow values printed to the .rch file may exceed the range allowed by the file format statements. This variable will eliminate print errors caused by very large values. IPRP Print code for .pso file. There are two options: 0 1 do not print pesticide output (.pso file will be empty) print pesticide output

62

SWAT USER'S MANUAL, VERSION 2000

Variable name IGN

Definition 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. This is done by setting 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.

PCPSIM

Rainfall input code. This variable identifies the method the model will use to process rainfall data. There are two options: 1 measured data read for each subbasin 2 rainfall generated for each subbasin If observed rainfall data is available for a watershed, the user should read in the measured data.

IDT

Time step used to report measured rainfall data (minutes). Required if IEVENT = 2 or 3. One of the following should be chosen: 1 min, 2 min, 3 min, 4 min, 5 min, 6 min, 10 min, 12 min, 15 min, 20 min, 30 min. Rainfall distribution code. There are two options: 0 1 skewed distribution mixed exponential distribution

IDIST

REXP

Value of exponent for mixed exponential rainfall distribution. A value for REXP is needed only if IDIST = 1. The model will set REXP = 1.3 if no value is entered.

CHAPTER 4:SWAT INPUT.COD FILE

63

Variable name TMPSIM

Definition Temperature input code. This variable identifies the method the model will use to process temperature data. There are two options: 1 2 measured date read for each subbasin daily max/min generated for each subbasin

If observed temperature data is available for the watershed, the user should read in the measured data. SLRSIM Solar radiation input code. This variable identifies the method the model will use to process solar radiation data. There are two options: 1 2 measured data read for each subbasin solar radiation generated for each subbasin

SWAT2000 is the first version that allows solar radiation data to be read into the model. This allows users to use recorded data or import values generated with an independent weather generator. The default or recommended option is #2allow SWAT to generate solar radiation values. RHSIM Relative humidity input code. This variable identifies the method the model will use to process relative humidity data. There are two options: 1 2 measured data read for each subbasin relative humidity generated for each subbasin

SWAT2000 is the first version that allows relative humidity data to be read into the model. This allows users to use recorded data or import values generated with an independent weather generator. The default or recommended option is #2allow SWAT to generate relative humidity values. WNDSIM Wind speed input code. This variable identifies the method the model will use to process wind speed data. There are two options: 1 2 measured data read for each subbasin wind speed generated for each subbasin

SWAT2000 is the first version that allows wind speed data to be read into the model. This allows users to use recorded data or import values generated with an independent weather generator.

64

SWAT USER'S MANUAL, VERSION 2000

Variable name WNDSIM, cont. IPET

Definition The default or recommended option is #2allow SWAT to generate wind speed values. Potential evapotranspiration (PET) method. There are four options for potential ET calculations: 0 1 2 3 Priestley-Taylor method Penman/Monteith method Hargreaves method read in potential ET values

Numerous methods exist to calculate potential evapotranspiration. Three of the most popular or widelyused 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 read them into SWAT. A discussion of Priestley-Taylor, Penman-Monteith and Hargreaves PET methods is found in Chapter 7 of the theoretical documentation. IEVENT Rainfall/runoff/routing option: 0 1 daily rainfall/curve number runoff/daily routing daily rainfall/Green & Ampt runoff/daily routing (sub-hourly rainfall required for Green & Ampt is generated from daily) this option not yet operational 2 sub-hourly rainfall/Green & Ampt runoff/daily routing 3 sub-hourly rainfall/Green & Ampt runoff/hourly routing Option 0 was the only active option in prior versions of the model and is the default. Option 3, hourly routing, should be considered in the testing phase. ICRK Crack flow code. There are two options: 0 1 do not model crack flow in soil 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.

CHAPTER 4:SWAT INPUT.COD FILE

65

Variable name IRTE

Definition Channel water routing method: 0 1 variable storage method Muskingum method

The default option is IRTE=0. The Muskingum method is a new option available with SWAT2000. The user must be careful to define MSK_CO1, MSK_CO2 and MSK_X (in .bsn) when the Muskingum method is chosen. IDEG 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) 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. IWQ In-stream water quality code. The variable identifies whether in-stream transformation of nutrients using the QUAL2E algorithms is allowed to occur. 0 1 ISPROJ do not model in-stream nutrient transformations model in-stream nutrient transformations

The default option is IWQ=0. Special project flag. SWAT includes sections of code specific to particular projects. This variable flags the code used in the particular simulation. There are three options: 0 1 2 not a special project HUMUS project Missouri River climate change project

A user will set this variable to something other than zero only if the SWAT programmers have told him to do so. For long runs, the output files can get so large that the user may have difficulty in opening the files to look at output. The user has the option of customizing the output printed to the output files. Lines of the .cod file are used to specify the variables to be printed to the reach output file (.rch), the subbasin

66

SWAT USER'S MANUAL, VERSION 2000

output file (.bsb), and the HRU output file (.sbs). If these lines contain only zeros, the model will print all the output variables to the file. Variable name IPDVAR(:) Definition Output variables printed to the .rch file. (up to 20 variables may be chosen in customized output.) The codes for the output variables are:
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 FLOW_IN: Average daily streamflow into reach (m3/s) FLOW_OUT: Average daily streamflow out of reach (m3/s) EVAP: Average daily loss of water from reach by evaporation (m3/s) TLOSS: Average daily loss of water from reach by transmission (m3/s) SED_IN: Sediment transported with water into reach (metric tons) SED_OUT: Sediment transported with water out of reach (metric tons) SEDCONC: Concentration of sediment in reach (mg/L) ORGN_IN: Organic nitrogen transported with water into reach (kg N) ORGN_OUT: Organic nitrogen transported with water out of reach (kg N) ORGP_IN: Organic phosphorus transported with water into reach (kg P) ORGP_OUT: Organic phosphorus transported with water out of reach (kg P) NO3_IN: Nitrate transported with water into reach (kg N) NO3_OUT: Nitrate transported with water out of reach (kg N) NH4_IN: Ammonium transported with water into reach (kg N) NH4_OUT: Ammonium transported with water out of reach (kg N) NO2_IN: Nitrite transported with water into reach (kg N) NO2_OUT: Nitrite transported with water out of reach (kg N) MINP_IN: Mineral phosphorus transported with water into reach (kg P) MINP_OUT: Mineral phosphorus transported with water out of reach (kg P) CHLA_IN: Chlorophyll-a transported with water into reach (kg) CHLA_OUT: Chlorophyll-a transported with water out of reach (kg) CBOD_IN: Carbonaceous biochemical oxygen demand transported into reach (kg O2) CBOD_OUT: Carbonaceous biochemical oxygen demand transported out of reach (kg O2) DISOX_IN: Dissolved oxygen transported into reach (kg O2) DISOX_OUT: Dissolved oxygen transported out of reach (kg O2) SOLPST_IN: Soluble pesticide transported with water into reach (mg a.i.) SOLPST_OUT: Soluble pesticide transported with water out of reach (mg a.i.) SORPST_IN: Pesticide sorbed to sediment transported with water into reach (mg a.i.) SORPST_OUT: Pesticide sorbed to sediment transported with water out of reach (mg a.i.)

CHAPTER 4:SWAT INPUT.COD FILE

67

Variable name

Definition
continued from previous page: 30 REACTPST: Loss of pesticide from water by reaction (mg a.i.) 31 VOLPST: Loss of pesticide from water by volatilization (mg a.i.) 32 SETTLPST: Transfer of pesticide from water to river bed sediment by settling (mg a.i.) 33 RESUSP_PST: Transfer of pesticide from river bed sediment to water by resuspension (mg a.i.) 34 DIFFUSEPST: Transfer of pesticide from water to river bed sediment by diffusion (mg a.i.) 35 REACBEDPST: Loss of pesticide from river bed sediment by reaction (mg a.i.) 36 BURYPST: Loss of pesticide from river bed sediment by burial (mg a.i.) 37 BED_PST: Pesticide in river bed sediment (mg a.i.) 38 BACTP_OUT: Number of persistent bacteria transported out of reach 39 BACTLP_OUT: Number of less persistent bacteria transported out of reach 40 CMETAL#1: Conservative metal #1 transported out of reach (kg) 41 CMETAL#2: Conservative metal #2 transported out of reach (kg) 42 CMETAL#3: Conservative metal #3 transported out of reach (kg)

IPDVAB(:)

Output variables printed to the .bsb file (up to 15 variables may be chosen in customized output.) The codes for the output variables are:
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 PRECIP: Average total precipitation on subbasin (mm H2O) SNOMELT: Snow melt (mm H2O) PET: Potential evapotranspiration (mm H2O) ET: Actual evapotranspiration (mm H2O) SW: Soil water content (mm H2O) PERC: Amount of water percolating out of root zone (mm H2O) SURQ: Surface runoff (mm H2O) GW_Q: Groundwater discharge into reach (mm H2O) WYLD: Net water yield to reach (mm H2O) SYLD: Sediment yield (metric tons/ha) ORGN: Organic N released into reach (kg/ha) ORGP: Organic P released into reach (kg/ha) NSURQ: Nitrate released into reach (kg/ha) SOLP: Soluble P released into reach (kg/ha) SEDP: Mineral P attached to sediment released into reach (kg/ha)

IPDVAS(:)

Output variables printed to the .sbs file (up to 20 variables may be chosen in customized output.) The codes for the output variables are:
1 2 3 4 5 6 PRECIP: Total precipitation on HRU (mm H2O) SNOFALL: Precipitation falling as snow, sleet, or freezing rain (mm H2O) SNOMELT: Amount of snow or ice melting (mm H2O) IRR: Amount of irrigation water applied to HRU (mm H2O) PET: Potential evapotranspiration (mm H2O) ET: Amount of water removed by evapotranspiration (mm H2O)

68

SWAT USER'S MANUAL, VERSION 2000

Variable name

Definition
continued from previous page: 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 SW: Soil water content at end of time period (mm H2O) PERC: Amount of water percolating out of the root zone (mm H2O) GW_RCHG: Amount of water entering both aquifers (mm H2O) DA_RCHG: Amount of water entering deep aquifer from root zone (mm H2O) REVAP: Water in shallow aquifer returning to root zone (mm H2O) SA_IRR: Amount of water removed from shallow aquifer for irrigation (mm H2O) DA_IRR: Amount of water removed from deep aquifer for irrigation (mm H2O) SA_ST: Amount of water in shallow groundwater storage at end of time period (mm H2O) DA_ST: Amount of water in deep groundwater storage at end of time period (mm H2O) SURQ: Surface runoff contribution to reach (mm H2O) TLOSS: Amount of water removed from tributary channels by transmission (mm H2O) LATQ: Lateral flow contribution to reach (mm H2O) GW_Q: Groundwater discharge into reach (mm H2O) WYLD: Net amount of water contributed by the HRU to the reach (mm H2O) SYLD: Amount of sediment contributed by the HRU to the reach (metric tons/ha) USLE: USLE soil loss (metric tons/ha) N_APP: Amount of N fertilizer applied (kg N/ha) P_APP: Amount of P fertilizer applied (kg P/ha) NAUTO: Amount of N fertilizer applied automatically (kg N/ha) PAUTO: Amount of P fertilizer applied automatically (kg P/ha) NGRZ: Nitrogen applied to HRU in grazing operation during time step (kg N/ha) PGRZ: Phosphorus applied to HRU in grazing operation during time step (kg P/ha) NRAIN: Nitrate added in rainfall (kg N/ha) NFIX: Amount of N fixed by legumes (kg N/ha) F-MN: Transformation of N from fresh organic to mineral pool (kg N/ha) A-MN: Transformation of N from active organic to mineral pool (kg N/ha) A-SN: Transformation of N from active organic to stable organic pool (kg N/ha) F-MP: Transformation of P from fresh organic to mineral pool (kg P/ha) AO-LP: Transformation of P from organic to labile pool (kg P/ha) L-AP: Transformation of P from labile to active mineral pool (kg P/ha) A-SP: Transformation of P from active mineral to stable mineral pool (kg P/ha) DNIT: Amount of N removed from soil by denitrification (kg N/ha) NUP: Nitrogen uptake by plants (kg N/ha)

CHAPTER 4:SWAT INPUT.COD FILE

69

Variable name

Definition
continued from previous page: 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 PUP: Phosphorus uptake by plants (kg P/ha) ORGN: Organic N contributed by HRU to reach (kg N/ha) ORGP: Organic P contributed by HRU to reach (kg P/ha) SEDP: Mineral P attached to sediment contributed by HRU to reach (kg P/ha) NSURQ: NO3 contributed by HRU in surface runoff to reach (kg N/ha) NLATQ: NO3 contributed by HRU in lateral flow to reach (kg N/ha) NO3L: NO3 leached below the soil profile (kg N/ha) NO3GW: NO3 contributed by HRU in groundwater flow to reach (kg N/ha) SOLP: Soluble phosphorus contributed by HRU in surface runoff to reach (kg P/ha) P_GW: Soluble phosphorus contributed by HRU in groundwater flow to reach (kg P/ha) W_STRS: Number of water stress days. TMP_STRS: Number of temperature stress days N_STRS: Number of nitrogen stress days. P_STRS: Number of phosphorus stress days. BIOM: Total plant biomass (metric tons/ha) LAI: Leaf area index YLD: Harvested yield (metric tons/ha) BACTP: Number of persistent bacteria in surface runoff (count) BACTLP: Number of less persistent bacteria in surface runoff (count)

The input control code file is a free format file. The variables may be placed in any position the user wishes on the line. Values for variables classified as integers should not include a decimal while values for variables classified as reals must contain a decimal. A blank space denotes the end of an input value and the beginning of the next value if there is another on the line
Variable name TITLE NBYR IYR IDAF IDAL IPD NYSKIP IPRN ILOG IPRP Line # 1 2 3 4 5 6 7 8 9 10 Format character integer integer integer integer integer integer integer integer integer F90 Format a80 free free free free free free free free free

70

SWAT USER'S MANUAL, VERSION 2000 Line # 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 29 29 29 29 29 29 29 29 29 29 29 29 29 29 29 29 Format integer integer integer integer real integer integer integer integer integer integer integer integer integer integer integer integer character integer integer integer integer integer integer integer integer integer integer integer integer integer integer integer integer integer F90 Format free free free free free free free free free free free free free free free free free a80 free free free free free free free free free free free free free free free free free

Variable name IGN PCPSIM IDT IDIST REXP TMPSIM SLRSIM RHSIM WNDSIM IPET IEVENT ICRK IRTE IDEG NO VARIABLE IWQ ISPROJ COMMENT LINE IPDVAR(1) IPDVAR(2) IPDVAR(3) IPDVAR(4) IPDVAR(5) IPDVAR(6) IPDVAR(7) IPDVAR(8) IPDVAR(9) IPDVAR(10) IPDVAR(11) IPDVAR(12) IPDVAR(13) IPDVAR(14) IPDVAR(15) IPDVAR(16) IPDVAR(17)

CHAPTER 4:SWAT INPUT.COD FILE Variable name IPDVAR(18) IPDVAR(19) IPDVAR(20) COMMENT LINE IPDVAB(1) IPDVAB(2) IPDVAB(3) IPDVAB(4) IPDVAB(5) IPDVAB(6) IPDVAB(7) IPDVAB(8) IPDVAB(9) IPDVAB(10) IPDVAB(11) IPDVAB(12) IPDVAB(13) IPDVAB(14) IPDVAB(15) COMMENT LINE IPDVAS(1) IPDVAS(2) IPDVAS(3) IPDVAS(4) IPDVAS(5) IPDVAS(6) IPDVAS(7) IPDVAS(8) IPDVAS(9) IPDVAS(10) IPDVAS(11) IPDVAS(12) IPDVAS(13) IPDVAS(14) IPDVAS(15) Line # 29 29 29 30 31 31 31 31 31 31 31 31 31 31 31 31 31 31 31 32 33 33 33 33 33 33 33 33 33 33 33 33 33 33 33 Format integer integer integer character integer integer integer integer integer integer integer integer integer integer integer integer integer integer integer character integer integer integer integer integer integer integer integer integer integer integer integer integer integer integer F90 Format free free free a80 free free free free free free free free free free free free free free free a80 free free free free free free free free free free free free free free free

71

72

SWAT USER'S MANUAL, VERSION 2000 Line # 33 33 33 33 33 Format integer integer integer integer integer F90 Format free free free free free

Variable name IPDVAS(16) IPDVAS(17) IPDVAS(18) IPDVAS(19) IPDVAS(20)

CHAPTER 5

SWAT INPUT DATA:

.BSN

General watershed attributes are defined in the basin input file. These attributes control a diversity of physical processes at the watershed level. With the exception of the watershed area, all parameters contained in this file will be set to the default or recommended values listed in the variable documentation if left blank. Variables governing bacteria or pesticide transport need to be initialized only if these processes are being modeled in the watershed.
73

74

SWAT USER'S MANUAL, VERSION 2000

Following is a brief description of the variables in the basin input file. They are listed in the order they appear within the file. Variable name TITLE Definition The first line is reserved for a description. The description may take up to 80 spaces. The title line is not processed by the model and may be left blank. Area of the watershed (km2) Snowfall temperature (C). Mean air temperature at which precipitation is equally likely to be rain as snow/freezing rain. The snowfall temperature should be between 5 C and 5 C. A default recommended for this variable is SFTMP = 1.0. Snow melt base temperature (C). The snow pack will not melt until the snow pack temperature exceeds a threshold value, Tmlt. The snow melt base temperature should be between 5 C and 5 C. A default recommended for this variable is SMTMP = 0.50. Melt factor for snow on June 21 (mm H2O/C-day). If the watershed is in the Northern Hemisphere, SMFMX will be the maximum melt factor. If the watershed is in the Southern Hemisphere, SMFMX will be the minimum melt factor. SMFMX and SMFMN allow the rate of snow melt to vary through the year. The variables account for the impact of snow pack density on snow melt. In rural areas, the melt factor will vary from 1.4 to 6.9 mm H2O/day-C (Huber and Dickinson, 1988). In urban areas, values will fall in the higher end of the range due to compression of the snow pack by vehicles, pedestrians, etc. Urban snow melt studies in Sweden (Bengston, 1981; Westerstrom, 1981) reported melt factors ranging from 3.0 to 8.0 mm H2O/day-C. Studies of snow melt on asphalt (Westerstrom, 1984) gave melt factors of 1.7 to 6.5 mm H2O/day-C. If no value for SMFMX is entered, the model will set SMFMX = 4.5.

DA_KM SFTMP

SMTMP

SMFMX

CHAPTER 5: SWAT INPUT.BSN

75

Variable name SMFMN

Definition Melt factor for snow on December 21 (mm H2O/C-day). If the watershed is in the Northern Hemisphere, SMFMN will be the minimum melt factor. If the watershed is in the Southern Hemisphere, SMFMN will be the maximum melt factor. SMFMX and SMFMN allow the rate of snow melt to vary through the year. The variables account for the impact of snow pack density on snow melt. In rural areas, the melt factor will vary from 1.4 to 6.9 mm H2O/day-C (Huber and Dickinson, 1988). In urban areas, values will fall in the higher end of the range due to compression of the snow pack by vehicles, pedestrians, etc. Urban snow melt studies in Sweden (Bengston, 1981; Westerstrom, 1981) reported melt factors ranging from 3.0 to 8.0 mm H2O/day-C. Studies of snow melt on asphalt (Westerstrom, 1984) gave melt factors of 1.7 to 6.5 mm H2O/day-C. If no value for SMFMN is entered, the model will set SMFMN = 4.5.

TIMP

Snow pack temperature lag factor. The influence of the previous days snow pack temperature on the current days snow pack temperature is controlled by a lagging factor, l sno . The lagging factor inherently accounts for snow pack density, snow pack depth, exposure and other factors affecting snow pack temperature. TIMP can vary between 0.01 and 1.0. As l sno approaches 1.0, the mean air temperature on the current day exerts an increasingly greater influence on the snow pack temperature and the snow pack temperature from the previous day exerts less and less influence. As TIMP goes to zero, the snow pack's temperature will be less influenced by the current day's air temperature. If no value for TIMP is entered, the model will set TIMP = 1.0.

SNOCOVMX

Minimum snow water content that corresponds to 100% snow cover, SNO100, (mm H2O). Due to variables such as drifting, shading and topography, the snow pack in a subbasin will rarely be uniformly distributed over the total area. This results in a fraction of the subbasin area that is bare of snow. This fraction must be quantified to accurately compute snow melt in the subbasin.

76

SWAT USER'S MANUAL, VERSION 2000

Variable name SNOCOVMX, cont.

Definition The factors that contribute to variable snow coverage are usually similar from year to year, making it possible to correlate the areal coverage of snow with the amount of snow present in the subbasin at a given time. This correlation is expressed as an areal depletion curve, which is used to describe the seasonal growth and recession of the snow pack as a function of the amount of snow present in the subbasin (Anderson, 1976). The areal depletion curve requires a threshold depth of snow, SNO100, to be defined above which there will always be 100% cover. The threshold depth will depend on factors such as vegetation distribution, wind loading of snow, wind scouring of snow, interception and aspect, and will be unique to the watershed of interest. If the snow water content is less than SNOCOVMX, then a certain percentage of ground cover will be bare. It is important to remember that once the volume of water held in the snow pack exceeds SNO100 the depth of snow over the HRU is assumed to be uniform, i.e. snocov = 1.0. The areal depletion curve affects snow melt only when the snow pack water content is between 0.0 and SNO100. Consequently if SNO100 is set to a very small value, the impact of the areal depletion curve on snow melt will be minimal. As the value for SNO100 increases, the influence of the areal depletion curve will assume more importance in snow melt processes. If no value for SNOCOVMX is entered, the model will set SNOCOVMX = 1.00.

SNO50COV

Fraction of snow volume represented by SNOCOVMX that corresponds to 50% snow cover. SWAT assumes a nonlinear relationship between snow water and snow cover. SNO50COV can vary between 0.01 and 0.99. Example areal depletion curves for various fractions of SNO100 at 50% coverage are shown in the following figures. If no value for SNO50COV is entered, the model will set SNO50COV = 0.50, i.e. 50% of SNOCOVMX.

CHAPTER 5: SWAT INPUT.BSN

1 0.9 0.8 Fraction areal coverage 0.7 0.6 0.5 0.4 0.3 0.2 0.1 0 0 0.1 0.2 0.3 0.4 0.5 0.6 0.7 0.8 0.9 1 Snow volume (fraction of SNO100 ) Fraction areal coverage 1 0.9 0.8 0.7 0.6 0.5 0.4 0.3 0.2 0.1 0 0 0.1 0.2 0.3 0.4 0.5 0.6 0.7 0.8 0.9 1 Snow volume (fraction of SNO100 )

77

Figure 5-1:10% SNO100 = 50% coverage

1

Figure 5-2: 30% SNO100 = 50%

coverage

0.9 0.8 Fraction areal coverage

Fraction areal coverage

0.9 0.8 0.7 0.6 0.5 0.4 0.3 0.2 0.1 0

0.7 0.6 0.5 0.4 0.3 0.2 0.1 0 0 0.1 0.2 0.3 0.4 0.5 0.6 0.7 0.8 0.9 1 Snow volume (fraction of SNO100 )

0.1

0.2

0.3

0.4

0.5

0.6

0.7

0.8

0.9

Snow volume (fraction of SNO100)

Figure 5-3: 50% SNO100 = 50% coverage

Figure 5-4: 70% SNO100 = 50% coverage

1 0.9 0.8 Fraction areal coverage 0.7 0.6 0.5 0.4 0.3 0.2 0.1 0 0 0.1 0.2 0.3 0.4 0.5 0.6 0.7 0.8 0.9 1

Snow volume (fraction of SNO100)

Figure 5-5: 90% SNO100 = 50% coverage

78

SWAT USER'S MANUAL, VERSION 2000

Variable name RCN SURLAG

Definition Concentration of nitrogen in rainfall (mg N/L). If no value for RCN is entered, the model will set RCN = 1.0. 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 5-6 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.

Figure 5-6: Influence of surlag and tconc on fraction of surface runoff released.

CHAPTER 5: SWAT INPUT.BSN

79

Variable name APM

PRF

SPCON

SPEXP

Definition 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 can 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 APM is entered, the model will set APM=1.0. 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 can 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. 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 spexp reach segment is calculated conc sed ,ch ,mx = c sp vch , pk 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. Exponent parameter for calculating sediment reentrained in channel sediment routing The maximum amount of sediment that can be transported from a spexp reach segment is calculated conc sed ,ch ,mx = c sp vch , pk 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.

80

SWAT USER'S MANUAL, VERSION 2000

Variable name EVRCH

Definition 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.

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). Evaporation from the water surface is allowed until the leaf area of the plant reaches the value specified for EVLAI. Chapter 27 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.

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).

CMN

Rate factor for humus mineralization of active organic nutrients (N and P). Chapters 10 and 11 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.

CHAPTER 5: SWAT INPUT.BSN

81

Variable name UBN

Definition 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 UBN is entered, the model will set UBN = 20.0. Figure 5-7 illustrates nitrogen uptake as a function of depth for four different uptake distribution parameter values.

Figure 5-7: Depth distribution of nitrogen uptake

82

SWAT USER'S MANUAL, VERSION 2000

Variable name UBP

Definition Phosphorus uptake distribution parameter. 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 5-7 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 UBP is entered, the model will set UBP = 20.0.

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.

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.

CHAPTER 5: SWAT INPUT.BSN

83

Variable name PHOSKD

Definition 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.

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 25C. 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.

84

SWAT USER'S MANUAL, VERSION 2000

Variable name PSP, cont.

Definition The P availability index is then calculated: P , Psolution ,i pai = solution f 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. 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.

RSDCO

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.

IRTPEST

Number of pesticide to be routed through the watershed channel network. This is the pesticide ID number from the pesticide database. While more than one type of pesticide may be applied to the HRUs, the model will monitor the movement of only one pesticide through the channel network.

WDPQ WGPQ WDLPQ WGLPQ

Die-off factor for persistent bacteria in soil solution. (1/day) Growth factor for persistent bacteria in soil solution. (1/day) Die-off factor for less persistent bacteria in soil solution. (1/day) Growth factor for less persistent bacteria in soil solution. (1/day)

CHAPTER 5: SWAT INPUT.BSN

85

Variable name WDPS WGPS WDLPS WGLPS BACTKDQ

Definition Die-off factor for persistent bacteria adsorbed to soil particles. (1/day) Growth factor for persistent bacteria adsorbed to soil particles. (1/day) Die-off factor for less persistent bacteria adsorbed to soil particles. (1/day) Growth factor for less persistent bacteria adsorbed to soil particles. (1/day) Bacteria partition coefficient. Partition coefficient for bacteria between soluble and sorbed phase in surface runoff. If no value for BACTKDQ is entered, the model will set BACTKDQ = 175.0.

THBACT

Temperature adjustment factor for bacteria die-off/growth. If no value for THBACT is entered, the model will set THBACT = 1.07.

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 in .cod file. 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 in .cod file. 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 in .cod file.

MSK_CO2

MSK_X

86

SWAT USER'S MANUAL, VERSION 2000

Variable name ESCO

Definition Soil evaporation compensation factor. This coefficient has been incorporated to allow the user to modify the depth distribution used to meet the soil evaporative demand to account for the effect of capillary action, crusting and cracks. ESCO must be between 0.01 and 1.0. As the value for ESCO is reduced, the model is able to extract more of the evaporative demand from lower levels. The change in depth distribution resulting from different values of esco are graphed in Figure 5-8.
E v a p o r a tio n a llo w e d w ith d e p th a s s u m in g 1 0 0 m m d e m a n d
3 5 .0 0

3 0 .0 0 Maximum Evaporation (mm H2O)

2 5 .0 0

2 0 .0 0

1 5 .0 0

1 0 .0 0

5 .0 0

0 .0 0 1 51 101 151 201 251 301 351 401 451 D e p t h (m m )

e s c o = 1 .0 e s c o = 0 .9 e s c o = 0 .8 e s c o = 0 .7

Figure 5-8: Soil evaporative demand distribution with depth

If no value for ESCO is entered, the model will set ESCO = 0.95. The value for ESCO may be set at the watershed or HRU level (ESCO in .hru).

CHAPTER 5: SWAT INPUT.BSN

87

Variable name EPCO

Definition Plant uptake compensation factor. The amount of water uptake that occurs on a given day is a function of the amount of water required by the plant for transpiration, Et, and the amount of water available in the soil, SW. If upper layers in the soil profile do not contain enough water to meet the potential water uptake, users may allow lower layers to compensate. The plant uptake compensation factor can range from 0.01 to 1.00. As epco approaches 1.0, the model allows more of the water uptake demand to be met by lower layers in the soil. As epco approaches 0.0, the model allows less variation from the original depth distribution to take place. If no value for EPCO is entered, the model will set EPCO = 1.0. The value for EPCO may be set at the watershed or HRU level (EPCO in .hru).

The basin input file is a free format file. The variables may be placed in any position the user wishes on the line. Values for variables classified as integers should not include a decimal while values for variables classified as reals must contain a decimal. A blank space denotes the end of an input value and the beginning of the next value if there is another on the line.
Variable name TITLE DA_KM BLANK LINE SFTMP SMTMP SMFMX SMFMN TIMP SNOCOVMX SNO50COV RCN SURLAG APM PRF SPCON Line # 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 Format character real real real real real real real real real real real real real real F90 Format a80 free free free free free free free free free free free free free free

88

SWAT USER'S MANUAL, VERSION 2000 Line # 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 Format real real real real real real real real real real real real real real real real real real integer real real real real real real real real real real real real real real real F90 Format free free free free free free free free free free free free free free free free free free free free free free free free free free free free free free free free free free

Variable name SPEXP BLANK LINE BLANK LINE BLANK LINE BLANK LINE BLANK LINE EVRCH EVLAI FFCB CMN UBN UBP NPERCO PPERCO PHOSKD PSP RSDCO PERCOP IRTPEST WDPQ WGPQ WDLPQ WGLPQ WDPS WGPS WDLPS WGLPS BACTKDQ THBACT MSK_CO1 MSK_CO2 MSK_X ESCO EPCO

CHAPTER 5: SWAT INPUT.BSN

89

REFERENCES
Anderson, E.A. 1976. A point energy and mass balance model of snow cover. NOAA Technical Report NWS 19, U.S. Dept. of Commerce, National Weather Service. Arnold, J.G., J.R. Williams and D.R. Maidment. 1995. Continuous-time water and sediment-routing model for large basins. Journal of Hydraulic Engineering 121(2):171-183. Barrow, N.J. and T.C. Shaw. 1975. The slow reactions between soil and anions. 2. Effect of time and temperature on the decrease in phosphate concentration in soil solution. Soil Sci. 119:167-177. Bengston, L. 1981. Snowmelt-generated runoff in urban areas. p. 444-451. In B.C. Yen (ed.) Urban stormwater hydraulics and hydrology: proceedings of the Second International Conference on Urban Storm Drainage, held at Urbana, Illinois, USA, 15-19 June 1981. Water Resources Publications, Littleton, CO. Huber, W.C. and R.E. Dickinson. 1988. Storm water management model, version 4: users manual. U.S. Environmental Protection Agency, Athens, GA. Jones, C.A. C.V. Cole, A.N. Sharpley, and J.R. Williams. 1984. A simplified soil and plant phosphorus model. I. Documentation. Soil Sci. Soc. Am. J. 48:800-805. Munns, D.N. and R.L. Fox. 1976. The slow reaction which continues after phosphate adsorption: Kinetics and equilibrium in some tropical soils. Soil Sci. Soc. Am. J. 40:46-51. Rajan, S.S.S. and R.L. Fox. 1972. Phosphate adsorption by soils. 1. Influence of time and ionic environment on phosphate adsorption. Commun. Soil. Sci. Plant Anal. 3:493-504. Sharpley, A.N. 1982. A prediction of the water extractable phosphorus content of soil following a phosphorus addition. J. Environ. Qual. 11:166-170.

90

SWAT USER'S MANUAL, VERSION 2000

Sharpley, A.N., C. Gray, C.A. Jones, and C.V. Cole. 1984. A simplified soil and plant phosphorus model. II. Prediction of labile, organic, and sorbed P amounts. Soil Sci. Soc. Am. J. 48:805-809. Westerstrom, G. 1981. Snowmelt runoff from urban plot. p. 452-459. In B.C. Yen (ed.) Urban stormwater hydraulics and hydrology: proceedings of the Second International Conference on Urban Storm Drainage, held at Urbana, Illinois, USA, 15-19 June 1981. Water Resources Publications, Littleton, CO. Westerstrom, G. 1984. Snowmelt runoff from Porson residential area, Lulea, Sweden. p. 315-323. In Proceedings of the Third International Conference on Urban Storm Drainage held at Chalmers University, Goteborg, Sweden, June 1984.

CHAPTER 6

SWAT INPUT DATA:

.SUB

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: properties of tributary channels within the subbasin, the amount of topographic relief within the subbasin and its impact on the climate, variables related to climate change, the number of HRUs in the subbasin and the names of HRU input files.

91

92

SWAT USER'S MANUAL, VERSION 2000

Following is a brief description of the variables in the subbasin general input file. They are listed in the order they appear within the file. Variable name TITLE Definition The first line of the .sub 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. Total number of HRUs modeled in the subbasin. Each subbasin must contain at least one HRU. LATITUDE Latitude of subbasin (degrees). The latitude is expressed as a real number with minutes and seconds converted to fractions of a degree. Elevation of subbasin (m). Elevation at the center of the elevation band (m). Orographic precipitation is a significant phenomenon in certain areas of the world. To account for orographic effects on both precipitation and temperature, SWAT allows up to 10 elevation bands to be defined in each subbasin. The only processes modeled separately for each individual elevation band are the accumulation, sublimation and melting of snow. As with the initial precipitation and temperature data, after amounts of sublimation and snow melt are determined for each elevation band, subbasin average values are calculated. These average values are the values that are used in the remainder of the simulation and reported in the output files. If the user wishes to simulate elevation bands in a subbasin, the elevation and fraction of the subbasin area contained in the elevation and must be specified.
ELEVB_FR(band)

HRUTOT

ELEV ELEVB(band)

Fraction of subbasin area within the elevation band. Values for ELEVB_FR should be between 0.0 and 1.0. Required only if elevation bands are being simulated in the subbasin.

CHAPTER 6: SWAT INPUT.SUB

93

Variable name SNOEB(band)

Definition Initial snow water content in elevation band (mm H2O). The amount of snow in the elevation band is expressed as depth of water instead of depth of snow because the density of snow is highly variable. Optional.

PLAPS

Precipitation lapse rate (mm H2O/km). A positive value denotes an increase in precipitation with an increase in elevation while a negative value denotes a decrease in precipitation with an increase in elevation. The lapse rate is used to adjust precipitation for elevation bands in the subbasin. To adjust the precipitation, the elevation of the recording station or the weather station is compared to the elevation specified for the elevation band. If no elevation bands are defined, the precipitation generated or read in from the .pcp file is used for the subbasin with no adjustment Required only if elevation bands are being simulated in the subbasin.

TLAPS

Temperature lapse rate (C/km). A positive value denotes an increase in temperature with an increase in elevation while a negative value denotes a decrease in temperature with an increase in elevation. The lapse rate is used to adjust temperature for elevation bands in the subbasin. To adjust the temperature, the elevation of the recording station or the weather station is compared to the elevation specified for the elevation band. If no elevation bands are defined, the temperature generated or read in from the .tmp file is used for the subbasin with no adjustment. If no value is entered for TLAPS, the model sets TLAPS = -6 C/km. Required only if elevation bands are being simulated in the subbasin.

94

SWAT USER'S MANUAL, VERSION 2000

Variable name SNO_SUB

Definition Initial snow water content (mm H2O). The amount of snow in the subbasin is expressed as depth of water instead of depth of snow because the density of snow is highly variable. This value is not used if the subbasin is divided into elevation bands (see variables ELEVB, ELEVB_FR and SNOEB in this file). Optional.

CH_L(1)

Longest tributary channel length in subbasin (km). The channel length is the distance along the channel from the subbasin outlet to the most distant point in the subbasin.

CH_S(1)

Average slope of tributary channels (m/m). The average channel slope is computed by taking the difference in elevation between the subbasin outlet and the most distant point in the subbasin and dividing by CH_L.

CH_W(1) CH_K(1)

Average width of tributary channels (m). Effective hydraulic conductivity in tributary channel alluvium (mm/hr). This parameter controls transmission losses from surface runoff as it flows to the main channel in the subbasin.

CH_N(1)

Mannings n value for the tributary channels.

Table 6-1: Values of Mannings roughness coefficient, n, for channel flow (Chow, 1959).1 Characteristics of Channel Median Range Excavated or dredged Earth, straight and uniform 0.025 0.016-0.033 Earth, winding and sluggish 0.035 0.023-0.050 Not maintained, weeds and brush 0.075 0.040-0.140 Natural streams Few trees, stones or brush 0.050 0.025-0.065 Heavy timber and brush 0.100 0.050-0.150 1 Chow (1959) has a very extensive list of Mannings roughness coefficients. These values represent only a small portion of those he lists in his book.

CHAPTER 6: SWAT INPUT.SUB

95

Variable name CO2

Definition Carbon dioxide concentration (ppmv). If no value for CO2 is entered the model will set CO2 = 330 ppmv (ambient CO2 concentration). (Optionalused in climate change studies only)

RFINC(mon)

Rainfall adjustment (% change). Daily rainfall within the month is adjusted by the specified percentage. For example, setting RFINC = 10 will make rainfall equal to 110% of the original value. (Optionalused in climate change studies only).

TMPINC(mon)

Temperature adjustment (C). Daily maximum and minimum temperatures within the month are raised or lowered by the specified amount. (Optionalused in climate change studies only).

RADINC(mon)

Radiation adjustment (MJ/m2-day). Daily radiation within the month is raised or lowered by the specified amount. (Optionalused in climate change studies only).

HUMINC(mon)

Humidity adjustment. Daily values for relative humidity within the month are raised or lowered by the specified amount. The relative humidity in SWAT is reported as a fraction. (Optionalused in climate change studies only).

HRUDAT MGTDAT SOILDAT CHEMDAT GWDAT

Name of HRU general input data file (.hru). Name of HRU land use management data file (.mgt). Name of HRU soil data file (.sol). Name of HRU soil chemical data file (.chm). Name of HRU groundwater data file (.gw).

96

SWAT USER'S MANUAL, VERSION 2000

The subbasin general input file is partially free format and partially fixed format. The variables that are free format will have free listed in the F90Format column and will not have a position defined. The variables that are fixed format will have a FORTRAN format and position specified. The free format variables may be placed in any position the user wishes on the line. Values for variables classified as integers should not include a decimal while values for variables classified as reals must contain a decimal. A blank space denotes the end of an input value and the beginning of the next value if there is another on the line. The fixed format variables must be entered using the specified format and positioning on the line in order for the model to read them properly. The format for the subbasin general input file is:
Variable name TITLE HRUTOT LATITUDE ELEV COMMENT LINE ELEVB(1) ELEVB(2) ELEVB(3) ELEVB(4) ELEVB(5) ELEVB(6) ELEVB(7) ELEVB(8) ELEVB(9) ELEVB(10) COMMENT LINE ELEVB_FR(1) ELEVB_FR(2) ELEVB_FR(3) ELEVB_FR(4) ELEVB_FR(5) ELEVB_FR(6) ELEVB_FR(7) Line # 1 2 3 4 5 6 6 6 6 6 6 6 6 6 6 7 8 8 8 8 8 8 8 space 1-80 space 1-8 space 9-16 space 17-24 space 25-32 space 33-40 space 41-48 space 49-56 space 57-64 space 65-72 space 73-80 space 1-80 space 1-8 space 9-16 space 17-24 space 25-32 space 33-40 space 41-48 space 49-56 Position space 1-80 Format character integer real real character decimal (xxxx.xxx) decimal (xxxx.xxx) decimal (xxxx.xxx) decimal (xxxx.xxx) decimal (xxxx.xxx) decimal (xxxx.xxx) decimal (xxxx.xxx) decimal (xxxx.xxx) decimal (xxxx.xxx) decimal (xxxx.xxx) character decimal (xxxx.xxx) decimal (xxxx.xxx) decimal (xxxx.xxx) decimal (xxxx.xxx) decimal (xxxx.xxx) decimal (xxxx.xxx) decimal (xxxx.xxx) F90 Format a80 free free free a80 f8.3 f8.3 f8.3 f8.3 f8.3 f8.3 f8.3 f8.3 f8.3 f8.3 a80 f8.3 f8.3 f8.3 f8.3 f8.3 f8.3 f8.3

CHAPTER 6: SWAT INPUT.SUB Variable name ELEVB_FR(8) ELEVB_FR(9) ELEVB_FR(10) COMMENT LINE SNOEB(1) SNOEB(2) SNOEB(3) SNOEB(4) SNOEB(5) SNOEB(6) SNOEB(7) SNOEB(8) SNOEB(9) SNOEB(10) PLAPS TLAPS SNO_SUB CH_L(1) CH_S(1) CH_W(1) CH_K(1) CH_N(1) CO2 COMMENT LINE RFINC(1) RFINC(2) RFINC(3) RFINC(4) RFINC(5) RFINC(6) COMMENT LINE RFINC(7) RFINC(8) RFINC(9) RFINC(10) Line # 8 8 8 9 10 10 10 10 10 10 10 10 10 10 11 12 13 14 15 16 17 18 19 20 21 21 21 21 21 21 22 23 23 23 23 space 1-80 space 1-8 space 9-16 space 17-24 space 25-32 space 33-40 space 41-48 space 1-80 space 1-8 space 9-16 space 17-24 space 25-32 Position space 57-64 space 65-72 space 73-80 space 1-80 space 1-8 space 9-16 space 17-24 space 25-32 space 33-40 space 41-48 space 49-56 space 57-64 space 65-72 space 73-80 Format decimal (xxxx.xxx) decimal (xxxx.xxx) decimal (xxxx.xxx) character decimal (xxxx.xxx) decimal (xxxx.xxx) decimal (xxxx.xxx) decimal (xxxx.xxx) decimal (xxxx.xxx) decimal (xxxx.xxx) decimal (xxxx.xxx) decimal (xxxx.xxx) decimal (xxxx.xxx) decimal (xxxx.xxx) real real real real real real real real real character decimal (xxxx.xxx) decimal (xxxx.xxx) decimal (xxxx.xxx) decimal (xxxx.xxx) decimal (xxxx.xxx) decimal (xxxx.xxx) character decimal (xxxx.xxx) decimal (xxxx.xxx) decimal (xxxx.xxx) decimal (xxxx.xxx) F90 Format f8.3 f8.3 f8.3 a80 f8.3 f8.3 f8.3 f8.3 f8.3 f8.3 f8.3 f8.3 f8.3 f8.3 free free free free free free free free free a80 f8.3 f8.3 f8.3 f8.3 f8.3 f8.3 a80 f8.3 f8.3 f8.3 f8.3

97

98

SWAT USER'S MANUAL, VERSION 2000 Line # 23 23 24 25 25 25 25 25 25 26 27 27 27 27 27 27 28 29 29 29 29 29 29 30 31 31 31 31 31 31 32 33 33 33 33 Position space 33-40 space 41-48 space 1-80 space 1-8 space 9-16 space 17-24 space 25-32 space 33-40 space 41-48 space 1-80 space 1-8 space 9-16 space 17-24 space 25-32 space 33-40 space 41-48 space 1-80 space 1-8 space 9-16 space 17-24 space 25-32 space 33-40 space 41-48 space 1-80 space 1-8 space 9-16 space 17-24 space 25-32 space 33-40 space 41-48 space 1-80 space 1-8 space 9-16 space 17-24 space 25-32 Format decimal (xxxx.xxx) decimal (xxxx.xxx) character decimal (xxxx.xxx) decimal (xxxx.xxx) decimal (xxxx.xxx) decimal (xxxx.xxx) decimal (xxxx.xxx) decimal (xxxx.xxx) character decimal (xxxx.xxx) decimal (xxxx.xxx) decimal (xxxx.xxx) decimal (xxxx.xxx) decimal (xxxx.xxx) decimal (xxxx.xxx) character decimal (xxxx.xxx) decimal (xxxx.xxx) decimal (xxxx.xxx) decimal (xxxx.xxx) decimal (xxxx.xxx) decimal (xxxx.xxx) character decimal (xxxx.xxx) decimal (xxxx.xxx) decimal (xxxx.xxx) decimal (xxxx.xxx) decimal (xxxx.xxx) decimal (xxxx.xxx) character decimal (xxxx.xxx) decimal (xxxx.xxx) decimal (xxxx.xxx) decimal (xxxx.xxx) F90 Format f8.3 f8.3 a80 f8.3 f8.3 f8.3 f8.3 f8.3 f8.3 a80 f8.3 f8.3 f8.3 f8.3 f8.3 f8.3 a80 f8.3 f8.3 f8.3 f8.3 f8.3 f8.3 a80 f8.3 f8.3 f8.3 f8.3 f8.3 f8.3 a80 f8.3 f8.3 f8.3 f8.3

Variable name RFINC(11) RFINC(12) COMMENT LINE TMPINC(1) TMPINC(2) TMPINC(3) TMPINC(4) TMPINC(5) TMPINC(6) COMMENT LINE TMPINC(7) TMPINC(8) TMPINC(9) TMPINC(10) TMPINC(11) TMPINC(12) COMMENT LINE RADINC(1) RADINC(2) RADINC(3) RADINC(4) RADINC(5) RADINC(6) COMMENT LINE RADINC(7) RADINC(8) RADINC(9) RADINC(10) RADINC(11) RADINC(12) COMMENT LINE HUMINC(1) HUMINC(2) HUMINC(3) HUMINC(4)

CHAPTER 6: SWAT INPUT.SUB Variable name HUMINC(5) HUMINC(6) COMMENT LINE HUMINC(7) HUMINC(8) HUMINC(9) HUMINC(10) HUMINC(11) HUMINC(12) COMMENT LINE HRUDAT MGTDAT SOILDAT CHEMDAT GWDAT Line # 33 33 34 35 35 35 35 35 35 36 37-END 37-END 37-END 37-END 37-END Position space 33-40 space 41-48 space 1-80 space 1-8 space 9-16 space 17-24 space 25-32 space 33-40 space 41-48 space 1-80 space 1-13 space 14-26 space 27-39 space 40-52 space 53-65 Format decimal (xxxx.xxx) decimal (xxxx.xxx) character decimal (xxxx.xxx) decimal (xxxx.xxx) decimal (xxxx.xxx) decimal (xxxx.xxx) decimal (xxxx.xxx) decimal (xxxx.xxx) character character character character character character F90 Format f8.3 f8.3 a80 f8.3 f8.3 f8.3 f8.3 f8.3 f8.3 a80 a13 a13 a13 a13 a13

99

REFERENCES
Chow, V.T. 1959. Open-channel hydraulics. McGraw-Hill, New York.

100

SWAT USER'S MANUAL, VERSION 2000

CHAPTER 7

SWAT INPUT DATA: .PCP

SWAT requires daily precipitation. Values for precipitation may be read from records of observed data or they may be generated. This chapter describes the format of the file used to read in measured precipitation data. Up to 18 precipitation files may be utilized in a simulation. The precipitation files are able to hold records for more than one gage, so there is not a limitation on the number of gages that can be used in a simulation. The precipitation data may be read into the model in daily or sub-daily time increments. The following sections describe the format for a daily and a subdaily precipitation file.

101

102

SWAT USER'S MANUAL, VERSION 2000

7.1 DAILY PRECIPITATION DATA

Daily precipitation data is used when the SCS curve number method is chosen to model surface runoff (Set by IEVENT in the .cod file). While the input file must contain data for the entire period of simulation, the record does not have to begin with the first day of simulation. SWAT is able to search for the beginning date in the file, saving editing time on the user's part. Once SWAT locates the record for the beginning day of simulation, it no longer processes the year and date. Because it does not check the subsequent dates, it is very important that the data for the remaining days in the simulation are listed sequentially. (If no year and date are entered for any of the records, the model assumes the first line of data corresponds to the first day of simulation.) A negative 99.0 (-99.0) should be inserted for missing data. This value tells SWAT to generate precipitation for that day. Following is a brief description of the variables in the precipitation input file. They are listed in the order they appear within the file. Variable name TITLE Definition The first line of the precipitation file is reserved for comments. The title line is not processed by the model and may be left blank. Latitude of precipitation recording gage location. This value is not used by the model and may be left blank. LONGITUDE ELEVATION Longitude of precipitation recording gage location. This value is not used by the model and may be left blank. Elevation of precipitation recording gage (m). The elevation of the recording gage is used to adjust precipitation values for elevation in subbasins where elevation bands and a precipitation lapse rate are defined. YEAR DATE PRECIPITATION Year (4-digit) Julian date Amount of precipitation falling during the day (mm).

LATITUDE

CHAPTER 7: SWAT INPUT.PCP

103

The format of the daily precipitation file with one record is:
Variable name TITLE LATITUDE LONGITUDE ELEVATION YEAR DATE PRECIPITATION Line # 1 2 3 4 5-END 5-END 5-END Position unrestricted space 8-12 space 8-12 space 8-12 space 1-4 space 5-7 space 8-12 Format character free free integer integer integer decimal(xxx.x) F90 Format unrestricted unrestricted unrestricted i5 i4 i3 f5.1

To place more than one data record within the .pcp file, repeat the original formatting for the recorded data to the right of the existing data. Simulations have been run with 200 records placed in the precipitation files. For example, assume there are records for six different rain gages stored in the daily .pcp. The formatting of the .pcp file is
Gage ALL 1 2 3 4 5 6 1 2 3 4 5 6 1 2 3 4 5 Variable name TITLE LATITUDE LATITUDE LATITUDE LATITUDE LATITUDE LATITUDE LONGITUDE LONGITUDE LONGITUDE LONGITUDE LONGITUDE LONGITUDE ELEVATION ELEVATION ELEVATION ELEVATION ELEVATION Line # 1 2 2 2 2 2 2 3 3 3 3 3 3 4 4 4 4 4 Position unrestricted space 8-12 space 13-17 space 18-22 space 23-27 space 28-32 space 33-37 space 8-12 space 13-17 space 18-22 space 23-27 space 28-32 space 33-37 space 8-12 space 13-17 space 18-22 space 23-27 space 28-32 Format character free free free free free free free free free free free free integer integer integer integer integer F90 Format unrestricted unrestricted unrestricted unrestricted unrestricted unrestricted unrestricted unrestricted unrestricted unrestricted unrestricted unrestricted unrestricted i5 i5 i5 i5 i5

104 Gage 6 ALL ALL 1 2 3 4 5 6

SWAT USER'S MANUAL, VERSION 2000 Variable name ELEVATION YEAR DATE PRECIPITATION PRECIPITATION PRECIPITATION PRECIPITATION PRECIPITATION PRECIPITATION Line # 4 5-END 5-END 5-END 5-END 5-END 5-END 5-END 5-END Position space 33-37 space 1-4 space 5-7 space 8-12 space 13-17 space 18-22 space 23-27 space 28-32 space 33-37 Format integer 4-digit integer 3-digit integer decimal(xxx.x) decimal(xxx.x) decimal(xxx.x) decimal(xxx.x) decimal(xxx.x) decimal(xxx.x) F90 Format i5 i4 i3 f5.1 f5.1 f5.1 f5.1 f5.1 f5.1

7.2 SUB-DAILY PRECIPITATION DATA

Sub-daily precipitation data is required if the Green & Ampt infiltration method is being used (Set by IEVENT in the .cod file). When the Green & Ampt infiltration method is used to calculate surface runoff, SWAT is unable to generate precipitation data. Because of this, PCPSIM in the .cod file must be set to 1 and negative 99.0 (-99.0) should not be inserted for missing data. An independent weather generator or extrapolation from adjacent weather stations should be used to fill in missing data. While the input file must contain data for the entire period of simulation, the record does not have to begin with the first day of simulation. SWAT is able to search for the beginning date in the file, saving editing time on the users part. Unlike the daily precipitation data, SWAT verifies that the date is correct on all lines. If the model reads in an incorrect date, it will print an error message to the input.std file stating the day and year in the precipitation record where the inconsistency is located and the program will stop. The number of lines of precipitation data per day is governed by the time step used (IDT in the .cod file). To save space, only one line is required for days with no rain at all. When SWAT reads a blank for the delimiter (see variable list below), it knows that all time steps on the day have no precipitation and that there are no more lines of precipitation data for that day.

CHAPTER 7: SWAT INPUT.PCP

105

Following is a brief description of the variables in the sub-daily precipitation input file. They are listed in the order they appear within the file. Variable name TITLE Definition The first line of the precipitation file is reserved for comments. The title line is not processed by the model and may be left blank. Latitude of precipitation recording gage location. This value is not used by the model and may be left blank. LONGITUDE ELEVATION Longitude of precipitation recording gage location. This value is not used by the model and may be left blank. Elevation of precipitation recording gage (m). The elevation of the recording gage is used to adjust precipitation values for elevation in subbasins where elevation bands and a precipitation lapse rate are defined. YEAR DATE HOUR DELIMITER Year (4-digit) Julian date Hour of day (0-23). The hour and minute are at the end of the time step. Space is allowed on the line for a colon to separate the hour and minute readings. The delimiter is used by the model to identify days where there is no rain and only one line is present for the day in the .pcp file. If a blank space is inserted instead of the colon, the model will assign zero precipitation to all time steps on the day. Minute of hour (0-59). The hour and minute are at the end of the time step. Amount of precipitation falling in the time period (mm).

LATITUDE

MINUTE PRECIPITATION

The format of the sub-daily precipitation file with one record is:
Variable name TITLE LATITUDE LONGITUDE ELEVATION YEAR DATE Line # 1 2 3 4 5-END 5-END Position unrestricted space 13-17 space 13-17 space 13-17 space 1-4 space 5-7 Format character free free integer integer integer F90 Format unrestricted unrestricted unrestricted i5 i4 i3

106

SWAT USER'S MANUAL, VERSION 2000 Line # 5-END 5-END 5-END 5-END Position space 8-9 space 10 space 11-12 space 13-17 Format integer character integer decimal(xxx.x) F90 Format i2 a1 i2 f5.1

Variable name HOUR DELIMITER MINUTE PRECIPITATION

To place more than one data record within the .pcp file, repeat the original formatting for the recorded data to the right of the existing data. Simulations have been run with 200 records placed in the precipitation files. For example, assume there are records for six different rain gages stored in the sub-daily .pcp. The formatting of the .pcp file is
Gage ALL 1 2 3 4 5 6 1 2 3 4 5 6 1 2 3 4 5 6 ALL ALL ALL ALL Variable name TITLE LATITUDE LATITUDE LATITUDE LATITUDE LATITUDE LATITUDE LONGITUDE LONGITUDE LONGITUDE LONGITUDE LONGITUDE LONGITUDE ELEVATION ELEVATION ELEVATION ELEVATION ELEVATION ELEVATION YEAR DATE HOUR DELIMITER Line # 1 2 2 2 2 2 2 3 3 3 3 3 3 4 4 4 4 4 4 5-END 5-END 5-END 5-END Position unrestricted space 13-17 space 18-22 space 23-27 space 28-32 space 33-37 space 38-42 space 13-17 space 18-22 space 23-27 space 28-32 space 33-37 space 38-42 space 13-17 space 18-22 space 23-27 space 28-32 space 33-37 space 38-42 space 1-4 space 5-7 space 8-9 space 10 Format character free free free free free free free free free free free free integer integer integer integer integer integer 4-digit integer 3-digit integer integer character F90 Format unrestricted unrestricted unrestricted unrestricted unrestricted unrestricted unrestricted unrestricted unrestricted unrestricted unrestricted unrestricted unrestricted i5 i5 i5 i5 i5 i5 i4 i3 i2 a1

CHAPTER 7: SWAT INPUT.PCP Gage ALL 1 2 3 4 5 6 Variable name MINUTE PRECIPITATION PRECIPITATION PRECIPITATION PRECIPITATION PRECIPITATION PRECIPITATION Line # 5-END 5-END 5-END 5-END 5-END 5-END 5-END Position space 11-12 space 13-17 space 18-22 space 23-27 space 28-32 space 33-37 space 38-42 Format integer decimal(xxx.x) decimal(xxx.x) decimal(xxx.x) decimal(xxx.x) decimal(xxx.x) decimal(xxx.x)

107

F90 Format i2 f5.1 f5.1 f5.1 f5.1 f5.1 f5.1

108

SWAT USER'S MANUAL, VERSION 2000

CHAPTER 8

SWAT INPUT DATA: .TMP

SWAT requires daily maximum and minimum air temperature. Temperature data may be read from records of observed data or they may be generated. This chapter reviews the file used to store measured temperature data. Up to 18 temperature files may be utilized in a simulation. The temperature files are able to hold records for more than one gage, so there is not a limitation on the number of gages that can be used in a simulation. As with the precipitation file, the record in the temperature input file does not have to begin with the first day of simulation. SWAT is able to search for the beginning date in the temperature file and all the comments made for this feature in the discussion of the precipitation file pertain to the temperature file as well.

109

110

SWAT USER'S MANUAL, VERSION 2000

A negative 99.0 (-99.0) should be inserted for missing maximum or minimum temperatures. This value tells SWAT to generate the missing value(s). Following is a brief description of the variables in the temperature input file. They are listed in the order they appear within the file.

Variable name TITLE

Definition The first line of the temperature file is reserved for comments. The title line is not processed by the model and may be left blank. Latitude of temperature recording gage location. This value is not used by the model and may be left blank. Longitude of temperature recording gage location. This value is not used by the model and may be left blank. Elevation of temperature recording gage (m). The elevation of the recording gage is used to adjust temperature values for elevation in subbasins where elevation bands are defined.

LATITUDE LONGITUDE ELEVATION

YEAR DATE MAX TEMP MIN TEMP

Year (4-digit) Julian date Daily maximum temperature (C). Daily minimum temperature (C).

The format of the temperature file with one record is:

Variable name TITLE LATITUDE LONGITUDE ELEVATION YEAR DATE MAX TEMP MIN TEMP Line # 1 2 3 4 5-END 5-END 5-END 5-END Position unrestricted space 8-17 space 8-17 space 8-17 space 1-4 space 5-7 space 8-12 space 13-17 Format character free free integer 4-digit integer 3-digit integer decimal(xxx.x) decimal(xxx.x) i10 i4 i3 f5.1 f5.1 F90 Format unrestricted

CHAPTER 8: SWAT INPUT.TMP

111

To place more than one data record within the .tmp file, repeat the original formatting for the recorded data to the right of the existing data. Simulations have been run with 150 records placed in the temperature files. For example, assume there are records for three different temperature gages stored in the .tmp. The formatting of the .tmp file is
Gage ALL 1 2 3 1 2 3 1 2 3 ALL ALL 1 1 2 2 3 3 Variable name TITLE LATITUDE LATITUDE LATITUDE LONGITUDE LONGITUDE LONGITUDE ELEVATION ELEVATION ELEVATION YEAR DATE MAX TEMP MIN TEMP MAX TEMP MIN TEMP MAX TEMP MIN TEMP Line # 1 2 2 2 3 3 3 4 4 4 5-END 5-END 5-END 5-END 5-END 5-END 5-END 5-END Position unrestricted space 8-17 space 18-27 space 28-37 space 8-17 space 18-27 space 28-37 space 8-17 space 18-27 space 28-37 space 1-4 space 5-7 space 8-12 space 13-17 space 18-22 space 23-27 space 28-32 space 33-37 Format character free free free free free free integer integer integer 4-digit integer 3-digit integer decimal(xxx.x) decimal(xxx.x) decimal(xxx.x) decimal(xxx.x) decimal(xxx.x) decimal(xxx.x) F90 Format unrestricted unrestricted unrestricted unrestricted unrestricted unrestricted unrestricted i10 i10 i10 i4 i3 f5.1 f5.1 f5.1 f5.1 f5.1 f5.1

112

SWAT USER'S MANUAL, VERSION 2000

CHAPTER 9

SWAT INPUT DATA: .SLR

SWAT requires daily solar radiation values. These values may be read from records of observed data or they may be generated. This chapter reviews the file used to read in measured solar radiation data. One solar radiation file may be used in a simulation. This file is able to hold records for more than one gage, so there is not a limitation on the number of gages that can be used in a simulation. As with the precipitation file, the record in the solar radiation input file does not have to begin with the first day of simulation. SWAT is able to search for the beginning date in the solar radiation file and all the comments made for this feature in the discussion of the precipitation file pertain to the solar radiation file as well.
113

114

SWAT USER'S MANUAL, VERSION 2000

A negative 99.0 (-99.0) should be inserted for missing radiation values. This value tells SWAT to generate the missing value(s). Following is a brief description of the variables in the solar radiation input file. They are listed in the order they appear within the file. Variable name TITLE Definition The first line of the solar radiation file is reserved for comments. The title line is not processed by the model and may be left blank. Year (4-digit) Julian date Daily total solar radiation (MJ/m2).

YEAR DATE SOL_RAD

The format of the solar radiation input file with one record is:
Variable name TITLE YEAR DATE SOL_RAD Line # 1 2-END 2-END 2-END Position unrestricted space 1-4 space 5-7 space 8-15 Format character 4-digit integer 3-digit integer decimal(xxxx.xxx) F90 Format unrestricted i4 i3 f8.3

To place more than one data record within the .slr file, repeat the original formatting for the recorded data to the right of the existing data. For example, assume there are records for six different solar radiation gages stored in the .slr. The formatting of the .slr file is
Gage ALL ALL ALL 1 2 3 4 5 6 Variable name TITLE YEAR DATE SOL_RAD SOL_RAD SOL_RAD SOL_RAD SOL_RAD SOL_RAD Line # 1 2-END 2-END 2-END 2-END 2-END 2-END 2-END 2-END Position unrestricted space 1-4 space 5-7 space 8-15 space 16-23 space 24-31 space 32-39 space 40-47 space 48-55 Format character 4-digit integer 3-digit integer decimal(xxxx.xxx) decimal(xxxx.xxx) decimal(xxxx.xxx) decimal(xxxx.xxx) decimal(xxxx.xxx) decimal(xxxx.xxx) F90 Format unrestricted i4 i3 f8.3 f8.3 f8.3 f8.3 f8.3 f8.3

CHAPTER 10

SWAT INPUT DATA: .WND

SWAT requires daily wind speed values when the Penman-Monteith method is selected to calculate potential evapotranspiration. Values for all these parameters may be read from records of observed data or they may be generated. This chapter reviews the input file used to read in measured daily wind speed values. One wind speed input file may be used in a simulation. This file is able to hold records for more than one gage, so there is not a limitation on the number of gages that can be used in a simulation.

115

116

SWAT USER'S MANUAL, VERSION 2000

As with the precipitation file, the record in the wind speed input file does not have to begin with the first day of simulation. SWAT is able to search for the beginning date in the wind speed file and all the comments made for this feature in the discussion of the precipitation file pertain to the wind speed file as well. A negative 99.0 (-99.0) should be inserted for missing wind speed values. This value tells SWAT to generate the missing value(s).

Following is a brief description of the variables in the wind speed input file. They are listed in the order they appear within the file. Variable name TITLE Definition The first line of the wind speed file is reserved for comments. The title line is not processed by the model and may be left blank. Year (4-digit) Julian date Daily average wind speed (m/s).

YEAR DATE WND_SP

The format of the wind speed input file with one record is:
Variable name TITLE YEAR DATE WND_SP Line # 1 2-END 2-END 2-END Position unrestricted space 1-4 space 5-7 space 8-15 Format character 4-digit integer 3-digit integer decimal(xxxx.xxx) F90 Format unrestricted i4 i3 f8.3

CHAPTER 10: SWAT INPUT.WND

117

To place more than one data record within the .wnd file, repeat the original formatting for the recorded data to the right of the existing data. For example, assume there are records for ten different wind speed gages stored in the .wnd. The formatting of the .wnd file is
Gage ALL ALL ALL 1 2 3 4 5 6 7 8 9 10 Variable name TITLE YEAR DATE WND_SP WND_SP WND_SP WND_SP WND_SP WND_SP WND_SP WND_SP WND_SP WND_SP Line # 1 2-END 2-END 2-END 2-END 2-END 2-END 2-END 2-END 2-END 2-END 2-END 2-END Position unrestricted space 1-4 space 5-7 space 8-15 space 16-23 space 24-31 space 32-39 space 40-47 space 48-55 space 56-63 space 64-71 space 72-79 space 80-87 Format character 4-digit integer 3-digit integer decimal(xxxx.xxx) decimal(xxxx.xxx) decimal(xxxx.xxx) decimal(xxxx.xxx) decimal(xxxx.xxx) decimal(xxxx.xxx) decimal(xxxx.xxx) decimal(xxxx.xxx) decimal(xxxx.xxx) decimal(xxxx.xxx) F90 Format unrestricted i4 i3 f8.3 f8.3 f8.3 f8.3 f8.3 f8.3 f8.3 f8.3 f8.3 f8.3

118

SWAT USER'S MANUAL, VERSION 2000

CHAPTER 11

SWAT INPUT DATA: .HMD

SWAT requires daily relative humidity values when the Penman-Monteith or Priestley-Taylor method is used to calculate potential evapotranspiration. Values for relative humidity may be read from records of observed data or they may be generated. This chapter reviews the input file used to read relative humidity values into the model. One relative humidity input file may be used in a simulation. This file is able to hold records for more than one gage, so there is not a limitation on the number of gages that can be used in a simulation. As with the precipitation file, the record in the relative humidity input file does not have to begin with the first day of simulation. SWAT is able to search for the beginning date in the relative humidity file and all the comments made for
119

120

SWAT USER'S MANUAL, VERSION 2000

this feature in the discussion of the precipitation file pertain to the relative humidity file as well. A negative 99.0 (-99.0) should be inserted for missing relative humidity values. This value tells SWAT to generate the missing value(s). Following is a brief description of the variables in the relative humidity input file. They are listed in the order they appear within the file. Variable name TITLE Definition The first line of the relative humidity file is reserved for comments. The title line is not processed by the model and may be left blank. Year (4-digit) Julian date Daily average relative humidity expressed as a fraction.

YEAR DATE RHD

The format of the relative humidity input file with one record is:
Variable name TITLE YEAR DATE RHD Line # 1 2-END 2-END 2-END Position unrestricted space 1-4 space 5-7 space 8-15 Format character 4-digit integer 3-digit integer decimal(xxxx.xxx) F90 Format unrestricted i4 i3 f8.3

CHAPTER 11: SWAT INPUT.HMD

121

To place more than one data record within the .hmd file, repeat the original formatting for the recorded data to the right of the existing data. For example, assume there are records for five different relative humidity gages stored in the .hmd. The formatting of the .hmd file is
Gage ALL ALL ALL 1 2 3 4 5 Variable name TITLE YEAR DATE RHD RHD RHD RHD RHD Line # 1 2-END 2-END 2-END 2-END 2-END 2-END 2-END Position unrestricted space 1-4 space 5-7 space 8-15 space 16-23 space 24-31 space 32-39 space 40-47 Format character 4-digit integer 3-digit integer decimal(xxxx.xxx) decimal(xxxx.xxx) decimal(xxxx.xxx) decimal(xxxx.xxx) decimal(xxxx.xxx) F90 Format unrestricted i4 i3 f8.3 f8.3 f8.3 f8.3 f8.3

122

SWAT USER'S MANUAL, VERSION 2000

CHAPTER 12

SWAT INPUT DATA: .PET

SWAT requires daily potential evapotranspiration values. If the user wishes to calculate potential evapotranspiration using a method other than Penman-Monteith, Priestley-Taylor, or Hargreaves, the potential

evapotranspiration values can be read in using the .pet file. The potential evapotranspiration file holds only one record that is used for the entire watershed. As with the precipitation file, the record in the potential evapotranspiration input file does not have to begin with the first day of simulation. SWAT is able to search for the beginning date in the potential evapotranspiration input file and all the comments made for this feature in the discussion of the precipitation file pertain to the potential evapotranspiration file as well.
123

124

SWAT USER'S MANUAL, VERSION 2000

Following is a brief description of the variables in the potential evapotranspiration input file. They are listed in the order they appear within the file. Variable name TITLE Definition The first line of the potential evapotranspiration file is reserved for comments. The title line is not processed by the model and may be left blank. Year (4-digit) Julian date Daily potential evapotranspiration for watershed (mm H2O).

YEAR DATE PETMEAS

The format of the potential evapotranspiration input file is:

Variable name TITLE YEAR DATE PETMEAS Line # 1 2-END 2-END 2-END Position unrestricted space 1-4 space 5-7 space 8-12 Format character 4-digit integer 3-digit integer decimal(xxx.x) F90 Format unrestricted i4 i3 f5.1

CHAPTER 13

SWAT INPUT DATA: .WGN

SWAT requires daily precipitation, maximum/minimum air temperature, solar radiation, wind speed and relative humidity. Values for all these parameters may be read from records of observed data or they may be generated. The weather generator input file contains the statistical data needed to generate representative daily climate data for the subbasins. Ideally, at least 20 years of records are used to calculate parameters in the .wgn file. Climatic data will be generated in two instances: when the user specifies that simulated weather will be used or when measured data is missing.

125

126

SWAT USER'S MANUAL, VERSION 2000

Following is a brief description of the variables in the weather generator input file. They are listed in the order they appear within the file. Variable name TITLE Definition The first line of the .wgn 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. Latitude of weather station used to create statistical parameters (degrees). The latitude is expressed as a real number with minutes and seconds converted to fractions of a degree. WLONGITUDE Longitude of weather station (degrees). This variable is not used by the model and may be left blank. WELEV RAIN_YRS Elevation of weather station (m). The number of years of maximum monthly 0.5 h rainfall data used to define values for RAIN_HHMX(1,:) RAIN_HHMX(12,:). If no value is input for RAIN_YRS, SWAT will set RAIN_YRS = 10. TMPMX(mon) Average or mean daily maximum air temperature for month (C). This value is calculated by summing the maximum air temperature for every day in the month for all years of record and dividing by the number of days summed:

WLATITUDE

mx mon =

T
d =1

mx ,mon

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. TMPMN(mon) Average or mean daily minimum air temperature for month (C).

CHAPTER 13: SWAT INPUT.WGN

127

Variable name TMPMN(mon), cont.

Definition 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:

mnmon =

T
d =1

mn ,mon

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.
TMPSTDMX(mon)

Standard deviation for daily maximum air temperature in month (C). This parameter quantifies the variability in maximum temperature for each month. The standard deviation is calculated: N 2 (Tmx ,mon mxmon ) = d =1 N 1

mxmon

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.
TMPSTDMN(mon)

Standard deviation for daily minimum air temperature in month (C). This parameter quantifies the variability in minimum temperature for each month. The standard deviation is calculated: N 2 (Tmn ,mon mnmon ) = d =1 N 1

mnmon

128

SWAT USER'S MANUAL, VERSION 2000

Variable name
TMPSTDMN(mon), cont.

Definition 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. Average or mean total monthly precipitation (mm H2O).
Rmon =
N

PCPMM(mon)

R
d =1

day ,mon

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.
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 ) = d =1 N 1

mon

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)
PCPSKW(mon)

Skew coefficient for daily precipitation in month. This parameter quantifies the symmetry of the precipitation distribution about the monthly mean. The coefficient of skewness is calculated:

CHAPTER 13: SWAT INPUT.WGN

129

Variable name PCPSKW(mon), cont.

Definition
N (Rday ,mon Rmon )
N d =1 3

g mon =

(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) PR_W(1,mon) Probability of a wet day following a dry day in the month. This probability is calculated:
Pi (W D ) = daysW
D ,i

daysdry ,i

where Pi(W/D) is the probability of a wet day following a dry day in month i, daysW/D,i is the number of times a wet day followed a dry day in month i for the entire period of record, and daysdry,i is the number of dry days in month i during the entire period of record. A dry day is a day with 0 mm of precipitation. A wet day is a day with > 0 mm precipitation. PR_W(2,mon) Probability of a wet day following a wet day in the month. This probability is calculated:
Pi (W W ) = daysW W ,i dayswet ,i

where Pi(W/W) is the probability of a wet day following a wet day in month i, daysW/W,i is the number of times a wet day followed a wet day in month i for the entire period of record, and dayswet,i is the number of wet days in month i during the entire period of record. A dry day is a day with 0 mm of precipitation. A wet day is a day with > 0 mm precipitation.

130

SWAT USER'S MANUAL, VERSION 2000

Variable name PCPD(mon)

Definition Average number of days of precipitation in month. This parameter is calculated:

d wet ,i = days wet ,i yrs

where d wet ,i is the average number of days of precipitation in month i, dayswet,i is the number of wet days in month i during the entire period of record, and yrs is the number of years of record.
RAINHHMX(mon)

Maximum 0.5 hour rainfall in entire period of record for month (mm H2O). This value represents the most extreme 30-minute rainfall intensity recorded in the entire period of record.

SOLARAV(mon)

Average daily solar radiation for month (MJ/m2/day). This value is calculated by summing the total solar radiation for every day in the month for all years of record and dividing by the number of days summed:

rad mon =

H
d =1

day ,mon

where radmon is the mean daily solar radiation for the month (MJ/m2/day), Hday,mon is the total solar radiation reaching the earths surface for day d in month mon (MJ/m2/day), and N is the total number of daily solar radiation records for month mon. DEWPT(mon) Average daily dew point temperature in month (C). The 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:

dewmon =

T
d =1

dew ,mon

CHAPTER 13: SWAT INPUT.WGN

131

Variable name DEWPT(mon), cont.

Definition 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. 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:

WNDAV(mon)

wnd mon =

d =1

wnd ,mon

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. The format of the weather generator input file is:
Variable name TITLE WLATITUDE WLONGITUDE WELEV RAIN_YRS TMPMX(1) TMPMX(2) TMPMX(3) TMPMX(4) TMPMX(5) TMPMX(6) TMPMX(7) TMPMX(8) TMPMX(9) TMPMX(10) TMPMX(11) TMPMX(12) Line # 1 2 2 3 4 5 5 5 5 5 5 5 5 5 5 5 5 Position space 1-80 space 13-19 space 32-38 space 13-19 space 13-19 space 1-6 space 7-12 space 13-18 space 19-24 space 25-30 space 31-36 space 37-42 space 43-48 space 49-54 space 55-60 space 61-66 space 67-72 Format character decimal(xxxx.xx) decimal(xxxx.xx) decimal(xxxx.xx) decimal(xxxx.xx) decimal(xxx.xx) decimal(xxx.xx) decimal(xxx.xx) decimal(xxx.xx) decimal(xxx.xx) decimal(xxx.xx) decimal(xxx.xx) decimal(xxx.xx) decimal(xxx.xx) decimal(xxx.xx) decimal(xxx.xx) decimal(xxx.xx) F90 Format a80 f7.2 f7.2 f7.2 f7.2 f6.2 f6.2 f6.2 f6.2 f6.2 f6.2 f6.2 f6.2 f6.2 f6.2 f6.2 f6.2

132

SWAT USER'S MANUAL, VERSION 2000 Line # 6 6 6 6 6 6 6 6 6 6 6 6 7 7 7 7 7 7 7 7 7 7 7 7 8 8 8 8 8 8 8 8 8 8 8 Position space 1-6 space 7-12 space 13-18 space 19-24 space 25-30 space 31-36 space 37-42 space 43-48 space 49-54 space 55-60 space 61-66 space 67-72 space 1-6 space 7-12 space 13-18 space 19-24 space 25-30 space 31-36 space 37-42 space 43-48 space 49-54 space 55-60 space 61-66 space 67-72 space 1-6 space 7-12 space 13-18 space 19-24 space 25-30 space 31-36 space 37-42 space 43-48 space 49-54 space 55-60 space 61-66 Format decimal(xxx.xx) decimal(xxx.xx) decimal(xxx.xx) decimal(xxx.xx) decimal(xxx.xx) decimal(xxx.xx) decimal(xxx.xx) decimal(xxx.xx) decimal(xxx.xx) decimal(xxx.xx) decimal(xxx.xx) decimal(xxx.xx) decimal(xxx.xx) decimal(xxx.xx) decimal(xxx.xx) decimal(xxx.xx) decimal(xxx.xx) decimal(xxx.xx) decimal(xxx.xx) decimal(xxx.xx) decimal(xxx.xx) decimal(xxx.xx) decimal(xxx.xx) decimal(xxx.xx) decimal(xxx.xx) decimal(xxx.xx) decimal(xxx.xx) decimal(xxx.xx) decimal(xxx.xx) decimal(xxx.xx) decimal(xxx.xx) decimal(xxx.xx) decimal(xxx.xx) decimal(xxx.xx) decimal(xxx.xx) F90 Format f6.2 f6.2 f6.2 f6.2 f6.2 f6.2 f6.2 f6.2 f6.2 f6.2 f6.2 f6.2 f6.2 f6.2 f6.2 f6.2 f6.2 f6.2 f6.2 f6.2 f6.2 f6.2 f6.2 f6.2 f6.2 f6.2 f6.2 f6.2 f6.2 f6.2 f6.2 f6.2 f6.2 f6.2 f6.2

Variable name TMPMN(1) TMPMN(2) TMPMN(3) TMPMN(4) TMPMN(5) TMPMN(6) TMPMN(7) TMPMN(8) TMPMN(9) TMPMN(10) TMPMN(11) TMPMN(12) TMPSTDMX(1) TMPSTDMX(2) TMPSTDMX(3) TMPSTDMX(4) TMPSTDMX(5) TMPSTDMX(6) TMPSTDMX(7) TMPSTDMX(8) TMPSTDMX(9) TMPSTDMX(10) TMPSTDMX(11) TMPSTDMX(12) TMPSTDMN(1) TMPSTDMN(2) TMPSTDMN(3) TMPSTDMN(4) TMPSTDMN(5) TMPSTDMN(6) TMPSTDMN(7) TMPSTDMN(8) TMPSTDMN(9) TMPSTDMN(10) TMPSTDMN(11)

CHAPTER 13: SWAT INPUT.WGN Variable name TMPSTDMN(12) PCPMM(1) PCPMM(2) PCPMM(3) PCPMM(4) PCPMM(5) PCPMM(6) PCPMM(7) PCPMM(8) PCPMM(9) PCPMM(10) PCPMM(11) PCPMM(12) PCPSTD(1) PCPSTD(2) PCPSTD(3) PCPSTD(4) PCPSTD(5) PCPSTD(6) PCPSTD(7) PCPSTD(8) PCPSTD(9) PCPSTD(10) PCPSTD(11) PCPSTD(12) PCPSKW(1) PCPSKW(2) PCPSKW(3) PCPSKW(4) PCPSKW(5) PCPSKW(6) PCPSKW(7) PCPSKW(8) PCPSKW(9) PCPSKW(10) Line # 8 9 9 9 9 9 9 9 9 9 9 9 9 10 10 10 10 10 10 10 10 10 10 10 10 11 11 11 11 11 11 11 11 11 11 Position space 67-72 space 1-6 space 7-12 space 13-18 space 19-24 space 25-30 space 31-36 space 37-42 space 43-48 space 49-54 space 55-60 space 61-66 space 67-72 space 1-6 space 7-12 space 13-18 space 19-24 space 25-30 space 31-36 space 37-42 space 43-48 space 49-54 space 55-60 space 61-66 space 67-72 space 1-6 space 7-12 space 13-18 space 19-24 space 25-30 space 31-36 space 37-42 space 43-48 space 49-54 space 55-60 Format decimal(xxx.xx) decimal(xxx.xx) decimal(xxx.xx) decimal(xxx.xx) decimal(xxx.xx) decimal(xxx.xx) decimal(xxx.xx) decimal(xxx.xx) decimal(xxx.xx) decimal(xxx.xx) decimal(xxx.xx) decimal(xxx.xx) decimal(xxx.xx) decimal(xxx.xx) decimal(xxx.xx) decimal(xxx.xx) decimal(xxx.xx) decimal(xxx.xx) decimal(xxx.xx) decimal(xxx.xx) decimal(xxx.xx) decimal(xxx.xx) decimal(xxx.xx) decimal(xxx.xx) decimal(xxx.xx) decimal(xxx.xx) decimal(xxx.xx) decimal(xxx.xx) decimal(xxx.xx) decimal(xxx.xx) decimal(xxx.xx) decimal(xxx.xx) decimal(xxx.xx) decimal(xxx.xx) decimal(xxx.xx) F90 Format f6.2 f6.2 f6.2 f6.2 f6.2 f6.2 f6.2 f6.2 f6.2 f6.2 f6.2 f6.2 f6.2 f6.2 f6.2 f6.2 f6.2 f6.2 f6.2 f6.2 f6.2 f6.2 f6.2 f6.2 f6.2 f6.2 f6.2 f6.2 f6.2 f6.2 f6.2 f6.2 f6.2 f6.2 f6.2

133

134

SWAT USER'S MANUAL, VERSION 2000 Line # 11 11 12 12 12 12 12 12 12 12 12 12 12 12 13 13 13 13 13 13 13 13 13 13 13 13 14 14 14 14 14 14 14 14 14 Position space 61-66 space 67-72 space 1-6 space 7-12 space 13-18 space 19-24 space 25-30 space 31-36 space 37-42 space 43-48 space 49-54 space 55-60 space 61-66 space 67-72 space 1-6 space 7-12 space 13-18 space 19-24 space 25-30 space 31-36 space 37-42 space 43-48 space 49-54 space 55-60 space 61-66 space 67-72 space 1-6 space 7-12 space 13-18 space 19-24 space 25-30 space 31-36 space 37-42 space 43-48 space 49-54 Format decimal(xxx.xx) decimal(xxx.xx) decimal(xxx.xx) decimal(xxx.xx) decimal(xxx.xx) decimal(xxx.xx) decimal(xxx.xx) decimal(xxx.xx) decimal(xxx.xx) decimal(xxx.xx) decimal(xxx.xx) decimal(xxx.xx) decimal(xxx.xx) decimal(xxx.xx) decimal(xxx.xx) decimal(xxx.xx) decimal(xxx.xx) decimal(xxx.xx) decimal(xxx.xx) decimal(xxx.xx) decimal(xxx.xx) decimal(xxx.xx) decimal(xxx.xx) decimal(xxx.xx) decimal(xxx.xx) decimal(xxx.xx) decimal(xxx.xx) decimal(xxx.xx) decimal(xxx.xx) decimal(xxx.xx) decimal(xxx.xx) decimal(xxx.xx) decimal(xxx.xx) decimal(xxx.xx) decimal(xxx.xx) F90 Format f6.2 f6.2 f6.2 f6.2 f6.2 f6.2 f6.2 f6.2 f6.2 f6.2 f6.2 f6.2 f6.2 f6.2 f6.2 f6.2 f6.2 f6.2 f6.2 f6.2 f6.2 f6.2 f6.2 f6.2 f6.2 f6.2 f6.2 f6.2 f6.2 f6.2 f6.2 f6.2 f6.2 f6.2 f6.2

Variable name PCPSKW(11) PCPSKW(12) PR_W(1,1) PR_W(1,2) PR_W(1,3) PR_W(1,4) PR_W(1,5) PR_W(1,6) PR_W(1,7) PR_W(1,8) PR_W(1,9) PR_W(1,10) PR_W(1,11) PR_W(1,12) PR_W(2,1) PR_W(2,2) PR_W(2,3) PR_W(2,4) PR_W(2,5) PR_W(2,6) PR_W(2,7) PR_W(2,8) PR_W(2,9) PR_W(2,10) PR_W(2,11) PR_W(2,12) PCPD(1) PCPD(2) PCPD(3) PCPD(4) PCPD(5) PCPD(6) PCPD(7) PCPD(8) PCPD(9)

CHAPTER 13: SWAT INPUT.WGN Variable name PCPD(10) PCPD(11) PCPD(12) RAINHHMX(1) RAINHHMX(2) RAINHHMX(3) RAINHHMX(4) RAINHHMX(5) RAINHHMX(6) RAINHHMX(7) RAINHHMX(8) RAINHHMX(9) RAINHHMX(10) RAINHHMX(11) RAINHHMX(12) SOLARAV(1) SOLARAV(2) SOLARAV(3) SOLARAV(4) SOLARAV(5) SOLARAV(6) SOLARAV(7) SOLARAV(8) SOLARAV(9) SOLARAV(10) SOLARAV(11) SOLARAV(12) DEWPT(1) DEWPT(2) DEWPT(3) DEWPT(4) DEWPT(5) DEWPT(6) DEWPT(7) DEWPT(8) Line # 14 14 14 15 15 15 15 15 15 15 15 15 15 15 15 16 16 16 16 16 16 16 16 16 16 16 16 17 17 17 17 17 17 17 17 Position space 55-60 space 61-66 space 67-72 space 1-6 space 7-12 space 13-18 space 19-24 space 25-30 space 31-36 space 37-42 space 43-48 space 49-54 space 55-60 space 61-66 space 67-72 space 1-6 space 7-12 space 13-18 space 19-24 space 25-30 space 31-36 space 37-42 space 43-48 space 49-54 space 55-60 space 61-66 space 67-72 space 1-6 space 7-12 space 13-18 space 19-24 space 25-30 space 31-36 space 37-42 space 43-48 Format decimal(xxx.xx) decimal(xxx.xx) decimal(xxx.xx) decimal(xxx.xx) decimal(xxx.xx) decimal(xxx.xx) decimal(xxx.xx) decimal(xxx.xx) decimal(xxx.xx) decimal(xxx.xx) decimal(xxx.xx) decimal(xxx.xx) decimal(xxx.xx) decimal(xxx.xx) decimal(xxx.xx) decimal(xxx.xx) decimal(xxx.xx) decimal(xxx.xx) decimal(xxx.xx) decimal(xxx.xx) decimal(xxx.xx) decimal(xxx.xx) decimal(xxx.xx) decimal(xxx.xx) decimal(xxx.xx) decimal(xxx.xx) decimal(xxx.xx) decimal(xxx.xx) decimal(xxx.xx) decimal(xxx.xx) decimal(xxx.xx) decimal(xxx.xx) decimal(xxx.xx) decimal(xxx.xx) decimal(xxx.xx) F90 Format f6.2 f6.2 f6.2 f6.2 f6.2 f6.2 f6.2 f6.2 f6.2 f6.2 f6.2 f6.2 f6.2 f6.2 f6.2 f6.2 f6.2 f6.2 f6.2 f6.2 f6.2 f6.2 f6.2 f6.2 f6.2 f6.2 f6.2 f6.2 f6.2 f6.2 f6.2 f6.2 f6.2 f6.2 f6.2

135

136

SWAT USER'S MANUAL, VERSION 2000 Line # 17 17 17 17 18 18 18 18 18 18 18 18 18 18 18 18 Position space 49-54 space 55-60 space 61-66 space 67-72 space 1-6 space 7-12 space 13-18 space 19-24 space 25-30 space 31-36 space 37-42 space 43-48 space 49-54 space 55-60 space 61-66 space 67-72 Format decimal(xxx.xx) decimal(xxx.xx) decimal(xxx.xx) decimal(xxx.xx) decimal(xxx.xx) decimal(xxx.xx) decimal(xxx.xx) decimal(xxx.xx) decimal(xxx.xx) decimal(xxx.xx) decimal(xxx.xx) decimal(xxx.xx) decimal(xxx.xx) decimal(xxx.xx) decimal(xxx.xx) decimal(xxx.xx) F90 Format f6.2 f6.2 f6.2 f6.2 f6.2 f6.2 f6.2 f6.2 f6.2 f6.2 f6.2 f6.2 f6.2 f6.2 f6.2 f6.2

Variable name DEWPT(9) DEWPT(10) DEWPT(11) DEWPT(12) WNDAV(1) WNDAV(2) WNDAV(3) WNDAV(4) WNDAV(5) WNDAV(6) WNDAV(7) WNDAV(8) WNDAV(9) WNDAV(10) WNDAV(11) WNDAV(12)

CHAPTER 14

SWAT INPUT DATA: CROP.DAT

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 include 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.

137

138

SWAT USER'S MANUAL, VERSION 2000

Following is a brief description of the variables in the land cover/plant growth database file. They are listed in the order they appear within the file. Variable name ICNUM Definition Land cover/plant code. The different plants listed in crop.dat must have consecutive values for ICNUM. ICNUM is the numeric code used in the management file to identify the land cover to be modeled. CPNM A four character code to represent the land cover/plant name. 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 plant species or land cover category, the four letter code for the new plant must be unique. IDC Land cover/plant classification: 1 2 3 4 5 6 7 warm season annual legume cold season annual legume perennial legume warm season annual cold season annual perennial trees

Processes modeled differently for the 7 groups are: 1 warm season annual legume simulate nitrogen fixation root depth varies during growing season due to root growth 2 cold season annual legume simulate nitrogen fixation root depth varies during growing season due to root growth fall-planted land covers will go dormant when daylength is less than the threshold daylength 3 perennial legume simulate nitrogen fixation root depth always equal to the maximum allowed for the plant species and soil plant goes dormant when daylength is less than the threshold daylength

CHAPTER 14: SWAT INPUTCROP.DAT

139

Variable name IDC, cont.

Definition 4 warm season annual root depth varies during growing season due to root growth 5 cold season annual root depth varies during growing season due to root growth fall-planted land covers will go dormant when daylength is less than the threshold daylength 6 perennial root depth always equal to the maximum allowed for the plant species and soil plant goes dormant when daylength is less than the threshold daylength 7 trees root depth always equal to the maximum allowed for the plant species and soil partitions new growth between leaves/needles (30%) and woody growth (70%). At the end of each growing season, biomass in the leaf fraction is converted to residue Full land cover/plant name. This description is not used by the model and is present to assist the user in differentiating between plant species.

DESCRIPTION

BIO_E

Radiation-use efficiency ((kg/ha)/(MJ/m2)).

or

biomass-energy

ratio

Radiation-use efficiency (RUE) is the amount of dry biomass produced per unit intercepted solar radiation. The radiation-use efficiency is assumed to be independent of the plants growth stage. BIO_E represents the potential or unstressed growth rate (including roots) per unit of intercepted photosynthetically active radiation. Determination of RUE is commonly performed and a literature review will provide those setting up experiments with numerous examples. The following overview of the methodology used to measure RUE was summarized from Kiniry et al (1998) and Kiniry et al (1999).

140

SWAT USER'S MANUAL, VERSION 2000

Variable name BIO_E, cont.

Definition To calculate RUE, the amount of photosynthetically active radiation (PAR) intercepted and the mass of aboveground biomass is measured several times throughout a plants growing season. The frequency of the measurements taken will vary but in general 4 to 7 measurements per growing season are considered to be adequate. As with leaf area determinations, the measurements should be performed on non-stressed plants. Intercepted radiation is measured with a light meter. Whole spectrum and PAR sensors are available and calculations of RUE will be performed differently depending on the sensor used. A brief discussion of the difference between whole spectrum and PAR sensors and the difference in calculations is given in Kiniry (1999). The use of a PAR sensor in RUE studies is strongly encouraged. When measuring radiation, three to five sets of measurements are taken rapidly for each plant plot. A set of measurements consists of 10 measurements above the leaf canopy, 10 below, and 10 more above. The light measurements should be taken between 10:00 am and 2:00 pm local time. The measurements above and below the leaf canopy are averaged and the fraction of intercepted PAR is calculated for the day from the two values. Daily estimates of the fraction of intercepted PAR are determined by linearly interpolating the measured values. The fraction of intercepted PAR is converted to an amount of intercepted PAR using daily values of incident total solar radiation measured with a standard weather station. To convert total incident radiation to total incident PAR, the daily solar radiation values are multiplied by the percent of total radiation that has a wavelength between 400 and 700 mm. This percent usually falls in the range 45 to 55% and is a function of cloud cover. 50% is considered to be a default value.

CHAPTER 14: SWAT INPUTCROP.DAT

141

Variable name BIO_E, cont.

Definition Once daily intercepted PAR values are determined, the total amount of PAR intercepted by the plant is calculated for each date on which biomass was harvested. This is calculated by summing daily intercepted PAR values from the date of seedling emergence to the date of biomass harvest. To determine biomass production, aboveground biomass is harvested from a known area of land within the plot. The plant material should be dried at least 2 days at 65C and then weighed. RUE is determined by fitting a linear regression for aboveground biomass as a function of intercepted PAR. The slope of the line is the RUE. Figure 14-1 shows the plots of aboveground biomass and summed intercepted photosynthetically active radiation for Eastern gamagrass. (Note that the units for RUE values in the graph, as well as values typically reported in literature, are different from those used by SWAT. To obtain the value used in SWAT, multiply by 10.)

Figure 14-1: Aboveground biomass and summed intercepted photosynthetically active radiation for Eastern gamagrass (After Kiniry et al.,1999).

142

SWAT USER'S MANUAL, VERSION 2000

Variable name BIO_E, cont.

Definition This parameter can greatly change the rate of growth, incidence of stress during the season and the resultant yield. This parameter should be one of the last to be adjusted. Adjustments should be based on research results. Care should be taken to make adjustments based only on data with no drought, nutrient or temperature stress. Harvest index for optimal growing conditions. The harvest index defines the fraction of the aboveground biomass that is removed in a harvest operation. This value defines the fraction of plant biomass that is lost from the system and unavailable for conversion to residue and subsequent decomposition. For crops where the harvested portion of the plant is aboveground, the harvest index is always a fraction less than 1. For crops where the harvested portion is belowground, the harvest index may be greater than 1. Two harvest indices are provided in the database, the harvest index for optimal growing conditions (HVSTI) and the harvest index under highly stressed growing conditions (WSYF). To determine the harvest index, the plant biomass removed during the harvest operation is dried at least 2 days at 65C and weighed. The total aboveground plant biomass in the field should also be dried and weighed. The harvest index is then calculated by dividing the weight of the harvested portion of the plant biomass by the weight of the total aboveground plant biomass. Plants will need to be grown in two different plots where optimal climatic conditions and stressed conditions are produced to obtain values for both harvest indices.

HVSTI

BLAI

Maximum potential leaf area index. BLAI is one of six parameters use to quantify leaf area development of a plant species during the growing season. Figure 14-2 illustrates the relationship of the database parameters to the leaf area development modeled by SWAT.

CHAPTER 14: SWAT INPUTCROP.DAT

143

Variable name BLAI, cont.

Definition

Figure 14-2: Leaf area index as a function of fraction of growing season for Alamo switchgrass

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.

144

SWAT USER'S MANUAL, VERSION 2000

Variable name BLAI, cont.

Definition 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 17 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. 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 droughtprone regions where planting densities are much smaller or irrigated conditions where densities are much greater.

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.

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.

CHAPTER 14: SWAT INPUTCROP.DAT

145

Variable name FRGRW2

Definition 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.

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.

DLAI

Fraction of growing season when leaf area declines. 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.

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.

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.

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.

146

SWAT USER'S MANUAL, VERSION 2000

Variable name T_OPT, cont.

T_BASE

Definition The peak of the plot defines the optimal temperature for leaf developmentnot 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 ~8C and the generic optimal temperature is ~25C. For cool season plants, the generic base temperature is ~0C and the generic optimal temperature is ~13C. 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 modelSWAT 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 8C.)

Figure 14-3: Rate of leaf tip appearance as a function of temperature for corn (After Kiniry et al, 1991)

CHAPTER 14: SWAT INPUTCROP.DAT

147

Variable name CNYLD

Definition Normal fraction of nitrogen in yield (kg N/kg yield). In addition to the amount of plant biomass removed in the yield, SWAT needs to know the amount of nitrogen and phosphorus removed in the yield. The harvested portion of the plant biomass is sent to a testing laboratory to determine the fraction of nitrogen and phosphorus in the biomass. This value is estimated on a dry weight basis.

CPYLD

Normal fraction of phosphorus in yield (kg P/kg yield). In addition to the amount of plant biomass removed in the yield, SWAT needs to know the amount of nitrogen and phosphorus removed in the yield. The harvested portion of the plant biomass is sent to a testing laboratory to determine the fraction of nitrogen and phosphorus in the biomass. This value is estimated on a dry weight basis.

BN(1)

Nitrogen uptake parameter #1: normal fraction of nitrogen in plant biomass at emergence (kg N/kg biomass) In order to calculate the plant nutrient demand throughout a plants growing cycle, SWAT needs to know the fraction of nutrient in the total plant biomass (on a dry weight basis) at different stages of crop growth. Six variables in the plant database provide this information: BN(1), BN(2), BN(3), BP(1), BP(2), and BP(3). Plant samples are analyzed for nitrogen and phosphorus content at three times during the growing season: shortly after emergence, near the middle of the season, and at maturity. The plant samples can be sent to testing laboratories to obtain the fraction of nitrogen and phosphorus in the biomass. Ideally, the plant samples tested for nutrient content should include the roots as well as the aboveground biomass. Differences in partitioning of nutrients to roots and shoots can cause erroneous conclusions when comparing productivity among species if only the aboveground biomass is measured.

148

SWAT USER'S MANUAL, VERSION 2000

Variable name BN(2)

Definition Nitrogen uptake parameter #2: normal fraction of nitrogen in plant biomass at 50% maturity (kg N/kg biomass) Please read the explanation for parameter BN(1) to obtain additional information about this parameter and methods used to measure it.

BN(3)

Nitrogen uptake parameter #3: normal fraction of nitrogen in plant biomass at maturity (kg N/kg biomass) Please read the explanation for parameter BN(1) to obtain additional information about this parameter and methods used to measure it.

BP(1)

Phosphorus uptake parameter #1: normal fraction of phosphorus in plant biomass at emergence (kg P/kg biomass) Please read the explanation for parameter BN(1) to obtain additional information about this parameter and methods used to measure it.

BP(2)

Phosphorus uptake parameter #2: normal fraction of phosphorus in plant biomass at 50% maturity (kg P/kg biomass) Please read the explanation for parameter BN(1) to obtain additional information about this parameter and methods used to measure it.

BP(3)

Phosphorus uptake parameter #3: normal fraction of phosphorus in plant biomass at maturity (kg P/kg biomass) Please read the explanation for parameter BN(1) to obtain additional information about this parameter and methods used to measure it.

WSYF

Lower limit of harvest index ((kg/ha)/(kg/ha)). The value between 0.0 and HVSTI which represents the lowest harvest index expected due to water stress. Please read the explanation for parameter HVSTI to obtain additional information about this parameter and methods used to measure it.

CHAPTER 14: SWAT INPUTCROP.DAT

149

Variable name USLE_C

Definition Minimum value of USLE C factor for water erosion applicable to the land cover/plant. The minimum C factor can be estimated from a known average annual C factor using the following equation (Arnold and Williams, 1995): CUSLE ,mn = 1.463 ln[CUSLE ,aa ] + 0.1034 where CUSLE,mn is the minimum C factor for the land cover and CUSLE,aa is the average annual C factor for the land cover.

GSI

Maximum stomatal conductance at high solar radiation and low vapor pressure deficit (ms-1). Stomatal conductance of water vapor is used in the Penman-Monteith calculations of maximum plant evapotranspiration. The plant database contains three variables pertaining to stomatal conductance that are required only if the Penman-Monteith equations are chosen to model evapotranspiration: maximum stomatal conductance (GSI), and two variables that define the impact of vapor pressure deficit on stomatal conductance (FRGMAX, VPDFR). Krner et al (1979) defines maximum leaf diffusive conductance as the largest value of conductance observed in fully developed leaves of well-watered plants under optimal climatic conditions, natural outdoor CO2 concentrations and sufficient nutrient supply. Leaf diffusive conductance of water vapor cannot be measured directly but can be calculated from measurements of transpiration under known climatic conditions. A number of different methods are used to determine diffusive conductance: transpiration measurements in photosynthesis cuvettes, energy balance measurements or weighing experiments, ventilated diffusion porometers and non-ventilated porometers. Krner (1977) measured diffusive conductance using a ventilated diffusion porometer. To obtain maximum leaf conductance values, leaf conductance is determined between sunrise and late morning until a clear decline or no further increase is observed. Depending on phenology, measurements are taken on at least three bright days in late spring and summer, preferably just after a rainy period. The means of

150

SWAT USER'S MANUAL, VERSION 2000

Variable name GSI, cont.

Definition maximum leaf conductance of 5 to 10 samples each day are averaged, yielding the maximum diffusive conductance for the species. Due to the variation of the location of stomata on plant leaves for different plant species, conductance values should be calculated for the total leaf surface area. Vapor pressure deficit (kPa) corresponding to the second point on the stomatal conductance curve. (The first point on the stomatal conductance curve is comprised of a vapor pressure deficit of 1 kPa and the fraction of maximum stomatal conductance equal to 1.00.) As with radiation-use efficiency, stomatal conductance is sensitive to vapor pressure deficit. Stockle et al (1992) compiled a short list of stomatal conductance response to vapor pressure deficit for a few plant species. Due to the paucity of data, default values for the second point on the stomatal conductance vs. vapor pressure deficit curve are used for all plant species in the database. The fraction of maximum stomatal conductance (FRGMAX) is set to 0.75 and the vapor pressure deficit corresponding to the fraction given by FRGMAX (VPDFR) is set to 4.00 kPa. If the user has actual data, they should use those values, otherwise the default values are adequate.

VPDFR

FRGMAX

Fraction of maximum stomatal conductance corresponding to the second point on the stomatal conductance curve. (The first point on the stomatal conductance curve is comprised of a vapor pressure deficit of 1 kPa and the fraction of maximum stomatal conductance equal to 1.00.) Please read the explanation for parameter VPDFR to obtain additional information about this parameter and methods used to measure it.

WAVP

Rate of decline in radiation use efficiency per unit increase in vapor pressure deficit. Stockle and Kiniry (1990) first noticed a relationship between RUE and vapor pressure deficit and were able to explain a large portion of within-species variability in RUE values for sorghum and corn by plotting RUE values as a function of average daily vapor pressure deficit values. Since this first article, a number of other studies

CHAPTER 14: SWAT INPUTCROP.DAT

151

Variable name WAVP, cont.

Definition have been conducted that support the dependence of RUE on vapor pressure deficit. However, there is still some debate in the scientific community on the validity of this relationship. If the user does not wish to simulate a change in RUE with vapor pressure deficit, the variable WAVP can be set to 0.0 for the plant. To define the impact of vapor pressure deficit on RUE, vapor pressure deficit values must be recorded during the growing seasons that RUE determinations are being made. It is important that the plants are exposed to no other stress than vapor pressure deficit, i.e. plant growth should not be limited by lack of soil water and nutrients. Vapor pressure deficits can be calculated from relative humidity (see Chapter 3 in Theoretical Documentation) or from daily maximum and minimum temperatures using the technique of Diaz and Campbell (1988) as described by Stockle and Kiniry (1990). The change in RUE with vapor pressure deficit is determined by fitting a linear regression for RUE as a function of vapor pressure deficit. Figure 14-4 shows a plot of RUE as a function of vapor pressure deficit for grain sorghum.

Figure 14-4: Response of radiation-use efficiency to mean daily vapor pressure deficit for grain sorghum (After Kiniry, 1999).

152

SWAT USER'S MANUAL, VERSION 2000

Variable name WAVP, cont.

Definition From Figure 14-4, the rate of decline in radiation-use efficiency per unit increase in vapor pressure deficit, ruedcl, for sorghum is 8.410-1 gMJ-1kPa-1. When RUE is adjusted for vapor pressure deficit, the model assumes the RUE value reported for BIO_E is the radiation-use efficiency at a vapor pressure deficit of 1 kPa. The value of WAVP varies among species, but a value of 6 to 8 is suggested as an approximation for most plants.

CO2HI

Elevated CO2 atmospheric concentration (L CO2/L air) corresponding the 2nd point on the radiation use efficiency curve. (The 1st point on the radiation use efficiency curve is comprised of the ambient CO2 concentration, 330 L CO2/L air, and the biomass-energy ratio reported for BIO_E) In order to assess the impact of climate change on agricultural productivity, SWAT incorporates equations that adjust RUE for elevated atmospheric CO2 concentrations. Values must be entered for CO2HI and BIOEHI in the plant database whether or not the user plans to simulate climate change. For simulations in which elevated CO2 levels are not modeled, CO2HI should be set to some number greater than 330 ppmv and BIOEHI should be set to some number greater than BIO_E. To obtain radiation-use efficiency values at elevated CO2 levels for plant species not currently in the database, plants should be established in growth chambers set up in the field or laboratory where CO2 levels can be controlled. RUE values are determined using the same methodology described in the explanation of BIO_E.

BIOEHI

Biomass-energy ratio corresponding to the 2nd point on the radiation use efficiency curve. (The 1st point on the radiation use efficiency curve is comprised of the ambient CO2 concentration, 330 L CO2/L air, and the biomass-energy ratio reported for BIO_E.) Please read the explanation for parameter CO2HI and BIO_E to obtain additional information about this parameter and methods used to measure it.

CHAPTER 14: SWAT INPUTCROP.DAT

153

Variable name RSDCO_PL

Definition Plant residue decomposition coefficient. The plant residue decomposition coefficient is the fraction of residue that will decompose in a day assuming optimal moisture, temperature, C:N ratio, and C:P ratio. This variable was originally in the basin input file (.bsn), but was added to the crop database so that users could vary decomposition by land cover. A default value of 0.05 is used for all plant species in the database.

Four lines are required to store the plant growth parameters for a land cover/plant in the database (crop.dat) file. The plant growth database file is a free format file. The variables may be placed in any position the user wishes on the line. Values for variables classified as integers should not include a decimal while values for variables classified as reals must contain a decimal. A blank space denotes the end of an input value and the beginning of the next value if there is another on the line.
Variable name ICNUM CPNM IDC BIO_E HVSTI BLAI FRGRW1 LAIMX1 FRGRW2 LAIMX2 DLAI CHTMX RDMX T_OPT T_BASE CNYLD CPYLD BN(1) BN(2) Line # 1 1 1 2 2 2 2 2 2 2 2 2 2 3 3 3 3 3 3 Format integer character integer real real real real real real real real real real real real real real real real F90 Format free a4 free free free free free free free free free free free free free free free free free

154

SWAT USER'S MANUAL, VERSION 2000 Line # 3 3 3 3 4 4 4 4 4 4 4 4 4 Format real real real real real real real real real real real real real F90 Format free free free free free free free free free free free free free

Variable name BN(3) BP(1) BP(2) BP(3) WSYF USLE_C GSI VPDFR FRGMAX WAVP CO2HI BIOEHI RSDCO_PL

REFERENCES
Arnold, J.G. and J.R. Williams. 1995. SWRRBA watershed scale model for soil and water resources management. p. 847-908. In V.P. Singh (ed) Computer models of watershed hydrology. Water Resources Publications. Diaz, R.A. and G.S. Campbell. 1988. Assessment of vapor density deficit from available air temperature information. ASA Annual Meetings, Anaheim, CA, Agron. Abstr., 1988, 16. Duncan, W.G. and Hesketh, J.D. 1968. Net photosynthesis rates, relative leaf growth rates and leaf numbers of 22 races of maize grown at eight temperatures. Crop Sci. 8:670-674. Kiniry, J.R. 1999. Response to questions raised by Sinclair and Muchow. Field Crops Research 62:245-247. Kiniry, J.R., J.A. Landivar, M. Witt, T.J. Gerik, J. Cavero, L.J. Wade. 1998. Radiation-use efficiency response to vapor pressure deficit for maize and sorghum. Field Crops Research 56:265-270.

CHAPTER 14: SWAT INPUTCROP.DAT

155

Kiniry, J.R., W.D. Rosenthal, B.S. Jackson, and G. Hoogenboom. 1991. Chapter 5: Predicting leaf development of crop plants. p. 30-42. In Hodges (ed.) Predicted crop phenology. CRC Press, Boca Raton, FL. Kiniry, J.R., C.R. Tischler and G.A. Van Esbroeck. 1999. Radiation use efficiency and leaf CO2 exchange for diverse C4 grasses. Biomass and Bioenergy 17:95-112. Krner, Ch. 1977. Blattdiffusionswiderstnde verschiedener Pflanzen in der zentralalpinen Grasheide der Hohen Tauren. p. 69-81. In Cernusca, A. (ed.) Alpine Grasheide Hohe Tauern. Ergebnisse der kosystemstudie 1976. Verff. sterr. MaB-Hochgebirgsprogr. ,,Hohe Tauern. Vol 1. Universittsverlag Wagner, Innsbruck. Krner, Ch., J.A. Scheel and H. Bauer. 1979. Maximum leaf diffusive conductance in vascular plants. Photosynthetica 13:45-82. Stockle, C.O. and J.R. Kiniry. 1990. Variability in crop radiation-use efficiency associated with vapor pressure deficit. Field Crops Research 25:171-181. Stockle, C.O., J.R. Williams, N.J. Rosenberg, and C.A. Jones. 1992. A method for estimating the direct and climatic effects of rising atmospheric carbon dioxide on growth and yield of crops: Part 1Modification of the EPIC model for climate change analysis. Agricultural Systems 38:225-238. Watson, D.J. 1958. The dependence of net assimilation rate on leaf area index. Ann. Bot. N.S. 22:37-54.

156

SWAT USER'S MANUAL, VERSION 2000

CHAPTER 15

SWAT INPUT DATA: TILL.DAT

SWAT uses five databases to store information required for plant growth, urban land characteristics, tillage, fertilizer components and pesticide properties. The tillage database distributed with SWAT contains mixing depth and mixing efficiency data for the most common tillage implements. Tillage operations redistribute nutrients, pesticide and residue in the soil profile. Appendix A documents the source of parameter values in the distributed database.

157

158

SWAT USER'S MANUAL, VERSION 2000

Following is a brief description of the variables in the tillage database file. They are listed in the order they appear within the file. Variable name ITNUM Definition Tillage number. ITNUM is the numeric code used in the management file to identify the tillage practice to be modeled. The different tillage operations in till.dat must have consecutive values for ITNUM. TILLNM EFFMIX An eight-character code representing the tillage operation name. 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). DEPTIL Depth of mixing caused by the tillage operation (mm).

The format of the tillage database file is:

Variable name ITNUM TILLNM EFFMIX DEPTIL Line # ALL ALL ALL ALL Position space 1-4 space 9-16 space 25-32 space 41-48 Format 4-digit integer character decimal(xxxx.xxx) decimal(xxxx.xxx) F90 Format i4 a8 f8.3 f8.3

CHAPTER 16

SWAT INPUT DATA: PEST.DAT

SWAT uses five databases to store information required for plant growth, urban land characteristics, tillage, fertilizer components and pesticide properties. The pesticide database contains parameters that govern pesticide fate and transport in the HRUs. Appendix A documents the source of parameter values in the distributed database.

159

160

SWAT USER'S MANUAL, VERSION 2000

Following is a brief description of the variables in the pesticide/toxin database file. They are listed in the order they appear within the file. Variable name IPNUM Definition Pesticide/toxin number. IPNUM is the numeric code used in the management file to identify the pesticide/toxin to be applied. The different toxins in pest.dat must have consecutive values for IPNUM. PNAME SKOC Name of pesticide/toxin. (up to 17 characters allowed) 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:
K p = K oc orgC 100

CHAPTER 16: SWAT INPUTPEST.DAT

161

Variable name SKOC, cont.

Definition 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. 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.

WOF

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 halflife 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 halflife 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.

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.

162

SWAT USER'S MANUAL, VERSION 2000

Variable name AP_EF

Definition 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.

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 20C and 30C.

The format of the pesticide/toxin database file is:

Variable name IPNUM PNAME SKOC WOF HLIFE_F HLIFE_S AP_EF WSOL Line # ALL ALL ALL ALL ALL ALL ALL ALL Position space 1-3 space 4-20 space 21-30 space 31-35 space 36-43 space 44-51 space 52-56 space 57-67 Format integer character decimal(xxxxxxxx.x) decimal(xx.xx) decimal(xxxxxx.x) decimal(xxxxxx.x) decimal(xx.xx) decimal(xxxxxxx.xxx) F90 Format i3 a17 f10.1 f5.2 f8.1 f8.1 f5.2 f11.3

CHAPTER 17

SWAT INPUT DATA: FERT.DAT

SWAT uses five databases to store information required for plant growth, urban land characteristics, tillage, fertilizer components and pesticide properties. The fertilizer database summarizes the relative fractions of nitrogen and phosphorus pools in the different fertilizers. Information on levels of bacteria in manure is also stored in this file. Appendix A documents the source of parameter values in the distributed database.

163

164

SWAT USER'S MANUAL, VERSION 2000

Following is a brief description of the variables in the fertilizer database file. They are listed in the order they appear within the file. Variable name IFNUM Definition Number of fertilizer in database. This number is the reference number used in the management file to identify the fertilizer type being applied. This number should be equivalent to the line number in the file. FERTNM FMINN Name of fertilizer/manure (up to 8 characters allowed). Fraction of mineral N (NO3 and NH4) in fertilizer (kg min-N/kg fertilizer). Value should be between 0.0 and 1.0. FMINP FORGN FORGP FNH3N Fraction of mineral P in fertilizer (kg min-P/kg fertilizer). Value should be between 0.0 and 1.0. Fraction of organic N in fertilizer (kg org-N/kg fertilizer). Value should be between 0.0 and 1.0. Fraction of organic P in fertilizer (kg org-P/kg fertilizer). Value should be between 0.0 and 1.0. Fraction of mineral N in fertilizer applied as ammonia (kg NH3-N/kg min-N). Value should be between 0.0 and 1.0. Concentration of persistent bacteria in manure/fertilizer (# bacteria/kg manure). Optional. Concentration of less-persistent bacteria in manure/fertilizer (# bacteria/kg manure). Optional. Bacteria partition coefficient. 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.

BACTPDB

BACTLPDB

BACTKDDB

CHAPTER 17: SWAT INPUTFERT.DAT

165

The format of the fertilizer database file is:

Variable name IFNUM FERTNM FMINN FMINP FORGN FORGP FNH3N BACTPDB BACTLPDB BACTKDDB Line # ALL ALL ALL ALL ALL ALL ALL ALL ALL ALL Position space 1-4 space 6-13 space 14-21 space 22-29 space 30-37 space 38-45 space 46-53 space 54-61 space 62-69 space 70-77 Format integer character decimal(xxxx.xxx) decimal(xxxx.xxx) decimal(xxxx.xxx) decimal(xxxx.xxx) decimal(xxxx.xxx) decimal(xxxx.xxx) decimal(xxxx.xxx) decimal(xxxx.xxx) F90 Format i4 a8 f8.3 f8.3 f8.3 f8.3 f8.3 f8.3 f8.3 f8.3

166

SWAT USER'S MANUAL, VERSION 2000

CHAPTER 18

SWAT INPUT DATA: URBAN.DAT

SWAT uses five databases to store information required for plant growth, urban land characteristics, tillage, fertilizer components and pesticide properties. 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 distributed database.

167

168

SWAT USER'S MANUAL, VERSION 2000

Following is a brief description of the variables in the urban database file. They are listed in the order they appear within the file. Variable name IUNUM URBNAME Definition Number of urban land type. This value should be equivalent to the line number. 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. URBFLNM FIMP Full description for urban land typemay take up to 54 characters. (not used by SWAT) 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. FCIMP Fraction directly connected impervious area in urban land type. 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.

CHAPTER 18: SWAT INPUTURBAN.DAT

169

Variable name FCIMP, cont.

Definition 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. 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.

CURBDEN

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.

DIRTMX THALF

Maximum amount of solids allowed to build up on impervious areas (kg/curb km). 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). Concentration of total nitrogen in suspended solid load from impervious areas (mg N/kg sed). Concentration of total phosphorus in suspended solid load from impervious areas (mg P/kg sed). Concentration of nitrate in suspended solid load from impervious areas (mg NO3-N/kg sed).

TNCONC TPCONC TNO3CONC

170

SWAT USER'S MANUAL, VERSION 2000

Every urban land type uses two lines in the urban.dat file to store input values. The format of every set of two lines is described below.
Variable name IUNUM URBNAME URBFLNM FIMP FCIMP CURBDEN URBCOEF DIRTMX THALF TNCONC TPCONC TNO3CONC Line # 1 1 1 1 1 2 2 2 2 2 2 2 Position space 1-3 space 5-8 space 10-64 space 65-72 space 73-80 space 5-12 space 13-20 space 21-28 space 29-36 space 37-44 space 45-52 space 53-60 Format integer character character decimal(xxxx.xxx) decimal(xxxx.xxx) decimal(xxxx.xxx) decimal(xxxx.xxx) decimal(xxxx.xxx) decimal(xxxx.xxx) decimal(xxxx.xxx) decimal(xxxx.xxx) decimal(xxxx.xxx) F90 Format i3 a4 a54 f8.3 f8.3 f8.3 f8.3 f8.3 f8.3 f8.3 f8.3 f8.3

REFERENCES
Huber, W.C. and R.E. Dickinson. 1988. Storm water management model, version 4: users manual. U.S. Environmental Protection Agency, Athens, GA. Huber, W.C. and J.P. Heaney. 1982. Chapter 3: Analyzing residual discharge and generation from urban and non-urban land surfaces. p. 121-243. In D.J. Basta and B.T. Bower (eds). Analyzing natural systems, analysis for regional residualsenvironmental quality management. John Hopkins University Press, Baltimore, MD. Sonnen, M.B. 1980. Urban runoff quality: information needs. ASCE Journal of the Technical Councils 106(TC1): 29-40.

CHAPTER 19

SWAT INPUT DATA:

.HRU

The HRU general input file contains information related to a diversity of features within the HRU. Data contained in the HRU input file can be grouped into the following categories: area contained in HRU, parameters affecting surface and subsurface water flow, parameters affecting erosion and management inputs related to the simulation of urban areas, irrigation, tile drains and potholes.

171

172

SWAT USER'S MANUAL, VERSION 2000

Following is a brief description of the variables in the HRU general input file. They are listed in the order they appear within the file. Variable name TITLE Definition The first line of the .hru 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. Fraction of total watershed area contained in HRU (km2/km2). If no value for HRU_FR is entered, the model will set HRU_FR = 0.0000001. SLSUBBSN Average slope length (m). This is the distance that sheet flow is the dominant surface runoff flow process. Slope length should be measured to the point that flow begins to concentrate. This length is easily observable after a heavy rain on a fallow field when the rills are well developed. In this situation, the slope length is the distance from the microwatershed divide to the origin of the rill. This value can also be determined from topographic maps. Terraces divide the slope of the hill into segments equal to the horizontal terrace interval. With terracing, the slope length is the terrace interval. For broadbase terraces, the horizontal terrace interval is the distance from the center of the ridge to the center of the channel for the terrace below. The horizontal terrace interval for steep backslope terraces is the distance from the point where cultivation begins at the base of the ridge to the base of the frontslope of the terrace below. Slope length is a parameter that is commonly overestimated. As a rule of thumb, 90 meters (300 ft) is considered to be a very long slope length. If no value for SLSUBBSN is entered, the model will set SLSUBBSN = 50. The GIS interfaces will assign the same value to this variable for all HRUs within a subbasin. However, some users like to vary this value by soil type and land cover. SLOPE Average slope steepness (m/m). The GIS interfaces will assign the same value to this variable for all HRUs within a subbasin. However, some users like to vary this value by soil type and land cover.

HRU_FR

CHAPTER 19: SWAT INPUT.HRU

173

Variable name OV_N

Definition Manning's "n" value for overland flow.

Table 19-1: Values of Mannings roughness coefficient, n, for overland flow (Engman, 1983). Characteristics of Land Surface Median Range Fallow, no residue 0.010 0.008-0.012 Conventional tillage, no residue 0.090 0.060-0.120 Conventional tillage, residue 0.190 0.160-0.220 Chisel plow, no residue 0.090 0.060-0.120 Chisel plow, residue 0.130 0.100-0.160 Fall disking, residue 0.400 0.300-0.500 No till, no residue 0.070 0.040-0.100 No till, 0.5-1 t/ha residue 0.120 0.070-0.170 No till, 2-9 t/ha residue 0.300 0.170-0.470 Rangeland, 20% cover 0.600 Short grass prairie 0.150 0.100-0.200 Dense grass 0.240 0.170-0.300 Bermudagrass 0.410 0.300-0.480

LAT_TTIME

Lateral flow travel time (days). Setting LAT_TTIME = 0.0 will allow the model to calculate the travel time based on soil hydraulic properties. This variable should be set to a specific value only by hydrologists familiar with the base flow characteristics of the watershed.

LAT_SED

Sediment concentration in lateral and groundwater flow (mg/L). Sediment concentration in lateral and groundwater flow is usually very low and does not contribute significantly to total sediment yields unless return flow is very high.

SLSOIL

Slope length for lateral subsurface flow (m). If no value is entered for SLSOIL, the model sets SLSOIL = SLSUBBSN. The GIS interfaces will assign the same value to this variable for all HRUs within a subbasin. However, some users like to vary this value by soil type and land cover.

CANMX

Maximum canopy storage (mm H2O). The plant canopy can significantly affect infiltration, surface runoff and evapotranspiration. As rain falls, canopy interception reduces the erosive energy of droplets and traps a portion of the rainfall within the canopy. The influence the canopy exerts on these processes is a function

174

SWAT USER'S MANUAL, VERSION 2000

Variable name CANMX, cont.

Definition of the density of plant cover and the morphology of the plant species. When calculating surface runoff, the SCS curve number method lumps canopy interception in the term for initial abstractions. This variable also includes surface storage and infiltration prior to runoff and is estimated as 20% of the retention parameter value for a given day (see Chapter 6). When the Green and Ampt infiltration equation is used to calculate surface runoff and infiltration, the interception of rainfall by the canopy must be calculated separately. SWAT allows the maximum amount of water that can be held in canopy storage to vary from day to day as a function of the leaf area index. CANMX is the maximum amount of water that can be trapped in the canopy when the canopy is fully developed (mm H2O)

ESCO

Soil evaporation compensation factor. This coefficient has been incorporated to allow the user to modify the depth distribution used to meet the soil evaporative demand to account for the effect of capillary action, crusting and cracks. ESCO must be between 0.01 and 1.0. As the value for ESCO is reduced, the model is able to extract more of the evaporative demand from lower levels. The change in depth distribution resulting from different values of esco are graphed in Figure 19-1.
E v a p o r a tio n a llo w e d w ith d e p th a s s u m in g 1 0 0 m m d e m a n d
3 5 .0 0

3 0 .0 0 Maximum Evaporation (mm H2O)

2 5 .0 0

2 0 .0 0

1 5 .0 0

1 0 .0 0

5 .0 0

0 .0 0 1 51 101 151 201 251 301 351 401 451 D e p th (m m )

e s c o = 1 .0 e s c o = 0 .9 e s c o = 0 .8 e s c o = 0 .7

Figure 19-1: Soil evaporative demand distribution with depth

CHAPTER 19: SWAT INPUT.HRU

175

Variable name ESCO, cont.

Definition If no value for ESCO is entered, the model will set ESCO = 0.95. The value for ESCO may be set at the watershed or HRU level (ESCO in .bsn). Plant uptake compensation factor. The amount of water uptake that occurs on a given day is a function of the amount of water required by the plant for transpiration, Et, and the amount of water available in the soil, SW. If upper layers in the soil profile do not contain enough water to meet the potential water uptake, users may allow lower layers to compensate. The plant uptake compensation factor can range from 0.01 to 1.00. As epco approaches 1.0, the model allows more of the water uptake demand to be met by lower layers in the soil. As epco approaches 0.0, the model allows less variation from the original depth distribution to take place. If no value for EPCO is entered, the model will set EPCO = 1.0. The value for EPCO may be set at the watershed or HRU level (EPCO in .bsn).

EPCO

RSDIN ERORGN

Initial residue cover (kg/ha). Optional Organic N enrichment ratio for loading with sediment. As surface runoff flows over the soil surface, part of the waters energy is used to pick up and transport soil particles. The smaller particles weigh less and are more easily transported than coarser particles. When the particle size distribution of the transported sediment is compared to that of the soil surface layer, the sediment load to the main channel has a greater proportion of clay sized particles. In other words, the sediment load is enriched in clay particles. Organic nitrogen in the soil is attached primarily to colloidal (clay) particles, so the sediment load will also contain a greater proportion or concentration of organic N than that found in the soil surface layer.

176

SWAT USER'S MANUAL, VERSION 2000

Variable name ERORGN, cont.

Definition The enrichment ratio is defined as the ratio of the concentration of organic nitrogen transported with the sediment to the concentration in the soil surface layer. SWAT will calculate an enrichment ratio for each storm event, or allow the user to define a particular enrichment ratio for organic nitrogen that is used for all storms during the simulation. To calculate the enrichment ratio, the value for ERORGN is set to zero. The default option is to allow the model to calculate the enrichment ratio. Phosphorus enrichment ratio for loading with sediment. The enrichment ratio is defined as the ratio of the concentration of phosphorus transported with the sediment to the concentration of phosphorus in the soil surface layer. SWAT will calculate an enrichment ratio for each storm event, or allow the user to define a particular enrichment ratio for phosphorus attached to sediment that is used for all storms during the simulation. If the value for ERORGP is set to zero, the model will calculate an enrichment ratio for every storm event. The default option is to allow the model to calculate the enrichment ratio.

ERORGP

FILTERW

Width of edge-of-field filter strip (m). Edge-of field filter strips may be defined in an HRU. Sediment, nutrient, pesticide and bacteria loads in surface runoff are reduced as the surface runoff passes through the filter strip. Optional.

IURBAN

Urban simulation code: 0 1 no urban sections in HRU urban sections in HRU, simulate using USGS regression equations 2 urban sections in HRU, simulate using build up/wash off algorithm

CHAPTER 19: SWAT INPUT.HRU

177

Variable name IURBAN, cont.

Definition Most large watersheds and river basins contain areas of urban land use. Estimates of the quantity and quality of runoff in urban areas are required for comprehensive management analysis. SWAT calculates runoff from urban areas with the SCS curve number method or the Green & Ampt equation. Loadings of sediment and nutrients are determined using one of two options. The first is a set of linear regression equations developed by the USGS (Driver and Tasker, 1988) for estimating storm runoff volumes and constituent loads. The other option is to simulate the buildup and washoff mechanisms, similar to SWMM Storm Water Management Model (Huber and Dickinson, 1988). Urban land type identification number from urban.dat. Irrigation code. Water applied to an HRU is obtained from one of five types of water sources: a reach, a reservoir, a shallow aquifer, a deep aquifer, or a source outside the watershed. In addition to the type of water source, the model must know the location of the water source (unless the source is outside the watershed). For the reach, shallow aquifer or deep aquifer, SWAT needs to know the subbasin number in which the source is located. If a reservoir is used to supply water, SWAT must know the reservoir number. This variable, along with IRRNO, specifies the source of irrigation water applied in the HRU. Irrigation water may be diverted from anywhere in the watershed or outside the watershed. IRR tells the model what type of water body the irrigation water is being diverted from. The options are: 0 no irrigation 1 divert water from reach 2 divert water from reservoir 3 divert water from shallow aquifer 4 divert water from deep aquifer 5 divert water from unlimited source outside watershed

URBLU IRR

178

SWAT USER'S MANUAL, VERSION 2000

Variable name IRRNO

Definition Irrigation source location. Water applied to an HRU is obtained from one of five types of water sources: a reach, a reservoir, a shallow aquifer, a deep aquifer, or a source outside the watershed. In addition to the type of water source, the model must know the location of the water source (unless the source is outside the watershed). For the reach, shallow aquifer or deep aquifer, SWAT needs to know the subbasin number in which the source is located. If a reservoir is used to supply water, SWAT must know the reservoir number. The definition of this variable depends on the setting of IRR. IRR = 1: IRRNO is the number of the reach that water is removed from. IRR = 2: IRRNO is the number of the reservoir that water is removed from. IRR = 3 or 4: IRRNO is the number of the subbasin that water is removed from. IRR = 0 or 5: this variable is not used.

FLOWMIN

Minimum in-stream flow for irrigation diversions (m3/s). If the source of the irrigation water is a reach, SWAT allows additional input parameters to be set. These parameters are used to prevent flow in the reach from being reduced to zero as a result of irrigation water removal. Users may define a minimum in-stream flow, a maximum irrigation water removal amount that cannot be exceeded on any given day, and/or a fraction of total flow in the reach that is available for removal on a given day. FLOWMIN may be set when IRR = 1. If FLOWMIN is defined by the user, irrigation water will be diverted from the reach only if flow in the reach is at or above FLOWMIN.

DIVMAX

Maximum daily irrigation diversion from the reach (If value entered for DIVMAX is positive the units are mm, if the value entered for DIVMAX is negative the units are 104 m3) If the source of the irrigation water is a reach, SWAT allows additional input parameters to be set. These parameters are used to prevent flow in the reach from

CHAPTER 19: SWAT INPUT.HRU

179

Variable name DIVMAX, cont.

Definition being reduced to zero as a result of irrigation water removal. Users may define a minimum in-stream flow, a maximum irrigation water removal amount that cannot be exceeded on any given day, and/or a fraction of total flow in the reach that is available for removal on a given day. DIVMAX may be set when IRR = 1. If DIVMAX is defined by the user, the amount of water removed from the reach and applied to the HRU on any one day will never exceed the value assigned to DIVMAX.

FLOWFR

Fraction of available flow that is allowed to be applied to the HRU. Available flow is defined as the total flow in reach minus FLOWMIN. If FLOWMIN is left at zero, the fraction of available flow becomes the fraction of total flow in reach that is allowed to be applied to the reach. If the source of the irrigation water is a reach, SWAT allows additional input parameters to be set. These parameters are used to prevent flow in the reach from being reduced to zero as a result of irrigation water removal. Users may define a minimum in-stream flow, a maximum irrigation water removal amount that cannot be exceeded on any given day, and/or a fraction of total flow in the reach that is available for removal on a given day. FLOWFR may be set when IRR = 1. The value for FLOWFR should be between 0.01 and 1.00. The model will default FLOWFR = 1.0 if no value is entered or 0.00 is entered.

DDRAIN

Depth to subsurface drain (mm). If drainage tiles are installed in the HRU, the depth to the tiles is needed. A common depth for drain installation is 90 mm. To simulate tile drainage in an HRU, the user must specify the depth from the soil surface to the drains, the amount of time required to drain the soil to field capacity, and the amount of lag between the time water enters the tile till it exits the tile and enters the main channel. Tile drainage occurs when the soil water content exceeds field capacity.

180

SWAT USER'S MANUAL, VERSION 2000

Variable name TDRAIN

Definition Time to drain soil to field capacity (hours). The time required to drain the soil from saturation to field capacity. Most tile drains are designed to reduce the water content to field capacity within 48 hours. To simulate tile drainage in an HRU, the user must specify the depth from the soil surface to the drains, the amount of time required to drain the soil to field capacity, and the amount of lag between the time water enters the tile till it exits the tile and enters the main channel. Tile drainage occurs when the soil water content exceeds field capacity.

GDRAIN

Drain tile lag time (hours). The amount of time between the transfer of water from the soil to the drain tile and the release of the water from the drain tile to the reach. To simulate tile drainage in an HRU, the user must specify the depth from the soil surface to the drains, the amount of time required to drain the soil to field capacity, and the amount of lag between the time water enters the tile till it exits the tile and enters the main channel. Tile drainage occurs when the soil water content exceeds field capacity.

IPOT

Number of HRU with impounded water. In areas of low relief and/or young geologic development, the drainage network may be poorly developed. Watersheds in these areas may have many closed depressional areas, referred to as potholes. Runoff generated within these areas flows to the lowest portion of the pothole rather than contributing to flow in the main channel. Other systems that are hydrologically similar to potholes include playa lakes and fields that are artifically impounded for rice production. To define an HRU as a pothole, the user must set IPOT to the HRU number. To initiate water impoundment, a release/impound operation must be placed in the .mgt file.

CHAPTER 19: SWAT INPUT.HRU

181

Variable name IPOT, cont.

Definition If the HRU does not contain the pothole, but does contribute runoff to the pothole in another HRU, the user should set IPOT to the number of the HRU with the pothole. The pothole can accept water only from HRUs located within the subbasin. Fraction of HRU area that drains into the pothole. Required if IPOT is set to a number other than zero. Average daily outflow to main channel from tile flow if drainage tiles are installed in the pothole (m3/s). Required only for the HRU that is ponding water (IPOT = current HRU number) if drainage tiles are installed.

POT_FR POT_TILE

POT_VOLX

Maximum volume of water stored in the pothole (104 m3 H2O). Required only for the HRU that is ponding water (IPOT = current HRU number).

POT_VOL

Initial volume of water stored in the pothole (104 m3 H2O). Required only for the HRU that is ponding water (IPOT = current HRU number).

POT_NSED

Equilibrium sediment concentration in pothole (mg/L). Required only for the HRU that is ponding water (IPOT = current HRU number).

POT_NO3L

Not currently active. Nitrate decay rate in pothole (1/day). Required only for the HRU that is ponding water (IPOT = current HRU number).

182

SWAT USER'S MANUAL, VERSION 2000

The HRU general input file is a free format file. The variables may be placed in any position the user wishes on the line. Values for variables classified as integers should not include a decimal while values for variables classified as reals must contain a decimal. A blank space denotes the end of an input value and the beginning of the next value if there is another on the line. The format for the HRU general input file is:
Variable name TITLE HRU_FR SLSUBBSN SLOPE OV_N LAT_TTIME LAT_SED SLSOIL CANMX ESCO EPCO RSDIN ERORGN ERORGP FILTERW IURBAN URBLU IRR IRRNO FLOWMIN DIVMAX FLOWFR DDRAIN TDRAIN GDRAIN NO VARIABLE IPOT POT_FR POT_TILE Line # 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 Format character real real real real real real real real real real real real real real integer integer integer integer real real real real real real free integer real real F90 Format a80 free free free free free free free free free free free free free free free free free free free free free free free free free free free free

CHAPTER 19: SWAT INPUT.HRU Variable name POT_VOLX POT_VOL POT_NSED POT_NO3L Line # 30 31 32 33 Format real real real real F90 Format free free free free

183

REFERENCES
Engman, E.T. 1983. Roughness coefficients for routing surface runoff. Proc. Spec. Conf. Frontiers of Hydraulic Engineering.

184

SWAT USER'S MANUAL, VERSION 2000

CHAPTER 20

SWAT INPUT DATA:

.MGT

A primary goal of environmental modeling is to assess the impact of anthropogenic activities on a given system. Central to this assessment is the itemization of the land and water management practices taking place within the system. The primary file used to summarize these practices is the HRU management file (.mgt). This file contains input data for planting, harvest, irrigation applications, nutrient applications, pesticide applications, and tillage operations.

185

186

SWAT USER'S MANUAL, VERSION 2000

20.1 GENERAL MANAGEMENT VARIABLES

The first two lines of the management input file contain general management variables. The remaining lines in the file list the sequence of management operations which occur at specific times during the simulation. The general management variables define the status of plants growing in the HRU at the beginning of the simulation. Other parameters on this line initialize the curve number for the HRU, the USLE P factor for sediment erosion calculations, and the amount of biological mixing.

The general management variables are: Variable name TITLE Definition The first line of the .mgt 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. Land cover status code. This code informs the model whether or not a land cover is growing at the beginning of the simulation. 0 no land cover growing 1 land cover growing NROT Number of years of rotation. This code identifies the number of years of management practices given in the .mgt file. (A blank line should be inserted between each different year of management.) If the management doesn't change from year to year, the management operations for only one year are needed. Two land covers/crops may not be grown simultaneously, but they may be grown in the same year. For two or more crops grown in the same year, NROT is equal to 1 for 1 year of management practices listed. NROT has nothing to do with the number of different crops grown. NMGT Management code. Used by SWAT/GRASS (GIS) interface. The model doesn't use this variable.

IGRO

CHAPTER 20: SWAT INPUT.MGT

187

Variable name NCRP

Definition Land cover identification number. If a land cover is growing at the beginning of the simulation (IGRO = 1), this variable defines the type of land cover. The identification number is the numeric code for the land cover given in the plant growht database.

ALAI

Initial leaf area index. If a land cover is growing at the beginning of the simulation (IGRO = 1), the leaf area index of the land cover must be defined.

BIO_MS

Initial dry weight biomass (kg/ha). If a land cover is growing at the beginning of the simulation (IGRO = 1), the initial biomass must be defined.

PHU

Total number of heat units or growing degree days needed to bring plant to maturity. This value is needed only if a land cover is growing at the beginning of the simulation (IGRO = 1). Calculation of PHU is reviewed in Chapter 17 of the SWAT 2000 Theoretical Documentation.

BIO_MIN

Minimum plant biomass for grazing (kg/ha). This variable was created so that the plant cover in an HRU would not be reduced to zero when grazing was included in the list of management operations. Grazing will not be simulated unless the biomass is at or above BIO_MIN.

BIOMIX

Biological mixing efficiency. Biological mixing is the redistribution of soil constituents as a result of the activity of biota in the soil (e.g. earthworms, etc.). Studies have shown that biological mixing can be significant in systems where the soil is only infrequently disturbed. In general, as a management system shifts from conventional tillage to conservation tillage to no-till there will be an increase in biological mixing. SWAT allows biological mixing to occur to a depth of 300 mm (or the bottom of the soil profile if it is shallower than 300 mm).

188

SWAT USER'S MANUAL, VERSION 2000

Variable name BIOMIX, cont.

Definition The efficiency of biological mixing is defined by the user and is conceptually the same as the mixing efficiency of a tillage implement. The redistribution of nutrients by biological mixing is calculated using the same methodology as that used for a tillage operation. Biological mixing is performed at the end of every calendar year. If no value for BIOMIX is entered, the model will set BIOMIX = 0.20

CN2

Initial SCS runoff curve number for moisture condition II. The SCS curve number is a function of the soils permeability, land use and antecedent soil water conditions. Typical curve numbers for moisture condition II are listed in the following tables for various land covers and soil types (SCS Engineering Division, 1986). These values are appropriate for a 5% slope. The curve number may be updated in plant, tillage, and harvest/ kill operations. If CNOP is never defined for these operations, the value set for CN2 will be used throughout the simulation. If CNOP is defined for an operation, the value for CN2 is used until the time of the operation containing the first CNOP value. From that point on, the model only uses operation CNOP values to define the curve number for moisture condition II. Values for CN2 and CNOP should be entered for pervious conditions. In HRUs with urban areas, the model will adjust the curve number to reflect the impact of the impervious areas.

Table 20-1: Runoff curve numbers for cultivated agricultural lands (from SCS Engineering Division, 1986)
Cover Hydrologic Soil Group Land Use Fallow Treatment or practice Bare soil Crop residue cover Straight row Straight row w/ residue Contoured Contoured w/ residue Contoured & terraced Hydrologic condition ---Poor Good Poor Good Poor Good Poor Good Poor Good Poor Good A 77 76 74 72 67 71 64 70 65 69 64 66 62 B 86 85 83 81 78 80 75 79 75 78 74 74 71 C 91 90 88 88 85 87 82 84 82 83 81 80 78 D 94 93 90 91 89 90 85 88 86 87 85 82 81

Row crops

Crop residue cover applies only if residue is on at least 5% of the surface throughout the year.

CHAPTER 20: SWAT INPUT.MGT

189

Variable name CN2, cont.

Definition

Table 20-1, cont.: Runoff curve numbers for cultivated agricultural lands
Cover Hydrologic Soil Group Land Use Treatment or practice Contoured & terraced w/ residue Straight row Straight row w/ residue Contoured Contoured w/ residue Contoured & terraced Contoured & terraced w/ residue Close-seeded or broadcast legumes or rotation Straight row Contoured Contoured & terraced Hydrologic condition Poor Good Poor Good Poor Good Poor Good Poor Good Poor Good Poor Good Poor Good Poor Good Poor Good A 65 61 65 63 64 60 63 61 62 60 61 59 60 58 66 58 64 55 63 51 B 73 70 76 75 75 72 74 73 73 72 72 70 71 69 77 72 75 69 73 67 C 79 77 84 83 83 80 82 81 81 80 79 78 78 77 85 81 83 78 80 76 D 81 80 88 87 86 84 85 84 84 83 82 81 81 80 89 85 85 83 83 80

Small grains

Table 20-2: Runoff curve numbers for other agricultural lands (from SCS Engineering Division, 1986)
Cover Hydrologic Soil Group Hydrologic Cover Type condition Pasture, grassland, or rangecontinuous forage for grazing1 Poor Fair Good Meadowcontinuous grass, protected from grazing and generally mowed for hay - - - Brushbrush-weed-grass mixture with brush the major element2 Poor Fair Good Woodsgrass combination (orchard or tree farm) Poor Fair Good Woods3 Poor Fair Good Farmsteadsbuildings, lanes, driveways, and surrounding lots. ---A 68 49 39 30 48 35 30 57 43 32 45 36 30 59 B 79 69 61 58 67 56 48 73 65 58 66 60 55 74 C 86 79 74 71 77 70 65 82 76 72 77 73 70 82 D 89 84 80 78 83 77 73 86 82 79 83 79 77 86

Poor: < 50% ground cover or heavily grazed with no mulch; Fair: 50 to 75% ground cover and not heavily grazed; Good: > 75% ground cover and lightly or only occasionally grazed 2 Poor: < 50% ground cover; Fair: 50 to 75% ground cover; Good: > 75% ground cover 3 Poor: Forest litter, small trees, and brush are destroyed by heavy grazing or regular burning; Fair: Woods are grazed but not burned, and some forest litter covers the soil; Good: Woods are protected from grazing, and litter and brush adequately cover the soil.

190

SWAT USER'S MANUAL, VERSION 2000

Variable name CN2, cont.

Definition

Table 20-3: Runoff curve numbers for urban areas (from SCS Engineering division, 1986)
Cover Hydrologic Soil Group Cover Type Fully developed urban areas Open spaces (lawns, parks, golf courses, cemeteries, etc.) Hydrologic condition Poor Fair Good ------------85% 72% 65% 38% 30% 25% 20% 12% Average % impervious area A 68 49 39 98 83 76 72 89 81 77 61 57 54 51 46 77 B 79 69 61 98 89 85 82 92 88 85 75 72 70 68 65 86 C 86 79 74 98 92 89 87 94 91 90 83 81 80 79 77 91 D 89 84 80 98 93 91 89 95 93 92 87 86 85 84 82 94

Impervious areas: Paved parking lots, roofs, driveways, etc. (excl. right-of-way) Paved streets and roads; open ditches (incl. right-of-way) Gravel streets and roads (including right-of-way) Dirt streets and roads (including right-of way) Urban districts: Commercial and business Industrial Residential Districts by average lot size: 1/8 acre (0.05 ha) or less (town houses) 1/4 acre (0.10 ha) 1/3 acre (0.13 ha) 1/2 acre (0.20 ha) 1 acre (0.40 ha) 2 acres (0.81 ha) Developing urban areas: Newly graded areas (pervious areas only, no vegetation)

USLE_P

USLE equation support practice factor. The support practice factor, PUSLE, is defined as the ratio of soil loss with a specific support practice to the corresponding loss with up-and-down slope culture. Support practices include contour tillage, stripcropping on the contour, and terrace systems. Stabilized waterways for the disposal of excess rainfall are a necessary part of each of these practices. Contour tillage and planting provides almost complete protection against erosion from storms of low to moderate intensity, but little or no protection against occasional severe storms that cause extensive breakovers of contoured rows. Contouring is most effective on slopes of 3 to 8 percent. Values for PUSLE and slope-length limits for contour support practices are given in Table 20-4.

SWAT will automatically adjust curve numbers for impervious areas when IURBAN and URBLU are defined in the .hru file. Curve numbers from Table 6-3 should not be used in this instance. Poor: grass cover < 50%; Fair: grass cover 50 to 75%; Good: grass cover > 75%

CHAPTER 20: SWAT INPUT.MGT

191

Variable name USLE_P, cont.

Definition
Table 20-4: P factor values and slope-length limits for contouring (Wischmeier and Smith, 1978). Land slope (%) PUSLE Maximum length (m) 1 to 2 0.60 122 3 to 5 0.50 91 6 to 8 0.50 61 9 to 12 0.60 37 13 to 16 0.70 24 17 to 20 0.80 18 21 to 25 0.90 15

Stripcropping is a practice in which contoured strips of sod are alternated with equal-width strips of row crop or small grain. Recommended values for contour stripcropping are given in Table 20-5.
Table 20-5: P factor values, maximum strip width and slope-length limits for contour stripcropping (Wischmeier and Smith, 1978). PUSLE values1 Land slope Strip width Maximum (%) (m) length (m) A B C 1 to 2 0.30 0.45 0.60 40 244 3 to 5 0.25 0.38 0.50 30 183 6 to 8 0.25 0.38 0.50 30 122 9 to 12 0.30 0.45 0.60 24 73 13 to 16 0.35 0.52 0.70 24 49 17 to 20 0.40 0.60 0.80 18 37 21 to 25 0.45 0.68 0.90 15 30
1

P values: A: For 4-year rotation of row crop, small grain with meadow seeding, and 2 years of meadow. A second row crop can replace the small grain if meadow is established in it. B: For 4-year rotation of 2 years row crop, winter grain with meadow seeding, and 1year meadow. C: For alternate strips of row crop and winter grain

Terraces are a series of horizontal ridges made in a hillside. There are several types of terraces. Broadbase terraces are constructed on gently sloping land and the channel and ridge are cropped the same as the interterrace area. The steep backslope terrace, where the backslope is in sod, is most common on steeper land. Impoundment terraces are terraces with underground outlets. Terraces divide the slope of the hill into segments equal to the horizontal terrace interval. With terracing, the slope length is the terrace interval. For broadbase terraces, the horizontal terrace interval is the distance from the center of the ridge to the center of the channel for the terrace below. The horizontal terrace interval for steep backslope terraces is the distance from the point where cultivation begins at

192

SWAT USER'S MANUAL, VERSION 2000

Variable name USLE_P, cont.

Definition the base of the ridge to the base of the frontslope of the terrace below. Values for PUSLE for contour farming terraced fields are listed in Table 20-6. These values apply to broadbase, steep backslope and level terraces. Keep in mind that the values given in Table 20-6 do not account for all erosion control benefits of terraces. The shorter slope-length used in the calculation of the length-slope factor will produce additional reduction.

Table 20-6: P factor values for contour-farmed terraced fields (from Wischmeier and Smith, 1978)1 Computing sediment yield3 Farm planning Land Steep backslope Graded slope underground channels Contour Stripcrop (%) P factor2 outlets sod outlets P factor 1 to 2 0.60 0.30 0.12 0.05 3 to 8 0.50 0.25 0.10 0.05 9 to 12 0.60 0.30 0.12 0.05 13 to 16 0.70 0.35 0.14 0.05 17 to 20 0.80 0.40 0.16 0.06 21 to 25 0.90 0.45 0.18 0.06
1

Slope length is the horizontal terrace interval. The listed values are for contour farming. No additional contouring factor is used in the computation. 2 Use these values for control of interterrace erosion within specified soil loss tolerances. 3 These values include entrapment efficiency and are used for control of offsite sediment within limits and for estimating the fields contribution to watershed sediment yield.

The format of the first two lines in the management file are:
Variable name TITLE IGRO NROT NMGT NCRP ALAI BIO_MS PHU BIO_MIN BIOMIX CN2 USLE_P Line # 1 2 2 2 2 2 2 2 2 2 2 2 Position space 1-80 space 1 space 2-4 space 5-8 space 9-12 space 13-20 space 21-28 space 29-36 space 37-44 space 45-52 space 53-60 space 61-68 Format character 1-digit integer 3-digit integer 4-digit integer 4-digit integer decimal (xxxxx.xx) decimal (xxxxx.xx) decimal (xxxxx.xx) decimal (xxxxx.xx) decimal (xxxxx.xx) decimal (xxxxx.xx) decimal (xxxxx.xx) F90 Format a80 i1 i3 i4 i4 f8.2 f8.2 f8.2 f8.2 f8.2 f8.2 f8.2

CHAPTER 20: SWAT INPUT.MGT

193

20.2 SCHEDULED MANAGEMENT OPERATIONS

SWAT will simulate 14 different types of management operations. The first four variables on all management lines are identical while the remaining ten are operation specific. 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:
1 2 3 4 5 planting/beginning of growing season: this operation initializes the growth of a specific land cover/plant type in the HRU irrigation operation: this operation applies water to the HRU fertilizer application: this operation adds nutrients to the soil in the HRU pesticide application: this operation applies a pesticide to the plant and/or soil in the HRU 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. It also sets IGRO = 0 which allows the next crop to be planted. tillage operation: this operation mixes the upper soil layers and redistributes the nutrients/chemicals/etc. within those layers 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) kill/end of growing season: this operation stops all plant growth and converts all plant biomass to residue. It also sets IGRO = 0 which allows the next crop to be planted. grazing operation: this operation removes plant biomass at a specified rate and allows simultaneous application of manure. auto irrigation initialization: this operation initializes auto irrigation within the HRU. Auto irrigation applies water whenever the plant experiences a user-specified level of water stress. auto fertilization initialization: this operation initializes auto fertilization within the HRU. Auto fertilization applies nutrients whenever the plant experiences a user-specified level of nitrogen stress. 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. release/impound: this operation releases/impounds water in HRUs growing rice or other plants

6 7

9 10

11

12

13

194

SWAT USER'S MANUAL, VERSION 2000

end of year rotation flag: this operation identifies the end of the operation scheduling for the year.

Figure 20-1: Management operations.

For each year of management operations provided, the operations must be listed in chronological order starting in January.

CHAPTER 20: SWAT INPUT.MGT

195

20.2.1 PLANTING/BEGINNING OF GROWING SEASON

The plant operation initiates plant growth. This operation can be used to designate the time of planting for agricultural crops or the initiation of plant growth in the spring for a land cover that requires several years to reach maturity (forests, orchards, etc.). The plant operation will be performed by SWAT only when no land cover is growing in an HRU. Before planting a new land cover, the previous land cover must be removed with a kill operation or a harvest and kill operation. If two plant operations are placed in the management file and the first land cover is not killed prior to the second plant operation, the second plant operation is ignored by the model. Information required in the plant operation includes the timing of the operation (month and day or fraction of base zero potential heat units), the total number of heat units required for the land cover to reach maturity, and the specific land cover to be simulated in the HRU. If the land cover is being transplanted, the leaf area index and biomass for the land cover at the time of transplanting must be provided. Also, for transplanted land covers, the total number of heat units for the land cover to reach maturity should be from the period the land cover is transplanted to maturity (not from seed generation). Heat units are reviewed in Chapter 17 of the Theoretical Documentation. The user has the option of varying the curve number in the HRU throughout the year. New curve number values may be entered in a plant operation, tillage operation and harvest and kill operation. The curve number entered for these operations are for moisture condition II. SWAT adjusts the entered value daily to reflect change in water content. 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.

196

SWAT USER'S MANUAL, VERSION 2000

The variables which may be entered on the planting line are listed and described below. Variable name MONTH DAY HUSC Definition Month operation takes place. Day operation takes place. Fraction of total base zero heat units at which operation takes place. Heat unit scheduling is explained in Chapter 17 of the SWAT 2000 Theoretical Documentation. If MONTH and DAY are not provided, HUSC must be set to a value. Management operation number. MGT_OP = 1 for planting/beginning of growing season Total heat units for cover/plant to reach maturity. Calculation of HEAT UNITS is reviewed in Chapter 17 of the SWAT 2000 Theoretical Documentation. Land cover/plant identification number from plant growth database. Harvest index target ((kg/ha)/(kg/ha)). This variable along with BIO_TARG allow the user to specify the harvest index and biomass produced by the plant every year. The model will then simulate plant growth to meet these specified values. If you are studying the effect of management practices on yields or you want the biomass to vary in response to different weather conditions, you would not want to use HITAR or BIO_TARG. Optional. Biomass (dry weight) target (metric tons/ha). This variable along with HITAR allow the user to specify the harvest index and biomass produced by the plant every year. The model will then simulate plant growth to meet these specified values. If you are studying the effect of management practices on yields or you want the biomass to vary in response to different weather conditions, you would not want to use HITAR or BIO_TARG. Optional. Initial leaf area index. This variable would be used only for covers/plants which are transplanted rather than established from seeds. Optional.

MGT_OP HEAT UNITS

NCR HITAR

BIO_TARG

ALAINIT

CHAPTER 20: SWAT INPUT.MGT

197

Variable name BIO_INIT

Definition Initial dry weight biomass (kg/ha). This variable would be used only for covers/plants that are transplanted rather than established from seeds. Optional.

CNOP

SCS runoff curve number for moisture condition II Please read discussion for CN2 in Section 20.1 General Management Variables for more information on this variable. Optional.

The format of the planting operation line is

Variable name MONTH DAY HUSC MGT_OP HEAT UNITS NCR HITAR BIO_TARG ALAINIT BIO_INIT CNOP Position space 1-4 space 5-8 space 9-16 space 17-20 space 21-28 space 29-32 space 33-40 space 41-48 space 49-56 space 61-66 space 67-72 Format 4-digit integer 4-digit integer decimal (xxxx.xxx) 4-digit integer decimal (xxxx.xxx) 4-digit integer decimal (xxxx.xxx) decimal (xxxx.xxx) decimal (xxxx.xxx) decimal (xx.xxx) decimal (xx.xxx) F90 Format i4 i4 f8.3 i4 f8.3 i4 f8.3 f8.3 f8.3 f6.3 f6.3

198

SWAT USER'S MANUAL, VERSION 2000

20.2.2 IRRIGATION OPERATION

Water applied to an HRU is obtained from one of five types of water sources: a reach, a reservoir, a shallow aquifer, a deep aquifer, or a source outside the watershed. In addition to the type of water source, the model must know the location of the water source (unless the source is outside the watershed). For the reach, shallow aquifer or deep aquifer, SWAT needs to know the subbasin number in which the source is located. If a reservoir is used to supply water, SWAT must know the reservoir number. If the source of the irrigation water is a reach, SWAT allows additional input parameters to be set. These parameters are used to prevent flow in the reach from being reduced to zero as a result of irrigation water removal. Users may define a minimum in-stream flow, a maximum irrigation water removal amount that cannot be exceeded on any given day, and/or a fraction of total flow in the reach that is available for removal on a given day. For a given irrigation event, SWAT determines the amount of water available in the source. The amount of water available is compared to the amount of water specified in the irrigation operation. If the amount available is less than the amount specified, SWAT will only apply the available water. Water applied to an HRU is used to fill the soil layers up to field capacity beginning with the soil surface layer and working downward until all the water applied is used up or the bottom of the profile is reached. If the amount of water specified in an irrigation operation exceeds the amount needed to fill the soil layers up to field capacity water content, the excess water is returned to the source. For HRUs that are defined as potholes or depressional areas, the irrigation water is added to the ponded water overlying the soil surface.

CHAPTER 20: SWAT INPUT.MGT

199

The variables which may be entered on the irrigation line are listed and described below Variable name MONTH DAY HUSC Definition Month operation takes place. Day operation takes place. Fraction of total base zero heat units at which operation takes place. Heat unit scheduling is explained in Chapter 17 of the SWAT 2000 Theoretical Documentation. If MONTH and DAY are not provided, HUSC must be set to a value. MGT_OP IRR_AMT Management operation number. MGT_OP = 2 for irrigation operation Depth of irrigation water applied on HRU (mm).

The format of the irrigation operation line is

Variable name MONTH DAY HUSC MGT_OP IRR_AMT Position space 1-4 space 5-8 space 9-16 space 17-20 space 33-40 Format 4-digit integer 4-digit integer decimal (xxxx.xxx) 4-digit integer decimal (xxxx.xxx) F90 Format i4 i4 f8.3 i4 f8.3

200

SWAT USER'S MANUAL, VERSION 2000

20.2.3 FERTILIZER APPLICATION

The fertilizer operation applies fertilizer or manure to the soil. Information required in the fertilizer operation includes the timing of the operation (month and day or fraction of plant potential heat units), the type of fertilizer/manure applied, the amount of fertilizer/manure applied, and the depth distribution of fertilizer application. SWAT assumes surface runoff interacts with the top 10 mm of soil. Nutrients contained in this surface layer are available for transport to the main channel in surface runoff. The fertilizer operation allows the user to specify the fraction of fertilizer that is applied to the top 10 mm. The remainder of the fertilizer is added to the first soil layer defined in the HRU .sol file. The weight fraction of different types of nutrients and bacteria are defined for the fertilizer In the fertilizer database,. The variables which may be entered on the fertilization line are listed and described below Variable name MONTH DAY HUSC Definition Month operation takes place. Day operation takes place. Fraction of total base zero heat units at which operation takes place. Heat unit scheduling is explained in Chapter 17 of the SWAT 2000 Theoretical Documentation. If MONTH and DAY are not provided, HUSC must be set to a value. MGT_OP FRT_LY1 Management operation number. MGT_OP = 3 for fertilizer application Fraction of fertilizer applied to top 10mm of soil. The remaining fraction is applied to the 1st soil layer below 10 mm. If FRT_LY1 is set to 0, the model applies 20% of the fertilizer to the top 10mm and the remainder to the 1st soil layer below 10mm.

CHAPTER 20: SWAT INPUT.MGT

201

Variable name FERT_ID

Definition Fertilizer identification number. This corresponds to the line number of the fertilizer in fert.dat. If no identification number is provided, the model assumes 28-10-10 is being applied.

FRT_KG

Amount of fertilizer applied to HRU (kg/ha).

The format of the fertilizer application line is

Variable name MONTH DAY HUSC MGT_OP FRY_LY1 FERT_ID FRT_KG Position space 1-4 space 5-8 space 9-16 space 17-20 space 21-28 space 29-32 space 33-40 Format 4-digit integer 4-digit integer decimal (xxxx.xxx) 4-digit integer decimal (xxxx.xxx) 4-digit integer decimal (xxxx.xxx) F90 Format i4 i4 f8.3 i4 f8.3 i4 f8.3

202

SWAT USER'S MANUAL, VERSION 2000

20.2.4 PESTICIDE APPLICATION

The pesticide operation applies pesticide to the HRU. Information required in the pesticide operation includes the timing of the operation (month and day or fraction of plant potential heat units), the type of pesticide applied, and the amount of pesticide applied. Field studies have shown that even on days with little or no wind, a portion of pesticide applied to the field is lost. The fraction of pesticide that reaches the foliage or soil surface is defined by the pesticides application efficiency. The variables which may be entered on the pesticide application line are listed and described below Variable name MONTH DAY HUSC Definition Month operation takes place. Day operation takes place. Fraction of total base zero heat units at which operation takes place. Heat unit scheduling is explained in Chapter 17 of the SWAT 2000 Theoretical Documentation. If MONTH and DAY are not provided, HUSC must be set to a value. MGT_OP PEST_ID PST_KG Management operation number. MGT_OP = 4 for pesticide application Pesticide identification code from pesticide database. Amount of pesticide applied to HRU (kg/ha).

The format of the pesticide application line is

Variable name MONTH DAY HUSC MGT_OP PEST_ID PST_KG Position space 1-4 space 5-8 space 9-16 space 17-20 space 57-60 space 61-66 Format 4-digit integer 4-digit integer decimal (xxxx.xxx) 4-digit integer 4-digit integer decimal (xx.xxx) F90 Format i4 i4 f8.3 i4 i4 f6.3

CHAPTER 20: SWAT INPUT.MGT

203

20.2.5 HARVEST AND KILL OPERATION

The harvest and kill operation stops plant growth in the HRU. The fraction of biomass specified in the land covers harvest index (in the plant growth database) is removed from the HRU as yield. The remaining fraction of plant biomass is converted to residue on the soil surface. The only information required by the harvest and kill operation is the timing of the operation (month and day or fraction of plant potential heat units). The user also has the option of updating the moisture condition II curve number in this operation. The variables which may be entered on the harvest and kill line are listed and described below Variable name MONTH DAY HUSC Definition Month operation takes place. Day operation takes place. Fraction of total base zero heat units at which operation takes place. Heat unit scheduling is explained in Chapter 17 of the SWAT 2000 Theoretical Documentation. If MONTH and DAY are not provided, HUSC must be set to a value. Management operation number. MGT_OP = 5 for harvest and kill operation SCS runoff curve number for moisture condition II Please read discussion for CN2 in Section 20.1 General Management Variables for more information on this variable. Optional.

MGT_OP CNOP

The format of the harvest and kill line is

Variable name MONTH DAY HUSC MGT_OP CNOP Position space 1-4 space 5-8 space 9-16 space 17-20 space 67-72 Format 4-digit integer 4-digit integer decimal (xxxx.xxx) 4-digit integer decimal (xx.xxx) F90 Format i4 i4 f8.3 i4 f6.3

204

SWAT USER'S MANUAL, VERSION 2000

20.2.6 TILLAGE OPERATION

The tillage operation redistributes residue, nutrients, pesticides and bacteria in the soil profile. Information required in the tillage operation includes the timing of the operation (month and day or fraction of base zero potential heat units), and the type of tillage operation. The user has the option of varying the curve number in the HRU throughout the year. New curve number values may be entered in a plant operation, tillage operation and harvest and kill operation. The curve number entered for these operations are for moisture condition II. SWAT adjusts the entered value daily to reflect change in water content. The variables which may be entered on the tillage line are listed and described below Variable name MONTH DAY HUSC Definition Month operation takes place. Day operation takes place. Fraction of total base zero heat units at which operation takes place. Heat unit scheduling is explained in Chapter 17 of the SWAT 2000 Theoretical Documentation. If MONTH and DAY are not provided, HUSC must be set to a value. MGT_OP TILLAGE_ID CNOP Management operation number. MGT_OP = 6 for tillage operation Tillage implement code from tillage database. SCS runoff curve number for moisture condition II Please read discussion for CN2 in Section 20.1 General Management Variables for more information on this variable. Optional.

CHAPTER 20: SWAT INPUT.MGT

205

The format of the tillage operation line is

Variable name MONTH DAY HUSC MGT_OP TILLAGE_ID CNOP Position space 1-4 space 5-8 space 9-16 space 17-20 space 29-32 space 67-72 Format 4-digit integer 4-digit integer decimal (xxxx.xxx) 4-digit integer 4-digit integer decimal (xx.xxx) F90 Format i4 i4 f8.3 i4 i4 f6.3

206

SWAT USER'S MANUAL, VERSION 2000

20.2.7 HARVEST OPERATION

The harvest operation will remove plant biomass without killing the plant. This operation is most commonly used to cut hay or grass. The only information required by the harvest operation is the date. However, a harvest index override and a harvest efficiency can be set. When no harvest index override is specified, SWAT uses the plant harvest index from the plant growth database to set the fraction of biomass removed. The plant harvest index in the plant growth database is set to the fraction of the plant biomass partitioned into seed for agricultural crops and a typical fraction of biomass removed in a cutting for hay. If the user prefers a different fraction of biomass to be removed, the harvest index override should be set to the desired value. A harvest efficiency may also be defined for the operation. This value specifies the fraction of harvested plant biomass removed from the HRU. The remaining fraction is converted to residue on the soil surface. If the harvest efficiency is left blank or set to zero, the model assumes this feature is not being used and removes 100% of the harvested biomass (no biomass is converted to residue). After biomass is removed in a harvest operation, the plants leaf area index and accumulated heat units are set back by the fraction of biomass removed. Reducing the number of accumulated heat units shifts the plants development to an earlier period in which growth is usually occurring at a faster rate. The variables which may be entered on the harvest line are listed and described below Variable name MONTH DAY Definition Month operation takes place. Day operation takes place.

CHAPTER 20: SWAT INPUT.MGT

207

Variable name HUSC

Definition Fraction of total base zero heat units at which operation takes place. Heat unit scheduling is explained in Chapter 17 of the SWAT 2000 Theoretical Documentation. If MONTH and DAY are not provided, HUSC must be set to a value.

MGT_OP HIOVR

Management operation number. MGT_OP = 7 for the harvest only operation Harvest index override ((kg/ha)/(kg/ha)) This variable will force the ratio of yield to total aboveground biomass to the specified value. The harvest index in the plant growth database (crop.dat) assumes only the seed is being harvested. If biomass is cut and removed (for example, in hay cuttings), HIOVR must be used to specify the amount of biomass removed. Optional.

HARVEFF

Harvest efficiency. The harvest efficiency defines the fraction of yield biomass removed by the harvesting equipment. The remainder of the yield biomass is converted to residue and added to the residue pool in the top 10 mm of soil. If the harvest efficiency is not set or a 0.00 is entered, the model assumes the user wants to ignore harvest efficiency and sets the fraction to 1.00 so that the entire yield is removed from the HRU. Optional.

The format of the harvest operation line is

Variable name MONTH DAY HUSC MGT_OP HIOVR HARVEFF Position space 1-4 space 5-8 space 9-16 space 17-20 space 21-28 space 33-40 Format 4-digit integer 4-digit integer decimal (xxxx.xxx) 4-digit integer decimal (xxxx.xxx) decimal (xxxx.xxx) F90 Format i4 i4 f8.3 i4 f8.3 f8.3

208

SWAT USER'S MANUAL, VERSION 2000

20.2.8 KILL OPERATION

The kill operation stops plant growth in the HRU. All plant biomass is converted to residue. The only information required by the kill operation is the timing of the operation (month and day or fraction of plant potential heat units). The variables which may be entered on the kill line are listed and described below Variable name MONTH DAY HUSC Definition Month operation takes place. Day operation takes place. Fraction of total base zero heat units at which operation takes place. Heat unit scheduling is explained in Chapter 17 of the SWAT 2000 Theoretical Documentation. If MONTH and DAY are not provided, HUSC must be set to a value. MGT_OP Management operation number. MGT_OP = 8 for kill operation The format of the kill line is
Variable name MONTH DAY HUSC MGT_OP Position space 1-4 space 5-8 space 9-16 space 17-20 Format 4-digit integer 4-digit integer decimal (xxxx.xxx) 4-digit integer F90 Format i4 i4 f8.3 i4

CHAPTER 20: SWAT INPUT.MGT

209

20.2.9 GRAZING OPERATION

The grazing operation simulates plant biomass removal and manure deposition over a specified period of time. This operation is used to simulate pasture or range grazed by animals. Information required in the grazing operation includes the time during the year at which grazing begins (month and day or fraction of plant potential heat units), the length of the grazing period, the amount of biomass removed daily, the amount of manure deposited daily, and the type of manure deposited. The amount of biomass trampled is an optional input. Biomass removal in the grazing operation is similar to that in the harvest operation. However, instead of a fraction of biomass being specified, an absolute amount to be removed every day is given. In some conditions, this can result in a reduction of the plant biomass to a very low level that will result in increased erosion in the HRU. To prevent this, a minimum plant biomass for grazing may be specified (BIO_MIN in the second line of the management file). When the plant biomass falls below the amount specified for BIO_MIN, the model will not graze, trample, or apply manure in the HRU on that day. If the user specifies an amount of biomass to be removed daily by trampling, this biomass is converted to residue. Nutrient fractions of the manure applied during grazing must be stored in the fertilizer database. The manure nutrient loadings are added to the topmost 10 mm of soil. This is the portion of the soil with which surface runoff interacts. After biomass is removed by grazing and/or trampling, the plants leaf area index and accumulated heat units are set back by the fraction of biomass removed.

210

SWAT USER'S MANUAL, VERSION 2000

The variables which may be entered on the grazing line are listed and described below Variable name MONTH DAY HUSC Definition Month grazing begins. Day grazing begins. Fraction of total base zero heat units at which operation takes place. Heat unit scheduling is explained in Chapter 17 of the SWAT 2000 Theoretical Documentation. If MONTH and DAY are not provided, HUSC must be set to a value. MGT_OP BMEAT NDGRAZ BMTRMP Management operation number. MGT_OP = 9 for grazing operation Dry weight of biomass consumed daily ((kg/ha)/day). Number of consecutive days grazing takes place in the HRU. Dry weight of biomass trampled daily ((kg/ha)/day) Trampling becomes significant as the number of animals grazed per hectare increases. This is a very subjective value which is typically set equal to BMEAT, i.e. the animals trample as much as they eat. Optional. WMANURE IGFTYP Dry weight of manure deposited daily ((kg/ha)/day). Manure identification code from fertilizer database

The format of the grazing operation line is

Variable name MONTH DAY HUSC MGT_OP BMEAT NDGRAZ BMTRMP WMANURE IGFTYP Position space 1-4 space 5-8 space 9-16 space 17-20 space 21-28 space 29-32 space 33-40 space 49-56 space 57-60 Format 4-digit integer 4-digit integer decimal (xxxx.xxx) 4-digit integer decimal (xxxx.xxx) 4-digit integer decimal (xxxx.xxx) decimal (xxxx.xxx) 4-digit integer F90 Format i4 i4 f8.3 i4 f8.3 i4 f8.3 f8.3 i4

CHAPTER 20: SWAT INPUT.MGT

211

20.2.10 AUTO IRRIGATION INITIALIZATION

Rather than specifying fixed amounts and time for irrigation, the user can allow the model to apply water as needed by the plant. The variables which may be entered on the auto irrigation line are listed and described below Variable name MONTH DAY HUSC Definition Month auto irrigation is initialized. Day auto irrigation is initialized. Fraction of total base zero heat units at which operation takes place. Heat unit scheduling is explained in Chapter 17 of the SWAT 2000 Theoretical Documentation. If MONTH and DAY are not provided, HUSC must be set to a value. Management operation number. MGT_OP = 10 for auto irrigation initialization Water stress factor of cover/plant that triggers irrigation. When the user selects auto-application of irrigation water in an HRU, a water stress threshold must be specified. The water stress threshold is a fraction of potential plant growth. Anytime actual plant growth falls below this threshold fraction due to water stress the model will automatically apply water to the HRU. If enough water is available from the irrigation source, the model will add water to the soil until it is at field capacity. This factor ranges from 0.0 to 1.0 where 0.0 indicates there is no growth of the plant due to water stress and 1.0 indicates there is no reduction of plant growth due to water stress. The water stress threshold is usually set somewhere between 0.90 and 0.95.

MGT_OP AUTO_WSTR

The format of the auto irrigation line is

Variable name MONTH DAY HUSC MGT_OP AUTO_WSTR Position space 1-4 space 5-8 space 9-16 space 17-20 space 33-40 Format 4-digit integer 4-digit integer decimal (xxxx.xxx) 4-digit integer decimal (xxxx.xxx) F90 Format i4 i4 f8.3 i4 f8.3

212

SWAT USER'S MANUAL, VERSION 2000

20.2.11 AUTO FERTILIZATION INITIALIZATION

Fertilization in an HRU may be scheduled by the user or automatically applied by SWAT. When the user selects auto-application of fertilizer in an HRU, a nitrogen stress threshold must be specified. The nitrogen stress threshold is a fraction of potential plant growth. Anytime actual plant growth falls below this threshold fraction due to nitrogen stress, the model will automatically apply fertilizer to the HRU. The user specifies the type of fertilizer, the fraction of total fertilizer applied to the soil surface, the maximum amount of fertilizer that can be applied during the year, the maximum amount of fertilizer that can be applied in any one application, and the application efficiency. The variables which may be entered on the auto fertilization line are listed and described below. Variable name MONTH DAY HUSC Definition Month initialization takes place. Day initialization takes place. Fraction of total base zero heat units at which operation takes place. Heat unit scheduling is explained in Chapter 17 of the SWAT 2000 Theoretical Documentation. If MONTH and DAY are not provided, HUSC must be set to a value. MGT_OP AUTO_NSTR Management operation number. MGT_OP = 11 for auto fertilization initialization Nitrogen stress factor of cover/plant that triggers fertilization. The nitrogen stress factor is calculated by dividing the growth of the plant undergoing nitrogen stress by the growth of the plant if there was no nitrogen stress. This factor ranges from 0.0 to 1.0 where 0.0 indicates there is no growth of the plant due to nitrogen stress and 1.0 indicates there is no reduction of plant growth due to nitrogen stress. The nitrogen stress threshold is usually set somewhere between 0.90 and 0.95.

CHAPTER 20: SWAT INPUT.MGT

213

Variable name FERT_ID

Definition Fertilizer identification number. This corresponds to the number of the fertilizer in the fertilizer database. If this variable is left blank or set to zero, the model will apply the commercial fertilizer 2810-10.

AUTO_NMXS

Maximum amount of mineral N allowed in any one application (kg N/ha). If this variable is left blank, the model will set AUTO_NMXS = 200.

AUTO_NMXA

Maximum amount of mineral N allowed to be applied in any one year (kg N/ha). If this variable is left blank, the model will set AUTO_NMXA = 300.

AUTO_EFF

Application efficiency. The amount of fertilizer applied in auto fertilization is based on the amount of nitrogen removed at harvest. If you set AUTO_EFF = 1.0, the model will apply enough fertilizer to replace the amount of nitrogen removed at harvest. If AUTO_EFF > 1.0, the model will apply fertilizer to meet harvest removal plus an extra amount to make up for nitrogen losses due to surface runoff/leaching. If AUTO_EFF < 1.0, the model will apply fertilizer at the specified fraction below the amount removed at harvest. If this variable is left blank, the model will set AUTO_EFF = 1.3.

AFRT_LY1

Fraction of fertilizer applied to top 10mm of soil. The remaining fraction is applied to the 1st soil layer below 10mm. If this variable is left blank, the model will set AFRT_LY1 = 0.2.

214

SWAT USER'S MANUAL, VERSION 2000

The format of the auto fertilization line is

Variable name MONTH DAY HUSC MGT_OP AUTO_NSTR FERT_ID AUTO_NMXS AUTO_NMXA AUTO_EFF AFRT_LY1 Position space 1-4 space 5-8 space 9-16 space 17-20 space 21-28 space 29-32 space 33-40 space 41-48 space 61-66 space 67-72 Format 4-digit integer 4-digit integer decimal (xxxx.xxx) 4-digit integer decimal (xxxx.xxx) 4-digit integer decimal (xxxx.xxx) decimal (xxxx.xxx) decimal (xx.xxx) decimal (xx.xxx) F90 Format i4 i4 f8.3 i4 f8.3 i4 f8.3 f8.3 f6.3 f6.3

CHAPTER 20: SWAT INPUT.MGT

215

20.2.12 STREET SWEEPING OPERATION

Street cleaning is performed in urban areas to control buildup of solids and trash. While it has long been thought that street cleaning has a beneficial effect on the quality of urban runoff, studies by EPA have found that street sweeping has little impact on runoff quality unless it is performed every day (U.S. Environmental Protection Agency, 1983). SWAT performs street sweeping operations only when the build up/wash off algorithm is specified for urban loading calculations. Street sweeping is performed only on dry days, where a dry day is defined as a day with less than 0.1 mm of surface runoff. The variables which may be entered on the street sweeping line are listed and described below. Variable name MONTH DAY HUSC Definition Month operation takes place. Day operation takes place. Fraction of total base zero heat units at which operation takes place. Heat unit scheduling is explained in Chapter 17 of the SWAT 2000 Theoretical Documentation. If MONTH and DAY are not provided, HUSC must be set to a value. MGT_OP SWEEPEFF Management operation number. MGT_OP = 12 for street sweeping 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).

216

SWAT USER'S MANUAL, VERSION 2000

Variable name SWEEPEFF, cont.

Definition 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.
Table 20-7: Removal efficiencies (fraction removed) from street cleaner path (from Pitt, 1979)
Street Cleaning Program and Street Surface Loading Conditions Vacuum Street Cleaner (5.5-55 kg/curb km) Total BOD5 COD KN PO4 Pesticides Solids

1 pass 2 passes 3 passes

Vacuum Street Cleaner (55-280 kg/curb km)

.31 .45 .53

.24 .35 .41

.16 .26 .08 .22 .37 .12 .27 .45 .14

.33 .50 .59

1 pass 2 passes 3 passes

Vacuum Street Cleaner (280-2820 kg/curb km)

.37 .51 .58

.29 .42 .47

.21 .31 .12 .29 .46 .17 .35 .51 .20

.40 .59 .67

1 pass 2 passes 3 passes

Mechanical Street Cleaner (50-500 kg/curb km)

.48 .60 .63

.38 .50 .52

.33 .43 .20 .42 .54 .25 .44 .57 .26

.57 .72 .75

1 pass 2 passes 3 passes

Flusher Mechanical Street Cleaner followed by a Flusher

.54 .75 .85 .30

.40 .58 .69 a b

.31 .40 .20 .48 .58 .35 .59 .69 .46 a b a b a b

.40 .60 .72 a b

.80 a: efficiency fraction estimated .15 to .40 b: efficiency fraction estimated .35 to 1.00

CHAPTER 20: SWAT INPUT.MGT

217

Variable name AVWSP

Definition Fraction of curb length available for sweeping. The availability factor, frav, is the fraction of the curb length that is sweepable. The entire curb length is often not available for sweeping due to the presence of cars and other obstacles. AVWSP can range from 0.01 to 1.00. If no value is entered for AVWSP (AVWSP left blank or set to 0.0, the model will assume 100% of the curb length is available for sweeping.

The format of the street sweeping line is

Variable name MONTH DAY HUSC MGT_OP SWEEPEFF AVWSP Position space 1-4 space 5-8 space 9-16 space 17-20 space 21-28 space 33-40 Format 4-digit integer 4-digit integer decimal (xxxx.xxx) 4-digit integer decimal (xxxx.xxx) decimal (xxxx.xxx) F90 Format i4 i4 f8.3 i4 f8.3 f8.3

218

SWAT USER'S MANUAL, VERSION 2000

20.2.13 RELEASE/IMPOUND OPERATION

In areas of low relief and/or young geologic development, the drainage network may be poorly developed. Watersheds in these areas may have many closed depressional areas, referred to as potholes. Runoff generated within these areas flows to the lowest portion of the pothole rather than contributing to flow in the main channel. Other systems that are hydrologically similar to potholes include playa lakes and fields that are artifically impounded for rice production. The algorithms reviewed in this section are used to model these types of systems. To define an HRU as a pothole, the user must set IPOT (.hru) to the HRU number. To initiate water impoundment, a release/impound operation must be placed in the .mgt file. The release/impound operation can be used only in the HRU designated as a depressional/impounded area in the subbasin (IPOT in .hru). The variables which may be entered on the release/impound line are listed and described below. Variable name MONTH DAY HUSC Definition Month operation takes place. Day operation takes place. Fraction of total base zero heat units at which operation takes place. Heat unit scheduling is explained in Chapter 17 of the SWAT 2000 Theoretical Documentation. If MONTH and DAY are not provided, HUSC must be set to a value. MGT_OP IREL_IMP Management operation number. MGT_OP = 13 for release/impoundment of water Release/impound action code: 0 1 initiate water impoundment initiate water release

CHAPTER 20: SWAT INPUT.MGT

219

The format of the release/impound line is

Variable name MONTH DAY HUSC MGT_OP IREL_IMP Position space 1-4 space 5-8 space 9-16 space 17-20 space 29-32 Format 4-digit integer 4-digit integer decimal (xxxx.xxx) 4-digit integer 4-digit integer F90 Format i4 i4 f8.3 i4 i4

20.2.14 END OF YEAR OPERATION

SWAT requires a blank line to be inserted after all operations for a single year are listed. The blank line lets the model know that there will be no more operations in the year. If a rotation is being simulated in which the land is left fallow for one of the years with no operations occurring, a blank line should be entered for the fallow year.

220

SWAT USER'S MANUAL, VERSION 2000

REFERENCES
Pitt, R. 1979. Demonstration of non-point pollution abatement through improved street cleaning practices. EPA-600/2-79-161 (NTIS PB80-108988), U.S. Environmental Protection Agency, Cincinnati, OH. Soil Conservation Service Engineering Division. 1986. Urban hydrology for small watersheds. U.S. Department of Agriculture, Technical Release 55. U.S. Environmental Protection Agency. 1983. Results of the nationwide urban runoff program; Volume 1 final report. NTIS PB84-185552, U.S. Environmental Protection Agency, Washington, D.C. Wischmeier, W.H., and D.D. Smith. 1978. Predicting rainfall losses: A guide to conservation planning. USDA Agricultural Handbook No. 537. U.S. Gov. Print. Office, Washington, D. C.

CHAPTER 21

SWAT INPUT DATA:

.WUS

Consumptive water use is a management tool that removes water from the basin. This file is used to simulate removal of water for irrigation outside the watershed or removal of water for urban/industrial use. Water removed for consumptive use is considered to be lost from the system. SWAT allows water to be removed from the shallow aquifer, the deep aquifer, the reach or the pond within any subbasin in the watershed. Water also may be removed from reservoirs for consumptive use.

221

222

SWAT USER'S MANUAL, VERSION 2000

Consumptive water use is allowed to vary from month to month. For each month in the year, an average daily volume of water removed from the source is specified.

Following is a brief description of the variables in the water use input file. They are listed in the order they appear within the file. Variable name TITLE Definition The first three lines of the .wus file are reserved for user comments. The comments may take up to 80 spaces on each line. The title lines are not processed by the model and may be left blank. Average daily water removal from the pond for the month (104 m3/day). Optional. WURCH(mon) Average daily water removal from the reach for the month (104 m3/day). Optional. WUSHAL(mon) Average daily water removal from the shallow aquifer for the month (104 m3/day). Optional. WUDEEP(mon) Average daily water removal from the deep aquifer for the month (104 m3/day). Optional. The format of the water use file is:
Variable name TITLE WUPND(1) WUPND(2) WUPND(3) WUPND(4:) WUPND(5) WUPND(6) Line # 1-3 4 4 4 4 4 4 Position space 1-80 space 1-10 space 11-20 space 21-30 space 31-40 space 41-50 space 51-60 Format character decimal (xxxxxxxx.x) decimal (xxxxxxxx.x) decimal (xxxxxxxx.x) decimal (xxxxxxxx.x) decimal (xxxxxxxx.x) decimal (xxxxxxxx.x) F90 Format a80 f10.1 f10.1 f10.1 f10.1 f10.1 f10.1

WUPND(mon)

CHAPTER 21: SWAT INPUT.WUS

223

Variable name WUPND(7) WUPND(8) WUPND(9) WUPND(10) WUPND(11) WUPND(12) WURCH(1) WURCH(2) WURCH(3) WURCH(4) WURCH(5) WURCH(6) WURCH(7) WURCH(8) WURCH(9) WURCH(10) WURCH(11) WURCH(12) WUSHAL(1) WUSHAL(2) WUSHAL(3) WUSHAL(4) WUSHAL(5) WUSHAL(6) WUSHAL(7) WUSHAL(8) WUSHAL(9) WUSHAL(10) WUSHAL(11) WUSHAL(12) WUDEEP(1) WUDEEP(2) WUDEEP(3) WUDEEP(4)

Line # 5 5 5 5 5 5 6 6 6 6 6 6 7 7 7 7 7 7 8 8 8 8 8 8 9 9 9 9 9 9 10 10 10 10

Position space 1-10 space 11-20 space 21-30 space 31-40 space 41-50 space 51-60 space 1-10 space 11-20 space 21-30 space 31-40 space 41-50 space 51-60 space 1-10 space 11-20 space 21-30 space 31-40 space 41-50 space 51-60 space 1-10 space 11-20 space 21-30 space 31-40 space 41-50 space 51-60 space 1-10 space 11-20 space 21-30 space 31-40 space 41-50 space 51-60 space 1-10 space 11-20 space 21-30 space 31-40

Format decimal (xxxxxxxx.x) decimal (xxxxxxxx.x) decimal (xxxxxxxx.x) decimal (xxxxxxxx.x) decimal (xxxxxxxx.x) decimal (xxxxxxxx.x) decimal (xxxxxxxx.x) decimal (xxxxxxxx.x) decimal (xxxxxxxx.x) decimal (xxxxxxxx.x) decimal (xxxxxxxx.x) decimal (xxxxxxxx.x) decimal (xxxxxxxx.x) decimal (xxxxxxxx.x) decimal (xxxxxxxx.x) decimal (xxxxxxxx.x) decimal (xxxxxxxx.x) decimal (xxxxxxxx.x) decimal (xxxxxxxx.x) decimal (xxxxxxxx.x) decimal (xxxxxxxx.x) decimal (xxxxxxxx.x) decimal (xxxxxxxx.x) decimal (xxxxxxxx.x) decimal (xxxxxxxx.x) decimal (xxxxxxxx.x) decimal (xxxxxxxx.x) decimal (xxxxxxxx.x) decimal (xxxxxxxx.x) decimal (xxxxxxxx.x) decimal (xxxxxxxx.x) decimal (xxxxxxxx.x) decimal (xxxxxxxx.x) decimal (xxxxxxxx.x)

F90 Format f10.1 f10.1 f10.1 f10.1 f10.1 f10.1 f10.1 f10.1 f10.1 f10.1 f10.1 f10.1 f10.1 f10.1 f10.1 f10.1 f10.1 f10.1 f10.1 f10.1 f10.1 f10.1 f10.1 f10.1 f10.1 f10.1 f10.1 f10.1 f10.1 f10.1 f10.1 f10.1 f10.1 f10.1

224

SWAT USER'S MANUAL, VERSION 2000 Line # 10 10 11 11 11 11 11 11 Position space 41-50 space 51-60 space 1-10 space 11-20 space 21-30 space 31-40 space 41-50 space 51-60 Format decimal (xxxxxxxx.x) decimal (xxxxxxxx.x) decimal (xxxxxxxx.x) decimal (xxxxxxxx.x) decimal (xxxxxxxx.x) decimal (xxxxxxxx.x) decimal (xxxxxxxx.x) decimal (xxxxxxxx.x) F90 Format f10.1 f10.1 f10.1 f10.1 f10.1 f10.1 f10.1 f10.1

Variable name WUDEEP(5) WUDEEP(6) WUDEEP(7) WUDEEP(8) WUDEEP(9) WUDEEP(10) WUDEEP(11) WUDEEP(12)

CHAPTER 21: SWAT INPUT.WUS

225

226

SWAT USER'S MANUAL, VERSION 2000

CHAPTER 22

SWAT INPUT DATA: .SOL

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.

227

228

SWAT USER'S MANUAL, VERSION 2000

Following is a brief description of the variables in the soil input file. They are listed in the order they appear within the file. The soil input file will hold data for up to 10 layers. Variable name TITLE/TEXT Definition 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. Soil name. The soil name is printed in HRU summary tables. HYDGRP Soil hydrologic group (A, B, C, or D) This variable is required only by 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). 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. 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).

SNAM

CHAPTER 22: SWAT INPUT.SOL

229

Variable name HYDGRP, cont.

Definition 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. Guidelines used by USDA Soil Survey to categorize soils into Hydrologic Groups are summarized in Table 22-1.
Table 22-1: Hydrologic Group Rating Criteria Criteria* Hydrologic Soil Groups A B C D Final constant infiltration rate (mm/hr) 7.6-11.4 3.8-7.6 1.3-3.8 0-1.3 Mean permeability: surface layer (mm/hr) > 254.0 84.0-254.0 8.4-84.0 < 8.4 Mean permeability: most restrictive layer > 254.0 84.0-254.0 8.4-84.0 < 8.4
below the surface layer to a depth of 1.0 m (mm/hr) Shrink-swell potential: most restrictive layer** Low Low Moderate High, Very High

Depth to bedrock or cemented pan (mm) > 1016 > 508 > 508 < 508 DUAL HYDROLOGIC GROUPS A/D B/D C/D Mean depth to water table (m) < 0.61 < 0.61 < 0.61 * These criteria are guidelines only. They are based on the theory that the minimum permeability occurs within the uppermost 50 cm. If the minimum permeability occurs between a depth of 50 to 100 cm, then the Hydrologic Soil Group is increased one group. For example, C to B. If the minimum permeability occurs below a depth of 100 cm, the Hydrologic Soil Group is based on the permeability above 100 cm, using the rules previously given. ** Shrink-swell potential is assigned to a profile using the following guidelines: Low: All soils with sand, loamy sand, sandy loam, loam or silt loam horizons that are at least 50 cm thick from the surface without a clay horizon within 100 cm of the surface. Medium: All soils with clay loam horizons within 50 cm of the surface or soils with clay horizons from 50 to 100 cm beneath the surface. High: All soils with clay horizons within 50 cm of the surface. Lower the shrink-swell potential one class when kaolinite clay is dominant.

SOL_ZMX

Maximum rooting depth of soil profile (mm). If no depth is specified, the model assumes the roots can develop throughout the entire depth of the soil profile.

230

SWAT USER'S MANUAL, VERSION 2000

Variable name ANION_EXCL

Definition Fraction of porosity (void space) from which anions are excluded. Most soil minerals are negatively charged at normal pH and the net interaction with anions such as nitrate is a repulsion from particle surfaces. This repulsion is termed negative adsorption or anion exclusion. Anions are excluded from the area immediately adjacent to mineral surfaces due to preferential attraction of cations to these sites. This process has a direct impact on the transport of anions through the soil for it effectively excludes anions from the slowest moving portion of the soil water volume found closest to the charged particle surfaces (Jury et al, 1991). In effect, the net pathway of the anion through the soil is shorter than it would be if all the soil water had to be used (Thomas and McMahon, 1972). If no value for ANION_EXCL is entered, the model will set ANION_EXCL = 0.50

SOL_CRK

Potential or maximum crack volume of the soil profile expressed as a fraction of the total soil volume. To accurately predict surface runoff and infiltration in areas dominated by Vertisols, the temporal change in soil volume must be quantified. Bronswijk (1989, 1990) outlines methods used to determine the maximum crack volume. Optional.

TEXTURE

Texture of soil layer. This data is not processed by the model and the line may be left blank.

SOL_Z(layer #) SOL_BD(layer #)

Depth from soil surface to bottom of layer (mm). Moist bulk density (Mg/m3 or g/cm3). The soil bulk density expresses the ratio of the mass of solid particles to the total volume of the soil, b = MS /VT. In moist bulk density determinations, the mass of the soil is the oven dry weight and the total volume of the soil is determined when the soil is at or near field capacity. Bulk density values should fall between 1.1 and 1.9 Mg/m3.

CHAPTER 22: SWAT INPUT.SOL

231

Variable name SOL_AWC(layer #)

Definition Available water capacity of the soil layer (mm H2O/mm soil). The plant available water, also referred to as the available water capacity, is calculated by subtracting the fraction of water present at permanent wilting point from that present at field capacity, AWC = FC WP where AWC is the plant available water content, FC is the water content at field capacity, and WP is the water content at permanent wilting point. Available water capacity is estimated by determining the amount of water released between in situ field capacity (the soil water content at soil matric potential of -0.033 MPa) and the permanent wilting point (the soil water content at soil matric potential of -1.5 MPa).

SOL_K(layer #)

Saturated hydraulic conductivity (mm/hr). The saturated hydraulic conductivity, Ksat, relates soil water flow rate (flux density) to the hydraulic gradient and is a measure of the ease of water movement through the soil. Ksat is the reciprocal of the resistance of the soil matrix to water flow.

SOL_CBN(layer #)

Organic carbon content (% soil weight). When defining by soil weight, the soil is the portion of the sample that passes through a 2 mm sieve.

CLAY(layer #)

Clay content (% soil weight). The percent of soil particles which are < 0.002 mm in equivalent diameter.

SILT(layer #)

Silt content (% soil weight). The percentage of soil particles which have an equivalent diameter between 0.05 and 0.002 mm.

SAND(layer #)

Sand content (% soil weight). The percentage of soil particles which have a diameter between 2.0 and 0.05 mm.

ROCK(layer #)

Rock fragment content (% total weight). The percent of the sample which has a particle diameter > 2 mm, i.e. the percent of the sample which does not pass through a 2 mm sieve.

232

SWAT USER'S MANUAL, VERSION 2000

Variable name SOL_ALB(layer #)

Definition Moist soil albedo. The ratio of the amount of solar radiation reflected by a body to the amount incident upon it, expressed as a fraction. The value for albedo should be reported when the soil is at or near field capacity.

USLE_K(layer #)

USLE equation soil erodibility (K) factor (units: 0.013 (metric ton m2 hr)/(m3-metric ton cm)). Some soils erode more easily than others even when all other factors are the same. This difference is termed soil erodibility and is caused by the properties of the soil itself. Wischmeier and Smith (1978) define the soil erodibility factor as the soil loss rate per erosion index unit for a specified soil as measured on a unit plot. A unit plot is 22.1-m (72.6-ft) long, with a uniform length-wise slope of 9-percent, in continuous fallow, tilled up and down the slope. Continuous fallow is defined as land that has been tilled and kept free of vegetation for more than 2 years. The units for the USLE soil erodibility factor in MUSLE are numerically equivalent to the traditional English units of 0.01 (ton acre hr)/(acre ft-ton inch). Wischmeier and Smith (1978) noted that a soil type usually becomes less erodible with decrease in silt fraction, regardless of whether the corresponding increase is in the sand fraction or clay fraction. Direct measurement of the erodibility factor is time consuming and costly. Wischmeier et al. (1971) developed a general equation to calculate the soil erodibility factor when the silt and very fine sand content makes up less than 70% of the soil particle size distribution.

KUSLE =

0.00021 M 1.14 (12 OM ) + 3.25 (csoilstr 2 ) + 2.5 (c perm 3) 100

where KUSLE is the soil erodibility factor, M is the particlesize parameter, OM is the percent organic matter (%), csoilstr is the soil structure code used in soil classification, and cperm is the profile permeability class. The particle-size parameter, M, is calculated
M = (msilt + mvfs ) (100 mc )

CHAPTER 22: SWAT INPUT.SOL

233

Variable name USLE_K, cont.

Definition where msilt is the percent silt content (0.002-0.05 mm diameter particles), mvfs is the percent very fine sand content (0.05-0.10 mm diameter particles), and mc is the percent clay content (< 0.002 mm diameter particles). The percent organic matter content, OM, of a layer can be calculated:
OM = 1.72 orgC

where orgC is the percent organic carbon content of the layer (%). Soil structure refers to the aggregation of primary soil particles into compound particles which are separated from adjoining aggregates by surfaces of weakness. An individual natural soil aggregate is called a ped. Field description of soil structure notes the shape and arrangement of peds, the size of peds, and the distinctness and durability of visible peds. USDA Soil Survey terminology for structure consists of separate sets of terms defining each of these three qualities. Shape and arrangement of peds are designated as type of soil structure; size of peds as class; and degree of distinctness as grade. The soil-structure codes for the equation are defined by the type and class of soil structure present in the layer. There are four primary types of structure, several of which are further roken down into subtypes: -Platy, with particles arranged around a plane, generally horizontal -Prismlike, with particles arranged around a verticle line and bounded by relatively flat vertical surfaces Prismatic: without rounded upper ends Columnar: with rounded caps -Blocklike or polyhedral, with particles arranged around a point and bounded by flat or rounded surfaces which are casts of the molds formed by the faces of surrounding peds Angular Blocky: bounded by planes intersecting at relatively sharp angles Subangular Blocky: having mixed rounded and plane faces with vertices mostly rounded

234

SWAT USER'S MANUAL, VERSION 2000

Variable name USLE_K, cont.

Definition -Spheroidal or polyhedral, with particles arranged around a point and bounded by curved or very irregular surfaces that are not accomodated to the adjoining aggregates Granular: relatively non-porous Crumb: very porous The size criteria for the class will vary by type of structure and are summarized in Table 22-2.
Table 22-2: Size classes of soil structure Shape of structure Prismatic and Size Classes Platy Columnar Blocky Very fine < 1 mm < 10 mm < 5 mm Fine 1-2 mm 10-20 mm 5-10 mm Medium 2-5 mm 20-50 mm 10-20 mm Coarse 5-10 mm 50-100 mm 20-50 mm Very coarse > 10 mm > 100 mm > 50 mm

Granular < 1 mm 1-2 mm 2-5 mm 5-10 mm > 10 mm

The codes assigned to csoilstr are: 1 very fine granular 2 fine granular 3 medium or coarse granular 4 blocky, platy, prismlike or massive 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: 1 rapid (> 150 mm/hr) 2 moderate to rapid (50-150 mm/hr) 3 moderate (15-50 mm/hr) 4 slow to moderate (5-15 mm/hr) 5 slow (1-5 mm/hr) 6 very slow (< 1 mm/hr) Williams (1995) proposed an alternative equation: KUSLE = f csand f cl si f orgc f hisand where fcsand is a factor that gives low soil erodibility factors for soils with high coarse-sand contents and high values for soils with little sand, fcl-si is a factor that gives low soil erodibility factors for soils with high clay to silt ratios, forgc is a factor that reduces soil erodibility for soils with high organic carbon content, and fhisand is a factor that

CHAPTER 22: SWAT INPUT.SOL

235

Variable name USLE_K, cont.

Definition reduces soil erodibility for soils with extremely high sand contents. The factors are calculated:

msilt 1 f csand = 0.2 + 0.3 exp 0.256 ms 100

msilt f cl si = m +m silt c 0.25 orgC f orgc = 1 orgC + exp[3.72 2.95 orgC ]
0.3

f hisand

m 0.7 1 s 100 = 1 ms m s 1 exp 5 . 51 22 . 9 1 + + 100 100

where ms is the percent sand content (0.05-2.00 mm diameter particles), msilt is the percent silt content (0.0020.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 (%). SOL_EC(layer #) Electrical conductivity (dS/m). Not currently active The format of the soil input file is:
Variable name TITLE SNAM HYDGRP SOL_ZMX ANION_EXCL SOL_CRK COMMENT LINE SOL_Z(1) SOL_Z(2) SOL_Z(3) SOL_Z(4) Line # 1 2 3 4 5 6 7 8 8 8 8 Position space 1-80 space 13-28 space 25 space 29-35 space 52-56 space 34-38 space 1-147 space 28-39 space 40-51 space 52-63 space 64-75 Format character character character decimal(xxxxxxxxx.xx) decimal(x.xxx) decimal(x.xxx) character decimal(xxxxxxxxx.xx) decimal(xxxxxxxxx.xx) decimal(xxxxxxxxx.xx) decimal(xxxxxxxxx.xx) F90 Format a80 a16 a1 f12.2 f5.3 f5.3 a80 f12.2 f12.2 f12.2 f12.2

236

SWAT USER'S MANUAL, VERSION 2000 Line # 8 8 8 8 8 8 9 9 9 9 9 9 9 9 9 9 10 10 10 10 10 10 10 10 10 10 11 11 11 11 11 11 11 11 11 Position space 76-87 space 88-99 space 100-111 space 112-123 space 124-135 space 136-147 space 28-39 space 40-51 space 52-63 space 64-75 space 76-87 space 88-99 space 100-111 space 112-123 space 124-135 space 136-147 space 28-39 space 40-51 space 52-63 space 64-75 space 76-87 space 88-99 space 100-111 space 112-123 space 124-135 space 136-147 space 28-39 space 40-51 space 52-63 space 64-75 space 76-87 space 88-99 space 100-111 space 112-123 space 124-135 Format decimal(xxxxxxxxx.xx) decimal(xxxxxxxxx.xx) decimal(xxxxxxxxx.xx) decimal(xxxxxxxxx.xx) decimal(xxxxxxxxx.xx) decimal(xxxxxxxxx.xx) decimal(xxxxxxxxx.xx) decimal(xxxxxxxxx.xx) decimal(xxxxxxxxx.xx) decimal(xxxxxxxxx.xx) decimal(xxxxxxxxx.xx) decimal(xxxxxxxxx.xx) decimal(xxxxxxxxx.xx) decimal(xxxxxxxxx.xx) decimal(xxxxxxxxx.xx) decimal(xxxxxxxxx.xx) decimal(xxxxxxxxx.xx) decimal(xxxxxxxxx.xx) decimal(xxxxxxxxx.xx) decimal(xxxxxxxxx.xx) decimal(xxxxxxxxx.xx) decimal(xxxxxxxxx.xx) decimal(xxxxxxxxx.xx) decimal(xxxxxxxxx.xx) decimal(xxxxxxxxx.xx) decimal(xxxxxxxxx.xx) decimal(xxxxxxxxx.xx) decimal(xxxxxxxxx.xx) decimal(xxxxxxxxx.xx) decimal(xxxxxxxxx.xx) decimal(xxxxxxxxx.xx) decimal(xxxxxxxxx.xx) decimal(xxxxxxxxx.xx) decimal(xxxxxxxxx.xx) decimal(xxxxxxxxx.xx) F90 Format f12.2 f12.2 f12.2 f12.2 f12.2 f12.2 f12.2 f12.2 f12.2 f12.2 f12.2 f12.2 f12.2 f12.2 f12.2 f12.2 f12.2 f12.2 f12.2 f12.2 f12.2 f12.2 f12.2 f12.2 f12.2 f12.2 f12.2 f12.2 f12.2 f12.2 f12.2 f12.2 f12.2 f12.2 f12.2

Variable name SOL_Z(5) SOL_Z(6) SOL_Z(7) SOL_Z(8) SOL_Z(9) SOL_Z(10) SOL_BD(1) SOL_BD(2) SOL_BD(3) SOL_BD(4) SOL_BD(5) SOL_BD(6) SOL_BD(7) SOL_BD(8) SOL_BD(9) SOL_BD(10) SOL_AWC(1) SOL_AWC(2) SOL_AWC(3) SOL_AWC(4) SOL_AWC(5) SOL_AWC(6) SOL_AWC(7) SOL_AWC(8) SOL_AWC(9) SOL_AWC(10) SOL_K(1) SOL_K(2) SOL_K(3) SOL_K(4) SOL_K(5) SOL_K(6) SOL_K(7) SOL_K(8) SOL_K(9)

CHAPTER 22: SWAT INPUT.SOL Variable name SOL_K(10) SOL_CBN(1) SOL_CBN(2) SOL_CBN(3) SOL_CBN(4) SOL_CBN(5) SOL_CBN(6) SOL_CBN(7) SOL_CBN(8) SOL_CBN(9) SOL_CBN(10) CLAY(1) CLAY(2) CLAY(3) CLAY(4) CLAY(5) CLAY(6) CLAY(7) CLAY(8) CLAY(9) CLAY(10) SILT(1) SILT(2) SILT(3) SILT(4) SILT(5) SILT(6) SILT(7) SILT(8) SILT(9) SILT(10) SAND(1) SAND(2) SAND(3) SAND(4) Line # 11 12 12 12 12 12 12 12 12 12 12 13 13 13 13 13 13 13 13 13 13 14 14 14 14 14 14 14 14 14 14 15 15 15 15 Position space 136-147 space 28-39 space 40-51 space 52-63 space 64-75 space 76-87 space 88-99 space 100-111 space 112-123 space 124-135 space 136-147 space 28-39 space 40-51 space 52-63 space 64-75 space 76-87 space 88-99 space 100-111 space 112-123 space 124-135 space 136-147 space 28-39 space 40-51 space 52-63 space 64-75 space 76-87 space 88-99 space 100-111 space 112-123 space 124-135 space 136-147 space 28-39 space 40-51 space 52-63 space 64-75 Format decimal(xxxxxxxxx.xx) decimal(xxxxxxxxx.xx) decimal(xxxxxxxxx.xx) decimal(xxxxxxxxx.xx) decimal(xxxxxxxxx.xx) decimal(xxxxxxxxx.xx) decimal(xxxxxxxxx.xx) decimal(xxxxxxxxx.xx) decimal(xxxxxxxxx.xx) decimal(xxxxxxxxx.xx) decimal(xxxxxxxxx.xx) decimal(xxxxxxxxx.xx) decimal(xxxxxxxxx.xx) decimal(xxxxxxxxx.xx) decimal(xxxxxxxxx.xx) decimal(xxxxxxxxx.xx) decimal(xxxxxxxxx.xx) decimal(xxxxxxxxx.xx) decimal(xxxxxxxxx.xx) decimal(xxxxxxxxx.xx) decimal(xxxxxxxxx.xx) decimal(xxxxxxxxx.xx) decimal(xxxxxxxxx.xx) decimal(xxxxxxxxx.xx) decimal(xxxxxxxxx.xx) decimal(xxxxxxxxx.xx) decimal(xxxxxxxxx.xx) decimal(xxxxxxxxx.xx) decimal(xxxxxxxxx.xx) decimal(xxxxxxxxx.xx) decimal(xxxxxxxxx.xx) decimal(xxxxxxxxx.xx) decimal(xxxxxxxxx.xx) decimal(xxxxxxxxx.xx) decimal(xxxxxxxxx.xx)

237

F90 Format f12.2 f12.2 f12.2 f12.2 f12.2 f12.2 f12.2 f12.2 f12.2 f12.2 f12.2 f12.2 f12.2 f12.2 f12.2 f12.2 f12.2 f12.2 f12.2 f12.2 f12.2 f12.2 f12.2 f12.2 f12.2 f12.2 f12.2 f12.2 f12.2 f12.2 f12.2 f12.2 f12.2 f12.2 f12.2

238

SWAT USER'S MANUAL, VERSION 2000 Line # 15 15 15 15 15 15 16 16 16 16 16 16 16 16 16 16 17 17 17 17 17 17 17 17 17 17 18 18 18 18 18 18 18 18 18 Position space 76-87 space 88-99 space 100-111 space 112-123 space 124-135 space 136-147 space 28-39 space 40-51 space 52-63 space 64-75 space 76-87 space 88-99 space 100-111 space 112-123 space 124-135 space 136-147 space 28-39 space 40-51 space 52-63 space 64-75 space 76-87 space 88-99 space 100-111 space 112-123 space 124-135 space 136-147 space 28-39 space 40-51 space 52-63 space 64-75 space 76-87 space 88-99 space 100-111 space 112-123 space 124-135 Format decimal(xxxxxxxxx.xx) decimal(xxxxxxxxx.xx) decimal(xxxxxxxxx.xx) decimal(xxxxxxxxx.xx) decimal(xxxxxxxxx.xx) decimal(xxxxxxxxx.xx) decimal(xxxxxxxxx.xx) decimal(xxxxxxxxx.xx) decimal(xxxxxxxxx.xx) decimal(xxxxxxxxx.xx) decimal(xxxxxxxxx.xx) decimal(xxxxxxxxx.xx) decimal(xxxxxxxxx.xx) decimal(xxxxxxxxx.xx) decimal(xxxxxxxxx.xx) decimal(xxxxxxxxx.xx) decimal(xxxxxxxxx.xx) decimal(xxxxxxxxx.xx) decimal(xxxxxxxxx.xx) decimal(xxxxxxxxx.xx) decimal(xxxxxxxxx.xx) decimal(xxxxxxxxx.xx) decimal(xxxxxxxxx.xx) decimal(xxxxxxxxx.xx) decimal(xxxxxxxxx.xx) decimal(xxxxxxxxx.xx) decimal(xxxxxxxxx.xx) decimal(xxxxxxxxx.xx) decimal(xxxxxxxxx.xx) decimal(xxxxxxxxx.xx) decimal(xxxxxxxxx.xx) decimal(xxxxxxxxx.xx) decimal(xxxxxxxxx.xx) decimal(xxxxxxxxx.xx) decimal(xxxxxxxxx.xx) F90 Format f12.2 f12.2 f12.2 f12.2 f12.2 f12.2 f12.2 f12.2 f12.2 f12.2 f12.2 f12.2 f12.2 f12.2 f12.2 f12.2 f12.2 f12.2 f12.2 f12.2 f12.2 f12.2 f12.2 f12.2 f12.2 f12.2 f12.2 f12.2 f12.2 f12.2 f12.2 f12.2 f12.2 f12.2 f12.2

Variable name SAND(5) SAND(6) SAND(7) SAND(8) SAND(9) SAND(10) ROCK(1) ROCK(2) ROCK(3) ROCK(4) ROCK(5) ROCK(6) ROCK(7) ROCK(8) ROCK(9) ROCK(10) SOL_ALB(1) SOL_ALB(2) SOL_ALB(3) SOL_ALB(4) SOL_ALB(5) SOL_ALB(6) SOL_ALB(7) SOL_ALB(8) SOL_ALB(9) SOL_ALB(10) USLE_K(1) USLE_K(2) USLE_K(3) USLE_K(4) USLE_K(5) USLE_K(6) USLE_K(7) USLE_K(8) USLE_K(9)

CHAPTER 22: SWAT INPUT.SOL Variable name USLE_K(10) SOL_EC(1) SOL_EC(2) SOL_EC(3) SOL_EC(4) SOL_EC(5) SOL_EC(6) SOL_EC(7) SOL_EC(8) SOL_EC(9) SOL_EC(10) Line # 18 19 19 19 19 19 19 19 19 19 19 Position space 136-147 space 28-39 space 40-51 space 52-63 space 64-75 space 76-87 space 88-99 space 100-111 space 112-123 space 124-135 space 136-147 Format decimal(xxxxxxxxx.xx) decimal(xxxxxxxxx.xx) decimal(xxxxxxxxx.xx) decimal(xxxxxxxxx.xx) decimal(xxxxxxxxx.xx) decimal(xxxxxxxxx.xx) decimal(xxxxxxxxx.xx) decimal(xxxxxxxxx.xx) decimal(xxxxxxxxx.xx) decimal(xxxxxxxxx.xx) decimal(xxxxxxxxx.xx)

239

F90 Format f12.2 f12.2 f12.2 f12.2 f12.2 f12.2 f12.2 f12.2 f12.2 f12.2 f12.2

REFERENCES
Bronswijk, J.J.B. 1989. Prediction of actual cracking and subsidence in clay soils. Soil Science 148:87-93. Bronswijk, J.J.B. 1990. Shrinkage geometry of a heavy clay soil at various stresses. Soil Science Soc. Am. J. 54:1500-1502. Natural Resources Conservation Service Soil Survey Staff. 1996. National soil survey handbook, title 430-VI. U.S. Government Printing Office, Washington, D.C. Thomas, G.W. and M. McMahon. 1972. The relation between soil characteristics, water movement and nitrate concentration of ground water. Univ. of Kentucky Water Resources Institute Research Report No. 52, Lexington, KY. Williams, J.R. 1995. Chapter 25. The EPIC Model. p. 909-1000. In Computer Models of Watershed Hydrology. Water Resources Publications. Highlands Ranch, CO. Wischmeier, W.H., C.B. Johnson, and B.V. Cross. 1971. A soil erodibility nomograph for farmland and construction sites. Journal of Soil and Water Conservation 26:189-193.

240

SWAT USER'S MANUAL, VERSION 2000

Wischmeier, W.H., and D.D. Smith. 1978. Predicting rainfall losses: A guide to conservation planning. USDA Agricultural Handbook No. 537. U.S. Gov. Print. Office, Washington, D. C.

CHAPTER 23

SWAT INPUT DATA: .CHM

The soils data used by SWAT can be divided into two groups, physical characteristics and chemical characteristics. Inputs for chemical characteristics are used to set initial levels of the different chemicals in the soil.

241

242

SWAT USER'S MANUAL, VERSION 2000

Following is a brief description of the variables in the soil chemical input file. They are listed in the order they appear within the file. Variable name TITLE Definition The first line of the .chm 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. The second line of the .chm file is reserved for the nutrient data title. This line is not processed by the model and may be left blank. SOIL LAYER Number of soil layer. This line is not processed by the model and may be left blank. SOL_NO3(layer #) Initial NO3 concentration in the soil layer (mg/kg). Users may define the amount of nitrate for all soil layers at the beginning of the simulation. If the user does not specify initial nitrate concentrations, SWAT will initialize levels of nitrate using the equations reviewed in Chapter 10 of the SWAT 2000 Theoretical Documentation. Optional.
SOL_ORGN(layer #)

NUTRIENT TITLE

Initial organic N concentration in the soil layer (mg/kg). Users may define the amount of organic nitrogen contained in humic substances for all soil layers at the beginning of the simulation. If the user does not specify initial nitrogen concentrations, SWAT will initialize levels of organic nitrogen using the equations reviewed in Chapter 10 of the SWAT 2000 Theoretical Documentation. Optional.

SOL_SOLP(layer #)

Initial soluble P concentration in soil layer (mg/kg). Users may define the amount of solution P for all soil layers at the beginning of the simulation. If the user does not specify initial solution P concentrations, SWAT will initialize the concentration to 5 mg P/kg soil in all soil layers. Optional.

CHAPTER 23: SWAT INPUT.CHM

243

Variable name

Definition Users may define the amount of organic phosphorus contained in humic substances for all soil layers at the beginning of the simulation. If the user does not specify initial organic P concentrations, SWAT will initialize levels of organic phosphorus using the equations reviewed in Chapter 11 of the SWAT 2000 Theoretical Documentation. Optional.

SOL_ORGP(layer #) Initial organic P concentration in soil layer (mg/kg).

PESTICIDE TITLE

Lines 8-11 are reserved for the pesticide data titles. These lines are not processed by the model and may be left blank.

PESTNUM PLTPST SOLPST

Number of pesticide from pesticide database. Required if pesticide amounts are given. Initial pesticide amount on foliage (kg/ha). Optional. Initial pesticide amount in soil (mg/kg). The pesticide is assumed to be found at this concentration in all soil layers. Optional.

PSTENR

Enrichment ratio for pesticide in the soil. As surface runoff flows over the soil surface, part of the waters energy is used to pick up and transport soil particles. The smaller particles weigh less and are more easily transported than coarser particles. When the particle size distribution of the transported sediment is compared to that of the soil surface layer, the sediment load to the main channel has a greater proportion of clay sized particles. In other words, the sediment load is enriched in clay particles. The sorbed phase of pesticide in the soil is attached primarily to colloidal (clay) particles, so the sediment load will also contain a greater proportion or concentration of pesticide than that found in the soil surface layer.

244

SWAT USER'S MANUAL, VERSION 2000

Variable name PSTENR, cont.

Definition The enrichment ratio is defined as the ratio of the concentration of sorbed pesticide transported with the sediment to the concentration in the soil surface layer. SWAT will calculate an enrichment ratio for each storm event, or allow the user to define a particular enrichment ratio for sorbed pesticide that is used for all storms during the simulation. To calculate the enrichment ratio, the value for PSTENR is set to zero. The default option is to allow the model to calculate the enrichment ratio

The format of the soil chemical input file is:

Variable name TITLE NUTRIENT TITLE SOIL LAYERS SOL_NO3(1) SOL_NO3(2) SOL_NO3(3) SOL_NO3(4) SOL_NO3(5) SOL_NO3(6) SOL_NO3(7) SOL_NO3(8) SOL_NO3(9) SOL_NO3(10) SOL_ORGN(1) SOL_ORGN(2) SOL_ORGN(3) SOL_ORGN(4) SOL_ORGN(5) SOL_ORGN(6) SOL_ORGN(7) SOL_ORGN(8) SOL_ORGN(9) SOL_ORGN(10) Line # 1 2 3 4 4 4 4 4 4 4 4 4 4 5 5 5 5 5 5 5 5 5 5 Position space 1-80 space 1-80 space 1-80 space 28-39 space 40-51 space 52-63 space 64-75 space 76-87 space 88-99 space 100-111 space 112-123 space 124-135 space 136-147 space 28-39 space 40-51 space 52-63 space 64-75 space 76-87 space 88-99 space 100-111 space 112-123 space 124-135 space 136-147 Format character character character decimal(xxxxxxxxx.xx) decimal(xxxxxxxxx.xx) decimal(xxxxxxxxx.xx) decimal(xxxxxxxxx.xx) decimal(xxxxxxxxx.xx) decimal(xxxxxxxxx.xx) decimal(xxxxxxxxx.xx) decimal(xxxxxxxxx.xx) decimal(xxxxxxxxx.xx) decimal(xxxxxxxxx.xx) decimal(xxxxxxxxx.xx) decimal(xxxxxxxxx.xx) decimal(xxxxxxxxx.xx) decimal(xxxxxxxxx.xx) decimal(xxxxxxxxx.xx) decimal(xxxxxxxxx.xx) decimal(xxxxxxxxx.xx) decimal(xxxxxxxxx.xx) decimal(xxxxxxxxx.xx) decimal(xxxxxxxxx.xx) F90 Format a80 a80 a80 f12.2 f12.2 f12.2 f12.2 f12.2 f12.2 f12.2 f12.2 f12.2 f12.2 f12.2 f12.2 f12.2 f12.2 f12.2 f12.2 f12.2 f12.2 f12.2 f12.2

CHAPTER 23: SWAT INPUT.CHM

245

Variable name SOL_SOLP(1) SOL_SOLP(2) SOL_SOLP(3) SOL_SOLP(4) SOL_SOLP(5) SOL_SOLP(6) SOL_SOLP(7) SOL_SOLP(8) SOL_SOLP(9) SOL_SOLP(10) SOL_ORGP(1) SOL_ORGP(2) SOL_ORGP(3) SOL_ORGP(4) SOL_ORGP(5) SOL_ORGP(6) SOL_ORGP(7) SOL_ORGP(8) SOL_ORGP(9) SOL_ORGP(10) PESTICIDE TITLE PSTNUM PLTPST SOLPST PSTENR

Line # 6 6 6 6 6 6 6 6 6 6 7 7 7 7 7 7 7 7 7 7 8-11 12-END 12-END 12-END 12-END

Position space 28-39 space 40-51 space 52-63 space 64-75 space 76-87 space 88-99 space 100-111 space 112-123 space 124-135 space 136-147 space 28-39 space 40-51 space 52-63 space 64-75 space 76-87 space 88-99 space 100-111 space 112-123 space 124-135 space 136-147 space 1-80

Format decimal(xxxxxxxxx.xx) decimal(xxxxxxxxx.xx) decimal(xxxxxxxxx.xx) decimal(xxxxxxxxx.xx) decimal(xxxxxxxxx.xx) decimal(xxxxxxxxx.xx) decimal(xxxxxxxxx.xx) decimal(xxxxxxxxx.xx) decimal(xxxxxxxxx.xx) decimal(xxxxxxxxx.xx) decimal(xxxxxxxxx.xx) decimal(xxxxxxxxx.xx) decimal(xxxxxxxxx.xx) decimal(xxxxxxxxx.xx) decimal(xxxxxxxxx.xx) decimal(xxxxxxxxx.xx) decimal(xxxxxxxxx.xx) decimal(xxxxxxxxx.xx) decimal(xxxxxxxxx.xx) decimal(xxxxxxxxx.xx) character integer real real real

F90 Format f12.2 f12.2 f12.2 f12.2 f12.2 f12.2 f12.2 f12.2 f12.2 f12.2 f12.2 f12.2 f12.2 f12.2 f12.2 f12.2 f12.2 f12.2 f12.2 f12.2 a80 free free free free

246

SWAT USER'S MANUAL, VERSION 2000

CHAPTER 24

SWAT INPUT DATA: .GW

SWAT partitions groundwater into two aquifer systems: a shallow, unconfined aquifer which contributes return flow to streams within the watershed and a deep, confined aquifer which contributes return flow to streams outside the watershed. The properties governing water movement into and out of the aquifers are initialized in the groundwater input file.

247

248

SWAT USER'S MANUAL, VERSION 2000

Following is a brief description of the variables in the groundwater input file. They are listed in the order they appear within the file. Variable name TITLE Definition The first line of the .gw 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. Initial depth of water in the shallow aquifer (mm H2O). Initial depth of water in the deep aquifer (mm H2O). If no value for DEEPST is entered, the model sets DEEPST = 1000.0 mm. GW_DELAY Groundwater delay time (days). Water that moves past the lowest depth of the soil profile by percolation or bypass flow enters and flows through the vadose zone before becoming shallow aquifer recharge. The lag between the time that water exits the soil profile and enters the shallow aquifer will depend on the depth to the water table and the hydraulic properties of the geologic formations in the vadose and groundwater zones. The delay time, gw, cannot be directly measured. It can be estimated by simulating aquifer recharge using different values for gw and comparing the simulated variations in water table level with observed values. Johnson (1977) developed a simple program to iteratively test and statistically evaluate different delay times for a watershed. Sangrey et al. (1984) noted that monitoring wells in the same area had similar values for gw, so once a delay time value for a geomorphic area is defined, similar delay times can be used in adjoining watersheds within the same geomorphic province. ALPHA_BF Baseflow alpha factor (days). The baseflow recession constant, gw, is a direct index of groundwater flow response to changes in recharge (Smedema and Rycroft, 1983). Values vary from 0.1-0.3 for land with slow response to recharge to 0.9-1.0 for land with a rapid response. Although the baseflow recession constant may be calculated, the best estimates are obtained by analyzing measured streamflow during periods of no recharge in the watershed.

SHALLST DEEPST

CHAPTER 24: SWAT INPUT.GW

249

Variable name ALPHA_BF

Definition It is common to find the baseflow days reported for a stream gage or watershed. This is the number of days for base flow recession to decline through one log cycle. When baseflow days are known, the alpha facter can be calculated: Q 1 1 2 .3 gw = ln gw, N = ln[10] = N BFD Q gw,0 BFD where gw is the baseflow recession constant, and BFD is the number of baseflow days for the watershed

GWQMN

Threshold depth of water in the shallow aquifer required for return flow to occur (mm H2O). Groundwater flow to the reach is allowed only if the depth of water in the shallow aquifer is equal to or greater than GWQMN.

GW_REVAP

Groundwater "revap" coefficient. Water may move from the shallow aquifer into the overlying unsaturated zone. In periods when the material overlying the aquifer is dry, water in the capillary fringe that separates the saturated and unsaturated zones will evaporate and diffuse upward. As water is removed from the capillary fringe by evaporation, it is replaced by water from the underlying aquifer. Water may also be removed from the aquifer by deep-rooted plants which are able to uptake water directly from the aquifer. This process is significant in watersheds where the saturated zone is not very far below the surface or where deep-rooted plants are growing. Because the type of plant cover will affect the importance of revap in the water balance, the parameters governing revap can be varied by land use. As GW_REVAP approaches 0, movement of water from the shallow aquifer to the root zone is restricted. As GW_REVAP approaches 1, the rate of transfer from the shallow aquifer to the root zone approaches the rate of potential evapotranspiration. The value for GW_REVAP should be between 0.02 and 0.20.

250

SWAT USER'S MANUAL, VERSION 2000

Variable name REVAPMN

Definition Threshold depth of water in the shallow aquifer for "revap" or percolation to the deep aquifer to occur (mm H2O). Movement of water from the shallow aquifer to the unsaturated zone or to the deep aquifer is allowed only if the volume of water in the shallow aquifer is equal to or greater than REVAPMN.

RCHRG_DP

Deep aquifer percolation fraction. 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.

GWHT

Initial groundwater height (m). Steady-state groundwater flow and the height of the water table are linearly proportional. The equations used to calculate the change in groundwater height with change in flow are included in SWAT. However, the groundwater height is not currently printed out in any of the output files. This variable is not active.

GW_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 to the total volume of rock. Specific yield is required to calculate groundwater height fluctuations. This variable is not active

GWNO3

Concentration of nitrate in groundwater contribution to streamflow from subbasin (mg N/L). Optional. Concentration of soluble phosphorus in groundwater contribution to streamflow from subbasin (mg P/L). Optional.

GWSOLP

CHAPTER 24: SWAT INPUT.GW

251

The groundwater file is a free format file. The variables may be placed in any position the user wishes on the line. Values for variables classified as integers should not include a decimal while values for variables classified as reals must contain a decimal. A blank space denotes the end of an input value and the beginning of the next value if there is another on the line.
Variable name
TITLE SHALLST DEEPST GW_DELAY ALPHA_BF GWQMN GW_REVAP REVAPMN RCHRG_DP GWHT GW_SPYLD GWNO3 GWSOLP

Line #
1 2 3 4 5 6 7 8 9 10 11 12 13

Format
character real real real real real real real real real real real real

F90 Format
a80 free free free free free free free free free free free free

REFERENCES
Johnson, K.H. 1977. A predictive method for ground water levels. Masters Thesis, Cornell University, Ithica, N.Y. Sangrey, D.A., K.O. Harrop-Williams, and J.A. Klaiber. 1984. Predicting groundwater response to precipitation. ASCE J. Geotech. Eng. 110(7): 957-975. Smedema, L.K. and D.W. Rycroft. 1983. Land drainageplanning and design of agricultural drainage systems, Cornell University Press, Ithica, N.Y.

252

SWAT USER'S MANUAL, VERSION 2000

CHAPTER 25

SWAT INPUT DATA: .RTE

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 main channel input file (.rte) summarizes the physical characteristics of the channel which affect water flow and transport of sediment, nutrients and pesticides.

253

254

SWAT USER'S MANUAL, VERSION 2000

Following is a brief description of the variables in the main channel input file. They are listed in the order they appear within the file. Variable name TITLE Definition The first line of the .rte 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. Average width of main channel at top of bank (m). Depth of main channel from top of bank to bottom (m). Average slope of main channel along the channel length (m/m). Length of main channel (km). Manning's "n" value for the main channel.
Table 25-1: Values of Mannings roughness coefficient, n, for channel flow (Chow, 1959).1 Characteristics of Channel Median Range Excavated or dredged Earth, straight and uniform 0.025 0.016-0.033 Earth, winding and sluggish 0.035 0.023-0.050 Not maintained, weeds and brush 0.075 0.040-0.140 Natural streams Few trees, stones or brush 0.050 0.025-0.065 Heavy timber and brush 0.100 0.050-0.150 1 Chow (1959) has a very extensive list of Mannings roughness coefficients. These values represent only a small portion of those he lists in his book.

CH_W(2) CH_D CH_S(2) CH_L(2) CH_N(2)

CH_K(2)

Effective hydraulic conductivity in main channel alluvium (mm/hr). Streams may be categorized by their relationship to the groundwater system. A stream located in a discharge area that receives groundwater flow is a gaining or effluent stream (Figure 25-1a). This type of stream is characterized by an increase in discharge downstream. A stream located in a recharge area is a losing or influent stream. This type of stream is characterized by a decrease in discharge downstream. A losing stream may be connected to (Figure 25-1b) or perched above (Figure 25-1c) the groundwater flow area. A stream that simultaneously receives and loses groundwater is a flow-through stream (Figure 25-1d).

CHAPTER 25: SWAT INPUT.RTE

255

Variable name CH_K(2), cont.

Definition

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.
Table 25-2: Example hydraulic conductivity values for various bed materials (from Lane, 1983). Bed material group Bed material characteristics Hydraulic conductivity 1 Very clean gravel and large Very high loss rate > 127 mm/hr sand 2 Clean sand and gravel, field High loss rate 51-127 mm/hr conditions 3 Sand and gravel mixture with 25-76 mm/hr Moderately high loss rate low silt-clay content 4 Sand and gravel mixture with Moderate loss rate 6-25 mm/hr high silt-clay content 5 Consolidated bed material; Insignificant to low loss rate high silt-clay content 0.025-2.5 mm/hr

256

SWAT USER'S MANUAL, VERSION 2000

Variable name CH_EROD

Definition Channel erodibility factor. The channel erodibility factor is conceptually similar to the soil erodibility factor used in the USLE equation. Channel erodibility is a function of properties of the bed or bank materials. Channel erodibility can be measured with a submerged vertical jet device. The basic premise of the test is that erosion of a vegetated or bare channel and local scour beneath an impinging jet are the result of hydraulic stresses, boundary geometry, and the properties of the material being eroded. Hanson (1990) developed a method for determining the erodibility coefficient of channels in situ with the submerged vertical jet. Allen et al. (1999) utilized this method to determine channel erodibility factors for thirty sites in Texas. A submerged, vertical jet of water directed perpendicularly at the channel bed causes erosion of the bed material in the vicinity of the jet impact area (Figure 25-2). Important variables in the erosion process are: the volume of material removed during a jetting event, elevation of the jet above the ground surface, diameter of the jet nozzle, jet velocity, time, mass density of the fluid and coefficient of erodibility.

Figure 25-2: Simplified cross-section of submerged jet test (After Allen et al, 1999)

CHAPTER 25: SWAT INPUT.RTE

257

Variable name CH_EROD, cont.

Definition Hanson (1991) defined a jet index, Ji, to relate erodibility to scour created by the submerged jet. The jet index is a function of the depth of scour beneath the jet per unit time and the jet velocity. The jet index is determined by a least squares fit following the procedures outlined in ASTM standard D 5852-95. Once the jet index is determined, the channel erodibility coefficient is calculated: K CH = 0.003 exp[385 J i ] where KCH is the channel erodibility coefficient (cm/h/Pa) and Ji is the jet index. In general, values for channel erodibility are an order of magnitude smaller than values for soil erodibility. CH_EROD is set to a value between 0.0 and 1.0. A value of 0.0 indicates a non-erosive channel while a value of 1.0 indicates no resistance to erosion.

CH_COV

Channel cover factor. The channel cover factor, CCH, is defined as the ratio of degradation from a channel with a specified vegetative cover to the corresponding degradation from a channel with no vegetative cover. The vegetation affects degradation by reducing the stream velocity, and consequently its erosive power, near the bed surface. CH_COV is set to a value between 0.0 and 1.0. A value of 0.0 indicates that the channel is completely protected from degradation by cover while a value of 1.0 indicates there is no vegetative cover on the channel.

CH_WDR

Channel width-depth ratio (m/m). While sediment transport calculations have traditionally been made with the same channel dimensions throughout a simulation, SWAT will model channel downcutting and widening. When channel downcutting and widening is simulated, channel dimensions are allowed to change during the simulation period. Required only if channel degradation is being modeled (IDEG = 1 in .cod).

258

SWAT USER'S MANUAL, VERSION 2000

Variable name ALPHA_BNK

Definition Baseflow alpha factor for bank storage (days). Bank storage contributes flow to the main channel or reach within the subbasin. Bank flow is simulated with a recession curve similar to that used for groundwater.The baseflow alpha factor, or recession constant, characterizes the bank storage recession curve. This constant will be some number less than 1.0, and will be large (approach one) for flat recessions and small (approach zero) for steep recessions. If no value is entered for ALPHA_BNK, the variable will be set to the same value as ALPHA_BF from the groundwater (.gw) file.

The main channel file is a free format file. The variables may be placed in any position the user wishes on the line. Values for variables classified as integers should not include a decimal while values for variables classified as reals must contain a decimal. A blank space denotes the end of an input value and the beginning of the next value if there is another on the line. The format of the main channel input file is:
Variable name TITLE CH_W(2) CH_D CH_S(2) CH_L(2) CH_N(2) CH_K(2) CH_EROD CH_COV CH_WDR ALPHA_BNK Line # 1 2 3 4 5 6 7 8 9 10 11 Format character real real real real real real real real real real F90 Format a80 free free free free free free free free free free

CHAPTER 25: SWAT INPUT.RTE

259

REFERENCES
Allen, P.M., J. Arnold, and E. Jakubowski. 1999. Prediction of stream channel erosion potential. Environmental and Engineering Geoscience 5:339-351. Chow, V.T. 1959. Open-channel hydraulics. McGraw-Hill, New York. Dingman, S.L. 1994. Physical hydrology. Prentice-Hall, Inc., Englewood Cliffs, NJ. Hanson, G.J. 1990. Surface erodibility of earthen channels at high stresses. Part II-Developing an in situ testing device. Trans. ASAE 33:132-137. Hanson, G.J. 1991. Development of a jet index method to characterize erosion resistance of soils in earthen spillways. Trans. ASAE 34:2015-2020. Lane, L.J. 1983. Chapter 19: Transmission Losses. p.19-119-21. In Soil Conservation Service. National engineering handbook, section 4: hydrology. U.S. Government Printing Office, Washington, D.C.

260

SWAT USER'S MANUAL, VERSION 2000

CHAPTER 26

SWAT INPUT DATA: .WWQ

While water quality is a broad subject, the primary areas of concern are nutrients, organic chemicalsboth 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. The data used by SWAT for in-stream water quality processes is contained in two files: the stream water quality input file (.swq) and the general water quality input file (.wwq).

261

262

SWAT USER'S MANUAL, VERSION 2000

Following is a brief description of the variables in the general water quality input file. The variables are listed in the order they appear within the file. Variable name TITLE LAO Definition The first line is reserved for user comments. This line is not processed by the model and may be left blank. Qual2E light averaging option. Qual2E defines four light averaging options. 1 Depth-averaged algal growth attenuation factor for light (FL) is computed from one daylight average solar radiation value calculated in the steady state temperature heat balance. FL is computed from one daylight average solar radiation value supplied by the user. FL is obtained by averaging the hourly daylight values of FL computed from the hourly daylight values of solar radiation calculated in the steady state temperature heat balance. FL is obtained by averaging the hourly daylight values of FL computed from the hourly daylight values of solar radiation calculated from a single value of total daily, photosynthetically active, solar radiation and an assumed cosine function.

2 3

The only option currently active in SWAT is 2. IGROPT Qual2E algal specific growth rate option. Qual2E provides three different options for computing the algal growth rate.
1

Multiplicative: the effects of nitrogen, phosphorus and light are multiplied together to calculate the net effect on the local algal growth rate Limiting nutrient: the local algal growth rate is limited by light and one of the nutrients (nitrogen or phosphorus) Harmonic mean: the local algal growth rate is limited by light and the harmonic mean of the nutrient interactions

CHAPTER 26: SWAT INPUT.WWQ

263

Variable name IGROPT, cont.

Definition The multiplicative option multiplies the growth factors for light, nitrogen and phosphorus together to determine their net effect on the local algal growth rate. This option has its biological basis in the mutiplicative effects of enzymatic processes involved in photosynthesis. The limiting nutrient option calculates the local algal growth rate as limited by light and either nitrogen or phosphorus. The nutrient/light effects are multiplicative, but the nutrient/nutrient effects are alternate. The algal growth rate is controlled by the nutrient with the smaller growth limitation factor. This approach mimics Liebigs law of the minimum. The harmonic mean is mathematically analogous to the total resistance of two resistors in parallel and can be considered a compromise between the multiplicative and limiting nutrient options. The algal growth rate is controlled by a multiplicative relation between light and nutrients, while the nutrient/nutrient interactions are represented by a harmonic mean. The default option is the limiting nutrient option (2).

AI0

Ratio of chlorophyll-a to algal biomass (g-chla/mg algae). Values for AI0 should fall in the range 10-100. If no value for AI0 is entered, the model will set AI0 = 50.0.

AI1

Fraction of algal biomass that is nitrogen (mg N/mg alg). Values for AI1 should fall in the range 0.07-0.09. If no value for AI1 is entered, the model will set AI1 = 0.08.

AI2

Fraction of algal biomass that is phosphorus (mg P/mg alg). Values for AI2 should fall in the range 0.01-0.02. If no value for AI2 is entered, the model will set AI2 = 0.015.

AI3

The rate of oxygen production per unit of algal photosynthesis (mg O2/mg alg). Values for AI3 should fall in the range 1.4-1.8. If no value for AI3 is entered, the model will set AI3 = 1.6.

AI4

The rate of oxygen uptake per unit of algal respiration (mg O2/mg alg). Values for AI4 should fall in the range 1.6-2.3. If no value for AI4 is entered, the model will set AI4 = 2.0.

264

SWAT USER'S MANUAL, VERSION 2000

Variable name AI5

Definition The rate of oxygen uptake per unit of NH3-N oxidation (mg O2/mg NH3-N). Values for AI5 should fall in the range 3.0-4.0. If no value for AI5 is entered, the model will set AI5 = 3.5.

AI6

The rate of oxygen uptake per unit of NO2-N oxidation (mg O2/mg NO2-N). Values for AI6 should fall in the range 1.00-1.14. If no value for AI6 is entered, the model will set AI6 = 1.07.

MUMAX

Maximum specific algal growth rate at 20 C (day-1). Values for MUMAX should fall in the range 1.0-3.0. If no value for MUMAX is entered, the model will set MUMAX = 2.0.

RHOQ

Algal respiration rate at 20 C (day-1). Values for RHOQ should fall in the range 0.05-0.50. If no value for RHOQ is entered, the model will set RHOQ = 0.30.

TFACT

Fraction of solar radiation computed in the temperature heat balance that is photosynthetically active. Values for TFACT should fall in the range 0.01-1.0. If no value for TFACT is entered, the model will set TFACT = 0.3.

K_L

Half-saturation coefficient for light (kJ/(m2min)). Values for K_L should fall in the range 0.2227-1.135. If no value for K_L is entered, the model will set K_L = 0.75.

K_N

Michaelis-Menton half-saturation constant for nitrogen (mg N/L). The Michaelis-Menton half-saturation constant for nitrogen and phosphorus define the concentration of N or P at which algal growth is limited to 50% of the maximum growth rate. Typical values for KN range from 0.01 to 0.30 mg N/L. Values for K_N should fall in the range 0.01-0.30. If no value for K_N is entered, the model will set K_N = 0.02.

CHAPTER 26: SWAT INPUT.WWQ

265

Variable name K_P

Definition Michaelis-Menton half-saturation constant for phosphorus (mg P/L). The Michaelis-Menton half-saturation constant for nitrogen and phosphorus define the concentration of N or P at which algal growth is limited to 50% of the maximum growth rate. Typical values for KP will range from 0.001 to 0.05 mg P/L. If no value for K_P is entered, the model will set K_P = 0.025.

LAMBDA0

Non-algal portion of the light extinction coefficient (m-1). The light extinction coefficient, k l , is calculated as a function of the algal density using the nonlinear equation: k l = k l,0 + k l,1 0 algae + k l, 2 ( 0 algae )
23

where k l,0 is the non-algal portion of the light extinction coefficient (m-1), k l,1 is the linear algal self shading coefficient (m-1 (g-chla/L)-1), k l, 2 is the nonlinear algal self shading coefficient (m-1 (g-chla/L)-2/3), 0 is the ratio of chlorophyll a to algal biomass (g chla/mg alg), and algae is the algal biomass concentration (mg alg/L). This equation allows a variety of algal, self-shading, light extinction relationships to be modeled. When k l ,1 = k l, 2 = 0 , no algal self-shading is simulated. When
k l,1 0 and k l, 2 = 0 , linear algal self-shading is modeled.

When k l,1 and k l, 2 are set to a value other than 0, non-linear algal self-shading is modeled. The Riley equation (Bowie et 1 and al., 1985) defines k l,1 = 0.0088 m -1 (g - chla/L ) k l, 2 = 0.054 m -1 (g - chla/L )
2 3

If no value for LAMBDA0 is entered, the model will set LAMBDA0 = 1.0. LAMBDA1 Linear algal self-shading coefficient (m-1(g chla/L)-1). See explanation for LAMBDA0 for more information on this variable. Values for LAMBDA1 should fall in the range 0.00650.065. If no value for LAMBDA1 is entered, the model will set LAMBDA1 = 0.03.

266

SWAT USER'S MANUAL, VERSION 2000

Variable name LAMBDA2

Definition Nonlinear algal self-shading coefficient (m-1(g chla/L)-2/3). See explanation for LAMBDA0 for more information on this variable. The recommended value for LAMBDA2 is 0.0541. If no value for LAMBDA2 is entered, the model will set LAMBDA2 = 0.054.

P_N

Algal preference factor for ammonia. Values for P_N should fall in the range 0.01-1.0. If no value for P_N is entered, the model will set P_N = 0.5.

The watershed water quality file is a free format file. The variables may be placed in any position the user wishes on the line. Values for variables classified as integers should not include a decimal while values for variables classified as reals must contain a decimal. A blank space denotes the end of an input value and the beginning of the next value if there is another on the line. The format of the general water quality input file is:
Variable name TITLE LAO IGROPT AI0 AI1 AI2 AI3 AI4 AI5 AI6 MUMAX RHOQ TFACT K_L K_N K_P LAMBDA0 Line # 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 Format character integer integer real real real real real real real real real real real real real real F90 Format a80 free free free free free free free free free free free free free free free free

CHAPTER 26: SWAT INPUT.WWQ Variable name LAMBDA1 LAMBDA2 P_N Line # 18 19 20 Format real real real F90 Format free free free

267

REFERENCES
Bowie, G.L. W.B. Mills, D.B. Porcella, C.L. Campbell, J.R. Pagenkopt, G.L. Rupp, K.M. Johnson, P.W.H. Chan, and S.A. Gherini. 1985. Rates, constants, and kinetic formulations in surface water quality modeling, 2nd ed. EPA/600/3-85/040, U.S. Environmental Protection Agency, Athens, GA.

268

SWAT USER'S MANUAL, VERSION 2000

CHAPTER 27

SWAT INPUT DATA: .SWQ

While water quality is a broad subject, the primary areas of concern are nutrients, organic chemicalsboth 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. The data used by SWAT for in-stream water quality processes is contained in two files: the stream water quality input file (.swq) and the general water quality input file (.wwq).

269

270

SWAT USER'S MANUAL, VERSION 2000

Following is a brief description of the variables in the stream water quality input file. The variables are listed in the order they appear within the file. Variable name TITLE NUTRIENT TITLE Definition The first line is reserved for user comments. This line is not processed by the model and may be left blank. The second line is reserved for the nutrient section title. This line is not processed by the model and may be left blank. Local algal settling rate in the reach at 20 C (m/day). Values for RS1 should fall in the range 0.15 to 1.82. If no value for RS1 is entered, the model sets RS1 = 1.0. RS2 Benthic (sediment) source rate for dissolved phosphorus in the reach at 20 C (mg dissolved P/(m2day)). If no value for RS2 is entered, the model sets RS2 = 0.05. RS3 Benthic source rate for NH4-N in the reach at 20 C (mg NH4-N/(m2day)). If no value for RS3 is entered, the model sets RS3 = 0.5. RS4 Rate coefficient for organic N settling in the reach at 20 C (day-1). Values for RS4 should fall in the range 0.001 to 0.10. If no value for RS4 is entered, the model sets RS4 = 0.05. RS5 Organic phosphorus settling rate in the reach at 20 C (day-1). Values for RS5 should fall in the range 0.001 to 0.1. If no value for RS5 is entered, the model sets RS5 = 0.05. RS6 Rate coefficient for settling of arbitrary non-conservative constituent in the reach at 20 C (day-1). If no value for RS6 is entered, the model sets RS6 = 2.5. Not currently used by the model. RS7 Benthic source rate for arbitrary non-conservative constituent in the reach at 20 C (mg ANC/(m2day)). If no value for RS7 is entered, the model sets RS7 = 2.5. Not currently used by the model.

RS1

CHAPTER 27: SWAT INPUT.SWQ

271

Variable name RK1

Definition Carbonaceous biological oxygen demand deoxygenation rate coefficient in the reach at 20 C (day-1). Values for RK1 should fall in the range 0.02 to 3.4. If no value for RK1 is entered, the model sets RK1 = 1.71.

RK2

Oxygen reaeration rate in accordance with Fickian diffusion in the reach at 20 C (day-1). Numerous methods have been developed to calculate the reaeration rate at 20C, 2,20. A few of the methods are listed below. Brown and Barnwell (1987) provide additional methods. Using field measurements, Churchill, Elmore and Buckingham (1962) derived the relationship:

2, 20 = 5.03 vc 0.969 depth 1.673

where 2,20 is the reaeration rate at 20C (day-1), v c is the average stream velocity (m/s), and depth is the average stream depth (m). OConnor and Dobbins (1958) incorporated stream turbulence characteristics into the equations they developed. For streams with low velocities and isotropic conditions,

2, 20

0.5 ( Dm v c ) = 294

depth1.5

where 2,20 is the reaeration rate at 20C (day-1), Dm is the molecular diffusion coefficient (m2/day), v c is the average stream velocity (m/s), and depth is the average stream depth (m). For streams with high velocities and nonisotropic conditions,

2, 20 = 2703

Dm slp 0.25 depth1.25

0.5

where 2,20 is the reaeration rate at 20C (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

Dm = 177 1.037Twater 20

272

SWAT USER'S MANUAL, VERSION 2000

Variable name

Definition

RK2

where Dm is the molecular diffusion coefficient (m2/day), and Twater is the average water temperature (C). Owens et al. (1964) developed an equation to determine the reaeration rate for shallow, fast moving streams where the stream depth is 0.1 to 3.4 m and the velocity is 0.03 to 1.5 m/s. 0.67 v 2, 20 = 5.34 c 1.85 depth where 2,20 is the reaeration rate at 20C (day-1), v c is the average stream velocity (m/s), and depth is the average stream depth (m). Values for RK2 should fall in the range 0.01 to 100.0. If no value for RK2 is entered, the model sets RK2 = 50.0.

RK3

Rate of loss of carbonaceous biological oxygen demand due to settling in the reach at 20 C (day-1). Values for RK3 should fall in the range -0.36 to 0.36. The recommended default for RK3 is 0.36 (not set by model).

RK4

Benthic oxygen demand rate in the reach at 20 C (mg O2/(m2day)). If no value for RK4 is entered, the model sets RK4 = 2.0. Coliform die-off rate in the reach at 20 C (day-1). Values for RK5 should fall in the range 0.05 to 4.0. If no value for RK5 is entered, the model sets RK5 = 2.0. Not currently used by the model.

RK5

RK6

Decay rate for arbitrary non-conservative constituent in the reach at 20 C (day-1). If no value for RK6 is entered, the model sets RK6 = 1.71. Not currently used by the model.

BC1

Rate constant for biological oxidation of NH4 to NO2 in the reach at 20 C in well-aerated conditions (day-1). Values for BC1 should fall in the range 0.1 to 1.0. If no value for BC1 is entered, the model sets BC1 = 0.55.

BC2

Rate constant for biological oxidation of NO2 to NO3 in the reach at 20 C in well-aerated conditions (day-1). Values for BC2 should fall in the range 0.2 to 2.0. If no value for BC2 is entered, the model sets BC2 = 1.1.

CHAPTER 27: SWAT INPUT.SWQ

273

Variable name

Definition

BC3

Rate constant for hydrolysis of organic N to NH4 in the reach at 20 C (day-1). Values for BC3 should fall in the range 0.2 to 0.4. If no value for BC3 is entered, the model sets BC3 = 0.21.

BC4

Rate constant for mineralization of organic P to dissolved P in the reach at 20 C (day-1). Values for BC4 should fall in the range 0.01 to 0.70. If no value for BC4 is entered, the model sets BC4 = 0.35.

PESTICIDE TITLE CHPST_REA

This line is reserved for the pesticide section title. This line is not processed by the model and may be left blank. Pesticide reaction coefficient in reach (day-1). The rate constant is related to the aqueous half-life:
k p ,aq = 0.693 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. CHPST_VOL Pesticide volatilization coefficient in reach (m/day). The volatilization mass-transfer coefficient can be calculated based on Whitmans 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: vv = K l He 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 Henrys constant

274

SWAT USER'S MANUAL, VERSION 2000

Variable name

Definition

CHPST_VOL, cont.

(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 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). OConnor and Dobbins (1956) defined the surface renewal rate as the ratio of the average stream velocity to depth. rl = 86400 vc 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. CHPST_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

where Kd is the pesticide partition coefficient (m3/g) and Kow is the pesticides octanol-water partition coefficient
3 3 (mg m water ) ). ( mg m octanol 1

CHAPTER 27: SWAT INPUT.SWQ

275

Variable name

Definition

CHPST_KOC

Values for the octanol-water partition coefficient have been published for many chemicals. If a published value cannot be found, it can be estimated from solubility (Chapra, 1997): ) log(K ow ) = 5.00 0.670 log( pst sol is the pesticide solubility (moles/L). The where pst sol solubility in these units is calculated:
= pst sol pst sol 10 3 MW

is the pesticide solubility (moles/L), pstsol is where pst sol the pesticide solubility (mg/L) and MW is the molecular weight (g/mole). If no value for CHPST_KOC is entered, the model will set CHPST_KOC = 0. CHPST_STL Settling velocity for pesticide sorbed to sediment (m/day). If no value for CHPST_STL is entered, the model will set CHPST_STL = 1.0. CHPST_RSP Resuspension velocity for pesticide sorbed to sediment (m/day). If no value for CHPST_RSP is entered, the model will set CHPST_RSP = 0.002. CHPST_MIX Mixing velocity (diffusion/dispersion) for pesticide in reach (m/day). The diffusive mixing velocity, vd, can be estimated from the empirically derived formula (Chapra, 1997):
vd = 69.35 MW 2 / 3 365

where vd is the rate of diffusion or mixing velocity (m/day), is the sediment porosity, and MW is the molecular weight of the pesticide compound. If no value for CHPST_MIX is entered, the model will set CHPST_MIX = 0.001.

276

SWAT USER'S MANUAL, VERSION 2000

Variable name

Definition

SEDPST_CONC SEDPST_REA

Initial pesticide concentration in reach bed sediment (mg/m3 sediment). Pesticide reaction coefficient in reach bed sediment (day-1). The rate constant is related to the sediment half-life: k p ,sed = 0.693 t1 / 2,sed

where kp,sed is the rate constant for degradation or removal of pesticide in the sediment (1/day), and t1/2,sed is the sediment half-life for the pesticide (days). If no value for SEDPST_REA is entered, the model will set SEDPST_REA = 0.05. SEDPST_BRY Pesticide burial velocity in reach bed sediment (m/day). If no value for SEDPST_BRY is entered, the model will set SEDPST_BRY = 0.002. SEDPST_ACT Depth of active sediment layer for pesticide (m). If no value for SEDPST_ACT is entered, the model will set SEDPST_ACT = 0.03. The stream water quality file is a free format file. The variables may be placed in any position the user wishes on the line. Values for variables classified as integers should not include a decimal while values for variables classified as reals must contain a decimal. A blank space denotes the end of an input value and the beginning of the next value if there is another on the line. The format of the stream water quality input file is:
Variable name TITLE NUTRIENT TITLE NO DATA NO DATA NO DATA NO DATA NO DATA NO DATA NO DATA Line # 1 2 3 4 5 6 7 8 9 Format character character real real real real real real real F90 Format a80 a80 free free free free free free free

CHAPTER 27: SWAT INPUT.SWQ Variable name NO DATA

QUAL2E TITLE LINE

277

Line # 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40

Format real real real real real real real real real real real real real real real real real real real character real real real real real real real real real real real

F90 Format free free free free free free free free free free free free free free free free free free free a80 free free free free free free free free free free free

RS1 RS2 RS3 RS4 RS5 RS6 RS7 RK1 RK2 RK3 RK4 RK5 RK6 BC1 BC2 BC3 BC4 PESTICIDE TITLE NO DATA CHPST_REA CHPST_VOL CHPST_KOC CHPST_STL CHPST_RSP CHPST_MIX SEDPST_CONC SEDPST_REA SEDPST_BRY SEDPST_ACT

278

SWAT USER'S MANUAL, VERSION 2000

REFERENCES
Brown, L.C. and T.O. Barnwell, Jr. 1987. The enhanced water quality models QUAL2E and QUAL2E-UNCAS documentation and user manual. EPA document EPA/600/3-87/007. USEPA, Athens, GA. Chapra, S.C. 1997. Surface water-quality modeling. McGraw-Hill, Boston. Churchill, M.A., H.L. Elmore, and R.A. Buckingham. 1962. The prediction of stream reaeration rates. International Journal of Air and Water Pollution. 6: 467-504. Danckwerts, P.V. 1951. Significance of liquid-film coefficients in gas absorption. Ind. Eng. Chem. 43:1460-1467. Higbie, R. 1935. The rate of adsorption of a pure gas into a still liquid during short periods of exposure. Trans. Amer. Inst. Chem. Engin. 31:365-389. Lewis, W.K. and W.G. Whitman. 1924. Principles of gas absorption. Ind. Eng. Chem. 16:1215-1220. OConnor, D.J. and W.E. Dobbins. 1958. Mechanism of reaeration in natural streams. Trans. ASCE. 123:641-684. Owens, M. R.W. Edwards, and J.W. Gibbs. 1964. Some reaeration studies in streams. International Journal of Air and Water Pollution 8:469-486. Whitman, W.G. 1923. The two-film theory of gas adsorption. Chem. Metallurg. Eng. 29:146-148.

CHAPTER 28

SWAT INPUT DATA: .PND

Ponds and wetlands are impoundments located within the subbasin area. The .pnd file contains parameter information used to model the water, sediment and nutrient balance for ponds and wetlands.

279

280

SWAT USER'S MANUAL, VERSION 2000

Following is a brief description of the variables in the subbasin pond input file. They are listed in the order they appear within the file. Variable name TITLE Definition 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. The second line of the file is reserved for a section title for the pond data. The title may take up to 80 spaces. The title line is not processed by the model and may be left blank. Fraction of subbasin area that drains into ponds. The value for PND_FR should be between 0.0 and 1.0. PND_PSA PND_PVOL PND_ESA PND_EVOL PND_VOL PND_SED PND_NSED PND_K IFLOD1 IFLOD2 NDTARG Surface area of ponds when filled to principal spillway (ha). Volume of water stored in ponds when filled to the principal spillway (104 m3 H2O). Surface area of ponds when filled to emergency spillway (ha). Volume of water stored in ponds when filled to the emergency spillway (104 m3 H2O). Initial volume of water in ponds (104 m3 H2O). Initial sediment concentration in pond water (mg/L). Equilibrium sediment concentration in pond water (mg/L). Hydraulic conductivity through bottom of ponds (mm/hr). Beginning month of non-flood season. Optional. Ending month of non-flood season. Optional. Number of days needed to reach target storage from current pond storage. The default value for NDTARG is 15 days. Optional. PSETL1 Phosphorus settling rate in pond for months IPND1 through IPND2 (m/year).

POND SECTION TITLE PND_FR

CHAPTER 28: SWAT INPUT.PND

281

Variable name PSETL1, cont.

Definition The apparent settling velocity is most commonly reported in units of m/year and this is how the values are input to the model. For natural lakes, measured phosphorus settling velocities most frequently fall in the range of 5 to 20 m/year although values less than 1 m/year to over 200 m/year have been reported (Chapra, 1997). Panuska and Robertson (1999) noted that the range in apparent settling velocity values for man-made reservoirs tends to be significantly greater than for natural lakes. Higgins and Kim (1981) reported phosphorus apparent settling velocity values from 90 to 269 m/year for 18 reservoirs in Tennessee with a median value of 42.2 m/year. For 27 Midwestern reservoirs, Walker and Kiihner (1978) reported phosphorus apparent settling velocities ranging from 1 to 125 m/year with an average value of 12.7 m/year. A negative settling rate indicates that the reservoir sediments are a source of N or P; a positive settling rate indicates that the reservoir sediments are a sink for N or P. Table 28-1 summarizes typical ranges in phosphorus settling velocity for different systems.
Table 28-1: Recommended apparent settling velocity values for phosphorus (Panuska and Robertson, 1999) Range in settling Nutrient Dynamics velocity values (m/year) Shallow water bodies with high net internal phosphorus flux 0 Water bodies with moderate net internal phosphorus flux 1<<5 Water bodies with minimal net internal phosphorus flux 5 < < 16 Water bodies with high net internal phosphorus removal > 16

PSETL2

Phosphorus settling rate in pond for months other than IPND1-IPND2 (m/year). See explanation for PSETL1 for more information aout this variable.

NSETL1

Nitrogen settling rate in pond for months IPND1 through IPND2 (m/year). See explanation for PSETL1 for more information aout this variable.

282

SWAT USER'S MANUAL, VERSION 2000

Variable name NSETL2

Definition Nitrogen settling rate in pond for months other than IPND1-IPND2 (m/year). See explanation for PSETL1 for more information aout this variable.

CHLA

Chlorophyll a production coefficient for ponds. The user-defined coefficient, Chlaco, is included to allow the user to adjust the predicted chlorophyll a concentration for limitations of nutrients other than phosphorus. When Chlaco is set to 1.00, no adjustments are made (the original equation is used). For most water bodies, the original equation will be adequate. The default value for CHLA is 1.00, which uses the original equation.

SECCI

Water clarity coefficient for ponds. The clarity of the pond is expressed by the secci-disk depth (m) which is calculated as a function of chlorophyll a. The user-defined coefficient, SDco, is included to allow the user to adjust the predicted secchi-disk depth for impacts of suspended sediment and other particulate matter on water clarity that are ignored by the original equation. When SDco is set to 1.00, no adjustments are made (the original equation is used). For most water bodies, the original equation will be adequate. The default value for SECCI is 1.00, which uses the original equation.

PND_NO3 PND_SOLP PND_ORGN PND_ORGP

COMMON VARIABLES SECTION TITLE

Initial concentration of NO3-N in pond (mg N/L). Initial concentration of soluble P in pond (mg P/L). Initial concentration of organic N in pond (mg N/L). Initial concentration of organic P in pond (mg P/L). The 25th line of the file is reserved for a section title for data used for ponds and wetlands. The title may take up to 80 spaces. The title line is not processed by the model and may be left blank. Beginning month of mid-year nutrient settling season. Ending month of mid-year nutrient settling season.

IPND1 IPND2

CHAPTER 28: SWAT INPUT.PND

283

Variable name WETLAND SECTION TITLE WET_FR WET_NSA WET_NVOL WET_MXSA WET_MXVOL WET_VOL WET_SED WET_NSED WET_K PSETLW1

Definition The 28th line of the file is reserved for a section title for the wetland data. The title may take up to 80 spaces. The title line is not processed by the model and may be left blank. Fraction of subbasin area that drains into wetlands. Surface area of wetlands at normal water level (ha). Volume of water stored in wetlands when filled to normal water level (104 m3 H2O). Surface area of wetlands at maximum water level (ha). Volume of water stored in wetlands when filled to maximum water level (104 m3 H2O). Initial volume of water in wetlands (104 m3 H2O). Initial sediment concentration in wetland water (mg/L). Equilibrium sediment concentration in wetland water (mg/L). Hydraulic conductivity of bottom of wetlands (mm/hr). Phosphorus settling rate in wetland for months IPND1 through IPND2 (m/year). See explanation for PSETL1 for more information aout this variable.

PSETLW2

Phosphorus settling rate in wetlands for months other than IPND1-IPND2 (m/year). See explanation for PSETL1 for more information aout this variable.

NSETLW1

Nitrogen settling rate in wetlands for months IPND1 through IPND2 (m/year). See explanation for PSETL1 for more information aout this variable.

NSETLW2

Nitrogen settling rate in wetlands for months other than IPND1-IPND2 (m/year). See explanation for PSETL1 for more information aout this variable.

284

SWAT USER'S MANUAL, VERSION 2000

Variable name CHLAW

Definition Chlorophyll a production coefficient for wetlands. The user-defined coefficient, Chlaco, is included to allow the user to adjust the predicted chlorophyll a concentration for limitations of nutrients other than phosphorus. When Chlaco is set to 1.00, no adjustments are made (the original equation is used). For most water bodies, the original equation will be adequate. The default value for CHLA is 1.00, which uses the original equation.

SECCIW

Water clarity coefficient for wetlands. The clarity of the wetland is expressed by the secci-disk depth (m) which is calculated as a function of chlorophyll a. The user-defined coefficient, SDco, is included to allow the user to adjust the predicted secchi-disk depth for impacts of suspended sediment and other particulate matter on water clarity that are ignored by the original equation. When SDco is set to 1.00, no adjustments are made (the original equation is used). For most water bodies, the original equation will be adequate. The default value for SECCIW is 1.00, which uses the original equation.

WET_NO3 WET_SOLP WET_ORGN WET_ORGP

Initial concentration of NO3-N in wetland (mg N/L). Initial concentration of soluble P in wetland (mg P/L). Initial concentration of organic N in wetland (mg N/L). Initial concentration of organic P in wetland (mg P/L).

CHAPTER 28: SWAT INPUT.PND

285

The pond input file is a free format file. The variables may be placed in any position the user wishes on the line. Values for variables classified as integers should not include a decimal while values for variables classified as reals must contain a decimal. A blank space denotes the end of an input value and the beginning of the next value if there is another on the line. The format of the pond input file is:
Variable name TITLE POND SECT. TITLE PND_FR PND_PSA PND_PVOL PND_ESA PND_EVOL PND_VOL PND_SED PND_NSED PND_K IFLOD1 IFLOD2 NDTARG PSETL1 PSETL2 NSETL1 NSETL2 CHLA SECCI PND_NO3 PND_SOLP PND_ORGN PND_ORGP
POND/WETLAND SECT. TITLE

Line # 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30

Format character character real real real real real real real real real integer integer integer real real real real real real real real real real character integer integer character real real

F90 Format a80 a80 free free free free free free free free free free free free free free free free free free free free free free a80 free free a80 free free

IPND1 IPND2 WETLAND SECT. TITLE WET_FR WET_NSA

286

SWAT USER'S MANUAL, VERSION 2000 Line # 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 Format real real real real real real real real real real real real real real real real real F90 Format free free free free free free free free free free free free free free free free free

Variable name WET_NVOL WET_MXSA WET_MXVOL WET_VOL WET_SED WET_NSED WET_K PSETLW1 PSETLW2 NSETLW1 NSETLW2 CHLAW SECCIW WET_NO3 WET_SOLP WET_ORGN WET_ORGP

REFERENCES
Chapra, S.C. 1997. Surface water-quality modeling. McGraw-Hill, Boston. Higgins, J.M. and B.R. Kim. 1981. Phosphorus retention models for the Tennessee Valley Authority reservoirs. Wat. Resour. Res. 17:571-576. Panuska, J.C. and D.M. Robertson. 1999. Estimating phosphorus concentration following alum treatment using apparent settling velocity. Lake and Reserv. Manage. 15:28-38. Walker, W.W. and J. Kiihner. 1978. An empirical analysis of factors controlling eutrophication in midwestern impoundments. Paper presented at the International Symposium on the Environmental Effects of Hydraulic Engineering Works, Univ. of Tenn., Knoxville.

CHAPTER 29

SWAT INPUT DATA: .RES

Reservoirs or lakes located on the main channel network of the watershed are modeled using input data stored in the reservoir input file (.res) and lake water quality file (.lwq).

287

288

SWAT USER'S MANUAL, VERSION 2000

29.1 RESERVOIR FILE

Following is a brief description of the variables in the reservoir input file. They are listed in the order they appear within the file. Variable name TITLE Definition 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. Number of the subbasin with which the reservoir is associated. Weather for subbasin is used for the reservoir. If no subbasin number is assigned to RES_SUB, the model uses weather data from subbasin 1 to model climatic processes on the reservoir. MORES Month the reservoir became operational (0-12). If 0 is input for MORES and IYRES, the model assumes the reservoir is in operation at the beginning of the simulation. IYRES Year of the simulation the reservoir became operational (eg 1980). If 0 is input for MORES and IYRES, the model assumes the reservoir is in operation at the beginning of the simulation. RES_ESA RES_EVOL RES_PSA RES_PVOL RES_VOL Reservoir surface area when the reservoir is filled to the emergency spillway (ha) Volume of water needed to fill the reservoir to the emergency spillway (104 m3). Reservoir surface area when the reservoir is filled to the principal spillway (ha). Volume of water needed to fill the reservoir to the principal spillway (104 m3). Initial reservoir volume. If the reservoir is in existence at the beginning of the simulation period, the initial reservoir volume is the volume on the first day of simulation. If the reservoir begins operation in the midst of a SWAT simulation, the initial reservoir volume is the volume of the reservoir the day the reservoir becomes operational (104 m3).

RES_SUB

CHAPTER 29: SWAT INPUT.RES

289

Variable name RES_SED RES_NSED RES_K IRESCO

Definition Initial sediment concentration in the reservoir (mg/L). Equilibrium sediment concentration in the reservoir (mg/L). Hydraulic conductivity of the reservoir bottom (mm/hr). Outflow simulation code: 0 compute outflow for uncontrolled reservoir with average annual release rate (if IRESCO=0, need RES_RR) 1 measured monthly outflow (if IRESCO=1, need RESOUT) 2 simulated controlled outflowtarget release (if IRESCO=2, need STARG, IFLOD1R, IFLOD2D, and NDTARGR 3 measured daily outflow (if IRESCO=3, need RESDAYO)

OFLOWMX(mon)

Maximum daily outflow for the month (m3/s). Set all months to zero if you do not want to trigger this requirement.

OFLOWMN(mon)

Minimum daily outflow for the month (m3/s). Set all months to zero if you do not want to trigger this requirement.

RES_RR RESMONO IFLOD1R IFLOD2R NDTARGR

Average daily principal spillway release rate (m3/s). Required if IRESCO = 0. Name of monthly reservoir outflow file. Required if IRESCO = 1. Beginning month of non-flood season. Needed if IRESCO = 2. Ending month of non-flood season. Needed if IRESCO = 2. Number of days to reach target storage from current reservoir storage. Needed if IRESCO = 2. Monthly target reservoir storage (104 m3). Needed if IRESCO = 2.

STARG(mon)

290

SWAT USER'S MANUAL, VERSION 2000

Variable name RESDAYO

WURESN(mon)

Definition Name of daily reservoir outflow file. Required if IRESCO = 3. Average amount of water withdrawn from reservoir each day in the month for consumptive use (104 m3). This variable allows water to be removed from the reservoir for use outside the watershed. Optional.

WURTNF

Fraction of water removed from the reservoir via WURESN that is returned and becomes flow out of reservoir (m3/m3). Optional.

The reservoir file is a free format file. The variables may be placed in any position the user wishes on the line. Values for variables classified as integers should not include a decimal while values for variables classified as reals must contain a decimal. A blank space denotes the end of an input value and the beginning of the next value if there is another on the line. The format of the reservoir input file is:
Variable name TITLE RES_SUB MORES IYRES RES_ESA RES_EVOL RES_PSA RES_PVOL RES_VOL RES_SED RES_NSED RES_K IRESCO COMMENT LINE OFLOWMX(1) OFLOWMX(2) OFLOWMX(3) OFLOWMX(4) Line # 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 15 15 15 Format character integer integer integer real real real real real real real real integer character real real real real F90 Format a80 free free free free free free free free free free free free a80 free free free free

CHAPTER 29: SWAT INPUT.RES

291

Variable name OFLOWMX(5) OFLOWMX(6) COMMENT LINE OFLOWMX(7) OFLOWMX(8) OFLOWMX(9) OFLOWMX(10) OFLOWMX(11) OFLOWMX(12) COMMENT LINE OFLOWMN(1) OFLOWMN(2) OFLOWMN(3) OFLOWMN(4) OFLOWMN(5) OFLOWMN(6) COMMENT LINE OFLOWMN(7) OFLOWMN(8) OFLOWMN(9) OFLOWMN(10) OFLOWMN(11) OFLOWMN(12) RES_RR RESMONO IFLOD1R IFLOD2R NDTARGR COMMENT LINE STARG(1) STARG(2) STARG(3) STARG(4) STARG(5) STARG(6)

Line # 15 15 16 17 17 17 17 17 17 18 19 19 19 19 19 19 20 21 21 21 21 21 21 22 23 24 25 26 27 28 28 28 28 28 28

Format real real character real real real real real real character real real real real real real character real real real real real real real character (len=13) integer integer integer character real real real real real real

F90 Format free free a80 free free free free free free a80 free free free free free free a80 free free free free free free free a13 free free free a80 free free free free free free

292

SWAT USER'S MANUAL, VERSION 2000

Variable name COMMENT LINE STARG(7) STARG(8) STARG(9) STARG(10) STARG(11) STARG(12) RESDAYO COMMENT LINE WURESN(1) WURESN(2) WURESN(3) WURESN(4) WURESN(5) WURESN(6) COMMENT LINE WURESN(7) WURESN(8) WURESN(9) WURESN(10) WURESN(11) WURESN(12) WURTNF

Line # 29 30 30 30 30 30 30 31 32 33 33 33 33 33 33 34 35 35 35 35 35 35 36

Format character real real real real real real character (len=13) character real real real real real real character real real real real real real real

F90 Format a80 free free free free free free a13 a80 free free free free free free a80 free free free free free free free

CHAPTER 29: SWAT INPUT.RES

293

29.2 DAILY RESERVOIR OUTFLOW FILE

When measured daily outflow is used for a reservoir, the name of the file containing the data is assigned to the variable RESDAYO. The daily outflow file contains the flow rate for every day of operation of the reservoir, beginning with the first day of operation in the simulation. The daily outflow file contains one variable: Variable name TITLE Definition The first line of the file is reserved for a description. The description may take up to 80 spaces. The title line is not processed by the model and may be left blank. The water release rate for the day (m3/sec).

RES_OUTFLOW

The format of the daily reservoir outflow file is:

Variable name TITLE RES_OUTFLOW Line # 1 2-END Position space 1-80 space 1-8 Format character decimal(xxxxx.xx) F90 Format a80 f8.2

294

SWAT USER'S MANUAL, VERSION 2000

29.3 MONTHLY RESERVOIR OUTFLOW FILE

When outflow data summarized on a monthly basis is used for a reservoir, the name of the file containing the data is assigned to the variable RESMONO. The monthly outflow file contains the average daily flow rate for every month of operation of the reservoir, beginning with the first month of operation in the simulation. The monthly outflow file contains the following variables: Variable name TITLE Definition The first line of the file is reserved for a description. The description may take up to 80 spaces. The title line is not processed by the model and may be left blank. Measured average daily outflow from the reservoir for the month (m3/s). Needed when IRESCO = 1. There must be a line of input for every year of simulation.

RESOUT(mon,yr)

Variable name TITLE

Line # 1

Format character

F90 Format a80

If IRESCO = 1, the model will read the input data for RESOUT. There should be one line for data for RESOUT for each year of simulation beginning with the 1st year of simulation. RESOUT(1,yr) RESOUT(2,yr) RESOUT(3,yr) RESOUT(4,yr) RESOUT(5,yr) RESOUT(6,yr) RESOUT(7,yr) RESOUT(8,yr) RESOUT(9,yr) RESOUT(10,yr) RESOUT(11,yr) RESOUT(12,yr)
2-END 2-END 2-END 2-END 2-END 2-END 2-END 2-END 2-END 2-END 2-END 2-END

real real real real real real real real real real real real

free free free free free free free free free free free free

CHAPTER 30

SWAT INPUT DATA: .LWQ

While water quality is a broad subject, the primary areas of concern are nutrients, organic chemicalsboth 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. The data used by SWAT for water quality in impoundments located on the main channel network is contained in the lake water quality input file (.lwq).

295

296

SWAT USER'S MANUAL, VERSION 2000

Following is a brief description of the variables in the lake water quality input file. They are listed in the order they appear within the file. Variable name TITLE NUTRIENT TITLE Definition The first line is reserved for user comments. This line is not processed by the model and may be left blank. The second line is reserved for the nutrient section title. This line is not processed by the model and may be left blank. Beginning month of mid-year nutrient settling period. Ending month of mid-year nutrient settling period. Phosphorus settling rate in reservoir for months IRES1 through IRES2 (m/year). The apparent settling velocity is most commonly reported in units of m/year and this is how the values are input to the model. For natural lakes, measured phosphorus settling velocities most frequently fall in the range of 5 to 20 m/year although values less than 1 m/year to over 200 m/year have been reported (Chapra, 1997). Panuska and Robertson (1999) noted that the range in apparent settling velocity values for man-made reservoirs tends to be significantly greater than for natural lakes. Higgins and Kim (1981) reported phosphorus apparent settling velocity values from 90 to 269 m/year for 18 reservoirs in Tennessee with a median value of 42.2 m/year. For 27 Midwestern reservoirs, Walker and Kiihner (1978) reported phosphorus apparent settling velocities ranging from 1 to 125 m/year with an average value of 12.7 m/year. A negative settling rate indicates that the reservoir sediments are a source of N or P; a positive settling rate indicates that the reservoir sediments are a sink for N or P. Table 30-1 summarizes typical ranges in phosphorus settling velocity for different systems.
Table 30-1: Recommended apparent settling velocity values for phosphorus (Panuska and Robertson, 1999) Range in Nutrient Dynamics settling velocity values (m/year) Shallow water bodies with high net internal phosphorus flux 0 Water bodies with moderate net internal phosphorus flux 1<<5 Water bodies with minimal net internal phosphorus flux 5 < < 16 Water bodies with high net internal phosphorus removal > 16

IRES1 IRES2 PSETLR1

CHAPTER 30: SWAT INPUT.LWQ

297

Variable name PSETLR2

Definition Phosphorus settling rate in reservoir for months other than IRES1-IRES2 (m/year). See explanation for PSETLR1 for more information about this parameter.

NSETLR1

Nitrogen settling rate in reservoir for months IRES1 through IRES2 (m/year). See explanation for PSETLR1 for more information about this parameter.

NSETLR2

Nitrogen settling rate in reservoir for months other than IRES1-IRES2 (m/year). See explanation for PSETLR1 for more information about this parameter.

CHLAR

Chlorophyll a production coefficient for reservoir. Chlorophyll a concentration in the reservoir is calculated from the total phosphorus concentration. The equation assumes the system is phosphorus limited. The chlorophyll a coefficient was added to the equation to allow the user to adjust results to account for other factors not taken into account by the basic equation such as nitrogen limitations. The default value for CHLA is 1.00, which uses the original equation.

SECCIR

Water clarity coefficient for the reservoir. The clarity of the reservoir is expressed by the secci-disk depth (m) which is calculated as a function of chlorophyll a. Because suspended sediment also can affect water clarity, the water clarity coefficient has been added to the equation to allow users to adjust for the impact of factors other than chlorophyll a on water clarity. The default value for SECCI is 1.00, which uses the original equation.

RES_ORGP RES_SOLP RES_ORGN RES_NO3

Initial concentration of organic P in reservoir (mg P/L). Initial concentration of soluble P in reservoir (mg P/L). Initial concentration of organic N in reservoir (mg N/L). Initial concentration of NO3-N in reservoir (mg N/L).

298

SWAT USER'S MANUAL, VERSION 2000

Variable name RES_NH3 RES_NO2 PESTICIDE TITLE LKPST_CONC LKPST_REA

Definition Initial concentration of NH3-N in reservoir (mg N/L). Initial concentration of NO2-N in reservoir (mg N/L). This line is reserved for the pesticide section title. This line is not processed by the model and may be left blank. Initial pesticide concentration in the reservoir water for the pesticide defined by IRTPEST (mg/m3). Reaction coefficient of the pesticide in reservoir water (day-1) The rate constant is related to the aqueous half-life:

k p ,aq =

0.693 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) LKPST_VOL Volatilization coefficient of the pesticide from the reservoir (m/day). The volatilization mass-transfer coefficient can be calculated based on Whitmans 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: vv = K l He 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 Henrys 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 lakes, the transfer coefficients are estimated using a stagnant film approach: Dg D Kg = Kl = l zg zl

CHAPTER 30: SWAT INPUT.LWQ

299

Variable name

Definition

LKPST_VOL, cont.

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), zl is the thickness of the liquid film (m), and zg is the thickness of the gas film (m). Alternatively, the transfer coefficients can be estimated with the equations:
32 K l = K l ,O 2 MW
0.25

18 K g = 168 w MW

0.25

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), K l ,O2 is the oxygen transfer coefficient (m/day), MW is the molecular weight of the compound, and w is the wind speed (m/s). Chapra (1997) lists several different equations that can be used to calculate K l ,O2 . LKPST_KOC Pesticide partition coefficient between water and sediment (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

3 3 (mg m water ) ). Values for the octanol-water ( mg m octanol partition coefficient have been published for many chemicals. If a published value cannot be found, it can be estimated from solubility (Chapra, 1997): 1

where Kd is the pesticide partition coefficient (m3/g) and Kow is the pesticides octanol-water partition coefficient

) log(K ow ) = 5.00 0.670 log( pst sol is the pesticide solubility (moles/L). The where pst sol solubility in these units is calculated: pst sol = pst sol 10 3 MW is the pesticide solubility (moles/L), pstsol is where pst sol the pesticide solubility (mg/L) and MW is the molecular weight (g/mole).

300

SWAT USER'S MANUAL, VERSION 2000

Variable name

Definition

LKPST_KOC, cont. LKPST_STL LKPST_RSP LKPST_MIX

LKPST_KOC ranges between 10-4 to 10 m3/g. Settling velocity of pesticide sorbed to sediment (m/day) Resuspension velocity of pesticide sorbed to sediment (m/day). Pesticide diffusion or mixing velocity (m/day) The diffusive mixing velocity, vd, can be estimated from the empirically derived formula (Chapra, 1997):
vd = 69.35 MW 2 / 3 365

where vd is the rate of diffusion or mixing velocity (m/day), is the sediment porosity, and MW is the molecular weight of the pesticide compound. LKSPST_CONC LKSPST_REA Initial pesticide concentration in the reservoir bottom sediments. (mg/m3) Reaction coefficient of pesticide in reservoir bottom sediment (day-1) The rate constant is related to the sediment half-life: k p ,sed = 0.693 t1 / 2,sed

where kp,sed is the rate constant for degradation or removal of pesticide in the sediment (1/day), and t1/2,sed is the sediment half-life for the pesticide (days). LKSPST_BRY LKSPST_ACT Burial velocity of pesticide in reservoir bottom sediment (m/day) Depth of active sediment layer in reservoir (m)

CHAPTER 30: SWAT INPUT.LWQ

301

The lake water quality file is a free format file. The variables may be placed in any position the user wishes on the line. Values for variables classified as integers should not include a decimal while values for variables classified as reals must contain a decimal. A blank space denotes the end of an input value and the beginning of the next value if there is another on the line. The format of the lake water quality input file is:
Variable name TITLE NUTRIENT TITLE IRES1 IRES2 PSETLR1 PSETLR2 NSETLR1 NSETLR2 CHLAR SECCIR RES_ORGP RES_SOLP RES_ORGN RES_NO3 RES_NH3 RES_NO2 PESTICIDE TITLE LKPST_CONC LKPST_REA LKPST_VOL LKPST_KOC LKPST_STL LKPST_RSP LKPST_MIX LKSPST_CONC LKSPST_REA LKSPST_BRY LKSPST_ACT Line # 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 Format character character integer integer real real real real real real real real real real real real character real real real real real real real real real real real F90 Format a80 a80 free free free free free free free free free free free free free free a80 free free free free free free free free free free free

302

SWAT USER'S MANUAL, VERSION 2000

REFERENCES
Chapra, S.C. 1997. Surface water-quality modeling. McGraw-Hill, Boston. Higgins, J.M. and B.R. Kim. 1981. Phosphorus retention models for the Tennessee Valley Authority reservoirs. Wat. Resour. Res. 17:571-576. Lewis, W.K. and W.G. Whitman. 1924. Principles of gas absorption. Ind. Eng. Chem. 16:1215-1220. Panuska, J.C. and D.M. Robertson. 1999. Estimating phosphorus concentration following alum treatment using apparent settling velocity. Lake and Reserv. Manage. 15:28-38. Walker, W.W. and J. Kiihner. 1978. An empirical analysis of factors controlling eutrophication in midwestern impoundments. Paper presented at the International Symposium on the Environmental Effects of Hydraulic Engineering Works, Univ. of Tenn., Knoxville. Whitman, W.G. 1923. The two-film theory of gas adsorption. Chem. Metallurg. Eng. 29:146-148.

CHAPTER 31

SWAT INPUT DATA: MEASURED

SWAT directly simulates the loading of water, sediment and other constituents off of land areas in the watershed. To simulate the loading of water and pollutants from sources not associated with a land area (e.g. sewage treatment plants), SWAT allows point source information to be read in at any point along the channel network. The point source loadings may be summarized on a daily, monthly, yearly, or average annual basis. Files containing the point source loads are created by the user. The loads are read into the model and routed through the channel network using recday, recmon, recyear, or reccnst commands in the watershed configuration file. SWAT will read in water, sediment, organic N, organic P, nitrate, soluble P, ammonium, nitrite, metal, and bacteria data from the point source files. Chapter 2 reviews the format of the command lines in the watershed configuration file while Chapter 31 reviews the format of the point source files.
303

304

SWAT USER'S MANUAL, VERSION 2000

31.1 DAILY RECORDS (RECDAY .DAT FILE)

The recday command in the watershed configuration (.fig) file requires a file containing SWAT input data summarized on a daily time step. An unlimited number of files with daily flow data are allowed in the simulation. The file numbers assigned to the recday files in the watershed configuration file (.fig) must be 1 and numbered sequentially. Following is a brief description of the variables in the recday input file. They are listed in the order they appear within the file. Variable name TITLE DAY Definition The first six lines of the file are reserved for user comments. The comments may take up to 80 spaces per line. Julian date for record If the julian date and year are provided for the records, SWAT will search for the beginning day of simulation in the record. If the julian date and year are left blank, SWAT assumes that the first line of record corresponds to the first day of simulation. (SWAT uses the date and year to locate the record corresponding to the first day of simulation. From that point on, the day and year are ignored.) YEAR FLODAY SEDDAY ORGNDAY ORGPDAY NO3DAY MINPDAY NH3DAY NO2DAY CMTL1DAY Four-digit year for record. See description of DAY for more information. Contribution to streamflow for the day (m3) Sediment loading to reach for the day (metric tons) Organic N loading to reach for the day (kg N) Organic P loading to reach for the day (kg P) NO3 loading to reach for the day (kg N) Mineral P loading to reach for the day (kg P) NH3 loading to reach for the day (kg N) NO2 loading to reach for the day (kg N) Loading of conservative metal #1 to reach for the day (kg)

Please keep in mind that FORTRAN limits the total number of files that can be open at one time to something in the neighborhood of 250. The input files containing daily data (.pcp, .tmp, and recday) remain open throughout the simulation.

CHAPTER 31: SWAT INPUTMEASURED

305

Variable name CMTL2DAY CMTL3DAY BACTPDAY BACTLPDAY

Definition Loading of conservative metal #2 to reach for the day (kg) Loading of conservative metal #3 to reach for the day (kg) Loading of persistent bacteria to reach for the day (# bact) Loading of less persistent bacteria to reach for the day (# bact)

One line of data is required for every day of the simulation period. The recday data file is a free format file. The variables may be placed in any position the user wishes on the line. Values for variables classified as integers should not include a decimal while values for variables classified as reals must contain a decimal. A blank space denotes the end of an input value and the beginning of the next value if there is another on the line. The format of the recday data file is:
Variable name TITLE DAY YEAR FLODAY SEDDAY ORGNDAY ORGPDAY NO3DAY MINPDAY NH3DAY NO2DAY CMTL1DAY CMTL2DAY CMTL3DAY BACTPDAY BACTLPDAY Line # 1-6 7-END 7-END 7-END 7-END 7-END 7-END 7-END 7-END 7-END 7-END 7-END 7-END 7-END 7-END 7-END Format character integer integer real or exponential real or exponential real or exponential real or exponential real or exponential real or exponential real or exponential real or exponential real or exponential real or exponential real or exponential real or exponential real or exponential F90 Format a80 free free free free free free free free free free free free free free free

306

SWAT USER'S MANUAL, VERSION 2000

31.2 MONTHLY RECORDS (RECMON .DAT FILE)

The recmon command in the watershed configuration (.fig) file requires a file containing input data summarized on a monthly time step. SWAT will accept an unlimited number of data files with monthly flow data. The file numbers assigned to the files in the watershed configuration file (.fig) must be numbered sequentially and begin at 1. Following is a brief description of the variables in the recmon data file. They are listed in the order they appear within the file. Variable name TITLE MONTH Definition The first 6 lines of the data file is reserved for user comments. The comments may take up to 80 spaces. Month of measured data. This variable is provided for the userit is ignored by SWAT. The model assumes the first line of measured data in the file contains data for January of the first year of simulation. The monthly data file must contain a line of data for every month of simulation in consecutive order. YEAR 4-digit year of measured data. This variable is provided for the userit is ignored by SWAT. The model assumes the first line of measured data in the file contains data for January of the first year of simulation. The monthly data file must contain a line of data for every month of simulation in consecutive order. FLOMON SEDMON ORGNMON ORGPMON NO3MON MINPMON Average daily water loading for month (m3/day). Average daily sediment loading for month (metric tons/day). Average daily organic nitrogen loading for month (kg N/day). Average daily organic phosphorus loading for month (kg P/day). Average daily nitrate loading for month (kg N/day). Average daily mineral (soluble) P loading for month (kg P/day).

CHAPTER 31: SWAT INPUTMEASURED

307

Variable name NH3MON NO2MON CMTL1MON CMTL2MON CMTL3MON BACTPMON BACTLPMON

Definition Average daily ammonia loading for month (kg N/day). Average daily nitrite loading for month (kg N/day). Average daily loading of conservative metal #1 for month (kg/day). Average daily loading of conservative metal #2 for month (kg/day). Average daily loading of conservative metal #3 for month (kg /day). Average daily loading of persistent bacteria for month (# bact/day). Average daily loading of less persistent bacteria for month (# bact/day).

The file must contain one line of data for every month of simulation (Even if the simulation begins in a month other than January, the file must contain lines for every month of the first year.) The recmon data file is a free format file. The variables may be placed in any position the user wishes on the line. Values for variables classified as integers should not include a decimal while values for variables classified as reals must contain a decimal. A blank space denotes the end of an input value and the beginning of the next value if there is another on the line. The format of the recmon data file is:
Variable name TITLE MONTH YEAR FLOMON SEDMON ORGNMON ORGPMON NO3MON MINPMON NH3MON NO2MON CMTL1MON CMTL2MON CMTL3MON Line # 1-6 7 END 7 END 7 END 7 END 7 END 7 END 7 END 7 END 7 END 7 END 7 END 7 END 7 END Format character integer integer real or exponential real or exponential real or exponential real or exponential real or exponential real or exponential real or exponential real or exponential real or exponential real or exponential real or exponential F90 Format a80 free free free free free free free free free free free free free

308

SWAT USER'S MANUAL, VERSION 2000 Line # 7 END 7 END Format real or exponential real or exponential F90 Format free free

Variable name BACTPMON BACTLPMON

CHAPTER 31: SWAT INPUTMEASURED

309

31.3 YEARLY RECORDS (RECYEAR .DAT FILE)

The recyear command in the watershed configuration (.fig) file requires a file containing SWAT input data summarized on an annual time step. SWAT will accept an unlimited number of data files with yearly flow data. The file numbers assigned to the recyear files in the watershed configuration file (.fig) must be numbered sequentially and begin at 1. Following is a brief description of the variables in the recyear data file. They are listed in the order they appear within the file. Variable name TITLE Definition The first six lines of the data file are reserved for user comments. The comments may take up to 80 spaces per line. 4-digit year of measured data. This variable is provided for the userit is ignored by SWAT. The model assumes the first line of measured data in the file contains data for the first year of simulation. The yearly data file must contain a line of data for every year of simulation in consecutive order. FLOYR SEDYR ORGNYR ORGPYR NO3YR MINPYR NH3YR NO2YR CMTL1YR Average daily water loading for year (m3/day). Average daily sediment loading for year (metric tons/day). Average daily organic nitrogen loading for year (kg N/day). Average daily organic phosphorus loading for year (kg P/day). Average daily nitrate loading for year (kg N/day). Average daily mineral (soluble) P loading for year (kg P/day). Average daily ammonia loading for year (kg N/day). Average daily nitrite loading for year (kg N/day). Average daily loading of conservative metal #1 for year (kg/day).

YEAR

310

SWAT USER'S MANUAL, VERSION 2000

Variable name CMTL2YR CMTL3YR BACTPYR BACTLPYR

Definition Average daily loading of conservative metal #2 for year (kg/day). Average daily loading of conservative metal #3 for year (kg/day). Average daily loading of persistent bacteria for year (# bact/day). Average daily loading of less persistent bacteria for year (# bact/day).

The recyear data file is a free format file. The variables may be placed in any position the user wishes on the line. Values for variables classified as integers should not include a decimal while values for variables classified as reals must contain a decimal. A blank space denotes the end of an input value and the beginning of the next value if there is another on the line.The format of the recyear data file is:
Variable name TITLE YEAR FLOYR SEDYR ORGNYR ORGPYR NO3YR MINPYR NH3YR NO2YR CMTL1YR CMTL2YR CMTL3YR BACTPYR BACTLPYR Line # 1-6 7 - END 7 - END 7 - END 7 - END 7 - END 7 - END 7 - END 7 - END 7 - END 7 - END 7 - END 7 - END 7 - END 7 - END Format character integer real or exponential real or exponential real or exponential real or exponential real or exponential real or exponential real or exponential real or exponential real or exponential real or exponential real or exponential real or exponential real or exponential F90 Format a80 free free free free free free free free free free free free free free

CHAPTER 31: SWAT INPUTMEASURED

311

31.4 AVERAGE ANNUAL RECORDS (RECCNST .DAT FILE)

The reccnst command in the watershed configuration (.fig) file requires a file containing average annual SWAT input data. SWAT will accept an unlimited number of data files with average annual flow data. The file numbers assigned to the reccnst files in the watershed configuration file (.fig) must be numbered sequentially and begin at 1. Following is a brief description of the variables in the reccnst data file. They are listed in the order they appear within the file. Variable name TITLE Definition The first six lines of the data file are reserved for user comments. The comments may take up to 80 spaces on each line. Average daily water loading (m3/day) Average daily sediment loading (metric tons/day) Average daily organic N loading (kg N/day) Average daily organic P loading (kg P/day) Average daily NO3 loading (kg N/day) Average daily mineral P loading (kg P/day) Average daily NH3 loading (kg N/day) Average daily NO2 loading (kg N/day) Average daily loading of conservative metal #1 (kg/day) Average daily loading of conservative metal #2 (kg/day) Average daily loading of conservative metal #3 (kg/day) Average daily loading of persistent bacteria (# bact/day) Average daily loading of less persistent bacteria (# bact/day)

FLOCNST SEDCNST ORGNCNST ORGPCNST NO3CNST MINPCNST NH3CNST NO2CNST CMTL1CNST CMTL2CNST CMTL3CNST BACTPCNST BACTLPCNST

312

SWAT USER'S MANUAL, VERSION 2000

The format of the reccnst data file is:

Variable name TITLE FLOCNST SEDCNST ORGNCNST ORGPCNST NO3CNST MINPCNST NH3CNST NO2CNST CMTL1CNST CMTL2CNST CMTL3CNST BACTPCNST BACTLPCNST Line # 1-6 7 7 7 7 7 7 7 7 7 7 7 7 7 Format character real or exponential real or exponential real or exponential real or exponential real or exponential real or exponential real or exponential real or exponential real or exponential real or exponential real or exponential real or exponential real or exponential F90 Format a80 free free free free free free free free free free free free free

CHAPTER 32

SWAT OUTPUT DATA: PRIMARY OUTPUT FILES

A number of output files are generated in every SWAT simulation. These files are: the summary output file (output.std), the HRU output file (.sbs), the subbasin output file (.bsb), and the main channel or reach output file (.rch). The detail of the data printed out in each file is controlled by the print codes in the input control code (.cod) file. Average daily values are always printed in the HRU, subbasin and reach files, but the time period they are summarized over will vary. Depending on the print code selected, the output files may include all daily values, daily amounts averaged over the month, daily amounts averaged over the year, or daily amounts averaged over the entire simulation period.

313

314

SWAT USER'S MANUAL, VERSION 2000

32.1 INPUT SUMMARY FILE (INPUT.STD)

The input summary file prints summary tables of important input values. This file provides the user with a mechanism to spot-check input values. All model inputs are not printed, but the file does contain some of the most important.

32.2 OUTPUT SUMMARY FILE (OUTPUT.STD)

The output summary file provides watershed average loadings from the HRUs to the streams. Tables are also included that present average annual HRU and subbasin values for a few parameters.

CHAPTER 32: SWAT OUTPUTPRIMARY FILES

315

32.3 HRU OUTPUT FILE (.SBS)

The HRU output file contains summary information for each of the hydrologic response units in the watershed. The file is written in spreadsheet format. Following is a brief description of the output variables in the HRU output file. Variable name LULC HRU GIS SUB MGT Definition Four letter character code for the cover/plant on the HRU. (code from crop.dat file) Hydrologic response unit number GIS code reprinted from watershed configuration file (.fig). See explanation of subbasin command. Topographically-defined subbasin to which the HRU belongs. Management number. This is pulled from the management (.mgt) file. Used by the SWAT/GRASS interface to allow development of output maps by landuse/management type. Daily time step: the julian date Monthly time step: the month (1-12) Annual time step: four-digit year Average annual summary lines: total number of years averaged together Drainage area of the HRU (km2). Total amount of precipitation falling on the HRU during time step (mm H2O). Amount of precipitation falling as snow, sleet or freezing rain during time step (water-equivalent mm H2O). Amount of snow or ice melting during time step (waterequivalent mm H2O). Irrigation (mm H2O). Amount of irrigation water applied to HRU during the time step. Potential evapotranspiration (mm H2O). Potential evapotranspiration from the HRU during the time step. Actual evapotranspiration (soil evaporation and plant transpiration) from the HRU during the time step (mm H2O).

MON

AREA PRECIP SNOFALL SNOMELT IRR PET ET

316

SWAT USER'S MANUAL, VERSION 2000

Variable name SW PERC

Definition Soil water content (mm H2O). Amount of water in the soil profile at the end of the time period. Water that percolates past the root zone during the time step (mm H2O). There is usually a lag between the time the water leaves the bottom of the root zone and reaches the shallow aquifer. Over a long period of time, this variable should equal groundwater recharge (PERC = GW_RCHG as time ). Recharge entering aquifers during time step (total amount of water entering shallow and deep aquifers during time step) (mm H2O). Deep aquifer recharge (mm H2O). The amount of water from the root zone that recharges the deep aquifer during the time step. (shallow aquifer recharge = GW_RCHG - DA_RCHG) Water in the shallow aquifer returning to the root zone in response to a moisture deficit during the time step (mm H2O). The variable also includes water uptake directly from the shallow aquifer by deep tree and shrub roots. Irrigation from shallow aquifer (mm H2O). Amount of water removed from the shallow aquifer for irrigation during the time step. Irrigation from deep aquifer (mm H2O). Amount of water removed from the deep aquifer for irrigation during the time step. Shallow aquifer storage (mm H2O). Amount of water in the shallow aquifer at the end of the time period. Deep aquifer storage (mm H2O). Amount of water in the deep aquifer at the end of the time period. Surface runoff contribution to streamflow in the main channel during time step (mm H2O). Transmission losses (mm H2O). Water lost from tributary channels in the HRU via transmission through the bed. This water becomes recharge for the shallow aquifer during the time step. Net surface runoff contribution to the main channel streamflow is calculated by subtracting TLOSS from SURQ. Lateral flow contribution to streamflow (mm H2O). Water flowing laterally within the soil profile that enters the main channel during time step.

GW_RCHG

DA_RCHG

REVAP

SA_IRR

DA_IRR

SA_ST DA_ST SURQ TLOSS

LATQ

CHAPTER 32: SWAT OUTPUTPRIMARY FILES

317

Variable name GW_Q

Definition Groundwater contribution to streamflow (mm H2O). Water from the shallow aquifer that enters the main channel during the time step. Groundwater flow is also referred to as baseflow. Water yield (mm H2O). Total amount of water leaving the HRU and entering main channel during the time step. (WYLD = SURQ + LATQ + GWQ TLOSS pond abstractions) Sediment yield (metric tons/ha). Sediment from the HRU that is transported into the main channel during the time step. Soil loss during the time step calculated with the USLE equation (metric tons/ha). This value is reported for comparison purposes only. Nitrogen fertilizer applied (kg N/ha). Total amount of nitrogen (mineral and organic) applied in fertilizer during the time step. Phosphorus fertilizer applied (kg P/ha). Total amount of phosphorus (mineral and organic) applied in fertilizer during the time step. Nitrogen fertilizer auto-applied (kg N/ha). Total amount of nitrogen (mineral and organic) auto-applied during the time step. Phosphorus fertilizer auto-applied (kg P/ha). Total amount of phosphorus (mineral and organic) auto-applied during the time step. Nitrogen applied during grazing operation (kg N/ha). Total amount of nitrogen (mineral and organic) added to soil by grazing operation during the time step. Phosphorus applied during grazing operation (kg P/ha). Total amount of phosphorus (mineral and organic) added to soil by grazing operation during the time step. Nitrate added to soil profile by rain (kg N/ha). Nitrogen fixation (kg N/ha). Amount of nitrogen fixed by legumes during the time step.

WYLD

SYLD USLE

N_APP

P_APP

NAUTO

PAUTO

NGRZ

PGRZ

NRAIN NFIX

318

SWAT USER'S MANUAL, VERSION 2000

Variable name F-MN

Definition Fresh organic to mineral N (kg N/ha). Mineralization of nitrogen from the fresh residue pool to the nitrate (80%) pool and active organic nitrogen (20%) pool during the time step. A positive value denotes a net gain in the nitrate and active organic pools from the fresh organic pool while a negative value denotes a net gain in the fresh organic pool from the nitrate and active organic pools. Active organic to mineral N (kg N/ha). Movement of nitrogen from the active organic pool to the nitrate pool during the time step. Active organic to stable organic N (kg N/ha). Movement of nitrogen from the active organic pool to the stable organic pool during the time step. Fresh organic to mineral P (kg P/ha). Mineralization of phosphorus from the fresh residue pool to the "active" mineral (80%) pool (P sorbed to soil surface) and the active organic (20%) pool. A positive value denotes a net gain in the active mineral and active organic pools from the fresh organic pool while a negative value denotes a net gain in the fresh organic pool from the active mineral and active organic pools. Organic to labile mineral P (kg P/ha). Movement of phosphorus between the organic pool and the labile mineral pool during the time step. A positive value denotes a net gain in the labile pool from the organic pool while a negative value denotes a net gain in the organic pool from the labile pool. Labile to active mineral P (kg P/ha). Movement or transformation of phosphorus between the "labile" mineral pool (P in solution) and the "active" mineral pool (P sorbed to the surface of soil particles) during the time step. A positive value denotes a net gain in the active pool from the labile pool while a negative value denotes a net gain in the labile pool from the active pool. Active to stable P (kg P/ha). Movement or transformation of phosphorus between the "active" mineral pool (P sorbed to the surface of soil particles) and the "stable" mineral pool (P fixed in soil) during the time step. A positive value denotes a net gain in the stable pool from the active pool while a negative value denotes a net gain in the active pool from the stable pool.

A-MN

A-SN

F-MP

AO-LP

L-AP

A-SP

CHAPTER 32: SWAT OUTPUTPRIMARY FILES

319

Variable name DNIT NUP PUP ORGN ORGP SEDP NSURQ NLATQ NO3L

Definition Denitrification (kg N/ha). Transformation of nitrate to gaseous compounds during the time step. Plant uptake of nitrogen (kg N/ha). Nitrogen removed from soil by plants during the time step. Plant uptake of phosphorus (kg P/ha). Phosphorus removed from soil by plants during the time step. Organic N yield (kg N/ha). Organic nitrogen transported out of the HRU and into the reach during the time step. Organic P yield (kg P/ha). Organic phosphorus transported with sediment into the reach during the time step. Sediment P yield (kg P/ha). Mineral phosphorus sorbed to sediment transported into the reach during the time step. NO3 in surface runoff (kg N/ha). Nitrate transported with surface runoff into the reach during the time step. NO3 in lateral flow (kg N/ha). Nitrate transported by lateral flow into the reach during the time step. NO3 leached from the soil profile (kg N/ha). Nitrate that leaches past the bottom of the soil profile during the time step. The nitrate is not tracked through the shallow aquifer. NO3 transported into main channel in the groundwater loading from the HRU (kg N/ha). Soluble P yield (kg P/ha). Soluble mineral forms of phosphorus transported by surface runoff into the reach during the time step. Soluble phosphorus transported by groundwater flow into main channel during the time step (kg P/ha). Water stress days during the time step (days). Temperature stress days during the time step (days). Nitrogen stress days during the time step (days). Phosphorus stress days during the time step (days). Biomass (metric tons/ha). Total biomass, i.e. aboveground and roots at the end of the time period reported as dry weight. Leaf area index at the end of the time period.

NO3GW SOLP

P_GW W_STRS TMP_STRS N_STRS P_STRS BIOM LAI

320

SWAT USER'S MANUAL, VERSION 2000

Variable name YLD

Definition Harvested yield (metric tons/ha). The model partitions yield from the total biomass on a daily basis (and reports it). However, the actual yield is not known until it is harvested. The harvested yield is reported as dry weight. Number of persistent bacteria in surface runoff entering reach (count). Number of less persistent bacteria in surface runoff entering reach (count).

BACTP BACTLP

The file format for the HRU output file (.sbs) is:
Variable name LULC HRU GIS SUB MGT MON AREA PRECIP SNOFALL SNOMELT IRR PET ET SW PERC GW_RCHG DA_RCHG REVAP SA_IRR DA_IRR SA_ST DA_ST SURQ Line # All All All All All All All All All All All All All All All All All All All All All All All Position space 1-4 space 5-8 space 10-17 space 19-22 space 24-27 space 29-32 space 33-42 space 43-52 space 53-62 space 63-72 space 73-82 space 83-92 space 93-102 space 103-112 space 113-122 space 123-132 space 133-142 space 143-152 space 153-162 space 163-172 space 173-182 space 183-192 space 193-202 Format character 4-digit integer 8-digit integer 4-digit integer 4-digit integer 4-digit integer decimal(xxxxxx.xxx) decimal(xxxxxx.xxx) decimal(xxxxxx.xxx) decimal(xxxxxx.xxx) decimal(xxxxxx.xxx) decimal(xxxxxx.xxx) decimal(xxxxxx.xxx) decimal(xxxxxx.xxx) decimal(xxxxxx.xxx) decimal(xxxxxx.xxx) decimal(xxxxxx.xxx) decimal(xxxxxx.xxx) decimal(xxxxxx.xxx) decimal(xxxxxx.xxx) decimal(xxxxxx.xxx) decimal(xxxxxx.xxx) decimal(xxxxxx.xxx) F90 Format a4 i4 i8 i4 i4 i4 f10.3 f10.3 f10.3 f10.3 f10.3 f10.3 f10.3 f10.3 f10.3 f10.3 f10.3 f10.3 f10.3 f10.3 f10.3 f10.3 f10.3

CHAPTER 32: SWAT OUTPUTPRIMARY FILES Variable name TLOSS LATQ GW_Q WYLD SYLD USLE N_APP P_APP NAUTO PAUTO NGRZ PGRZ NRAIN NFIX F-MN A-MN A-SN F-MP AO-LP L-AP A-SP DNIT NUP PUP ORGN ORGP SEDP NSURQ NLATQ NO3L NO3GW SOLP P_GW W_STRS TMP_STRS Line # All All All All All All All All All All All All All All All All All All All All All All All All All All All All All All All All All All All Position space 203-212 space 213-222 space 223-232 space 233-242 space 243-252 space 253-262 space 263-272 space 273-282 space 283-292 space 293-302 space 303-312 space 313-322 space 323-332 space 333-342 space 343-352 space 353-362 space 363-372 space 373-382 space 383-392 space 393-402 space 403-412 space 413-422 space 423-432 space 433-442 space 443-452 space 453-462 space 463-472 space 473-482 space 483-492 space 493-502 space 503-512 space 513-522 space 523-532 space 533-542 space 543-552 Format decimal(xxxxxx.xxx) decimal(xxxxxx.xxx) decimal(xxxxxx.xxx) decimal(xxxxxx.xxx) decimal(xxxxxx.xxx) decimal(xxxxxx.xxx) decimal(xxxxxx.xxx) decimal(xxxxxx.xxx) decimal(xxxxxx.xxx) decimal(xxxxxx.xxx) decimal(xxxxxx.xxx) decimal(xxxxxx.xxx) decimal(xxxxxx.xxx) decimal(xxxxxx.xxx) decimal(xxxxxx.xxx) decimal(xxxxxx.xxx) decimal(xxxxxx.xxx) decimal(xxxxxx.xxx) decimal(xxxxxx.xxx) decimal(xxxxxx.xxx) decimal(xxxxxx.xxx) decimal(xxxxxx.xxx) decimal(xxxxxx.xxx) decimal(xxxxxx.xxx) decimal(xxxxxx.xxx) decimal(xxxxxx.xxx) decimal(xxxxxx.xxx) decimal(xxxxxx.xxx) decimal(xxxxxx.xxx) decimal(xxxxxx.xxx) decimal(xxxxxx.xxx) decimal(xxxxxx.xxx) decimal(xxxxxx.xxx) decimal(xxxxxx.xxx) decimal(xxxxxx.xxx) F90 Format f10.3 f10.3 f10.3 f10.3 f10.3 f10.3 f10.3 f10.3 f10.3 f10.3 f10.3 f10.3 f10.3 f10.3 f10.3 f10.3 f10.3 f10.3 f10.3 f10.3 f10.3 f10.3 f10.3 f10.3 f10.3 f10.3 f10.3 f10.3 f10.3 f10.3 f10.3 f10.3 f10.3 f10.3 f10.3

321

322

SWAT USER'S MANUAL, VERSION 2000 Line # All All All All All All All Position space 553-562 space 563-572 space 573-582 space 583-592 space 593-602 space 603-612 space 613-622 Format decimal(xxxxxx.xxx) decimal(xxxxxx.xxx) decimal(xxxxxx.xxx) decimal(xxxxxx.xxx) decimal(xxxxxx.xxx) decimal(xxxxxx.xxx) decimal(xxxxxx.xxx) F90 Format f10.3 f10.3 f10.3 f10.3 f10.3 f10.3 f10.3

Variable name N_STRS P_STRS BIOM LAI YLD BACTP BACTLP

CHAPTER 32: SWAT OUTPUTPRIMARY FILES

323

32.4 SUBBASIN OUTPUT FILE (.BSB)

The subbasin output file contains summary information for each of the subbasins in the watershed. The reported values for the different variables are the total amount or weighted average of all HRUs within the subbasin. The subbasin output file is written in spreadsheet format. Following is a brief description of the output variables in the subbasin output file.

Variable name SUB GIS MON

Definition Subbasin number. GIS code reprinted from watershed configuration file (.fig). See explanation of subbasin command. Daily time step: julian date Monthly time step: the month (1-12) Annual time step: four-digit year Average annual summary lines: total number of years averaged together Area of the subbasin (km2). Total amount of precipitation falling on the subbasin during time step (mm H2O). Amount of snow or ice melting during time step (waterequivalent mm H2O). Potential evapotranspiration from the subbasin during the time step (mm H2O). Actual evapotranspiration from the subbasin during the time step (mm). Soil water content (mm). Amount of water in the soil profile at the end of the time period.

AREA PRECIP SNOMELT PET ET SW

324

SWAT USER'S MANUAL, VERSION 2000

Variable name PERC

Definition Water that percolates past the root zone during the time step (mm). There is potentially a lag between the time the water leaves the bottom of the root zone and reaches the shallow aquifer. Over a long period of time, this variable should equal groundwater percolation. Surface runoff contribution to streamflow during time step (mm H2O). Groundwater contribution to streamflow (mm). Water from the shallow aquifer that returns to the reach during the time step. Water yield (mm H2O). The net amount of water that leaves the subbasin and contributes to streamflow in the reach during the time step. (WYLD = SURQ + LATQ + GWQ TLOSS pond abstractions) Sediment yield (metric tons/ha). Sediment from the subbasin that is transported into the reach during the time step. Organic N yield (kg N/ha). Organic nitrogen transported out of the subbasin and into the reach during the time step. Organic P yield (kg P/ha). Organic phosphorus transported with sediment into the reach during the time step. NO3 in surface runoff (kg N/ha). Nitrate transported by the surface runoff into the reach during the time step. Soluble P yield (kg P/ha). Phosphorus that is transported by surface runoff into the reach during the time step. Mineral P yield (kg P/ha). Mineral phosphorus attached to sediment that is transported by surface runoff into the reach during the time step.

SURQ GW_Q

WYLD

SYLD

ORGN ORGP

NSURQ SOLP SEDP

CHAPTER 32: SWAT OUTPUTPRIMARY FILES

325

The format of the subbasin output file (.bsb) is:

Variable name SUB GIS MON AREA PRECIP SNOMELT PET ET SW PERC SURQ GW_Q WYLD SYLD ORGN ORGP NSURQ SOLP SEDP Line # All All All All All All All All All All All All All All All All All All All Position space 7-10 space 12-19 space 21-24 space 25-34 space 35-44 space 45-54 space 55-64 space 65-74 space 75-84 space 85-94 space 95-104 space 105-114 space 115-124 space 125-134 space 135-144 space 145-154 space 155-164 space 165-174 space 175-184 Format 4-digit integer 8-digit integer 4-digit integer decimal(xxxxxx.xxx) decimal(xxxxxx.xxx) decimal(xxxxxx.xxx) decimal(xxxxxx.xxx) decimal(xxxxxx.xxx) decimal(xxxxxx.xxx) decimal(xxxxxx.xxx) decimal(xxxxxx.xxx) decimal(xxxxxx.xxx) decimal(xxxxxx.xxx) decimal(xxxxxx.xxx) decimal(xxxxxx.xxx) decimal(xxxxxx.xxx) decimal(xxxxxx.xxx) decimal(xxxxxx.xxx) decimal(xxxxxx.xxx) F90 Format i4 i8 i4 f10.3 f10.3 f10.3 f10.3 f10.3 f10.3 f10.3 f10.3 f10.3 f10.3 f10.3 f10.3 f10.3 f10.3 f10.3 f10.3

326

SWAT USER'S MANUAL, VERSION 2000

32.5 MAIN CHANNEL OUTPUT FILE (.RCH)

The main channel output file contains summary information for each routing reach in the watershed. The file is written in spreadsheet format. Following is a brief description of the output variables in the .rch file. Variable name RCH GIS MON Definition Reach number. The reach number is also the hydrograph number of the subbasin as defined in the .fig file. GIS number reprinted from watershed configuration (.fig) file. See explanation of subbasin command. Daily time step: the julian date Monthly time step: the month (1-12) Annual time step: 4-digit year Average annual summary lines: number of years averaged together Area drained by reach (km2). Average daily streamflow into reach during time step (m3/s). Average daily streamflow out of reach during time step (m3/s). Average daily rate of water loss from reach by evaporation during time step (m3/s). Average daily rate of water loss from reach by transmission through the streambed during time step (m3/s). Sediment transported with water into reach during time step (metric tons). Sediment transported with water out of reach during time step (metric tons). Concentration of sediment in reach during time step (mg/L). Organic nitrogen transported with water into reach during time step (kg N). Organic nitrogen transported with water out of reach during time step (kg N). Organic phosphorus transported with water into reach during time step (kg P). Organic phosphorus transported with water out of reach during time step (kg P).

AREA FLOW_IN FLOW_OUT EVAP TLOSS SED_IN SED_OUT SEDCONC ORGN_IN ORGN_OUT ORGP_IN ORGP_OUT

CHAPTER 32: SWAT OUTPUTPRIMARY FILES

327

Variable name NO3_IN NO3_OUT NH4_IN NH4_OUT NO2_IN NO2_OUT MINP_IN MINP_OUT ALGAE_IN ALGAE_OUT CBOD_IN CBOD_OUT DISOX_IN DISOX_OUT

Definition Nitrate transported with water into reach during time step (kg N). Nitrate transported with water out of reach during time step (kg N). Ammonium transported with water into reach during time step (kg N). Ammonium transported with water out of reach during time step (kg N). Nitrite transported with water into reach during time step (kg N). Nitrite transported with water out of reach during time step (kg N). Mineral phosphorus transported with water into reach during time step (kg P). Mineral phosphorus transported with water out of reach during time step (kg P). Algal biomass transported with water into reach during time step (kg). Algal biomass transported with water out of reach during time step (kg). Carbonaceous biochemical oxygen demand of material transported into reach during time step (kg O2). Carbonaceous biochemical oxygen demand of material transported out of reach during time step (kg O2). Amount of dissolved oxygen transported into reach during time step (kg O2). Amount of dissolved oxygen transported out of reach during time step (kg O2).

While more than one pesticide may be applied to the HRUs, due to the complexity of the pesticide equations only the pesticide listed in .bsn is routed through the stream network. SOLPST_IN SOLPST_OUT Soluble pesticide transported with water into reach during time step (mg active ingredient) Soluble pesticide transported with water out of reach during time step (mg active ingredient).

328

SWAT USER'S MANUAL, VERSION 2000

Variable name SORPST_IN SORPST_OUT REACTPST VOLPST SETTLPST RESUSP_PST DIFFUSEPST REACBEDPST BURYPST BED_PST BACTP_OUT BACTLP_OUT CMETAL#1 CMETAL#2 CMETAL#3

Definition Pesticide sorbed to sediment transported with water into reach during time step (mg active ingredient). Pesticide sorbed to sediment transported with water out of reach during time step (mg active ingredient). Loss of pesticide from water by reaction during time step (mg active ingredient). Loss of pesticide from water by volatilization during time step (mg active ingredient). Transfer of pesticide from water to river bed sediment by settling during time step (mg active ingredient). Transfer of pesticide from river bed sediment to water by resuspension during time step (mg active ingredient). Transfer of pesticide from water to river bed sediment by diffusion during time step (mg active ingredient). Loss of pesticide from river bed sediment by reaction during time step (mg active ingredient). Loss of pesticide from river bed sediment by burial during time step (mg active ingredient). Pesticide in river bed sediment during time step (mg active ingredient). Number of persistent bacteria transported out of reach during time step. Number of less persistent bacteria transported out of reach during time step. Conservative metal #1 transported out of reach (kg). Conservative metal #2 transported out of reach (kg). Conservative metal #3 transported out of reach (kg).

CHAPTER 32: SWAT OUTPUTPRIMARY FILES

329

The format of the main channel output file (.rch) is:

Variable name RCH GIS MON AREA FLOW_IN FLOW_OUT EVAP TLOSS SED_IN SED_OUT SEDCONC ORGN_IN ORGN_OUT ORGP_IN ORGP_OUT NO3_IN NO3_OUT NH4_IN NH4_OUT NO2_IN NO2_OUT MINP_IN MINP_OUT CHLA_IN CHLA_OUT CBOD_IN CBOD_OUT DISOX_IN DISOX_OUT SOLPST_IN SOLPST_OUT SORPST_IN SORPST_OUT REACTPST Line # All All All All All All All All All All All All All All All All All All All All All All All All All All All All All All All All All All Position space 7-10 space 12-19 space 21-25 space 26-37 space 38-49 space 50-61 space 62-73 space 74-85 space 86-97 space 98-109 space 110-121 space 122-133 space 134-145 space 146-157 space 158-169 space 170-181 space 182-193 space 194-205 space 206-217 space 218-229 space 230-241 space 242-253 space 254-265 space 266-277 space 278-289 space 290-301 space 302-313 space 314-325 space 326-337 space 338-349 space 350-361 space 362-373 space 374-385 space 386-397 Format 4-digit integer 8-digit integer 5-digit integer exponential exponential exponential exponential exponential exponential exponential exponential exponential exponential exponential exponential exponential exponential exponential exponential exponential exponential exponential exponential exponential exponential exponential exponential exponential exponential exponential exponential exponential exponential exponential F90 Format i4 i8 i5 e12.4 e12.4 e12.4 e12.4 e12.4 e12.4 e12.4 e12.4 e12.4 e12.4 e12.4 e12.4 e12.4 e12.4 e12.4 e12.4 e12.4 e12.4 e12.4 e12.4 e12.4 e12.4 e12.4 e12.4 e12.4 e12.4 e12.4 e12.4 e12.4 e12.4 e12.4

330

SWAT USER'S MANUAL, VERSION 2000 Line # All All All All All All All All All All All All Position space 398-409 space 410-421 space 422-433 space 434-445 space 446-457 space 458-469 space 470-481 space 482-493 space 494-505 space 506-517 space 518-529 space 530-541 Format exponential exponential exponential exponential exponential exponential exponential exponential exponential exponential exponential exponential F90 Format e12.4 e12.4 e12.4 e12.4 e12.4 e12.4 e12.4 e12.4 e12.4 e12.4 e12.4 e12.4

Variable name VOLPST SETTLPST RESUSP_PST DIFFUSEPST REACBEDPST BURYPST BED_PST BACTP_OUT BACTLP_OUT CMETAL#1 CMETAL#2 CMETAL#3

CHAPTER 32: SWAT OUTPUTPRIMARY FILES

331

32.6 HRU IMPOUNDMENT OUTPUT FILE (.WTR)

The HRU impoundment output file contains summary information for ponds, wetlands and depressional/impounded areas in the HRUs. The file is written in spreadsheet format. Following is a brief description of the output variables in the HRU impoundment output file. Variable name LULC HRU GIS SUB MGT Definition Four letter character code for the cover/plant on the HRU. (code from crop.dat file) Hydrologic response unit number GIS code reprinted from watershed configuration file (.fig). See explanation of subbasin command. Topographically-defined subbasin to which the HRU belongs. Management number. This is pulled from the management (.mgt) file. Used by the SWAT/GRASS interface to allow development of output maps by landuse/management type. Daily time step: the julian date Monthly time step: the month (1-12) Annual time step: year Average annual summary lines: total number of years averaged together Drainage area of the HRU (km2). Precipitation falling directly on the pond during the time step (mm H2O). The depth of water is the volume divided by the area of the HRU. Pond inflow (mm H2O). Surface runoff entering the pond during the time step. The depth of water is the volume divided by the area of the HRU. Pond sediment inflow (metric tons/ha). Sediment transported into the pond during the time step. The loading is the mass divided by the area of the HRU. Evaporation from the pond surface during the time step (mm H2O). The depth of water is the volume divided by the area of the HRU.

MON

AREA PNDPCP

PND_IN

PSED_I

PNDEVP

332

SWAT USER'S MANUAL, VERSION 2000

Variable name PNDSEP

Definition Water that seeps through the bottom of the pond and recharges the shallow aquifer during the time step (mm H2O). The depth of water is the volume divided by the area of the HRU. Pond outflow (mm H2O). Water leaving the pond and entering the reach during the time step. The depth of water is the volume divided by the area of the HRU. Pond sediment outflow (metric tons/ha). Sediment transported out of the pond and entering the reach during the time step. . The loading is the mass divided by the area of the HRU. Volume of water in pond at end of time step (m3 H2O). Concentration of organic N in pond at end of time step (mg N/L or ppm). Concentration of nitrate in pond at end of time step (mg N/L or ppm). Concentration of organic P in pond at end of time step (mg P/L or ppm). Concentration of mineral P in pond at end of time step (mg P/L or ppm). Concentration of chlorophyll-a in pond at end of time step (mg chl-a/L or ppm). Secchi-disk depth of pond at end of time step (m). Precipitation falling directly on the wetland during the time step (mm H2O). The depth of water is the volume divided by the area of the HRU. Wetland inflow (mm H2O). Surface runoff entering the wetland during the time step. The depth of water is the volume divided by the area of the HRU. Wetland sediment inflow (metric tons/ha). Sediment transported into the wetland during the time step. The loading is the mass divided by the area of the HRU. Evaporation from the wetland during the time step (mm H2O). The depth of water is the volume divided by the area of the HRU. Water that seeps through the bottom of the wetland and recharges the shallow aquifer during the time step (mm H2O). The depth of water is the volume divided by the area of the HRU.

PND_OUT

PSED_O

PNDVOL PNDORGN PNDNO3 PNDORGP PNDMINP PNDCHLA PNDSECI WETPCP

WET_IN

WSED_I

WETEVP

WETSEP

CHAPTER 32: SWAT OUTPUTPRIMARY FILES

333

Variable name WET_OUT

Definition Wetland outflow (mm H2O). Water leaving the wetland and entering the reach during the time step. The depth of water is the volume divided by the area of the HRU. Wetland sediment outflow (metric tons/ha). Sediment transported out of the wetland and entering the reach during the time step. . The loading is the mass divided by the area of the HRU. Volume of water in wetland at end of time step (m3 H2O). Concentration of organic N in wetland at end of time step (mg N/L or ppm). Concentration of nitrate in wetland at end of time step (mg N/L or ppm). Concentration of organic P in wetland at end of time step (mg P/L or ppm). Concentration of mineral P in wetland at end of time step (mg P/L or ppm). Concentration of chlorophyll-a in wetland at end of time step (mg chl-a/L or ppm). Secchi-disk depth of wetland at end of time step (m). Precipitation falling directly on the pothole during the time step (mm H2O). The depth of water is the volume divided by the area of the HRU. Pothole inflow (mm H2O). Surface runoff entering the pothole during the time step. The depth of water is the volume divided by the area of the HRU. Pothole sediment inflow (metric tons/ha). Sediment transported into the pothole during the time step. The loading is the mass divided by the area of the HRU. Evaporation from the pothole during the time step (mm H2O). The depth of water is the volume divided by the area of the HRU. Water that seeps through the bottom of the pothole and enters the underlying soil during the time step (mm H2O). The depth of water is the volume divided by the area of the HRU. Pothole outflow (mm H2O). Water leaving the pothole and entering the reach during the time step. The depth of water is the volume divided by the area of the HRU.

WSED_O

WET_VOL WETORGN WETNO3 WETORGP WETMINP WETCHLA WETSECI POTPCP

POT_IN

OSED_I

POTEVP

POTSEP

POT_OUT

334

SWAT USER'S MANUAL, VERSION 2000

Variable name OSED_O

Definition Pothole sediment outflow (metric tons/ha). Sediment transported out of the pothole and entering the reach during the time step. . The loading is the mass divided by the area of the HRU. Volume of water in pothole at end of time step (m3 H2O). Surface area of pothole at end of time step (ha). Surface runoff contribution to streamflow in the main channel from entire HRU during the time step (mm H2O). Amount of water removed by transpiration from plants during the time step (mm H2O). Amount of water removed by evaporation from the soil during the time step (mm H2O).

POTVOL POT_SA HRU_SURQ PLANT_ET SOIL_ET

The format of the HRU impoundment output file (.wtr) is:

Variable name LULC HRU GIS SUB MGT MON AREA PNDPCP PND_IN PSED_I PNDEVP PNDSEP PND_OUT PSED_O PNDVOL PNDORGN PNDNO3 PNDORGP PNDMINP PNDCHLA PNDSECI Line # All All All All All All All All All All All All All All All All All All All All All Position space 1-4 space 5-8 space 10-17 space 19-22 space 24-27 space 29-32 space 33-42 space 43-52 space 53-62 space 63-72 space 73-82 space 83-92 space 93-102 space 103-112 space 113-122 space 123-132 space 133-142 space 143-152 space 153-162 space 163-172 space 173-182 Format character 4-digit integer 8-digit integer 4-digit integer 4-digit integer 4-digit integer decimal(xxxxxx.xxx) decimal(xxxxxx.xxx) decimal(xxxxxx.xxx) decimal(xxxxxx.xxx) decimal(xxxxxx.xxx) decimal(xxxxxx.xxx) decimal(xxxxxx.xxx) decimal(xxxxxx.xxx) exponential decimal(xxxxxx.xxx) decimal(xxxxxx.xxx) decimal(xxxxxx.xxx) decimal(xxxxxx.xxx) decimal(xxxxxx.xxx) decimal(xxxxxx.xxx) F90 Format a4 i4 i8 i4 i4 i4 f10.3 f10.3 f10.3 f10.3 f10.3 f10.3 f10.3 f10.3 e10.4 f10.3 f10.3 f10.3 f10.3 f10.3 f10.3

CHAPTER 32: SWAT OUTPUTPRIMARY FILES Variable name WETPCP WET_IN WSED_I WETEVP WETSEP WET_OUT WSED_O WET_VOL WETORGN WETNO3 WETORGP WETMINP WETCHLA WETSECI POTPCP POT_IN OSED_I POTEVP POTSEP POT_OUT OSED_O POTVOL POT_SA HRU_SURQ PLANT_ET SOIL_ET Line # All All All All All All All All All All All All All All All All All All All All All All All All All All Position space 183-192 space 193-202 space 203-212 space 213-222 space 223-232 space 233-242 space 243-252 space 253-262 space 263-272 space 273-282 space 283-292 space 293-302 space 303-312 space 313-322 space 323-332 space 333-342 space 343-352 space 353-362 space 363-372 space 373-382 space 383-392 space 393-402 space 403-412 space 413-422 space 423-432 space 433-442 Format decimal(xxxxxx.xxx) decimal(xxxxxx.xxx) decimal(xxxxxx.xxx) decimal(xxxxxx.xxx) decimal(xxxxxx.xxx) decimal(xxxxxx.xxx) decimal(xxxxxx.xxx) exponential decimal(xxxxxx.xxx) decimal(xxxxxx.xxx) decimal(xxxxxx.xxx) decimal(xxxxxx.xxx) decimal(xxxxxx.xxx) decimal(xxxxxx.xxx) decimal(xxxxxx.xxx) decimal(xxxxxx.xxx) decimal(xxxxxx.xxx) decimal(xxxxxx.xxx) decimal(xxxxxx.xxx) decimal(xxxxxx.xxx) decimal(xxxxxx.xxx) exponential decimal(xxxxxx.xxx) decimal(xxxxxx.xxx) decimal(xxxxxx.xxx) decimal(xxxxxx.xxx) F90 Format f10.3 f10.3 f10.3 f10.3 f10.3 f10.3 f10.3 e10.4 f10.3 f10.3 f10.3 f10.3 f10.3 f10.3 f10.3 f10.3 f10.3 f10.3 f10.3 f10.3 f10.3 e10.4 f10.3 f10.3 f10.3 f10.3

335

336

SWAT USER'S MANUAL, VERSION 2000

32.7 RESERVOIR OUTPUT FILE (.RSV)

The reservoir output file contains summary information for reservoirs in the watershed. The file is written in spreadsheet format. Following is a brief description of the output variables in the reservoir output file. Variable name RES MON Definition Reservoir number (assigned in .fig file) Daily time step: the julian date Monthly time step: the month (1-12) Annual time step: four-digit year Volume of water in reservoir at end of time step (m3 H2O). Average flow into reservoir during time step (m3/s H2O). Average flow out of reservoir during time step (m3/s H2O). Precipitation falling directly on the reservoir during the time step (m3 H2O). Evaporation from the reservoir during the time step (m3 H2O). Water that seeps through the bottom of the reservoir and enters the shallow aquifer during the time step (m3 H2O). Reservoir sediment inflow (metric tons). Sediment transported into the reservoir during the time step. Reservoir sediment outflow (metric tons). Sediment transported out of the reservoir during the time step. Amount of organic nitrogen transported into reservoir during the time step (kg N). Amount of organic nitrogen transported out of reservoir during the time step (kg N). Amount of organic phosphorus transported into reservoir during the time step (kg P). Amount of organic phosphorus transported out of reservoir during the time step (kg P). Amount of nitrate transported into reservoir during the time step (kg N).

VOLUME FLOW_IN FLOW_OUT PRECIP EVAP SEEPAGE SED_IN SED_OUT ORGN_IN ORGN_OUT ORGP_IN ORGP_OUT NO3_IN

CHAPTER 32: SWAT OUTPUTPRIMARY FILES

337

Variable name NO3_OUT NO2_IN NO2_OUT NH3_IN NH3_OUT MINP_IN MINP_OUT CHLA_IN CHLA_OUT SECCHIDEPTH PEST_IN REACTPST VOLPST SETTLPST RESUSP_PST DIFFUSEPST REACBEDPST BURYPST

Definition Amount of nitrate transported out of reservoir during the time step (kg N). Amount of nitrite transported into reservoir during the time step (kg N). Amount of nitrite transported out of reservoir during the time step (kg N). Amount of ammonia transported into reservoir during the time step (kg N). Amount of ammonia transported out of reservoir during the time step (kg N). Amount of mineral phosphorus transported into reservoir during the time step (kg P). Amount of mineral phosphorus transported out of reservoir during the time step (kg P). Amount of chlorophyll a transported into reservoir during the time step (kg chla). Amount of chlorophyll a transported out of reservoir during the time step (kg chla). Secchi-disk depth of reservoir at end of time step (m). Amount of pesticide transported into reservoir during the time step (mg pesticide active ingredient). Loss of pesticide from water by reaction during time step (mg active ingredient). Loss of pesticide from water by volatilization during time step (mg active ingredient). Transfer of pesticide from water to reservoir bed sediment by settling during time step (mg active ingredient). Transfer of pesticide from reservoir bed sediment to water by resuspension during time step (mg active ingredient). Transfer of pesticide from water to reservoir bed sediment by diffusion during time step (mg active ingredient). Loss of pesticide from reservoir bed sediment by reaction during time step (mg active ingredient). Loss of pesticide from reservoir sediment by burial during time step (mg active ingredient).

338

SWAT USER'S MANUAL, VERSION 2000

Variable name PEST_OUT PSTCNCW PSTCNCB

Definition Amount of pesticide transported out of reservoir during the time step (mg pesticide active ingredient). Average concentration of pesticide in reservoir water during time step (mg active ingredient/m3 H2O or ppb). Average concentration of pesticide in reservoir bed sediment during time step (mg active ingredient/m3 H2O or ppb).

The format of the reservoir output file (.rsv) is:

Variable name RES MON VOLUME FLOW_IN FLOW_OUT PRECIP EVAP SEEPAGE SED_IN SED_OUT ORGN_IN ORGN_OUT ORGP_IN ORGP_OUT NO3_IN NO3_OUT NO2_IN NO2_OUT NH3_IN NH3_OUT MINP_IN MINP_OUT CHLA_IN CHLA_OUT SECCHIDEPTH PEST_IN Line # All All All All All All All All All All All All All All All All All All All All All All All All All All Position space 7-14 space 16-19 space 20-31 space 32-43 space 44-55 space 56-67 space 68-79 space 80-91 space 92-103 space 104-115 space 116-127 space 128-139 space 140-151 space 152-163 space 164-175 space 176-187 space 188-199 space 200-211 space 212-223 space 224-235 space 236-247 space 248-259 space 260-271 space 272-283 space 284-295 space 296-307 Format integer integer exponential exponential exponential exponential exponential exponential exponential exponential exponential exponential exponential exponential exponential exponential exponential exponential exponential exponential exponential exponential exponential exponential exponential exponential F90 Format i8 i4 e12.4 e12.4 e12.4 e12.4 e12.4 e12.4 e12.4 e12.4 e12.4 e12.4 e12.4 e12.4 e12.4 e12.4 e12.4 e12.4 e12.4 e12.4 e12.4 e12.4 e12.4 e12.4 e12.4 e12.4

CHAPTER 32: SWAT OUTPUTPRIMARY FILES Variable name REACTPST VOLPST SETTLPST RESUSP_PST DIFFUSEPST REACBEDPST BURYPST PEST_OUT PSTCNCW PSTCNCB Line # All All All All All All All All All All Position space 308-319 space 320-331 space 332-343 space 344-355 space 356-367 space 368-379 space 380-391 space 392-403 space 404-415 space 416-427 Format exponential exponential exponential exponential exponential exponential exponential exponential exponential exponential F90 Format e12.4 e12.4 e12.4 e12.4 e12.4 e12.4 e12.4 e12.4 e12.4 e12.4

339

340

SWAT USER'S MANUAL, VERSION 2000

CHAPTER 33

SWAT: CALIBRATION

Calibration of a model run can be divided into several steps: water balance and stream flow sediment nutrients

WATER BALANCE AND STREAM FLOW

To calibrate the water balance and stream flow you need to have some understanding of the actual conditions occurring in the watershed. Ideally, you have data from a stream gage located within or at the outlet of your watershed.
The U.S. Geological Survey maintains a website (http://water.usgs.gov/) with daily records for all stream gages in the U.S. available for downloading.

Calibration for water balance and stream flow is first done for average annual conditions. Once the run is calibrated for average annual conditions, the user can shift to monthly or daily records to fine-tune the calibration. The average annual observed and simulated results should be summarized in a manner similar to the following table: Total Water Yield 200 mm 300 mm Baseflow 80 mm 20 mm Surface Flow 120 mm 280 mm

Actual SWAT

(When calibrating, we usually summarize data as depth of water in millimeters over the drainage area. Feel free to use whatever units you prefer.)
If you are calibrating at the watershed outlet, the SWAT values for the table are provided in the .std file. These values are listed in the table titled "Ave Annual Basin Values" located near the end of the file. If you are calibrating a gage located within the watershed, the total water yield can be calculated from the FLOW_OUT variable in the reach (.rch) file. The values for Baseflow and Surface Flow have to be estimated from the HRU output (.sbs) file or the subbasin output file (.bsb). To estimate the contributions by baseflow and streamflow, the average annual values for GWQ, SURQ and WYLD need to be averaged so that an areally weighted value for the drainage area of interest is obtained. The surface flow and baseflow then need to be converted to fractions by dividing by the total water yield (WYLD). These fractions are then multiplied by the total water yield obtained from the reach output file. The values for GWQ and SURQ cannot be used directly because in-stream precipitation, evaporation, transmission losses, etc. will alter the net water yield from that predicted by the WYLD variable in the HRU or Subbasin Output files.

There are a number of methods available for partitioning observed stream flow into fractions contributed by baseflow and surface runoff. If daily steam flow is available, a baseflow filter program can be run which performs this analysis.

I. BASIC WATER BALANCE & TOTAL FLOW CALIBRATION CALIBRATE SURFACE RUNOFF: Step 1: Adjust the curve number (CN2 in .mgt) until surface runoff is acceptable. Appendix A contains tables of curve number values for a wide variety of land covers. Appendix B contains tables summarizing ranges for the general categories of land cover and lists the land cover category for all plants in the SWAT Land Cover/Plant database. If surface runoff values are still not reasonable after adjusting curve numbers, adjust: -soil available water capacity (0.04) (SOL_AWC in .sol) and/or -soil evaporation compensation factor (ESCO in .bsn or .hru). CALIBRATE SUBSURFACE FLOW: Step 2: Once surface runoff is calibrated, compare measured and simulated values of baseflow. If simulated baseflow is too high: -increase the groundwater "revap" coefficient (GW_REVAP in .gw)the maximum value that GW_REVAP should be set at is 0.20. -decrease the threshold depth of water in the shallow aquifer for "revap" to occur (REVAPMN in .gw)the minimum value that REVAPMN should be set at is 0.0. -increase the threshold depth of water in the shallow aquifer required for base flow to occur (GWQMN in .gw)the maximum value that GWQMN should be set at is left to user discretion. If simulated baseflow is too low, check the movement of water into the aquifer. If groundwater recharge (GWQ in .sbs or .bsb) is greater than or equal to the desired baseflow: -decrease the groundwater "revap" coefficient (GW_REVAP in .gw)the minimum value that GW_REVAP should be set at is 0.02. -increase the threshold depth of water in the shallow aquifer for "revap" to occur (REVAPMN in .gw). -decrease the threshold depth of water in the shallow aquifer required for base flow to occur (GWQMN in .gw)the minimum value that GWQMN should be set at is 0.0. Step 3: Repeat steps 1 and 2 until values are acceptable. It may take several reiterations to get the surface runoff and baseflow correct. II. TEMPORAL FLOW CALIBRATION Once average annual and annual surface runoff and baseflow are realistic, the temporal flow should look reasonable as well. A few problems that may still be present include:

Flow

Observed Simulated

Time (days)

1) Peaks are reasonable, but the recessions "bottom out": Check the transmission losses/values for channel hydraulic conductivity (CH_K in .rte). The value for channel hydraulic conductivity is an effective hydraulic conductivity for movement of water out of the stream bed.
For perennial streams receiving groundwater contribution to flow, the groundwater enters the stream through the sides and bottom of the stream bed, making the effective hydraulic conductivity of the channel beds to water losses equal to zero. The only time the channel hydraulic conductivity would be greater than zero is for ephemeral and transient streams that do not receive continuous groundwater contributions to streamflow.

A second variable that will affect the shape of the hydrograph is the baseflow alpha factor (ALPHA_BF in .gw).

Flow

Observed Simulated

Time (days)

2) In snow melt months, the peaks are too high and recessions are too low: Check the values for maximum and minimum melt rates for snow (SMFMX and SMFMN in .bsn). These values may need to be lowered. Another variable that will impact snow melt is the temperature lapse rate (TLAPS in .sub). These values may need to be increased. Finally, the baseflow alpha factor may need to be modified (ALPHA_BF in .gw).

III. SPATIAL FLOW CALIBRATION If you are calibrating a watershed with multiple stream gages, calibrate streamflow for the gage furthest upstream. Once that gage is calibrated, move downstream to the next gage and calibrate for that area. It is important that, as you calibrate downstream gages, you do not change parameters within the files associated with the drainage area of the upstream gages already calibrated.

SEDIMENT
There are two sources of sediment in the SWAT simulation: loadings from HRUs/subbasins and channel degradation/deposition. Once the ratio of surface runoff to baseflow contribution to streamflow is being simulated correctly, the sediment contribution (loadings from HRUs/subbasins) should be close to measured values. In most situations, the user will probably have little information about channel degradation/deposition. For those unable to go out and assess the channel, we suggest that you adjust the loadings from the subbasins until they look reasonable and then assume that the remaining difference between actual and observed is due to channel degradation/deposition. The average annual observed and simulated results should be summarized in a manner similar to the following table. A more detailed table which contains the loadings by land use on a given soil type may be used also. Sediment 187 metric tons/yr 354 metric tons/yr 1459 metric tons/yr 2,000 metric tons/yr 2,873 metric tons/yr 2,321 metric tons/yr
Sediment loadings from the HRUs/subbasins can be calculated by summing values for SYLD in either the .sbs or .bsb file. The amount of sediment leaving the reach can be obtained from values reported for SED_OUT in the .rch file.

Loadings from mixed forest Loadings from bermuda pasture Loadings from range Loading from HRUs/subbasins Amount of sediment leaving reach Actual

0.14 metric tons/ha/yr 0.23 metric tons/ha/yr 0.35 metric tons/ha/yr 0.28 metric tons/ha/yr

CHECK RESERVOIR/POND SIMULATION: Reservoirs and ponds have a big impact on sediment loadings. If the amount of sediment being simulated in the watershed is off, first verify that you are accounting for all the ponds and reservoirs in the watershed and that they are being simulated properly. CALIBRATE SUBBASIN LOADINGS: While surface runoff is the primary factor controlling sediment loadings to the stream, there are a few other variables that affect sediment movement into the stream. 1) Tillage has a great impact on sediment transport. With tillage, plant residue is removed from the surface causing erosion to increase. Verify that the tillage practices are being accurately simulated. 2) USLE equation support practices (P) factor (USLE_P in the .mgt file): Verify that you have accurately accounted for contouring and terracing in agricultural areas. In general, agricultural land with a slope greater that 5% will be terraced.

3) USLE equation slope length factor (SLSUBBSN in .hru file): There is usually a large amount of uncertainty in slope length measurements. The slope length will also be affected by support practices used in the HRU. 4) Slope in the HRUs (SLOPE in .hru file): Verify that the slopes given for the subbasin are correct. 5) USLE equation cropping practices (C) factor (USLE_C in crop.dat): In some cases, the minimum C value reported for the plant cover may not be accurate for your area. CALIBRATE CHANNEL DEGRADATION/DEPOSITION: Channel degradation will be significant during extreme storm events and in unstable subbasins. Unstable subbasins are those undergoing a significant change in land use patterns such as urbanization. Variables that affect channel degradation/deposition include: 1) The linear and exponential parameters used in the equation to calculate sediment reentrained in channel sediment routing (SPCON and SPEXP in .bsn file). These variables affect sediment routing in the entire watershed. 2) The channel erodibility factor (CH_EROD in .rte) 3) The channel cover factor (CH_COV in .rte)

NUTRIENTS
The nutrients of concern in SWAT are nitrate, soluble phosphorus, organic nitrogen and organic phosphorus. When calibrating for a nutrient, keep in mind that changes made will have an effect all the nutrient levels. Nutrient calibration can be divided into two steps: calibration of nutrient loadings and calibration of in-stream water quality processes.

CALIBRATE NUTRIENT LOADINGS (ALL NUTRIENTS): 1) Check that the initial concentrations of the nutrients in the soil are correct. These are set in the soil chemical input file (.chm): nitrate (SOL_NO3 in .chm) soluble P (SOL_MINP in .chm) organic N (SOL_ORGN in .chm) organic P (SOL_ORGP in .chm) 2) Verify that fertilizer applications are correct. Check amounts and the soil layer that the fertilizer is applied to. The fertilizer may be applied to the top 10mm of soil or incorporated in the first soil layer. The variable FRT_LY1 identifies the fraction of fertilizer applied to the top 10mm of soil. (If this variable is left at zero, the model will set FRT_LY1 = 0.20). 3) Verify that tillage operations are correct. Tillage redistributes nutrients in the soil and will alter the amount available for interaction or transport by surface runoff. 4) Alter the biological mixing efficiency (BIOMIX in .mgt file). Biological mixing acts the same as a tillage operation in that it incorporates residue and nutrients into the soil. This variable controls mixing due to biological activity in the entire watershed. CALIBRATE NUTRIENT LOADINGS (NITRATE): In addition to the variables mentioned above, 1) Modify the nitrogen percolation coefficient (NPERCO in .bsn file) CALIBRATE NUTRIENT LOADINGS (SOLUBLE P): In addition to the variables mentioned in the section for all nutrients, 1) Modify the phosphorus percolation coefficient (PPERCO in .bsn file) 2) Modify the phosphorus soil partitioning coefficient (PHOSKD in .bsn file). CALIBRATE NUTRIENT LOADINGS (ORGANIC N & P): Organics are transported to the stream attached to sediment, so the movement of sediment will greatly impact the movement of organics.

CALIBRATE IN-STREAM NUTRIENT PROCESSES:

SWAT includes in-stream nutrient cycling processes as described in the QUAL2E documentation. Variables in the watershed water quality (.wwq) and stream water quality (.swq) files control these processes.

SWAT Calibration Techniques

[email protected]

Calibration, Validation & Verification

F CALIBRATION: model testing with known input and output used to adjust or estimate factors F VALIDATION: comparison of model results with an independent data set (without further adjustment). F VERIFICATION: examination of the numerical technique in the computer code to ascertain that it truly represents the conceptual model and that there are no inherent numerical problems

[email protected]

BRC/TIAER/UT

Calibration/Validation Periods
distinct time period similar range of conditions adequate time period to simulate conditions

Flow

Time Setup Calibration

[email protected]

Validation
BRC/TIAER/UT

Model Configuration
F

Land use categories

land use types in watershed, existing and future land uses, management techniques employed, management questions

Subwatersheds
location, physical characteristics/soils, gaging station locations, topographic features, management questions.

Reaches
topographic features, stream morphology, cross-section data available Calibration Issues:
individual land use parameter determination location of gaging station data location of water quality monitoring information available information on stream systems
[email protected] BRC/TIAER/UT

Model Configuration
Calibration Points Example

LEGEND

[email protected]

BRC/TIAER/UT

Calibration/Validation Procedures
F F F

Hydrology - first and foremost Sediment - next Water quality - last (nitrogen, phosphorus, pesticides, DO, bacteria) Check list for model testing
4 water balance - is it all accounted for? 4 time series 4 annual total - stream flow & base flow 4 monthly/seasonal total 4 frequency duration curve 4 sediment and nutrients balance
[email protected] BRC/TIAER/UT

Calibration Time Step

F

Calibration sequence
annual water balance seasonal variability storm variability
time series plot u frequency duration curve
u

baseflow overall time series

[email protected]

BRC/TIAER/UT

Calibration/Validation Statistics
Mean and standard deviation of the simulated and measured data Slope, intercept and regression coefficient/coefficient of determination Nash-Suttcliffe Efficiency

[email protected]

BRC/TIAER/UT

Calibration/Validation Common Problems

F F

too little data - too short a monitoring period small range of conditions
only small storms only storms during the spring...

prediction of future conditions which are outside the model conditions calibration/validation does not adequately test separate pieces of model
accuracy of each land use category prediction

calibration adjustments destroy physical representation of system by model adjustment of the wrong parameters
[email protected] BRC/TIAER/UT

Calibration/Validation Suggested References

F

Neitsch, S. L., J. G. Arnold, J. R. Kiniry and J. R. Willams. 2001. Soil and Water Assessment Tool Manual, USDA-ARS Publications. pp: 341-354. http://www.brc.tamus .edu/swat/manual. Santhi, C., J. G. Arnold, J. R. Williams, W. A. Dugas, R. Srinivasan and L. M. Hauck. 2001. Validation of the SWAT Model on a Large River Basin with Point and Nonpoint Sources. J. American Water Resources Association 37(5): 1169-1188. Srinivasan, R., T. S. Ramanarayanan, J. G. Arnold and S. T. Bednarz. 1997. Large area hydrologic modeling and assessment: Part II - Model application. J. American Water Resources Association 34(1): 91-102. Arnold, J.G., R. S. Muttiah, R. Srinivasan and P. M. Allen. 2000. Regional estimation of baseflow and groundwater recharge in the upper Mississippi basin. J. Hydrology 227(2000): 21-40.

[email protected]

BRC/TIAER/UT

Hydrology Calibration Summary

F

Key considerations
Water balance
overall amount u distribution among hydrologic components
u

Storm sequence
u

time lag or shifts

time of concentration, travel time

shape of hydrograph
peak recession consider antecedent conditions
[email protected] BRC/TIAER/UT

Example Calibration Plot

[email protected]

BRC/TIAER/UT

Example Calibration Plot

Calibration of flow at Hico, Bosque River Watershed, TX
Observed 350 300
Flow Volume (mm/year)

Simulated

250 200 150 100 50 0

1962 1964 1966 1968 1970 1972 1974 1976 1978 1980 1982 1984 1986 1988 1990 1992 1994 1996

Time

[email protected]

BRC/TIAER/UT

Example Calibration Plot

[email protected]

BRC/TIAER/UT

Hydrologic Calibration Scenario 1

Simulated Observed Flow (cfs)

Time (hours)
[email protected] BRC/TIAER/UT

Hydrologic Calibration
Model failed to simulate some peak flows
F F

Rainfall station is not representative Localized storm -no response Malfunctioning gages (precipitation or flow)

Simulated Observed

Flow (cfs)

Time (hours)

Solutions
F F

Use precipitation data from representative meteorological stations Carefully review precipitation and flow data for the particular duration
[email protected] BRC/TIAER/UT

Hydrologic Calibration Scenario 2

Simulated Observed Flow (cfs)

Time (hours)
[email protected] BRC/TIAER/UT

Hydrologic Calibration
Model consistently over predicts the flow
F

High Surface flow

Flow (cfs)

Simulated Observed

Solutions
F F F

Time (hours)

Decrease curve number for different land uses (CN in .mgt) Soil available water (SOL_AWC in .sol) Soil evaporation compensation factor (ESCO in *.sub)

[email protected]

BRC/TIAER/UT

Hydrologic Calibration
Model consistently over predicts the flow
F F
Flow (cfs)

High base flow Too little evapotranspiration

Simulated Observed

Solutions
F

Time (hours)

F F

Increase deep percolation loss (Adjust threshold depth of water in shallow aquifer required for the base flow to occur) (GWQMN in .gw) Increase groundwater revap coefficient (GW_REVAP in .gw) Decrease theshold depth of water in shallow aquifer for revap to occur (REVAPMN in .gw) [email protected] BRC/TIAER/UT

[email protected]

BRC/TIAER/UT

Hydrologic Calibration Scenario 3

Simulated Observed Flow (cfs)

Time (hours)
[email protected] BRC/TIAER/UT

Hydrologic Calibration
Simulated flow follows the observed pattern but lags the actual flow consistently
F

Time of concentration is too long Less than actual slope for overland flow Over estimated surface roughness Solutions
F F F

Simulated Observed

Flow (cfs)

Time (hours)

Adjust slope for over land flow (SLOPE) Adjust Mannings roughness coefficient (OV_N) Adjust the value of overland flow length (SLSUBBSN), if necessary
[email protected] BRC/TIAER/UT

Hydrologic Calibration Scenario 4

Simulated Observed Flow (cfs)

Time (hours)
[email protected] BRC/TIAER/UT

Hydrologic Calibration
Simulated flow over predicts peak flows but under predicts all other times
F F

Flow (cfs)

Too little base flow Too high surface runoff

Simulated Observed

Time (hours)

Solutions
F F F

Adjust infiltration Adjust interflow Adjust base flow recession parameter

[email protected]

BRC/TIAER/UT

Sediment Calibration Summary

F

Key considerations
Sources of sediment loadings
Loadings from HRUs/Subbasins u Channel degradation/deposition
u

Sediment loading distribution

overall amount u Seasonal loading
u

distribution by storm sequence rising and falling limb of hydrograph peak concentration
[email protected] BRC/TIAER/UT

Example Calibration Plot

[email protected]

BRC/TIAER/UT

Sediment Calibration Scenario 1

Sediment
0.60 0.50 Observed Simulated

Sediment tons/ha

0.40 0.30 0.20 0.10 0.00 1 2 3 4 5 6 7 8

Time in Months

[email protected]

BRC/TIAER/UT

Sediment Calibration
Model consistently under predicts the sediment
Sediment
0.60 0.50 Observed Simulated

Sediment tons/ha

Low sediment yield

0.40 0.30 0.20

0.10

Solutions
F

0.00 1 2 3 4 5 6 7 8
Time in Months

Calibrate HRU/Subbasin Loadings

Adjust USLE crop management factor (P) (USLE_P in .sub) Adjust USLE slope length factor (LS) (SLSUBBSN in .sub) Adjust the slope of HRUs (SLOPE in .sub) Adjust crop practice factor (C) for land use (USLE_C in crop.dat) Verify tillage operations in *.mgt files and adjust crop residue coefficient ( RSDCO) and bio-mixing efficiency (BIOMIX) in .bsn

Calibrate Channel degradation/deposition

Linear and exponential parameters used for channel sediment routing (SPCON and SPEXP in .bsn) Channel erodibility facor (CH_EROD in .rte) Channel cover factor (CH_COV in .rte) [email protected] BRC/TIAER/UT

Sediment Calibration Scenario 2

Sediment
0.60 0.50 Observed Simulated

Sediment tons/ha

0.40 0.30 0.20 0.10 0.00 1 2 3 4 5 6 7 8

Time in Months

[email protected]

BRC/TIAER/UT

Sediment Calibration
Model consistently over predicts the sediment
Sediment
0.60 0.50

Sediment tons/ha

High sediment yield

Observed Simulated

0.40 0.30 0.20 0.10

Solutions
F

0.00 1 2 3 4 5 6 7 8
Time in Months

Calibrate HRU/Subbasin Loadings

Adjust USLE crop management factor (P) (USLE_P in .sub) Adjust USLE slope length factor (LS) (SLSUBBSN in .sub) Adjust the slope of HRUs (SLOPE in .sub) Adjust crop practice factor (C) for land use (USLE_C in crop.dat) Verify tillage operations in *.mgt files and adjust crop residue coefficient ( RSDCO) and bio-mixing efficiency (BIOMIX) in .bsn

Calibrate Channel degradation/deposition

Linear and exponential parameters used for channel sediment routing (SPCON and SPEXP in .bsn) Channel erodibility facor (CH_EROD in .rte) Channel cover factor (CH_COV in .rte) [email protected] BRC/TIAER/UT

Nutrients Calibration Summary

F

Key considerations
Sources of nutrients loadings
Loadings from HRUs/Subbasins u In-stream processes
u

Nutrient loading distribution

overall amount u Seasonal loading
u

distribution by storm sequence rising and falling limb of hydrograph peak concentration
[email protected] BRC/TIAER/UT

Example Calibration Plot

Organic N
2.00 Org N kg/ha 1.50 1.00 0.50 0.00 1 5 9 13 17 21 25 29 33 37 41 45 49 53 53 Months(93-97) 57 57

Obs Org N kg/ha

Sim org N kg/ha

Mineral N
0.60

Min N kg/ha

0.40 0.20 0.00

13

17

21

25

29

33

37

41

45

Months(93-97)

Obs min N kg/ha

Sim min N kg/ha

Monthly calibration of nitrogen at Hico, Bosque Watershed, TX

[email protected] BRC/TIAER/UT

49

Mineral Nitrogen Calibration Scenario 1

Mineral Nitrogen
0.60 0.50 Observed Simulated

Mineral N kg/ha

0.40 0.30 0.20 0.10 0.00 1 2 3 4 5 6 7 8

Time in Months

[email protected]

BRC/TIAER/UT

Mineral Nitrogen Calibration

Model consistently under predicts the mineral nitrogen
Mineral Nitrogen
0.60 0.50
Mineral N kg/ha

Low mineral nitrogen loading

Calibrate mineral nitrogen loadings

Observed Simulated

0.40

0.30 0.20 0.10

Solutions
F

0.00 1 2 3 4 5 6 7 8
Time in Months

Adjust initial concentration of the nutrient in soils (SOL_NO3 in .sol) Verify fertilizer application rates and adjust fertilizer application fraction to surface layer as 0.20 (FRT_LY1 in .mgt) Verify tillage operations in *.mgt files and adjust crop residue coefficient ( RSDCO) and bio-mixing efficiency (BIOMIX) in .bsn Adjust nitrogen percolation coefficient (NPERCO in .bsn)
F

Calibrate in-stream mineral nitrogen processes

Adjust fraction of algal biomass that is as nitrogen for water quality (AI1 in.wwq)
[email protected] BRC/TIAER/UT

Mineral Nitrogen Calibration Scenario 2

Mineral Nitrogen
0.60 0.50
Mineral N kg/ha

Observed Simulated

0.40 0.30 0.20 0.10 0.00 1 2 3 4 5 6 7 8

Time in Months

[email protected]

BRC/TIAER/UT

Mineral Nitrogen Calibration

Model consistently over predicts the mineral nitrogen
0.60 0.50

Mineral Nitrogen

Observed Simulated

Mineral N kg/ha

High mineral nitrogen loading

Calibrate mineral nitrogen loadings

0.40

0.30 0.20 0.10

Solutions
F

0.00 1 2 3 4 5 6 7 8
Time in Months

Adjust initial concentration of the nutrient in soils (SOL_NO3 in .sol) Verify fertilizer application rates and adjust fertilizer application fraction to surface layer as 0.20 (FRT_LY1 in .mgt) Verify tillage operations in *.mgt files and adjust crop residue coefficient ( RSDCO) and bio-mixing efficiency (BIOMIX) in .bsn Adjust nitrogen percolation coefficient (NPERCO in .bsn)
F

Calibrate in-stream mineral nitrogen processes

Adjust fraction of algal biomass that is as nitrogen for water quality (AI1 in.wwq)
[email protected] BRC/TIAER/UT

Organic Nitrogen Calibration Scenario 1

Organic Nitrogen
0.60 0.50
Organic N kg/ha

Observed Simulated

0.40 0.30 0.20 0.10 0.00 1 2 3 4 5 6 7 8

Time in Months

[email protected]

BRC/TIAER/UT

Organic Nitrogen Calibration

Model consistently under predicts the organic nitrogen
F
Organic N kg/ha

Organic Nitrogen

Low Organic nitrogen loading

0.60 0.50 0.40 0.30 0.20 0.10 Observed Simulated

Solutions
F

0.00 1 2 3 4 5 6 7 8
Time in Months

Calibrate organic nitrogen loadings

Adjust initial concentration of the nutrient in soils (SOL_ORGN in .sol) Verify fertilizer application rates and adjust fertilizer application fraction to surface layer as 0.20 (FRT_LY1 in .mgt)

Calibrate in-stream organic nitrogen processes

Adjust fraction of algal biomass that is as nitrogen for water quality (AI1 in.wwq)

[email protected]

BRC/TIAER/UT

Organic Nitrogen Calibration Scenario 2

Organic Nitrogen
0.60 0.50 Observed Simulated

Organic N kg/ha

0.40 0.30 0.20 0.10 0.00 1 2 3 4 5 6 7 8

Time in Months

[email protected]

BRC/TIAER/UT

Organic Nitrogen Calibration

Model consistently over predicts the organic nitrogen
0.60 0.50
Organic N kg/ha

Organic Nitrogen

High Organic nitrogen loading

Observed Simulated

0.40 0.30 0.20 0.10 0.00 1 2 3 4 5 6 7 8

Time in Months

Solutions
F

Calibrate organic nitrogen loadings

Adjust initial concentration of the nutrient in soils (SOL_ORGN in .sol) Verify fertilizer application rates and adjust fertilizer application fraction to surface layer as 0.20 (FRT_LY1 in .mgt)

Calibrate in-stream organic nitrogen processes

Adjust fraction of algal biomass that is as nitrogen for water quality (AI1 in.wwq)

[email protected]

BRC/TIAER/UT

Soluble Phosphorus Calibration Scenario 1

Soluble Phosphorus
0.60 0.50 Observed Simulated

Soluble P kg/ha

0.40 0.30 0.20 0.10 0.00 1 2 3 4 5 6 7 8

Time in Months

[email protected]

BRC/TIAER/UT

Soluble Phosphorus Calibration

Model consistently under predicts the soluble phosphorus
0.60 0.50
Soluble P kg/ha

Soluble Phosphorus

Low soluble phosphorus loading

Calibrate soluble phosphorus loadings

Observed Simulated

0.40 0.30 0.20 0.10

Solutions
F

0.00 1 2 3 4 5 6 7 8
Time in Months

Adjust initial concentration of the nutrient in soils (SOL_MINP in .sol) Verify fertilizer application rates and adjust fertilizer application fraction to surface layer as 0.20 (FRT_LY1 in .mgt) Verify tillage operations in *.mgt files and adjust crop residue coefficient ( RSDCO) and bio-mixing efficiency (BIOMIX) in .bsn Adjust phosphorus percolation coefficient (PPERCO in .bsn) Adjust phosphorus soil partitioning coefficient (PHOSKD in .bsn)
F

Calibrate in-stream soluble phosphorus processes

Adjust fraction of algal biomass that is as phosphorus for water quality (AI2 in.wwq)
[email protected] BRC/TIAER/UT

Soluble Phosphorus Calibration Scenario 2

Soluble Phosphorus
0.60 0.50 0.40 0.30 0.20 0.10 0.00 1 2 3 4 5 6 7 8
Time in Months

Observed Simulated

Sol P kg/ha

[email protected]

BRC/TIAER/UT

Soluble Phosphorus Calibration

Model consistently over predicts the soluble phosphorus
0.60 0.50 0.40

Soluble Phosphorus

Sol P kg/ha

High soluble phosphorus loading

Calibrate soluble phosphorus loadings

Observed Simulated

0.30 0.20 0.10

Solutions
F

0.00 1 2 3 4 5 6 7 8
Time in Months

Adjust initial concentration of the nutrient in soils (SOL_MINP in .sol) Verify fertilizer application rates and adjust fertilizer application fraction to surface layer as 0.20 (FRT_LY1 in .mgt) Verify tillage operations in *.mgt files and adjust crop residue coefficient ( RSDCO) and bio-mixing efficiency (BIOMIX) in .bsn Adjust phosphorus percolation coefficient (PPERCO in .bsn) Adjust phosphorus soil partitioning coefficient (PHOSKD in .bsn)
F

Calibrate in-stream soluble phosphorus processes

Adjust fraction of algal biomass that is as phosphorus for water quality (AI2 in.wwq)
[email protected] BRC/TIAER/UT

Organic Phosphorus Calibration Scenario 1

Organic Phosphorus
0.60 0.50 Observed Simulated

Organic P kg/ha

0.40 0.30 0.20 0.10 0.00 1 2 3 4 5 6 7 8

Time in Months

[email protected]

BRC/TIAER/UT

Organic Phosphorus Calibration

Model consistently under predicts the organic phosphorus
0.60 0.50
Organic P kg/ha

Organic Phosphorus

Low organic phosphorus loading

Observed Simulated

0.40 0.30 0.20 0.10

Solutions
F

0.00 1 2 3 4 5 6 7 8
Time in Months

Calibrate organic phosphorus loadings

Adjust initial concentration of the nutrient in soils (SOL_ORGP in .sol) Verify fertilizer application rates and adjust fertilizer application fraction to surface layer as 0.20 (FRT_LY1 in .mgt)

Calibrate in-stream organic phosphorus processes

Adjust fraction of algal biomass that is as phosphorus for water quality (AI2 in.wwq)

[email protected]

BRC/TIAER/UT

Organic Phosphorus Calibration Scenario 2

Organic Phosphorus
0.60 0.50 Observed Simulated

Organic P kg/ha

0.40 0.30 0.20 0.10 0.00 1 2 3 4 5 6 7 8

Time in Months

[email protected]

BRC/TIAER/UT

Organic Phosphorus Calibration

Model consistently over predicts the organic phosphorus
0.60
Organic P kg/ha

Organic Phosphorus

High organic phosphorus loading

0.50 0.40 0.30 0.20 0.10 0.00

Observed Simulated

Solutions
F

Time in Months

Calibrate organic phosphorus loadings

Adjust initial concentration of the nutrient in soils (SOL_ORGP in .sol) Verify fertilizer application rates and adjust fertilizer application fraction to surface layer as 0.20 (FRT_LY1 in .mgt)

Calibrate in-stream organic phosphorus processes

Adjust fraction of algal biomass that is as phosphorus for water quality (AI2 in.wwq)

[email protected]

BRC/TIAER/UT

Tables of Runoff Curve Number Values

Table 1: Runoff curve numbers for cultivated agricultural lands
Cover Hydrologic Soil Group Land Use Fallow Treatment or practice Bare soil Crop residue cover Row crops Straight row Straight row w/ residue Contoured Contoured w/ residue Contoured & terraced Contoured & terraced w/ residue Small grains Straight row Straight row w/ residue Contoured Contoured w/ residue Contoured & terraced Contoured & terraced w/ residue Close-seeded or broadcast legumes or rotation Straight row Contoured Contoured & terraced

Hydrologic condition ---Poor Good Poor Good Poor Good Poor Good Poor Good Poor Good Poor Good Poor Good Poor Good Poor Good Poor Good Poor Good Poor Good Poor Good Poor Good Poor Good

A 77 76 74 72 67 71 64 70 65 69 64 66 62 65 61 65 63 64 60 63 61 62 60 61 59 60 58 66 58 64 55 63 51

B 86 85 83 81 78 80 75 79 75 78 74 74 71 73 70 76 75 75 72 74 73 73 72 72 70 71 69 77 72 75 69 73 67

C 91 90 88 88 85 87 82 84 82 83 81 80 78 79 77 84 83 83 80 82 81 81 80 79 78 78 77 85 81 83 78 80 76

D 94 93 90 91 89 90 85 88 86 87 85 82 81 81 80 88 87 86 84 85 84 84 83 82 81 81 80 89 85 85 83 83 80

These tables are reproduced from Urban Hydrology for Small Watersheds, USDA Soil Conservation Service Engineering Division, Technical Release 55, June 1986. Crop residue cover applies only if residue is on at least 5% of the surface throughout the year.

Table 2: Runoff curve numbers for other agricultural lands

Cover Hydrologic Soil Group Cover Type Pasture, grassland, or rangecontinuous forage for grazing
1

Hydrologic condition Poor Fair Good

A 68 49 39 30 48 35 30 57 43 32 45 36 30 59

B 79 69 61 58 67 56 48 73 65 58 66 60 55 74

C 86 79 74 71 77 70 65 82 76 72 77 73 70 82

D 89 84 80 78 83 77 73 86 82 79 83 79 77 86

Meadowcontinuous grass, protected from grazing and generally mowed for hay. Brushbrush-weed-grass mixture with brush the major element2

---Poor Fair Good

Woodsgrass combination (orchard or tree farm)

Poor Fair Good

Woods

Poor Fair Good ----

Farmsteadsbuildings, lanes, driveways, and surrounding lots.

Poor: < 50% ground cover or heavily grazed with no mulch Fair: 50 to 75% ground cover and not heavily grazed Good: > 75% ground cover and lightly or only occasionally grazed 2 Poor: < 50% ground cover Fair: 50 to 75% ground cover Good: > 75% ground cover 3 Poor: Forest litter, small trees, and brush are destroyed by heavy grazing or regular burning Fair: Woods are grazed but not burned, and some forest litter covers the soil. Good: Woods are protected from grazing, and litter and brush adequately cover the soil.

Table 3: Runoff curve numbers for urban areas

Cover Hydrologic Soil Group Hydrologic condition Average % impervious area A B C D

Cover Type Fully developed urban areas Open spaces (lawns, parks, golf courses, cemeteries, etc.)4

Poor Fair Good

68 49 39

79 69 61

86 79 74

89 84 80

Impervious areas: Paved parking lots, roofs, driveways, etc. (excluding right-of-way) Paved streets and roads; curbs and storm sewers (excluding right-of-way) Paved streets and roads; open ditches (including right-of-way) Gravel streets and roads (including right-ofway) Dirt streets and roads (including right-of way) Urban districts: Commercial and business Industrial Residential Districts by average lot size: 1/8 acre (0.05 ha) or less (town houses) 1/4 acre (0.10 ha) 1/3 acre (0.13 ha) 1/2 acre (0.20 ha) 1 acre (0.40 ha) 2 acres (0.81 ha) Developing urban areas: Newly graded areas (pervious areas only, no vegetation) 65% 38% 30% 25% 20% 12% 77 61 57 54 51 46 85 75 72 70 68 65 90 83 81 80 79 77 92 87 86 85 84 82 85% 72% 89 81 92 88 94 91 95 93 ---------------98 98 83 76 72 98 98 89 85 82 98 98 92 89 87 98 98 93 91 89

77

86

91

94

Poor: grass cover < 50% Fair: grass cover 50 to 75% Good: grass cover > 75%

Table 4: Runoff curve numbers for arid and semiarid rangelands

Cover Hydrologic Soil Group Cover Type Herbaceousmixture of grass, weeds, and low-growing brush, with brush the minor element. Hydrologic condition5 Poor Fair Good Oak-aspenmountain brush mixture of oak brush, aspen, mountain mahogany, bitter brush, maple, and other brush. Poor Fair Good Pinyon-juniperpinyon, juniper, or both: grass understory. Poor Fair Good Sagebrush with grass understory. Poor Fair Good Desert shrubmajor plants include saltbrush, greasewood, creosotebush, blackbrush, bursage, palo verde, mesquite, and cactus. A B 80 71 62 66 48 30 75 58 41 67 51 35 C 87 81 74 74 57 41 85 73 61 80 63 47 D 93 89 85 79 63 48 89 80 71 85 70 55

Poor Fair Good

63 55 49

77 72 68

85 81 79

88 86 84

Poor: < 30% ground cover (litter, grass, and brush overstory) Fair: 30 to 70% ground cover Good: > 70% ground cover

Curve Number Calibration

Table 1: Guideline runoff curve number ranges
Land Cover Category Row crop Small grain/close grown crop Perennial grasses Annual grasses (close-seeded legumes) Range Semiarid/arid range Brush Woods Orchard/tree farm Urban A 61-72 58-65 30-68 51-66 39-68 39-74 30-48 25-45 32-57 46-89 Hydrologic Soil Group B C 70-81 77-88 69-76 77-84 58-79 71-86 67-77 76-85 61-79 74-86 62-80 74-87 48-67 65-77 55-66 70-77 58-73 72-82 65-92 77-94 D 80-91 80-88 78-89 80-89 80-89 85-93 73-83 77-83 79-86 82-95

APPENDIX A

DATABASES

The following sections describe the source of input for databases included with the model and any assumptions used in compilation of the database. Also, a methodology for appending additional information to the various databases is summarized.

355

356

SWAT USERS MANUAL, VERSION 2000

A.1 LAND COVER/PLANT GROWTH DATABASE

The land cover/plant growth database contains information needed by SWAT to simulate the growth of a particular land cover. The growth parameters in the plant growth database define plant growth under ideal conditions and quantify the impact of some stresses on plant growth. Table A-1 lists all the default plant species and Table A-2 lists all the generic land covers included in the database. When adding a new plant/land cover to the database, a review of existing literature should provide most of the parameter values needed to simulate plant growth. For users that plan to collect the data directly, the following sections briefly describe the methods used to obtain the plant growth parameters needed by SWAT.
Table A-1: Plants included in plant growth database. Plant Common Name Code Taxonomic Name Corn Zea mays L. CORN Corn silage Zea mays L. CSIL Zea mays L. saccharata Sweet corn SCRN Tripsacum dactyloides (L.) L. Eastern gamagrass EGAM Sorghum bicolor L. (Moench) Grain sorghum GRSG
Sorghum hay Johnsongrass Sugarcane Spring wheat Winter wheat Durum wheat Rye Spring barley Oats Rice Pearl millet Timothy Smooth bromegrass Meadow bromegrass Tall fescue Kentucky bluegrass Bermudagrass Crested wheatgrass Western wheatgrass Slender wheatgrass

Plant type
warm season annual warm season annual warm season annual perennial warm season annual warm season annual perennial perennial cool season annual cool season annual cool season annual cool season annual cool season annual cool season annual warm season annual warm season annual perennial perennial perennial perennial perennial perennial perennial perennial perennial

SGHY JHGR SUGC SWHT WWHT DWHT RYE BARL OATS RICE PMIL TIMO BROS BROM FESC BLUG BERM CWGR WWGR SWGR

Sorghum bicolor L. (Moench) Sorghum halepense (L.) Pers. Saccharum officinarum L. Triticum aestivum L. Triticum aestivum L. Triticum durum Desf. Secale cereale L. Hordeum vulgare L. Avena sativa L. Oryza sativa L. Pennisetum glaucum L. Phleum pratense L. Bromus inermis Leysser Bromus biebersteinii Roemer & Schultes Festuca arundinacea Poa pratensis Cynodon dactylon Agropyron cristatum (L.) Gaertner Agropyron smithii (Rydb.) Gould Agropyron trachycaulum Malte

APPENDIX A: DATABASES

357

Common Name
Italian (annual) ryegrass Russian wildrye Altai wildrye Sideoats grama Big bluestem Little bluestem Alamo switchgrass Indiangrass Alfalfa Sweetclover Red clover Alsike clover Soybean Cowpeas Mung bean Lima beans Lentils Peanut Field peas Garden or canning peas Sesbania Flax Upland cotton (harvested with stripper) Upland cotton (harvested with picker) Tobacco Sugarbeet Potato Sweetpotato Carrot Onion Sunflower Spring canola-Polish Spring canola-Argentine Asparagus Broccoli Cabbage Cauliflower Celery Head lettuce Spinach Green beans Cucumber

Plant Code RYEG RYER RYEA SIDE BBLS LBLS SWCH INDN ALFA CLVS CLVR CLVA SOYB CWPS MUNG LIMA LENT PNUT FPEA PEAS SESB FLAX COTS COTP TOBC SGBT POTA SPOT CRRT ONIO SUNF CANP CANA ASPR BROC CABG CAUF CELR LETT SPIN GRBN CUCM

Taxonomic Name
Lolium multiflorum Lam. Psathyrostachys juncea (Fisch.) Nevski Leymus angustus (Trin.) Pilger Bouteloua curtipendula (Michaux) Torrey Andropogon gerardii Vitman Schizachyrium scoparium (Michaux) Nash Panicum virgatum L. Sorghastrum nutans (L.) Nash Medicago sativa L. Melilotus alba Med. Trifolium pratense L. Trifolium hybridum L. Glycine max L., Merr. Vigna sinensis Phaseolus aureus Roxb. Phaseolus lunatus L. Lens esculenta Moench J. Arachis hypogaea L. Pisum arvense L. Pisum sativum L. ssp. sativum Sesbania macrocarpa Muhl [exaltata] Linum usitatissum L. Gossypium hirsutum L. Gossypium hirsutum L. Nicotiana tabacum L. Beta vulgaris (saccharifera) L. Solanum tuberosum L. Ipomoea batatas Lam. Daucus carota L. subsp. sativus (Hoffm.) Arcang. Allium cepa L. var cepa Helianthus annuus L. Brassica campestris Brassica napus Asparagus officinalis L. Brassica oleracea L. var italica Plenck. Brassica oleracea L. var capitata L. Brassica oleracea L. var botrytis L. Apium graveolens L. var dulce (Mill.) Pers. Lactuca sativa L. var capitata L. Spinacia oleracea L. Phaseolus vulgaris Cucumis sativus L.

Plant type
cool season annual perennial perennial perennial perennial perennial perennial perennial perennial legume perennial legume cool season annual legume perennial legume warm season annual legume warm season annual legume warm season annual legume warm season annual legume warm season annual legume warm season annual legume cool season annual legume cool season annual legume warm season annual legume cool season annual warm season annual warm season annual warm season annual warm season annual cool season annual warm season annual cool season annual cool season annual warm season annual cool season annual cool season annual perennial cool season annual perennial cool season annual perennial cool season annual cool season annual warm season annual legume warm season annual

358

SWAT USERS MANUAL, VERSION 2000 Plant Code EGGP CANT HMEL WMEL PEPR STRW TOMA APPL PINE OAK POPL MESQ

Common Name
Eggplant Cantaloupe Honeydew melon Watermelon Bell pepper Strawberry Tomato Apple Pine Oak Poplar Honey mesquite

Taxonomic Name
Solanum melongena L. Cucumis melo L. Cantaloupensis group Cucumis melo L. Inodorus group Citrullus lanatus (Thunb.) Matsum and Nakai Capsicum annuum L. Grossum group Fragaria X Ananassa Duchesne. Lycopersicon esculentum Mill. Malus domestica Borkh. Pinus Quercus Populus Prosopis glandulosa Torr. var. glandulosa

Plant Type
warm season annual warm season annual warm season annual warm season annual warm season annual perennial warm season annual trees trees trees trees trees

Table A-2: Generic Land Covers included in database. Plant Name Code Origin of Plant Growth Values Agricultural Land-Generic AGRL use values for Grain Sorghum Agricultural Land-Row Crops AGRR use values for Corn Agricultual Land-Close-grown AGRC use values for Winter Wheat Orchard ORCD use values for Apples use values for Bermudagrass Hay HAY use values for Oak Forest-mixed FRST use values for Oak Forest-deciduous FRSD use values for Pine Forest-evergreen FRSE Wetlands WETL use values for Alamo Switchgrass Wetlands-forested WETF use values for Oak Wetlands-nonforested WETN use values for Alamo Switchgrass use values for Bermudagrass Pasture PAST use values for Bermudagrass Summer pasture SPAS Winter pasture WPAS use values for Fescue Range-grasses RNGE use values for Little Bluestem (LAImax=2.5) Range-brush RNGB use values for Little Bluestem (LAImax=2.0) Range-southwestern US SWRN use values for Little Bluestem (LAImax=1.5) Water WATR

Plant Type
warm season annual warm season annual cool season annual trees perennial trees trees trees perennial trees perennial perennial perennial perennial perennial perennial perennial not applicable

The Bermudagrass parameters input for Hay and Pasture are valid only in latitudes less than 35 to 37. At higher latitudes, Fescue parameters should be used to model generic Hay and Pasture. Water was included in the plant growth database in order to process USGS map layers in the HUMUS project. This land cover should not be used as a land cover in an HRU. To model water bodies, create ponds, wetlands or reservoirs.

APPENDIX A: DATABASES

359

A.1.1 LAND COVER/PLANT TYPES IN DATABASE

When compiling the list of plants in the default database, we attempted to include the most economically important plants as well as those that are widely distributed in the landscape. This list is by no means exhaustive and users may need to add plants to the list. A number of generic land cover types were also compiled to facilitate linkage of land use/land cover maps to SWAT plant categories. Because of the broad nature of the some of the categories, a number of assumptions had to be made when compiling the plant growth parameter values. The user is strongly recommended to use parameters for a specific plant rather than those of the generic land covers any time information about plant types is available for the region being modeled. Plant code (CPNM): 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. When adding a new plant species or land cover category, the four letter code for the new plant must be unique. Land cover/plant classification (IDC): SWAT groups plants into seven categories: warm season annual legume, cold season annual legume, perennial legume, warm season annual, cold season annual, perennial and trees. (Biannual plants are classified as perennials.) The differences between the categories as modeled by SWAT are summarized in Chapter 17. Plant classifications can be easily found in horticulture books that summarize characteristics for different species. The classifications assigned to the plants in Table A-1 were obtained from Martin et al. (1976) and Bailey (1935).

A.1.2 TEMPERATURE RESPONSES

SWAT uses the base temperature (T_BASE) 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 modelSWAT uses the same base temperature throughout the growing season. The optimal temperature (T_OPT) is used to calculate temperature stress for the plant during the growing season (temperature stress is the only calculation

360

SWAT USERS MANUAL, VERSION 2000

in which optimal temperature is used). Chapter 19 reviews the influence of optimal temperature on plant growth. 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 A-1 plots data for corn. (Note that the line intersects the x-axis at 8C.)

Figure A-1: Rate of leaf tip appearance as a function of temperature for corn (After Kiniry et al, 1991).

Optimal temperature for plant growth is difficult to measure directly. Looking at Figure A-1, one might be tempted to select the temperature corresponding to the peak of the plot as the optimal temperature. This would not be correct. The peak of the plot defines the optimal temperature for leaf developmentnot 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

APPENDIX A: DATABASES

361

used. For warm season plants, the generic base temperature is ~8C and the generic optimal temperature is ~25C. For cool season plants, the generic base temperature is ~0C and the generic optimal temperature is ~13C. Base and optimal temperatures for the plants included in the database are listed in Table A-3.
Table A-3: Temperature parameters for plants included in plant growth database. Plant Common Name Code Tbase Topt Corn 8 25 CORN Corn silage 8 25 CSIL 12 24 Sweet corn SCRN 12 25 Eastern gamagrass EGAM 11 30 Grain sorghum GRSG
Sorghum hay Johnsongrass Sugarcane Spring wheat Winter wheat Durum wheat Rye Spring barley Oats Rice Pearl millet Timothy Smooth bromegrass Meadow bromegrass Tall fescue Kentucky bluegrass Bermudagrass Crested wheatgrass Western wheatgrass Slender wheatgrass Italian (annual) ryegrass Russian wildrye Altai wildrye Sideoats grama Big bluestem Little bluestem Alamo switchgrass Indiangrass Alfalfa Sweetclover

Reference
(Kiniry et al, 1995) (Kiniry et al, 1995) (Hackett and Carolane, 1982) (Kiniry, personal comm., 2001) (Kiniry et al, 1992a) (Kiniry et al, 1992a) (Kiniry et al, 1992a) (Kiniry and Williams, 1994) (Kiniry et al, 1995) (Kiniry et al, 1995) estimated estimated (Kiniry et al, 1995) (Kiniry, personal comm., 2001) (Martin et al, 1976) (Kiniry et al, 1991) estimated estimated (Kiniry et al, 1995) estimated (Kiniry, personal comm., 2001) (Kiniry, personal comm., 2001) (Kiniry et al, 1995) (Kiniry et al, 1995) estimated estimated (Kiniry et al, 1995) (Kiniry et al, 1995) (Kiniry, personal comm., 2001) (Kiniry, personal comm., 2001) (Kiniry, personal comm., 2001) (Kiniry et al, 1996) (Kiniry, personal comm., 2001) (Kiniry, personal comm., 2001) estimated

SGHY JHGR SUGC SWHT WWHT DWHT RYE BARL OATS RICE PMIL TIMO BROS BROM FESC BLUG BERM CWGR WWGR SWGR RYEG RYER RYEA SIDE BBLS LBLS SWCH INDN ALFA CLVS

11 11 11 0 0 0 0 0 0 10 10 8 8 6 0 12 12 6 6 8 0 0 0 12 12 12 12 12 4 1

30 30 25 18 18 15 12.5 25 15 25 30 25 25 25 15 25 25 25 25 25 18 15 15 25 25 25 25 25 20 15

362 Common Name

Red clover Alsike clover Soybean Cowpeas Mung bean

SWAT USERS MANUAL, VERSION 2000 Plant Code CLVR CLVA SOYB CWPS MUNG LIMA LENT PNUT FPEA PEAS SESB FLAX COTS COTP TOBC SGBT POTA SPOT CRRT ONIO SUNF CANP CANA ASPR BROC CABG CAUF CELR LETT SPIN GRBN CUCM EGGP CANT HMEL WMEL PEPR STRW TOMA APPL Tbase
1 1 10 14 15 18 3 14 1 5 10 5 15 15 10 4 7 14 7 7

Topt
15 15 25 28 30 26 20 27 15 14 25 22.5 30 30 25 18 22 24 24 19

Reference
estimated estimated (Kiniry et al, 1992a) (Kiniry et al, 1991; Hackett and Carolane, 1982) (Hackett and Carolane, 1982) (Hackett and Carolane, 1982) (Hackett and Carolane, 1982) (Hackett and Carolane, 1982) estimated (Hackett and Carolane, 1982) estimated estimated (Martin et al, 1976) (Martin et al, 1976) (Martin et al, 1976) (Kiniry and Williams, 1994) (Hackett and Carolane, 1982) (estimated; Hackett and Carolane, 1982) (Kiniry and Williams, 1994) (Hackett and Carolane, 1982; Kiniry and Williams, 1994) (Kiniry et al, 1992b; Kiniry, personal communication, 2001) (Kiniry et al, 1995) (Kiniry et al, 1995) (Hackett and Carolane, 1982) (Hackett and Carolane, 1982) (Hackett and Carolane, 1982) (Hackett and Carolane, 1982) (Hackett and Carolane, 1982) (Hackett and Carolane, 1982) (Kiniry and Williams, 1994) (Hackett and Carolane, 1982) (Kiniry and Williams, 1994) (Hackett and Carolane, 1982) (Hackett and Carolane, 1982; Kiniry and Williams, 1994) (Kiniry and Williams, 1994) (Kiniry and Williams, 1994) (Kiniry and Williams, 1994) (Kiniry and Williams, 1994) (Hackett and Carolane, 1982) (Hackett and Carolane, 1982)

Lima beans Lentils Peanut Field peas Garden or canning peas Sesbania Flax Upland cotton (harvested with stripper) Upland cotton (harvested with picker) Tobacco Sugarbeet Potato Sweetpotato Carrot Onion

Sunflower Spring canola-Polish Spring canola-Argentine Asparagus Broccoli Cabbage Cauliflower Celery Head lettuce Spinach Green beans Cucumber Eggplant Cantaloupe Honeydew melon Watermelon Bell pepper Strawberry Tomato Apple

6 5 5 10 4 1 5 4 7 4 10 16 15 15 16 18 18 10 10 7

25 21 21 24 18 18 18 22 18 24 19 32 26 35 36 35 27 32 22 20

APPENDIX A: DATABASES

363

Common Name
Pine Oak Poplar Honey mesquite

Plant Code PINE OAK POPL MESQ

Tbase
0 10 10 10

Topt
30 30 30 30

Reference
(Kiniry, personal comm., 2001) (Kiniry, personal comm., 2001) (Kiniry, personal comm., 2001) (Kiniry, personal comm., 2001)

A.1.3 LEAF AREA DEVELOPMENT

Leaf area development is a function of the plants growing season. Plant growth database variables used to quantify leaf area development are: BLAI, FRGRW1, LAIMX1, FRGRW2, LAIMX2, and DLAI. Figure A-2 illustrates the relationship of the database parameters to the leaf area development modeled by SWAT.

Figure A-2: Leaf area index as a function of fraction of growing season for Alamo switchgrass.

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.

364

SWAT USERS MANUAL, VERSION 2000

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 17 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. Leaf area development parameter values for the plants included in the database are listed in Table A-4 (LAImx = BLAI; frPHU,1 = FRGRW1; frLAI,1 = LAIMX1; frPHU,2 = FRGRW2; frLAI,2 = LAIMX2; frPHU,sen = DLAI).
Table A-4: Leaf area development parameters for plants included in plant growth database. Plant Common Name Code LAImx frPHU,1 frLAI,1 frPHU,2 frLAI,2 frPHU,sen Corn 3 0.15 0.05 0.50 0.95 0.70 CORN
Corn silage Sweet corn Eastern gamagrass Grain sorghum

Reference
(Kiniry et al, 1995; Kiniry, personal comm., 2001) (Kiniry et al, 1995; Kiniry, personal comm., 2001) (Kiniry, personal comm., 2001; Kiniry and Williams, 1994) (Kiniry, personal comm., 2001) (Kiniry, personal comm., 2001; Kiniry and Bockholt, 1998) (Kiniry, personal comm., 2001; Kiniry and Bockholt, 1998)

CSIL SCRN EGAM GRSG SGHY

4 2.5 2.5 3

0.15 0.15 0.05 0.15

0.05 0.05 0.18 0.05

0.50 0.50 0.25 0.50

0.95 0.95 0.90 0.95

0.70 0.50 0.40 0.64

Sorghum hay

0.15

0.05

0.50

0.95

0.64

APPENDIX A: DATABASES Common Name

Johnsongrass Sugarcane Spring wheat Winter wheat Durum wheat

365

Plant Code JHGR SUGC SWHT WWHT DWHT RYE BARL OATS RICE PMIL TIMO BROS BROM FESC BLUG BERM CWGR WWGR SWGR RYEG RYER RYEA SIDE BBLS LBLS SWCH INDN ALFA CLVS CLVR CLVA

LAImx
2.5 6 4 4 4

frPHU,1
0.15 0.15 0.15 0.05 0.15

frLAI,1
0.05 0.01 0.05 0.05 0.01

frPHU,2
0.57 0.50 0.50 0.45 0.50

frLAI,2
0.95 0.95 0.95 0.95 0.95

frPHU,sen
0.50 0.75 0.60 0.50 0.80

Reference
(Kiniry, personal comm., 2001; Kiniry et al, 1992a) (Kiniry and Williams, 1994) (Kiniry et al, 1995; Kiniry, personal comm., 2001) (Kiniry et al, 1995; Kiniry, personal comm., 2001) (Kiniry, personal communication, 2001; estimated) (Kiniry, personal communication, 2001; estimated) (Kiniry et al, 1995; Kiniry, personal comm., 2001) (Kiniry, personal comm., 2001) (Kiniry, personal comm., 2001; estimated) (Kiniry, personal comm., 2001; estimated) (Kiniry, personal comm., 2001; estimated) (Kiniry, personal comm., 2001; estimated) (Kiniry et al, 1995; Kiniry, personal comm., 2001) (Kiniry, personal comm, 2001; estimated) (Kiniry, personal comm., 2001) (Kiniry, personal comm, 2001) (Kiniry et al, 1995; Kiniry, personal comm., 2001) (Kiniry et al, 1995; Kiniry, personal comm., 2001) (Kiniry, personal comm., 2001; estimated) (Kiniry, personal comm., 2001; estimated) (Kiniry et al, 1995) (Kiniry et al, 1995) (Kiniry, personal comm., 2001) (Kiniry, personal comm., 2001) (Kiniry, personal comm., 2001) (Kiniry, personal comm., 2001; Kiniry et al, 1996) (Kiniry, personal comm., 2001) (Kiniry, personal comm., 2001) (Kiniry, personal comm., 2001; estimated) (Kiniry, personal comm., 2001; estimated) (Kiniry, personal comm., 2001; estimated)

Rye Spring barley Oats Rice Pearl millet

4 4 4 5 2.5

0.15 0.15 0.15 0.30 0.15

0.01 0.01 0.02 0.01 0.01

0.50 0.45 0.50 0.70 0.50

0.95 0.95 0.95 0.95 0.95

0.80 0.60 0.80 0.80 0.85

Timothy Smooth bromegrass Meadow bromegrass Tall fescue Kentucky bluegrass Bermudagrass Crested wheatgrass Western wheatgrass Slender wheatgrass Italian (annual) ryegrass

4 5 3 4 2 4 4 4 4 4

0.15 0.15 0.45 0.15 0.05 0.05 0.35 0.50 0.15 0.20

0.01 0.01 0.02 0.01 0.05 0.05 0.02 0.02 0.01 0.32

0.50 0.50 0.80 0.50 0.30 0.49 0.62 0.89 0.50 0.45

0.95 0.95 0.95 0.95 0.70 0.95 0.95 0.95 0.95 0.95

0.85 0.85 0.85 0.80 0.35 0.99 0.85 0.85 0.85 0.50

Russian wildrye Altai wildrye Sideoats grama Big bluestem Little bluestem Alamo switchgrass Indiangrass Alfalfa Sweetclover Red clover

3 3 1.7 3 2.5 6 3 4 4 4

0.35 0.35 0.05 0.05 0.05 0.10 0.05 0.15 0.15 0.15

0.02 0.02 0.05 0.10 0.10 0.20 0.10 0.01 0.01 0.01

0.62 0.62 0.30 0.25 0.25 0.20 0.25 0.50 0.50 0.50

0.95 0.95 0.70 0.70 0.70 0.95 0.70 0.95 0.95 0.95

0.80 0.80 0.35 0.35 0.35 0.70 0.35 0.90 0.75 0.75

Alsike clover

0.15

0.01

0.50

0.95

0.75

366

SWAT USERS MANUAL, VERSION 2000 Plant Code SOYB CWPS MUNG LIMA LENT PNUT FPEA PEAS SESB FLAX COTS COTP TOBC SGBT POTA SPOT CRRT ONIO SUNF CANP CANA ASPR BROC CABG CAUF CELR LETT SPIN GRBN CUCM EGGP CANT HMEL WMEL PEPR

Common Name
Soybean Cowpeas Mung bean Lima beans Lentils

LAImx
3 4 4 2.5 4

frPHU,1
0.15 0.15 0.15 0.10 0.15

frLAI,1
0.05 0.01 0.01 0.05 0.02

frPHU,2
0.50 0.50 0.50 0.80 0.50

frLAI,2
0.95 0.95 0.95 0.95 0.95

frPHU,sen
0.60 0.80 0.90 0.90 0.90

Reference
(Kiniry, personal comm., 2001; Kiniry et al, 1992a) (Kiniry, personal comm., 2001; estimated) (Kiniry, personal comm., 2001; estimated) (Kiniry and Williams, 1994) (Kiniry, personal comm., 2001; estimated) (Kiniry, personal comm., 2001; estimated) (Kiniry, personal comm., 2001; estimated) (Kiniry and Williams, 1994) (Kiniry, personal comm., 2001; estimated) (Kiniry, personal comm., 2001; estimated) (Kiniry, personal comm., 2001; estimated) (Kiniry, personal comm., 2001; estimated) (Kiniry and Williams, 1994) (Kiniry and Williams, 1994) (Kiniry, personal comm., 2001; Kiniry and Williams, 1994) (Kiniry, personal comm., 2001; estimated) (Kiniry and Williams, 1994) (Kiniry and Williams, 1994) (Kiniry, personal comm., 2001; Kiniry et al, 1992b) (Kiniry et al, 1995) (Kiniry et al, 1995) (Kiniry and Williams, 1994) (Kiniry and Williams, 1994) (Kiniry and Williams, 1994) (Kiniry and Williams, 1994) (Kiniry and Williams, 1994) (Kiniry and Williams, 1994) (Kiniry and Williams, 1994) (Kiniry and Williams, 1994) (Kiniry and Williams, 1994) (Kiniry and Williams, 1994) (Kiniry and Williams, 1994) (Kiniry and Williams, 1994) (Kiniry and Williams, 1994) (Kiniry and Williams, 1994)

Peanut Field peas Garden or canning peas Sesbania Flax

4 4 2.5 5 2.5

0.15 0.15 0.10 0.15 0.15

0.01 0.01 0.05 0.01 0.02

0.50 0.50 0.80 0.50 0.50

0.95 0.95 0.95 0.95 0.95

0.75 0.75 0.60 0.90 0.90

Upland cotton (harvested with stripper) Upland cotton (harvested with picker) Tobacco Sugarbeet Potato

4 4 4.5 5 4

0.15 0.15 0.15 0.05 0.15

0.01 0.01 0.05 0.05 0.01

0.50 0.50 0.50 0.50 0.50

0.95 0.95 0.95 0.95 0.95

0.95 0.95 0.70 0.60 0.60

Sweetpotato Carrot Onion Sunflower Spring canola-Polish Spring canola-Argentine Asparagus Broccoli Cabbage Cauliflower Celery Head lettuce Spinach Green beans Cucumber Eggplant Cantaloupe Honeydew melon Watermelon Bell pepper

4 3.5 1.5 3 3.5 4.5 4.2 4.2 3 2.5 2.5 4.2 4.2 1.5 1.5 3 3 4 1.5 5

0.15 0.15 0.15 0.15 0.15 0.15 0.25 0.25 0.25 0.25 0.25 0.25 0.10 0.10 0.15 0.15 0.15 0.15 0.15 0.15

0.01 0.01 0.01 0.01 0.02 0.02 0.23 0.23 0.23 0.23 0.23 0.23 0.05 0.05 0.05 0.05 0.05 0.05 0.05 0.05

0.50 0.50 0.50 0.50 0.45 0.45 0.40 0.40 0.40 0.40 0.40 0.40 0.90 0.80 0.50 0.50 0.50 0.50 0.50 0.50

0.95 0.95 0.95 0.95 0.95 0.95 0.86 0.86 0.86 0.86 0.86 0.86 0.95 0.95 0.95 0.95 0.95 0.95 0.95 0.95

0.60 0.60 0.60 0.62 0.50 0.50 1.00 1.00 1.00 1.00 1.00 1.00 0.95 0.90 0.60 0.60 0.60 0.60 0.60 0.60

APPENDIX A: DATABASES

367

Common Name
Strawberry Tomato Apple Pine Oak Poplar Honey mesquite

Plant Code STRW TOMA APPL PINE OAK POPL MESQ

LAImx
3 3 4 5 5 5 1.25

frPHU,1
0.15 0.15 0.10 0.15 0.05 0.05 0.05

frLAI,1
0.05 0.05 0.15 0.70 0.05 0.05 0.05

frPHU,2
0.50 0.50 0.50 0.25 0.40 0.40 0.40

frLAI,2
0.95 0.95 0.75 0.99 0.95 0.95 0.95

frPHU,sen
0.60 0.95 0.99 0.99 0.99 0.99 0.99

Reference
(Kiniry and Williams, 1994) (Kiniry and Williams, 1994) (Kiniry, personal comm., 2001; estimated) (Kiniry, personal comm., 2001) (Kiniry, personal comm., 2001) (Kiniry, personal comm., 2001) (Kiniry, 1998; Kiniry, personal communication, 2001)

A.1.4 ENERGY-BIOMASS CONVERSION

Radiation-use efficiency (RUE) quantifies the efficiency of a plant in converting light energy into biomass. Four variables in the plant growth database are used to define the RUE in ideal growing conditions (BIO_E), the impact of reduced vapor pressure on RUE (WAVP), and the impact of elevated CO2 concentration on RUE (CO2HI, BIOEHI). Determination of RUE is commonly performed and a literature review will provide those setting up experiments with numerous examples. The following overview of the methodology used to measure RUE was summarized from Kiniry et al (1998) and Kiniry et al (1999). To calculate RUE, the amount of photosynthetically active radiation (PAR) intercepted and the mass of aboveground biomass is measured several times throughout a plants growing season. The frequency of the measurements taken will vary but in general 4 to 7 measurements per growing season are considered to be adequate. As with leaf area determinations, the measurements should be performed on non-stressed plants. Intercepted radiation is measured with a light meter. Whole spectrum and PAR sensors are available and calculations of RUE will be performed differently depending on the sensor used. A brief discussion of the difference between whole spectrum and PAR sensors and the difference in calculations is given in Kiniry (1999). The use of a PAR sensor in RUE studies is strongly encouraged.

368

SWAT USERS MANUAL, VERSION 2000

When measuring radiation, three to five sets of measurements are taken rapidly for each plant plot. A set of measurements consists of 10 measurements above the leaf canopy, 10 below, and 10 more above. The light measurements should be taken between 10:00 am and 2:00 pm local time. The measurements above and below the leaf canopy are averaged and the fraction of intercepted PAR is calculated for the day from the two values. Daily estimates of the fraction of intercepted PAR are determined by linearly interpolating the measured values. The fraction of intercepted PAR is converted to an amount of intercepted PAR using daily values of incident total solar radiation measured with a standard weather station. To convert total incident radiation to total incident PAR, the daily solar radiation values are multiplied by the percent of total radiation that has a wavelength between 400 and 700 mm. This percent usually falls in the range 45 to 55% and is a function of cloud cover. 50% is considered to be a default value. Once daily intercepted PAR values are determined, the total amount of PAR intercepted by the plant is calculated for each date on which biomass was harvested. This is calculated by summing daily intercepted PAR values from the date of seedling emergence to the date of biomass harvest. To determine biomass production, aboveground biomass is harvested from a known area of land within the plot. The plant material should be dried at least 2 days at 65C and then weighed. RUE is determined by fitting a linear regression for aboveground biomass as a function of intercepted PAR. The slope of the line is the RUE. Figure A-3 shows the plots of aboveground biomass and summed intercepted

photosynthetically active radiation for Eastern gamagrass. (Note that the units for RUE values in the graph, as well as values typically reported in literature, are different from those used by SWAT. To obtain the value used in SWAT, multiply by 10.)

APPENDIX A: DATABASES

369

Figure A-3: Aboveground biomass and summed intercepted photosynthetically active radiation for Eastern gamagrass (After Kiniry et al.,1999).

Stockle and Kiniry (1990) first noticed a relationship between RUE and vapor pressure deficit and were able to explain a large portion of within-species variability in RUE values for sorghum and corn by plotting RUE values as a function of average daily vapor pressure deficit values. Since this first article, a number of other studies have been conducted that support the dependence of RUE on vapor pressure deficit. However, there is still some debate in the scientific community on the validity of this relationship. If the user does not wish to simulate a change in RUE with vapor pressure deficit, the variable WAVP can be set to 0.0 for the plant. To define the impact of vapor pressure deficit on RUE, vapor pressure deficit values must be recorded during the growing seasons that RUE determinations are being made. It is important that the plants are exposed to no other stress than vapor pressure deficit, i.e. plant growth should not be limited by lack of soil water and nutrients. Vapor pressure deficits can be calculated from relative humidity (see Chapter 3) or from daily maximum and minimum temperatures using the technique of Diaz and Campbell (1988) as described by Stockle and Kiniry (1990). The change in RUE with vapor pressure deficit is determined by fitting a

370

SWAT USERS MANUAL, VERSION 2000

linear regression for RUE as a function of vapor pressure deficit. Figure A-4 shows a plot of RUE as a function of vapor pressure deficit for grain sorghum.

Figure A-4: Response of radiation-use efficiency to mean daily vapor pressure deficit for grain sorghum (After Kiniry, 1999).

From Figure A-4, the rate of decline in radiation-use efficiency per unit increase in vapor pressure deficit, ruedcl, for sorghum is 8.410-1 gMJ-1kPa-1. When RUE is adjusted for vapor pressure deficit, the model assumes the RUE value reported for BIO_E is the radiation-use efficiency at a vapor pressure deficit of 1 kPa. In order to assess the impact of climate change on agricultural productivity, SWAT incorporates equations that adjust RUE for elevated atmospheric CO2 concentrations. Values must be entered for CO2HI and BIOEHI in the plant database whether or not the user plans to simulate climate change. For simulations in which elevated CO2 levels are not modeled, CO2HI should be set to some number greater than 330 ppmv and BIOEHI should be set to some number greater than BIO_E. To obtain radiation-use efficiency values at elevated CO2 levels for plant species not currently in the database, plants should be established in growth chambers set up in the field or laboratory where CO2 levels can be controlled. RUE values are determined using the same methodology described previously.

APPENDIX A: DATABASES

371

Radiation-use efficiency parameter values for the plants included in the database are listed in Table A-5 (RUE = BIO_E; ruedcl = WAVP; RUEhi = BIOEHI; CO2hi = CO2HI).

Table A-5: Biomass production parameters for plants included in plant growth database. Plant Common Name Code RUE ruedcl RUEhi CO2hi Reference Corn 39 7.2 45 660 (Kiniry et al, 1998; Kiniry et al, 1997; Kiniry, CORN
Corn silage Sweet corn Eastern gamagrass Grain sorghum

CSIL SCRN EGAM GRSG SGHY JHGR SUGC SWHT WWHT DWHT RYE BARL OATS RICE PMIL TIMO BROS BROM FESC BLUG BERM CWGR WWGR SWGR RYEG RYER RYEA SIDE

39 39 21 33.5

7.2 7.2 10 8.5

45 45 58 36

660 660 660 660

personal communication, 2001) (Kiniry et al, 1998; Kiniry et al, 1997; Kiniry, personal communication, 2001) (Kiniry and Williams, 1994; Kiniry et al, 1997; Kiniry, personal communication, 2001) (Kiniry et al, 1999; Kiniry, personal communication, 2001) (Kiniry et al, 1998; Kiniry, personal communication, 2001) (Kiniry et al, 1998; Kiniry, personal communication, 2001) (Kiniry et al, 1992a; Kiniry, personal communication, 2001) (Kiniry and Williams, 1994; Kiniry, personal communication, 2001) (Kiniry et al, 1992a; Kiniry, personal communication, 2001; estimated) (Kiniry et al, 1995; estimated) (estimated) (estimated) (Kiniry et al, 1995; estimated) (Kiniry, personal communication, 2001) (Kiniry et al, 1989; estimated) (estimated) (estimated) (estimated) (Kiniry et al, 1995; estimated) (estimated) (Kiniry, personal communication, 2001) (Kiniry, personal communication, 2001) (Kiniry et al, 1995; Kiniry, personal communication, 2001) (Kiniry et al, 1995; estimated) (estimated) (estimated) (Kiniry et al, 1995; estimated) (Kiniry et al, 1995; Kiniry, personal communication, 2001) (Kiniry et al, 1999; Kiniry, personal communication, 2001)

Sorghum hay Johnsongrass Sugarcane Spring wheat Winter wheat Durum wheat Rye Spring barley Oats Rice Pearl millet Timothy Smooth bromegrass Meadow bromegrass Tall fescue Kentucky bluegrass Bermudagrass Crested wheatgrass Western wheatgrass Slender wheatgrass Italian (annual) ryegrass Russian wildrye Altai wildrye Sideoats grama

33.5 35 25 35 30 30 35 35 35 22 35 35 35 35 30 18 35 35 35 35 30 30 30 11

8.5 8.5 10 8 6 7 7 7 10 5 8 8 8 8 8 10 10 8 8 8 6 8 8 10

36 36 33 46 39 45 45 45 45 31 40 45 45 45 39 31 36 38 45 45 39 39 46 21

660 660 660 660 660 660 660 660 660 660 660 660 660 660 660 660 660 660 660 660 660 660 660 660

372 Common Name

Big bluestem Little bluestem Alamo switchgrass Indiangrass Alfalfa Sweetclover Red clover Alsike clover Soybean Cowpeas Mung bean Lima beans Lentils Peanut Field peas Garden or canning peas Sesbania Flax Upland cotton (harvested with stripper) Upland cotton (harvested with picker) Tobacco Sugarbeet Potato Sweetpotato Carrot Onion Sunflower Spring canola-Polish Spring canola-Argentine Asparagus Broccoli Cabbage Cauliflower Celery Head lettuce Spinach Green beans Cucumber Eggplant Cantaloupe

SWAT USERS MANUAL, VERSION 2000 Plant Code BBLS LBLS SWCH INDN ALFA CLVS CLVR CLVA SOYB CWPS MUNG LIMA LENT PNUT FPEA PEAS SESB FLAX COTS COTP TOBC SGBT POTA SPOT CRRT ONIO SUNF CANP CANA ASPR BROC CABG CAUF CELR LETT SPIN GRBN CUCM EGGP CANT RUE
14 34 47 34 20 25 25 25 25 35 25 25 20 20 25 25 50 25 15 15

ruedcl
10 10 8.5 10 10 10 10 10 8 8 10 5 10 4 10 5 10 10 3 3

RUEhi
39 39 54 39 35 30 30 30 34 39 33 34 33 25 30 34 60 33 19 19

CO2hi
660 660 660 660 660 660 660 660 660 660 660 660 660 660 660 660 660 660 660 660

Reference
(Kiniry et al, 1999; Kiniry, personal communication, 2001) (Kiniry, personal communication, 2001) (Kiniry et al, 1996; Kiniry, personal communication, 2001) (Kiniry, personal communication, 2001) (Kiniry, personal communication, 2001) (estimated) (estimated) (estimated) (Kiniry et al, 1992a; Kiniry, personal communication, 2001) (estimated) (estimated) (Kiniry and Williams, 1994; estimated) (estimated) (estimated) (estimated) (Kiniry and Williams, 1994; estimated) (estimated) (estimated) (estimated) (estimated)

39 30 25 15 30 30 46 34 34 90 26 19 21 27 23 30 25 30 30 30

8 10 14.8 3 10 10 32.3 10 10 5 5 5 5 5 8 5 5 8 8 3

44 35 30 19 35 35 59 39 40 95 30 25 25 30 25 35 34 39 39 39

660 660 660 660 660 660 660 660 660 660 660 660 660 660 660 660 660 660 660 660

(Kiniry and Williams, 1994; estimated) (Kiniry and Williams, 1994; estimated) (Manrique et al, 1991; estimated) (estimated) (Kiniry and Williams, 1994; estimated) (Kiniry and Williams, 1994; estimated) (Kiniry et al, 1992b; Kiniry, personal communication, 2001) (Kiniry et al, 1995; estimated) (Kiniry et al, 1995; estimated) (Kiniry and Williams, 1994; estimated) (Kiniry and Williams, 1994; estimated) (Kiniry and Williams, 1994; estimated) (Kiniry and Williams, 1994; estimated) (Kiniry and Williams, 1994; estimated) (Kiniry and Williams, 1994; estimated) (Kiniry and Williams, 1994; estimated) (Kiniry and Williams, 1994; estimated) (Kiniry and Williams, 1994; estimated) (Kiniry and Williams, 1994; estimated) (Kiniry and Williams, 1994; estimated)

APPENDIX A: DATABASES Common Name

Honeydew melon Watermelon Bell pepper Strawberry Tomato Apple Pine Oak Poplar Honey mesquite

373

Plant Code HMEL WMEL PEPR STRW TOMA APPL PINE OAK POPL MESQ

RUE
30 30 30 30 30 15 15 15 30 16.1

ruedcl
3 3 8 8 8 3 8 8 8 8

RUEhi
39 39 39 39 39 20 16 16 31 18

CO2hi
660 660 660 660 660 660 660 660 660 660

Reference
(Kiniry and Williams, 1994; estimated) (Kiniry and Williams, 1994; estimated) (Kiniry and Williams, 1994; estimated) (Kiniry and Williams, 1994; estimated) (Kiniry and Williams, 1994; estimated) (estimated) (Kiniry, personal communication, 2001) (Kiniry, personal communication, 2001) (Kiniry, personal communication, 2001) (Kiniry, 1998; Kiniry, personal comm., 2001)

A.1.5 STOMATAL CONDUCTANCE

Stomatal conductance of water vapor is used in the Penman-Monteith calculations of maximum plant evapotranspiration. The plant database contains three variables pertaining to stomatal conductance that are required only if the Penman-Monteith equations are chosen to model evapotranspiration: maximum stomatal conductance (GSI), and two variables that define the impact of vapor pressure deficit on stomatal conductance (FRGMAX, VPDFR). Krner et al (1979) defines maximum leaf diffusive conductance as the largest value of conductance observed in fully developed leaves of well-watered plants under optimal climatic conditions, natural outdoor CO2 concentrations and sufficient nutrient supply. Leaf diffusive conductance of water vapor cannot be measured directly but can be calculated from measurements of transpiration under known climatic conditions. A number of different methods are used to determine diffusive conductance: transpiration measurements in photosynthesis cuvettes, energy balance measurements or weighing experiments, ventilated diffusion porometers and non-ventilated porometers. Krner (1977) measured diffusive conductance using a ventilated diffusion porometer. To obtain maximum leaf conductance values, leaf conductance is determined between sunrise and late morning until a clear decline or no further increase is observed. Depending on phenology, measurements are taken on at least three bright days in late spring and summer, preferably just after a rainy period.

374

SWAT USERS MANUAL, VERSION 2000

The means of maximum leaf conductance of 5 to 10 samples each day are averaged, yielding the maximum diffusive conductance for the species. Due to the variation of the location of stomata on plant leaves for different plant species, conductance values should be calculated for the total leaf surface area. Krner et al (1979) compiled maximum leaf diffusive conductance data for 246 plant species. The data for each individual species was presented as well as summarized by 13 morphologically and/or ecologically comparable plant groups. All maximum stomatal conductance values in the plant growth database were based on the data included in Krner et al (1979) (see Table A-6). As with radiation-use efficiency, stomatal conductance is sensitive to vapor pressure deficit. Stockle et al (1992) compiled a short list of stomatal conductance response to vapor pressure deficit for a few plant species. Due to the paucity of data, default values for the second point on the stomatal conductance vs. vapor pressure deficit curve are used for all plant species in the database. The fraction of maximum stomatal conductance (FRGMAX) is set to 0.75 and the vapor pressure deficit corresponding to the fraction given by FRGMAX (VPDFR) is set to 4.00 kPa. If the user has actual data, they should use those values, otherwise the default values are adequate.

A.1.6 CANOPY HEIGHT/ROOT DEPTH

Maximum canopy height (CHTMX) 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. To determine maximum rooting depth (RDMX), 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 m 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. Table A-6 lists the

APPENDIX A: DATABASES

375

maximum canopy height and maximum rooting depths for plants in the default database.
Table A-6: Maximum stomatal conductance ( g l ,mx ), maximum canopy height (hc,mx), maximum root depth (zroot,mx), minimum USLE C factor for land cover (CUSLE,mn). Plant g l,mx Common Name Code hc,mx Corn .0071 2.5 CORN
Corn silage Sweet corn Eastern gamagrass Grain sorghum

zroot,mx
2.0 2.0 2.0 2.0 2.0

CUSLE,mn
.20 .20 .20 .003 .20

Reference
(Krner et al, 1979; Martin et al, 1976; Kiniry et al, 1995; Kiniry, personal comm., 2001) (Krner et al, 1979; Martin et al, 1976; Kiniry et al, 1995; Kiniry, personal comm., 2001) (Krner et al, 1979, Kiniry and Williams, 1994; Kiniry, personal comm., 2001) (Krner et al, 1979; Kiniry, personal comm., 2001) (Krner et al, 1979; Kiniry, personal comm., 2001) (Krner et al, 1979; Martin et al, 1976; Kiniry, personal comm., 2001) (Krner et al, 1979; Kiniry et al, 1992a) (Krner et al, 1979; Kiniry and Williams, 1994) (Krner et al, 1979; Kiniry, personal comm., 2001) (Krner et al, 1979; Kiniry, personal comm., 2001; Kiniry et al, 1995) (Krner et al, 1979; estimated; Kiniry, personal comm., 2001) (Krner et al, 1979; estimated; Martin et al, 1976; Kiniry, personal comm., 2001) (Krner et al, 1979; Kiniry and Williams, 1994; Kiniry et al, 1995) (Krner et al, 1979; Martin et al, 1976; Kiniry, personal comm., 2001) (Krner et al, 1979; Martin et al, 1976; estimated) (Krner et al, 1979; Kiniry, personal comm., 2001; estimated) (Krner et al, 1979; estimated) (Krner et al, 1979; Martin et al, 1976; estimated) (Krner et al, 1979; estimated; Kiniry et al, 1995) (Krner et al, 1979; Martin et al, 1976; estimated) (Krner et al, 1979; Kiniry, personal comm., 2001) (Krner et al, 1979; Kiniry, personal comm., 2001) (Krner et al, 1979; Martin et al, 1976; Kiniry et al, 1995) (Krner et al, 1979; Martin et al, 1976; Kiniry et al, 1995; estimated) (Krner et al, 1979; estimated)

CSIL SCRN EGAM GRSG SGHY JHGR SUGC SWHT WWHT DWHT RYE BARL OATS RICE PMIL TIMO BROS BROM FESC BLUG BERM CWGR WWGR SWGR

.0071 .0071 .0055 .0050

2.5 2.5 1.7 1.0

Sorghum hay Johnsongrass Sugarcane Spring wheat Winter wheat

.0050 .0048 .0055 .0056 .0056

1.5 1.0 3.0 0.9 0.9

2.0 2.0 2.0 2.0 1.3

.20 .20 .001 .03 .03

Durum wheat Rye Spring barley Oats Rice

.0056 .0100 .0083 .0055 .0078

1.0 1.0 1.2 1.5 0.8

2.0 1.8 1.3 2.0 0.9

.03 .03 .01 .03 .03

Pearl millet Timothy Smooth bromegrass Meadow bromegrass Tall fescue

.0143 .0055 .0025 .0055 .0055

3.0 0.8 1.2 0.8 1.5

2.0 2.0 2.0 1.3 2.0

.20 .003 .003 .003 .03

Kentucky bluegrass Bermudagrass Crested wheatgrass Western wheatgrass Slender wheatgrass

.0055 .0055 .0055 .0083 .0055

0.2 0.5 0.9 0.6 0.7

1.4 2.0 1.3 1.3 2.0

.003 .003 .003 .003 .003

376

SWAT USERS MANUAL, VERSION 2000 Plant Code RYEG RYER RYEA SIDE BBLS LBLS SWCH INDN ALFA CLVS CLVR CLVA SOYB CWPS MUNG LIMA LENT PNUT FPEA PEAS SESB FLAX COTS COTP TOBC SGBT POTA

Common Name
Italian (annual) ryegrass Russian wildrye Altai wildrye Sideoats grama Big bluestem

g l,mx
.0055 .0065 .0055 .0055 .0055

hc,mx
0.8 1.0 1.1 0.4 1.0

zroot,mx
1.3 1.3 1.3 1.4 2.0

CUSLE,mn
.03 .03 .03 .003 .003

Reference
(Krner et al, 1979; estimated) (Krner et al, 1979; estimated; Kiniry et al, 1995) (Krner et al, 1979; Kiniry, personal comm., 2001; Kiniry et al, 1995) (Krner et al, 1979; Kiniry, personal comm., 2001) (Krner et al, 1979; Kiniry, personal comm., 2001) (Krner et al, 1979; Kiniry, personal comm., 2001) (Krner et al, 1979; Kiniry, personal comm., 2001; Kiniry et al, 1996) (Krner et al, 1979; Kiniry, personal comm., 2001) (Jensen et al, 1990; Martin et al, 1976; Kiniry, personal comm., 2001) (Krner et al, 1979; Kiniry, personal comm., 2001; Martin et al, 1976; estimated) (Krner et al, 1979; Martin et al, 1976; estimated) (Krner et al, 1979; Martin et al, 1976; estimated) (Krner et al, 1979; Kiniry et al, 1992a) (Krner et al, 1979; estimated) (Krner et al, 1979; estimated) (Krner et al, 1979; Kiniry and Williams, 1994; Maynard and Hochmuth, 1997) (Krner et al, 1979; Martin et al, 1976; Maynard and Hochmuth, 1997) (Krner et al, 1979; estimated) (Krner et al, 1979; Martin et al, 1976; Maynard and Hochmuth, 1997; estimated) (Krner et al, 1979; Kiniry and Williams, 1994; Maynard and Hochmuth, 1997) (Krner et al, 1979; Kiniry, personal comm., 2001; estimated) (Krner et al, 1979; Martin et al, 1976; Jensen et al, 1990; estimated) (Monteith, 1965; Kiniry, personal comm., 2001; Martin et al, 1976) (Monteith, 1965; Kiniry, personal comm., 2001; Martin et al, 1976) (Krner et al, 1979; Martin et al, 1976; Kiniry and Williams, 1994) (Krner et al, 1979; Kiniry and Williams, 1994) (Krner et al, 1979; Martin et al, 1976; Maynard and Hochmuth, 1997; Kiniry and Williams, 1994)

Little bluestem Alamo switchgrass Indiangrass Alfalfa Sweetclover

.0055 .0055 .0055 .0100 .0055

1.0 2.5 1.0 0.9 1.5

2.0 2.2 2.0 3.0 2.4

.003 .003 .003 .01 .003

Red clover Alsike clover Soybean Cowpeas Mung bean Lima beans Lentils Peanut Field peas Garden or canning peas

.0065 .0055 .0071 .0055 .0055 .0055 .0055 .0063 .0055 .0055

0.75 0.9 0.8 1.2 1.5 0.6 0.55 0.5 1.2 0.6

1.5 2.0 1.7 2.0 2.0 2.0 1.2 2.0 1.2 1.2

.003 .003 .20 .03 .20 .20 .20 .20 .01 .20

Sesbania Flax Upland cotton (harvested with stripper) Upland cotton (harvested with picker) Tobacco

.0055 .0055 .0091 .0091 .0048

2.0 1.2 1.0 1.0 1.8

2.0 1.5 2.5 2.5 2.0

.20 .20 .20 .20 .20

Sugarbeet Potato

.0071 .0050

1.2 0.6

2.0 0.6

.20 .20

APPENDIX A: DATABASES Common Name

Sweetpotato Carrot Onion Sunflower Spring canola-Polish

377

Plant Code SPOT CRRT ONIO SUNF CANP CANA ASPR BROC CABG CAUF

g l,mx
.0065 .0065 .0065 .0077 .0065

hc,mx
0.8 0.3 0.5 2.5 0.9

zroot,mx
2.0 1.2 0.6 2.0 0.9

CUSLE,mn
.05 .20 .20 .20 .20

Reference
(Krner et al, 1979; estimated; Maynard and Hochmuth, 1997) (Krner et al, 1979; Kiniry and Williams, 1994; Maynard and Hochmuth, 1997) (Krner et al, 1979; Kiniry and Williams, 1994; Maynard and Hochmuth, 1997) (Krner et al, 1979; Kiniry, personal comm., 2001) (Krner et al, 1979; estimated; Kiniry et al, 1995) (Krner et al, 1979; estimated; Kiniry et al, 1995) (Krner et al, 1979; Kiniry, personal comm., 2001; Maynard and Hochmuth, 1997; Kiniry and Williams, 1994) (Krner et al, 1979; Kiniry, personal comm., 2001; Maynard and Hochmuth, 1997; Kiniry and Williams, 1994) (Krner et al, 1979; Kiniry, personal comm., 2001; Maynard and Hochmuth, 1997; Kiniry and Williams, 1994) (Krner et al, 1979; Kiniry, personal comm., 2001; Maynard and Hochmuth, 1997; Kiniry and Williams, 1994) (Krner et al, 1979; Kiniry, personal comm., 2001; Maynard and Hochmuth, 1997; Kiniry and Williams, 1994) (Krner et al, 1979; Kiniry and Williams, 1994; Maynard and Hochmuth, 1997) (Krner et al, 1979; Kiniry, personal comm., 2001; Maynard and Hochmuth, 1997; Kiniry and Williams, 1994) (Krner et al, 1979; Kiniry and Williams, 1994; Maynard and Hochmuth, 1997) (Krner et al, 1979; Kiniry, personal comm., 2001; Maynard and Hochmuth, 1997) (Krner et al, 1979; Kiniry, personal comm., 2001; Maynard and Hochmuth, 1997; Kiniry and Williams, 1994) (Krner et al, 1979; Kiniry, personal comm., 2001; Maynard and Hochmuth, 1997; Kiniry and Williams, 1994) (Krner et al, 1979; Kiniry, personal comm., 2001; Maynard and Hochmuth, 1997; Kiniry and Williams, 1994) (Krner et al, 1979; Kiniry, personal comm., 2001; Maynard and Hochmuth, 1997; Kiniry and Williams, 1994) (Krner et al, 1979; Kiniry, personal comm., 2001; Maynard and Hochmuth, 1997; Kiniry and Williams, 1994) (Krner et al, 1979; Kiniry, personal comm., 2001; Maynard and Hochmuth, 1997; Kiniry and Williams, 1994)

Spring canola-Argentine Asparagus

.0065 .0065

1.3 0.5

1.4 2.0

.20 .20

Broccoli

.0065

0.5

0.6

.20

Cabbage

.0065

0.5

0.6

.20

Cauliflower

.0065

0.5

0.6

.20

Celery

CELR LETT SPIN GRBN CUCM EGGP CANT HMEL WMEL PEPR

.0065

0.5

0.6

.20

Head lettuce Spinach

.0025 .0065

0.2 0.5

0.6 0.6

.01 .20

Green beans Cucumber

.0077 .0033

0.6 0.5

1.2 1.2

.20 .03

Eggplant

.0065

0.5

1.2

.03

Cantaloupe

.0065

0.5

1.2

.03

Honeydew melon

.0065

0.5

1.2

.03

Watermelon

.0065

0.5

2.0

.03

Bell pepper

.0053

0.5

1.2

.03

Strawberry

STRW

.0065

0.5

0.6

.03

378

SWAT USERS MANUAL, VERSION 2000 Plant Code TOMA APPL PINE OAK POPL MESQ

Common Name
Tomato

g l,mx
.0077

hc,mx
0.5

zroot,mx
2.0

CUSLE,mn
.03

Reference
(Krner et al, 1979; Kiniry, personal comm., 2001; Maynard and Hochmuth, 1997; Kiniry and Williams, 1994) (Krner et al, 1979; estimated; Jensen et al, 1990) (Krner et al, 1979; Kiniry, personal comm., 2001) (Krner et al, 1979; Kiniry, personal comm., 2001) (Krner et al, 1979; Kiniry, personal comm., 2001) (Krner et al, 1979; Kiniry, personal comm., 2001)

Apple Pine Oak Poplar

.0071 .0019 .0020 .0036

3.5 10.0 6.0 7.5

2.0 3.5 3.5 3.5

.001 .001 .001 .001

Honey mesquite

.0036

6.0

3.5

.001

A.1.7 PLANT NUTRIENT CONTENT

In order to calculate the plant nutrient demand throughout a plants growing cycle, SWAT needs to know the fraction of nutrient in the total plant biomass (on a dry weight basis) at different stages of crop growth. Six variables in the plant database provide this information: BN(1), BN(2), BN(3), BP(1), BP(2), and BP(3). Plant samples are analyzed for nitrogen and phosphorus content at three times during the growing season: shortly after emergence, near the middle of the season, and at maturity. The plant samples can be sent to testing laboratories to obtain the fraction of nitrogen and phosphorus in the biomass. Ideally, the plant samples tested for nutrient content should include the roots as well as the aboveground biomass. Differences in partitioning of nutrients to roots and shoots can cause erroneous conclusions when comparing productivity among species if only the aboveground biomass is measured. The fractions of nitrogen and phosphorus for the plants included in the default database are listed in Table A-7.

Table A-7: Nutrient parameters for plants included in plant growth database. Plant Common Name Code frN,1 frN,2 frN,3 frP,1 frP,2 Corn .0470 .0177 .0138 .0048 .0018 CORN Corn silage .0470 .0177 .0138 .0048 .0018 CSIL .0470 .0177 .0138 .0048 .0018 Sweet corn SCRN .0200 .0100 .0070 .0014 .0010 Eastern gamagrass EGAM

frP,3
.0014 .0014 .0014 .0007

Reference
(Kiniry et al., 1995) (Kiniry et al., 1995) (Kiniry and Williams, 1994) (Kiniry, personal communication, 2001)

APPENDIX A: DATABASES

379

Common Name
Grain sorghum Sorghum hay Johnsongrass Sugarcane Spring wheat Winter wheat Durum wheat Rye Spring barley Oats Rice Pearl millet Timothy Smooth bromegrass Meadow bromegrass Tall fescue Kentucky bluegrass Bermudagrass Crested wheatgrass Western wheatgrass Slender wheatgrass Italian (annual) ryegrass Russian wildrye Altai wildrye Sideoats grama Big bluestem Little bluestem Alamo switchgrass Indiangrass Alfalfa Sweetclover Red clover Alsike clover Soybean Cowpeas Mung bean Lima beans Lentils Peanut Field peas Garden or canning peas Sesbania Flax

Plant Code GRSG SGHY JHGR SUGC SWHT WWHT DWHT RYE BARL OATS RICE PMIL TIMO BROS BROM FESC BLUG BERM CWGR WWGR SWGR RYEG RYER RYEA SIDE BBLS LBLS SWCH INDN ALFA CLVS CLVR CLVA SOYB CWPS MUNG LIMA LENT PNUT FPEA PEAS SESB FLAX

frN,1
.0440 .0440 .0440 .0100 .0600 .0663 .0600 .0600 .0590 .0600 .0500 .0440 .0314 .0400 .0400 .0560 .0200 .0600 .0300 .0300 .0300 .0660 .0226 .0226 .0200 .0200 .0200 .0350 .0200 .0417 .0650 .0650 .0600 .0524 .0600 .0524 .0040 .0440 .0524 .0515 .0040 .0500 .0482

frN,2
.0164 .0164 .0164 .0040 .0231 .0255 .0231 .0231 .0226 .0231 .0200 .0300 .0137 .0240 .0240 .0210 .0100 .0231 .0200 .0200 .0200 .0254 .0180 .0180 .0100 .0120 .0120 .0150 .0120 .0290 .0280 .0280 .0280 .0265 .0231 .0265 .0030 .0164 .0265 .0335 .0030 .0200 .0294

frN,3
.0128 .0128 .0128 .0025 .0134 .0148 .0130 .0130 .0131 .0134 .0100 .0100 .0103 .0160 .0160 .0120 .0060 .0134 .0120 .0120 .0120 .0147 .0140 .0140 .0060 .0050 .0050 .0038 .0050 .0200 .0243 .0243 .0240 .0258 .0134 .0258 .0015 .0128 .0258 .0296 .0015 .0150 .0263

frP,1
.0060 .0060 .0060 .0075 .0084 .0053 .0084 .0084 .0057 .0084 .0060 .0060 .0038 .0028 .0028 .0099 .0014 .0084 .0020 .0020 .0020 .0105 .0040 .0040 .0014 .0014 .0014 .0014 .0014 .0035 .0060 .0060 .0060 .0074 .0049 .0074 .0035 .0074 .0074 .0033 .0030 .0074 .0049

frP,2
.0022 .0022 .0022 .0030 .0032 .0020 .0032 .0032 .0022 .0032 .0030 .0022 .0025 .0017 .0017 .0022 .0010 .0032 .0015 .0015 .0015 .0040 .0040 .0040 .0010 .0010 .0010 .0010 .0010 .0028 .0024 .0024 .0025 .0037 .0019 .0037 .0030 .0037 .0037 .0019 .0020 .0037 .0024

frP,3
.0018 .0018 .0018 .0019 .0019 .0012 .0019 .0019 .0013 .0019 .0018 .0012 .0019 .0011 .0011 .0019 .0007 .0019 .0013 .0013 .0013 .0024 .0024 .0024 .0007 .0007 .0007 .0007 .0007 .0020 .0024 .0024 .0025 .0035 .0011 .0035 .0015 .0023 .0035 .0014 .0015 .0035 .0023

Reference
(Kiniry, personal communication, 2001) (Kiniry, personal communication, 2001) (Kiniry et al., 1992a) (Kiniry and Williams, 1994) (Kiniry et al., 1992a) (Kiniry et al., 1995) estimated estimated (Kiniry et al., 1995) (Kiniry, personal communication, 2001) estimated estimated estimated (Kiniry et al., 1995) (Kiniry et al., 1995) estimated (Kiniry, personal communication, 2001) (Kiniry, personal communication, 2001) (Kiniry et al., 1995) (Kiniry et al., 1995) estimated estimated (Kiniry et al., 1995) (Kiniry et al., 1995) (Kiniry, personal communication, 2001) (Kiniry, personal communication, 2001) (Kiniry, personal communication, 2001) (Kiniry et al., 1996) (Kiniry, personal communication, 2001) (Kiniry, personal communication, 2001) estimated estimated estimated (Kiniry et al., 1992a) estimated estimated (Kiniry and Williams, 1994) estimated estimated estimated (Kiniry and Williams, 1994) estimated estimated

380 Common Name

Upland cotton (harvested with stripper) Upland cotton (harvested with picker) Tobacco Sugarbeet Potato Sweetpotato Carrot Onion Sunflower Spring canola-Polish Spring canola-Argentine Asparagus Broccoli Cabbage Cauliflower Celery Head lettuce Spinach Green beans Cucumber Eggplant Cantaloupe Honeydew melon Watermelon Bell pepper Strawberry Tomato Apple Pine Oak Poplar Honey mesquite

SWAT USERS MANUAL, VERSION 2000 Plant Code COTS COTP TOBC SGBT POTA SPOT CRRT ONIO SUNF CANP CANA ASPR BROC CABG CAUF CELR LETT SPIN GRBN CUCM EGGP CANT HMEL WMEL PEPR STRW TOMA APPL PINE OAK POPL MESQ frN,1
.0580 .0580 .0470 .0550 .0550 .0450 .0550 .0400 .0500 .0440 .0440 .0620 .0620 .0620 .0620 .0620 .0360 .0620 .0040 .0663 .0663 .0663 .0070 .0663 .0600 .0663 .0663 .0060 .0060 .0060 .0060 .0200

frN,2
.0192 .0192 .0177 .0200 .0200 .0160 .0075 .0300 .0230 .0164 .0164 .0500 .0090 .0070 .0070 .0150 .0250 .0400 .0030 .0075 .0255 .0255 .0040 .0075 .0350 .0255 .0300 .0020 .0020 .0020 .0020 .0100

frN,3
.0177 .0177 .0138 .0120 .0120 .0090 .0012 .0020 .0146 .0128 .0128 .0400 .0070 .0040 .0040 .0100 .0210 .0300 .0015 .0048 .0075 .0148 .0020 .0048 .0250 .0148 .0250 .0015 .0015 .0015 .0015 .0080

frP,1
.0081 .0081 .0048 .0060 .0060 .0045 .0060 .0021 .0063 .0074 .0074 .0050 .0050 .0050 .0050 .0060 .0084 .0050 .0040 .0053 .0053 .0053 .0026 .0053 .0053 .0053 .0053 .0007 .0007 .0007 .0007 .0007

frP,2
.0027 .0027 .0018 .0025 .0025 .0019 .0030 .0020 .0029 .0037 .0037 .0040 .0040 .0035 .0035 .0050 .0032 .0040 .0035 .0025 .0020 .0020 .0020 .0025 .0020 .0020 .0035 .0004 .0004 .0004 .0004 .0004

frP,3
.0025 .0025 .0014 .0019 .0019 .0015 .0020 .0019 .0023 .0023 .0023 .0020 .0030 .0020 .0020 .0030 .0019 .0035 .0015 .0012 .0015 .0012 .0017 .0012 .0012 .0012 .0025 .0003 .0003 .0003 .0003 .0003 estimated estimated

Reference

(Kiniry and Williams, 1994) (Kiniry and Williams, 1994) (Kiniry and Williams, 1994) estimated (Kiniry and Williams, 1994) (Kiniry and Williams, 1994) (Kiniry, personal communication, 2001) (Kiniry et al., 1995) (Kiniry et al., 1995) (Kiniry and Williams, 1994) (Kiniry and Williams, 1994) (Kiniry and Williams, 1994) (Kiniry and Williams, 1994) (Kiniry and Williams, 1994) (Kiniry and Williams, 1994) (Kiniry and Williams, 1994) (Kiniry and Williams, 1994) (Kiniry and Williams, 1994) (Kiniry and Williams, 1994) (Kiniry and Williams, 1994) (Kiniry and Williams, 1994) (Kiniry and Williams, 1994) (Kiniry and Williams, 1994) (Kiniry and Williams, 1994) (Kiniry and Williams, 1994) estimated (Kiniry, personal communication, 2001) (Kiniry, personal communication, 2001) (Kiniry, personal communication, 2001) (Kiniry, personal communication, 2001)

A.1.8 HARVEST
Harvest operations are performed on agricultural crops where the yield is sold for a profit. Four variables in the database provide information used by the model to harvest a crop: HVSTI, WSYF, CNYLD, and CPYLD. The harvest index defines the fraction of the aboveground biomass that is removed in a harvest operation. This value defines the fraction of plant biomass

APPENDIX A: DATABASES

381

that is lost from the system and unavailable for conversion to residue and subsequent decomposition. For crops where the harvested portion of the plant is aboveground, the harvest index is always a fraction less than 1. For crops where the harvested portion is belowground, the harvest index may be greater than 1. Two harvest indices are provided in the database, the harvest index for optimal growing conditions (HVSTI) and the harvest index under highly stressed growing conditions (WSYF). To determine the harvest index, the plant biomass removed during the harvest operation is dried at least 2 days at 65C and weighed. The total aboveground plant biomass in the field should also be dried and weighed. The harvest index is then calculated by dividing the weight of the harvested portion of the plant biomass by the weight of the total aboveground plant biomass. Plants will need to be grown in two different plots where optimal climatic conditions and stressed conditions are produced to obtain values for both harvest indices. In addition to the amount of plant biomass removed in the yield, SWAT needs to know the amount of nitrogen and phosphorus removed in the yield. The harvested portion of the plant biomass is sent to a testing laboratory to determine the fraction of nitrogen and phosphorus in the biomass. Table A-8 lists values for the optimal harvest index (HIopt), the minimum harvest index (HImin), the fraction of nitrogen in the harvested portion of biomass (frN,yld), and the fraction of phosphorus in the harvested portion of biomass (frP,yld).

Table A-8: Harvest parameters for plants included in the plant growth database. Plant Common Name Code HIopt HImin frN,yld frP,yld Reference Corn 0.50 0.30 .0140 .0016 (Kiniry, personal communication, 2001; CORN
Corn silage Sweet corn Eastern gamagrass Grain sorghum

CSIL SCRN EGAM GRSG

0.90 0.50 0.90 0.45

0.90 0.30 0.90 0.25

.0140 .0214 .0160 .0199

.0016 .0037 .0022 .0032

Kiniry et al, 1995) (Kiniry, personal communication, 2001; Kiniry et al, 1995) (Kiniry, personal communication, 2001; Nutrition Monitoring Division, 1984a) (Kiniry, personal communication, 2001) (Kiniry and Bockholt, 1998; Nutrition Monitoring Division, 1984b)

382 Common Name

Sorghum hay Johnsongrass Sugarcane Spring wheat Winter wheat Durum wheat Rye Spring barley Oats Rice

SWAT USERS MANUAL, VERSION 2000 Plant Code SGHY JHGR SUGC SWHT WWHT DWHT RYE BARL OATS RICE PMIL TIMO BROS BROM FESC BLUG BERM CWGR WWGR SWGR RYEG RYER RYEA SIDE BBLS LBLS SWCH INDN ALFA CLVS CLVR HIopt
0.90 0.90 0.50 0.42 0.40 0.40 0.40 0.54 0.42 0.50

HImin
0.90 0.90 0.01 0.20 0.20 0.20 0.20 0.20 0.175 0.25

frN,yld
.0199 .0200 .0000 .0234 .0250 .0263 .0284 .0210 .0316 .0136

frP,yld
.0032 .0028 .0000 .0033 .0022 .0057 .0042 .0017 .0057 .0013

Reference
(Kiniry, personal communication, 2001; Nutrition Monitoring Division, 1984b) (Kiniry, personal communication, 2001; Kiniry et al, 1992a) (Kiniry and Williams, 1994) (Kinry et al, 1995; Kiniry et al, 1992a) (Kiniry et al, 1995) (Kiniry, personal communication, 2001; Nutrition Monitoring Division, 1984b) (Kiniry, personal communication, 2001; Nutrition Monitoring Division, 1984b) (Kiniry et al, 1995) (Kiniry, personal communication, 2001; Nutrition Monitoring Division, 1984b) (Kiniry, personal communication, 2001; Nutrition Monitoring Division, 1984b) (Kiniry, personal communication, 2001; estimated) (Kiniry, personal communication, 2001; estimated) (Kiniry, personal communication, 2001; Kiniry et al, 1995) (Kiniry, personal communication, 2001; Kiniry et al, 1995) (Kiniry, personal communication, 2001; estimated) (Kiniry, personal communication, 2001) (Kiniry, personal communication, 2001) (Kiniry, personal communication, 2001; Kiniry et al, 1995) (Kiniry, personal communication, 2001; Kiniry et al, 1995) (Kiniry, personal communication, 2001; estimated) (Kiniry, personal communication, 2001; estimated) (Kiniry, personal communication, 2001; Kiniry et al, 1995) (Kiniry, personal communication, 2001; Kiniry et al, 1995) (Kiniry, personal communication, 2001) (Kiniry, personal communication, 2001) (Kiniry, personal communication, 2001) (Kiniry et al, 1996) (Kiniry, personal communication, 2001) (Kiniry, personal communication, 2001) (Kiniry, personal communication, 2001; estimated) (Kiniry, personal communication, 2001; estimated)

Pearl millet Timothy Smooth bromegrass Meadow bromegrass Tall fescue

0.25 0.90 0.90 0.90 0.90

0.10 0.90 0.90 0.90 0.90

.0200 .0234 .0234 .0234 .0234

.0028 .0033 .0033 .0033 .0033

Kentucky bluegrass Bermudagrass Crested wheatgrass Western wheatgrass Slender wheatgrass

0.90 0.90 0.90 0.90 0.90

0.90 0.90 0.90 0.90 0.90

.0160 .0234 .0500 .0500 .0500

.0022 .0033 .0040 .0040 .0040

Italian (annual) ryegrass Russian wildrye Altai wildrye Sideoats grama Big bluestem Little bluestem Alamo switchgrass Indiangrass Alfalfa Sweetclover

0.90 0.90 0.90 0.90 0.90 0.90 0.90 0.90 0.90 0.90

0.90 0.90 0.90 0.90 0.90 0.90 0.90 0.90 0.90 0.90

.0220 .0230 .0230 .0160 .0160 .0160 .0160 .0160 .0250 .0650

.0028 .0037 .0037 .0022 .0022 .0022 .0022 .0022 .0035 .0040

Red clover

0.90

0.90

.0650

.0040

APPENDIX A: DATABASES

383

Common Name
Alsike clover Soybean Cowpeas Mung bean Lima beans

Plant Code CLVA SOYB CWPS MUNG LIMA LENT PNUT FPEA PEAS SESB FLAX COTS COTP TOBC SGBT POTA SPOT CRRT ONIO SUNF CANP CANA ASPR BROC CABG CAUF CELR LETT SPIN

HIopt
0.90 0.31 0.42 0.31 0.30

HImin
0.90 0.01 0.05 0.01 0.22

frN,yld
.0600 .0650 .0427 .0420 .0368

frP,yld
.0040 .0091 .0048 .0040 .0046

Reference
(Kiniry, personal communication, 2001; estimated) (Kiniry et al, 1992a) (estimated; Nutrition Monitoring Division, 1984c) (estimated; Nutrition Monitoring Division, 1984c) (Kiniry and Williams, 1994; Nutrition Monitoring Division, 1984a) (estimated; Nutrition Monitoring Division, 1984c) (estimated; Nutrition Monitoring Division, 1984c) estimated (Kiniry and Williams, 1994; Nutrition Monitoring Division, 1984a) estimated estimated (Kiniry, personal communication, 2001; estimated) (Kiniry, personal communication, 2001; estimated) (Kiniry and Williams, 1994) (Kiniry and Williams, 1994) (Kiniry and Williams, 1994; Nutrition Monitoring Division, 1984a) (estimated; Nutrition Monitoring Division, 1984a) (Kiniry and Williams, 1994; Nutrition Monitoring Division, 1984a) (Kiniry and Williams, 1994; Nutrition Monitoring Division, 1984a) (Kiniry et al, 1992b; Nutrition Monitoring Division, 1984d) (Kiniry et al, 1995) (Kiniry et al, 1995) (Kiniry and Williams, 1994; Nutrition Monitoring Division, 1984a) (Kiniry and Williams, 1994; Nutrition Monitoring Division, 1984a) (Kiniry and Williams, 1994; Nutrition Monitoring Division, 1984a) (Kiniry and Williams, 1994; Nutrition Monitoring Division, 1984a) (Kiniry and Williams, 1994; Nutrition Monitoring Division, 1984a) (Kiniry and Williams, 1994; Nutrition Monitoring Division, 1984a) (Kiniry and Williams, 1994; Nutrition Monitoring Division, 1984a)

Lentils Peanut Field peas Garden or canning peas Sesbania Flax Upland cotton (harvested with stripper) Upland cotton (harvested with picker) Tobacco Sugarbeet Potato Sweetpotato Carrot Onion Sunflower

0.61 0.40 0.45 0.30 0.31 0.54 0.50 0.40 0.55 2.00 0.95 0.60 1.12 1.25 0.30

0.01 0.30 0.10 0.22 0.01 0.40 0.40 0.30 0.55 1.10 0.95 0.40 0.90 0.95 0.18

.0506 .0505 .0370 .0410 .0650 .0400 .0140 .0190 .0140 .0130 .0246 .0097 .0135 .0206 .0454

.0051 .0040 .0021 .0051 .0091 .0033 .0020 .0029 .0016 .0020 .0023 .0010 .0036 .0032 .0074

Spring canola-Polish Spring canola-Argentine Asparagus Broccoli Cabbage

0.23 0.30 0.80 0.80 0.80

0.01 0.01 0.95 0.95 0.95

.0380 .0380 .0630 .0512 .0259

.0079 .0079 .0067 .0071 .0031

Cauliflower Celery Head lettuce Spinach

0.80 0.80 0.80 0.95

0.95 0.95 0.01 0.95

.0411 .0199 .0393 .0543

.0059 .0049 .0049 .0058

384 Common Name

Green beans Cucumber Eggplant Cantaloupe Honeydew melon

SWAT USERS MANUAL, VERSION 2000 Plant Code GRBN CUCM EGGP CANT HMEL WMEL PEPR STRW TOMA APPL PINE OAK POPL MESQ HIopt
0.10 0.27 0.59 0.50 0.55

HImin
0.10 0.25 0.25 0.25 0.25

frN,yld
.0299 .0219 .0218 .0138 .0071

frP,yld
.0039 .0043 .0041 .0017 .0010

Reference
(Kiniry and Williams, 1994; Nutrition Monitoring Division, 1984a) (Kiniry and Williams, 1994; Nutrition Monitoring Division, 1984a) (Kiniry and Williams, 1994; Nutrition Monitoring Division, 1984a) (Kiniry and Williams, 1994; Consumer Nutrition Center, 1982) (Kiniry and Williams, 1994; Consumer Nutrition Center, 1982) (Kiniry and Williams, 1994; Consumer Nutrition Center, 1982) (Kiniry and Williams, 1994; Nutrition Monitoring Division, 1984a) (Kiniry and Williams, 1994; Consumer Nutrition Center, 1982) (Kiniry and Williams, 1994; Nutrition Monitoring Division, 1984a) (estimated; Consumer Nutrition Center, 1982) (Kiniry, personal communication, 2001) (Kiniry, personal communication, 2001) (Kiniry, personal communication, 2001) (Kiniry, personal communication, 2001)

Watermelon Bell pepper Strawberry Tomato Apple Pine Oak Poplar Honey mesquite

0.50 0.60 0.45 0.33 0.10 0.76 0.76 0.76 0.05

0.25 0.25 0.25 0.15 0.05 0.60 0.01 0.01 0.01

.0117 .0188 .0116 .0235 .0019 .0015 .0015 .0015 .0015

.0011 .0030 .0023 .0048 .0004 .0003 .0003 .0003 .0003

A.1.9 USLE C FACTOR

The USLE C factor is the ratio of soil loss from land cropped under specified conditions to the corresponding loss from clean-tilled, continuous fallow. This factor measures the combined effect of all the interrelated cover and management variables. SWAT calculates the actual C factor based on the amount of soil cover and the minimum C factor defined for the plant/land cover. The minimum C factor quantifies the maximum decrease in erosion possible for the plant/land cover. Because the USLE C factor is influenced by management, this variable may be adjusted by the user to reflect management conditions in the watershed of interest. The minimum C factor can be estimated from a known average annual C factor using the following equation (Arnold and Williams, 1995):
CUSLE ,mn = 1.463 ln[CUSLE ,aa ] + 0.1034

APPENDIX A: DATABASES

385

where CUSLE,mn is the minimum C factor for the land cover and CUSLE,aa is the average annual C factor for the land cover. The minimum C factor for plants in the database are listed in Table A-6.

A.1.10 RESIDUE DECOMPOSITION

The plant residue decomposition coefficient is the fraction of residue that will decompose in a day assuming optimal moisture, temperature, C:N ratio, and C:P ratio. This variable was originally in the basin input file (.bsn), but was added to the crop database so that users could vary decomposition by land cover. A default value of 0.05 is used for all plant species in the database.

386

SWAT USERS MANUAL, VERSION 2000

A.2 TILLAGE DATABASE

The tillage database contains information needed by SWAT to simulate the redistribution of nutrients and pesticide that occurs in a tillage operation. Table A-9 lists all the default tillage implements. This list was summarized from a farm machinery database maintained by the USDA Economic Research Service. Depth of tillage for each implement was also obtained from the USDA Economic Research Service. The fraction of residue mixed into the soil was estimated for each implement from a Residue Scorecard provided by NACDs (National Association of Conservation Districts) Conservation Technology Information Center.
Table A-9: Implements included in the tillage database. Implement Tillage Code Duckfoot Cultivator DUCKFTC Field Cultivator FLDCULT Furrow-out Cultivator FUROWOUT Marker (Cultivator) MARKER Rolling Cultivator ROLLCULT Row Cultivator ROWCULT Discovator DISCOVAT Leveler LEVELER Harrow (Tines) HARROW Culti-mulch Roller CULMULCH Culti-packer Pulverizer CULPKPUL Land Plane-Leveler LANDLEVL Landall, Do-All LANDALL Laser Planer LASRPLAN Levee-Plow-Disc LEVPLDIS Float FLOAT Field Conditioner (Scratcher) FLDCDSCR Lister (Middle-Buster) LISTRMID Roller Groover ROLLGROV Roller Packer Attachment ROLPKRAT Roller Packer Flat Roller ROLPKRFT Sand-Fighter SANDFIGT Seedbed Roller SEEDROLL Crust Buster CRUSTBST Roller Harrow ROLLHRRW Triple K TRIPLE K Finishing Harrow FINHARRW Flex-Tine Harrow CL FLEXHARW Powered Spike Tooth Harrow SPIKETTH Spike Tooth Harrow SPIKTOTH Springtooth Harrow SPRGTOTH Soil Finisher SOILFINS Mixing Depth
100 mm 100 mm 25 mm 100 mm 25 mm 25 mm 25 mm 25 mm 25 mm 25 mm 40 mm 75 mm 150 mm 150 mm 25 mm 60 mm 60 mm 40 mm 60 mm 40 mm 40 mm 100 mm 100 mm 60 mm 60 mm 100 mm 100 mm 25 mm 75 mm 25 mm 25 mm 75 mm

Mixing Efficiency
0.55 0.30 0.75 0.45 0.50 0.25 0.50 0.50 0.20 0.25 0.35 0.50 0.30 0.30 0.75 0.10 0.10 0.15 0.25 0.05 0.35 0.70 0.70 0.10 0.40 0.40 0.55 0.20 0.40 0.25 0.35 0.55

APPENDIX A: DATABASES

387

Implement
Rotary Hoe Roterra Roto-Tiller Rotovator-Bedder Rowbuck Ripper Middle Buster Rod Weeder Rubber-Wheel Weed Puller Multi-Weeder Moldboard Plow Reg Chisel Plow Coulter-Chisel Disk Plow Stubble-mulch Plow Subsoil Chisel Plow Row Conditioner Hipper Rice Roller Paraplow Subsoiler-Bedder Hip-Rip Deep Ripper-Subsoiler V-Ripper Bed Roller Bedder (Disk) Bedder Disk-Hipper Bedder Disk-Row Bedder Shaper Disk Border Maker Disk Chisel (Mulch Tiller) Offset Disk-Heavy Duty Offset Disk-Light Duty One-Way (Disk Tiller) Tandem Disk Plow Tandem Disk Reg Single Disk Power Mulcher Blade 10 ft Furrow Diker Beet Cultivator Cultiweeder Packer

Tillage Code ROTHOE ROTERRA ROTOTILL ROTBEDDR ROWBUCK RIPPER MIDBST1R RODWEEDR RUBWHWPL MULTIWDR MLDBOARD CHISPLOW CCHPLOW DISKPLOW STUBMLCH SUBCHPLW ROWCOND HIPPER RICEROLL PARAPLOW SBEDHIPR RIPRSUBS VRIPPER BEDROLLR BEDDER D BEDDHIPR BEDDKROW BEDDER S DSKBRMKR DKCHMTIL OFFSETHV OFFSETLT ONE-WAYT TANDEMPL TANDEMRG SINGLDIS PWRMULCH BLADE 10 FURWDIKE BEETCULT CLTIWEED PACKER

Mixing Depth
5 mm 5 mm 5 mm 100 mm 100 mm 350 mm 100 mm 25 mm 5 mm 25 mm 150 mm 150 mm 150 mm 100 mm 75 mm 350 mm 25 mm 100 mm 50 mm 350 mm 350 mm 350 mm 350 mm 50 mm 150 mm 150 mm 100 mm 150 mm 150 mm 150 mm 100 mm 100 mm 100 mm 75 mm 75 mm 100 mm 50 mm 75 mm 100 mm 25 mm 100 mm 40 mm

Mixing Efficiency
0.10 0.80 0.80 0.80 0.70 0.25 0.70 0.30 0.35 0.30 0.95 0.30 0.50 0.85 0.15 0.45 0.50 0.50 0.10 0.15 0.70 0.25 0.25 0.25 0.55 0.65 0.85 0.55 0.55 0.55 0.70 0.55 0.60 0.55 0.60 0.45 0.70 0.25 0.70 0.25 0.30 0.35

In addition to information about specific implements, the tillage database includes default information for the different crop residue management categories. Table A-10 summarizes the information in the database on the different residue management categories.

388

SWAT USERS MANUAL, VERSION 2000 Mixing Efficiency

0.95 0.50 0.25 0.05

Table A-10: Generic management scenarios included in the tillage database. Implement Tillage Code Mixing Depth Generic Fall Plowing Operation 150 mm FALLPLOW Generic Spring Plowing Operation 125 mm SPRGPLOW 100 mm Generic Conservation Tillage CONSTILL 25 mm Generic No-Till Mixing ZEROTILL

ASAE (1998b) categorizes tillage implements into five different categoriesprimary tillage, secondary tillage, cultivating tillage, combination primary tillage, and combination secondary tillage. The definitions for the categories are (ASAE, 1998b): Primary tillage: the implements displace and shatter soil to reduce soil strength and bury or mix plant materials, pesticides, and fertilizers in the tillage layer. This type of tillage is more aggressive, deeper, and leaves a rougher soil surface relative to secondary tillage. Examples include plowsmoldboard, chisel, disk, bedder; moldboard listers; disk bedders; subsoilers; disk harrowsoffset disk, heavy tandem disk; and powered rotary tillers. Secondary tillage: the implements till the soil to a shallower depth than primary tillage implements, provide additional pulverization, mix pesticides and fertilizers into the soil, level and firm the soil, close air pockets, and eradicate weeds. Seedbed preparation is the final secondary tillage operation. Examples include harrowsdisk, spring, spike, coil, tine-tooth, knife, packer, ridger, leveler, rotary ground driven; field or field conditioner cultivators; rod weeders; rollers; powered rotary tillers; bed shapers; and rotary hoes. Cultivating tillage: the implements perform shallow post-plant tillage to aid the crop by loosening the soil and/or by mechanical eradication of undesired vegetation. Examples include row crop cultivatorsrotary ground-driven, spring tooth, shank tooth; rotary hoes; and rotary tillers. Combination primary tillage: the implements perform primary tillage functions and utilize two or more dissimilar tillage components as integral parts of the implement. Combination secondary tillage: the implements perform secondary tillage functions and utilize two or more dissimilar tillage components as integral parts of the implement. ASAE (1998b) provides detailed descriptions and illustrations for the major implements. These are very helpful for those who are not familiar with farm implements.

APPENDIX A: DATABASES

389

A.3 PESTICIDE DATABASE

The pesticide database file (pest.dat) summarizes pesticide attribute information for various pesticides. The pesticide data included in the database was originally compiled for the GLEAMS model in the early nineties (Knisel, 1993). The following table lists the pesticides included in the pesticide database.
Table A-11: SWAT Pesticide Database Washoff Frac. 0.40 0.95 0.45 0.65 0.05 0.90 0.20 0.95 0.95 0.05 0.95 0.80 0.95 0.60 0.95 0.40 0.40 0.50 0.90 0.95 0.40 0.65 0.65 0.20 0.95 0.95 0.95 0.20 0.95 0.65 0.60 0.95 0.30 Half-Life Foliar Soil (days) 5.0 10.0 5.0 5.0 10.0 7.0 5.0 7.0 4.0 2.0 0.1 30.0 7.0 5.0 5.0 5.0 10.0 30.0 30.0 30.0 8.0 18.0 18.0 15.0 3.0 30.0 2.0 10.0 15.0 9.0 2.0 4.0 8.0 20.0 21.0 60.0 30.0 20.0 7.0 9.0 14.0 7.0 28.0 0.1 120.0 14.0 10.0 14.0 30.0 21.0 120.0 90.0 100.0 35.0 35.0 35.0 60.0 7.0 100.0 30.0 30.0 30.0 14.0 20.0 7.0 26.0 Water Solubility (mg/L) 2.5 660000 33 0.001 13 100000 0.8 231000 100000 0.1 120000 9500 900000 100 360000 0.004 105 650 11000 1000000 0.002 1370 875 0.31 550000 817000 1000000 0.1 1000000 400000 2300000 1370000 71.5

Trade Name 2,4,5-TP 2 Plus 2 Aatrex Abate Acaraben Accelerate Acclaim Alanap Alar Aldrin Aliette Ally Amiben Amid-Thin W Amitrol T Ammo Antor A-Rest Arsenal Arsonate Asana Assert (m) Assert (p) Assure Asulox Avenge Azodrin Balan Banol Banvel Basagran Basta Bayleton

Common Name Silvex Mecoprop Amine Atrazine Temephos Chlorobenzilate Endothall Salt Fenoxaprop-Ethyl Naptalam Sodium Salt Daminozide Aldrin Fosetyl-Aluminum Metsulfuron-Methyl Chloramben Salts NAA Amide Amitrole Cypermethrin Diethatyl-Ethyl Ancymidol Imazapyr Acid MSMA Esfenvalerate Imazamethabenz-m Imazamethabenz-p Quizalofop-Ethyl Asulam Sodium Salt Difenzoquat Monocrotophos Benefin Propamocarb Dicamba Bentazon Glufosinate Ammonia Triadimefon

Koc (ml/g) 2600 20 100 100000 2000 20 9490 20 10 300 20 35 15 100 100 100000 1400 120 100 10000 5300 66 35 510 40 54500 1 9000 1000000 2 34 100 300

390

SWAT USERS MANUAL, VERSION 2000

Trade Name Baytex Baythroid Benlate Benzex Betamix Betanex Bidrin Bladex Bolero Bolstar Bordermaster Botran Bravo Buctril Butyrac Ester Caparol Carbamate Carsoron Carzol Cerone Chem-Hoe Chlordane Chopper Classic Cobra Comite Command Cotoran Counter Crossbow Curacron Cygon Cyprex Cythion Dacamine Dacthal Dalapon Dasanit DDT Dedweed DEF Dessicant L-10 Devrinol

Common Name Fenthion Cyfluthrin Benomyl BHC Phenmedipham Desmedipham Dicrotophos Cyanazine Thiobencarb Sulprofos MCPA Ester DCNA (Dicloran) Chlorothalonil Bromoxynil Octan. Ester 2,4-DB Ester Prometryn Ferbam Dichlobenil Formetanate Hydrochlor Ethephon Propham (IPC) Chlordane Imazapyr Amine Chlorimuron-ethyl Lactofen Propargite Clomazone Fluometuron Terbufos Triclopyr Amine Profenofos Dimethoate Dodine Acetate Malathion 2,4-D Acid DCPA Dalapon Sodium Salt Fensulfothion DDT MCPA Amine Tribufos Arsenic Acid Napropamide

Koc (ml/g) 1500 100000 1900 55000 2400 1500 75 190 900 12000 1000 1000 1380 10000 500 400 300 400 1000000 100000 200 100000 100 110 100000 4000 300 100 500 20 2000 20 100000 1800 20 5000 1 10000 240000 20 5000 100000 400

Washoff Frac. 0.65 0.40 0.25 0.05 0.70 0.70 0.70 0.60 0.70 0.55 0.50 0.50 0.50 0.20 0.45 0.50 0.90 0.45 0.95 0.95 0.50 0.05 0.80 0.90 0.20 0.20 0.80 0.50 0.60 0.95 0.90 0.95 0.50 0.90 0.45 0.30 0.95 0.90 0.05 0.95 0.25 0.95 0.60

Half-Life Foliar Soil (days) 2.0 5.0 6.0 3.0 5.0 5.0 20.0 5.0 7.0 0.5 8.0 4.0 5.0 3.0 7.0 10.0 3.0 5.0 30.0 5.0 2.0 2.5 30.0 15.0 2.0 5.0 3.0 30.0 2.5 15.0 3.0 3.0 10.0 1.0 5.0 10.0 37.0 4.0 10.0 7.0 7.0 10000.0 15.0 34.0 30.0 240.0 600.0 30.0 30.0 28.0 14.0 21.0 140.0 25.0 10.0 30.0 7.0 7.0 60.0 17.0 60.0 100.0 10.0 10.0 100.0 90.0 40.0 3.0 56.0 24.0 85.0 5.0 46.0 8.0 7.0 20.0 1.0 10.0 100.0 30.0 24.0 120.0 25.0 30.0 10000.0 70.0 Water Solubility (mg/L) 4.2 0.002 2 0.1 4.7 8 1000000 170 28 0.31 5 7 0.6 0.08 8 33 120 21.2 500000 1239000 250 0.1 500000 1200 0.1 0.5 1000 110 5 2100000 28 39800 700 130 890 0.5 900000 0.01 0.1 866000 2.3 17000 74

APPENDIX A: DATABASES

391

Trade Name Di-Syston Dibrom Dieldrin Dimilin Dinitro Diquat Dithane Dowpon Dropp DSMA Du-ter Dual Dyfonate Dylox Dymid Dyrene Elgetol EPN Eradicane Ethanox Evik Evital Far-Go Fenatrol Fenitox Fruitone CPA Fundal Funginex Furadan Fusilade Glean Goal Guthion Harmony Harvade Hoelon Hyvar Imidan Isotox Karate Karathane Karmex Kelthane

Common Name Disulfoton Naled Dieldrin Diflubenzuron Dinoseb Phenol Diquat Dibromide Mancozeb Dalapon Thidiazuron Methanearsonic Acid Na Triphenyltin Hydroxide Metolachlor Fonofos Trichlorfon Diphenamid Anilazine DNOC Sodium Salt EPN EPTC Ethion Ametryn Norflurazon Triallate Fenac Fenitrothion 3-CPA Sodium Salt Chlordimeform Hydroclo. Triforine Carbofuran Fluazifop-P-Butyl Chlorsulfuron Oxyfluorfen Azinphos-Methyl Thifensulfuron-Methyl Dimethipin Diclofop-Methyl Bromacil Phosmet Lindane Lambda-Cyhalothrin Dinocap Diuron Dicofol

Koc (ml/g) 600 180 50000 10000 500 1000000 2000 4 110 100000 23000 200 870 10 210 3000 20 13000 200 10000 300 600 2400 20 2000 20 100000 540 22 5700 40 100000 1000 45 10 16000 32 820 1100 180000 550 480 180000

Washoff Frac. 0.50 0.90 0.05 0.05 0.60 0.95 0.25 0.95 0.40 0.95 0.40 0.60 0.60 0.95 0.80 0.50 0.95 0.60 0.75 0.65 0.65 0.50 0.40 0.95 0.90 0.95 0.90 0.80 0.55 0.40 0.75 0.40 0.65 0.80 0.80 0.45 0.75 0.90 0.05 0.40 0.30 0.45 0.05

Half-Life Foliar Soil (days) 3.0 5.0 5.0 27.0 3.0 30.0 10.0 37.0 3.0 30.0 18.0 5.0 2.5 3.0 5.0 5.0 8.0 5.0 3.0 7.0 5.0 15.0 15.0 30.0 3.0 3.0 1.0 5.0 2.0 4.0 30.0 8.0 2.0 3.0 3.0 8.0 20.0 3.0 2.5 5.0 8.0 30.0 4.0 30.0 1.0 1400.0 10.0 20.0 1000.0 70.0 30.0 10.0 1000.0 75.0 90.0 40.0 10.0 30.0 1.0 20.0 5.0 6.0 150.0 60.0 90.0 82.0 180.0 8.0 10.0 60.0 21.0 50.0 15.0 160.0 35.0 10.0 12.0 10.0 37.0 60.0 19.0 400.0 30.0 20.0 90.0 60.0 Water Solubility (mg/L) 25 2000 0.1 0.08 50 718000 6 1000 20 1400000 1 530 16.9 120000 260 8 100000 0.5 344 1.1 185 28 4 500000 30 200000 500000 30 351 2 7000 0.1 29 2400 3000 0.8 700 20 7.3 0.005 4 42 1

392

SWAT USERS MANUAL, VERSION 2000

Trade Name Kerb Krenite Lannate Larvadex Larvin Lasso Limit Lontrel Lorox Lorsban Manzate Marlate Matacil Mavrik Metasystox Milogard Miral Mitac Modown Monitor Morestan Nemacur Nemacur Sulfone Nemacur Sulfoxide Norton Octave Oftanol Orthene Orthocide Oust Pay-Off Penncap-M Phenatox Phosdrin Phoskil Pipron Pix Plantvax Poast Polyram Pounce Pramitol Prefar

Common Name Pronamide Fosamine Ammon. Salt Methomyl Cyromazine Thiodicarb Alachlor Amidochlor Clopyralid Linuron Clorpyrifos Maneb Methoxychlor Aminocarb Fluvalinate Oxydemeton-Methyl Propazine Isazofos Amitraz Bifenox Methamidophos Oxythioquinox Fenamiphos Fenamiphos Sulfone Fenamiphos Sulfoxide Ethofumesate Prochloraz Isofenphos Acephate Captan Sulfometuron-Methyl Flucythrinate Methyl Parathion Toxaphene Mevinphos Parathion (Ethyl) Piperalin Mepiquat Chlor. Salt Oxycarboxin Sethoxydim Metiram Permethrin Prometon Bensulide

Koc (ml/g) 200 150 72 200 350 170 1000 6 400 6070 1000 80000 100 1000000 10 154 100 1000 10000 5 2300 240 45 40 340 500 600 2 200 78 100000 5100 100000 44 5000 5000 1000000 95 100 500000 100000 150 1000

Washoff Frac. 0.30 0.95 0.55 0.95 0.70 0.40 0.70 0.95 0.60 0.65 0.65 0.05 0.90 0.40 0.95 0.45 0.65 0.45 0.40 0.95 0.50 0.70 0.70 0.70 0.65 0.50 0.65 0.70 0.65 0.65 0.40 0.90 0.05 0.95 0.70 0.60 0.95 0.70 0.70 0.40 0.30 0.75 0.40

Half-Life Foliar Soil (days) 20.0 4.0 0.5 30.0 4.0 3.0 8.0 2.0 15.0 3.3 3.0 6.0 4.0 7.0 3.0 5.0 5.0 1.0 3.0 4.0 10.0 5.0 18.0 42.0 10.0 30.0 30.0 2.5 9.0 10.0 5.0 3.0 2.0 0.6 4.0 10.0 30.0 10.0 3.0 7.0 8.0 30.0 30.0 60.0 8.0 30.0 150.0 7.0 15.0 20.0 30.0 60.0 30.0 12.0 120.0 6.0 30.0 10.0 135.0 34.0 2.0 7.0 6.0 30.0 5.0 18.0 42.0 30.0 120.0 150.0 3.0 2.5 20.0 21.0 5.0 9.0 3.0 14.0 30.0 1000.0 20.0 5.0 20.0 30.0 500.0 120.0 Water Solubility (mg/L) 15 1790000 58000 136000 19.1 240 10 300000 75 0.4 6 0.1 915 0.005 1000000 8.6 69 1 0.4 1000000 1 400 400 400 50 34 24 818000 5.1 70 0.06 60 3 600000 24 20 1000000 1000 4390 0.1 0.006 720 5.6

APPENDIX A: DATABASES

393

Trade Name Prelude Prime Princep Probe Prowl Pursuit Pydrin Pyramin Ramrod Reflex Rescue Ridomil Ro-Neet Ronstar Roundup Rovral Royal Slo-Gro Rubigan Sancap Savey Scepter Sencor Sevin Sinbar Slug-Geta Sonalan Spectracide Spike Sprout Nip Stam Supracide Surflan Sutan Swat Tackle Talstar Tandem Tanone Tattoo TBZ Temik Temik Sulfone Temik Sulfoxide

Common Name Paraquat Flumetralin Simazine Methazole Pendimethalin AC 263,499 Fenvalerate Pyrazon Propaclor Fomesafen Salt 2,4-DB Sodium Amine Metalaxyl Cycloate Oxadiazon Glyphosate Amine Iprodione Maleic Hydrazide Fenarimol Dipropetryn Hexythiazox Imazaquin Ammonium Metribuzin Carbaryl Terbacil Methiocarb Ethalfluralin Diazinon Tebuthiuron Chlorpropham Propanil Methidathion Oryzalin Butylate Phosphamidon Acifluorfen Bifenthrin Tridiphane Phenthoate Bendiocarb Thiabendazole Aldicarb Aldicarb Sulfone Aldicarb Sulfoxide

Koc (ml/g) 1000000 10000 130 3000 5000 10 5300 120 80 60 20 50 430 3200 24000 700 20 600 900 6200 20 60 300 55 300 4000 1000 80 400 149 400 600 400 7 113 240000 5600 250 570 2500 40 10 30

Washoff Frac. 0.60 0.40 0.40 0.40 0.40 0.90 0.25 0.85 0.40 0.95 0.45 0.70 0.50 0.50 0.60 0.40 0.95 0.40 0.40 0.40 0.95 0.80 0.55 0.70 0.70 0.40 0.90 0.90 0.90 0.70 0.90 0.40 0.30 0.95 0.95 0.40 0.40 0.65 0.85 0.60 0.70 0.70 0.70

Half-Life Foliar Soil (days) 30.0 7.0 5.0 5.0 30.0 20.0 10.0 5.0 3.0 30.0 9.0 30.0 2.0 20.0 2.5 5.0 10.0 30.0 5.0 5.0 20.0 5.0 7.0 30.0 10.0 4.0 4.0 30.0 8.0 1.0 3.0 5.0 1.0 5.0 5.0 7.0 8.0 2.0 3.0 30.0 7.0 20.0 30.0 1000.0 20.0 60.0 14.0 90.0 90.0 35.0 21.0 6.0 100.0 10.0 70.0 30.0 60.0 47.0 14.0 30.0 360.0 30.0 30.0 60.0 40.0 10.0 120.0 30.0 60.0 40.0 360.0 30.0 1.0 7.0 20.0 13.0 17.0 14.0 26.0 28.0 40.0 5.0 403.0 7.0 20.0 30.0 Water Solubility (mg/L) 620000 0.1 6.2 1.5 0.275 200000 0.002 400 613 700000 709000 8400 95 0.7 900000 13.9 400000 14 16 0.5 160000 1220 120 710 24 0.3 60 2500 89 200 220 2.5 44 1000000 250000 0.1 1.8 200 40 50 6000 6000 6000

394

SWAT USERS MANUAL, VERSION 2000

Trade Name Tenoran Terbutrex Terrachlor Terraneb Terrazole Thimet Thiodan Thiram Thistrol Tillam Tilt Tolban Topsin Tordon Tralomethrin Treflan Tre-Hold Tupersan Turflon Velpar Vendex Vernam Volck oils Vydate Weedar Weed-B-Gon Wedone Zolone

Common Name Chloroxuron Terbutryn PCNB Chloroneb Etridiazole Phorate Endosulfan Thiram MCPB Sodium Salt Pebulate Propiconazole Profluralin Thiophanate-Methyl Picloram Tralomethrin Trifluralin NAA Ethyl Ester Siduron Triclopyr Ester Hexazinone Fenbutatin Oxide Vernolate Petroleum oil Oxamyl 2,4-D amine 2,4,5-T Amine Dichlorprop Ester Phosalone

Koc (ml/g) 3000 2000 5000 1650 1000 1000 12400 670 20 430 1000 2240 1830 16 100000 8000 300 420 780 54 2300 260 1000 25 20 80 1000 1800

Washoff Frac. 0.40 0.50 0.40 0.50 0.60 0.60 0.05 0.50 0.95 0.70 0.70 0.35 0.40 0.60 0.40 0.40 0.40 0.70 0.70 0.90 0.20 0.80 0.50 0.95 0.45 0.45 0.45 0.65

Half-Life Foliar Soil (days) 15.0 5.0 4.0 30.0 3.0 2.0 3.0 8.0 7.0 4.0 30.0 1.0 5.0 8.0 1.0 3.0 5.0 30.0 15.0 30.0 30.0 2.0 2.0 4.0 9.0 10.0 9.0 8.0 60.0 42.0 21.0 130.0 20.0 60.0 50.0 15.0 14.0 14.0 110.0 140.0 10.0 90.0 27.0 60.0 10.0 90.0 46.0 90.0 90.0 12.0 10.0 4.0 10.0 24.0 10.0 21.0 Water Solubility (mg/L) 2.5 22 0.44 8 50 22 0.32 30 200000 100 110 0.1 3.5 200000 0.001 0.3 105 18 23 3300 0.013 108 100 282000 796000 500000 50 3

Knisel (1993) cites Wauchope et al. (1992) as the source for water solubility, soil half-life and Koc values. Wash-off fraction and foliar half-life were obtained from Willis et al. (1980) and Willis and McDowell (1987).

A.3.1 WATER SOLUBILITY

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

APPENDIX A: DATABASES

395

possible concentration of pesticide in solution is seldom reached (Leonard and Knisel, 1988). Reported solubility values are determined under laboratory conditions at a constant temperature, typically between 20C and 30C.

A.3.2 SOIL ADSORPTION COEFFICIENT

The pesticide adsorption coefficient reported in the pesticide database can usually be obtained from a search through existing literature on the pesticide.

A.3.3 SOIL HALF-LIFE

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. The pesticide half-life for a chemical will vary with a change in soil environment (e.g. change in soil temperature, water content, etc.). Soil half-life values provided in the database are average or representative values. Half-life values reported for a chemical commonly vary by a factor of 2 to 3 and sometimes by as much as a factor of 10. For example, the soil half-life for atrazine can range from 120 to 12 days when comparing values reported in cool, dry regions to those from warm, humid areas. Another significant factor is soil treatment history. Repeated soil treatment by the same or a chemically similar pesticide commonly results in a reduction in half-life for the pesticide. This reduction is attributed to the preferential build-up of microbial populations adapted to degrading the compound. Users are encouraged to replace the default soil half-life value with a site-specific or region-specific value whenever the information is available.

A.3.4 FOLIAR HALF-LIFE

As with the soil half-life, the foliar half-life entered for a pesticide is a lumped parameter describing the loss rate of pesticides on the plant canopy. For most pesticides, the foliar half-life is much less than the soil half-life due to enhanced volatilization and photodecomposition. While values for foliar half-life

396

SWAT USERS MANUAL, VERSION 2000

were available for some pesticides in the database, the majority of foliar half-life values were calculated using the following rules: 1) Foliar half-life was 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 was adjusted downward for pesticides with vapor pressures less than 10-5 mm Hg. 3) The maximum foliar half-life assigned was 30 days.

A.3.5 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. Some wash-off fraction values were obtained from Willis et al. (1980). For the remaining pesticides, solubility was used as a guide for estimating the wash-off fraction.

A.3.6 APPLICATION EFFICIENCY

The application efficiency for all pesticides listed in the database is defaulted to 0.75. This variable is a calibration parameter.

APPENDIX A: DATABASES

397

A.4 FERTILIZER DATABASE

The fertilizer database file (fert.dat) summarizes nutrient fractions for various fertilizers and types of manure. The following table lists the fertilizers and types of manure in the fertilizer database.
Table A-12: SWAT Fertilizer Database Name Name Code Elemental Nitrogen Elemental Phosphorous Anhydrous Ammonia Urea 46-00-00 33-00-00 31-13-00 30-80-00 30-15-00 28-10-10 28-03-00 26-13-00 25-05-00 25-03-00 24-06-00 22-14-00 20-20-00 18-46-00 18-04-00 16-20-20 15-15-15 15-15-00 13-13-13 12-20-00 11-52-00 11-15-00 10-34-00 10-28-00 10-20-20 10-10-10 08-15-00 08-08-00 07-07-00 07-00-00 06-24-24 05-10-15 Elem-N Elem-P ANH-NH3 UREA 46-00-00 33-00-00 31-13-00 30-80-00 30-15-00 28-10-10 28-03-00 26-13-00 25-05-00 25-03-00 24-06-00 22-14-00 20-20-00 18-46-00 18-04-00 16-20-20 15-15-15 15-15-00 13-13-13 12-20-00 11-52-00 11-15-00 10-34-00 10-28-00 10-20-20 10-10-10 08-15-00 08-08-00 07-07-00 07-00-00 06-24-24 05-10-15 Min-N 1.000 0.000 0.820 0.460 0.460 0.330 0.310 0.300 0.300 0.280 0.280 0.260 0.250 0.250 0.240 0.220 0.200 0.180 0.180 0.160 0.150 0.150 0.130 0.120 0.110 0.110 0.100 0.100 0.100 0.100 0.080 0.080 0.070 0.070 0.060 0.050 Min-P 0.000 1.000 0.000 0.000 0.000 0.000 0.057 0.352 0.066 0.044 0.013 0.057 0.022 0.013 0.026 0.062 0.088 0.202 0.018 0.088 0.066 0.066 0.057 0.088 0.229 0.066 0.150 0.123 0.088 0.044 0.066 0.035 0.031 0.000 0.106 0.044 Org-N 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 Org-P 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 NH3-N/ Min N 0.000 0.000 1.000 1.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000

398

SWAT USERS MANUAL, VERSION 2000

Name 05-10-10 05-10-05 04-08-00 03-06-00 02-09-00 00-15-00 00-06-00 Dairy-Fresh Manure Beef-Fresh Manure Veal-Fresh Manure Swine-Fresh Manure Sheep-Fresh Manure Goat-Fresh Manure Horse-Fresh Manure Layer-Fresh Manure

Name Code 05-10-10 05-10-05 04-08-00 03-06-00 02-09-00 00-15-00 00-06-00 DAIRY-FR BEEF-FR VEAL-FR SWINE-FR SHEEP-FR GOAT-FR HORSE-FR LAYER-FR

Min-N 0.050 0.050 0.040 0.030 0.020 0.000 0.000 0.007 0.010 0.023 0.026 0.014 0.013 0.006 0.013

Min-P 0.044 0.044 0.035 0.026 0.040 0.066 0.026 0.005 0.004 0.006 0.011 0.003 0.003 0.001 0.006

Org-N 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.031 0.030 0.029 0.021 0.024 0.022 0.014 0.040 0.040 0.045 0.025

Org-P 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.003 0.007 0.007 0.005 0.005 0.005 0.003 0.013 0.010 0.016 0.009

NH3-N/ Min N 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.990 0.990 0.990 0.990 0.990 0.990 0.990 0.990 0.990 0.990 0.990

Broiler-Fresh Manure BROIL-FR 0.010 0.004 Turkey-Fresh Manure TRKEY-FR 0.007 0.003 Duck-Fresh Manure DUCK-FR 0.008 0.023 Values in bold italics are estimated (see section A.4.2)

A.4.1 COMMERCIAL FERTILIZERS

In compiling the list of commercial fertilizers in the database, we tried to identify and include commonly used fertilizers. This list is not comprehensive, so users may need to append the database with information for other fertilizers used in their watersheds. When calculating the fractions of N and P for the database, it is important to remember that the percentages reported for a fertilizer are %N-%P2O5-%K2O. The fraction of mineral N in the fertilizer is equal to %N divided by 100. To calculate the fraction of mineral P in the fertilizer, the fraction of P in P2O5 must be known. The atomic weight of phosphorus is 31 and the atomic weight of oxygen is 16, making the molecular weight of P2O5 equal to 142. The fraction of P in P2O5 is 62/142 = 0.44 and the fraction of mineral P in the fertilizer is equal to 0.44 (%P2O5 / 100).

APPENDIX A: DATABASES

399

A.4.2 MANURE
The values in the database for manure types were derived from manure production and characteristics compiled by the ASAE (1998a). Table A-13 summarizes the levels of nitrogen and phosphorus in manure reported by the ASAE. The data summarized by ASAE is combined from a wide range of published and unpublished information. The mean values for each parameter are determined by an arithmetic average consisting of one data point per reference source per year and represent fresh (as voided) feces and urine.
Table A-13: Fresh manure production and characteristics per 1000 kg live animal mass per day (from ASAE, 1998a)
Parameter Total Manure Total Solids kg kg mean std dev mean std dev mean std dev mean std dev mean std dev mean std dev Dairy 86 17 12 2.7 0.45 0.096 0.079 0.083 0.094 0.024 0.061 0.0058 Beef 58 17 8.5 2.6 0.34 0.073 0.086 0.052 0.092 0.027 0.030 ** Veal 62 24 5.2 2.1 0.27 0.045 0.12 0.016 0.066 0.011 ** ** Swine 84 24 11 6.3 0.52 0.21 0.29 0.10 0.18 0.10 0.12 ** Animal Type Sheep Goat Horse 40 41 51 11 8.6 7.2 11 13 15 3.5 1.0 4.4 0.42 0.45 0.30 0.11 0.12 0.063 ** ** ** ** ** ** 0.087 0.11 0.071 0.030 0.016 0.026 0.032 ** 0.019 0.014 ** 0.0071 Layer 64 19 16 4.3 0.84 0.22 0.21 0.18 0.30 0.081 0.092 0.016 Broiler 85 13 22 1.4 1.1 0.24 ** ** 0.30 0.053 ** ** Turkey 47 13 12 3.4 0.62 0.13 0.080 0.018 0.23 0.093 ** ** Duck 110 ** 31 15 1.5 0.54 ** ** 0.54 0.21 0.25 **

Total Kjeldahl kg nitrogen Ammonia kg nitrogen Total kg phosphorus Orthokg phosphorus ** Data not found. All values wet basis. Typical live animal masses for which manure values represent are: dairy, 640 kg; beef, 360 kg; veal, 91 kg; swine, 61 kg; sheep, 27 kg; goat, 64 kg; horse, 450 kg; layer, 1.8 kg; broiler, 0.9 kg; turkey, 6.8 kg; and duck, 1.4 kg. All nutrient values are given in elemental form.

The fractions of the nutrient pools were calculated on a Total Solids basis, i.e. the water content of the manure was ignored. Assumptions used in the calculations are: 1) the mineral nitrogen pool is assumed to be entirely composed of NH3/NH4+, 2) the organic nitrogen pool is equal to total Kjeldahl nitrogen minus ammonia nitrogen, 3) the mineral phosphorus pool is equal to the value given for orthophosphorus, and 4) the organic phosphorus pool is equal to total phosphorus minus orthophosphorus. Total amounts of nitrogen and phosphorus were available for all manure types. For manure types with either the ammonia nitrogen or orthophosphorus value missing, the ratio of organic to mineral forms of the provided element were used to partition the total amount of the other element. For example, in Table A-

400

SWAT USERS MANUAL, VERSION 2000

13 amounts of total Kjeldahl N, ammonia N, and total P are provided for veal but data for orthophosphorus is missing. To partition the total P into organic and mineral pools, the ratio of organic to mineral N for veal was used. If both ammonia nitrogen and orthophosphorus data are missing, the ratio of the organic to mineral pool for a similar animal were used to partition the total amounts of element into different fractions. This was required for goat and broiler manure calculations. The ratio of organic to mineral pools for sheep was used to partition the goat manure nutrient pools while layer manure nutrient ratios were used to partition the broiler manure nutrient pools. As can be seen from the standard deviations in Table A-13, values for nutrients in manure can vary widely. If site specific data are available for the region or watershed of interest, those values should be used in lieu of the default fractions provided in the database.

APPENDIX A: DATABASES

401

A.5 URBAN DATABASE

The urban database file (urban.dat) summarizes urban landscape attributes needed to model urban areas. These attributes tend to vary greatly from region to region and the user is recommended to use values specific to the area being modeled. The following tables list the urban land types and attributes that are provided in the urban database. Numerous urban land type classifications exist. For the default urban land types included in the database, an urban land use classification system created by Palmstrom and Walker (1990) was simplified slightly. Table A-14 lists the land type classifications used by Palmstrom and Walker and those provided in the database.
Table A-14: Urban land type classification systems Palmstrom and Walker (1990) SWAT Urban Database Residential-High Density Residential-High Density Residential-Med/High Density Residential-Medium Density Residential-Med/Low Density Residential-Med/Low Density Residential-Low Density Residential-Low Density Residential-Rural Density Commercial Commercial Industrial Industrial-Heavy Transportation Industrial-Medium Institutional Transportation Institutional

The urban database includes the following information for each urban land type: 1) fraction of urban land area that is impervious (total and directly connected); 2) curb length density; 3) wash-off coefficient; 4) maximum accumulated solids; 5) number of days for solid load to build from 0 kg/curb km to half of the maximum possible load; 6) concentration of total N in solid loading; 7) concentration of total P in solid loading; and 8) concentration of total NO3-N in solid loading. The fraction of total and directly connected impervious areas is needed for urban surface runoff calculations. The remaining information is used only when the urban build up/wash off algorithm is chosen to model sediment and nutrient loading from the urban impervious area.

402

SWAT USERS MANUAL, VERSION 2000

A.5.1 DRAINAGE SYSTEM CONNECTEDNESS

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. However these methods are not always feasible. An alternative approach is to use data from other inventoried watersheds with similar land types. Table A-15 contains ranges and average values calculated from a number of different individual surveys (the average values from Table A-15 are the values included in the database). Table A-16 contains data collected from the cities of Madison and Milwaukee, Wisconsin and Marquett, Michigan.
Table A-15: Range and average impervious fractions for different urban land types. Range Average Range Average total total connected connected Urban Land Type impervious impervious impervious impervious Residential-High Density .60 .44 - .82 .44 .32 - .60 (> 8 unit/acre or unit/2.5 ha) Residential-Medium Density .38 .23 - .46 .30 .18 - .36 (1-4 unit/acre or unit/2.5 ha) Residential-Med/Low Density .20 .14 - .26 .17 .12 - .22 (> 0.5-1 unit/acre or unit/2.5 ha) Residential-Low Density .12 .07 - .18 .10 .06 - .14 (< 0.5 unit/acre or unit/2.5 ha) Commercial .67 .48 - .99 .62 .44 - .92 Industrial .84 .63 - .99 .79 .59 - .93 Transportation .98 .88 - 1.00 .95 .85 1.00 Institutional .51 .33 - .84 .47 .30 - .77 Table A-16: Impervious fractions for different urban land types in Madison and Milwaukee, WI and Marquett, MI. Directly Indirectly connected connected Urban Land Type impervious impervious Pervious Residential-High Density .51 .00 .49 Residential-Medium Density .24 .13 .63 Residential-Low Density .06 .10 .84 Regional Mall .86 .00 .14 Strip Mall .75 .00 .25 Industrial-Heavy .80 .02 .18 Industrial-Light .69 .00 .31 Airport .09 .25 .66 Institutional .41 .00 .59 Park .08 .06 .86

APPENDIX A: DATABASES

403

A.5.2 CURB LENGTH DENSITY

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. The curb length densities assigned to the different land uses in the database were calculated by averaging measured curb length densities reported in studies by Heaney et al. (1977) and Sullivan et al. (1978). Table A-17 lists the reported values and the averages used in the database.
Table A-17: Measured curb length density for various land types Location: Tulsa, 10 Ontario Average of OK Cities two values Land type km/ha km/ha km/ha Residential 0.30 0.17 0.24 Commercial 0.32 0.23 0.28 Industrial 0.17 0.099 0.14 Park 0.17 -0.17 Open 0.063 0.059 0.06 Institutional -0.12 0.12

SWAT database categories using average value: All Residential Commercial Industrial Transportation, Institutional

A.5.3 WASH-OFF COEFFICENT

The database assigns the original default value, 0.18 mm-1, to the wash-off coefficient for all land types in the database (Huber and Heaney, 1982). This value was calculated assuming that 13 mm of total runoff in one hour would wash off 90% of the initial surface load. 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.

A.5.4 MAXIMUM SOLID ACCUMULATION AND RATE OF ACCUMULATION

The shape of the solid build-up equation is defined by two variables: the maximum solid accumulation for the land type and the amount of time it takes to build up from 0 kg/curb km to one-half the maximum value. The values assigned

404

SWAT USERS MANUAL, VERSION 2000

to the default land types in the database were extrapolated from a study performed by Sartor and Boyd (1972) in ten U.S. cities. They summarized the build-up of solids over time for residential, commercial, and industrial land types as well as providing results for all land types combined (Figure A-5).

Figure A-5: Solid loading as a function of time (Sartor and Boyd, 1972)

The lines plotted in Figure A-5 were adapted for use in the database. Table A-18 lists maximum load values and time to accumulate half the maximum load that were derived from the graph. The assignment of values to the different land types is provided in the table also.
Table A-18: Maximum solid load and accumulation time (from Sartor and Boyd, 1972). Maximum time to accumulate SWAT database categories loading maximum load Land type kg/curb km days using value: Residential 225 0.75 All Residential Commercial 200 1.60 Commercial Industrial 400 2.35 Industrial All land types 340 3.90 Transportation/Institutional

APPENDIX A: DATABASES

405

A.5.5 NUTRIENT CONCENTRATION IN SOLIDS

For the default land types in the database, nutrient concentrations in the solids were extrapolated from a nationwide study by Manning et al. (1977). The data published by Manning is summarized in Table A-19. Three concentration values are required: total nitrogen (mg N/kg), nitrate nitrogen (mg NO3-N/kg), and total phosphorus (mg P/kg). Manning provided total nitrogen values for all of his land use categories, nitrate values for one land use category and mineral phosphorus values for all the land use categories. To obtain nitrate concentrations for the other land use categories, the ratio of NO3-N to total N for commercial areas was assumed to be representative for all the categories. The nitrate to total N ratio for commercial land was multiplied by the total N concentrations for the other categories to obtain a nitrate concentration. The total phosphorus concentration was estimated by using the ratio of organic phosphorus to orthophosphate provided by the Northern Virginia Planning District Commission (1979). Total phosphorus loads from impervious areas are assumed to be 75 percent organic and 25 percent mineral. Table A-20 summarizes the assignment of values to the default land types in the urban database.
Table A-19: Nationwide dust and dirt build-up rates and pollutant fractions (Manning et al., 1977) Pollutant Land Use Category
Dust & Dirt Accumulation (kg/curb km/day) Total N-N (mg/kg) NO3 (mg/kg) PO4-P (mg/kg) mean range # obs. mean range # obs. mean range # obs. mean range # obs. Single Family Residential 17 1-268 74 460 325-525 59 ---49 20-109 59 Mult. Family Residential 32 2-217 101 550 356-961 93 ---58 20-73 93 Commercial 47 1-103 158 420 323-480 80 24 10-35 21 60 0-142 101 Industrial 90 1-423 67 430 410-431 38 ---26 14-30 38 All Data 45 1-423 400 480 323-480 270 24 10-35 21 53 0-142 291

406

SWAT USERS MANUAL, VERSION 2000 SWAT database categories using value:

Table A-20: Nutrient concentration assignments for default land types Manning et al (1977) Modifications: Final Value:

Total Nitrogen-N Single Fam Res. 460 ppm -460 ppm Residential: Med/Low & Low Mult. Fam. Res. 550 ppm -550 ppm Residential: Med. & High Commercial 420 ppm -420 ppm Commercial Industrial 430 ppm -430 ppm Industrial All Data 480 ppm -480 ppm Transportation/Institutional Nitrate-N: multiply reported value by fraction of weight that is nitrogen to get NO3-N Single Fam Res. (5.5/420) x 460 6.0 ppm Residential: Med/Low & Low Mult. Fam. Res. (5.5/420) x 550 7.2 ppm Residential: Med. & High Commercial 5.5 ppm -5.5 ppm Commercial Industrial (5.5/420) x 430 5.6 ppm Industrial All Data (5.5/420) x 480 6.3 ppm Transportation/Institutional Total Phosphorus-P: assume PO4-P is 25% of total P Single Fam Res. 49/(.25) 196 ppm Residential: Med/Low & Low 49 ppm PO4-P 58/(.25) 232 ppm Residential: Med. & High Mult. Fam. Res. 58 ppm PO4-P 60/(.25) 240 ppm Commercial Commercial 60 ppm PO4-P 26/(.25) 104 ppm Industrial Industrial 26 ppm PO4-P 53/(.25) 212 ppm Transportation/Institutional All Data 53 ppm PO4-P

A.6 REFERENCES
American Society of Agricultural Engineers, 1998a. Manure production and characteristics, p. 646-648. In ASAE Standards 1998, 45th edition, Section D384.1. ASAE, St. Joseph. American Society of Agricultural Engineers, 1998b. Terminology and definitions for agricultural tillage implements, p. 261-272. In ASAE Standards 1998, 45th edition, Section S414.1. ASAE, St. Joseph. Arnold, J.G. and J.R. Williams. 1995. SWRRBA watershed scale model for soil and water resources management. p. 847-908. In V.P. Singh (ed) Computer models of watershed hydrology. Water Resources Publications. Bailey, L.H. 1935. The Standard cyclopedia of horticulture. The Macmillan Publishing Co., New York, N.Y. Consumer Nutrition Center. 1982. Composition of foods: Fruit and fruit juices. USDA Human Nutrition Information Service. Agricultural Handbook 8-9. Diaz, R.A. and G.S. Campbell. 1988. Assessment of vapor density deficit from available air temperature information. ASA Annual Meetings, Anaheim, CA, Agron. Abstr., 1988, 16.

APPENDIX A: DATABASES

407

Duncan, W.G. and Hesketh, J.D. 1968. Net photosynthesis rates, relative leaf growth rates and leaf numbers of 22 races of maize grown at eight temperatures. Crop Sci. 8:670-674. Hackett, C. and J. Carolane. 1982. Edible horticultural crops, a compendium of information on fruit, vegetable, spice and nut species, Part II: Attribute data. Division of Land Use Research, CSIRO, Canberra. Heaney, J.P., W.C. Huber, M.A. Medina, Jr., M.P. Murphy, S.J. Nix, and S.M. Haasan. 1977. Nationwide evaluation of combined sewer overflows and urban stormwater dischargesVol. II: Cost assessment and impacts. EPA600/2-77-064b (NTIS PB-266005), U.S. Environmental Protection Agency, Cincinnati, OH. Huber, W.C. and R.E. Dickinson. 1988. Storm water management model, version 4: users manual. U.S. Environmental Protection Agency, Athens, GA. Huber, W.C. and J.P. Heaney. 1982. Chapter 3: Analyzing residual discharge and generation from urban and non-urban land surfaces. p. 121-243. In D.J. Basta and B.T. Bower (eds). Analyzing natural systems, analysis for regional residualsenvironmental quality management. John Hopkins University Press, Baltimore, MD. Jensen, M.E., R.D. Burman, and R.G. Allen. 1990. Evapotranspiration and Irrigation Water Requirements. ASCE Manuals and Reports on Engineering Practice No. 70. ASCE, New York, N.Y. Kiniry, J.R. 1998. Biomass accumulation and radiation use efficiency of honey mesquite and eastern red cedar. Biomass and Bioenergy 15:467-473. Kiniry, J.R. 1999. Response to questions raised by Sinclair and Muchow. Field Crops Research 62:245-247. Kiniry, J.R., R. Blanchet, J.R. Williams, V. Texier, C.A. Jones, and M. Cabelguenne. 1992b. Sunflower simulation using EPIC and ALMANAC models. Field Crops Res., 30:403-423. Kiniry, J.R. and A.J. Bockholt. 1998. Maize and sorghum simulation in diverse Texas environments. Agron. J. 90:682-687.

408

SWAT USERS MANUAL, VERSION 2000

Kiniry, J.R. C.A. Jones, J.C. O'Toole, R. Blanchet, M. Cabelguenne and D.A. Spanel. 1989. Radiation-use efficiency in biomass accumulationprior to grain-filling for five grain-crop species. Field Crops Research 20:51-64. Kiniry, J.R., J.A. Landivar, M. Witt, T.J. Gerik, J. Cavero, L.J. Wade. 1998. Radiation-use efficiency response to vapor pressure deficit for maize and sorghum. Field Crops Research 56:265-270. Kiniry, J.R., D.J. Major, R.C. Izaurralde, J.R. Williams, P.W. Gassman, M. Morrison, R. Bergentine, and R.P. Zentner. 1995. EPIC model parameters for cereal, oilseed, and forage crops in the northern Great Plains region. Can. J. Plant Sci. 75: 679-688. Kiniry, J.R., W.D. Rosenthal, B.S. Jackson, and G. Hoogenboom. 1991. Chapter 5: Predicting leaf development of crop plants. p. 30-42. In Hodges (ed.) Predicted crop phenology. CRC Press, Boca Raton, FL. Kiniry, J.R., M.A. Sanderson, J.R. Williams, C.R. Tischler, M.A. Hussey, W.R. Ocumpaugh, J.C. Read, G.V. Esbroeck, and R.L. Reed. 1996. Simulating Alamo switchgrass with the Almanac model. Agron. J. 88:602-606. Kiniry, J.R., C.R. Tischler and G.A. Van Esbroeck. 1999. Radiation use efficiency and leaf CO2 exchange for diverse C4 grasses. Biomass and Bioenergy 17:95-112. Kiniry, J.R. and J.R. Williams. 1994. EPIC Crop Parameters for Vegetables for the Nitrogen and Phosphorus Portions of the RCA Analysis. Memorandum. Kiniry, J.R., J.R. Williams, P.W. Gassman, P. Debaeke. 1992a. A general, process-oriented model for two competing plant species. Transactions of the ASAE 35:801-810. Kiniry, J.R., J.R. Williams, R.L. Vanderlip, J.D. Atwood, D.C. Reicosky, J. Mulliken, W.J. Cox, H.J. Mascagni, Jr., S.E. Hollinger and W.J. Wiebold. 1997. Evaluation of two maize models for nine U.S. locations. Agron. J. 89:421-426.

APPENDIX A: DATABASES

409

Knisel, W.G. (ed). 1993. GLEAMS: Groundwater loading effects of agricultural management systems, Version 2.10. UGA-CPES-BAED Publication No. 5. University of Georgia, Tifton, GA. Krner, Ch. 1977. Blattdiffusionswiderstnde verschiedener Pflanzen in der zentralalpinen Grasheide der Hohen Tauren. p. 69-81. In Cernusca, A. (ed.) Alpine Grasheide Hohe Tauern. Ergebnisse der kosystemstudie 1976. Verff. sterr. MaB-Hochgebirgsprogr. ,,Hohe Tauern. Vol 1. Universittsverlag Wagner, Innsbruck. Krner, Ch., J.A. Scheel and H. Bauer. 1979. Maximum leaf diffusive conductance in vascular plants. Photosynthetica 13:45-82. Leonard, R.A. and W.G. Knisel. 1988. Evaluating groundwater contamination potential from herbicide use. Weed Tech. 2:207-216. Manning, M.J., R.H. Sullivan, and T.M. Kipp. 1977. Nationwide evaluation of combined sewer overflows and urban stormwater dischargesVol. III: Characterization of discharges. EPA-600/2-77-064c (NTIS PB-272107) U.S. Environmental Protection Agency, Cincinnati, OH. Manrique, L.A., J.R. Kiniry, T. Hodges, and D.S. Axness. 1991. Dry matter production and radiation interception of potato. Crop Sci. 31: 1044-1049. Martin, J.H., W.H. Leonard and D.L. Stamp. 1976. Principles of field crop production, 3rd edition. Macmillan Publishing Co., Inc., New York. Maynard, D.N. and Hochmuth. 1997. Knott's handbook for vegetable growers, 4th edition. John Wiley & Sons, Inc., New York. Monteith, J.L. 1965. Evaporation and the environment. p. 205-234. In The state and movement of water in living organisms, XIXth Symposium. Soc. for Exp. Biol., Swansea. Cambridge University Press. Northern Virginia Planning District Commission. 1979. Guidebook for screening urban nonpoint pollution management strategies: a final report prepared for Metropolitan Washington Council of Governments. Northern Virginia Planning District Commission, Falls Church, VA.

410

SWAT USERS MANUAL, VERSION 2000

Nutrition Monitoring Division. 1984b. Composition of food: Cereal grains and pasta. USDA Human Nutrition Information Service. Agricultural Handbook 8-20. Nutrition Monitoring Division. 1984c. Composition of food: Legumes and legume products. USDA Human Nutrition Information Service.

AgriculturalHandbook 8-16. Nutrition Monitoring Division. 1984d. Composition of food: Nut and seed products. USDA Human Nutrition Information Service.

AgriculturalHandbook 8-12. Nutrition Monitoring Division. 1984a. Composition of food: Vegetables and vegetable products. USDA Human Nutrition Information Service. Agricultural Handbook 8-11. Palmstrom, N. and W.W. Walker, Jr. 1990. P8 Urban Catchment Model: Users guide, program documentation, and evaluation of existing models, design concepts and Hunt-Potowomut data inventory. The Narragansett Bay Project Report No. NBP-90-50. Sartor, J.D. and G.B. Boyd. 1972. Water pollution aspects of street surface contaminants. EPA-R2-72-081 (NTIS PB-214408) U.S. Environmental Protection Agency, Washington, DC. Sonnen, M.B. 1980. Urban runoff quality: information needs. ASCE Journal of the Technical Councils 106(TC1): 29-40. Stockle, C.O. and J.R. Kiniry. 1990. Variability in crop radiation-use efficiency associated with vapor pressure deficit. Field Crops Research 25:171-181. Stockle, C.O., J.R. Williams, N.J. Rosenberg, and C.A. Jones. 1992. A method for estimating the direct and climatic effects of rising atmospheric carbon dioxide on growth and yield of crops: Part 1Modification of the EPIC model for climate change analysis. Agricultural Systems 38:225-238. Sullivan, R.H., W.D. Hurst, T.M. Kipp, J.P. Heaney, W.C. Huber, and S.J. Nix. 1978. Evaluation of the magnitude and significance of pollution from urban storm water runoff in Ontario. Research Report No. 81, Canada-

APPENDIX A: DATABASES

411

Ontario

Research

Program,

Environmental

Protection

Service,

Environment Canada, Ottawa, Ontario. Watson, D.J. 1958. The dependence of net assimilation rate on leaf area index. Ann. Bot. N.S. 22:37-54. Wauchope, R.D., T.M. Buttler, A.G. Hornsby, P.W.M. Augustijn-Beckers, and J.P. Burt. 1992. The SCS/ARS/CES pesticide properties database for environmental decision-making. Environ. Contam. Toxicol. Reviews 123:1-164. Willis, G.H. and L.L. McDowell. 1987. Pesticide persistence on foliage. Environ. Contam. Toxicol. Reviews 100:23-73. Willis, G.H., W.F. Spencer, and L.L. McDowell. 1980. Chapter 18: The interception of applied pesticides by foliage and their persistence and washoff potential. p. 595-606. In W.G. Knisel (ed). CREAMS: A field scale model for chemicals, runoff, and erosion from agricultural management systems, Vol. 3. U.S. Dept. of Agri., Sci., and Education Adm., Conservation Research Report No. 26. U.S. Government Printing Office, Washington, D.C.

412

SWAT USERS MANUAL, VERSION 2000

APPENDIX B

EXAMPLE WATERSHED CONFIGURATIONS

The watershed configuration file defines the spatial relationship of objects within the watershed. The three techniques used to subdivide a watershed are the subwatershed discretization, the hillslope discretization, and the grid cell discretization. The following sections describe how to set up the watershed configuration file for each of the different discretization techniques.

B.1 SUBWATERSHED DISCRETIZATION

The subwatershed discretization divides the watershed into subbasins based on topographic features of the watershed. This technique preserves the natural flow paths, boundaries, and channels required for realistic routing of water, sediment and chemicals. All of the GIS interfaces developed for SWAT use the subwatershed discretization to divide a watershed. The number of subbasins chosen to model the watershed depends on the size of the watershed, the spatial detail of available input data and the amount of detail required to meet the goals of the project. When subdividing the watershed, keep in mind that topographic attributes (slope, slope length, channel length, channel width, etc.) are calculated or summarized at the subbasin level. The subbasin delineation should be detailed enough to capture significant topographic variability within the watershed. Once the subbasin delineation has been completed, the user has the option of modeling a single soil/land use/management scheme for each subbasin or partitioning the subbasins into multiple hydrologic response units (HRUs). Hydrologic response units are unique soil/land use/management combinations within the subbasin which are modeled without regard to spatial positioning. When multiple HRUs are modeled within a subbasin, the land phase of the hydrologic cycle is modeled for each HRU and then the loadings from all HRUs within the subbasin are summed. The net loadings for the subbasin are then routed through the watershed channel network. HRUs are set up in the subbasin general attribute file (.sub). The following sections demonstrate how to create a SWAT watershed configuration file using the subwatershed discretization.

B.1.1 SUBWATERSHED DISCRETIZATION: 3 SUBBASINS

Assume we have a watershed with 3 subbasins as illustrated in Figure B-1.

Figure B-1: Subwatershed delineation

Step 1: Write the subbasin command for each subbasin. (This command simulates the land phase of the hydrologic cycle.)
column 1 column 2 column 3 column 4 column 5 column 6 column 7
space 1-10 space 11-16 space 17-22 space 23-28 space 29-34 space 35-40 space 41-46 space 47-55

subbasin subbasin subbasin

1 1 1

1 2 3

1 2 3

Writing subbasin in space 1-10 is optional. The model identifies the configuration command by the code in column 1. The option of writing the command in space 1-10 is provided to assist the user in interpreting the configuration file. Column 2 is the hydrograph storage location number (array location) where data for the loadings (water, sediment, chemicals) from the subbasin are stored. Column 3 is the subbasin number. The subbasin number tells SWAT which input files listed in file.cio contain the data used to model the subbasin. Subbasin numbers are assigned sequentially in file.cio to each pair of lines after line 14. The files listed on lines 15 & 16 of file.cio are used to model subbasin 1, the files listed on lines 17 & 18 of file.cio are used to model subbasin 2, the files listed on lines 19 & 20 of file.cio are used to model subbasin 3, and so on.

Step 2a: Route the stream loadings through the reach network. Begin by routing the headwater subbasin loadings through the main channel of the respective subbasin. (Headwater subbasins are those with no subbasins upstream.) Referring to Figure B-1, assume that subbasins 1 and 2 are upstream of subbasin 3. This would make subbasins 1 and 2 headwater subbasins.
column 1 column 2 column 3 column 4 column 5 column 6 column 7
space 1-10 space 11-16 space 17-22 space 23-28 space 29-34 space 35-40 space 41-46 space 47-55

subbasin subbasin subbasin route route

1 1 1 2 2

1 2 3 4 5

1 2 3 1 2

1 2

0.000 0.000

As mentioned in the last step, column 1 is used to identify the command. Column 2 is the hydrograph storage location number identifying the location where results from the route simulation are placed. Column 3 provides the number of the reach, or main channel, the inputs are routed through. The number of the reach in a particular subbasin is the same as the number of the subbasin. Column 4 lists the number of the hydrograph storage location containing the data to be routed through the reach. The loadings from subbasin 1 are stored in hydrograph storage #1 and the loadings from subbasin 2 are stored in hydrograph storage #2. Column 6 lists the fraction of overland flow. For the subwatershed discretization, this value will always be zeroflow is always considered to be channelized before entering the next subbasin. Step 2b: Route the stream loadings through the reach network. Use the add and route commands to continue routing through the watershed. For this example, the water, sediment and chemicals flowing out of subbasins 1 and 2 and the loadings from subbasin 3 must be added together and routed through the main channel of subbasin 3. The loadings from the outlet of subbasin 1 are stored in hydrograph location #4; the loadings from the outlet of subbasin 2 are stored in hydrograph location #5; and the loadings from subbasin 3 are stored in hydrograph location #3.

column 1 column 2 column 3 column 4 column 5 column 6 column 7

space 1-10 space 11-16 space 17-22 space 23-28 space 29-34 space 35-40 space 41-46 space 47-55

subbasin subbasin subbasin route route add add route

1 1 1 2 2 5 5 2

1 2 3 4 5 6 7 8

1 2 3 1 2 4 6 3

1 2 5 3 7

0.000 0.000

0.000

The add command is specified in column 1 by the number 5. The hydrograph storage location numbers of the 2 data sets to be added are listed in columns 3 and 4. The summation results are stored in the hydrograph location number given in column 2. Step 3: Once the stream loadings have been routed to the watershed outlet, append a finish command line to signify the end of the watershed routing file.
column 1 column 2 column 3 column 4 column 5 column 6 column 7
space 1-10 space 11-16 space 17-22 space 23-28 space 29-34 space 35-40 space 41-46 space 47-55

subbasin subbasin subbasin route route add add route finish

1 1 1 2 2 5 5 2 0

1 2 3 4 5 6 7 8

1 2 3 1 2 4 6 3

1 2 5 3 7

0.000 0.000

0.000

B.1.2 SUBWATERSHED DISCRETIZATION: SAVING SIMULATION RESULTS FOR DOWNSTREAM RUNS

If the watershed of interest is split up into subwatersheds that are modeled with separate SWAT runs, the outflow from the upstream subwatersheds must be saved in a file using the save command. This data will then be input into the SWAT simulation of the downstream portion of the watershed using a recday command. In example B.1.1, the outflow from the watershed is stored in hydrograph location #8, so this is the data we need to store in a daily file for use in another SWAT simulation. The watershed configuration modified to store outflow data is:
column 1 column 2 column 3 column 4 column 5 column 6 column 7
space 1-10 space 11-16 space 17-22 space 23-28 space 29-34 space 35-40 space 41-46 space 47-55

subbasin subbasin subbasin route route add add route save finish

1 1 1 2 2 5 5 2 9 0

1 2 3 4 5 6 7 8 8

1 2 3 1 2 4 6 3

1 2 5 3 7

0.000 0.000

0.000

The save command is specified in column 1 by the number 9. Column 2 lists the hydrograph storage location of the data to be saved in the event output file. The name of the event output file is listed in file.cio and usually possesses the .eve file extension. Only one save command is allowed in a simulation. The event file output is described in Chapter 44.

B.1.3 SUBWATERSHED DISCRETIZATION: INCORPORATING POINT SOURCE/UPSTREAM SIMULATION DATA

Point source and upstream simulation data may be incorporated into a run using one of four record commands: recday, recmon, recyear, and reccnst. The recday command reads data from a file containing loadings of different constituents for each day of simulation. The recmon command reads data from a file containing average daily loadings for each month. The recyear command reads data from a file containing average daily loadings for each year. The reccnst command reads in average annual daily loadings. The record command chosen to read in the data is a function of the detail of data available. To read in upstream simulation data, the recday command is always used. Assuming the subbasin delineation in Figure B-1 is used with one point source (sewage treatment plants) per subbasin, the watershed configuration file is:
column 1 column 2 column 3 column 4 column 5 column 6 column 7
space 1-10 space 11-16 space 17-22 space 23-28 space 29-34 space 35-40 space 41-46 space 47-55

subbasin subbasin subbasin recday add route recday add route add recday add add route finish

1 1 1 2 1 3 10 4 sub1.pnt 5 5 2 6 10 7 sub2.pnt 5 8 2 9 5 10 10 11 sub3.pnt 5 12 5 13 2 14 0

1 2 3 1 4 1 2 7 2 6 3 11 12 3 1 5

0.000

2 8 9

0.000

10 3 13

0.000

All of the record commands require 2 lines. On the first line, column 1 contains the command code for the specific record command, column 2 contains the hydrologic storage location where the data from the file is stored, and column 3 contains the file number. A different file number must be used for each point source of a specific type (e.g., all recday commands must have unique file numbers). The second line lists the name of the file containing the input data. A description of the four types of record files is given in Chapter 43.

B.1.4 SUBWATERSHED DISCRETIZATION: INCORPORATING RESERVOIRS

Water bodies located along the main channel are modeled using reservoirs. To incorporate a reservoir into a simulation, a routres command is used. There is no limitation on the number of reservoirs modeled. Assuming the subbasin delineation in Figure B-1 is used with one reservoir located at the outlet, the watershed configuration file is:
space 1-10 space 11-16 space 17-22 space 23-28 space 29-34 space 35-40 space 41-46 space 47-55

subbasin subbasin subbasin route route add add route routres finish

1 1 1 2 1 3 2 4 2 5 5 6 5 7 2 8 3 9 lakefork.res 0

1 2 3 1 1 2 2 4 5 6 3 3 7 1 8 lakefork.lwq

0.000 0.000

0.000 3

The routres command requires 2 lines. On the first line, the routres command is identified with the number 3 in column 1. Column 2 gives the hydrograph storage location where outflow data from the reservoir is stored. Column 3 lists the reservoir number. Column 4 gives the hydrograph storage location of the data to be routed through the reservoir. Column 5 lists the subbasin with which the reservoir is associated. A different reservoir number must be assigned to each reservoir and the numbers should be sequential beginning with 1. The second line lists two file names, the reservoir input file (.res) and the reservoir water quality file (.lwq).

B.1.5 SUBWATERSHED DISCRETIZATION: SAVING SIMULATION RESULTS FOR ONE LOCATION

Users often need to compare streamflow, sediment, nutrient and/or pesticide levels predicted by the model with levels measured in the stream. To save daily or hourly model output data for a particular location on the stream, the saveconc command is used. Assume there is a stream gage at the outlet of the watershed shown in Figure B-1 and that we want to compare simulated and measured streamflow for this location. Hydrograph storage location #8 stores the flow data for this location in the watershed, so this is the data we need to process to create the saveconc output file. The watershed configuration modified to process data for this location is:
column 1 column 2 column 3 column 4 column 5 column 6 column 7
space 1-10 space 11-16 space 17-22 space 23-28 space 29-34 space 35-40 space 41-46 space 47-55

subbasin subbasin subbasin route route add add route saveconc finish

1 1 1 2 1 3 2 4 2 5 5 6 5 7 2 8 14 8 strgage.out 0

1 2 3 1 2 4 6 3 1

1 2 5 3 7 0

0.000 0.000

0.000

The saveconc command requires 2 lines. On the first line, the saveconc command is identified with the number 14 in column 1. Column 2 gives the hydrograph storage location of the data to be processed for the saveconc output file. Column 3 lists the file number. Column 4 gives the print frequency (daily or hourly). More than one saveconc command may be used in a simulation. A different file number must be assigned to each saveconc output file and the file numbers should be sequential beginning with 1. The second line lists the name of the saveconc output file. The saveconc command differs from the save command in that it converts the mass amounts of water, sediment, and chemicals to units that are commonly used to report measured values. Output files produced by the saveconc command cannot be read into another SWAT runthe save command must be used to produce input for another simulation.

B.2 HILLSLOPE DISCRETIZATION

The hillslope discretization allows overland flow from one subbasin to flow onto the land area of another subbasin. As the name implies, this discretization allows SWAT to model hillslope processes. The hillslope discretization incorporates more detail into the watershed configuration file than the subwatershed discretization. The number of subbasins chosen to model the watershed will depend on the size of the watershed, the spatial relationship of different land uses to one another, the spatial detail of available input data and the amount of detail required to meet the goals of the project. Because this discretization scheme places more emphasis on land use, the subbasins are delineated so that there is one land use and soil per subbasin. The hillslope discretization can be combined with the subwatershed discretization to provide detailed modeling of particular land use areas while modeling the remaining land use areas with the more generalized approach. Useful applications of this discretization include: watersheds with concentrated animal feeding operations, watersheds where detailed modeling of filter strips is desired, and microwatersheds where the scale of the simulation allows detail about relative land use positions to be incorporated.

B.2.1 HILLSLOPE DISCRETIZATION: MODELING A DAIRY OPERATION

Assume a microwatershed containing a concentrated animal feeding operation with several different areas of land use and management is being modeled. Milking cows are confined in stalls. All waste produced by the milking cows is collected and applied over manure application fields also located in the microwatershed. The dry cows are kept in pastures. The pastured cows keep the areas adjacent to the farm buildings denuded of grass. Runoff from the denuded areas flows onto the pasture. Runoff from the pasture flows into a filter strip or buffer zone. Runoff exiting the filter strip enters the stream. The manure application fields are isolated from the rest of the dairy operation. Runoff from the application fields flows into a filter strip, and then enters the steam. Figure B-2 illustrates the relationship of land areas in the dairy operation. Areas of the microwatershed outside of the daily operation are forested.

Figure B-2: Spatial positioning of land areas in dairy operation.

This microwatershed will be divided into 6 subbasins: Subbasin 1: loafing area Subbasin 2: pasture Subbasin 3: filter strip associated with pasture Subbasin 4: waste application area Subbasin 5: filter strip associated with waste application area Subbasin 6: completely channelized stream and forest in microwatershed

Step 1: Write the subbasin command for each subbasin. (This command simulates the land phase of the hydrologic cycle.)
column 1 column 2 column 3 column 4 column 5 column 6 column 7
space 1-10 space 11-16 space 17-22 space 23-28 space 29-34 space 35-40 space 41-46 space 47-55

subbasin subbasin subbasin subbasin subbasin subbasin

1 1 1 1 1 1

1 2 3 4 5 6

1 2 3 4 5 6

Writing subbasin in space 1-10 is optional. The model identifies the configuration command by the code in column 1. The option of writing the command in space 1-10 is provided to assist the user in interpreting the configuration file. Column 2 is the hydrograph storage location number (array location) where data for the loadings (water, sediment, chemicals) from the subbasin are stored. Column 3 is the subbasin number. The subbasin number tells SWAT which input files listed in file.cio contain the data used to model the subbasin. Subbasin numbers are assigned sequentially in file.cio to each pair of lines after line 14. The files listed on lines 15 & 16 of file.cio are used to model subbasin 1, the files listed on lines 17 & 18 of file.cio are used to model subbasin 2, the files listed on lines 19 & 20 of file.cio are used to model subbasin 3, and so on. Step 2: Route the stream loadings. The hillslope discretization differs from the subwatershed discretization primarily in the method used to route loadings through the watershed. Loadings from subbasins are not routed through the subbasin if the flow leaving the subbasin is not completely channelized. For our example, subbasin 6 is the only subbasin completely channelized. Assume that runoff from the denuded areas (subbasin 1) is sheet flow, i.e. there are no rills, gullies or any other evidence of channelized flow in the denuded area. Runoff from the denuded area will be routed to the pasture (subbasin 2) using the route command:
column 1 column 2 column 3 column 4 column 5 column 6 column 7
space 1-10 space 11-16 space 17-22 space 23-28 space 29-34 space 35-40 space 41-46 space 47-55

route

1.000

As mentioned in the last step, column 1 is used to identify the command. Column 2 is the hydrograph storage location number identifying the location where results from the channelized portion of the route simulation are placed. In this instance, because there is no channelized flow, this storage location will contain no data.

Column 3 provides the number of the reach or subbasin the inputs are routed through. (The number of the reach in a particular subbasin is the same as the number of the subbasin.) The fraction of the loadings classified as overland flow are applied to the subbasin land area while the fraction of the loadings classified as channelized flow are routed through the main channel of the subbasin and are exposed to in-stream processes. Channelized flow has no interaction with the land area in the subbasin. Column 4 lists the number of the hydrograph storage location containing the data to be routed through the reach. The loadings from subbasin 1 are stored in hydrograph storage #1. Column 6 lists the fraction of overland flow. For completely channelized flow this fraction is zero. For 100% overland flow, this fraction is 1.00. The entire watershed configuration to this point looks like:
column 1 column 2 column 3 column 4 column 5 column 6 column 7
space 1-10 space 11-16 space 17-22 space 23-28 space 29-34 space 35-40 space 41-46 space 47-55

subbasin subbasin subbasin subbasin subbasin subbasin route

1 1 1 1 1 1 2

1 2 3 4 5 6 7

1 2 3 4 5 6 2

1.000

Assume that runoff from the pasture is slightly channelized (10% channels). Flow from the pasture is routed to the filter strip (subbasin 3) using the next route command:
column 1 column 2 column 3 column 4 column 5 column 6 column 7
space 1-10 space 11-16 space 17-22 space 23-28 space 29-34 space 35-40 space 41-46 space 47-55

subbasin subbasin subbasin subbasin subbasin subbasin route route

1 1 1 1 1 1 2 2

1 2 3 4 5 6 7 8

1 2 3 4 5 6 2 3

1 2

1.000 0.900

As mentioned previously, hydrograph storage location #7 contains no data because none of the runoff entering subbasin 2 is channelized. Consequently, when routing runoff leaving subbasin 2, this hydrograph storage location can be ignored. For subbasin 3, however, there will be data in hydrograph storage location #8 from the 10% of flow that is channelized in that subbasin. Loadings from subbasin 3 will enter the main stream in subbasin 6. The total loadings from the denuded area/pasture/filter strip section of the microwatershed are determined

by adding the runoff generated from subbasin 3 and the channelized flow routing results.
column 1 column 2 column 3 column 4 column 5 column 6 column 7
space 1-10 space 11-16 space 17-22 space 23-28 space 29-34 space 35-40 space 41-46 space 47-55

subbasin subbasin subbasin subbasin subbasin subbasin route route add

1 1 1 1 1 1 2 2 5

1 2 3 4 5 6 7 8 9

1 2 3 4 5 6 2 3 3

1 2 8

1.000 0.900

The loadings from simulation of the land phase of the hydrologic cycle in subbasin 3 are stored in hydrograph storage location #3 and the loadings from simulation of the channelized flow in subbasin 3 are stored in hydrograph location #8. The add command is specified in column 1 by the number 5. The hydrograph storage location numbers of the 2 data sets to be added are listed in columns 3 and 4. The summation results are stored in the hydrograph location number given in column 2. Net loadings from the denuded area/pasture/filter strip is stored in hydrograph location #9. Assume that the manure application area (subbasin 4) is well managed and all runoff from this area is overland flow (no channelized flow). To route flow from the application area to the associated filter strip (subbasin 5) a route command will be appended to the end of the configuration:
column 1 column 2 column 3 column 4 column 5 column 6 column 7
space 1-10 space 11-16 space 17-22 space 23-28 space 29-34 space 35-40 space 41-46 space 47-55

subbasin subbasin subbasin subbasin subbasin subbasin route route add route

1 1 1 1 1 1 2 2 5 2

1 2 3 4 5 6 7 8 9 10

1 2 3 4 5 6 2 3 3 5

1 2 8 4

1.000 0.900 1.000

Hydrograph storage location #10 contains no data because none of the runoff entering subbasin 5 is channelized. Consequently, when routing runoff leaving subbasin 5, this hydrograph storage location can be ignored. Net loadings from the waste application area/filter strip section of the watershed is stored in hydrograph location #5.

Flow through subbasin 6, which contains the stream, is completely channelized. All of the loadings for the stream must be summed together and then routed through the stream. There are 3 sources of loading to the stream: the denuded area/pasture/filter strip (hydrograph location #9), the waste application area/filter strip (hydrograph location #10), and the forest land area (hydrograph location #6). Add commands are used to sum the loadings.
column 1 column 2 column 3 column 4 column 5 column 6 column 7
space 1-10 space 11-16 space 17-22 space 23-28 space 29-34 space 35-40 space 41-46 space 47-55

subbasin subbasin subbasin subbasin subbasin subbasin route route add route add add

1 1 1 1 1 1 2 2 5 2 5 5

1 2 3 4 5 6 7 8 9 10 11 12

1 2 3 4 5 6 2 3 3 5 9 6

1 2 8 4 5 11

1.000 0.900 1.000

Flow is routed through the stream using a route command:

column 1 column 2 column 3 column 4 column 5 column 6 column 7
space 1-10 space 11-16 space 17-22 space 23-28 space 29-34 space 35-40 space 41-46 space 47-55

subbasin subbasin subbasin subbasin subbasin subbasin route route add route add add route

1 1 1 1 1 1 2 2 5 2 5 5 2

1 2 3 4 5 6 7 8 9 10 11 12 13

1 2 3 4 5 6 2 3 3 5 9 6 6

1 2 8 4 5 11 12

1.000 0.900 1.000

0.000

Step 3: Once the stream loadings have been routed to the watershed outlet, append a finish command line to signify the end of the watershed routing file.
column 1 column 2 column 3 column 4 column 5 column 6 column 7
space 1-10 space 11-16 space 17-22 space 23-28 space 29-34 space 35-40 space 41-46 space 47-55

subbasin subbasin subbasin subbasin subbasin subbasin route route add route add add route finish

1 1 1 1 1 1 2 2 5 2 5 5 2 0

1 2 3 4 5 6 7 8 9 10 11 12 13

1 2 3 4 5 6 2 3 3 5 9 6 6

1 2 8 4 5 11 12

1.000 0.900 1.000

0.000

B.2.2 HILLSLOPE DISCRETIZATION: COMBINING WITH SUBWATERSHED DISCRETIZATION

The hillslope discretization is a very detailed discretization scheme and is suited to small watersheds. However, it can be used in combination with the subwatershed discretization to provide detailed simulation of certain land uses in a large watershed whose spatial relationships are important to the study. As an example, assume that the dairy operation described in Section B.2.1 is located in a headwater region of the watershed example used in Section B.1. Figure B-3 illustrates the location of the dairy in the larger watershed. (Assume the microwatershed modeled in Section B.2.1 is subbasin B in Figure B-3.)

Figure B-3: Watershed with dairy operation

There are two options that may be used to combine the detailed modeling of the dairy with the less detailed modeling of the other land uses in the watershed. The first option is to model the dairy in a separate simulation and save the loadings from the microwatershed using the save command. These daily loadings will then be read into the simulation of the larger watershed using a recday command. The second option is to merge the watershed configuration given in Section B.2.1 with the watershed configuration given Section B.1.1

Option 1: Two separate runs. The watershed configuration file for simulation of the microwatershed with the dairy will be modified to save the outflow data to an event file. The name of the event file is specified as dairy.eve in the file.cio for the microwatershed simulation.
column 1 column 2 column 3 column 4 column 5 column 6 column 7
space 1-10 space 11-16 space 17-22 space 23-28 space 29-34 space 35-40 space 41-46 space 47-55

subbasin subbasin subbasin subbasin subbasin subbasin route route add route add add route save finish

1 1 1 1 1 1 2 2 5 2 5 5 2 9 0

1 2 3 4 5 6 7 8 9 10 11 12 13 13

1 2 3 4 5 6 2 3 3 5 9 6 6

1 2 8 4 5 11 12

1.000 0.900 1.000

0.000

Because the area in subbasin B is modeled in the microwatershed simulation, the area will not be directly modeled in the large watershed simulation. Instead, the data in the file dairy.eve will be read in and routed.
column 1 column 2 column 3 column 4 column 5 column 6 column 7
space 1-10 space 11-16 space 17-22 space 23-28 space 29-34 space 35-40 space 41-46 space 47-55

subbasin subbasin route recday add add route finish

1 1 2 10 dairy.eve 5 5 2 0

1 2 3 4 5 6 7

1 2 1 1 3 5 2

0.000

4 2 6

0.000

In the above configuration, subbasin A is subbasin 1, subbasin C is subbasin 2 and outflow from subbasin B is read in with the recday command.

Option 2: A combined simulation. In this simulation, the routing for the entire watershed is contained in one configuration file. We will include comment lines in this watershed configuration to identify the different portions of the watershed being simulated. Subbasin B will be divided into 6 separate subbasins numbered 1-6 with the same land use assignments listed in section B.2.1. Subbasin A is subbasin 7 in this simulation while subbasin C is subbasin 8.
column 1 column 2 column 3 column 4 column 5 column 6 column 7
space 1-10 space 11-16 space 17-22 space 23-28 space 29-34 space 35-40 space 41-46 space 47-55

* land phase for subbasin B subbasin 1 1 1 subbasin 1 2 2 subbasin 1 3 3 subbasin 1 4 4 subbasin 1 5 5 subbasin 1 6 6 * land phase for subbasin A subbasin 1 7 7 * land phase for subbasin C subbasin 1 8 8 * route flow through subbasin A route 2 9 7 7 0.000 * route flow through subbasin B route 2 10 2 1 1.000 route 2 11 3 2 0.900 add 5 12 3 11 route 2 13 5 4 1.000 add 5 14 12 5 add 5 15 6 14 route 2 16 6 15 0.000 * add outflow from subbasin A and B to loadings from subbasin C add 5 17 9 16 add 5 18 8 17 * route flow through subbasin C route 2 19 8 18 0.000 finish 0

Comment lines are denoted by an asterisk in the first space. When SWAT reads an asterisk in this location it knows the line is a comment line and does not process the line.

B.3 GRID CELL DISCRETIZATION

The grid cell discretization allows a user to capture a high level of spatial heterogeneity or variability in the simulation. The grid cells should be small enough to obtain homogenous land use, soil, and topographic characteristics for the area in each cell but large enough to keep the amount of data required for the run at a reasonable level. The routing methodology for the grid cell discretization is the same as that for the subwatershed discretization. The difference between the two discretization schemes lies in the average size of the subbasin and the method used to define subbasin boundaries. The GIS interfaces are currently not able to delineate a watershed using a grid cell discretization. However, there are plans to create a GIS tool capable of generating a grid cell discretization.

B.3.1 GRID CELL DISCRETIZATION: 9 CELLS

To illustrate the grid cell discretization, a simple nine-cell example will be used.

Figure B-4: Grid cell delineation with flow paths shown.

Step 1: Write the subbasin command for each cell. (This command simulates the land phase of the hydrologic cycle.)
column 1 column 2 column 3 column 4 column 5 column 6 column 7
space 1-10 space 11-16 space 17-22 space 23-28 space 29-34 space 35-40 space 41-46 space 47-55

subbasin subbasin subbasin subbasin subbasin subbasin subbasin subbasin subbasin

1 1 1 1 1 1 1 1 1

1 2 3 4 5 6 7 8 9

1 2 3 4 5 6 7 8 9

Writing subbasin in space 1-10 is optional. The model identifies the configuration command by the code in column 1. The option of writing the command in space 1-10 is provided to assist the user in interpreting the configuration file. Column 2 is the hydrograph storage location number (array location) where data for the loadings (water, sediment, chemicals) from the subbasin are stored. Column 3 is the subbasin number. The subbasin number tells SWAT which input files listed in file.cio contain the data used to model the subbasin. Subbasin numbers are assigned sequentially in file.cio to each pair of lines after line 14.

The files listed on lines 15 & 16 of file.cio are used to model subbasin 1, the files listed on lines 17 & 18 of file.cio are used to model subbasin 2, the files listed on lines 19 & 20 of file.cio are used to model subbasin 3, and so on. Step 2a: Route the stream loadings through the flow path network. Begin by routing the headwater subbasin loadings through the main channel of the respective subbasin. (Headwater subbasins are those with no subbasins upstream.) Referring to Figure B-4, subbasins 1, 3, 6 and 7 are headwater subbasins.
column 1 column 2 column 3 column 4 column 5 column 6 column 7
space 1-10 space 11-16 space 17-22 space 23-28 space 29-34 space 35-40 space 41-46 space 47-55

subbasin subbasin subbasin subbasin subbasin subbasin subbasin subbasin subbasin route route route route

1 1 1 1 1 1 1 1 1 2 2 2 2

1 2 3 4 5 6 7 8 9 10 11 12 13

1 2 3 4 5 6 7 8 9 1 3 6 7

1 3 6 7

0.000 0.000 0.000 0.000

As mentioned in the last step, column 1 is used to identify the command. Column 2 is the hydrograph storage location number identifying the location where results from the route simulation are placed. Column 3 provides the number of the reach, or main channel, the inputs are routed through. The number of the reach in a particular subbasin is the same as the number of the subbasin. Column 4 lists the number of the hydrograph storage location containing the data to be routed through the reach. Column 6 lists the fraction of overland flow. For the grid cell discretization, this value will always be zero. Step 2b: Route the stream loadings through the reach network. Use the add and route commands to continue routing through the watershed. First, add the outflow from subbasin 1 to the loadings from subbasin 4 and route the total through the channel in subbasin 4.

column 1 column 2 column 3 column 4 column 5 column 6 column 7

space 1-10 space 11-16 space 17-22 space 23-28 space 29-34 space 35-40 space 41-46 space 47-55

subbasin subbasin subbasin subbasin subbasin subbasin subbasin subbasin subbasin route route route route add route

1 1 1 1 1 1 1 1 1 2 2 2 2 5 2

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15

1 2 3 4 5 6 7 8 9 1 3 6 7 10 4

1 3 6 7 4 14

0.000 0.000 0.000 0.000 0.000

The loadings from the outlet of subbasin 1 are stored in hydrograph location #10; the loadings from subbasin 4 are stored in hydrograph location #4. The add command is specified in column 1 by the number 5. The hydrograph storage location numbers of the 2 data sets to be added are listed in columns 3 and 4. The summation results are stored in the hydrograph location number given in column 2. Next, add the outflow from subbasin 3 to the loadings from subbasin 2 and route the total through the channel in subbasin 2.
column 1 column 2 column 3 column 4 column 5 column 6 column 7
space 1-10 space 11-16 space 17-22 space 23-28 space 29-34 space 35-40 space 41-46 space 47-55

subbasin subbasin subbasin subbasin subbasin subbasin subbasin subbasin subbasin route route route route add route add route

1 1 1 1 1 1 1 1 1 2 2 2 2 5 2 5 2

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17

1 2 3 4 5 6 7 8 9 1 3 6 7 10 4 11 2

1 3 6 7 4 14 2 16

0.000 0.000 0.000 0.000 0.000 0.000

Next, add the outflow from subbasin 2 and 4 to the loadings from subbasin 5 and route the total through the channel in subbasin 5.
column 1 column 2 column 3 column 4 column 5 column 6 column 7
space 1-10 space 11-16 space 17-22 space 23-28 space 29-34 space 35-40 space 41-46 space 47-55

subbasin subbasin subbasin subbasin subbasin subbasin subbasin subbasin subbasin route route route route add route add route add add route

1 1 1 1 1 1 1 1 1 2 2 2 2 5 2 5 2 5 5 2

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20

1 2 3 4 5 6 7 8 9 1 3 6 7 10 4 11 2 15 18 5

1 3 6 7 4 14 2 16 17 5 19

0.000 0.000 0.000 0.000 0.000 0.000

0.000

Next, add the outflow from subbasin 5 and 7 to the loadings from subbasin 8 and route the total through the channel in subbasin 8.
column 1 column 2 column 3 column 4 column 5 column 6 column 7
space 1-10 space 11-16 space 17-22 space 23-28 space 29-34 space 35-40 space 41-46 space 47-55

subbasin subbasin subbasin subbasin subbasin subbasin subbasin subbasin subbasin route route route route add route add route add add route add add route

1 1 1 1 1 1 1 1 1 2 2 2 2 5 2 5 2 5 5 2 5 5 2

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23

1 2 3 4 5 6 7 8 9 1 3 6 7 10 4 11 2 15 18 5 20 21 8

1 3 6 7 4 14 2 16 17 5 19 13 8 22

0.000 0.000 0.000 0.000 0.000 0.000

0.000

0.000

Next, add the outflow from subbasin 8 and 6 to the loadings from subbasin 9, route the total through the channel in subbasin 9, and append a finish command line to signify the end of the watershed routing file.
column 1 column 2 column 3 column 4 column 5 column 6 column 7
space 1-10 space 11-16 space 17-22 space 23-28 space 29-34 space 35-40 space 41-46 space 47-55

subbasin subbasin subbasin subbasin subbasin subbasin subbasin subbasin subbasin route route route route add route add route add add route add add route add add route finish

1 1 1 1 1 1 1 1 1 2 2 2 2 5 2 5 2 5 5 2 5 5 2 5 5 2 0

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26

1 2 3 4 5 6 7 8 9 1 3 6 7 10 4 11 2 15 18 5 20 21 8 23 24 9

1 3 6 7 4 14 2 16 17 5 19 13 8 22 12 9 25

0.000 0.000 0.000 0.000 0.000 0.000

0.000

0.000

0.000

As illustrated in section B.2.2 for the hillslope discretization, it is possible to combine the grid cell discretization with the subwatershed discretization to provide detailed modeling of portions of a large watershed while treating less significant areas in the more generalized approach used in the subwatershed discretization.