Jump to main content.

USEPA Reach File Version 1.0 (RF1) for the Conterminous United States (CONUS)

Table of Contents

1.0 Identification Information
1.1 Citation
1.2 Description
1.2.1 Abstract
1.2.2 Purpose
1.2.3 Supplemental Information
1.3 Time Period of Content
1.4 Status
1.5 Spatial Domain
1.6 Keywords
1.7 Access Constraints
1.8 Use Constraints
1.9 Point of Contact
1.10 Browse Graphic
1.11 Data Set Credit
1.12 Security Information
1.13 Native Data Set Environment
2.0 Data Quality Information
2.2 Logical Consistency Report
2.3 Completeness Report
2.4 Positional Accuracy
2.5 Lineage
3.0 Spatial Data Organization Information
3.2 Direct Spatial Reference Method
3.3 Point and Vector Object Information
4.0 Spatial Reference Information
4.1 Horizontal Coordinate System Definition
5.0 Entity and Attribute Information
5.1 Detailed Description
5.2 Overview Description
6.0 Distribution Information
6.1 Distributor Organization
6.2 Resource Description
6.3 Distribution Liability
6.4 Standard Order Process
6.7 Available Time Period
7.0 Metadata Reference Information
7.1 Metadata Date
7.4 Metadata Contact
7.5 Metadata_Standard_Name
7.6 Metadata_Standard_Version
7.7 Metadata_Time_Convention
8.0 Citation Information
8.1 Originator
8.2 Publication Date
8.4 Title
8.5 Edition
8.6 Geospatial Data Presentation Form
8.8 Publication Information
8.10 Online Linkage
9.0 Time Period Information
9.1 Single Date/Time
10.0 Contact Information
10.1 Contact Person Primary
10.2 Contact Organization Primary
10.4 Contact Address
10.5 Contact Voice Telephone
10.8 Contact Electronic Mail Address
The following text conforms with the hierarchy of data elements in the FGDC Content Standards for Digital Geospatial Metadata. This ARC/Info coverage supersedes all earlier copies, translations or coverages of the RF1 database which may have been made by the U.S. Geological Survey (USGS) or the U.S. Environmental Protection Agency (EPA).
1.0 Identification_Information:
  Originator: United States Environmental Protection Agency
  Publication_Date: 1996
  Title: USEPA Reach File Version 1.0 (RF1) for the Conterminous United States (CONUS)

1.1 Citation:
See Section 8.0 - Citation Information
1.2 Description:
Reach File Version 1.0 (RF1) was developed by EPA in 1982 and this is an accurate translation of that database into an ARC/INFO coverage. The RF1 source file has been maintained without modification on the EPA-IBM mainframe computer since 1982.
Abstract:
Reach File Version 1.0 (RF1) is a vector database of approximately 700,000 miles of streams and open waters in the conterminous United States. It is used extensively by EPA and States,and has been used by the U.S. Fish and Wildlife Service and the National Weather Service for many years. This configuration of RF1 for the geographic information systems community, extends the use of RF1 to ARC/INFO users in the U.S.Geological Survey, the U.S. Environmental Protection Agency and others.

 

 

RF1 was prepared by the U.S. Environmental Protection Agency (EPA) in 1982 from stable base color separates of National Oceanographic and Aeronautical Administration (NOAA) aeronautical charts having a scale of 1:500,000. These charts provided the best nationwide hydrographic coverage available on a single scale at that time. They included all hydrography shown on USGS maps having a scale of 1:250,000 with extensive additions, corrections and improvements in detail made by NOAA from aerial photography and satellite imagery. All hydrographic features on those charts were optically scanned from the color separates using a scanner resolution finer than feature line width. The surface water features selected for inclusion in the RF1 database were converted from the scanned raster form to vector form with coordinates expressed as latitude and longitude. Surface water names in RF1 were derived from the source maps and supplemented by names from miscellaneous state maps and maps of the USGS. Many other RF1 attributes are described herein.

In the 1980's, RF1 was used by EPA for performing water quality modeling on whole river basins for all of the hydrologic regions in the conterminous United States. In this role, it was used to provide national assessments and overviews of water quality and to provide the foundation for a nationwide stratified sampling frame for performing statistical summaries of modeled and measured water quality on all the surface waters of the 48 States.

In the 1980's, environmental data integration was strengthened significantly by EPA using the Reach File. Whereas, STORET had, for many years, integrated the water quality monitoring data of EPA, States, the USGS, and other Federal agencies by agency codes, standard water quality parameter codes, date, time, depth, site coordinates, state, basin, and user-definable polygons, the Reach File provided STORET with the capability to search upstream and downstream to relate the environmental data of many agencies to each other along stream paths. This brought about the ability to integrate ambient water quality at sites sampled by the several hundred official monitoring agencies using STORET in a new and powerful manner. Thus, for example, any and all water quality measurements made by the USGS and stored in WATSTORE were easily accessed via STORET prior to the introduction of the Reach File, but with the Reach File, it became possible to integrate the data from USGS WATSTORE records with the much larger holdings of environmental data from EPA, States and other Federal agencies on a station-by-station basis along stream paths. Stream ordered data integration of this type was important in the development of effluent guidelines pursuant to the Clean Water Act during the 1980's, and is but one example of the new dimension in data integration made possible by the standard reach numbering scheme and the hydrologic networking provided in RF1.

Linking multiple databases to RF1 and hence to each other, was accomplished by a process called reach indexing. The process takes advantage of the facts that each reach has been assigned a unique identifier and the stream path for each reach is described in terms of latitude/longitude coordinates. Using simple algebraic processing, each lat/lon point for every point of interest in a database is indexed to the closest point in the nearest RF1 reach. The unique reach number for that reach and its relative position, prorated against the full computed reach length, is placed in the database being reach indexed. From then on, access to all points that have been reach indexed in that indexed database, may be achieved in hydrological order by navigating upstream or downstream through RF1, picking up reach numbers in hydrological order from RF1 and retrieving the points of interest, if present, from the indexed database by reach numbers as the reaches are encountered in the navigation of RF1.

Purpose:
This ARC/INFO coverage is intended for general water resources applications within the GIS user community. It was created to replace two earlier USGS translations of RF1. This coverage supercedes all previous ARC/INFO coverages.
Supplemental_Information:
Limitations_of_Data:
The coordinates and the attribute data of this coverage are machine conversions by EPA of the data in the EPA RF1 files exactly as it exists in the original RF1, archived in 1982. No coordinate data were altered beyond mere conversion to an Albers Equal Area projection. The RF1 streamflow data were obtained without alteration directly from EPA Storet files as data developed for RF1 in June, 1982.

 

 

