U.S. Geological Survey in cooperation with U.S. Environmental Protection Agency2000National Hydrography Dataset Stream Route Reaches (Transport and Coastline Reach Theme)vector digital dataHelena, MontanaMontana State Libraryhttp://nris.state.mt.us/nsdi/nhd/data/nhd_stream.zipYCo_nhd_streamThis shapefile contains the stream route reaches from the National Hydrography Dataset for all 4th-code subbasins that include any part of Montana.
This theme represents transport and coastline reach routes. A reach is a significant piece of surface water generally, but not always, between two confluences. A single transport or coastline reach route may be composed of one or more network element routes. For example, a single transport reach route may be made of two network elements, one which is an intermittent stream/river, and another which is a perennial stream/river. Transport and coastline reaches have names, when available. These routes and their associated measures form the foundation of the NHD's linear referencing system. Measures for coastline reaches run from 0-100 in the opposite direction of the coordinates, which are oriented so that the water is to the right and the land is to the left. Measures for transport reaches run from 0-100 in the opposite direction of the coordinates, which are oriented upstream to downstream when flow direction is known. The exceptions to this rule are measures for branched path transport reaches which are composed of the artificial paths in large areal features such as lake/ponds. If the main path within a branched reach can be determined from surrounding level and flow attributes, the artificial paths that comprise the main path will have measures from 0-100 and all remaining artificial paths within the branched reach will have measures between 100-200. These remaining artificial paths are assigned measures in the range 100-200 on a prorated basis considering their individual lengths relative to the total of their lengths. If the main path cannot be determined, all artificial paths comprising the branched reach are assigned measures in the range 100-200 on a prorated basis considering their individual lengths relative to the total of their lengths.
The National Hydrography Dataset (NHD) is a feature-based database that interconnects and uniquely identifies the stream segments or reaches that comprise the nations surface water drainage system. It is based initially on the content of the U.S. Geological Survey 1:100,000-scale Digital Line Graph (DLG) hydrography data, integrated with reach-related information from the U.S. Environmental Protection Agency Reach File Version 3.0 (RF3). More specifically, it contains reach codes for networked features and isolated lakes, flow direction, names, stream level, and centerline representations for areal water bodies. Reaches are also defined to represent waterbodies. The NHD also incorporates the National Spatial Data Infrastructure framework criteria set out by the Federal Geographic Data Committee.The National Hydrography Dataset combines elements of the DLG and RF3: spatial accuracy and comprehensiveness from the DLG and network relationships, names, stream level, and a unique identifier (reach code) for surface water features from RF3. The NHD supersedes DLG and RF3 by incorporating them, not by replacing them. Users of DLG and RF3 will find the National Hydrography Dataset both familiar and greatly expanded and refined. The NHD provides a national framework for assigning reach addresses to water-related entities, such as industrial dischargers, 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 in a manner similar to street addresses. 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 better 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. The National Hydrography Dataset is designed to provide comprehensive coverage of hydrologic data for the U.S. While initially based on 1:100,000-scale data, the NHD is designed to incorporate - and encourage the development of - higher-resolution data required by many users. It will facilitate the improved integration of water-related data in support of the application requirements of a growing national user community and will enable shared maintenance and enhancement.This is an abbreviated version of the metadata provided by the USGS for the National Hydrography Dataset (NHD). Each cataloging unit has unique metadata, available by downloading that unit from http://nris.state.mt.us/nsdi/nhd/. For more information about the NHD, see http://nhd.usgs.gov.
Except for the title, the first two paragraphs of the abstract, and the attribute lists in the Entity and Attribute section, the metadata files for the five themes of the NHD available from the State Library (points, drainage, stream reaches, waterbodies, and lakes) are essentially identical.
Some features previously unnamed in the area in and around Billings have been named by City of Billings GIS Division. Some features have been re-aligned to match the 2005 satellite imagery, and more recently to the West End Flood Study data, and to the Oct 17, 2009 high-resolution aerial imagery. This data is updated primarily in order to more accurately depict storm drains and ditches, and other related surface flow.en2000publication dateIrregular-113.447708-112.46641248.53036148.1059421800767.7375002541592.848000217815.517000889787.402000HydrographyStreamRiverLakePondCanalDitchReservoirSpringSeepSwampMarshArtificial PathReachMontanaNoneNone. Acknowledgment of the originating agencies would be appreciated in products derived from these data.Montana State Librarymailing address
PO Box 201800
HelenaMT59620-1800406-444-5356nris@state.mt.usESRI ArcCatalog 8.3.0.800Feature ClassThe accuracy of the attributes of the Digital Line Graph data 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 digital line graph 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 on reaches were validated against a March 1999 extract from the Geographic Names Information System. The entry and identifier for the names match those in the Geographic Names Information System. The association of each name to reaches has not been methodically checked, and so a name may be applied to the wrong reaches. Anecdotal reviews indicate that 80 percent or more of the named reaches have the correct name. Reaches were delineated with a batch procedure and were checked extensively during the visual pass steps of processing. Based on automated quality assurance/quality control checks performed at various intervals during the processing, approximately 99 percent of the reaches are delineated according to standards.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.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 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 (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. A priority for maintenance of the National Hydrography Dataset is the rectification of these differences. 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://mapping.usgs.gov/standards/.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 their true position. Additional offsets to positions may have been introduced where there are many features 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 to assess the positional accuracy of digital data. Linear features of the same type along the adjoining edges of data sets are aligned if they are within a 0.02 inch tolerance (at map scale). To align the features, the midpoint between the end of the corresponding features is computed, and the ends of features are moved to this point. Features outside the tolerance are not moved; instead, a feature of type connector was added to join the features.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.U.S. Environmental Protection Agency1997Reach File version 3100000onlinereach codes, network flow direction, stream namesU.S. Geological Survey1999Geographic Names Information Systemonlinenames for reaches and areal water bodiesU.S. Geological Survey1981DLG-3 Data File100000onlinespatial and attribute information
Converted Digital Line Graph (DLG-3) data to the features and converted the coordinate system to geographic (longitude-latitude) coordinates in the North American Datum of 1983, in five steps:
1. The U.S. Geological Surveys 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 conversion problems or uncertain conversions (for example, the DLG-3 attribute code for reservoir sometimes should convert to the feature type Reservoir and other times to feature type Lake/Pond) were flagged for later inspection. Only known conversion problems were flagged and no additional steps to detect or repair discrepancies in the original DLG-3 or the converted NHD were taken.
2. A default value of a characteristic was added in cases where the description was incomplete.
3. All instances in which problems and uncertainties 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, the North American Datum of 1983, using version 2.1 of NADCON software (National Geodetic Survey, n.d.). This process generated the features data.
1994
Flow validation performed after initial release of data:
1. Convert RF3 to 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 based on the standards used for the National Hydrography Dataset, and identify inflow/outflow points where transport reaches entered and exited waterbodies.
2. Create artificial paths. Using waterbodies from the features data and inflow/outflow points extracted from RF3 double prime, this process automatically generated the lines used to delineate artificial paths within waterbodies using the ARC/INFO GRID routine.
3. Blind pass. This batch step conflated RF3 double prime 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 to waterbodies (February 1995 extract).
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. Using the list, software presented each case to analysts to make appropriate edits to the data. Analysts recorded notes where repairs could not be made; these notes are encoded in the cataloging unit digital update units under a separate process description.
5. Build superquads. After the quadrangle-based visual pass was complete, all quadrangles that cover all or part of each cataloging unit using 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. Like 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 other errors in the data; these notes are encoded in the cataloging unit digital update units under a separate process description.
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 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 include assigning the final reach codes, building waterbody reaches, adding final artificial paths in waterbodies, and implementing any recent changes in standards for the National Hydrography Dataset. The spelling of geographic names were replaced from the March 1999, data extract from the Geographic Names Information System. Following this procedure, reaches, features, characteristics, geographic names, and relations were loaded into the database that holds the National Hydrography Dataset.
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 related to the National Hydrography Dataset. 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.
2000Using NHD-Edit, each GNIS waterbody and linear reach record was examined on screen to make sure that the GNIS ID from the GNIS matched that of the NHD reach. If not, the Name tool was used to apply the correct name. In addition, flow direction was checked and those reaches not flowing in the proper direction were flagged with the flow tool.2001Dataset copied.withheld20050603Dataset copied.withheld20070816nhd_stream.dbfFeature Class318ShapeFeature geometry.Coordinates defining the features.RCH_IDDouble8388ESRIRCH_IDUnique identifier generated by software for this copy of the dataset.COM_IDDouble8388COM_IDUnique identifier of the NHD feature or reach.RCH_CODEString1400RCH_CODEA numeric code that uniquely identifies a reach. This 14-digit code has 2 parts: the first 8 digits are the hydrologic unit code for the subbasin in which the reach is located; the last 6 digits are a sequentially ordered, arbitrarily assigned number.RCH_DATEString800RCH_DATEDate that the RCH_CODE was assigned. Display format: YYYYMMDD.ISP_LEVELDouble8388ISP_LEVELStream level. Has a value range of 1 to 99 and the value -9998 for "unspecified". (Reference "NHD Concepts and Contents" for a more complete discussion of stream level.)METERSDouble8388METERSLength of the reach, in meters.OBJECTIDOID4100ESRISequential unique whole numbers that are automatically generated.Shape_fidMAPString100OBJECTIDGNIS_IDString800Internal feature number.ESRISequential unique whole numbers that are automatically generated.MapBIKEMAPString300SHAPE_FIDNAMEString9900MAPHUCString800Feature geometry.EsriCoordinates defining the features.GNIS_IDGNIS identifier of the point landmark name. A "blank" means that the name is not populated.TYPEString3000BIKEMAPShapeGeometry400Feature geometry.EsriCoordinates defining the features.NAMEText of the reach name. A "blank" means that the name is not populated. (Reference "NHD Concepts and Contents" Appendix A for name information by NHD feature type.)last_edited_dateDate800EsriCoordinates defining the features.SHAPEMapIDInteger4100Feature geometry.ESRICoordinates defining the features.last_edited_dateCommentString5000SHAPE_fidcreated_userString25500Feature geometry.EsriCoordinates defining the features.Shape.STLength()created_dateDate800Feature geometry.EsriCoordinates defining the features.Water_Featlast_edited_userString25500Feature geometry.ESRICoordinates defining the features.HUC8-digit, 4th-code hydrologic unit code identifier of the sub-basin that contains the reach.SHAPE_FIDInteger4100EsriCoordinates defining the features.TypeShape.STLength()Double000Feature geometry.EsriCoordinates defining the features.TYPEWater_FeatString5000The National Hydrography Dataset is a comprehensive set of digital spatial data that encodes information about naturally occurring and constructed bodies of water, paths through which water flows, and related entities. The information encoded about features includes classification by type, other characteristics, a unique common identifier, the feature length or area, and (rarely) the elevation of the surface of water pools and a description of the stage of the elevation. For reaches, encoded information includes a reach code, the date the reach code was assigned, a unique common identifier, the reach length or area, and, for transport reaches, the stream level. Geographic names, and their identifiers in the Geographic Names Information System, are assigned to reaches or, if no reach is available, to features. The data also contain relations among reaches that encode the direction of water flow, metadata, and information that supports the exchange of future updates and improvements to the data.Anno_104_267RelationshipMontana State Librarymailing address
PO Box 201800
HelenaMT59620-1800406-444-5355nris@state.mt.usUsers must make their own determination of the applicability of this data to their purposes.ESRI Shapefile4.3324.332http://nris.state.mt.us/nsdi/nhd/data/nhd_stream.zipCD-ROMDownloadable Data20031219Gerry DaumillerMontana State Librarymailing address
PO Box 201800
HelenaMT59620-1800406-444-5358gdaumiller@state.mt.usenFGDC Content Standards for Digital Geospatial MetadataFGDC-STD-001-1998local time2021020506221500FALSE20230801150103002023080115010300NWPS_Streams_Ditches0022055832.4878612509374.671916389987.204068803945.2099741ProjectedGCS_North_American_1983Linear Unit: Foot (0.304800)NAD_1983_StatePlane_Montana_FIPS_2500_Feet_Intl<ProjectedCoordinateSystem xsi:type='typens:ProjectedCoordinateSystem' xmlns:xsi='http://www.w3.org/2001/XMLSchema-instance' xmlns:xs='http://www.w3.org/2001/XMLSchema' xmlns:typens='http://www.esri.com/schemas/ArcGIS/10.8'><WKT>PROJCS["NAD_1983_StatePlane_Montana_FIPS_2500_Feet_Intl",GEOGCS["GCS_North_American_1983",DATUM["D_North_American_1983",SPHEROID["GRS_1980",6378137.0,298.257222101]],PRIMEM["Greenwich",0.0],UNIT["Degree",0.0174532925199433]],PROJECTION["Lambert_Conformal_Conic"],PARAMETER["False_Easting",1968503.937007874],PARAMETER["False_Northing",0.0],PARAMETER["Central_Meridian",-109.5],PARAMETER["Standard_Parallel_1",45.0],PARAMETER["Standard_Parallel_2",49.0],PARAMETER["Latitude_Of_Origin",44.25],UNIT["Foot",0.3048],AUTHORITY["EPSG",2256]]</WKT><XOrigin>-117014400</XOrigin><YOrigin>-98447700</YOrigin><XYScale>3048</XYScale><ZOrigin>0</ZOrigin><ZScale>1</ZScale><MOrigin>-973.7418255</MOrigin><MScale>3999999.9962747097</MScale><XYTolerance>0.0032808398950131233</XYTolerance><ZTolerance>0.001</ZTolerance><MTolerance>0.001</MTolerance><HighPrecision>true</HighPrecision><WKID>2256</WKID><LatestWKID>2256</LatestWKID></ProjectedCoordinateSystem>1.0 Version 6.2 (Build 9200) ; Esri ArcGIS 10.9.1.28388NWPS_Streams_Ditches1800767.73752541592.848889787.402217815.5171-110.168747-107.21574746.6906444.82510411-109.160462-107.35347246.45460045.299581ISO 19115 Geographic Information - MetadataDIS_ESRI1.0dataset002withheld4.332Feature ClassFeature ClassVectorSimpleFALSE318TRUETRUEGCS_North_American_1983NAD_1983_StatePlane_Montana_FIPS_2500_Feet_Intlcoordinate pairinternational feet0.0005000.000500North American Datum of 1983Geodetic Reference System 806378137.000000298.257222Explicit elevation coordinate included with horizontal coordinates1.000000NAD_1983_StatePlane_Montana_FIPS_2500_Feet_IntlEPSG5.3(9.0.0)31820230801