Richard B. Alexander, John W. Brakebill, Robert E. Brew, and Richard A. Smith 19990228 Version 1.2, August 01, 1999 map--digital data U.S. Geological Survey Open-File Report 99-457 ERF1 Reston, Virginia U.S. Geological Survey http://water.usgs.gov/lookup/getspatial?erf1 U.S. Environmental Protection Agency's River Reach File 1 (RF1)to ensure the hydrologic integrity of the digital reach traces and to quantify the mean water time of travel in river reaches and reservoirs [see USEPA (1996) for a description of the original RF1]. reaches capable of supporting regional and national water-quality and river-flow modeling and transport investigations in the water-resources community. ERF1 has been recently used at the U.S. Geological Survey to support interpretations of stream water-quality monitoring network data (see Alexander and others, 1996; Smith and others, 1995). In these analyses, the reach network has been used to determine flow pathways between the sources of point and nonpoint pollutants (e.g., fertilizer use, municipal wastewater discharges) and downstream water-quality monitoring locations in support of predictive water-quality models of stream nutrient transport. Any use of trade, product, or firm names is for descriptive purposes only and does not imply endorsement by the U.S. Government. Although this Federal Geographic Data Committee-compliant metadata file is intended to document the data set in nonproprietary form, as well as in ARC/INFO format, this metadata file may include some ARC/INFO-specific terminology. 19990107 none Complete As Needed -127.81690486 -65.55541404 48.19323122 23.24701718 none stream river network sparrow reach RF1 Water Quality Reservoir inlandWaters none Conterminous United States none The version of RF1 used to compile ERF1 was an early edition of a USGS RF1 translation and was recently updated by USEPA (1996). The capability of the enhanced version of RF1 (ERF1) and the current USEPA version has not been evaluated. The user is referred to the USEPA version [see Web address given in the USEPA (1996) reference] for discussions of streamflow accuracy and general background on the origin of RF1. Richard B. Alexander U.S. Geological Survey Hydrologist mailing and physical address

12201 Sunrise Valley Dr., MS 413