The RF1 streamflow data consist of mean annual flow and 7Q10 low flow estimates made at the downstream ends of more than 60,000 transport reaches coupled to an estimate of the time-of- travel velocity for the full length of those same reaches under each of those two flow regimes. EPA needed to estimate flows for more than 60,000 reaches because it needed flow data on all RF1 reaches and the USGS had consistent streamflow data on fewer than 2000 of them. Even on these few reaches where consistent data were available, the data were needed at the downstream ends of the reaches rather than where the USGS gages were typically located. Thus, in fact, all of the RF1 flow data are estimates at locations other than USGS gage sites. An additional limitation in the gage network was that vast areas of the country were without USGS data for drainage areas under 500 square miles, except for gages with data gaps, data skew, and anomalous conditions. Approximately 2,000 gages in this category were included in the data set used, such that 4112 gages with flow data were actually used in producing the estimates for all RF1 reaches. Another group of gages was used in the flow estimation process. Drainage area, an attribute essential to the flow estimation process used, is usually available from all USGS flow gages. All of the 4112 gages that included useful flow records, and approximately 4000 additional gages that did not have useful flow data for the project, were used to assign drainage area to reaches in RF1. The drainage area attribute available for gages was thereby used on approximately 8000 gages. By snapping gages to reaches, the project was able to acquire drainage area for approximately one reach in every eight reaches in RF1. Thus some gages were used for streamflow data and their drainage area measurement, and the remaining were used for only their drainage area measurement.

Streamflow data from the USGS Daily Values File for the 4112 gages were used to develop estimates of mean annual flow and 7Q10 flow at the gage sites. Because of data skew and anomalous conditions at many of these gages, interactive graphics techniques were applied to the solution of the mean annual and 7Q10 flow estimates at the gage sites. The interactive graphics provided visual displays of all of the daily values at the 4112 gages to visually detect skew and data anomalies within an automated framework in which the team of hydrologists in the project were able to apply graphical procedures generally used manually by hydrologists all over the world to solve for the mean annual and 7Q10 flows. It was determined in 1982 that these estimates were essentially equal to those produced for the same gages by USGS fully automated methods, except where the data were skewed or anomalous. Hydrological procedures described in "ESTIMATION OF STREAMFLOWS FOR THE REACH FILE," June, 1982 were used in an EPA contract with W.E. Gates and Associates, Inc. to transfer the mean annual flows and 7Q10 low flows at gaged sites to the downstream ends of all reaches including ungaged reaches. The average velocities over the length of each transport reach in the Reach File were developed for those two flows using streamflow, measured time-of-travel data where available, and watershed characteristics under the same contract with W.E. Gates and Associates.

EPA has advised users (1983 EPA memo to Regions, States and other RF1 users), that the overall flow estimation methodology used in producing the RF1 flow estimates was not designed to produce accurate results on start reaches or small ungaged tributaries, nor in estuaries or ungaged coastal streams. Thus the accuracy of the flow estimates in these types of streams is not expected to be adequate for many applications. The principal use of these estimates, it pointed out, was intended to be on reaches where the estimates had been made between upstream and downstream gages. Reviewers commented at that time, that the flow estimates in this latter category were essentially the same as their own which had been made by methods of their choice. EPA added that use of these flow values may benefit from an initial evaluation on a basin-wide or watershed basis, distinguishing between accuracies of the flow estimates among the various reach types, such as start reaches, and reaches in which the flow is regulated by man's activity. Factors such as irregular density of reaches in a particular area of a state or data problems within the period of record for a particular gage, may introduce local variations in the accuracy of these flow estimates. The USGS Water Resources Division cautions users that since the RF1 flow estimates are provided at the downstream ends of gaged and ungaged reaches and not at the actual gage sites, these RF1 flow estimates may differ from USGS records at the gage sites. Furthermore, the USGS Water Resources Division cautions users that these 1982 RF1 flow data are from EPA files and may not accurately represent current records of the USGS.

Procedures:
All procedures applied in generating this ARC/INFO configuration of RF1 consisted of database handling procedures applied by EPA to produce intermediate files appropriate for ARC/INFO import requirements, and common ARC/INFO procedures described in the ARC/INFO users manuals. The RF1 Trace File was used to generate a line coverage as an Albers Equal Area projection. The RF1 Structure File was used to provide topological attributes, hydrological modeling attributes, surface water names, and other data for this coverage, and the RF1 Reach Characteristics File was used to provide the coverage with streamflows and corresponding stream velocities.

 

 

RF1 as used by EPA, retains its reach-to-reach topology in the Structure File for direct open access in mathematical modeling and upstream and downstream database traversals. All but 131 of the more than 60,000 reaches include this topological information, complete for all forms of stream path traversals and flow routing. At present, the RF1 Trace File is used by EPA for graphical display purposes and for reach indexing purposes, and it is not needed in any topological role, because all necessary topological information is contained in the RF1 Structure File. However, of interest to ARC/INFO users is the fact that a total of 3,607 reaches are not provided with reach traces in the Trace File. This is of concern because ARC/INFO builds its own topology from stream traces and is constrained to the topology it builds. Therefore, ARC/INFO users may experience difficulty where traces are not available. It uses data sources such as the RF1 Trace File as input to its topology building process, and will fail at any location within a network where there is a missing reach trace. The RF1.STRUCTx files therefore may be useful to ARC/INFO users where difficulties associated with this situation may be encountered. The following summary of differences is provided to help the ARC/INFO users assess the significance of this situation relative to his or her application:

Summary of Differences:
Total vector-object count in the AAT file:
64,955 arc features, some reaches represented by 2 records due to the 500 point limit per record in ARC/INFO
Reaches without attributes:
129 CUSEG's in the RF1.AAT file have no match in the RF1.STRUCTx files, i.e., topologic attributes are missing on 129 reaches in RF1 Structure File.
Attributes without traces:
3607 RF1.STRUCTx CUSEG's have no match in the RF1.AAT file. Since ARC/INFO builds its own topology from the RF1 trace file, it will produce topologic anomolies on 3607 reaches except where the missing trace records are isolated reaches. To be of further assistance in this matter, a file which details the presence and absence of Trace File data and Structure File data on a reach-by-reach basis has been incorporated in this coverage under the Entity_Type_Label RF1.CUSEGLIST.
Reviews_Applied (February 1996):
Related_Data_Sets:
RF1 was built as a database consisting of two groups of record types. The first group contained three record types which provided reach-by-reach information related by Catalog unit and reach segment number (CUSEG); the second contained two record types which provided information on areal objects namely, open waters and watersheds, which were also related by CUSEG. This ARC/INFO coverage was assembled from the three record types of the first group through a reconfiguration process beginning with the use of the following three intermediate files retrieved from EPA STORET system:


