National Hydrography Dataset (NHD) in Arc - High-resolution: Copper River Collaborative study area

Metadata also available as

Metadata:

Identification_Information
Data_Quality_Information
Spatial_Data_Organization_Information
Spatial_Reference_Information
Entity_and_Attribute_Information
Distribution_Information
Metadata_Reference_Information

Identification_Information:

Citation:

Citation_Information:

Originator:

U.S. Geological Survey in cooperation with U.S. Environmental Protection Agency, USDA Forest Service, and other Federal, State and local partners (see dataset specific metadata under Data_Set_Credit for details).

Publication_Date: See dataset specific metadata.

Publication_Time: Unknown

Title:

National Hydrography Dataset (NHD) in Arc - High-resolution: Copper River Collaborative study area

Geospatial_Data_Presentation_Form: vector digital data

Publication_Information:

Publication_Place: Reston, Virginia
Publisher: U.S. Geological Survey

Online_Linkage: \\ANALISA-2K\D_Pray\crc_new\data\hydro\strms_nhd_63k

Description:

Abstract:

Ecotrust-generated stream coverage derived from NHDinArc for Copper River Collaborative study area.

Line coverages from the reach.rch feature class were extracted from the National Hydrography Dataset (NHD) such that this coverage is simply a line coverage of high resolution NHD streams and does not retain all of the other features and functionality of the NHD. Scale is 1:63,360.

Purpose:

The NHD is a national framework for assigning reach addresses to water-related entities, such as industrial discharges, drinking water supplies, fish habitat areas, wild and scenic rivers. Reach addresses establish the locations of these entities relative to one another within the NHD surface water drainage network, much like addresses on streets. Once linked to the NHD by their reach addresses, the upstream/downstream relationships of these water-related entities--and any associated information about them--can be analyzed using software tools ranging from spreadsheets to geographic information systems (GIS). GIS can also be used to combine NHD-based network analysis with other data layers, such as soils, land use and population, to help understand and display their respective effects upon one another. Furthermore, because the NHD provides a nationally consistent framework for addressing and analysis, water-related information linked to reach addresses by one organization (national, state, local) can be shared with other organizations and easily integrated into many different types of applications to the benefit of all.

Supplemental_Information:

Ecotrust methods:

NHDinArc folders were obtained from the NHD website for each subbasin within the Copper River basin as well as the subbasin that includes Cordova. The route.rch feature class within each nhd coverarage within each folder was exported as a shapefile in ArcMap and then all of the route.rch shapefiles within the Copper River basin were merged and converted into a coverage.

From original NHD metadata abstract:

The National Hydrography Dataset (NHD) is a feature-based database that interconnects and uniquely identifies the stream segments or reaches that make up the nation's surface water drainage system. NHD data was originally developed at 1:100,000-scale and exists at that scale for the whole country. This high-resolution NHD, generally developed at 1:24,000/1:12,000 scale, adds detail to the original 1:100,000-scale NHD. (Data for Alaska, Puerto Rico and the Virgin Islands was developed at high-resolution, not 1:100,000 scale.) Local resolution NHD is being developed where partners and data exist. The NHD contains reach codes for networked features, flow direction, names, and centerline representations for areal water bodies. Reaches are also defined on waterbodies and the approximate shorelines of the Great Lakes, the Atlantic and Pacific Oceans and the Gulf of Mexico. The NHD also incorporates the National Spatial Data Infrastructure framework criteria established by the Federal Geographic Data Committee.

Time_Period_of_Content:

Time_Period_Information:

Single_Date/Time:

Calendar_Date:: REQUIRED: The year (and optionally month, or month and day) for which the data set corresponds to the ground.

Currentness_Reference: See dataset specific metadata.

Status:

Progress: In work
Maintenance_and_Update_Frequency: Irregular

Spatial_Domain:

Bounding_Coordinates:

West_Bounding_Coordinate: -148.164716
East_Bounding_Coordinate: -139.904216
North_Bounding_Coordinate: 63.372707
South_Bounding_Coordinate: 59.745721

Keywords:

Theme:

