SDETrims.DBO.Hydro_RiversStreams

Metadata also available as

Frequently-anticipated questions:


What does this data set describe?

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

    U.S. Geological Survey in coope, USDA Forest Service, and other Feder, See dataset specific metadata., SDETrims.DBO.Hydro_RiversStreams: U.S. Geological Survey, Reston, Virginia.

    Online Links:

    • Service=sde:sqlserver:CHUCKNORRIS; Database=SDETrims; Version=dbo.DEFAULT

  2. What geographic area does the data set cover?

    West_Bounding_Coordinate: -98.953964
    East_Bounding_Coordinate: -94.071603
    North_Bounding_Coordinate: 34.157109
    South_Bounding_Coordinate: 29.496422

  3. What does it look like?

  4. Does the data set describe conditions during a particular time period?

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

  5. What is the general form of this data set?

    Geospatial_Data_Presentation_Form: vector digital data

  6. How does the data set represent geographic features?

    1. How are geographic features stored in the data set?

      This is a Vector data set. It contains the following vector data types (SDTS terminology):

      • G-polygon (70350)

    2. What coordinate system is used to represent geographic features?

      Horizontal positions are specified in geographic coordinates, that is, latitude and longitude. Latitudes are given to the nearest 0.000001. Longitudes are given to the nearest 0.000001. Latitude and longitude values are specified in Decimal degrees.

      The horizontal datum used is North American Datum of 1983.
      The ellipsoid used is Geodetic Reference System 80.
      The semi-major axis of the ellipsoid used is 6378137.000000.
      The flattening of the ellipsoid used is 1/298.257222.

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

  7. How does the data set describe geographic features?

    SDETrims.DBO.Hydro_RiversStreams

    OBJECTID
    Internal feature number. (Source: ESRI)

    Sequential unique whole numbers that are automatically generated.

    TLID

    FNODE

    TNODE

    LENGTH

    FEDIRP

    FENAME

    FETYPE

    FEDIRS

    CFCC

    FRADDL

    TOADDL

    FRADDR

    TOADDR

    ZIPL

    ZIPR

    CENSUS1

    CENSUS2

    CFCC1

    CFCC2

    SOURCE

    Shape
    Feature geometry. (Source: ESRI)

    Coordinates defining the features.

    SEGLEN

    Shape.len

    SDETrims.DBO.Anno_458_816

    Entity_and_Attribute_Overview:
    The National Hydrography Dataset is a comprehensive set of digital spatial data that encodes information about naturally occurring and constructed bodies of water, paths through which water flows, and related entities. The information encoded about features includes a feature date, classification by type, other characteristics, a unique common identifier, the feature length or area, and (rarely) elevation of the surface of water pools and a description of the stage of the elevation. For reaches, encoded information includes a reach code. Names and their identifiers in the Geographic Names Information System, are assigned to most feature types. The direction of flow is encoded for networked features. The data also contains relations that encode metadata, and information that supports the exchange of future updates and improvements to the data. The names and definitions of all feature types, characteristics, and values are in the Standards for National Hydrography Dataset: Reston, Virginia, U.S. Geological Survey, 1999. The document is available online through <http://mapping.usgs.gov/standards/>.
    Entity_and_Attribute_Detail_Citation:
    The names and definitions of all feature types, characteristics, and values are in U.S. Geological Survey, 1999, Standards for National Hydrography Dataset High Resolution: Reston, Virginia, U.S. Geological Survey. The document is available online through <http://mapping.usgs.gov/standards/>. Information about tables and fields in the data are available from the user documentation for the National Hydrography Dataset at <http://nhd.usgs.gov>. The National Map - Hydrography Fact Sheet is also available at: <http://erg.usgs.gov/isb/pubs/factsheets/fs06002.html>.


Who produced the data set?

  1. Who are the originators of the data set? (may include formal authors, digital compilers, and editors)

  2. Who also contributed to the data set?

    See dataset specific metadata.

  3. To whom should users address questions about the data?

    Earth Science Information Center, U.S. Geological Survey
    507 National Center
    Reston, VA 20192
    USA

    1 888 257 8747 (voice)
    ask@usgs.gov

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


Why was the data set created?

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


How was the data set created?

  1. From what previous works were the data drawn?

  2. How were the data generated, processed, and modified?

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

    Data sources used in this process:

    • C:\DOCUME~1\adube\LOCALS~1\Temp\xml1E.tmp

  3. What similar or related data should the user be aware of?


How reliable are the data; what problems remain in the data set?

  1. How well have the observations been checked?

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

  2. How accurate are the geographic locations?

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

  3. How accurate are the heights or depths?

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

  4. Where are the gaps in the data? What is missing?

    The completeness of the data reflects the content of the sources, which most often are the published USGS topographic quadrangle and/or the USDA Forest Service Primary Base Series (PBS) map. The USGS topographic quadrangle is usually supplemented by Digital Orthophoto Quadrangles (DOQs). Features found on the ground may have been eliminated or generalized on the source map because of scale and legibility constraints. In general, streams longer than one mile (approximately 1.6 kilometers) were collected. Most streams that flow from a lake were collected regardless of their length. Only definite channels were collected so not all swamp/marsh features have stream/rivers delineated through them. Lake/ponds having an area greater than 6 acres were collected. Note, however, that these general rules were applied unevenly among maps during compilation. Reaches codes are defined on all features of type stream/river, canal/ditch, artificial path, coastline, and connector. Waterbody reach codes are defined on all lake/pond and most reservoir features. Names were applied from the GNIS database. Detailed capture conditions are provided for every feature type in the Standards for National Hydrography Dataset available online through <http://mapping.usgs.gov/standards/>. This statement is generally true for the most common sources of NHD data. Other sources and methods may have been used to create or update NHD data. In some cases, additional information may be found in the NHDMetadata table.

  5. How consistent are the relationships among the observations, including topology?

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


How can someone get a copy of the data set?

Are there legal restrictions on access or use of the data?

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

  1. Who distributes the data set? (Distributor 1 of 1)

    Earth Science Information Center, U.S. Geological Survey
    507 National Center
    Reston, VA 20192
    USA

    1 888 275 8747 (voice)
    ask@usgs.gov

    Hours_of_Service: 0800-1600 Eastern Time
    Contact_Instructions:
    In addition to the address above there are other ESIC offices throughout the country. A full list of these offices is at URL: <http://mapping.usgs.gov/esic/esic_index.html>
  2. What's the catalog number I need to order this data set?

    Downloadable Data

  3. What legal disclaimers am I supposed to read?

  4. How can I download or order the data?


Who wrote the metadata?

Dates:
Last modified: 15-Apr-2004
Metadata author:
Earth Science Information Center, U.S. Geological Survey
507 National Center
Reston, VA 20192
USA

REQUIRED: The telephone number by which individuals can speak to the organization or individual. (voice)

Hours_of_Service: 0800-1600 Eastern Time
Contact_Instructions:
In addition to the address above there are other ESIC offices throughout the country. A full list of these offices is at URL: <http://mapping.usgs.gov/esic/esic_index.html>
Metadata standard:
FGDC Content Standards for Digital Geospatial Metadata (FGDC-STD-001-1998)
Metadata extensions used:


Generated by mp version 2.8.6 on Mon Aug 20 13:58:55 2007