RF1struct.all RF1flow.all RF1trace.all

The rf1trace file consists of all records of the RF1 Trace Record Type; the rf1struct consists of all records of the RF1 Hydrologic Structure Record Type; and the RF1flow file consists of a subset of the RF1 Reach Characteristics Record Type. The rf1trace was used to produce the necessary AAT file and the other two files were used as sources of attribute data.

References_Cited:
Reach File Manual, draft of June 30, 1986, EPA, C. Robert Horn.
1.3 Time_Period_of_Content:
See Section 9.0 - Time Period Information
Currentness_Reference:
publication date
1.4 Status:
Progress:
complete
Maintenance_and_Update_Frequency:
As needed
1.5 Spatial_Domain:
 
   Bounding_Coordinates:

      West_Bounding_Coordinate: -123.7196
      East_Bounding_Coordinate: -56.9772
      North_Bounding_Coordinate: 46.5590
      South_Bounding_Coordinate: 21.9543
1.6 Keywords:
Theme:
Theme_Keyword_Thesaurus:
None
Theme_Keywords:
RF1, Stream, Map, Reach File, Reach File Version 1.0, Hydrography, Hydrology, Flow, Velocity, Stream Names
1.7 Access_Constraints:
None
1.8 Use_Constraints:
None
1.9 Point_of_Contact:
See Section 10.0 - Contact Information
1.10 Browse Graphic
Browse Graphic File Name:
rf1.gif
Browse Graphic File Description:
National RF1 for conterminous United States.
Browse Graphic File Type:
GIF - Graphic Interchange Format
1.11 Data Set Credit:
1.12 Security_Information:
Security_Classification:
Unclassified
1.13 (Native Data Set Environment) Source_Data_Set_Environment:
The source data set environment for RF1 is STORET; the data set environment for this coverage is ARC/INFO.
2.0 Data_Quality_Information:
2.2 Logical_Consistency_Report:
Chain-node topology present.
2.3 Completeness_Report:
See Supplemental_Information
2.4 Positional_Accuracy:
Locations in the rf1.trace.all file were given as degrees with 4 decimal digits. Thus, locations are specified to an accuracy of 0.0001 degrees, or about 11m, with the effect that all lines in RF1 retain the full positional accuracy of the RF1 source maps (scale 1:500,000). Double precision was used in ARC/INFO.
2.5 Lineage:
See Supplemental_Information for overview.
Process_Step 1:
Process_Description:
EPA provided the USGS with an official complete copy of RF1 in the 1980's with full documentation. That copy was converted by the USGS WRD to an ARC/INFO coverage which is herewith replaced.
Process_Date:
late 1980's
Process_Step 2:
Process_Description:
EPA provided the USGS with another copy of the same RF1 database in 1994. That copy was converted by USGS WRD to an ARC/INFO coverage to replace the previous USGS conversion, and it is herewith replaced due to anomolies.
Process_Step: 3
Process_Description:
EPA translated RF1 from its native form to ARC/INFO form to produce this coverage. It provides all data elements in the RF1 Structure File; flow and velocity data elements from the RF1 Reach Characteristics File, and vector traces of streams and shorelines from the RF1 Trace File.
Process_Date:
May 1996
3.0 Spatial_Data_Organization_Information:
3.2 Direct_Spatial_Reference_Method:
Vector
3.3 Vector Point_and_Vector_Object_Information:
SDTS_Terms_Description:
SDTS_Point_and_Vector_Object_Type:
Point
Point_and_Vector_Object_Count:
0
SDTS_Point_and_Vector_Object_Type:
String
Point_and_Vector_Object_Count:
64955
SDTS_Point_and_Vector_Object_Type:
GT-polygon composed of chains
Point_and_Vector_Object_Count:
0
4.0 Spatial_Reference_Information:
4.1 Horizontal_Coordinate_System_Definition:
Planar:
Map_Projection:
Map_Projection_Name:
Albers Conical Equal Area
Alber_Conical_Equal_Area:
Standard_Parallel:
29.5
Standard_Parallel:
45.5
Longitude_of_Central_Meridian:
-96
Latitude_of_Projection_Origin:
23
False_Easting:
0.00000
False_Northing:
0.00000
5.0 Entity_and_Attribute_Information:
5.1 Detailed_Description:
Entity_Type:
Entity_Type_label:
RF1.AAT
Entity_Type_Definition:
Arc Attribute Table (An ArcInfo artifact)
Number_of_Attributes_in_Entity:
13
Attribute:
Attribute_Label:
-
Attribute_Definition:
Arc Attribute Table (An ArcInfo artifact)
Attribute_Definition_Source:
EPA
Attribute_Domain_Values:
-
Attribute:
Attribute_Label:
FNODE#
Attribute_Definition:
Internal number of from-node (An ArcInfo artifact)
Attribute_Definition_Source:
Computed
Attribute_Domain_Values:
Sequential unique positive integer
Attribute:
Attribute_Label:
TNODE#
Attribute_Definition:
Internal number of to-node (An ArcInfo artifact)
Attribute_Definition_Source:
Computed
Attribute_Domain_Values:
Sequential unique positive integer
Attribute:
Attribute_Label:
LPOLY#
Attribute_Definition:
Internal number of poly to left of arc (An ArcInfo artifact)
Attribute_Definition_Source:
Computed
Attribute_Domain_Values:
Sequential unique positive integer (An ArcInfo artifact)
Attribute:
Attribute_Label:
RPOLY#
Attribute_Definition:
Internal number of poly to right of arc (An ArcInfo artifact)
Attribute_Definition_Source:
Computed
Attribute_Domain_Values:
Sequential unique positive integer
Attribute:
Attribute_Label:
LENGTH
Attribute_Definition:
Length of arc in coverage units (An ArcInfo artifact)
Attribute_Definition_Source:
Computed
Attribute_Domain_Values:
Positive real numbers
Attribute:
Attribute_Label:
RF1#
Attribute_Definition:
Internal feature number
Attribute_Definition_Source:
Computed ARC/INFO artifact
Attribute_Domain_Values:
Sequential unique positive integer
Attribute:
Attribute_Label:
RF1-ID
Attribute_Definition:
ARC/INFO Cover ID (An ARC/INFO artifact).
Attribute_Definition_Source:
User-defined ARC/INFO artifact
Attribute_Domain_Values:
Integer
Attribute:
Attribute_Label:
CUSEG
Attribute_Definition:
This is the unique identifier for each reach. It is an 11-digit alphanumeric number. It contains CATUNIT, the nationally unique 8-digit alphanumeric identifier for the cataloging unit in which the reach occurs, and SEG, a 3-digit alphanumeric reach number, unique within the cataloging unit. It is provided as an 11-digit alphanumeric number rather than the 15 digits in RF1.Struct.All, because the four least significant digits, provided in the 1983 RF1 only for update, were never used and were left as a null field.
Attribute_Definition_Source:
EPA
Attribute_Domain_Values:
numeral characters 01010071001 through 18100200999; leading zeros.
Attribute:
Attribute_Label:
CATUNIT
Attribute_Definition:
Hydrologic cataloging unit code (CU)
Attribute_Definition_Source:
Subset of CUSEG coding.
Attribute_Domain_Values:
numeral characters 00000000 through 18100200.
Attribute:
Attribute_Label:
ACCTUNIT
Attribute_Definition:
Hydrologic accounting unit code
Attribute_Definition_Source:
Subset of CUSEG coding.
Attribute_Domain_Values:
numeral characters 000000 through 181002
Attribute:
Attribute_Label:
SUBREGION
Attribute_Definition:
Hydrologic subregion code
Attribute_Definition_Source:
Subset of CUSEG coding.
Attribute_Domain_Values:
numeral characters 0000 through 1810
Attribute:
Attribute_Label:
REGION
Attribute_Definition:
Hydrologic region code
Attribute_Definition_Source:
Subset of CUSEG coding.
Attribute_Domain_Values:
numeral characters 00 through 18
Attribute:
Attribute_Label:
SEG
Attribute_Definition:
Reach segment number within Cataloging Unit, i.e., within a CATUNIT (CU).
Attribute_Definition_Source:
Subset of CUSEG coding.
Attribute_Domain_Values:
numeral characters 001 through 999; leading zero characters, no decimal point character.
Entity_Type:
Entity_Type_label:
RF1.FLOW
Entity_Type_Definition:
Flow table for reach file
Number_of_Attributes_in_Entity:
6
Attribute:
Attribute_Label:
-
Attribute_Definition:
Flow table for reach file
Attribute_Definition_Source:
EPA
Attribute_Domain_Values:
-
Attribute:
Attribute_Label:
CUSEG
Attribute_Definition:
Unique 11-digit alphanumeric identifier for each reach.
Attribute_Definition_Source:
EPA
Attribute_Domain_Values:
CUSEG in RF1.AAT table.
Attribute:
Attribute_Label:
FLOW#
Attribute_Definition:
Record number from source flow File
Attribute_Definition_Source:
Computed.
Attribute:
Attribute_Label:
MNFLO
Attribute_Definition:
RF1 mean annual flow (in cubic feet per second) -an approximation of mean annual flow at the base of the immediate reach. This should not be used on small tributary streams or estuaries without careful review (see 1.2 Definition, Abstract).
Attribute_Definition_Source:
EPA
Attribute:
Attribute_Label:
SEVTEN
Attribute_Definition:
RF1 Low Flow (in cubic feet per second) - an approximation of 7-day-10 year low flow at the base of the immediate reach. This should not be used on small ungaged streams, start reaches, or estuaries without careful review (see 1.2 Definition, Abstract).
Attribute_Definition_Source:
EPA
Attribute:
Attribute_Label:
MFVEL
Attribute_Definition:
RF1 Mean flow velocity (in feet per second). This should not be used on small ungaged streams, start reaches, or estuaries without careful review (see 1.2 Definition, Abstract).
Attribute_Definition_Source:
EPA
Attribute:
Attribute_Label:
LFVEL
Attribute_Definition:
RF1 Low Flow Velocity (in feet per second). This should not be used on small ungaged streams, start reaches, or estuaries without careful review (see 1.2 Definition, Abstract).
Attribute_Definition_Source:
EPA
Entity_Type:
Entity_Type_label:
RF1.CSLIST
Entity_Type_Definition:
Cross-match of RF1.AAT and RF1.STRUCTx files
Number_of_Attributes_in_Entity:
4
Attribute:
Attribute_Label:
-
Attribute_Definition:
Cross-match of RF1.AAT and RF1.STRUCTx files
Attribute_Definition_Source:
Computed
Attribute_Domain_Values:
-
Attribute:
Attribute_Label:
CUSEG
Attribute_Definition:
Unique 11-digit alphanumeric identifier for each reach (Note for experienced users of RF2 and RF3: The MI attribute was never used in RF1).
Attribute_Definition_Source:
EPA
Attribute_Domain_Values:
CUSEG in RF1.AAT table.
Attribute:
Attribute_Label:
IN_AAT
Attribute_Definition:
Indicates if this CUSEG is in the RF1.AAT file.
Attribute_Definition_Source:
Computed
Attribute_Domain_Values:
  1. 0 = not in .AAT
  2. 1= in .AAT