Theme_Keyword_Thesaurus:: U.S. Department of the Interior, U.S. Geological Survey, 1999, Standards for National Hydrography Dataset (<http://mapping.usgs.gov/standards/>)
Theme_Keyword: FWHYDROGRAPHY
Theme_Keyword: Hydrography
Theme_Keyword: Stream / River
Theme_Keyword: Lake / Pond
Theme_Keyword: Canal / Ditch
Theme_Keyword: Reservoir
Theme_Keyword: Spring / Seep
Theme_Keyword: Swamp / Marsh
Theme_Keyword: Artificial Path
Theme_Keyword: Reach Code

Place:

Place_Keyword: Copper River basin
Place_Keyword: Cordova

Place:

Place_Keyword_Thesaurus:: U.S. Department of Commerce, 1977, Countries, dependencies, areas of special sovereignty, and their principal administrative divisions (Federal Information Processing Standards 10-3): Washington, D.C., National Institute of Standards and Technology.
Place_Keyword: US

Access_Constraints: None

Use_Constraints:

None. Acknowledgment of the originating agencies would be appreciated in products derived from these data.

Point_of_Contact:

Contact_Information:

Contact_Organization_Primary:

Contact_Organization: Earth Science Information Center, U.S. Geological Survey

Contact_Address:

Address_Type: mailing address
Address: 507 National Center
City: Reston
State_or_Province: VA
Postal_Code: 20192
Country: USA

Contact_Voice_Telephone: 1 888 ASK USGS

Contact_Voice_Telephone: 1 888 275 8747

Contact_Electronic_Mail_Address: ask@usgs.gov

Hours_of_Service: 0800-1600 Eastern Time

Contact_Instructions:

In addition to the address above there are other ESIC offices throughout the country. A full list of these offices is at URL: <http://mapping.usgs.gov/esic/esic_index.html>

Data_Set_Credit: See dataset specific metadata.

Native_Data_Set_Environment:

Microsoft Windows 2000 Version 5.0 (Build 2195) Service Pack 4; ESRI ArcCatalog 8.3.0.800

Data_Quality_Information:

Attribute_Accuracy:

Attribute_Accuracy_Report:: Statements of attribute accuracy are based on accuracy statements made for U.S. Geological Survey Digital Line Graph (DLG) data, which is estimated to be 98.5 percent. One or more of the following methods were used to test attribute accuracy: manual comparison of the source with hardcopy plots; symbolized display of the DLG on an interactive computer graphic system; selected attributes that could not be visually verified on plots or on screen were interactively queried and verified on screen. In addition, software validated feature types and characteristics against a master set of types and characteristics, checked that combinations of types and characteristics were valid, and that types and characteristics were valid for the delineation of the feature. Feature types, characteristics, and other attributes conform to the Standards for National Hydrography Dataset (USGS, 1999) as of the date they were loaded into the database. All names were validated against a current extract from the Geographic Names Information System (GNIS). The entry and identifier for the names match those in the GNIS. The association of each name to reaches has been interactively checked, however, operator error could in some cases apply a name to a wrong reach. This statement is generally true for the most common sources of NHD data. Other sources and methods may have been used to create or update NHD data. In some cases, additional information may be found in the NHDMetadata table.

Logical_Consistency_Report:

Points, nodes, lines, and areas conform to topological rules. Lines intersect only at nodes, and all nodes anchor the ends of lines. Lines do not overshoot or undershoot other lines where they are supposed to meet. There are no duplicate lines. Lines bound areas and lines identify the areas to the left and right of the lines. Gaps and overlaps among areas do not exist. All areas close.

Completeness_Report:

The completeness of the data reflects the content of the sources, which most often are the published USGS topographic quadrangle and/or the USDA Forest Service Primary Base Series (PBS) map. The USGS topographic quadrangle is usually supplemented by Digital Orthophoto Quadrangles (DOQs). Features found on the ground may have been eliminated or generalized on the source map 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 their 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 were collected. Note, however, that these general rules were applied unevenly among maps during compilation. Reaches codes are defined on all features of type stream/river, canal/ditch, artificial path, coastline, and connector. Waterbody reach codes are defined on all lake/pond and most reservoir features. Names were applied from the GNIS database. Detailed capture conditions are provided for every feature type in the Standards for National Hydrography Dataset available online through <http://mapping.usgs.gov/standards/>. This statement is generally true for the most common sources of NHD data. Other sources and methods may have been used to create or update NHD data. In some cases, additional information may be found in the NHDMetadata table.

Positional_Accuracy:

Horizontal_Positional_Accuracy:

Horizontal_Positional_Accuracy_Report:: Statements of horizontal positional accuracy are based on accuracy statements made for U.S. Geological Survey topographic quadrangle maps. 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 the true position. Additional offsets to positions may have been introduced where feature density is high to improve the legibility of map symbols. In addition, the digitizing of maps is estimated to contain a horizontal positional error of less than or equal to 0.003 inch standard error (at map scale) in the two component directions relative to the source maps. Visual comparison between the map graphic (including digital scans of the graphic) and plots or digital displays of points, lines, and areas, is used as control to assess the positional accuracy of digital data. Digital map elements along the adjoining edges of data sets are aligned if they are within a 0.02 inch tolerance (at map scale). Features with like dimensionality (for example, features that all are delineated with lines), with or without like characteristics, that are within the tolerance are aligned by moving the features equally to a common point. Features outside the tolerance are not moved; instead, a feature of type connector is added to join the features. This statement is generally true for the most common sources of NHD data. Other sources and methods may have been used to create or update NHD data. In some cases, additional information may be found in the NHDMetadata table.

Vertical_Positional_Accuracy:

Vertical_Positional_Accuracy_Report:: Statements of vertical positional accuracy for elevation of water surfaces are based on accuracy statements made for U.S. Geological Survey topographic quadrangle maps. These maps were compiled to meet National Map Accuracy Standards. For vertical accuracy, this standard is met if at least 90 percent of well-defined points tested are within one-half contour interval of the correct value. Elevations of water surface printed on the published map meet this standard; the contour intervals of the maps vary. These elevations were transcribed into the digital data; the accuracy of this transcription was checked by visual comparison between the data and the map. This statement is generally true for the most common sources of NHD data. Other sources and methods may have been used to create or update NHD data. In some cases, additional information may be found in the NHDMetadata table.

Lineage:

Process_Step:

Process_Description:: The processes used to create and maintain high-resolution NHD data can be found in the table called "NHDMetadata". Because NHD data can be downloaded using several user-defined areas, the process descriptions can vary for each download. The NHDMetadata table contains a list of all the process descriptions that apply to a particular download. These process descriptions are linked using the DuuID to the NHDFeatureToMetadata table which contains the com_ids of all the features within the download. In addition, another table, the NHDSourceCitation, can also be linked through the DuuID to determine the sources used to create or update NHD data.
Process_Date: Unknown

Process_Step:

Process_Description:: Converted NHD data to geodatabase format. Conversion included assignment of FCodes, FDate, and Resolution attribute values; assignment of reach codes to associated features; replacement of branched reaches with linear reaches; merge of area features with identical classification that adjoin or overlap; split of large area features that exceed 100/25 sq. km. (depending on feature type) at subbasin boundaries; reduction of feature classes, feature types, and attribution to simplify data; merge of network flow features at vertical relationship locations; conversion of artificial paths along coastline to coastline feature type; addition of M coordinates and values to network flow features; addition of Z coordinates, but not values, to all feature geometry; addition of value added attributes; switch to primary flow navigation by network features (NHDFlowline, route.drain) in place of reach features; and elimination of metadata boundaries.
Process_Date: 2004

Process_Step:

Process_Description: See dataset specific metadata.

Process_Step:

Process_Description: Metadata imported.
Source_Used_Citation_Abbreviation: C:\DOCUME~1\matthew\LOCALS~1\Temp\xml20F5.tmp

Spatial_Data_Organization_Information:

Direct_Spatial_Reference_Method: Vector

Point_and_Vector_Object_Information:

SDTS_Terms_Description:

SDTS_Point_and_Vector_Object_Type: Complete chain
Point_and_Vector_Object_Count: 43773

SDTS_Terms_Description:

SDTS_Point_and_Vector_Object_Type: Point
Point_and_Vector_Object_Count: 4

Spatial_Reference_Information:

Horizontal_Coordinate_System_Definition:

Planar:

Map_Projection:

Map_Projection_Name: Albers Conical Equal Area

Albers_Conical_Equal_Area:

Standard_Parallel: 55.000000
Standard_Parallel: 65.000000
Longitude_of_Central_Meridian: -154.000000
Latitude_of_Projection_Origin: 50.000000
False_Easting: 0.000000
False_Northing: 0.000000

Planar_Coordinate_Information:

Planar_Coordinate_Encoding_Method: coordinate pair

Coordinate_Representation:

Abscissa_Resolution: 0.000213
Ordinate_Resolution: 0.000213

Planar_Distance_Units: meters

Geodetic_Model:

Horizontal_Datum_Name: North American Datum of 1927
Ellipsoid_Name: Clarke 1866
Semi-major_Axis: 6378206.400000
Denominator_of_Flattening_Ratio: 294.978698

Vertical_Coordinate_System_Definition:

Altitude_System_Definition:

Altitude_Datum_Name: National Geodetic Vertical Datum of 1929
Altitude_Resolution: 0.000100
Altitude_Distance_Units: meters
Altitude_Encoding_Method:: Explicit elevation coordinate included with horizontal coordinates

Entity_and_Attribute_Information:

Detailed_Description:

Entity_Type:

Entity_Type_Label: strms_nhd_63k.aat

Attribute:

Attribute_Label: FID

Attribute_Definition: Internal feature number.

Attribute_Definition_Source: ESRI