National Hydrography Dataset
![]() |
February 2000ContentsOverview Features Feature types and characteristics Delineation rules Common identifier Special feature types: Artificial Path, Connector, and Underpass Reaches Reach types and delineation Transport reach Delineation Underlying feature rule Confluence-to-confluence rule Branched path rule Application of, and deviation from, the rules Coastline Reach Waterbody reach Shoreline reach Reach code Common identifier Reach summary Encoding flow relations among transport and coastline reaches Direction of flow using flow relations Sequencing flow relations along a reach Identifying level paths through the drainage network Stream level Tracing stream levels among reach flow relations Metadata and digital update units Digital update units Geographic names Characteristics of domestic geographic names Entry conventions for geographic names Common identifier Coordinates and related measures Horizontal coordinate referencing system Lengths and areas Elevations of water surfaces Data Quality Conterminous United States (excluding the Pacific Northwest), Hawaii, Puerto Rico, and the Virgin Islands Lineage Attribute accuracy Logical consistency Completeness Horizontal positional accuracy Vertical positional accuracy Pacific Northwest and Alaska Glossary References Appendix A. Overview of features, reaches, and related items. Appendix B. Feature code and description field structures and definitions Feature code structure Description field structure Appendix C. Encoding characteristics using field names Appendix D. Development of Reach Files and related concepts Purpose and approach Reach file development Appendix E. Transport reach delineation rules and examples Underlying feature rule Confluence-to-confluence rule Like feature types (and their surrogates) Unlike feature types: stream/river and canal/ditch No confluence: underpasses and pipelines Branched path rule Appendix F. Organization and examples of hydrologic units Appendix G. Peculiarities Quad Edge Effects DLG-3 coding inconsistencies Inland oceans Disguised aqueducts Coastal features - foreshore versus sand Stream/rivers controlled by dams that become a series of slackwater pools Reservoir versus lake/pond NHD linework doesn�t match the published USGS 1:100,000-scale map Names Subbasin (formerly known as cataloging unit) boundaries and the features that touch and cross them Squared-off coastal subbasin boundaries Empty subbasins Coastline reaches that bound stream/rivers Waterbody reaches Flow/coordinate direction/measure direction Artificial Paths that fall outside of the 2-D features they represent
OverviewThe National Hydrography Dataset (NHD) 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 these features includes classification and other characteristics, delineation, geographic name, position and related measures, a "reach code" through which other information can be related to the NHD, and the direction of water flow. In addition to this geographic information, the dataset contains metadata and information that supports the exchange of future updates and improvements to the data. The data support many applications, such as:
In 1999, coverage was made available for the conterminous United States and Hawaii. Data for Puerto Rico, the Virgin Islands, and parts of Alaska will follow. The production of data for the remainder of Alaska will be ongoing for several years. Efforts to maintain and improve the data will occur continually. The NHD is the culmination of cooperative efforts of the U.S. Environmental Protection Agency (USEPA) and the U.S. Geological Survey (USGS). Other organizations also contributed to the effort. This volume describes the concepts and information content of the NHD, including features, reaches, metadata, geographic names, coordinate systems and related measures, and data quality.
Features![]() A feature is a defined entity and its representation. In the NHD, features include naturally occurring and constructed bodies of water, paths through which water flows, and related entities. Features are classified by type, may be described by additional characteristics, and are delineated using standard methods. Feature types and characteristics Features are classified by type. These feature types, such as "stream/river", "canal/ditch", and "lake/pond", provide the basic description of the features. Each type has a name and a definition. For example, the three most frequently encountered feature types and corresponding definitions are as follows:
Characteristics, which are traits, qualities, or properties of features, are provided for many feature types. Each characteristic has a name, a definition, and a list of values and corresponding definitions. For example, the features lake/pond and stream/river have the characteristic Hydrographic Category:
Appendix A lists the names and characteristics associated with each feature type. The "Standards for National Hydrography Dataset" (USGS, 1999) contains the names and definitions of all feature types, characteristics, and values. The document is available online through http://mapping.usgs.gov/standards/.
Encoding feature types and characteristics A five-digit feature code encodes the feature type and combinations of characteristics and values that can be assigned to a type. The first three digits encode the feature type, and the last two digits encode a set of characteristics and values. For example, the feature type "dam/weir" has the code "343". There are five combinations of characteristics and values that can be assigned to features of this type. These combinations are assigned the values of "00" through "04". The resulting possible feature codes are listed below:
Feature codes are stored in a data element named "FCODE". For those who prefer to use text instead of the numeric code, words also are used to encode the feature type, characteristic, and value information in the feature code:
For example, a feature classified as a "Dam/Weir" may have the characteristic of "Construction Material" with a value of "earthen", and the characteristic of "Operational Status" with a value of "operational". This information is encoded as follows:
Appendix B lists each feature code and its corresponding description. Appendix C lists the name of the field for each characteristic and the list of values for each characteristic.
A feature type and feature code are assigned to each feature. Description fields, fields for each characteristic, and feature codes are encoded in a lookup table. Associating the lookup table with features by matching the feature codes allows words denoting characteristics and values to be substituted for the numeric feature code. The shape and extent of features are delineated using points (including nodes), lines, or areas (see figure 1). ![]() Figure 1. Features are delineated using points, lines, or areas. The delineation of each feature follows three rules:
Delineations of linear and areal features of different types may overlap. Where they overlap, they use the same lines or areas for their delineations. For example (see figure 2) the delineation of linear features of the types canal/ditch and bridge use the same lines where they overlap. Similarly, the delineations of areal features of the types lake/pond and swamp/marsh share the same areas where they overlap. ![]() Figure 2. Examples of overlapping delineations of features. Features delineated with lines have two additional rules: they may not have branches, and they must start and stop at decision or merge points along a network. These points exist where a path represented by a network can branch among two or more choices. For example, a decision point exists at the confluence of two stream/rivers; at the confluence, one can choose among two or more paths. Conversely, a decision point does not exist where features at different elevations cross; travel along the path of each feature is independent from that of the other. For example, a decision point does not exist where a canal/ditch passes over a stream/river. Lines always have a direction; that is, lines trace a path between places where they start and stop. This characteristic provides a means to encode the direction of the flow of water. For features delineated with lines, for which the direction of flow is a prominent characteristic (the feature types artificial path, canal/ditch, connector, pipeline, and stream/river), and for which the direction of flow is known, the lines are oriented in the direction of the flow of water. Note that the direction of flow is not always known (for example, where source materials are ambiguous) or uniform (for example, in tidal areas), and so the lines are not always oriented in the direction of flow. In addition, along the coastline of the United States, the lines are oriented so that the water is to the right of the direction of the line. The delineation of features stops at the borders of the United States. The common identifier is a 10-digit integer value that uniquely identifies the occurrence of each feature. Each value occurs only once throughout the Nation. Once assigned, the value is associated permanently with its feature. When a feature is deleted, the value for its identifier is retired. The common identifier is stored in a data element named "COM_ID". Special feature types: Artificial Path, Connector, and Underpass The feature types artificial path, connector, and underpass serve special functions. The artificial path and connector ensure that the hydrographic network is complete. The artificial path represents the flow of water into, through, and out of features1 delineated using areas (that is, it serves as a centerline) and also delineates the coastline. The connector fills gaps in the delineation of other features. An underpass and two relations ("above" and "below"), represent places where features cross at different elevations. An example is where a feature of the type canal/ditch passes over a feature of the type stream/river (see figure 3.) The canal/ditch is encoded as being above an underpass, and the stream/river is encoded as being below the (same) underpass. ![]() ![]() Figure 3. Encoding an underpass. Appendix A identifies the feature types that may be related to an underpass. Note that underpasses are encoded only where they can be observed from source materials. Reaches![]() A reach is a continuous, unbroken stretch or expanse of surface water. In the NHD, this idea has been expanded to define a reach as a significant segment of surface water that has similar hydrologic characteristics, such as a stretch of stream/river between two confluences, or a lake/pond. Reaches also are defined for unconnected (isolated) features, such as an isolated lake/pond. Once a reach is defined for a segment of water and assigned a reach code, the reach will rarely be changed, if at all. Many activities for improving and updating the data, such as the integration of more accurate coordinate data, the replacement of linear feature delineations with areas, or the addition of smaller features, change only the alignment of existing reaches and do not require that they be redefined. The stability of reach definition and reach code assignment makes reaches a useful foundation for geocoding observations and statistics. Changes to the surface waters (for example, the creation of a new reservoir) and corrections to erroneous delineations of reaches, of course, would change reaches and reach codes. The NHD is the latest refinement of reaches and reach codes. Information about earlier implementations is in Appendix D Three types of reaches are in use: transport, coastline, and waterbody reaches. A fourth type, shoreline reach, has not been implemented. A transport reach represents the pathway for the movement of water through a drainage network. These reaches also are used to encode the direction in which water flows along the reach when the direction is known. They provide a basis on which locations of observations can be geocoded and linked to the drainage network. Lines delineate transport reaches. Only lines that delineate features of the types canal/ditch, pipeline, stream/river, artificial path, and connector delineate transport reaches. For transport reaches for which the direction of flow is known, the lines are oriented in the direction of the flow of water. Note that the direction of flow is not always known (for example, where source materials are ambiguous) or uniform (for example, in tidal areas), and so some lines are not oriented in the direction of flow. Three general rules determine the location of the ends of transport reaches: the underlying feature rule, the confluence-to-confluence rule, and the branched path rule. The delineation of a transport reach follows that of one or more features. Where two or more features are followed, a transport reach follows delineations of :
A transport reach always follows the entire delineation of the underlying feature or features; the delineation of a feature is not split among reaches. Transport reaches abut and do not overlap. In the confluence-to-confluence rule, a transport reach is a stretch of water between:
In the application of this rule, divergences serve the same role as confluences. Reaches defined by this rule must be contiguous and may not branch (see figure 4). ![]() Figure 4. Confluence-to-confluence reach delineation. Note that some confluences are not considered to be significant enough to break the delineation of a reach. Thus, although transport reaches start and end at confluences, not every confluence causes a transport reach to start or end (see Appendix E for more information). A branched path transport reach connects reaches that enter and exit an areal feature (see figure 5). Reaches that follow this rule occur most often in large2 features of type lake/pond and swamp/marsh, and they also may occur in other areal features. Artificial paths delineated within the areal feature provide the lines needed to delineate this special transport reach. The reach may branch and at times be discontiguous. ![]() Figure 5. Branched path reach delineation. The branched path transport reach avoids the need to define flow channels, confluences and divergences, and confluence-based transport reaches in areal features. It is used where the information needed to delineate these items reliably is not available, and at other places. Application of, and deviation from, the rules The underlying feature, confluence-to-confluence, and branched path rules govern the delineation of most transport reaches. These rules, however, have exceptions. Unusual configurations of features require modification of the rules, as do the variable condition and ambiguities of information sources. In places where unusual configurations of features or ambiguities in sources occur more often, a larger percentage of reaches delineated using modified rules will be found. Appendix E lists more examples of reach delineation rules and exceptions to the rules. A coastline reach represents a section of coastline along the Atlantic, Pacific, or Arctic Oceans, the Great Lakes, the Gulf of Mexico, or the Caribbean Sea. These reaches provide a basis for geocoding locations of observations along the coastline. Artificial paths that follow the coastline provide the lines used for coastline reach delineation. The delineation of a coastline reach may follow one or more artificial paths. A coastline reach always follows the entire delineation of the underlying artificial path or paths; the delineation of an artificial path is not split among reaches. Coastline reaches abut and do not overlap. The lines are usually oriented so that the water is to the right of the line. This results in a general orientation of coastline reaches northward along the Atlantic Ocean, southward along the Pacific Ocean, eastward along the Gulf of Mexico, westward along the Arctic Ocean and the U.S. side of the Great Lakes, and counterclockwise around islands. A coastline reach is delineated for coastal islands that have a drainage network or more than 5 miles (approximately 8.06 kilometers) of isolated drainage. Other coastal islands may or may not be delineated with a coastline reach. The ends of coastline reaches occur where transport reaches discharge into the oceans, Gulf of Mexico, Caribbean Sea, or Great Lakes (although not every point of discharge is the end of a coastline reach). At the mouth of an areal stream/river, coastline reaches end where the artificial path used to delineate the transport reach intersects the coastline. A waterbody is a hydrographic feature delineated using areas. Reaches assigned to waterbodies are termed waterbody reaches. These reaches provide a means to geocode observations for areas of water. (In contrast, transport reaches represent the path of a flow of water and provide a means of geocoding observations along the path.) Areal delineations of features provide the areas used to delineate waterbody reaches3. The shoreline reach has not been implemented and is discussed for information purposes only. A shoreline reach would represent all or part of the shoreline of an inland waterbody. Analogous to coastline reaches, they would provide a basis for geocoding locations of observations along the shoreline. Lines would delineate shoreline reaches. These reaches would abut and not overlap. The types of features that would provide these lines are being investigated, as are questions of the direction, relative to the water, in which these reaches should be ordered, means of handling islands, and rules for deciding where these reaches would start and stop. A reach code is a numeric code that uniquely labels each reach. This 14-digit code has 2 parts: the first 8 digits are the hydrologic unit4 code for the subbasin in which the reach exists; the last 6 digits are assigned in sequential order, and arbitrarily among the reaches. Each reach code occurs only once throughout the Nation. Once assigned, a reach code is associated with its reach permanently. If a reach is deleted, its reach code is retired. A reach code should not be altered. Reach codes can serve to geocode an observation to a reach or a position along a reach. Observations can be geocoded to an entire reach by associating the reach code with the observation data, or to sections of a transport, coastline, or (the planned) shoreline reach by using the reach and reach code as the basis of a linear referencing system. Reach codes are stored in data elements named "RCH_CODE". In addition to the reach code, the date on which the code was assigned in the NHD is encoded. The date is stored in data elements named "RCH_DATE". In addition to identifying each feature, the common identifier uniquely identifies each reach. Each 10-digit integer value occurs only once throughout the Nation. Once assigned, the value is associated permanently with its reach. When a reach is deleted, the value for its identifier is retired. The common identifier is stored in a data element named "COM_ID". Table 1 summarizes the types, related items, delineation, and underlying features of reaches. Table 1. Summary of reach organization by type.
Encoding flow relations among transport and coastline reaches![]() Flow relations among transport and coastline reaches encode drainage network connectivity among reaches independently from their delineations. Relations among transport reaches define a connected hydrographic network and encode the direction of water flow among reaches. This connectivity enables hydrologic sequencing of reaches (what is upstream and downstream of a given point in the hydrographic network) and navigating the network in an upstream or downstream direction. Similarly, relations among coastline reaches allow the traversal of the coastline using reaches. Relations among transport and coastline reaches connect hydrographic networks to the coastline and enable the ordering of the mouths of these networks along the coastline. Flow relations are especially useful in applications that require information about connectivity among, but not about, the underlying delineations and coordinate positions of reaches. Flow relations are encoded by identifying a pair of reaches that touch and describing the flow of water between the reaches. Note that the direction of flow is not always known (for example, where source materials are ambiguous); in these cases, flow relations are not created.
Direction of flow using flow relations The common identifiers for a pair of reaches and a description of the direction of water flow between the reaches are used to encode flow relations. Five values describe the direction of water flow between transport reaches; a sixth value describes connections between pairs of touching coastline reaches or between touching transport and coastline reaches:
![]() Figure 6. Flow relations illustrating in, out, network start, and network end directions. (A common identifier value of "0" represents a null entry.) ![]() Figure 7. Flow relations illustrating out and in directions. ![]() Figure 8. Flow relations for a branched path reach. ![]() Figure 9. Flow relations illustrating non-flowing connections. (A common identifier value of "0" represents a null entry.) Flow relations are stored as four data elements. The common identifier for the first reach is stored in a data element named "COM_ID_1". The common identifier for the second reach is stored in a data element named "COM_ID_2". The direction description is stored in two data elements: as a character string in a data element named "DIR_TEXT" and as a numeric alias5 in a data element named "DIRECTION". Sequencing flow relations along a reach Sequence numbers order flow relations of transport reaches that flow into or out of the interior of another transport reach. The reach that flows in or out is always the first reach in the flow relation; the reach along whose interior the inflowing and outflowing reach is being sequenced is the second reach in the flow relation. The flow relations are numbered sequentially, starting with 1, from upstream to downstream along the interior of the second reach. Sequence numbers also order flow relations of transport reaches that have a non-flowing connection to the interior of a coastline reach. The non-flowing connection flow relations of intersecting transport reaches are numbered sequentially, starting with 1, from start to end along the interior of the coastline reach. A sequence number of 0 means that the first reach touches the second reach at its end and not along its interior. The sequence number is stored with the flow relations in a data element named "SEQUENCE". Figure 10 illustrates the sequencing of flow relations. ![]() Figure 10. Sequencing flow relations along transport and coastline reaches. (A common identifier value of "0" represents a null entry.) Identifying level paths through the drainage network![]() Transport reaches and flow relations provide the components of the drainage network. The level path builds on these elements to create a sequence of transport reaches that trace the main stem for a given flow of water. The level path traces the flow between a head and the next largest flow of water or between a head and the ocean. Geographic names often follow these paths. Level paths are encoded by associating stream levels to transport reaches and by associating a delta level with flow relations. The stream level is a numeric code that identifies each main path of water flow through a drainage network. Stream level is assigned by identifying the terminus of a drainage network (see Figure 11). The lowest value6 for stream level is assigned to a transport reach at the end of a flow and to upstream transport reaches that trace the main path of flow back to the head. The stream level value is incremented by one and is assigned to all transport reaches that terminate at this path (that is, all tributaries to the path) and to all transport reaches 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 transport reaches that trace the main path of the tributaries to to their heads. This process is continued until all transport reaches for which flow is encoded are assigned a stream level. ![]() Figure 11. Stream level assignment for a simple drainage network. For example (see Figure 12), the Mississippi River terminates at the Gulf of Mexico. The transport reaches that trace the main flow of the river, from the head to the mouth on the Gulf, are assigned a stream level of 1. The transport reaches that trace the main flow of each tributary to the Mississippi River (such as the Ohio/Monongahela Rivers) from their heads to their termini on the Mississippi River, are assigned a stream level of 2. The transport reaches that trace the main flow of each tributary to the level 2 tributaries (such as the Tennessee River, which is a tributary to the Ohio/Monongahela Rivers), from each head to each mouth on their level 2 tributary, are assigned a stream level of 3. ![]() Figure 12. Stream level assignments along the Mississippi River. Ideally, each main path would trace the flow of the largest volume of water. Stream levels encoded in two predecessors7 to the NHD were based on flow volume data, and these paths were retained wherever possible. Data about flow volumes were not available for other reaches. Instead, the path with the same geographic name was used to determine the level path. Where a geographic name was not available or known, the longest and straightest path was used to determine a main path. Where this rule did not adequately discriminate among the choices, the rightmost (looking upstream) transport reach was assumed to be the continuation of a main path. Stream level is stored in a data element named "LEVEL". The special value "-9998" means that a value can be applied to the transport reach but has not been specified. This value usually occurs where flow relations cannot be determined or have not been encoded. Without this information, main paths cannot be identified and stream level cannot be assigned. This value is also assigned to coastline reaches. Tracing stream levels among reach flow relations To help identify main paths in the flow relations table, the difference, or delta level, between the stream levels of inflowing and outflowing reaches is encoded. To calculate this value, the stream level of the second reach in the relation is subtracted from the stream level of the first reach in the relation (see Figure 13). Delta levels of "0" mean that a relation links two reaches that are on the same main path. In most other cases, the delta level will have a value of "1". Areas of complex divergence and braided stream configurations can yield other values. A special value of "-9999" means that a value for delta level is not applicable to the relation, and this occurs when the direction is bidirectional, network start, network end, or non-flowing connection. A special value of "-9998" means that a value could not be specified because the stream level was not specified for one or both reaches that are associated by the flow relation. The values are stored with the flow relations in a data element named "DELTA_LVL". ![]() Figure 13. Difference in stream levels encoded with flow relations. Metadata and digital update units![]() Metadata, or data about data, are data that describe the content, quality, condition, and other characteristics of data. Metadata answer questions such as "How current are these data?"; "How accurate are they?"; "Are there any restrictions on their use?"; "What is their coordinate system?"; and many others. Metadata help organizations manage data, advertise and share data, and make informed use of data. Metadata for the NHD use data elements from the "Content Standards for Digital Geospatial Metadata" (Federal Geographic Data Committee, 1994). The standard allows the identity, quality, spatial data organization and reference, entity and attribute definitions, distribution sources and forms, and metadata of the data to be documented. The metadata are provided as text files. For the NHD, a general set of metadata accompanies each set of data. This NHD (for National Hydrography Dataset) metadata provides general information that applies to all data. Within the NHD, values differ for metadata elements such as currentness and quality. For example, features originate from more than 1,800 datasets of different vintages, and reaches from more than 2,100 datasets. In the future, many organizations will collaborate to maintain and improve the data. These new data will differ in currentness, source, accuracy, and other characteristics. A single document that provides metadata for these dynamic and varied data would be either very general or very unwieldy. Digital update units associate specific metadata information with selected features and reaches. A digital update unit is a collection of one or more features and (or) reaches to which a set of metadata values applies. These values include only those needed to describe unique aspects of the associated features or reaches. A feature or reach may be a member of one or more digital update units. Metadata associated with digital update units supplement information provided in the NHD metadata. These digital update unit metadata amplify, and in some cases replace, the more general information provided in the NHD metadata. In the initial release of the NHD, there are two types of digital update units; subbasin and quadrangle digital update units (see Figure 14):
![]() Figure 14. Digital update units associate metadata with a set of features and (or) reaches. Metadata associated with each digital update unit amplify or replace information provided as NHD metadata. As development and improvement of the data continue, additional digital update units will be created. These may have collections of features, reaches, and shapes different from the digital update units in the initial release. These new digital update units also may have metadata elements different from those included in the digital update units in the initial release. Digital update units are assigned unique identifiers and stored in data elements named "DUU_ID". Geographic names![]() A geographic name is "the proper name, specific term, or expression by which a particular geographical entity is, or was, known" (Orth and Payne, 1997, p. 43). Geographic names designated as being official for Federal use are encoded for many reaches and features. These names were taken from the National Geographic Names Database of the Geographic Names Information System8 (USGS, 1995), the Federal Government's primary source for identifying official names. Reaches and features can carry geographic names (see Figure 15 and Table 2). Reaches carry geographic names most often. If there is no reach to carry a name, then the feature carries the name. Appendix A lists the types of features that may carry names. Geographic names are stored in data elements named "NAME". In addition, the eight-digit identifier for a name in the Geographic Names Information System is stored in data elements named "GNIS_ID".
![]() Figure 15. Geographic names applied to transport and waterbody reaches. Note that geographic names have not been applied to all reaches and features. Names are applied to transport and coastline reaches that were named in the USEPA's Reach File version 3 (see Appendix D). Names are also applied to waterbody reaches and features delineated using points or areas in cases where batch processes can reliably associate the name with the reach or feature. Table 2. Reaches and features that can carry geographic names (Notes for table: (1) Type: The table lists all reach and feature types defined for the NHD. Note that not all types have been collected in the initial release. (2) Geographic name: An "X" in the column indicates that a geographic name may be associated with reaches or features of this type. Note that geographic names have not been encoded for many reaches and features. (3) An asterisk (*) means that the feature or names are not in the initial release of the NHD. (4) Coastline reaches carry the name of the water feature that they bound. (5) For the State of Washington, waterbody reaches carry the names of the features types ice mass, lake/pond, reservoir, and swamp/marsh. Elsewhere, waterbody reaches carry the names of the features type lake/pond only.)
Characteristics of domestic geographic names (Adapted from "Principles, policies, and procedures: domestic geographic names" (Orth and Payne, 1997, p. 3); "The national gazetteer of the United States of America: concise: (USGS, 1990, p. xi); and "Geographic Names Information System" (USGS, 1995, p. 7-8).) Geographic names normally originate in and are influenced by spoken language. It is important to remember this fact because many people are concerned with written forms of names, including matters of spelling, capitalization, word form, and writing marks, that may have little to do with the way names are spoken. Geographic names in the United States most often reflect English, French, and Spanish naming traditions. Most geographic names are binomial in that they have two parts, denoting specific and generic information. The generic part tells the kind of place, feature, or area to which the name refers and usually is a single topographic term, such as brook, creek, lake, spring, or river. The specific part uniquely identifies the particular place, feature, or area, and it may consist of one or more words. For example:
The binomial (two-part) form of specific and generic information is strong and in written usage often leads to combining words in the specific part of the name, such as Threemile Run and Redhill Gulch. The names of some features can be long, especially if the specific part is a prepositional phrase: Cliffs of the Seven Double Pillars, Foot of the Mountain Run, and Cañon del Rajadero de los Negros. Some geographic names have a "false" generic that does not describe the feature correctly. For features of the type stream/river, common false generics are terms for depressions in the Earth's surface (such as "draw", "gully" or "gulch") that usually are not defined as applying to water flowing through the depression. Some names have rare generic forms. Examples include colorful American names such as Bowl of Tears (lake), Butlers Toothpick (pinnacle rock), Titans Piazza (hill), and Devils Racepath (ridge). Among variations of the binomial form are one-word names that require a capitalized article: The Canal, The Lagoon, The Lakes, and La Laguna. Entry conventions for geographic names The entries for geographic names include uppercase and lowercase alphabetic, numeric, and punctuation and other special characters. Most names are entered in the way they are commonly written; for example "Adams Creek" and "Green Lake". Exceptions include the following:
Common identifier![]() The common identifier is a 10-digit integer value that uniquely identifies each feature or reach. Each value occurs only once throughout the Nation. Each feature and reach is assigned an identifier, stored in the data element named "COM_ID". Once assigned, the identifier is associated permanently with its feature or reach and should not be altered. When a feature or reach is deleted, its identifier is retired. Common identifiers serve several purposes. They are the basis for relating features and reaches for several purposes, including the following:
Common identifiers are also the basis for tracking and sharing deletions, additions, and modifications of features, reaches, and relations. Coordinates and related measures![]() Positions are encoded using a common coordinate referencing system. Other measurements, including lengths, areas, and selected surface elevations, also are encoded. Horizontal coordinate referencing system The locations of points, lines, and the boundaries of areas are encoded using geographic (longitude-latitude) coordinates. The coordinates are encoded in decimal degrees, with west longitude and south latitude represented by negative values. The horizontal datum is the North American Datum of 1983 (NAD83). Lengths of linear features and areas of areal features are supplied for convenience in applications that require these measures. The coordinate data were projected from longitude-latitude coordinates to the Albers Equal Area projection, and lengths and areas were calculated and saved. The parameters for the projected coordinate systems are shown below:
The North American Datum of 1983 was specified for the projected coordinate system. The distance units of the projected system were meters. Lengths are computed in meters and stored in data elements named "METERS". Areas are computed in square kilometers and stored in data elements named "SQ_KM". The elevation of water surfaces where water pools is encoded for a few features. Water surface elevations may be encoded for features of the type area to be submerged, canal/ditch, inundation area, lake/pond, reservoir, and stream/river. Note that these elevations have not been entered for most features. The vertical datum for the conterminous United States and Alaska is the National Geodetic Vertical Datum of 1929. For Puerto Rico and the Virgin Islands, the datum is Local Mean Sea Level. Elevations are recorded in meters and stored in data elements named "ELEV". Two encoded values have special meanings. A value of -9999 means that an elevation value will not be applied to the feature. A value of -9998 means that a value can be applied to the feature but has not been specified. In addition to the elevation, the prevailing condition (for example, "average water elevation") to which the elevation applies is provided. The condition is stored as a text string in data elements named "STAGE". Where the "ELEV" field has a value of -9999 or -9998, the "STAGE" field is blank. Data Quality![]() The NHD resulted from a multiyear effort to process and integrate datasets containing delineations and classification of features, reaches, hydrologic units, and geographic names. This section provides an overview of the production processes, sources of information used in these processes, and other statements related to data quality. This section describes what is "generally true" about the initial release of the data for the conterminous United States, Hawaii, Puerto Rico, and the Virgin Islands. The NHD, even in its initial release, has variations in currentness, processes, and other characteristics. It is important to note that, even before the initial release of the data, collaborative efforts are under way to correct and improve the data. Completion of these efforts will contradict even these "generally true" statements for places where the improvements are made. It is important to review the metadata to understand the condition of data. The discussion below applies to the conterminous United States (excluding the Pacific Northwest10), Hawaii, Puerto Rico, and the Virgin Islands. Figure 16 illustrates the information sources and processes used to develop the data. ![]() Figure 16. Information sources and processes used to create the NHD. Sources of information used to construct the initial release of the NHD include:
Efforts are under way to improve the NHD; most of these involve the collecting data for the conterminous United States from 1:24,000-scale maps, and digital images with positional accuracies commensurate with 1:12,000 and larger scales. Currentness varies by individual maps; see digital update units for more information.
This process converted DLG data to features and associated characteristics and converted the coordinate system to geographic (longitude-latitude) coordinates in the NAD83 in five steps:
This process generated the "features" data. The basic steps for building reaches are as follows:
The accuracy of the attributes of the DLG data is estimated to be 98.5 percent. One or more of the following methods was used to test attribute accuracy:
In addition, software was used to validate feature types and characteristics against a master set of types and characteristics, to check that combinations of types and characteristics were valid, and to check 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. The entry and identifier for geographic names match those in the Geographic Names Information System as of March 1999. 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. According to automated quality assurance/quality control checks performed at various intervals during the processing, it is estimated that 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 within a dataset. 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 NHD, are most often USGS 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 1mile (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. Rectification of these differences is a priority for maintenance of the NHD. Transport reaches are defined on almost all of the features of types stream/river, canal/ditch, pipeline, artificial path, 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 to 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/. Horizontal positional accuracy Statements of horizontal positional accuracy are based on accuracy statements made for USGS 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 positions12. 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 datasets 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 the 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 USGS 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. Similar approaches are being used to develop data for the Pacific Northwest and Alaska. Specific statements will be provided when these data are released. Glossary(The main sources for the definitions include Darcy and Boston (1988); Federal Geographic Data Committee (1994, 1997); Merriam-Webster (1998); Padmanabhan, Yoon, and Leipnik (1992); and Stamp and Clark (1979).) ARC/INFO ® 13 - Geographic information systems software developed by the Environmental Systems Research Institute of Redlands, California. area - A generic term for a bounded, continuous, two-dimensional object that may or may not include its boundary. See line, node, and point. cataloging unit - Currently known as subbasin. characteristic - A distinguishing trait, quality, or property. coastline - A line that follows the main outline of the land, including bays, but crosses rivers at their mouths. In the NHD, the outlines of selected coastal islands are included as part of the coastline. See shoreline. coastline reach - A reach that represents a section of coastline. common identifier - A 10-digit integer value that uniquely identifies each feature or reach in the NHD. conflation - A process by which two sets of map data for the same region may be aligned and merged on the basis of matches of corresponding features portrayed in both sets. confluence - Flowing together; the junction and union of two or more streams or moving fluids. In the NHD, this idea has been generalized to allow the feature types of artificial path, canal/ditch, connector, pipeline, and stream/river to meet at a confluence. See divergence. conterminous - Having a common boundary; enclosed within a common boundary. conterminous United States - the lower 48 States and the District of Columbia. contiguous - Touching along a boundary or at a point; touching or connected throughout in an unbroken sequence. contour - An imaginary line on the ground, all points of which are at the same elevation. contour interval - The difference in elevation between two adjacent contours. coordinate reference system - A set of points, lines, and (or) surfaces and a set of rules that creates a reference frame whereby each point in a given surface can be identified uniquely by a set of numbers. coordinates - Linear and (or) angular quantities that describe the location of a point in relation to a given coordinate reference system. coverage - A digital version of a map forming the basic unit of vector data storage in ARC/INFO ® . datum - Any quantity, or set of quantities, that may serve as a reference or basis for the calculation of other quantities. In relation to mapping and geographic information systems, datum usually refers to a set of quantities that serve as a reference for the calculation of positions. See horizontal datum, linear referencing system, and vertical datum. decimal degree - Representation of the measure of an angle using whole and decimal fractions of a degree. decimal degree = degrees + (minutes/60) + (seconds/3600). See latitude, longitude. degree - An angular unit of measure equal to 1/360th of the circumference of a circle. See decimal degree, latitude, and longitude. delineate - To mark the outline of; to describe, portray, or set forth with accuracy or in detail. delineation - The act of delineating; something made by delineating. diacritical mark - A mark near or through a character or combination of characters that indicates a phonetic value (a spoken sound) different from that given the unmarked or otherwise marked character. digital update unit - A collection of one or more features and (or) reaches to which a set of metadata elements apply. divergence - Flowing apart; the junction and separation of a stream or moving fluids into two or more paths. In the NHD, this idea has been generalized to allow the feature types of artificial path, canal/ditch, connector, pipeline, and stream/river to meet at a divergence. See confluence. elevation - The vertical distance above or below a vertical datum to a point or object on the Earth's surface. entity - Generally, something that has separate and distinct existence and objective or conceptual reality. In a database, an object of interest about which data can be collected. feature - A defined entity and its representation. In the NHD, features include naturally occurring and constructed bodies of water, paths through which water flows, and related entities. These spatial phenomena are classified into defined feature types, are described by additional characteristics, and are delineated in standard ways. feature code - A numeric value that encodes the type and values for a set of characteristics of a feature. This five-digit code has two parts: the first three digits encode the feature type; the last two digits encode values for a set of characteristics associated with the feature. feature type - A member of a classification scheme for features. For example, in the NHD, features can be classified by types such as canal/ditch, lake/pond, and stream/river. field - A single piece of information, the smallest unit normally manipulated by a database management system. geocode - A location identifier. More specifically, a geocode is a data value assigned to a spatial object that encodes the location of the object (or a place along the object). A geocode can be used to associate other data with the object (or a place along the object). The term geocode also denotes the process of assigning a location identifier to an object. In the NHD, reach codes provide a starting point for geocoding observations to or along hydrographic features. geographic name - The proper name, specific term, or expression by which a particular geographical entity is, or was, known. head - The source of a stream. horizontal datum - A set of constants to which horizontal coordinates are referred; a reference for position. hydrography - (1) The science comprising the description, study, and mapping of the waters of the Earth's surface (the seas, lakes, rivers, and so on), including their forms and physical features. (2) The subject matter of this science, the hydrographic features of the globe or part of it; the distribution of water on the Earth's surface. hydrologic unit - A member of the hierarchical system for identifying and subdividing river-basin units of the United States. Hydrologic units are used for the collection and organization of hydrologic data. The levels of the hierarchy, listed in order of largest to smallest in area, are region, subregion, accounting unit, and subbasin. For example: region - New England region: the drainage within the United States that ultimately discharges into: (a) the Bay of Fundy, (b) the Atlantic Ocean within and between the States of Maine and Connecticut, (c) Long Island Sound north of the New York-Connecticut state line, and (d) the Riviere St. Francois, a tributary of the St. Lawrence River. subbasin - The fourth level of subdivision of hydrologic units. A subbasin represents the geographic area of part or all of a surface drainage basin, a combination of drainage basins, or a distinct hydrologic feature. Subbasins are uniquely identified with an eight-digit hydrologic unit code. -subregion - Connecticut: the Connecticut River basin. accounting unit - Lower Connecticut: the Connecticut River basin below Vernon Dam. subbasin - Chicopee. Each hydrologic unit is identified uniquely with a hydrologic unit code. hydrologic unit code - A hierarchical, numeric code that uniquely identifies hydrologic units. The first two digits identify the region, the first four digits identify subregions, the first six digits identify accounting units, and the full eight digits identify subbasins. For example, from the example provided with the definition of hydrologic unit, the hydrologic unit codes are: 01 - the region (New England) 0108 - the subregion (Connecticut) 010802 - the accounting unit (Lower Connecticut) 01080204 - the subbasin (Chicopee) Zeroes in the two-digit accounting unit field indicate that the accounting unit and the subregion are the same. Zeroes in the two-digit subbasin field indicate that the subbasin and the accounting unit are the same. latitude - Distance north or south of the Equator, measured as an angle with the center of the Earth. In the NHD, latitude values are encoded in decimal degrees. See longitude. level path - A sequence of transport reaches that trace the main stem for a given flow of water. line - A generic term for a one-dimensional object having a length and direction. See area, node, and point. linear referencing system - A set of datums, networks, and linear referencing methods, whereby each point along a network can be identified uniquely by specifying the direction and distance from any known point on the network. longitude - Distance east or west on the Earth's surface, measured by the angle that the meridian of a particular place makes with the Prime (Greenwich) Meridian. In the NHD, longitude values are encoded in decimal degrees. See latitude. lookup table - A table that provides the ability to use a known value to locate an unknown value. In the NHD, the feature code links features to the textual descriptions of their associated characteristics. map scale - The relationship between a distance on a map, chart, or photograph and the corresponding distance on the Earth. For map scales commonly associated with the NHD, see the following table:
metadata - Data about data; data that describe the content, quality, condition, and other characteristics of data. mouth - The place where a stream enters a larger body of water. node - A zero-dimensional object that is the topological junction of two or more lines, or an end point of a line. See area, line, and point. point - A zero-dimensional object that specifies geometric location. See area, line, and node. quadrangle - A four-sided area, bounded by parallels of latitude and meridians of longitude, used as an areal unit in mapping. reach - A continuous unbroken stretch or expanse of surface water. In the NHD, this idea has been expanded to define reach as a significant segment of surface water that has similar hydrologic characteristics. Reaches have standard types and delineations. See coastline reach, shoreline reach, transport reach, and waterbody reach. reach code - A 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. relation - In a database, a named association among sets of entities. shoreline - The line where water and land meet. In the NHD, shoreline applies to inland waters only. See coastline. shoreline reach - A reach that represents all or part of a shoreline. This type of reach has not been implemented. stage - The elevation of the surface of a body of water measured relative to a vertical datum. subbasin - The fourth level of subdivision of hydrologic units. A subbasin represents the geographic area of part or all of a surface drainage basin, a combination of drainage basins, or a distinct hydrologic feature. Subbasins are uniquely identified with an eight-digit hydrologic unit code. terminus (plural termini) - A finishing point; a part that forms the end. topology - A branch of geometrical mathematics concerned with order, contiguity, and relative position rather than actual linear dimensions. Topology is used to establish and describe spatial relationships among features. transport reach - A reach that represents the pathway for the flow of water through a drainage network. traverse - To move or pass along. traversal - An instance of traversing. tributary - A stream or river that flows into a larger one. In the NHD, this idea has been generalized to allow transport reaches with underlying feature types of artificial path, canal/ditch, connector, pipeline, and stream/river to have or be tributaries. vertical datum - A set of constants specifying a coordinate system to which elevations are referred. waterbody - A hydrographic feature that is delineated using areas. waterbody reach - A reach that represents a waterbody. (In contrast, a transport reach represents the flows of water through such areas.) workspace - A directory containing geographic datasets for use with ARC/INFO ® . ReferencesAllord, G.J., 1992, 1 to 2,000,000 hydrologic unit map of the conterminous United States (digital dataset): Reston, VA, U.S. Geological Survey, http://water.usgs.gov/GIS/huc.html. Darcy, L., and Boston, L., comps., 1988, Webster's new world dictionary of computer terms (3d ed.): New York, Simon & Schuster, Inc. Federal Geographic Data Committee, 1994, Content standards for digital geospatial metadata: Washington, Federal Geographic Data Committee, 66 p. [http://www.fgdc.gov/metadata/metadata.html] Federal Geographic Data Committee, 1997, Framework introduction and guide: Washington, Federal Geographic Data Committee, 105 p. [http://www.fgdc.gov/framework/frameworkintroguide/] Merriam-Webster, 1998, WWWebster: Merriam-Webster's collegiate dictionary (10th ed.) [Online]: Springfield, MA, Merriam-Webster, Inc., http://www.m-w.com/netdict.htm. National Geodetic Survey, [n.d.], NADCON version 2.1 [Software]: Silver Spring, MD, National Geodetic Survey. [Information about the current version of the software is available through http://www.ngs.noaa.gov/PC_PROD/pc_prod.shtml.] Orth, D., and Payne, R., 1997, Principles, policies, and procedures: domestic geographic names: Reston, VA, U.S. Geological Survey, 51 p. [http://geonames.usgs.gov/bgn.html] Padmanabhan, G., Yoon, J., and Leipnik, M., comps., 1992, A glossary of GIS terminology: National Center for Geographic Information and Analysis Technical Report 92-13, 79 p. Seaber, P., Kapinos, F.P., and Knapp, G., 1987, Hydrologic unit maps: U.S. Geological Survey Water-Supply Paper 2294, 63 p., 1 pl. (Reprinted 1994.) Stamp, L.D., and Clark, A., eds., 1979 [1981], A glossary of geographical terms (3d ed.): New York, Longman, 571 p. U.S. Environmental Protection Agency, 1994, The U.S. EPA reach file version 3.0 Alpha release (RF3-Alpha) technical reference [Online], http://www.epa.gov/waters/doc/techref.html U.S. Geological Survey, 1990, The national gazetteer of the United States of America: concise: U.S. Geological Survey Professional Paper 1200-US, 526 p. U.S. Geological Survey, 1995, Geographic names information system: U.S. Geological Survey data users guide 6, 29 p. [http://geonames.usgs.gov/gnis_users_guide_toc.html] U.S. Geological Survey, 1998, Hydrologic unit maps [Online], http://water.usgs.gov/lookup/get?huc. U.S. Geological Survey, 1999, Standards for National Hydrography Dataset: Reston, VA, U.S. Geological Survey, http://mapping.usgs.gov/standards/ U.S. Geological Survey, 1999, National Atlas, Hydrologic unit boundaries [Online], http://www.nationalatlas.gov/atlasftp.html .
Appendix AOverview of features, reaches, and related items.Table 1A. Feature types and related items Notes on table: (1) Feature type: The table lists all feature types and characteristics defined for the NHD. Note that not all feature types have been collected. (2) Geo(graphic) name: An X in the column indicates that a geographic name may be associated with features of this type. Note that geographic names have not been encoded for many features. (3) For the State of Washington, waterbody reaches carry the geographic names of lake/pond, reservoir, ice mass, and swamp/marsh. (4) Surface elevation: An X in the column indicates that the elevation of the surface of the water may be associated with the features of this feature type. Note that the surface elevations have not been encoded for most features. (5) An asterisk (*) means that the item is not in the initial release of the NHD.
Table 2A. Reaches and related items Notes on table: (1) Geo(graphic) name: An X in the column indicates that a geographic name may be associated with the reaches of this type. Note that geographic names have not been encoded for many reaches, especially those that follow the feature types canal/ditch or pipeline. Coastline reaches carry the name of the water feature that they bound. (2) Stream level: For coastline reaches, stream level is assigned the value of "-9998", which means that no value has been specified.
The general format of the feature code is as follows: FFFCC, in which FFF is the three-digit code for a feature type. CC is the two-digit code for a combination of values for characteristics associated with a feature type. If only the feature type is identified, these last two digits are assigned the value "0". For example, the feature type "Dam/Weir" has the three-digit identifier "343". This number serves as the first three digits of the feature code. A code of "34300" is used if no characteristics are encoded for the feature. A feature classified as "Dam/Weir" also may have the characteristic of "Construction Material" with the values of "earthen" and "nonearthen", and the characteristic of "Operational Status" with the values of "operational" and "under construction". The codes used to encode the combinations of values are shown below:
Table 1B and Table 2B list all feature codes and their meanings. The description field uses a single character string to encode one or more characteristics and values for each feature code. The general format of the character string is shown below: characteristic|value, in which "characteristic" is the name of the characteristic. The vertical line character ("|") separates the characteristic and value. "value" is the value of the characteristic for the feature code. When two or more characteristics are encoded by a feature code, these characteristic-value pairs are separated by the semicolon and space characters ("; "). If no characteristics are encoded (that is, if the code ends in "00"), the text "Feature type only: no attributes" is encoded. For example, from the "Dam/Weir" characteristics and values described above, the following character strings are encoded for the feature codes:
Table 1B and Table 2B list all character strings. The document "Standards for National Hydrography Dataset" (USGS, 1999) contains the names and definitions of all feature types, characteristics, and values. The document is available online through http://mapping.usgs.gov/standards/.
Table 1B. Feature code definitions listed numerically by feature code (FCODE) (Note that many of the listed codes were not required in the initial release of the NHD. Appendix A lists feature types and characteristics that were not encoded.)
Table 2B. Feature code definitions listed alphabetically by feature type (Note that many of the listed codes were not required in the NHD. Appendix A lists feature types and characteristics that were not encoded.)
Fields provide another text-based means of encoding characteristics and values. Each field encodes the value for one characteristic. The name of each field is an abbreviation of the name of the corresponding characteristic. The entries for a field are the values for the characteristic. For example, a feature classified as "Dam/Weir" may also have the characteristic of "Construction Material" with the values of "earthen" and "nonearthen", and the characteristic of "Operational Status" with the values of "operational" and "under construction". Using fields for characteristics, the following fields and entries can be encoded:
Table 1C contains the names of fields and the corresponding characteristics. Table 1C. Field names used for characteristics and related domains of values, listed alphabetically by field name (Note that several characteristics were not used in the initial release of the NHD. Appendix A lists feature types and characteristics that were not encoded. The "Standards for National Hydrography Dataset" (USGS, 1999) contains the names and definitions of all characteristics and values. It also lists the values that can be applied for each feature type. The document is available online through http://mapping.usgs.gov/standards/.)
(Adapted from "The U.S. EPA Reach File Version 3.0 alpha release (RF-3 Alpha) technical reference" (USEPA, 1994).) In the 1970's, the U.S. Environmental Protection Agency (USEPA) began creating a series of hydrographic databases of the surface waters of the conterminous United States and Hawaii. The structure and content of these Reach File databases were created to establish hydrologic sequencing, to perform hydrologic navigation for modeling applications, and to provide unique identifiers, called reach codes, for each surface water feature. A key characteristic of the Reach Files is the use of relations among reaches to define a connected hydrographic network. These relations provide connectivity among reaches even if their delineations do not form a topologically connected set of lines. The direction of water flow is also encoded using these relations. This connectivity enables hydrologic sequencing of reaches (identifying what is upstream and downstream of a given point in the hydrographic network), as well as navigating the network in an upstream or downstream direction. The unique reach codes assigned to each reach have been used to geocode the locations of many water-related observations. Examples include USEPA national databases for surface waters, such as STORET Water Quality Sampling Sites, Municipal and Industrial Facility Discharges, and Drinking Water Intakes. Using the reach code, observations in these databases can be associated with their locations on surface water features. The Reach File was first conceived in the early 1970's with a proof-of-concept file, known as Reach File Version 1.0 Alpha (RF1A), completed in 1975. The first full implementation, referred to as "Reach File Version 1.0" (RF1), was completed in 1982. The source for RF1 was the USGS 1:250,000-scale hydrography that had been photoreduced to a scale of 1:500,000 by the National Oceanic and Atmospheric Administration. RF1 consists of approximately 68,000 reach segments comprising 650,000 miles of stream. Although RF1 still supports broad-based national applications, the need to provide a more detailed hydrologic network motivated the development of Reach File Version 2.0 (RF2) in the late 1980's. RF2 was created by using the Feature File (now called the National Geographic Names Database) of the USGS Geographic Names Information System (GNIS) to add one new level of reach segments to RF1. RF2 contains 170,000 reach segments. Widespread interest in providing a more comprehensive, nationally consistent hydrologic database led to the development of the Reach File Version 3-Alpha (RF3-Alpha). This database combines data from RF1 and RF2, the GNIS, and the 1988 edition of USGS 1:100,000-scale digital line graph (DLG) hydrography data. RF3-Alpha contains nearly 3,200,000 individual hydrographic features (reaches) and more than 93,000,000 coordinate points. The NHD is the fourth in the series of continuing improvements to reach data. This database supplements attribute-based connectivity with reach delineations that provide spatial connectivity, common classification of features that underlie the reaches, and a design that encourages cooperative data maintenance and improvements among many organizations.
A transport reach represents the pathway for the movement of water through a drainage network and encodes the direction in which water flows along the reach. Transport reaches provide a basis through which locations of observations can be geocoded and linked to the drainage network. Encoding flow relations among the reaches provides the ability to navigate through a drainage network and is the basis for determining hydrologic sequencing in the network. Lines delineate transport reaches. Linear delineations of the feature types canal/ditch, pipeline, and stream/river provide the lines for most transport reach delineations. By themselves, however, these features may not depict all flows through a drainage network. For areal features of the type area of complex channels, estuary, ice mass, lake/pond, playa, reservoir, swamp/marsh, wash, canal/ditch, and stream/river, "artificial path" features complete the network to represent the flow of water into, through, and out of features that are delineated by using areas. "Connector" features fill gaps in the delineation of features through which water flows. For transport reaches for which the direction of flow is known, the lines are oriented in the direction of the flow of water. Note that the direction of flow is not always known (for example, when source materials are ambiguous) or uniform (for example, in tidal areas), and so the lines are not always oriented in the direction of flow. Three general rules determine the location of the ends of transport reaches:
These rules govern the delineation of most transport reaches and make the delineation of most reaches a straightforward process. The rules do have exceptions, however. Unusual configurations of features require modification of the rules, as do the variable condition and ambiguities of information sources. In places where unusual configurations of feature or ambiguities in sources predominate, a larger percentage of reaches using modified rules will be encountered. This appendix describes the conditions that most often influence transport reach delineation. The delineation of a transport reach follows those of one or more linear features. Where two or more features are followed, a transport reach follows delineations of :
Figure 1E illustrates the delineation of a reach that follows features of the same type, or, in the case of the artificial path, acts as surrogates for the same type. Different reaches follow features of different types (see Figure 2E). ![]() Figure 1E. Transport reach delineation for features of the same type. ![]() Figure 2E. Transport reach delineation for features of different types. A transport reach always follows the entire delineation of the underlying feature or features; the delineation of a feature is not split among reaches. Transport reaches abut and do not overlap. Exception: Insignificant lake/pond features (10-acre rule) An exception to the underlying feature rule is made for artificial paths that represent flow through lake/pond features of 10 acres (4.05 hectares) or less. In these cases, the lake/pond feature is ignored for the purpose of reach delineation. The artificial path is treated as an extension of the inflowing and outflowing linear feature and is not designated as a separate transport reach (see Figure 3E). ![]() Figure 3E. Transport reach delineation for insignificant lake/pond features. Like feature types (and their surrogates) In the "confluence-to-confluence" rule, a transport reach is a stretch of water between:
This rule applies where the features are of the same type or are of types (that is, artificial path and connector) that act as surrogates for features of the same type. These reaches must be contiguous and may not branch (see Figure 4E). ![]() Figure 4E. Confluence-to-confluence delineation among like feature types. Generally, divergences and confluences are treated as "confluences" for reach delineation. Separate reaches are delineated for each channel (see Figure 5E). ![]() Figure 5E. Confluence-to-confluence delineation for multiple channels. When an areal feature of type stream/river splits into two channels, a decision must be made as to whether or not reach delineation (that is, the addition of artificial paths and creation reaches) should be performed in the secondary channel. The following rules (see Figure 6E) guide reach delineation for the channels:
![]() Figure 6E. Transport reach delineation for multiple divergent channels. When the land separating the channels is large or long, it may be clear that the primary and the secondary channels are different stream/rivers and, therefore, both channels have reaches delineated. Regardless of the size and shape of the land, the presence of tributaries to the secondary channel weighs heavily in determining that it will have reaches delineated. Exception: Insignificant confluences (5-mile rule) Where a simple14 tributary or divergence of less than 5 miles (approximately 8.06 kilometers) in length intersects an areal feature of type stream/river, the intersection is not considered to be a confluence for delineating the reach along the areal stream/river (see Figure 7E). This approach avoids breaking major stream/rivers into unnecessarily small reaches caused by the confluence of small tributaries and divergences. ![]() Figure 17. Significant and insignificant confluences in reach delineation. Unlike feature types: stream/river and canal/ditch The intersection of features types stream/river and canal/ditch that occurs at the same elevation (see Figure 8E) generally is treated as a confluence for the canal/ditch but not for the stream/river. An alternate approach treats the intersection as a confluence for both feature types. ![]() Figure 8E. Confluence of stream/river and canal/ditch. No confluence: underpasses and pipelines Because fluids carried by features do not flow together at an underpass (where features intersect at different elevations), there is no confluence, and so the confluence-to-confluence rule does not apply and the reaches are not broken at the intersection. With the information available during the development of the initial release of the NHD, it was not possible to determine if fluids carried by pipelines flow together with those carried by other features (for example, stream/river and canal/ditch) with which a pipeline intersects on a map. The assumption is that the fluids do not flow together. So there is no confluence, the confluence-to-confluence rule does not apply, and the reaches are not broken at the intersection. (When it is known that a pipeline exchanges fluids with another feature of a different type, it will be treated as a confluence of unlike feature types.) A branched path transport reach connects reaches that enter and exit an areal feature (see Figure 9E). The branched path transport reach avoids the need to define flow channels, confluences and divergences, and confluence-based transport reaches in areal features. It is used where information needed to delineate these items reliably is not available and in other places at the analyst�s discretion. Reaches that follow this rule occur most often in large15 features of type lake/pond and swamp/marsh and may occur in other areal features. Artificial paths delineated within the areal feature provide the lines needed to delineate this special transport reach. The reach may branch and, infrequently, may be discontiguous (see Figure 10E). ![]() Figure 9E. Branched path reach delineation. In cases where channels and confluences are delineated, confluence-based reaches are delineated, and branched path transport reaches are not needed. If the flow channels delineated within a feature are incomplete, a branched path transport reach is added to provide connectivity (see Figure10E). ![]() Figure 10E. Use of branched path reaches where other features provide flow channels through areal features. Exception: Insignificant lake/pond features (10-acre rule) An exception to the branched path rule is made for artificial paths that represent flow through lake/pond features of 10 acres (4.05 hectares) or less. In these cases, the artificial paths are treated as extensions of the inflowing and outflowing linear features, and the confluence-to-confluence delineation rule is used for transport reaches within the lake/pond (see Figure11E). ![]() Figure 11E. Transport reach delineation in significant and insignificant lake/pond features.
(Adapted from "Hydrologic unit maps" (Seaber, Kapinos, and Knapp, 1987)). A hydrologic unit is a member of the hierarchical system for identifying and subdividing river-basin units of the United States. Such units are used by water resource organizations for locating, storing, retrieving, and exchanging hydrologic data; for indexing and inventorying hydrologic data in cataloging water-data acquisition activities; and in a variety of other applications. A standard four-level hierarchy16 of hydrologic units exists for the Nation. The levels in this hierarchy, listed from largest to smallest in area, are region, subregion, accounting unit, and subbasin:
All boundaries of units within the United States are hydrologic (hydrographic) in nature. At the international boundaries of the United States with Mexico and Canada, region and subregion boundaries end or coincide with the boundary. The boundaries of accounting units and subbasins are hydrologic, and can be extended into Mexico and Canada. With the exception of areas near the international boundary, each unit nests within, or coincides with, its next largest unit. Seaber, Kapinos, and Knapp (1987) provide additional technical criteria for delineating hydrologic units. Each hydrologic unit has been assigned a name corresponding to the principal hydrologic feature(s) within the unit. In the absence of such features, the assigned name may reflect a cultural or political feature within the unit. All regions and subregions are uniquely named; however, the accounting units are named uniquely only within each region, and the subbasins are named uniquely only within each accounting unit. Duplication of some names at the subbasin level is unavoidable because a large number of streams share the same names. Shown below is an example of the units in the hierarchy (see Figure 1F): region - New England region: the drainage within the United States that ultimately discharges into: (a) the Bay of Fundy, (b) the Atlantic Ocean within and between the States of Maine and Connecticut, (c) Long Island Sound north of the New York-Connecticut state line, and (d) the Riviere St. Francois, a tributary of the St. Lawrence River. subregion - Connecticut: the Connecticut River basin. accounting unit - Lower Connecticut: the Connecticut River basin below Vernon Dam. subbasin - Chicopee. ![]() Figure 1F. Hydrologic units in the New England region. (Data from Allord, 1992). An 8-digit hydrologic unit code uniquely identifies each of the four levels of classification within four 2-digit fields. The first 2 digits identify regions, the first 4 digits identify subregions, the first 6 digits identify accounting units, and the full 8 digits identify subbasins. For example, the hydrologic unit codes for the example provided above are as follows: 01 - the region (New England) 0108 - the subregion (Connecticut) 010802 - the accounting unit (Lower Connecticut) 01080204 - the subbasin (Chicopee) Zeroes in the two-digit accounting unit field indicate that the accounting unit and the subregion are the same. Zeroes in the two-digit subbasin field indicate that the subbasin and the accounting unit are the same. Additional information is available in the online document "Hydrologic unit maps" (USGS, 1998) at http://water.usgs.gov/lookup/get?huc. Hydrologic unit boundaries have also been incorporated as a map layer in the National Atlas of the United States and are available online at http://www.nationalatlas.gov/hucsm.htm The NHD contains certain peculiarities, which generally reflect inconsistencies and deficiencies in the source data used to create the NHD. The items in this category tend to be irritating, but they do not undermine the usefulness of the NHD and can be resolved on a case by case basis. In some cases, such as quad edge effects, mismatches are likely to be encountered frequently. However, developers of the NHD decided it would be more valuable to make the NHD available as soon as possible rather than investing the time and money that would have been required to identify and correct every quad edge mismatch in the raw data. The purpose of this list is to alert users to the existence of these peculiarities so that they can be anticipated and dealt with as they occur. The following summary describes the most significant of these and any steps, already taken or planned, to resolve them. Features in the NHD still stop and start at USGS 1:100,000-scale quadrangle edges. Reaches, however, are continuous across quad edges. By delineating features based on the 1:100,000-scale quadrangle, the NHD maintains the lineage of each feature. By making the reaches continuous across quad edges, the NHD maintains the ability to navigate through the hydrologic network and the ability to create routes and event data without artificial breaks at the quad edges. Because the NHD is designed to manage the data hydrologically, discrepancies at quad edges become more obvious. Some features stop abruptly, and some features cross quad edges but are classified differently on both sides. This reflects the different sources and dates used to make the 1:100,000-scale maps and associated DLGs from which the NHD was created. The feature types and characteristics in the NHD reflect the coding of the original DLGs. If a feature was miscoded in the DLG, it likely will be misclassified in the NHD. In some cases, the DLG did not provide enough information to create a correct NHD feature. The following are a few "systematic" coding problems we would like to point out. The DLG code 050 0116 is defined as "bay, estuary, gulf, ocean, or sea,". This code was intended to describe saltwater areas, but in some cases it was used for "named" bays within freshwater areas. The DLG code 050 0116 was always converted to the NHD feature sea/ocean even when applied to an inland "bay". Therefore, some landlocked (i.e.inland) sea/ocean features were created. Conduits like penstocks, aqueducts, tunnels, and pipelines were coded in various ways in the DLGs. In the NHD, the intent is to classify these features by their form. Due to coding inconsistencies or inadequate information, the DLG did not always provide enough information to carry out the NHD intent. For example, in the NHD an open artificial channel would be classified as a canal/ditch, but a closed conduit would be classified as a pipeline. If the feature is "underground," it would have a "relationship to surface" of underground, but if it is inside a tunnel, then both canal/ditch and tunnel would have been created in the NHD. The same real-world feature also could be classified differently if it appeared on different 1:100,000-scale quads (see previous quad-edge effects discussion)
Coastal features - foreshore versus sand Several symbols were used on the topographic and topographic/bathymetric maps to identify sand, sand dunes, tidal flats, and foreshore areas. Often these symbols were confused when applying DLG codes. As a result, foreshore features sometimes stop abruptly (see previous quad-edge effects discussion). Stream/rivers controlled by dams that become a series of slackwater pools When a stream/river is impounded or has the flow controlled for navigation, it often is difficult to classify the feature based on the information shown on the topographic map. Does it behave like a stream/river or more like a lake/pond? Most often, if a feature was named on the map as a �lake�, it was coded in DLG as a lake. But this was done inconsistently. It becomes more obvious in the NHD because reaches are delineated differently if the feature is a stream/river or a lake/pond. In the source DLG data, the decision to classify a waterbody as a lake/pond or a reservoir was based on the name of the feature. If the name contained the generic term "reservoir", it was coded 050 0101 (reservoir). In the NHD, an attempt was made to clarify this distinction based on the form of the feature. However, in some cases there was not enough information in the DLG to make the correct classification. A lake/pond is a standing body of water with a predominately natural shoreline (it may be impounded). A reservoir is a constructed basin. In building the NHD, if the feature was coded as 050 0101(reservoir) or 050 0421(lake/pond) it was classified as a lake/pond unless the geometry of the feature indicated that it was a constructed basin (it was square). Other DLG codes for sewage disposal pond, filtration pond, and aquaculture ponds were converted to the NHD feature reservoir.
NHD linework doesn�t match the published USGS 1:100,000-scale map Some of the 1:100,000-scale DLGs were created from BLM editions or from earlier planimetric editions of the1:100,000-scale maps. These maps were replaced with USGS topographic editions, but usually, the DLG was not re-digitized. The date of the source DLG indicates which edition of the map was used for digitizing. If the date of the source DLG is older than the published 1:100,000-scale topographic map, it is likely that the DLG was digitized from a planimetric or BLM edition. Names for transport reaches came from RF3. Names from RF3 were validated against GNIS. There are reaches that have names in GNIS that do not have names in the NHD and some names in NHD are applied to the wrong path when compared to GNIS. Users are encouraged to supply updates to names to the USGS. GNIS is continually updated (including Board of Geographic Names (BGN) decisions and new names), therefore, names in the NHD are likely to be more current than those on published 1:100,000-scale maps. Subbasin boundaries and the features that touch and cross them The NHD is a seamless dataset. However, initial distribution of the NHD data is by subbasins. It is not possible to "clip" a subbasin from the seamless data using existing subbasin boundaries, because the resolution of the subbasin boundaries does not match the resolution of the reach linework. Generally the subbasin boundaries are based on 1:250,000-scale linework and the reaches are based on 1:100,000-scale linework. Data are pulled from the seamless NHD database and associated with the appropriate subbasin using a number of rules.
1. All reaches that have a reach code that includes the subbasin number 2. All features that are part of the reaches from step 1 (artificial path, 1-D canal/ditch, connector, 1-D stream/river, and pipeline) 3. All non-reached features (including landmarks and 2-D stream/rivers and 2-D canal/ditches) that are within or "touch" the subbasin boundary. As a result of these rules, features can extend outside the subbasin boundaries. The most obvious examples are 2-D stream/rivers. They are included in a subbasin if they touch the subbasin boundary. This means they will appear in multiple adjacent subbasins. These duplicated features should not pose a problem unless adjacent subbasins are to be appended. A tool to append subbasins is being developed that will properly delete one of the instances. Some reaches may appear to cross subbasin boundaries. The flow direction relationships are used to determine which subbasin a reach is associated with, not just the subbasin boundary. In building the NHD, problems with reaches being clipped in RF3 were fixed whenever possible, but a few cases where reaches are associated with the wrong subbasin still exist. Squared-off coastal subbasin boundaries Along the coast, the NHD used subbasin boundaries that were extended as straight lines into the ocean to the edge of the 1:100,000-scale quad to ensure that all coastal islands in the DLG were included in the NHD. There are a number of subbasins that represent a single waterbody with the edge of the water body coinciding with the edge of the subbasin. These subbasins are: 01100007 � Long Island Sound 02040204 � Delaware Bay 02060001 � Upper Chesapeake 02080101 � Lower Chesapeake 04020300 � Lake Superior 04060200 � Lake Michigan 04080300 � Lake Huron 04120200 � Lake Erie 04150200 � Lake Ontario In addition, the NHD does not have data for: 20090000 - Northwestern Hawaiian Islands 21030001 - Canal Zone. Panama Canal Zone. 21030002 - Navassa. Navassa Island. 21030003 - Roncador-Serrana. Roncador and Serrana Banks. The waterbodies represented by these subbasins are not represented as waterbody reaches in the NHD. The boundaries of the subbasins that border these �waterbody subbasins� were extended to encompass the area enclosed by the �waterbody subbasins�. Any hydrographic features such as islands, including streams and lakes on the islands, that are inside these waterbody subbasins are included in the bordering subbasins. Coastline reaches that bound stream/rivers RF3 and DLG sometimes used different sources and rules in tidal areas to determine where a stream ends and the ocean begins. In the NHD, the feature classification comes form the DLG, but the information used to create coastline reaches comes from RF3. As a result, coastline reaches sometimes bound stream/river features.
Waterbody reaches were created automatically by associating a lake/pond (and only lake/ponds) in the NHD with a �lake� identified in RF3. Because of discrepancies in coding and coordinates among the various sources, not all lake/ponds in the NHD have been identified as waterbody reaches. Users needing to link information to a lake that does not have an associated reach with an assigned reach code, may create a reach for the lake/pond and provide the updates to the NHD. In some cases, lake/ponds near the subbasin boundary may appear not to be associated with a waterbody reach. Because of the rules needed to create subbasins from the seamless NHD database, waterbodies along a subbasin boundary may appear in both subbasins. The waterbody reaches however, will only appear in the subbasin identified by the waterbody reach code. Flow/coordinate direction/measure direction In the NHD, flow direction is known and recorded for some, but not all, transport reaches. Flow direction is recorded in flow relationships that describe which transport reaches exchange flow. Recording the flow direction for a transport reach also affects the order of the reach�s coordinates and the direction of the measures along the reach�s route. When flow direction is recorded for a transport reach, the coordinates of the reach are ordered from upstream to downstream and the measures along the routes for the reach run from downstream to upstream. When flow direction is either unknown or not recorded for a transport reach, coordinate order and measure direction are indeterminate. The coordinates of coastal reaches are ordered so that the water is to the right and the land is to the left and the measures along the routes run the opposite direction. For more information on this subject, see the Introducing the NHDinARC technical reference. Artificial Paths that fall outside of the 2-D features they represent Artificial paths were created in 2-D stream/rivers, 2-D canal/ditches, and lake/ponds using ARC/INFO ® grid with a tolerance of approximately 17 meters. Artificial paths may fall outside of the feature they represent, they may fall on top of an edge of the feature they represent, or they may fall extremely close to the edge of a feature they represent. Artificial paths were only created in headwater lake/ponds when the direction of flow was available from RF3. Artificial paths do not follow submerged streams, which represent the old stream channel through an impounded lake/pond. Footnotes1These feature types are area of complex channels, estuary, ice mass, lake/pond, playa, reservoir, swamp/marsh, wash, and wide canal/ditch and stream/river. 2Large areal features cover 10 or more acres (approximately 4.05 or more hectares). 3Features of the type lake/pond most often are the basis for waterbody reach delineation in the initial release. An exception is the State of Washington where, on the basis of work done by a State agency, waterbody reaches are based on areal delineations of the features types ice mass, lake/pond, reservoir, and swamp/marsh. In the future, feature types that could provide the basis for waterbody reach delineation are area of complex channels, estuary, lake/pond, playa, sea/ocean, wash, and areal delineations of canal/ditch and stream/river. 4Hydrologic units (Seaber, Kapinos, and Knapp, 1987) provide a systematic means of identifying and subdividing river-basin units. The subbasin is the fourth-level subdivision of hydrologic units. Additional information about hydrologic units is in appendix F. 5These are the numeric codes for the direction descriptions:
"710" for Out. "711" for Bidirectional. "712" for Network Start. "713" for Network End. "714" for Non-flowing Connection. 6The lowest value for stream level is:
"2" for transport reaches that terminate at the Great Lakes or the Great Salt Lake. "3" for transport reaches that terminate at the boundary of the United States with Canada or Mexico. "4" for transport reaches that terminate at any other place (isolated drainage). 7Reach File Versions 1 and 2, which are described in Appendix D. 8Information about the Geographic Names Information System is available online at http://geonames.usgs.gov/index.html. 9Geographic names are encoded using the "Latin 1" character set (International Organization for Standardization (ISO) standard 8859-1). 10In this data quality discussion, the "Pacific Northwest" includes the Pacific Northwest hydrologic region (region 17) and the Williamson, Sprague, and Upper Klamath Lake (Oregon) subbasins (18010201, -02, and -03, respectively). This area includes the State of Washington, most of Idaho and Oregon, and parts of western Montana and Wyoming. 11Identification of commercial products is for information only. No endorsement by the U.S. Government is implied or intended. 12At 1:100,000 scale, 0.02 inch is approximately 167 feet (50.8 meters), and at 1:24,000 scale, 40 feet (approximately 12.2 meters). 13Identification of commercial products is for information only. No endorsement by the U.S. Government is implied or intended. 14A simple tributary or divergence is a reach that has no tributaries. 15Large areal features cover 10 or more acres (approximately 4.05 or more hectares). 16Efforts are under way to add levels of subdivision, especially fifth- and sixth-level units. |