Attribute:
Attribute_Label:
IN_STRUCT
Attribute_Definition:
Indicates if this CUSEG is in RF1.STRUCTx files
Attribute_Definition_Source:
Computed
Attribute_Domain_Values:
  1. 0 = not in .STRUCTx
  2. 1 = in .STRUCTx
Entity_Type:
Entity_Type_label:
RF1.STRUCT1
Entity_Type_Definition:
Hydrologic Structure File
Number_of_Attributes_in_Entity:
21
Attribute:
Attribute_Label:
-
Attribute_Definition:
Hydrologic Structure File
Attribute_Definition_Source:
EPA
Attribute_Domain_Values:
-
Attribute:
Attribute_Label:
CUSEG
Attribute_Definition:
Unique 11-digit alphanumeric identifier for each reach.
Attribute_Definition_Source:
EPA
Attribute_Domain_Values:
CUSEG in RF1.AAT table.
Attribute:
Attribute_Label:
STRUCT#
Attribute_Definition:
Record number of Structure source file
Attribute_Definition_Source:
Computed
Attribute:
Attribute_Label:
SEQNO
Attribute_Definition:
Sequence Number: A five (5)-digit hydrologic sequence number. Reaches are processed in SEQNO order for flood routing and water quality modeling, beginning anywhere in the file. The sequencing in the database begins at the most upstream reach of the lowest level stream in cataloging unit 01010001. From there on, the next transport reach in this sequence is either the next reach downstream of the immediate reach, or the most upstream reach in the tributary system above the complement reach (if a complement reach having a level higher than the immediate reach is present at the base of the immediate reach). This progression continues until a terminal reach has been encountered. After a terminal reach has been encountered, the sequence continues with the most upstream reach of the lowest level stream of a different terminal stream system, which may or may not be in the same cataloging unit. The above sequencing progresses from terminal stream system to terminal stream system until end of file. (Note: The user may ignore non-transport reaches when encountered while flow routing. To determine if a reach is a non-transport reach, test the value of the RFLAG data element. If it is zero, then the reach is a non-transport reach.)
Attribute_Definition_Source:
EPA
Attribute:
Attribute_Label:
RFLAG
Attribute_Definition:
Transport Reach Flag; if value is 1 then reach is a transport reach, else it is a non-transport reach.
Attribute_Definition_Source:
EPA
Attribute_Domain_Values:
0,1
Attribute:
Attribute_Label:
OWFLAG
Attribute_Definition:
Open Water Flag; if value is 1 then reach is an open water reach, else it is non-open water. These reaches may be any one of the types A, M, or V.
Attribute_Definition_Source:
EPA
Attribute_Domain_Values:
0,1
Attribute:
Attribute_Label:
TFLAG
Attribute_Definition:
Terminal Flag; if value is 1 then reach is a terminal reach, else it is non-terminal. (A terminal reach is one which has no transport reach into which it discharges.) These reaches may be any one of the types T, V, X, or Z.
Attribute_Definition_Source:
EPA
Attribute_Domain_Values:
0,1
Attribute:
Attribute_Label:
SFLAG
Attribute_Definition:
Start Flag; if value is 1 then reach is a start reach, else it is non-start. (A start reach is one which has no transport reach connected to its upstream end.) These reaches may be any one of the types S, X, E, or Z.
Attribute_Definition_Source:
EPA
Attribute_Domain_Values:
0,1
Attribute:
Attribute_Label:
TYPE
Attribute_Definition:
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.