Reston VA 20192 USA 1-888-275-8747 ralex@usgs.gov David L. Lorenz of the U.S. Geological Survey assembled the majority of the documentation for this data set. dgux, R4.11MU04, AViiON UNIX ARC/INFO version 7.1.1 ARC/INFO version 7.2.1, NT The direct drainage area of each reach (RCHAREA) was computed by Smith and others (1997) using a Theissen method. It considers solely the distance to the nearest reach and does not consider any topographic features. It provides reasonably good estimates for higher-order streams, but is less accurate for lower orders. See process steps 3, 4, and 5, to assess the accuracy of MEANV, RCHTOT, and RESTOT. This data set is believed to provide complete and accurate connectivity among the streams represented. These arcs representing streams are intended to be presented in a TNODE to FNODE orientation. The arcs are pointing in a downstream direction. The set of streams represented reflects the choices in the U.S. Environmental Protection Agency's "Reach File 1." See DeWald and others, 1985. Reservoir and lake boundaries were removed from the original RF1 data set. They are represented by a single trace to satisfy the connectivity requirements of the dataset. ArcEdit functions were used to delineate centerlines within the RF1 shoreline boundaries. The centerline reaches approximate the thalweg of each reservoir or lake. Shorlines of major estuaries and some coastal areas were added to the data set to serve as a stopping location for trace routines. Existing reaches extending within estuaries were deleted. Smith, R.A., Schwarz, G.E., and Alexander, R.B. 19971201 model Water Resources Research Volume 33, Number 12, pp. 2781-2798 Washington, D.C. American Geophysical Union 500000 Arc/INFO coverage and ASCII files 19971201 none Smith and others, 1997 Linework, connectivity, areas Smith, R.A., Alexander, R.B., and Schwarz, G.E. 19950602 map Spring Meeting June 2, 1995, Baltimore, Maryland. Washington, D.C. American Geophysical Union 500000 map 19950602 none Smith and others, 1995 Linework, connectivity, areas Alexander, R.B., Smith, R.A., and Schwarz, G.E. 19960101 map Management Conference December 5-6, 1995, Kenner, Louisiana. Washington, DC USEPA 500000 map 19971201 none Alexander and others, 1996 Linework, connectivity, areas DeWald, T., Horn, R., Greenspun, R., and Taylor, P. 19850101 model Washington, D.C. U.S. Environmental Protection Agency 500000 Arc/INFO coverage 19950101 none DeWald and others, 1985 Linework and attributes U.S. Environmental Protection Agency 19960101 model Washington, D.C. U.S. Environmental Protection Agency http://www.epa.gov/waterscience/basins/metadata/rf1.htm 500000 Arc/INFO Export 19960101 none USEPA 1996 Linework and attributes National Oceanic and Atmospheric Administration 19971201 model Washington, D.C. National Oceanic and Atmospheric Administration 500000 Arc/INFO Coverage 19971201 none NOAA, 1997 Linework and attributes Ruddy, B.C., and Hitt, K.J. 19900101 model U.S. Geological Survey Open-file Report 90-163 Reston, Virginia U.S. Geological Survey Arc/INFO coverage 19900101 April, 1998 on the World Wide Web at http://water.usgs.gov/lookup/getspatial?reservoir Ruddy and Hitt, 1990 Points and attributes for reservoirs. Omernik, J.M. 19870101 model Annals of the Association of American Geographers Volume 77, pp. 118-125 unknown Association of American Geographers map 19870101 none Omernik, 1987 Ecoregions Allord, G.J.. 19920101 model U.S. Geological Survey Open-file Report 90-163 Reston, Virginia U.S. Geological Survey Arc/INFO coverage 19920101 April, 1998 on the World Wide Web at http://water.usgs.gov/lookup/getspatial?huc2m Allord, 1992 Hydrologic unit boundaries U.S. Geological Survey 19970101 model The National Atlas of the United States of America fedlandsm Reston, Virginia U.S. Geological Survey Arc/INFO coverage 19920101 July, 1998 on the World Wide Web at http://www-atlas.usgs.gov/ USGS, 1997a Federal land polygons U.S. Geological Survey 19970101 model The National Atlas of the United States of America parkwaysm Reston, Virginia U.S. Geological Survey Arc/INFO coverage 19920101 July, 1998 on the World Wide Web at http://www-atlas.usgs.gov/ USGS, 1997a Wild amp Scenic Rivers (a) The RF1 trace file was edited to exclude reservoir shorelines. Segments with a TYPE='L' (lake shoreline segment) were removed from the file. (b) ArcEdit functions were used to create centerlines within the RF1 shoreline boundaries. A separate coverage of the shoreline segments was superpositioned as a backcover in ArcEdit and used as a guide in the manual positioning of the centerlines. The downstream nodes of tributary reaches were moved (using the VERTEX MOVE ArcEdit command) and joined with other tributary nodes to form centerlines. The VERTEX ADD ArcEdit function was applied to centerline reaches in ArcEdit to ensure that the new arcs approximated the thalweg of each reservoir. A total of 4,180 reaches in 1,146 reservoirs were added as centerlines to produce a total of 60,298 reaches in ERF1 trace file. [Note that in one case the interior reach extends beyond the reservoir boundaries (ERF1##=10117). In future editions of the file, a node will be added at the reservoir outlet. Also note that the attributes listed in the ERF1.AAT file may not be accurate for centerlines because these reaches were created from reservoir tributary reaches.] 19981207 Using the ArcPlot TRACE function, the connectivity of reaches was determined by navigating upstream from all reaches where there is no downstream reach. These reaches are called terminal reaches. Disruptions in navigation resulting from disconnected nodes or, more commonly, improperly oriented arcs were corrected in ArcEdit by joining nodes or "flipping" the arc direction, respectively. To conform with TRACE requirements, from-nodes (FNODE#) were located at the downstream end of each reach and to-nodes (TNODE#) were located at the upstream end of the reaches. This node orientation is maintained in the final version of ERF1. Fewer than 10 disruptions were detected in navigation in each of water-resources regions. Additional edits were performed to correct a few instances of circular reaches (identical to- and from-nodes) and inaccurate digital representations of rivers. 19981207 For approximately 5,600 reaches with missing mean velocity values (and positive mean streamflow values), estimates of mean velocity were made using the regression-based approach developed by W.E. Gates and Associates (USEPA, written communication, Nov 1982, "Reach File Enhancements, Chapter 3, Development of time-of-travel predictions). The authors developed regression relations for each of 9 stream orders from USGS topographic sheets that were used to predict velocity as a function of streamflow and stream order. The calibration data set consisted of 2229 time-of-travel/velocity/ discharge measurements. Velocity is related to log-transformed flow and flow squared separately for data from each stream order. Because of differences in stream order of USGS topographic maps and RF1 scale digitizations, a probability matrix was established to compute a stream-order weighted estimate of velocity for ERF1. 19981207 The reach time-of-travel (RCHTOT) in units of days was computed as the quotient of reach length and reach velocity for 59,364 reaches with positive values of velocity such that RCHTOT = C1 * LENGTH / MEANV (1) where C1 is a conversion factor of 0.00003797 ft-day/meter-second, LENGTH is the length in meters of the Arc reach segment, and MEANV is the mean velocity in feet per second. Reaches with missing time-of-travel are assigned a value of zero. 19981207 (a) ERF1 centerlines were associated with the RF1 shoreline features and attributes (i.e., reservoir name in PNAME and unique reservoir code in PNMCD) by converting reservoir shoreline segments to polygons and intersecting these polygons with the centerlines. A total of 4,180 reaches were linked to 1,146 reservoirs with shoreline boundaries in RF1. (b) These centerline reaches were digitally matched with reservoirs identified in the USGS reservoir file (Ruddy and Hitt, 1990) by linking each reservoir to the nearest centerline within 10 kilometers using the Arc NEAR function. The USGS reservoir file consists of 2,728 reservoirs with normal capacity of at least 5,000 acre-feet or maximum capacities of at least 25,000 acre-feet and that were completed as of January 1, 1988. These reservoirs are digitally represented by points in an Arc coverage which represent the location of the center of the dam. [see Web location cited in references for Ruddy and Hitt (1990)]. Manual verification of reservoir-RF1 reach links were completed by comparing the river and reservoir names in RF1 to those in the USGS reservoir file, and by visual inspection for agreement between the centerlines and reservoir shoreline boundaries. A total of 815 reservoirs were matched with RF1 shorelines features (350 unmatched RF1 water bodies). Of these 815 reservoirs, there are 19 pairs of reservoirs that match the same RF1 water body (i.e., duplicate PNMCD-RES values in the file ERF1.RESINT), and 2 RF1 water bodies that match the same USGS reservoir RESERVOIR##=1004). Reservoir residence time (i.e., time-of-travel or RESTOT) in units of days was computed for 810 reservoirs with available values of normal capacity and outflow such that RESTOT = NORMCAP / MEANQ-OUT * C2 (2) where NORMCAP is the normal capacity in acre-feet from the USGS reservoir file, MEANQ-OUT is the mean streamflow for the immediate reach downstream of the reservoir, and C2 is a conversion factor of 0.50416 cubic feet-day/acre feet-second. Reservoirs with missing time-of-travel values are assigned a value of zero. The reservoir attributes for 1,165 reservoirs appear in the file ERF1.RESINT. (c) Remaining reservoirs in the USGS reservoir file were initially matched to RF1 reaches located outside of the RF1 shoreline boundaries using the Arc NEAR criterion of 10 kilometers described previously. Manual verification of links was initially completed by comparing the river names with those in the USGS reservoir file. An automated graphical display using AML was created to allow visual verification and correction of the remaining reservoir-reach links and previous links that were in question. USGS topographic maps were used in combination with the display aml to obtain accurate reservoir-reach matches. A total of 1,322 reservoirs were matched to 1,245 RF1 reaches external to RF1 shoreline boundaries (RESCODE = 3, 4, or 5). Multiple reservoirs were linked to 67 reaches (2 reaches with 4 reservoirs each; 6 reaches with 3 reservoirs each; and 59 reaches with 2 reservoirs each). Reservoir residence time in units of days (RESTOT) was computed for 1,296 reservoirs with available values of normal capacity and streamflow such that RESTOT = NORMCAP / MEANQ * C2 (3) where MEANQ is the RF1 reach mean streamflow. The reservoir attributes for 1,322 reservoirs appear in the file ERF1.RESEXT. 19981207 Major estuaries and coastal shorelines were added from the National Oceanic and Atmospheric Administration USEPA Reach File Version 1.0 (RF1) (NOAA, 1997) for the Conterminous United States (CONUS) as enhanced for NOAA's Strategic Environmental Assessments Division. Shorelines and estuary boundaries were snapped to existing reaches and assigned ERF1## and E2RF1## values of 80000. For identification purposes, the shorelines and estuary boundaries maintained the USEPA items for identification purpose. In addition, TERMFLAG = 3 for these shoreline segments. 19990404 Major river basins where MEANQ gt 5000 were checked for connectivity and orientation using the ARCPLOT TRACE commands. The following corrections were made. Numbers represent attribute ERF1##. An item E2RF1## was added to reflect changes in the unique identifier of reaches and will be used in future modeling applications. ERF1## and E2RF1## are equal except for the first three transport reaches corrected listed below. 4368 Susquehanna confluence is at the wrong location. Used all attributes from the downstream reach 3422. New E2RF1## = 65000 32047 snapped to 32051, Calc TERMFLAG = 0 upstream 32051 E2RF1## calculated to 65001 32048 snapped to 32051, Calc TERMFLAG = 0 upstream 32051 E2RF1## calculated to 65002 54175 and 54176 snapped to 53437. New upstream reach created and merged (unsplit) with ERF1## 53438. 2817 and 3038 intertwined at upstream end split reach 3083 at 1:2m hydrologic unit boundary (Huc bnd) and deleted upstream end . 6734 - Upper reach duplicated by 10493 (Little Ogeechee R.) split 10493 at huc bnd and deleted upstream end 11945 and 12634 intertwined upstream split both at Huc bnd, deleted upstream ends 13879 and 13880 are intertwined Deleted 13880, wrong location 15384 and 15402 - intertwined at upstream ends split 15402 at Huc bnd, deleted upstream end 17258 and 7875 - intertwined at upstream end split 7875 at Huc bnd, deleted upstream end 19453 and 19452 - intertwined, Deleted 19452, wrong location 23117 and 32841 intertwined at upstream ends split 23117 at Huc bnd, deleted upstream 52204 and 47249 intertwined at upstream ends split both 52204 and 47249 at Huc bnd and deleted upstream ends 53575 and 53574 intertwined upstream split both 53575 and 53574 at Huc bnd and deleted upstream ends 53786 and 54262 intertwined upstream split 54262 at huc bnd and deleted upstream end 3322 - deleted unnecessary arcs, corrected node toploogy 5645 - deleted unnecessary arcs, corrected node toploogy 10527 - Snapped to 10534, W. Br. Cooper R. 6187 - Snapped to 6195, S. Santee 6720 - deleted unnecessary arcs, corrected node topology 11829 - corrected topology 13559 deleted zingers, L shaped arcs 16257 and 16636 - unsnapped nodes at upstream end 15979 and 16584 - unsnapped nodes at upstream end Unsnapped nodes at upstream 21922 from 21911 22744 removed and unsplit to 22745 re-calculated RCHAREA Flipped 31870 31873, Calc TERMFLAG = 0 32013 snapped, Calc TERMFLAG = 0 57137 and 57141 Flipped and snapped 57101 snapped to node 51065 snapped to node 31249 and 34050 intertwined at upstream ends split 31249 at Huc bnd, deleted upstream end. 19990501 All coastal shoreline reachs (E2RF1## gt 80000), TERMFLAG = 3. TERMFLAG for disconnected reaches and reaches flowing outside continental US = 2. TERMFLAG for reaches ending at the shoreline to terminate modeling applications = 1. 19990519 Reaches with missing or zero MEANQ or MEANV values (932) were assigned -9999.99. RESTOT and RCHTOT that would result in a negative values were also assigned -9999.99. 19990719 Vector String 60298 Albers Conical Equal Area 29.5 45.5 -96 23 0.0 0.0 coordinate pair 459.9369506835 459.9369506835 Meters North American Datum of 1983 Spheroid GRS1980 6378206.4 294.98 Brief description of the attributes of the ERF1 geospatial data set and associated INFO files. Fields defined in original RF1 may not have the correct information because of enhancement processing. See USEPA (1996) for documentation for RF1. See Ruddy and Hitt (1990) for documentation of reservoir codes. See NOAA (1997) for documentation for NOAA codes. > ERF1.AAT: Arc Attribute Table > 1 FNODE# 4 5 B > 5 TNODE# 4 5 B > 9 LPOLY# 4 5 B > 13 RPOLY# 4 5 B > 17 LENGTH 4 12 F > 21 ERF1# 4 5 B > 25 ERF1-ID 4 5 B > 29 HUC 8 8 I > 37 SEG 3 3 I > 40 RFLAG 1 1 C > 41 OWFLAG 1 1 C > 42 TFLAG 1 1 C > 43 SFLAG 1 1 C > 44 TYPE 1 1 C > 45 SEGL 4 5 F > 49 LEV 2 2 I > 51 PNAME 30 30 C > 81 PNMCD 11 11 C > 92 OWNAME 30 30 C > 122 OWNMCD 11 11 C > 133 RESCODE 4 5 B > 137 RESVOIR1 4 5 B > 141 RESVOIR2 4 5 B > 145 RESVOIR3 4 5 B > 149 RESVOIR4 4 5 B > 153 ERF1## 4 5 B > 157 E2RF1## 4 5 B > 161 PNAME-RES 30 30 C > 191 PNMCD-RES 11 11 C > 202 MEANQ 4 10 F > 206 MEANV 4 10 F > 210 RCHAREA 4 9 F > 214 TOTAREA 4 9 F > 218 STRAHLER 4 5 B > 222 STATE1 2 2 I > 224 STATE2 2 2 I > 226 STATE3 2 2 I > 228 RCHTOT 4 12 F > 232 RESTOT 4 12 F > 236 TERMFLAG 4 5 B > 240 CONTFLAG 4 5 B > 244 LRATIO 4 12 F > 248 EDACDA 5 5 C > 253 EDANAME 50 50 C > ** REDEFINED ITEMS ** > 29 RR 11 11 C > 29 HUC2 2 2 I > 29 HUC4 4 4 I > 29 HUC6 6 6 I > > Item Name Description > > CONTFLAG Continental flag (see below). > EDACDA NOAA code identifying estuarine/coastal drainage > areas for major estuaries in the United States. > EDANAME NOAA name identifying estuarine/coastal drainage > areas for major estuaries in the United States. > ERF1# Arc internal number of the arc. > ERF1## Unique key identifying the reach Version 1 files. > E2RF1## A secondary unique reach identification number that > reflects revisions in process steps 6 and 7. > ERF1-ID Arc identification number. > FNODE# Internal number of the from node. > HUC Hydrologic Cataloging unit of the reach. > HUC2 Hydrologic Region of the reach. > HUC4 Hydrologic Subregion of the reach. > HUC6 Hydrologic Accounting unit of the reach. > LENGTH Reach length in meters. > LEV The stream level used for hierarchical relationships, defined in RF1. > LPOLY# Internal number of the left polygon, always zero. > LRATIO Indicates fraction of reach lying within continental > boundaries, see CONTFLAG. > MEANQ Mean streamflow for reach, in cubic feet per second. > -9999.99 = nodata > MEANV Velocity corresponding to mean streamflow for reach, > in feet per second. > OWFLAG Open water flag defined in RF1. > OWNAME Open water name defined in RF1. > OWNMCD Open water name code, defined in RF1. > PNAME Name of the reach defined in RF1. > PNAME-RES Reservoir name, defined in RF1. > PNMCD Reach name code defined in RF1. > PNMCD-RES Reservoir name code, defined in RF1. Link from arc > attribute table (ERF1.AAT) to the resint table > (ERF1.RESINT). > RCHAREA Total area associated with reach, in square kilometers. > RCHTOT Reach water time of travel (days). -9999.99 = nodata > RESCODE Reservoir reach type code (see below). > RESTOT Reservoir time of travel associated with the reach, > in days (see below). -9999.99 = nodata > RESVOIR1 Reservoir identification number 1 (see below). > RESVOIR2 Reservoir identification number 2 (see below). > RESVOIR3 Reservoir identification number 3 (see below). > RESVOIR4 Reservoir identification number 4 (see below). > RFLAG Transport reach flag defined in RF1. > RPOLY# Internal number of the right polygon, always zero. > RR "River Reach" identifier. Key to RF1. > SEG The 3-digit segment number. > SEGL The reach length defined in RF1. > SFLAG Start flag defined in RF1. > STATE1 State fips code 1. > STATE2 State fips code 2. > STATE3 State fips code 3. > STRAHLER Strahler stream order of the reach. > TERMFLAG Terminal reach flag used for model applications. > TFLAG Terminal flag defined in RF1. > TNODE# Internal number of the TO node. > TOTAREA Total area above reach outlet, in square kilometers. > TYPE The reach type defined in RF1. > > ERF1.NAT: Node Attribute Table > > COLUMN ITEM NAME WIDTH OUTPUT TYPE N.DEC > 1 ARC# 4 5 B - > 5 ERF1# 4 5 B - > 9 ERF1-ID 4 5 B - > > ARC# Internal number in the node attribute table. > ERF1# Internal number of the arc. > ERF1-ID Unique identifier. Primary key. > >ERF1.RESATTS: Reservoir Statistics table > >COLUMN ITEM NAME WIDTH OUTPUT TYPE N.DEC > 1 FIPS 5 5 I 0 > 6 STATE 2 2 C - > 8 NUM 3 3 I - > 11 DAMNAME 37 37 C - > 48 RESNAME 26 26 C - > 74 OWNERNAME 20 20 C - > 94 OWNERCODE 1 1 C - > 95 SIZECODE 1 1 C - > 96 MAXCAP 9 9 N 0 > 105 NORMCAP 9 9 N 0 > 114 SURFCAP 9 9 N 0 > 123 POPNAME 37 37 C - > 160 HUC 8 8 I - > 168 RIVER 29 29 C - > 197 YEAR 4 4 I - > 201 PURP 10 10 C - > 211 HEIGHT 5 5 N 0 > 216 HYDCAP 8 8 N 0 > 224 LOCKS 1 1 I - > 225 SOURCE 1 1 C - > 226 SURFAREA 9 9 N 0 > 235 SURFACODE 1 1 C - > 236 STORAT 4 4 N 2 > 240 STORATCODE 1 1 C - > 241 DRAINAREA 9 9 N 2 > 250 STLINE 1 1 I - > 251 ALTST 2 2 C - > 253 ALTID 5 5 I - > 258 REV 4 4 F 1 > 262 LONDD 4 12 F 6 > 266 LATDD 4 12 F 6 > 270 RESERVOIR## 4 5 B - > ** REDEFINED ITEMS ** > 1 FIPSST 2 2 I - > 3 FIPSCNTY 3 3 I - > 6 STATENUM 5 5 C - > 160 HUC2 2 2 I - > 160 HUC4 4 4 I - > 160 HUC6 6 6 I - > > ALTID Alternate state id number, defined in reservoir. > ALTST Adjacent state FIPS code, defined in reservoir. > DAMNAME Name of dam, defined in reservoir. > DRAINAREA Drainage area above dam, in square miles. Defined in > reservoir. > FIPS The 5-digit FIPS code for the state and county. > FIPSCNTY The 3-digit FIPS code for the county. > FIPSST The 2-digit FIPS code for the state. > HEIGHT Height of dam, in feet. Defined in reservoir. > HYDCAP Installed power capacity of dam, in megawatts. > Defined in reservoir. > LATDD Latitude of dam, defined in reservoir. > LOCKS The number of navigation locks, defined in reservoir. > LONDD Longitude of dam, defined in reservoir. > MAXCAP Maximum capacity of reservoir, in acre feet. Defined > in reservoir. > NORMCAP Normal capacity, acre-ft, of the reservoir of which > the reach is part. Defined in reservoir. > NUM Arbitrary sequence number of dam, defined in reservoir. > OWNERCODE Owner of dam code, defined in reservoir. > OWNERNAME Name of owner of dam, defined in reservoir. > POPNAME Popular name of dam, defined in reservoir. > PURP Major purpose of dam, defined in reservoir. > RESERVOIR## Link between the arc attribute table and reservoir tables. > RESNAME Name of reservoir, defined in reservoir. > REV Revision number for reservoir data, defined in reservoir. > RIVER Name of river on which dam is built, defined in > reservoir. > SIZECODE Reservoir size code, defined in reservoir. > SOURCE Source of changes to reservoir files, defined in > reservoir. > STATE State fips code, defined in reservoir. > STATENUM State and sequence number for reservoir, defined in > reservoir. > STLINE Flag to indicate dam is on state line, defined in > reservoir. > STORAT Storage ratio, defined in reservoir. > STORATCODE Storage ration code, defined in reservoir. > SURFACODE Surface area code, defined in reservoir. > SURFAREA Surface area of reservoir, in acres. Defined in > reservoir. > SURFCAP Capacity used to calculate surface area, defined in > reservoir. > YEAR The year the dam was completed, defined in reservoir. ********************************************************************************** >ERF1.RESEXT: Reservoir Statistics table > >COLUMN ITEM NAME WIDTH OUTPUT TYPE N.DEC > 1 ERF1## 4 5 B - > 5 RESERVOIR## 4 5 B - > 9 RESCODE 4 5 B - > 13 PNAME-RES 30 30 C - > 43 PNMCD-RES 11 11 C - > 54 MEANQ 4 10 F 2 > 58 RESTOT 4 12 F 5 > > ERF1## Unique key identifying the reach. > MEANQ Mean streamflow for reach, in cubic feet per second. > PNAME-RES Reservoir name, defined in RF1. > PNMCD-RES Reservoir name code, defined in RF1. Link from arc > RESCODE Reservoir reach type code (see below). > RESERVOIR## Link between the arc attribute table and reservoir tables. > RESTOT Reservoir time of travel associated with the reach, > in days (see below). ******************************************************************************** >ERF1.RESINT: > >COLUMN ITEM NAME WIDTH OUTPUT TYPE N.DEC > 1 RESERVOIR## 4 5 B - > 5 RESCODE 4 5 B - > 9 PNAME-RES 30 30 C - > 39 PNMCD-RES 11 11 C - > 50 RESTOT 4 12 F 5 > 54 MEANQ-OUT 4 10 F 2 > > MEANQ-OUT Mean streamflow for reach below reservoir, in cubic > feet per second. > PNAME-RES Reservoir name, defined in RF1. > PNMCD-RES Reservoir name code, defined in RF1. Link from arc > RESCODE Reservoir reach type code (see below). > RESERVOIR## Link between the arc attribute table and reservoir tables. > RESTOT Reservoir time of travel associated with the reach, > in days (see below). ******************************************************************************* >Additional explanation and domains of items in ERF1 and reservor tables. >Some attributes are from original RF1 data, and may have changed due to >enhanced processing. > CONTFLAG > Code to approximately separate fresh-water from tidally > influenced reaches. > 0 == Fresh-water reach, LRATIO gt= .50. > 1 == Tidal reach, LRATIO lt .50. OWFLAG -- RF1 attribute > Open Water Flag > 0 == Non Open Water > 1 == Open Water RESCODE > [Note that hydraulic data displayed in the file RESV%%%%.TXT > (where %%%% is a unique supplier intake and reach identification > number), including water time of travel, are not available for > all impoundments] > 1,2 == The reach is interior to RF1 shoreline features > 3 == The reach is the outlet reach for a reservoir with RF1 > shoreline features > 4 == No shoreline features are present in the RF1 coverage > 5 == No shoreline features are present in the RF1 coverage; > the reservoir is an "offstream" facility that may divert > river flow (no reservoir characteristics are reported > for these cases) > RESTOT > Where RESTOT is a positive value, the reservoir residence time > (computed as quotient of the normal capacity of the reservoir > and the streamflow at the outlet of the reservoir) is used to > define the water time of travel in the reach. Where multiple > reaches are associated with a single reservoir, the reach share > of the reservoir residence time is proportional to the reach > length relative to the total reach length of the reservoir. > RESVOIR1, RESVOIR2, RESVOIR3, RESVOIR4 > Identification number for impoundments with hydraulic data. The > ID number corresponds to RESERVOIR## in the ERF1.RESATTS file. > Note that multiple reservoirs may be associated with a reach. > RFLAG -- RF1 attribute > 0 == Non-Transport reach > 1 == Transport reach, RF1 attribute SFLAG -- RF1 attribute > 0 == Non-Start reach, RF1 attribute > 1 == Start reach, RF1 attribute TFLAG -- RF1 attribute > 0 == Non-Terminal Reach, RF1 attribute > 1 == Terminal reach, RF1 attribute TERMFLAG -- Modeling applications > 0 == Transport reach > 1 == Terminal reach > 2 == Non-connected, or exits to a closed basin > 3 == Shoreline reach TYPE -- RF1 attribute > Reach Type - The term "reach type", not to be confused with any of the > Reach File record types, refers to a one-character code assigned to each > RF1 reach to categorize transport reaches and shoreline reaches as follows: > A. Artificial Lake Reach (A transport reach). An artificial reach > within a lake or reservoir inserted in the file to provide > connection between input and output reaches of the open water. > B. Bi-directional Reach (A transport reach). A reach for which the > direction of flow is ambiguous. > C. Coastal or Continental Shoreline Segment (A shoreline reach) A > reach which represents a segment of a shoreline of a gulf, sea, or > ocean. > D. Dam Reach (A transport reach). A reach which is a dam through > which and/or around which water flows. This type of reach has the > same primary and open water names as the next reach upstream. > E. Entry Reach (A transport reach). A reach which receives flow > from Canada or Mexico. > F. Falls Reach (A transport reach). A reach which is either a > waterfall, drop spillway, or a reach of rapids. > G. Great Lakes Shoreline Segment (A shoreline reach). A reach which > represents a segment of a shoreline of the the Great Lakes. > I. Island Shoreline Segment (A shoreline reach). A reach which > represents a segment of a shoreline of an island. > L. Lake Shoreline Segment (A shoreline reach). A segment which follows > the shoreline of a lake other than one of the Great Lakes. > M. Artificial Open Water Reach (A transport reach). An artificial > reach within any open water, other than a lake or reservoir, to > provide connection between input and output reaches of the open > water. > N. Non-Connected Reach (A transport reach). A reach not having codes > to link it to other reaches. > R. Regular Reach (A transport reach). A reach which has upstream and > downstream reaches connected to it and which is not classified as > another type of reach. > S. Start Reach (A transport reach). A headwater reach which has no > reaches above it and either one or two transport reaches connected > to its downstream end. > T. Terminal Reach (A transport reach). A reach downstream of which > there is no other reach (for example, a reach which terminates > into an ocean, a land-locked lake, or the ground). This type of > reach has either one or two reaches connected to its upstream end. > V. Open Water Terminal Reach (A transport reach). A reach which is both > a terminal reach and an artificial open water reach. > W. Wide-River Shoreline Segment (A shoreline reach). A reach which > represents a segment of the left or right bank of a stream. > X. Terminal Start Reach (A transport reach). A reach which is both a > terminal reach and a start reach. > Y. International Boundary Reach (A transport reach). A reach extending > along a portion of an international boundary. Occurences of this > type of reach are not actual surface water features. Instead, they > are a type of artificial reach. They have been inserted in the file > for database navigation between reaches along streams which flow > out and then back into the US. They are not intended for usual > studies of streamflow or the fate of pollutants. > Z. Terminal Entry Reach (A transport reach). A reach which is both a > terminal reach and an entry reach. none U.S. Geological Survey Ask USGS - Water Webserver Team mailing

445 National Center

Reston VA 20192 1-888-275-8747 (1-888-ASK-USGS) http://answers.usgs.gov/cgi-bin/gsanswers?pemail=h2oteam&subject=GIS+Dataset+erf1 Although this data set has been used by the U.S. Geological Survey, U.S. Department of the Interior, no warranty expressed or implied is made by the U.S. Geological Survey as to the accuracy of the data and related materials. The act of distribution shall not constitute any such warranty, and no responsibility is assumed by the U.S. Geological Survey in the use of this data, software, or related materials. Any use of trade, product, or firm names is for descriptive purposes only and does not imply endorsement by the U.S. Government. Export Full coverage zipped 1 http://water.usgs.gov/GIS/dsdl/erf1.e00.gz None. This dataset is provided by USGS as a public service. 20041108 U.S. Geological Survey Ask USGS -- Water Webserver Team mailing

445 National Center

Reston VA 20192 1-888-275-8747 (1-888-ASK-USGS) http://water.usgs.gov/user_feedback_form.html FGDC Content Standards for Digital Geospatial Metadata FGDC-STD-001-1998