Professional Documents
Culture Documents
ArcGIS-SWAT A Geodata Model and GIS Interface For
ArcGIS-SWAT A Geodata Model and GIS Interface For
ArcGIS-SWAT A Geodata Model and GIS Interface For
net/publication/227518606
Article in JAWRA Journal of the American Water Resources Association · March 2006
DOI: 10.1111/j.1752-1688.2006.tb03839.x
CITATIONS READS
202 5,129
7 authors, including:
Huidae Cho
New Mexico State University
69 PUBLICATIONS 496 CITATIONS
SEE PROFILE
All content following this page was uploaded by Janghwoan Choi on 14 September 2018.
1Paper No. 04087 of the Journal of the American Water Resources Association (JAWRA) (Copyright © 2006). Discussions are open until
October 1, 2006.
2Respectively, (Olivera) Assistant Professor of Civil Engineering, (Valenzuela, Choi, Cho, Koka, Agrawal) Graduate Research Assistants,
Texas A&M University, 3136 TAMU, College Station, Texas 77843; (Srinivasan) Associate Professor of Biological and Agricultural Engineer-
ing, Texas A&M University, 1500 Research Parkway, Suite 221E, College Station, Texas 77845 (E-Mail/Olivera: folivera@civil.tamu. edu).
ArcGIS-SWAT has been developed for the ArcGIS Microsoft Access), however, cannot access the geo-
platform. The ArcGIS-SWAT data model stores SWAT graphic information in the geodatabases. Geodatabase
geographic, numeric, and text input data and results. tables are object classes in which each row represents
The geodatabase data structure, which is that of a an object and each column stores an attribute of the
relational database with the capability of storing geo- object. Feature classes are particular cases of object
graphic information in addition to numbers and text, classes in which each object is additionally attributed
was used for the data model. Therefore, a geodatabase with a feature (i.e., a geographic shape). Feature
is proposed as the repository of all the spatial and classes collect features of a single type, so that they
temporal information of a SWAT simulation, as are either point feature classes, line feature classes,
opposed to a series of text files. Likewise, the ArcGIS- or polygon feature classes. Furthermore, feature
SWAT interface uses ArcObjects (Zeiler, 2001), which classes that share the same spatial extent can be col-
conform to the Component Object Model (COM) proto- lected in feature datasets. Within feature datasets,
col and therefore facilitate the use, within ArcGIS- geometric networks can be built based on line feature
SWAT, of already available functionalities in other classes, which establish topologic relationships among
Windows-based applications. In particular, the use of their elements. Finally, relationship classes can be
Microsoft Excel and MATLAB for result visualization created to associate objects of different classes
and statistical analysis is demonstrated. Another fea- through key fields and can be stored as part of the
ture of ArcGIS-SWAT is its capability to georeference geodatabase.
the hydrologic response units (HRUs), which allows a Maidment (2002) pioneered the use of geodatabase
more accurate calculation of the model parameters data structures in water resources engineering by
than what would be obtained if they were averaged developing the ArcHydro data model. ArcHydro is a
over the subbasins. geospatial and temporal data model that supports
Integration with other hydrologic models is accom- hydrologic simulation models but is not a simulation
plished through the sharing of geographic and hydro- model itself. In ArcHydro, the structure of a hydrolog-
logic data. For this purpose, hydrologic objects (e.g., ic system is defined around the stream geometric net-
watershed polygons) and their corresponding parame- work, in which links and junctions are defined.
ters (e.g., watershed times of concentration) are Drainage areas are related to network junctions, and
exported from the ArcGIS-SWAT geodatabase to a time series are related to monitoring points in the
not-model-specific hub geodatabase, from which they map, which in turn are related to network junctions.
can be imported by another interface for use in a dif- Thus, the stream network and the relationships
ferent model. By implementing the hub geodatabase among the different hydrologic elements and the net-
concept, model integration consists of interfacing each work junctions constitute the backbone of the ArcHy-
model to the hub rather than to each of the other dro representation of a system (Olivera et al., 2002).
models. As an example, it is presented how HMS – a The ArcHydro data model was developed with the
computer application for flood analysis developed by envisioned purpose of storing in an organized fashion
the Hydrologic Engineering Center (HEC) (USACE, spatial and time series data to support most (if not
2005) and not related to SWAT – uses information all) hydrologic models. However, the SWAT data
originally developed by the ArcGIS-SWAT interface structure does not include all of the elements of
and stored in the ArcGIS-SWAT data model. ArcHydro and, more importantly, includes a number
of elements not considered in it. Among the elements
of ArcHydro not included in the SWAT data structure
are the channel cross sections and profile lines, the
THE GEODATABASE DATA STRUCTURE stream geometric network (since the network topology
AND ARCHYDRO in SWAT is based on attributes), and those that are
redundantly stored as hydrographic elements and as
The ArcGIS-SWAT data model is based on the geo- drainage elements. The SWAT data structure, on the
database data structure. Geodatabases are relational other hand, includes many land and stream parame-
databases that can also store geographic features ters to model the soil water balance, plant growth,
(MacDonald, 1999). That is, a geodatabase is a collec- irrigation and fertilization practices, and pollutant
tion of tables whose fields can store a geographic transport that are not included in ArcHydro. Hence,
shape (i.e., a point, a line, or a polygon), a string, or a using ArcHydro as the SWAT data model would have
number and that are related to each other through required such a level of customization that it would
key fields. Regardless of the number of tables and have left little of its original design, and it was decid-
relationships in a geodatabase, it is stored in a single ed to develop a new geodata model specifically for
file, and its contents can be explored using database SWAT.
management systems (DBMS). Non-GIS DBMS (e.g.,
classes. These relationships are represented by Soil and land use data can be provided by the user;
arrows in Figure 2. For example, the relationship however, tools have been included for easy use of soil
between [Outlet] and [Subbasin] is established by data from the State Soil Geographic (STATSGO)
storing the HYDROID value of the subbasin outlet database (USDA-NRCS, 1995) and lookup tables for
point in the OUTLET field of the subbasin polygon. converting different land use classifications to the
Note that in <TimeSeries>, the field FEATUREID SWAT classification.
stores the HYDROID value of the corresponding fea- The STATSGO database defines map units, each of
ture. The feature classes also have fields related to which consists of one or more polygonal areas of the
their geometry (i.e., AREA for polygons and LENGTH same soil type. This database, whose format is differ-
for lines), and [Reach], in particular, has FNODE and ent from the one defined in USDA-NRCS (1995),
TNODE that store the upstream and downstream includes one feature class of map-unit polygons per
points of each reach segment, which are used to estab- state, called [(State Name)], and one object class per
lish the stream network topology. Other attributes map unit, called <(Map unit)>. Texas, for example,
such as elevation, slope, and location (i.e., longitude has 633 map units represented by 4,031 polygons, and
and latitude) are also included. consequently if the study area were in Texas, a fea-
ture class [Texas] with 4,031 map unit polygons and
633 map unit object classes <TX001>, <TX002>, …
<TX633> would be included in the static geodatabase.
In these object classes, the records refer to the differ-
ent soil components of the map unit, and the fields
store soil properties of the component and of up to 10
layers of the component, as well as the percentage of
the component in the map unit. To speed up the
database operations, only the feature and object class-
es of the states needed are added to the static geo-
database from a source set of 48 geodatabases of
STATSGO data (i.e., one geodatabase per state of the
conterminous United States). The reader is referred
to USDA-NRCS (1995) for detailed STATSGO docu-
mentation on soil map units, components, and layers.
Similarly, land use data consist of polygonal areas
within which a single land use is found. Land uses
can be classified with any land use classification sys-
tem but should be converted to the SWAT classifica-
tion system for implementation with SWAT. Thus, a
lookup table, that the user can modify if needed, has
been included to define the equivalence of the Ander-
son et al. (1976), National Land Cover Dataset
(NLCD) (USGS, 2004a), and SWAT land use classifi-
cation systems.
Regardless of the sources of the input data, one soil
type grid and one land use grid are created. After
identifying the grid cells that have the same soil type
and land use within each subbasin, they are grouped
together and converted into polygons that represent
HRUs. Thus, in the resulting polygon feature class,
called [PolyHRU], the features have a unique combi-
nation of input data. As can be seen in Figure 2,
Figure 1. Feature Classes Generated
by the Watershed Delineator.
[PolyHRU] polygons have a unique identification
number stored in field HYDROID, which is used to
establish relationships with [SubBasin] and
HRU Definition <TimeSeries>.
Additionally, ArcGIS-SWAT calculates runoff curve
numbers (USDA-SCS, 1972) and terrain slopes per
The HRU definition module identifies unique com- HRU. Runoff curve numbers are calculated based on
binations of soil and land use within each subbasin.
Figure 2. Attributes of and Relationships Among the Feature Classes and the Time Series Object Class.
Rectangular boxes represent feature and object classes. Text on gray background indicates the class
name, and text on white background indicates the class attributes. Arrows indicate relationships.
of weather stations in the static geodatabase, called stored in the dynamic geodatabase. The term “On-
[USWeather]. [USWeather] includes the location as screen” under the header “Input/Other” refers to
well as multiannual statistics of temperature, precipi- input entered by the modeler interactively; and “Time
tation, solar radiation, and wind speed for each of the series” under the same header refers to a pointer to a
12 months of the year for 1,041 National Climatic time series file. The object classes under the header
Data Center (NCDC) stations (USEPA, 2004). The “Output/Dynamic” are created to organize the input
ArcGIS-SWAT weather generation module assigns entered interactively by the user. It should be noted
one station in [USWeather] to each subbasin in [Sub- that user input is unavoidable in an application that
Basin] based on proximity to its centroid and stores assesses the effect of human actions and land man-
the matches in object class <SubWGn> and the agement practices on water quantity and quality.
weather statistics of the assigned stations in object In the process of preparing the input files, soil type
class <WGn>. and land use data are used to populate the HRU files.
Alternatively, observed weather time series at user- Soils information of the predominant STATSGO com-
provided stations can be used. As in the previous case, ponent in the HRU is transferred to the HRU soil files
the weather generation module assigns a station to (HRU name).sol. Likewise, land use information is
each subbasin based on proximity to its centroid, but used to select, from a database of default values, HRU
now it stores the matches in object classes <SubPcp>, management parameters such as the support practice
<SubTmp>, <SubSlR>, <SubWnd>, and <SubHmd> factor of the modified universal soil loss equation
and the time series in object classes <Pcp>, <Tmp>, (Williams, 1995) or the percentage of the area where
<SlR>, <Wnd>, and <Hmd> for precipitation, temper- specific land management practices apply, such as
ature, solar radiation, wind speed, and relative planting, irrigating, fertilizing, harvesting, or street
humidity, respectively. Finally, the weather time sweeping, and transfer them to the HRU manage-
series are redundantly stored in <TimeSeries> (where ment files (HRU name).mgt.
all input and output temporal information is consoli- ArcGIS-SWAT also allows the user to modify the
dated), and all matched weather stations are append- dynamic and static geodatabases and, after changes
ed to [MonitoringPoints] and related to <TimeSeries>. are made, create a new set of input files that reflect
these changes. Thus, the information in the geo-
databases is always updated and consistent with the
Preparing SWAT Input Files input files.
basins.cod Input control code file: Specifies the length of the On screen <cod>
simulation, the printing frequency and selected
options for various processes.
basins.bsn Basin input file: Stores watershed parameters [Watershed] On screen <bsn>
pcp.pcp (*) Precipitation file: Stores daily measured precipitation <Pcp> (*)
for a number of gauges.
tmp.tmp (*) Temperature file: Stores daily measured maximum <Tmp> (*)
and minimum temperature for a number of gauges.
slr.slr (*) Solar radiation file: Stores daily solar radiation for <SlR> (*)
a number of gauges.
wnd.wnd (*) Wind file: Stores daily average wind speed for a <Wnd> (*)
number of gauges.
hmd.hmd (*) Humidity file: Stores daily relative humidity for a <Hmd> (*)
number of gauges.
pet.pet (*) Potential evapotranspiration file: Stores daily potential Time series (*)
evapotranspiration for the watershed.
crop.dat Land cover and plant growth file: Contains plant <Crop>
growth parameters for all land covers in the watershed.
(Subbasin name).pnd (*) Pond/wetland file: Contains information for impound- – [SubBasin] On screen <Pnd>
ments within the subbasin.
(Subbasin name).wus (*) Water use file: Contains information for consumptive – [SubBasin] On screen <WUs>
water use in the subbasin.
(Subbasin name).rte Main channel file: Contains parameters governing water – [SubBasin] On screen <RTE>
and sediment movement in the main channel of the
subbasin.
(Subbasin name).swq (*) Stream water quality file: Contains parameters to model – [SubBasin] On screen <SQW>
pesticide and QUAL2E nutrient transformations in the
main channel of the subbasin.
(HRU name).sol Soil file: Contains information about the physical – [PolyHRU], On screen <Sol>
properties of the soils in the HRU. <(Map Unit)>
(HRU name).chm (*) Soil chemical file: Contains information about the initial – [PolyHRU] On screen <Chm>
nutrient and pesticide levels of the soil in the HRU.
(HRU name).gw Ground water file: Contains information about the – [PolyHRU] On screen <GW>
shallow and deep aquifer in the subbasin.
(HRU name).mgt Land management file: Contains management scenarios <Irr> [PolyHRU] On screen <Mgt1>,
and specifies the land cover in the HRU. <MgtType>, <Mgt2>
<MgtDate>,
<MgtSCS>
basins.res (*) Reservoir file: Contains parameters to model the movement – [SubBasin] On screen <Res>
of water and sediment through a reservoir.
basins.lwq (*) Lake water quality file: Contains parameters to model the – [SubBasin] On screen <Res>
movement of nutrients and pesticides through a reservoir.
recday.dat (*), Point source discharge files: Contain information about [MonitoringPoint] On-screen
recmon.dat (*), loadings to the channel network from point sources.
recyear.dat (*)
reccnst.dat (*)
model geodatabase and the hub geodatabase, inde- ArcGIS-SWAT. It has been presented here only to
pendently of other models. According to this stress the advantages of the use of the geodatabase
approach, the number of required protocols would and hub geodatabase approach.
increase linearly with the number of models, because
one protocol would be needed per model. On the con-
trary, if no hub geodatabase were used and data were
transferred between each match of two model geo- APPLICATION
databases, the number of protocols would be equal to
the combination of the number of models taken two at ArcGIS-SWAT was applied to the Upper Seco
a time, which is equal to where n is the number of Creek in Central Texas for which studies have been
models. The hub geodatabase can be as simple or com- conducted in the past (Srinivasan and Arnold, 1994;
plex as needed, depending on the models that will be Baird et al., 1996; Brown and Raines, 2002) and data
integrated and on the data that will be shared. The are available. The Upper Seco Creek is part of the
hub-geodatabase concept stems from Olivera et al. Nueces basin (Figure 3). The study area was the
(2003), in which ArcHydro (Maidment, 2002) was pro- catchment of U.S. Geological Survey (USGS) gauging
posed as the hub geodatabase. However, the point station 08201500 (Seco Creek at Miller Ranch near
conveyed here is that any geodatabase that can store Utopia), which has a drainage area of 116 km2.
the hydrologic elements common to the models that
are being integrated (including ArcHydro) can be used
as the hub geodatabase.
The hub geodatabase presented here addresses the
hydrologic elements and their topologic relationships
and is suitable for integrating models that share the
same watershed structure and stream network. It
includes five feature classes: [Stream], [ExitPoint],
[DrainageArea], [Lake], and [Station]. [Stream] stores
the segments of the channel network; [ExitPoint]
stores the points on the channel network from which
drainage areas are delineated; [DrainageArea] stores
the incremental drainage area of each point in [Exit-
Point]; [Lake] stores outlet points of water bodies on
the channel network from which drainage areas are
delineated; and [Station] stores the points where pre- Figure 3. The Seco Creek Watershed is Part of the Nueces
cipitation, flow gauging, and/or water quality moni- River Basin (in gray) in Texas. Points 2941250992554 and
2937170992513 are the rain gauges located at 99°25´54´´W,
toring stations are located. All features in the five 29°41´25´´N and 99°25´13´´W, 29°37´17´´N; and point
feature classes have a unique identification number USGS08201500 is the flow gauging station located at
stored in a field called ID. Additionally, the features 99°24´10´´W, 29°34´23´´N. The stream highlighted in
are cross referenced through the ID field so that black is the longest flow path in the watershed.
drainage areas are related to their exit points,
streams are related to the drainage area where they
are located, and lakes are related to the exit point Daily precipitation data were obtained from two
that represents them. Likewise, [Stream] includes stations set as part of the Seco Creek Water Quality
fields FNODE and TNODE that store identification Demonstration Project (Brown et al., 1998; Brown and
codes of the upstream and downstream nodes of the Raines, 2002) (Figure 3). Likewise, daily flow data
segments, which are used for establishing the net- were obtained for USGS flow gauging station
work topology. 08201500 (USGS, 2006) (Figure 3). Temperature,
Once the hub geodatabase is populated – for exam- solar radiation, wind, and humidity data were gener-
ple, by copying features and attributes from the ated from the weather statistics stored in [USWeath-
SWAT geodatabases – its contents can be used by er]. Topographic data in DEM format, with a
another model interface. As an application example, horizontal resolution of 10 m, were obtained from
the use of data developed by ArcGIS-SWAT and USGS (2004b). Streams were delineated for drainage
stored in the hub geodatabase for creating an HEC- areas greater than 2 km2 (i.e., 20,000 DEM cells), and
HMS model is demonstrated. The tool to retrieve the a total of 39 stream-subbasin-outlet sets were identi-
data from the hub geodatabase and format it for fied (Figure 1). Land use data in grid format, with a
HEC-HMS is a separate application and is not part of horizontal resolution of 30 m, were taken from NLCD
c = α vβpeak (1)
Likewise, the tools for visualization and statistical of the geodatabase capability to store geographic
analysis of the SWAT output called MS Excel COM information, it constitutes a complete repository of a
objects and used their functionality within ArcGIS for simulation’s data and results, something not possible
plotting the time series of monthly sediment load with the SWAT text input and output files.
(Figure 8a) and monthly sediment load as a function
of the monthly flow (Figure 8b) and performing statis-
tical analysis (i.e., trend line). Correlation and regres-
sion analysis, as well as analysis of variance (ANOVA)
can also be performed by MS Excel but are not dis-
cussed here. In these plots, it was observed that the
sediment load was concentrated in a few number of
months and that it was correlated to the monthly flow
with an r2 of 0.92. Similarly, the tools called MATLAB
COM objects and used their functionality for develop-
ing a three-dimensional plot of the flow profile of the
longest flow path in the watershed (Figure 8c) (the
longest flow path has been highlighted in black in
Figure 3). This three-dimensional plot allows one to
observe the flow at a given point over time and the
flow at a given time over the entire stream. Variables
other than flow and sediment load can also be plotted (a)
and analyzed.
Finally, the streams and watersheds delineated by
ArcGIS-SWAT and stored in the dynamic geodatabase
were copied to the hub geodatabase, from which
another application (unrelated to ArcGIS-SWAT)
retrieved them and created a topologically correct
schematic of the watershed for hydrologic analysis
with HEC-HMS (Figure 9). Thus, it is demonstrated
that a hub geodatabase can be used to share geo-
graphic data between different applications and that
the use of data developed by ArcGIS-SWAT is not lim-
ited to SWAT.
CONCLUSIONS
(b)
ACKNOWLEDGMENTS
LITERATURE CITED
A feature of ArcGIS-SWAT is its capability to geo-
reference the HRUs, which allows accounting for the American Society of Civil Engineers, 1993. Criteria for Evaluation
HRU’s location within the subbasin and the estima- of Watershed Models. ASCE Task Committee on the Definition
tion of individual parameter values, without lumping of Criteria for Evaluation of Watershed Models of the Watershed
them over their subbasin. However, the quantification Management Committee, Irrigation and Drainage Committee.
Journal of Irrigation and Drainage Engineering 119(3):429-442.
of the effect of accounting for the HRU’s location on Anderson, J.R., E.E. Hardy, J.T. Roach, and R.E. Witmer, 1976. A
flows and loads was beyond the scope of this paper. Land Use and Land Cover Classification System for Use With
The use of Monte Carlo simulations in combination Remote Sensor Data. Geological Survey Professional Paper 964,
with the ArcGIS-SWAT data model allows the estima- U.S. Government Printing Office, Washington D.C. Available at
tion of the uncertainty of the SWAT results by produc- http://landcover.usgs.gov/pdf/anderson.pdf. Accessed on April 21,
2004.
ing frequency distributions of the variables rather Arnold, J.G., R. Srinivasan, R.S. Muttiah, and J.R. Williams, 1998.
than a single value. By generating results such as Large Area Hydrologic Modeling and Assessment – Part I:
“there is a 10 percent chance that the median sedi- Model Development. Journal of the American Water Resources
ment concentration will be greater than 900 mg/l,” the Association (JAWRA) 34(1):73-89.
modeler is provided valuable information for inter- Baird, C., M. Jennings, D. Ockerman, and T. Dybala, 1996. Charac-
terization of Nonpoint Sources and Loadings to the Corpus
preting the SWAT output. Likewise, the use of pro- Christi Bay National Estuary Program Study Area. Corpus
gramming objects that conform the COM protocol Christi Bay National Estuary Program CCBNEP–05, 226 pp.,
allowed the implementation of functionality of other Texas Natural Resources Conservation Commission (TNRCC),
Windows-based applications within ArcGIS. In partic- Austin, Texas.
ular, the use of MS Excel functionality for plotting Bian, L., H. Sun, C. Blodgett, S. Egbert, L. WeiPing, R. LiMei, and
A. Koussis, 1996. An Integrated Interface System to Couple the
and regression analysis as well as of MATLAB func- SWAT Model and ARC/INFO. In: Proceedings of the 3rd Inter-
tionality for three-dimensional plotting was demon- national Conference on Integrating GIS and Environmental
strated. For model integration, the use of a hub Modeling. U.S. National Center for Geographic Information and
geodatabase that stores geographic and hydrologic Analysis, Santa Fe, New Mexico, CD-ROM.
data relevant to different models is proposed and Brown, D. and T. Raines, 2002. Simulation of Flow and Effects of
Best Management Practices in the Upper Seco Creek Basin,
demonstrated. In particular, it was presented how
South-Central Texas, 1991-98. U.S. Geological Survey Water
information developed by ArcGIS-SWAT for use by Resources Investigations Report 02-4249, Austin, Texas.
SWAT was transferred to the hub geodatabase, from Brown, D., R. Slattery, and J. Gilhousen, 1998. Summary Statistics
which it was retrieved by another application and and Graphical Comparisons of Historical Hydrologic and Water-
used to create an HMS model for flood analysis. It is Quality Data, Seco Creek Watershed, South-Central Texas. U.S.
Geological Survey Open-File Report 98-627, 37 pp.
envisioned that the use of the hub geodatabase con-
Di Luzio, M., R. Srinivasan, and J.G. Arnold, 1998. Watershed Ori-
cept will ease model integration. ented Non-point Pollution Assessment Tool. In: Proceedings of
With respect to previous SWAT GIS interfaces, the 7th International Conference on Computers in Agriculture.
ArcGIS-SWAT takes advantage of programming tech- American Society of Agricultural Engineers, St. Joseph, Michi-
nology – such as the geodatabase data structure and gan, pp. 233-241.
Di Luzio, M., R. Srinivasan, and J.G. Arnold, 2002. Integration of Olivera, F., D.R. Maidment, and D. Honeycutt, 2002. HydroNet-
Watershed Tools and SWAT Model Into BASINS. Journal of the works. In: ArcHydro: GIS for Water Resources, D.R. Maidment
American Water Resources Association (JAWRA) 38(4):1127- (Editor). ESRI Press, Redlands, California, pp. 33-53.
1141. Rosenthal, W.D. and D.W. Hoffman, 1999. Hydrologic Modeling/GIS
Di Luzio, M., R. Srinivasan, J.G. Arnold, and S.L. Neitsch, 2000. as an Aid in Locating Monitoring Sites. Transactions ASAE 42
Soil and Water Assessment Tool – ArcView GIS Interface Manu- (6):1591-1598.
al – Version 2000. Grassland, Soil and Water Research Labora- Santhi, C., J.G. Arnold, J.R. Williams, W.A. Dugas, R. Srinivasan,
tory, Agricultural Research Service and Blackland Research and L.M. Hauck, 2001. Validation of the SWAT Model on a
Center, Texas Agricultural Experiment Station, Temple, Texas. Large River Basin With Point and Nonpoint Sources. Journal of
Eckhardt, K. and J.G. Arnold, 2001. Automatic Calibration of a Dis- American Water Resources Association (JAWRA) 37(5):1169-
tributed Catchment Model. Journal of Hydrology 251(2001):103- 1188.
109. Spruill, C.A., S.R. Workman, and J.L. Taraba, 2000. Simulation of
Eckhardt, K., L. Breuer, and H.G. Frede, 2003. Parameter Uncer- Daily and Monthly Stream Discharge From Small Watersheds
tainty and the Significance of Simulated Land Use Change Using the SWAT Model. Transactions ASAE 43(6):1431-1439.
Effects. Journal of Hydrology 273(2003):164-176. Srinivasan, R. and J.G. Arnold, 1994. Integration of a Basin-Scale
Fontaine, T.A., T.S. Cruickshank, J.G. Arnold, and R.H. Hotchkiss, Water Quality Model With GIS. Journal of the American Water
2002. Development of a Snowfall-Snowmelt Routine for Moun- Resources Association (JAWRA) 30(3):453-462.
tainous Terrain for SWAT. Journal of Hydrology 262(2002):209- Tripathi, M.P., R.K. Panda, and N.S. Raghuwanshi, 2003. Identifi-
223. cation and Prioritization of Critical Sub-Watersheds for Soil
Hanratty, M.P. and H.G. Stefan, 1998. Simulating Climate Change Conservation Management Using the SWAT Model. Biosystems
Effects in a Minnesota Agricultural Watershed. Journal of Envi- Engineering 85 (3):365-379.
ronmental Quality 27:1524-1532. USACE (U.S. Army Corps of Engineers), 2005. Hydrologic Modeling
Jensen, S.K. and J.O. Domingue, 1988. Extracting Topographic System – HEC-HMS – User’s Manual, Vol. 3.0.0. U.S. Army
Structure From Digital Elevation Data for Geographic Informa- Corps of Engineers-Hydrologic Engineering Center, CPD-74A,
tion System Analysis. Photogrammetric Engineering and Davis, California.
Remote Sensing 54(11). USDA-NRCS (U.S. Department of Agriculture-Natural Resources
King, K.W., J.G. Arnold, and R.L. Bingner, 1999. Comparison of Conservation Service), 1995. State Soil Geographic (STATSGO)
Green-Ampt and Curve Number Methods on Goodwin Creek Database – Data User Guide. U.S. Department of Agriculture,
Watershed Using SWAT. Transactions ASAE 42(4):919-925. Natural Resources Conservation Service, Miscellaneous Publica-
MacDonald, A., 1999. Building a Geodatabase. ESRI Press, Red- tion Number 1492, Washington D.C.
lands, California. USDA-SCS (U.S. Department of Agriculture-Soil Conservation Ser-
Maidment, D.R. (Editor), 2002. ArcHydro: GIS for Water Resources. vice), 1972. National Engineering Handbook – Section 4:
ESRI Press, Redlands, California. Hydrology. U.S. Department of Agriculture, Soil Conservation
Martinec, J. and A. Rango, 1989. Merits of Statistical Criteria for Service, Washington, D.C.
the Performance of Hydrological Models. Water Resources Bul- USEPA (U.S. Environmental Protection Agency), 2004. BASINS:
letin 25(2):421-432. Better Assessment Science Integrating Point and Nonpoint
Nash, J.E. and J.E. Sutcliffe, 1970. River Flow Forecasting Through Sources – NOAA’s National Climatic Data Centers (NCDC)
Conceptual Models – Part 1-A: Discussion of Principles. Journal Weather Data Management (WDM) Stations Point Locations in
of Hydrology 10(82):282-290. the United States, Puerto Rico, and the U.S. Virgin Islands.
Neitsch, S.L., J.G. Arnold, J.R. Kiniry, J.R. Williams, and K.W. Available at http://www.epa.gov/waterscience/basins/metadata/
King, 2002a. Soil and Water Assessment Tool – Theoretical Doc- wdm.htm. Accessed on September 30, 2004.
umentation – Version 2000. Grassland, Soil and Water Research USGS (U.S. Geological Survey), 2004a. National Land Cover
Laboratory, Agricultural Research Service and Blackland Dataset 1992 (NLCD 1992). Available at http://landcover.usgs.
Research Center, Texas Agricultural Experiment Station, Tem- gov/natllandcover.asp. Accessed on April 2004.
ple, Texas. USGS (U.S. Geological Survey), 2004b. Seamless Data Distribution
Neitsch, S.L., J.G. Arnold, J.R. Kiniry, R. Srinivasan, and J.R. System, Earth Resources Observation and Science (EROS).
Williams, 2002b. Soil and Water Assessment Tool – User’s Man- Available at http://seamless.usgs.gov/. Accessed on April 2004.
ual – Version 2000. Grassland, Soil and Water Research Labora- USGS (U.S. Geological Survey), 2006. Daily Streamflow for the
tory, Agricultural Research Service and Blackland Research Nation. Available at http://nwis.waterdata.usgs.gov/usa/nwis/
Center, Texas Agricultural Experiment Station, Temple, Texas. discharge. Accessed in January 2006.
Neitsch, S.L., J.G. Arnold, and R. Srinivasan, 2002c. Pesticides Fate Weber, A., N. Fohrer, and D. Moller, 2001. Long-Term Land Use
and Transport Predicted by the Soil and Water Assessment Tool Changes in a Mesoscale Watershed Due to Socio-Economics Fac-
(SWAT) – Atrazine, Metolachlor and Trifluralin in the Sugar tors – Effects on Landscape Structures and Functions. Ecologi-
Creek Watershed. Grassland, Soil and Water Research Labora- cal Modeling 140:125-140.
tory, Agricultural Research Service and Blackland Research Williams, J.R., 1995. The EPIC Model. In: Computer Models of
Center, Texas Agricultural Experiment Station, Temple, Texas. Watershed Hydrology, V.P. Singh (Editor). Water Resources Pub-
Olivera, F., 2001. Extracting Hydrologic Information From Spatial lications, Highlands Ranch, Colorado, pp. 909-1000.
Data for HMS Modeling. Journal of Hydrologic Engineering 6 Zeiler, M., 2001. Exploring ArcObjects. ESRI Press, Redlands, Cali-
(6):524-530. fornia.
Olivera, F., R. Dodson, and D. Djokic, 2003. Use of Arc Hydro for
Integration of Hydrologic Applications. In: Proceedings of the
American Society of Civil Engineers (ASCE) World Water and
Environmental Resources Congress 2003, Philadelphia, Penn-
sylvania. American Society of Civil Engineers (ASCE), Reston,
Virginia, doi 10.1061/40685(2003)249.