Attribute_Definition_Source:
EPA
Attribute:
Attribute_Label:
SEGL
Attribute_Definition:
Reach Length (miles): The length of the immediate reach calculated from its reach trace record to the nearest tenth of a mile.
Attribute_Definition_Source:
EPA
Attribute:
Attribute_Label:
LEV
Attribute_Definition:
Stream Level: The stream level of the immediate reach. Non-zero values are assigned to transport reaches, and shoreline segments are assigned a level of zero. Each transport reach is assigned a stream level which may be used to define the hierarchical relationship between streams and tributaries in a given drainage network. A tributary to a given stream is always one level higher than the stream into which it flows. For instance, the Mississippi River is a level-one stream, the Ohio River is a level-two stream, and the Tennessee River is a level-three stream. Stream levels are useful in the retrieval algorithms which traverse the Reach File. A "level path" can be followed to identify all mainstem reaches of a given river. For instance, the mainstem of the Mississippi River can be readily identified by retrieving all level-one reaches upstream of the Mississippi River terminus.
Attribute_Definition_Source:
EPA
Attribute_Domain_Values:
0 <= LEV <= 99
Attribute:
Attribute_Label:
J
Attribute_Definition:
Junction Index: A flow routing index pertaining to the junction at the downstream end of the immediate reach. The Junction Index for a reach having a convergent junction at its base is equal to the level of the next reach downstream. For simple junctions (one input reach and one output reach) and divergent junctions (one input reach and two output reaches), this variable is assigned the value of zero. The value of this index for any non-transport reach is also zero. The Junction Index may be used as a subscript in dimensioned arrays of flows and loads in flood routing and water quality modeling. When used as a subscript, it is a pointer to a place in memory where the accumulated flows and loads may be temporarily held while branching off to accumulate flows on another tributary to the reach immediately downstream. This attribute, in combination with SEQNO provides all the topologic information needed for flood routing or modeling water quality through small drainage systems or the entire RF1 drainage system in a single pass. Although more cumbersome for the task, the data elements ULCS, URCS, DSCS, CCS may also be used for this purpose.
Attribute_Definition_Source:
EPA
Attribute_Domain_Values:
Integer; 0 <= J <= 99
Attribute:
Attribute_Label:
K
Attribute_Definition:
Divergence Code: Reaches which are connected to divergent junctions are categorized with this one-digit divergence code. The inflowing reach is referred to as the "input reach"; the outflowing reach receiving the majority of the flow is the "major reach"; and the outflowing reach receiving the minority of the flow is the "minor reach".
Attribute_Definition_Source:
EPA
Attribute_Domain_Values:
The possible values of K are as follows:
  0       Not part of a divergent junction
  1       Input reach where minor reach is downstream left
  2       Input reach where minor reach is downstream right
  3       Minor reach of a divergence
  4       Combination of K values 1 and 3
  5       Combination of K values 2 and 3
  6       Major reach of a divergence
  7       Combination of K values 1 and 6
  8       Combination of K values 2 and 6
Attribute:
Attribute_Label:
PMILE
Attribute_Definition:
Path mile: the distance, in miles, from the downstream end of the immediate reach to the terminus, as measured along the hydraulic transport path. (A terminus is the downstream point of a drainage system where a stream enters an ocean, the ground, a land-locked lake, one of the Great Lakes, or where it flows into Canada or Mexico.)
Attribute_Definition_Source:
EPA
Attribute:
Attribute_Label:
ARBSUM
Attribute_Definition:
Arbolate Sum: The sum of the lengths, in miles, of all digitized reaches upstream from the base of the immediate reach, including all branches of all streams above it. This gives an indication of the size of the drainage system upstream of the reach.
Attribute_Definition_Source:
EPA
Attribute:
Attribute_Label:
DSSEQ
Attribute_Definition:
SEQNO of the immediate downstream reach.
Attribute_Definition_Source:
EPA
Attribute:
Attribute_Label:
USSEQ
Attribute_Definition:
SEQNO of upstream main reach. If one reach is connected to the head of the immediate reach, USSEQ is the SEQNO of that reach; if two are connected to the head of the immediate reach, then USSEQ is the SEQNO of the one having the smaller LEV value. (No more than two reaches may be connected to the head of an RF1 reach.)
Attribute_Definition_Source:
EPA
Attribute:
Attribute_Label:
USDIR
Attribute_Definition:
Upstream Reach Direction of the USSEQ reach.
Attribute_Definition_Source:
EPA
Attribute_Domain_Values:
L or R looking upstream.
Attribute:
Attribute_Label:
TERMID
Attribute_Definition:
Terminal Stream System Identifier. Each transport reach is either a terminal reach or is upstream of a terminal reach. A terminal reach is the most downstream reach in a stream system. The base of a terminal reach connects to an ocean, gulf, great lake, or other sink. All such points of connection have been assigned a terminal identification code (TERMID). All reaches, including the terminal reach, which deliver water to a given terminal point are said to belong to the terminal system designated by TERMID in each reach record.
Attribute_Definition_Source:
EPA
Attribute_Domain_Values:
1 <= TERMID <= 99999
Attribute:
Attribute_Label:
TRMBLV
Attribute_Definition:
Terminal Base Level: This is the stream level of the terminal reach of the stream system to which the immediate reach belongs. Terminal reaches are assigned levels according to the manner in which the streams terminate, as follows:
          TRMBLV    Description
            1       Stream outlet is Atlantic, Pacific, or
                    Gulf of Mexico;
            2       Stream outlet is one of the Great Lakes,
                    or the Great Salt Lake;
            3       Stream exits from U.S. into Canada or
                    Mexico;
            4       Isolated drainage (flows into the
                    ground).
