U.S. Rivers and Streams

Metadata also available as

Metadata:


Identification_Information:
Citation:
Citation_Information:
Originator:
U.S. Geological Survey in cooperation with U.S. Environmental Protection Agency
Originator: Esri
Publication_Date: 20120301
Title: U.S. Rivers and Streams
Edition: 2012
Geospatial_Data_Presentation_Form: vector digital data
Series_Information:
Series_Name: Data & Maps for ArcGIS®
Issue_Identification: 2012 - World, Europe, and United States
Publication_Information:
Publication_Place: Redlands, California, USA
Publisher: Esri
Other_Citation_Details: Location: \usa\hydro
Description:
Abstract:
U.S. Rivers and Streams represents detailed rivers and streams in the United States.
Purpose:
U.S. Rivers and Streams provides a database of linear water features that interconnects and identifies the stream segments or reaches that comprise the surface water drainage system of United States.
Supplemental_Information: Largest scale when displaying the data: 1:24,000.
Time_Period_of_Content:
Time_Period_Information:
Single_Date/Time:
Calendar_Date: 2004
Currentness_Reference: publication date
Status:
Progress: Complete
Maintenance_and_Update_Frequency: Annually
Spatial_Domain:
Bounding_Coordinates:
West_Bounding_Coordinate: -160.220853
East_Bounding_Coordinate: -66.988396
North_Bounding_Coordinate: 49.376613
South_Bounding_Coordinate: 18.922673
Keywords:
Theme:
Theme_Keyword_Thesaurus: None
Theme_Keyword: line
Theme_Keyword: rivers
Theme_Keyword: streams
Theme_Keyword: hydrography
Theme_Keyword: inlandWaters
Place:
Place_Keyword_Thesaurus: None
Place_Keyword: United States
Temporal:
Temporal_Keyword_Thesaurus: None
Temporal_Keyword: 2004
Access_Constraints: Access granted to Licensee only.
Use_Constraints:
The data are provided by multiple, third party data vendors under license to Esri for inclusion on Data & Maps for ArcGIS® for use with Esri® software. Each data vendor has its own data licensing policies and may grant varying redistribution rights to end users. Please consult the redistribution rights below for this data set provided on Data & Maps. As used herein, “Geodata” shall mean any digital data set consisting of geographic data coordinates and associated attributes.
The redistribution rights for this data set: Redistribution rights are granted by the data vendor for hard-copy renditions or static, electronic map images (e.g. .gif, .jpeg, etc.) that are plotted, printed, or publicly displayed with proper metadata and source/copyright attribution to the respective data vendor(s). Geodata is redistributable with a Value-Added Software Application developed by Esri Business Partners on a royalty-free basis with proper metadata and source/copyright attribution to the respective data vendor(s). Geodata is redistributable without a Value-Added Software Application (i.e., adding the sample data to an existing, [non]commercial data set for redistribution) with proper metadata and source/copyright attribution to the respective data vendor(s).
The terms and conditions below apply to all the data sets provided on Data & Maps.
Proprietary Rights and Copyright: Licensee acknowledges that the Data and Related Materials contain proprietary and confidential property of Esri and its licensor(s). The Data and Related Materials are owned by Esri and its licensor(s) and are protected by United States copyright laws and applicable international copyright treaties and/or conventions.
Limited Warranty and Disclaimer: Esri warrants that the media upon which the Data and Related Materials are provided will be free from defects in materials and workmanship under normal use and service for a period of ninety (90) days from the date of receipt.
THE DATA AND RELATED MATERIALS ARE EXCLUDED FROM THE LIMITED WARRANTY, AND THE LICENSEE EXPRESSLY ACKNOWLEDGES THAT THE DATA CONTAINS SOME NONCONFORMITIES, DEFECTS, OR ERRORS. Esri DOES NOT WARRANT THAT THE DATA WILL MEET LICENSEE'S NEEDS OR EXPECTATIONS; THAT THE USE OF THE DATA WILL BE UNINTERRUPTED; OR THAT ALL NONCONFORMITIES, DEFECTS, OR ERRORS CAN OR WILL BE CORRECTED. Esri IS NOT INVITING RELIANCE ON THIS DATA, AND THE LICENSEE SHOULD ALWAYS VERIFY ACTUAL DATA.
EXCEPT FOR THE LIMITED WARRANTY SET FORTH ABOVE, THE DATA AND RELATED MATERIALS CONTAINED THEREIN ARE PROVIDED "AS-IS," WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE.
HIGH RISK ACTIVITIES: (A) THE DATA AND RELATED MATERIALS ARE NOT FAULT-TOLERANT AND ARE NOT DESIGNED, MANUFACTURED, OR INTENDED FOR USE OR RESALE FOR INSURANCE UNDERWRITING OR WITH CRITICAL HEALTH AND SAFETY OR ONLINE CONTROL EQUIPMENT IN HAZARDOUS ENVIRONMENTS THAT REQUIRE FAIL-SAFE PERFORMANCE, INCLUDING, BUT NOT LIMITED TO THE OPERATION OF NUCLEAR FACILITIES, NAVIGATION OR GUIDANCE (I.E., AIRCRAFT, NAUTICAL VEHICLE, ETC.), OR COMMUNICATION SYSTEMS, AIR TRAFFIC CONTROL, EMERGENCY RESPONSE, TERRORISM PREVENTION OR RESPONSE, LIFE SUPPORT, OR WEAPONS SYSTEMS ("HIGH RISK ACTIVITIES"). Esri SPECIFICALLY DISCLAIMS ANY EXPRESS OR IMPLIED WARRANTY OF FITNESS FOR HIGH RISK ACTIVITIES.
(B) TO THE EXTENT PERMITTED BY LAW, LICENSEE AGREES TO INDEMNIFY, DEFEND, AND HOLD Esri, ITS OFFICERS, DIRECTORS, EMPLOYEES, AGENTS, SUBCONTRACTORS, LICENSORS, SUCCESSORS, AND ASSIGNS HARMLESS FROM AND AGAINST ANY AND ALL LIABILITY, LOSSES, CLAIMS, EXPENSES (INCLUDING ATTORNEYS' FEES), DEMANDS, OR DAMAGES OF ANY KIND, INCLUDING DIRECT, INDIRECT, SPECIAL, PUNITIVE, INCIDENTAL, OR CONSEQUENTIAL DAMAGES, ARISING OUT OF OR IN ANY WAY CONNECTED WITH LICENSEE'S USE OR PERMITTING THE USE BY OTHERS OF THE DATA, AND VENDOR'S HARDWARE OR SOFTWARE FOR HIGH RISK ACTIVITIES. DELIVERY OF THE DATA, AND VENDOR'S HARDWARE OR SOFTWARE DOES NOT CONSTITUTE A WAIVER OF THE RIGHTS AND OBLIGATIONS SET FORTH IN THIS ARTICLE.
Exclusive Remedy and Limitation of Liability: The entire liability of Esri or its licensor(s) and Licensee's exclusive remedy shall be to terminate the Agreement upon Licensee returning the Data and Related Materials to Esri with a copy of Licensee's invoice/receipt and Esri returning the license fees paid to Licensee.
IN NO EVENT SHALL Esri AND/OR ITS LICENSOR(S) BE LIABLE FOR COSTS OF PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOST PROFITS, LOST SALES, OR BUSINESS EXPENDITURES, INVESTMENTS, OR COMMITMENTS IN CONNECTION WITH ANY BUSINESS; LOSS OF ANY GOODWILL; OR FOR ANY INDIRECT, SPECIAL, INCIDENTAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES ARISING OUT OF THIS AGREEMENT OR USE OF THE DATA AND RELATED MATERIALS, HOWEVER CAUSED, ON ANY THEORY OF LIABILITY, AND WHETHER OR NOT Esri OR ITS LICENSOR(S) HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. THESE LIMITATIONS SHALL APPLY NOTWITHSTANDING ANY FAILURE OF ESSENTIAL PURPOSE OF ANY EXCLUSIVE REMEDY.
Third Party Beneficiary: Esri's licensor(s) has (have) authorized Esri to (sub)distribute and (sub)license its (their) data as incorporated into the Data and Related Materials. As an intended third party beneficiary to this Agreement, the Esri licensor(s) is (are) entitled to directly enforce, in its own name, the rights and obligations undertaken by the Licensee and to seek all legal and equitable remedies as are afforded to Esri.
In the event that the data vendor(s) has (have) granted the end user permission to redistribute the Geodata, please use proper proprietary or copyright attribution for the various data vendor(s), and provide the associated metadata file(s) with the Geodata. In compliance with FGDC metadata standards, Esri has attempted to practice proper metadata methodologies by providing any data source information, descriptions, and file names to assist in this effort.
Point_of_Contact:
Contact_Information:
Contact_Organization_Primary:
Contact_Organization: Esri
Contact_Person: ArcGIS Content Team
Contact_Address:
Address_Type: mailing and physical address
Address: 380 New York Street
City: Redlands
State_or_Province: California
Postal_Code: 92373-8100
Country: USA
Contact_Voice_Telephone: 909-793-2853
Contact_Facsimile_Telephone: 909-793-5953
Contact_Electronic_Mail_Address: info@esri.com
Hours_of_Service: 7:00 a.m.–5:30 p.m. Pacific time, Monday–Friday
Contact_Instructions:
In the United States– Please direct all inquiries regarding software/data pricing and consulting services to your local Esri Regional Office. For support, you may contact Esri Support Center by telephone (voice) between 5:00 a.m. and 5:00 p.m. Pacific time, Monday through Friday, by dialing 888-377-4575; facsimile (fax) available at 909-792-0960; electronic mail (e-mail) support@esri.com; or visit <http://support.esri.com/>; Esri holidays excluded.
Outside the United States– Please direct all inquiries regarding software/data pricing, sales, support, and consulting services to your local Esri Office. This information can be found at <http://www.esri.com/about-esri/locations.html>.
For other questions or comments, you may contact Esri headquarters by e-mail, telephone, or fax or write to us.
Native_Data_Set_Environment:
Microsoft Windows XP Version 5.1 (Build 2600) Service Pack 1; Esri ArcCatalog 9.1.0.722

Data_Quality_Information:
Logical_Consistency_Report:
The shapefile is converted to SDC (Smart Data Compression) format using tools in ArcGIS. The SDC data set is then imported into a file geodatabase to verify, validate, and if needed repair the geometry.
Completeness_Report:
After processing, the data set is checked for drawing display and number of records and file sizes compared with source materials. Some of the cartographic disparities with this data, inherent in the original 1:100,000 source data, remain in that the density of features can change abruptly.
[From National Hydrography Dataset (NHD) documentation - The completeness of the data reflects the content of the sources, which, in the initial release of the National Hydrography Dataset, most often are U.S. Geological Survey topographic maps. Features found on the ground may have been eliminated or generalized on the source graphic because of scale and legibility constraints. In general, streams longer than one mile (approximately 1.6 kilometers) were collected. Most streams that flow from a lake were collected regardless of length. Only definite channels were collected so not all swamp/marsh features have stream/rivers delineated through them. Lake/ponds having an area greater than 6 acres (approximately 2.4 hectares) were collected. Note, however, that these general rules were applied unevenly among maps during compilation. Some map quadrangles have a much sparser pattern of hydrography than do adjoining maps and these differences continue in the digital rendition of these features. Transport reaches are defined on nearly all features of type stream/river, canal/ditch, artificial path, pipeline, and connector. Waterbody reaches are defined on the subset of lake/pond features that were identified as waterbodies during the development of Reach File Version 3. Most attention in applying geographic names was given to transport reaches that follow stream/rivers and waterbody reaches. Near the international boundaries with Canada and Mexico, only the parts of features within the United States are delineated. Detailed capture conditions are provided for every feature type in the Standards for National Hydrography Dataset (USGS, 1999), available online through <http://geography.usgs.gov/standards/.>]
Positional_Accuracy:
Horizontal_Positional_Accuracy:
Horizontal_Positional_Accuracy_Report:
The data set originally comes from several sources. Most of the data is from U.S. Geological Survey topographic quadrangle maps or sources that exceed its horizontal accuracy. These maps were compiled to meet National Map Accuracy Standards. For horizontal accuracy, this standard is met if at least 90 percent of points tested are within 0.02 inch (at map scale) of their true position. At 1:100,000 scale, 0.02 inch is approximately 167 feet (50.8 meters).
Lineage:
Source_Information:
Source_Citation:
Citation_Information:
Originator:
U.S. Geological Survey in cooperation with U.S. Environmental Protection Agency
Publication_Date: 2004
Title: National Hydrography Dataset
Geospatial_Data_Presentation_Form: vector digital data
Publication_Information:
Publication_Place: Reston, Virginia, USA
Publisher: U.S. Geological Survey
Other_Citation_Details:
The tiles were downloaded in December 2004.
National Hydrography Dataset is an ongoing project with Alaska being worked on currently.
Online_Linkage: <http://nhd.usgs.gov/>
Online_Linkage: <ftp://nhdftp.usgs.gov/SubRegions/Medium/>
Source_Scale_Denominator: 100000
Type_of_Source_Media: online
Source_Time_Period_of_Content:
Time_Period_Information:
Single_Date/Time:
Calendar_Date: 2004
Source_Currentness_Reference: publication date
Source_Citation_Abbreviation: NHD
Source_Contribution: Attribute and geospatial data
Process_Step:
Process_Description:
Convert DLG [Digital Line Graph] data to features: This process converted DLG data to features and associated characteristics and converted the coordinate system to geographic (longitude-latitude) coordinates in NAD83 in five steps: 1. The USGS's [U.S. Geological Survey] "Batch DLG-3 to DLG-F Conversion System" converted DLG-3 nodes, lines, areas, and associated attribute codes to temporary features and associated characteristics. Known conditions for which conversions could not be reliably made were flagged for later inspection. Only known conversion problems were flagged, and no additional steps were taken to detect or repair discrepancies in the original DLG-3 or the converted NHD [National Hydrography Dataset]. 2. A default value of a characteristic was added in cases where the description was incomplete. 3. All instances in which data were flagged were inspected and resolved interactively. 4. Feature delineation rules were applied to the temporary features in a batch process to create the final version of features. 5. Coordinate values were converted to geographic coordinates and to the NAD83 using the NADCON software version 2.1 (National Geodetic Survey, n.d.).
This process generated the "features" data. Build reaches: The basic steps for building reaches are as follows: 1. Convert RF3 [Reach File Version 3] to RF3" (RF3 double prime). This batch operation processed Reach File Version 3 to delete duplicate reaches, reassign reaches to the correct cataloging unit, validate geographic names assigned to reaches against data from the Geographic Names Information System (December 1996 extract), apply updates supplied by the States of California and Arizona, redelineate reaches on the basis of standards used for the NHD, and identify inflow/outflow points where transport reaches entered and exited waterbodies. 2. Create artificial paths. Using waterbodies from the feature data and inflow/outflow points extracted from RF3", this process automatically generated the centerlines used to delineate artificial paths within waterbodies by using subroutines within the ARC/INFO® GRID module. 3. Blind pass. This batch step conflated features and RF3" reaches and transferred reach information (reach code, reach date, name, stream level, and flow relationships) to the features. It also integrated the artificial paths generated in the previous step with the other features, built reaches on the artificial paths, and assigned geographic names (February 1995 extract) to waterbodies. 4. Quadrangle-based visual pass. During this interactive step, analysts ensured that the data developed in the previous batch processes conformed to reach delineation rules and that reaches were assigned to the appropriate cataloging unit. Batch procedures identified and developed a list of possible errors. (Errors not detected by the software may continue in the data.) Using the list, software presented each case to analysts to make appropriate edits to the data. Analysts recorded notes about repairs that could not be made and about other errors in the data. (These notes are encoded in the cataloging unit digital update units.) 5. Build superquads. After the quadrangle-based visual pass was complete, all quadrangles that cover all or part of each cataloging unit were paneled into a superquad. In this batch process, reaches that cross quad boundaries were corrected to conform to reach delineation rules. 6. Cataloging unit-based visual pass. As they did with the quadrangle-based visual pass, analysts ensured that reaches conformed to reach delineation rules. Batch procedures identified and developed a list of possible errors. (Errors not detected by the software may continue in the data.) Analysts examined each error and corrected the data. Analysts recorded notes about repairs that could not be made and about other errors in the data. (These notes are encoded in the cataloging unit digital update units.) 7. Central quality assurance/quality control. This step (1) confirmed that integrity checks were performed successfully during the visual pass activity, and (2) assessed statistics gathered during the earlier processes to determine if additional review of data was needed. A check of data from the cataloging unit-based visual pass was run in batch; any data that did not pass the procedure were reviewed interactively. If substantive changes were required, the data were reprocessed using procedures (as required) described in previous steps. The edited data then were rechecked using the central quality assurance/quality control process. 8. Data preparation and database load. This batch procedure performed final processing to the data emerging from the quality assurance/quality control step. Some of the activities included assigning the final reach codes, building waterbody reaches, adding final artificial paths in waterbodies, and implementing any recent changes in standards for the NHD. The spelling of geographic names was replaced using the March 1999 data extract from the Geographic Names Information System. After this, reaches, features, characteristics, geographic names, and relations were loaded into the database that holds the NHD. 9. Flow relation correction and validation. The flow relations were checked for consistency through a batch procedure, which generated a list of possible errors. Software presented possible errors to analysts, who corrected flow relations and, occasionally, the delineation of reaches. Changes were posted to the database. 10. Extract distribution copies of data. Data for a cataloging unit were extracted from the database and converted into an ARC/INFO® workspace containing coverages and other files. Data available in the Spatial Data Transfer Standard format were developed from the workspaces. The workspaces and the Spatial Data Transfer Standard-formatted files were made available to the public.
Modified flow relationships for a subbasin.
Updated stream level attributes based on flow relationships produced by the flow validation process. Stream level updates were based upon names for named reaches and the arbolate sum for unnamed reaches. Arbolate sum for any reach on the network is the sum of the lengths of all upstream reaches connected to that reach through flow relationships.
Modified Names: Added names to NHD reaches by comparing them to the GNIS [Geographic Names Information System] coordinates using ArcView NHD Tools.
Modified Flow Relationships using NHD ArcView Tools: Performed flow quality assurance/control and repaired flow relationships, as needed.
Modified Names using NHD ArcView Tools: Added names to NHD reaches and waterbodies by comparing them to the GNIS coordinates.
Replaced branched and disjoint (disconnected) reaches with linear reaches in NHDFlowline. This change occurred during the conversion to the geodatabase model. Each NHDFlowline that was part of a branched or disjoint reach was assigned to a new reach. The ComID of the NHDFlowline was unchanged. The change information from the old reach to the new reach was captured in the NHDReachCrossReference table. Each new reach has M values assigned from 0 to 100.
Merged and/or split area features (NHDWaterbody, NHDArea, region.wb, region.lm) and updated associated artificial path WBAreaComID (wb_com_id) values. This change occurred during the conversion to the geodatabase model. If adjacent or overlapping area features had identical classifications, including ReachCode where applicable, the features were merged. If an area feature exceeded 100 sq. km. (25 sq. km. for canal/ditch, stream/river, or submerged stream) and crossed a subbasin boundary, the feature was split at the subbasin boundary. If any sliver polygons of a size of less than 5 sq. km. adjoined the split features, the slivers were merged back into the larger area feature. Merged or split area features were assigned a new ComID.
Deleted name and GNIS Id values from NHD features where GNIS feature type is valley. This update, at the request of the GNIS staff, is to remove the possible application of a valley name (hypsographic feature) to a stream/river (hydrographic feature). In most instances, the valley name cannot be presumed to apply to the stream/river. Where the name does apply to the stream/river, the GNIS name must be updated from valley to a hydrographic feature type in order for the name to be valid in the NHD.
Process_Date: 1994-2004
Source_Produced_Citation_Abbreviation: NHD
Process_Step:
Process_Description:
The following steps were performed by Esri: Downloaded the over 200 compressed files from <ftp://nhdftp.usgs.gov/SubRegions/Medium/> and extracted them. Used the NHDFlowline source feature class from each NHD source tile. Merged all NHD source tiles into a single data set. Replaced the numeric values with text strings for the attribute FTYPE. Added the attribute AP_WITHIN. For features where attribute FTYPE is "Artificial Path", attribute AP_WITHIN is populated with the value from the FTYPE attribute of the U.S. Water Bodies that the feature falls within. For all other features, attribute AP_WITHIN is blank. Added attributes METERS and FEET and calculated their values. Created ArcGIS® layer file (.lyr), projection file (.prj), and spatial indices.
Source_Used_Citation_Abbreviation: NHD
Process_Date: 20050328

Spatial_Data_Organization_Information:
Direct_Spatial_Reference_Method: Vector
Point_and_Vector_Object_Information:
SDTS_Terms_Description:
SDTS_Point_and_Vector_Object_Type: String
Point_and_Vector_Object_Count: 2955059

Spatial_Reference_Information:
Horizontal_Coordinate_System_Definition:
Geographic:
Latitude_Resolution: 0.000000
Longitude_Resolution: 0.000000
Geographic_Coordinate_Units: Decimal degrees
Geodetic_Model:
Horizontal_Datum_Name: D_WGS_1984
Ellipsoid_Name: WGS_1984
Semi-major_Axis: 6378137.000000
Denominator_of_Flattening_Ratio: 298.257224

Entity_and_Attribute_Information:
Detailed_Description:
Entity_Type:
Entity_Type_Label: dtl_riv
Entity_Type_Definition:
The lines represent the detailed rivers and streams in the United States.
Entity_Type_Definition_Source: Esri
Attribute:
Attribute_Label: ObjectID
Attribute_Definition: Internal feature number.
Attribute_Definition_Source: Esri
Attribute_Domain_Values:
Unrepresentable_Domain:
Sequential unique whole numbers that are automatically generated.
Attribute:
Attribute_Label: NAME
Attribute_Definition: The name of the river or stream.
Attribute_Definition_Source: Esri
Attribute_Domain_Values:
Unrepresentable_Domain: Names for the features.
Attribute:
Attribute_Label: FTYPE
Attribute_Definition: The feature type of river or stream.
Attribute_Definition_Source: Esri
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: ARTIFICIAL PATH
Enumerated_Domain_Value_Definition:
The linear water feature is an abstraction to facilitate hydrologic modeling and connectivity through open water bodies and along coastal and Great Lakes shorelines and to act as a surrogate for lakes and other water bodies.
Enumerated_Domain_Value_Definition_Source:
U.S. Geological Survey in cooperation with U.S. Environmental Protection Agency
Enumerated_Domain:
Enumerated_Domain_Value: CANAL/DITCH
Enumerated_Domain_Value_Definition:
The linear water feature is an artificial open waterway (1-dimensional) constructed to transport water, to irrigate or drain land, to connect two or more bodies of water, or to serve as a waterway for watercraft.
Enumerated_Domain_Value_Definition_Source:
U.S. Geological Survey in cooperation with U.S. Environmental Protection Agency
Enumerated_Domain:
Enumerated_Domain_Value: CONNECTOR
Enumerated_Domain_Value_Definition:
The linear water feature is a known, but nonspecific, connection between two nonadjacent network segments. It fills gaps in the delineation of features through which water flows.
Enumerated_Domain_Value_Definition_Source:
U.S. Geological Survey in cooperation with U.S. Environmental Protection Agency
Enumerated_Domain:
Enumerated_Domain_Value: PIPELINE
Enumerated_Domain_Value_Definition:
The linear water feature is a closed conduit, with pumps, valves and control devices, for conveying fluids, gases, or finely divided solids.
Enumerated_Domain_Value_Definition_Source:
U.S. Geological Survey in cooperation with U.S. Environmental Protection Agency
Enumerated_Domain:
Enumerated_Domain_Value: STREAM/RIVER
Enumerated_Domain_Value_Definition:
The linear water feature is flowing water (1-dimensional) as a stream or river.
Enumerated_Domain_Value_Definition_Source:
U.S. Geological Survey in cooperation with U.S. Environmental Protection Agency
Attribute:
Attribute_Label: FCODE
Attribute_Definition:
The feature code (five-digit) for the river or stream. The first three digits encode the feature type; the last two digits encode values for a set of characteristics associated with the feature.
Attribute_Definition_Source:
U.S. Geological Survey in cooperation with U.S. Environmental Protection Agency
Attribute_Domain_Values:
Codeset_Domain:
Codeset_Name:
The National Hydrography Dataset, Concepts and Contents - Appendix B. Feature code and description field structures and definitions
Codeset_Source:
U.S. Geological Survey in cooperation with U.S. Environmental Protection Agency
Attribute:
Attribute_Label: FCODE_DESC
Attribute_Definition: The description of the feature code for the river or stream.
Attribute_Definition_Source: Esri
Attribute_Domain_Values:
Codeset_Domain:
Codeset_Name:
The National Hydrography Dataset, Concepts and Contents - Appendix B. Feature code and description field structures and definitions
Codeset_Source:
U.S. Geological Survey in cooperation with U.S. Environmental Protection Agency
Attribute:
Attribute_Label: STRM_LEVEL
Attribute_Definition:
The numeric code that identifies the path level of water flow through a drainage network for the river or stream. The lowest value ["1" for rivers or streams that terminate at the Atlantic, Pacific, or Arctic Oceans, the Gulf of Mexico, or the Caribbean Sea; "2" for rivers or streams that terminate at the Great Lakes or the Great Salt Lake; "3" for rivers or streams that terminate at the boundary of the United States with Canada or Mexico; "4" for rivers or streams that terminate at any other place (isolated drainage).] for stream level is assigned to a river or stream at the end of a flow and to upstream rivers and streams that trace the main path of flow back to the head. The stream level value is incremented by one and is assigned to all rivers and streams that terminate at this path (that is, all tributaries to the path) and to all rivers and streams that trace the main path of the flow along each tributary back to its head. The stream level value is incremented again and is assigned to rivers and streams that trace the main path of the tributaries to their heads. This process is continued until all rivers and streams for which flow is encoded are assigned a stream level.
Attribute_Definition_Source:
U.S. Geological Survey in cooperation with U.S. Environmental Protection Agency
Attribute_Domain_Values:
Range_Domain:
Range_Domain_Minimum: 1
Range_Domain_Maximum: 99
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: 428
Enumerated_Domain_Value_Definition: The linear water feature is unspecified.
Enumerated_Domain_Value_Definition_Source:
U.S. Geological Survey in cooperation with U.S. Environmental Protection Agency
Attribute:
Attribute_Label: AP_WITHIN
Attribute_Definition:
The feature type of the water body that the linear water feature allows connectivity through. Only pertains to linear water features that have a feature type of "Artificial Path".
Attribute_Definition_Source: Esri
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: Canal/Ditch
Enumerated_Domain_Value_Definition:
The areal water feature is a canal (2-dimensional) or ditch (2-dimensional).
Enumerated_Domain_Value_Definition_Source:
U.S. Geological Survey in cooperation with U.S. Environmental Protection Agency
Enumerated_Domain:
Enumerated_Domain_Value: Ice Mass
Enumerated_Domain_Value_Definition: The areal water feature is an ice mass.
Enumerated_Domain_Value_Definition_Source:
U.S. Geological Survey in cooperation with U.S. Environmental Protection Agency
Enumerated_Domain:
Enumerated_Domain_Value: Inundation Area
Enumerated_Domain_Value_Definition: The areal water feature is an inundation area.
Enumerated_Domain_Value_Definition_Source:
U.S. Geological Survey in cooperation with U.S. Environmental Protection Agency
Enumerated_Domain:
Enumerated_Domain_Value: Lake/Pond
Enumerated_Domain_Value_Definition: The areal water feature is a lake or pond.
Enumerated_Domain_Value_Definition_Source:
U.S. Geological Survey in cooperation with U.S. Environmental Protection Agency
Enumerated_Domain:
Enumerated_Domain_Value: Playa
Enumerated_Domain_Value_Definition: The areal water feature is a playa.
Enumerated_Domain_Value_Definition_Source:
U.S. Geological Survey in cooperation with U.S. Environmental Protection Agency
Enumerated_Domain:
Enumerated_Domain_Value: Reservoir
Enumerated_Domain_Value_Definition: The areal water feature is a reservoir.
Enumerated_Domain_Value_Definition_Source:
U.S. Geological Survey in cooperation with U.S. Environmental Protection Agency
Enumerated_Domain:
Enumerated_Domain_Value: Stream/River
Enumerated_Domain_Value_Definition:
The areal water feature is a stream (2-dimensional) or river (2-dimensional).
Enumerated_Domain_Value_Definition_Source:
U.S. Geological Survey in cooperation with U.S. Environmental Protection Agency
Enumerated_Domain:
Enumerated_Domain_Value: Swamp/Marsh
Enumerated_Domain_Value_Definition: The areal water feature is a swamp or marsh.
Enumerated_Domain_Value_Definition_Source:
U.S. Geological Survey in cooperation with U.S. Environmental Protection Agency
Attribute:
Attribute_Label: METERS
Attribute_Definition: The length of the river or stream in meters.
Attribute_Definition_Source: Esri
Attribute_Domain_Values:
Unrepresentable_Domain: Calculated lengths for the features.
Attribute:
Attribute_Label: FEET
Attribute_Definition: The length of the river or stream in feet.
Attribute_Definition_Source: Esri
Attribute_Domain_Values:
Unrepresentable_Domain: Calculated lengths for the features.
Attribute:
Attribute_Label: Shape
Attribute_Definition: Feature geometry.
Attribute_Definition_Source: Esri
Attribute_Domain_Values:
Unrepresentable_Domain: Coordinates defining the features.

Distribution_Information:
Distributor:
Contact_Information:
Contact_Organization_Primary:
Contact_Organization: Esri; Esri Offices
Contact_Address:
Address_Type: mailing and physical address
Address: 380 New York Street
City: Redlands
State_or_Province: California
Postal_Code: 92373-8100
Country: USA
Contact_Voice_Telephone: 800-447-9778
Contact_Instructions:
In the United States, contact the Esri Telebusiness staff at 800-447-9778 for more information about our software and data.
Outside the United States, please direct all inquiries to your local Esri Office. This information can be found at <http://www.esri.com/about-esri/locations.html>.
Resource_Description: Offline Data, Downloadable Data
Distribution_Liability: See use constraints.
Standard_Order_Process:
Digital_Form:
Digital_Transfer_Information:
Format_Name: SDC
Format_Specification:
The SDC file contains the geospatial and attribute data. The SDI file contains the spatial index. The PRJ file contains the coordinate system information (optional). The XML file (*.sdc.xml) contains the metadata describing the data set (optional).
File_Decompression_Technique: ArcGIS® software
Transfer_Size: 293.265
Digital_Transfer_Option:
Online_Option:
Computer_Contact_Information:
Network_Address:
Network_Resource_Name: <http://www.ArcGIS.com>
Offline_Option:
Offline_Media: DVD–ROM
Recording_Capacity:
Recording_Density: 4.38 or 7.95
Recording_Density_Units: GB (gigabytes)
Recording_Format: UDF (Universal Disc Format)
Fees: Software purchase price
Ordering_Instructions: Data & Maps is available only as part of Esri® software.
Technical_Prerequisites: To use this data requires software that supports SDC files.

Metadata_Reference_Information:
Metadata_Date: 20111214
Metadata_Contact:
Contact_Information:
Contact_Organization_Primary:
Contact_Organization: Esri
Contact_Person: ArcGIS Content Team
Contact_Address:
Address_Type: mailing and physical address
Address: 380 New York Street
City: Redlands
State_or_Province: California
Postal_Code: 92373-8100
Country: USA
Contact_Voice_Telephone: 909-793-2853
Contact_Facsimile_Telephone: 909-793-5953
Contact_Electronic_Mail_Address: info@esri.com
Hours_of_Service: 7:00 a.m.–5:30 p.m. Pacific time, Monday–Friday
Metadata_Standard_Name: FGDC Content Standards for Digital Geospatial Metadata
Metadata_Standard_Version: FGDC-STD-001-1998
Metadata_Time_Convention: local time
Metadata_Extensions:
Online_Linkage: <http://www.esri.com/metadata/esriprof80.html>
Profile_Name: Esri Metadata Profile

Generated by mp version 2.9.6 on Mon Jul 02 12:39:31 2012