Attribute_Definition_Source:
EPA
Attribute_Domain_Values:
1 <= TRMBLV <= 4
Attribute:
Attribute_Label:
STRTSQ
Attribute_Definition:
The SEQNO of the start reach on the same level path as the immediate reach.
Attribute_Definition_Source:
EPA
Attribute:
Attribute_Label:
STOPSQ
Attribute_Definition:
The SEQNO of the most downstream reach on the same level path as the immediate reach.
Attribute_Definition_Source:
EPA
Entity_Type:
Entity_Type_label:
RF1.STRUCT2
Entity_Type_Definition:
Hydrologic Structure File, part 2
Number_of_Attributes_in_Entity:
8
Attribute:
Attribute_Label:
-
Attribute_Definition:
Hydrologic Structure File, part 2
Attribute_Definition_Source:
EPA
Attribute_Domain_Values:
-
Attribute:
Attribute_Label:
CUSEG
Attribute_Definition:
Unique 11-digit alphanumeric identifier for each reach.
Attribute_Definition_Source:
EPA
Attribute_Domain_Values:
CUSEG in RF1.AAT table.
Attribute:
Attribute_Label:
STRUCT#
Attribute_Definition:
Record number of Structure source file
Attribute_Definition_Source:
Computed
Attribute:
Attribute_Label:
PNAME
Attribute_Definition:
Primary Name For transport reaches, including open water reaches, this is a stream name. For shoreline reaches, this is the name of the open water body. Each transport reach of a given stream level within an open water body will bear the name of the stream which feeds that open water reach at that level (See OWNAME below). Thus the entire watercourse of any given named river in RF1 could be shown by its name alone. For instance, the entire Mississippi River, or the entire Colorado River, or the full course of Four Mile Run or Rock Creek. This is convenient for more reasons than simply showing or accessing data on rivers of a given name; it provides a basis for assigning stream levels, an improtant attribute in building and using databases of rivers. Where names were not giben on the source maps, pwuedo names were inserted into the file based on visual interpretation of the source maps to help in automatically assigning levels and to provide at least a presumed watercourse where streams were not named on the source maps. The psuedo names begin with an asterisk in a form such as "*A", "*B", "*C", etc., to bring attention to the users that names were needed for these streams.
Attribute_Definition_Source:
EPA
Attribute:
Attribute_Label:
PNMCD
Attribute_Definition:
11-digit Primary Name Code: All reaches of a given stream have been assigned the same name and the same primary name code. Other streams having that same name will have different primary name codes.
Attribute_Definition_Source:
EPA
Attribute_Domain_Values:
0 <= PNMCD <= 99999999999
Attribute:
Attribute_Label:
CNAME
Attribute_Definition:
Primary name of complement reach
Attribute_Definition_Source:
EPA
Attribute:
Attribute_Label:
CNMCD
Attribute_Definition:
Primary name code of Complement reach
Attribute_Definition_Source:
EPA
Attribute_Domain_Values:
0 <= CNMCD <= 99999999999
Attribute:
Attribute_Label:
OWNAME
Attribute_Definition:
If OWFLAG = 1 then OWNAME = the name of the open water through which the immediate reach flows, else OWNAME = 30 blank characters.
Attribute_Definition_Source:
EPA
Attribute:
Attribute_Label:
OWNMCD
Attribute_Definition:
If OWFLAG = 1 and OWNAME <> 30 blank characters, then OWNMCD = the namecode of the open water through which the immediate reach flows, else OWNNMCD = 00000000000. Every other lake with the same name has a different OWNMCD.
Attribute_Definition_Source:
EPA
Attribute_Domain_Values:
0 <= OWNMCD <= 99999999999
Entity_Type:
Entity_Type_label:
RF1.STRUCT3
Entity_Type_Definition:
Hydrologic Structure File, part 3
Number_of_Attributes_in_Entity:
7
Attribute:
Attribute_Label:
-
Attribute_Definition:
Hydrologic Structure File, part 3
Attribute_Definition_Source:
EPA
Attribute_Domain_Values:
-
Attribute:
Attribute_Label:
CUSEG
Attribute_Definition:
Unique 11-digit alphanumeric identifier for each reach.
Attribute_Definition_Source:
EPA
Attribute_Domain_Values:
CUSEG in RF1.AAT table.
Attribute:
Attribute_Label:
STRUCT#
Attribute_Definition:
Record number of Structure source file
Attribute_Definition_Source:
Computed
Attribute:
Attribute_Label:
DSCS
Attribute_Definition:
The CUSEG of the immediate downstream reach. In RF1, no more than two reaches may be connected to either end of a reach. If there is no downstream right reach, then DSCS = 00000000000

.
Attribute_Definition_Source:
EPA
Attribute_Domain_Values:
00000000000<= DSCS <= 18100200999
Attribute:
Attribute_Label:
CCS
Attribute_Definition:
The CUSEG of the complement reach. The complement is the reach that flows into the same junction as the immediate reach, except that if the downstream end of the immediate reach is a divergent junction, then CCS identifies the reach which is the minor recipient of the outflow from the immediate reach. In RF1, no more than two reaches may be connected to either end of a reach. If there is no complement reach, then CCS = 00000000000.
Attribute_Definition_Source:
EPA
Attribute_Domain_Values:
00000000000 <= CCS <=18100200999
Attribute:
Attribute_Label:
CDIR
Attribute_Definition:
Complement Direction. This data item reveals whether the complement reach is connected to the left or right bank of the immediate reach at its downstream end.
Attribute_Definition_Source:
EPA
Attribute_Domain_Values:
L or R, looking downstream.
Attribute:
Attribute_Label:
ULCS
Attribute_Definition:
The CUSEG of the upstream left reach (Left looking upstream). In RF1, no more than two reaches may be connected to either end of a reach. If there is no upstream left reach, then ULCS = 00000000000.
Attribute_Definition_Source:
EPA
Attribute_Domain_Values:
00000000000 <= ULCS <= 18100200999
Attribute:
Attribute_Label:
URCS
Attribute_Definition:
The CUSEG of the upstream right reach (Right looking upstream). In RF1, no more than two reaches may be connected to either end of a reach. If there is no upstream right reach, then URCS = 00000000000.
Attribute_Definition_Source:
EPA
Attribute_Domain_Values:
00000000000 <= URCS <= 18100200999
Entity_Type:
Entity_Type_label:
RF1.STRUCT4
Entity_Type_Definition:
Hydrologic Structure File, part 4
Number_of_Attributes_in_Entity:
16
Attribute:
Attribute_Label:
-
Attribute_Definition:
Hydrologic Structure File, part 4
Attribute_Definition_Source:
EPA
Attribute_Domain_Values:
-
Attribute:
Attribute_Label:
CUSEG
Attribute_Definition:
Unique 11-digit alphanumeric identifier for each reach.
Attribute_Definition_Source:
EPA
Attribute_Domain_Values:
CUSEG in RF1.AAT table.
Attribute:
Attribute_Label:
STRUCT#
Attribute_Definition:
Record number of Structure source file
Attribute_Definition_Source:
Computed
Attribute:
Attribute_Label:
ULAT
Attribute_Definition:
Latitude of upstream end of immediate reach. This attribute was copied into the RF1 Structure File directly from the RF1 Trace File.
Attribute_Definition_Source:
EPA
Attribute:
Attribute_Label:
ULON
Attribute_Definition:
Longitude of upstream end of immediate reach. This attribute was copied into the RF1 Structure File directly from the RF1 Trace File.
Attribute_Definition_Source:
EPA
Attribute:
Attribute_Label:
Q3LAT
Attribute_Definition:
Third Quartile Latitude upstream from base of reach. This attribute was copied into the RF1 Structure File directly from the RF1 Trace File.
Attribute_Definition_Source:
EPA
Attribute:
Attribute_Label:
Q3LON
Attribute_Definition:
Third Quartile Longitude upstream from base of reach. This attribute was copied into the RF1 Structure File directly from the RF1 Trace File.
Attribute_Definition_Source:
EPA
Attribute:
Attribute_Label:
MDLAT
Attribute_Definition:
Midpoint Latitude along reach path. This value was copied into the RF1 Structure File directly from the RF1 Trace File.
Attribute_Definition_Source:
EPA
Attribute:
Attribute_Label:
MDLON
Attribute_Definition:
Midpoint Longitude along reach path. This value was copied into the RF1 Structure File directly from the RF1 Trace File.
Attribute_Definition_Source:
EPA
Attribute:
Attribute_Label:
Q1LAT
Attribute_Definition:
First Quartile Latitude upstream from base of reach. This attribute was copied into the RF1 Structure File directly from the RF1 Trace File.
Attribute_Definition_Source:
EPA
Attribute:
Attribute_Label:
Q1LON
Attribute_Definition:>
First Quartile Longitude upstream from base of reach. This attribute was copied into the RF1 Structure File directly from the RF1 Trace File.
Attribute_Definition_Source:
EPA
Attribute:
Attribute_Label:
DLAT
Attribute_Definition:
Latitude of downstream end of immediate reach. This attribute was copied into the RF1 Structure File directly from the RF1 Trace File.
Attribute_Definition_Source:
EPA
Attribute:
Attribute_Label:
DLON
Attribute_Definition:
Longitude of downstream end of immediate reach. This attribute was copied into the RF1 Structure File directly from the RF1 Trace File.
Attribute_Definition_Source:
EPA
Attribute:
Attribute_Label:
MINLAT
Attribute_Definition:
Minimum Latitude of immediate reach. This value was populated in the RF1 Structure File directly from the RF1 Trace File.
Attribute_Definition_Source:
EPA
Attribute:
Attribute_Label:
MINLON
Attribute_Definition:
Minimum Longitude of the immediate reach. This value was populated in the RF1 Structure File directly from the RF1 Trace File.
Attribute_Definition_Source:
EPA
Attribute:
Attribute_Label:
MAXLAT
Attribute_Definition:
Maximum Latitude of immediate reach. This value was populated in the RF1 Structure File directly from the RF1 Trace File.
Attribute_Definition_Source:
EPA
Attribute:
Attribute_Label:
MAXLON
Attribute_Definition:
Maximum Longitude of the immediate reach. This value was populated in the RF1 Structure File directly from the RF1 Trace File.
Attribute_Definition_Source:
EPA
Entity_Type:
Entity_Type_label:
RF1.STRUCT5
Entity_Type_Definition:
Hydrologic Structure File, part 5
Number_of_Attributes_in_Entity:
10
Attribute:
Attribute_Label:
-
Attribute_Definition:
Hydrologic Structure File, part 5
Attribute_Definition_Source:
EPA

-
Attribute:
Attribute_Label:
CUSEG
Attribute_Definition:
Unique 11-digit alphanumeric identifier for each reach.
Attribute_Definition_Source:
EPA
Attribute_Domain_Values:
CUSEG in RF1.AAT table.
Attribute:
Attribute_Label:
STRUCT#
Attribute_Definition:
Record number of Structure source file
Attribute_Definition_Source:
Computed
Attribute:
Attribute_Label:
TWLATI
Attribute_Definition:
Tucker window latitude of first corner. A Tucker window is the smallest rectangle which will enclose the immediate reach.
Attribute_Definition_Source:
EPA
Attribute:
Attribute_Label:
TWLAG1
Attribute_Definition:
Tucker window longitude of first corner.
Attribute_Definition_Source:
EPA (See TWLATI)
Attribute:
Attribute_Label:
TWLAT2
Attribute_Definition:
Tucker window latitude of second corner.
Attribute_Definition_Source:
EPA (See TWLATI)
Attribute:
Attribute_Label:
TWLAG2
Attribute_Definition:
Tucker window longitude of second corner.
Attribute_Definition_Source:
EPA (See TWLATI)
Attribute:
Attribute_Label:
TWLAT3
Attribute_Definition:
Tucker window latitude of third corner.
Attribute_Definition_Source:
EPA (See TWLATI)
Attribute:
Attribute_Label:
TWLAG3
Attribute_Definition:
Tucker window longitude of third corner.
Attribute_Definition_Source:
EPA (See TWLATI)
Attribute:
Attribute_Label:
TWLAT4
Attribute_Definition:
Tucker window latitude of fourth corner.
Attribute_Definition_Source:
EPA (See TWLATI)
Attribute:
Attribute_Label:
TWLAG4
Attribute_Definition:
Tucker window longitude of fourth corner.
Attribute_Definition_Source:
EPA (See TWLATI)
Entity_Type:
Entity_Type_label:
RF1.STRUCT6
Entity_Type_Definition:
Hydrologic Structure File, part 6
Number_of_Attributes_in_Entity:
14
Attribute:
Attribute_Label:
-
Attribute_Definition:
Hydrologic Structure File, part 6
Attribute_Definition_Source:
EPA
Attribute_Domain_Values:
-
Attribute:
Attribute_Label:
CUSEG
Attribute_Definition:
Unique 11-digit alphanumeric identifier for each reach.
Attribute_Definition_Source:
EPA
Attribute_Domain_Values:
CUSEG in RF1.AAT table.
Attribute:
Attribute_Label:
STRUCT#
Attribute_Definition:
Record number of Structure source file
Attribute_Definition_Source:
Computed
Attribute:
Attribute_Label:
NSTCO
Attribute_Definition:
Number of State/County Codes populated for this reach. See STCO1,2,3,4,5,6 and 7.
Attribute_Definition_Source:
EPA
Attribute_Domain_Values:
0 through 7
Attribute:
Attribute_Label:
SCFLAG
Attribute_Definition:
State/County Flag. The State-county flag, which can take the following values:
                A -  The reach is totally enclosed by one county,
                B -  At least one endpoint of the reach lies on
                     the border between counties,
                C -  The reach occupies more than one county and
                     neither endpoint of the reach lies on a
                     border between counties.
                0 -  None exists
Attribute_Definition_Source:
EPA
Attribute:
Attribute_Label:
STCO1
Attribute_Definition:
State/County FIPS Code 1: The first of seven 5-digit FIPS codes associated with the reach. The first two (2) digits are the State code and the last three digits are the County code.
Attribute_Definition_Source:
EPA
Attribute:
Attribute_Label:
STCO2
Attribute_Definition:
State/County FIPS Code 2: See STCO1
Attribute_Definition_Source:
EPA
Attribute:
Attribute_Label:
STCO3
Attribute_Definition:
State/County FIPS Code 3: See STCO1
Attribute_Definition_Source:
EPA
Attribute:
Attribute_Label:
STCO4
Attribute_Definition:
State/County FIPS Code 4: See STCO1
Attribute_Definition_Source:
EPA
Attribute:
Attribute_Label:
STCO5
Attribute_Definition:
State/County FIPS Code 5: See STCO1
Attribute_Definition_Source:
EPA
Attribute:
Attribute_Label:
STCO6
Attribute_Definition:
State/County FIPS Code 6: See STCO1
Attribute_Definition_Source:
EPA
Attribute:
Attribute_Label:
STCO7
Attribute_Definition:
State/County FIPS Code 7: See STCO1
Attribute_Definition_Source:
EPA
Attribute:
Attribute_Label:
STCO8
Attribute_Definition:
State/County FIPS Code 8: See STCO1
Attribute_Definition_Source:
EPA
Attribute:
Attribute_Label:
QC1
Attribute_Definition:
Parameter for special uses
Attribute_Definition_Source:
EPA
Attribute:
Attribute_Label:
QC2
Attribute_Definition:
Parameter for special uses
Attribute_Definition_Source:
EPA
5.2 Overview Description:
Entity_and_Attribute_Overview:
In RF1, each reach is uniquely identified by a cataloging unit (CATUNIT) combined with a segment number (SEG). This is the RF1 reach identifier, a nationally unique identifier for stream and shoreline reaches referred to herein as CUSEG.

 

 

The hydrologic Structure File contains the RF1 topologic information and basic hydrologic information about each reach. Because of its size, it was split into 6 parts, RF1.STRUCTx, where 1 <= x <= 6. Each record contains both the CUSEG code and the record number (STRUCT#) of the original file.

129 CUSEG's in the RF1.AAT file have no match in the RF1.STRUCTx files, and 3607 RF1.STRUCTx CUSEG's have no match in the RF1.AAT file. The RF1.CSLIST file contains a complete list of all CUSEG codes in either file, and indicates whether a particular CUSEG is used in a file.

Entity_and_Attribute_Detail_Citation:
See Entity_and_Attribute_Information
6.0 Distribution_Information:
6.1 Distributor_Contact_Organization:
EPA Office of Wetlands Oceans and Watersheds - STORET User Assistance
Distributor_Contact_Address:
See Section 10.4 - Contact Address
Distributor_Contact_Voice_Telephone:
See Section 10.5 - Contact Voice Telephone
Distributor_Contact_Electronic_Mail_Address:
See Section 10.8 - Contact Electronic Mail Address
6.2 Resource_Description:
RF1 Configured for ARC/INFO
6.3 Distribution_Liability:
Although these data have been processed successfully on a computer system at the U.S. Environmental Protection Agency, no warranty expressed or implied is made by the EPA regarding the utility of the data on any other system, nor shall the act of distribution constitute any such warranty.
6.4 Standard_Order_Process:
Digital_Form:
Digital_Transfer_Information:
Format_Name:
ARC/INFO export. Files are compressed with the GNU-zip public-domain file compression utility. The transfer filesize of the national file (rf1.e00.gz) is approximately 100 MB, compressed.
Digital_Transfer_Option:
Online_Option:
Computer_Contact_Information:
Network_Address:
Network_Resource_Name:
Available via HTTP. Click on the resource name below to transfer the data to your site.
http://www.epa.gov/owow/reach/rf1.e00.gz
Fees:The online option is available at no charge.
 

 

6.7 Available_Time_Period:
Immediate.
7.0 Metadata_Reference_Information:
7.1 Metadata_Date:
19960601
7.4 Metadata_Contact:
See Section 10.0 Contact Information
7.5 Metadata_Standard_Name:
FGDC Content Standards for Digital Geospatial Metadata
7.6 Metadata_Standard_Version:
19940608
7.7 Metadata_Time_Convention:
Local Time
8.0 Citation_Information:
8.1 Originator:
U.S. Environmental Protection Agency
8.2 Publication_Date:
1996
8.4 Title:
Reach File Version 1 Configured for ARC/INFO
8.5 Edition:
ARC/INFO Configuration Edition 3.0
8.6 Geospatial Data Presentation Form:
map
8.8 Publication_Information:
Publication_Place:
Washington, D.C.
Publisher:
U.S. Environmental Protection Agency
8.10 Online Linkage:
EPA Office of Wetlands, Oceans and Watersheds (http://www.epa.gov/OWOW)
9.0 Time Period Information
9.1 Single_Date/Time:
Calendar_Date:
051796
10.0 Contact Information
10.1 Contact Person Primary
Contact Organization:
EPA Office of Wetlands, Oceans, and Watersheds (OWOW)
STORET User Assistance
10.2 Contact Organization Primary
Contact Organization:
EPA Office of Wetlands, Oceans, and Watersheds (OWOW)
STORET User Assistance
10.4 Contact Address
Address Type
Mailing and physical address
Address
401 M Street SW (4503F)

Washington, DC 20460
10.5 Contact Voice Telephone
(800) 424-9067
10.8 Contact Electronic Mail Address
storet@epamail.epa.gov

Local Navigation

Jump to main content.