NATIONAL HYDROGRAPHY DATASET - HYDROGRAPHIC LANDMARKS 1:24K

Metadata:

• Identification_Information
• Data_Quality_Information
• Spatial_Data_Organization_Information
• Spatial_Reference_Information
• Entity_and_Attribute_Information
• Distribution_Information
• Metadata_Reference_Information

Identification_Information:

Citation:

Citation_Information:

Originator:

U.S. Geological Survey in cooperation with U.S. Environmental Protection Agency, USDA Forest Service, and Florida Department of Environmental Protection.

Publication_Date: 20060501

Publication_Time: Unknown

Title: NATIONAL HYDROGRAPHY DATASET - HYDROGRAPHIC LANDMARKS 1:24K

Geospatial_Data_Presentation_Form: vector digital data

Publication_Information:

Publication_Place: Reston, Virginia

Publisher: U.S. Geological Survey

Other_Citation_Details: State of Florida

Online_Linkage: <http://www.dep.state.fl.us/>

Description:

Abstract:

This data set contains points representing NHD hydrographic landmark features. 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.

The NHD data was originally created by the USGS and EPA along with other federal, state, and local agencies. The FDEP is the NHD data steward for Florida. This data was originally in geodatabase format. When in shapefile format the data loses the network functionality of the geodatabase. Please contact the FDEP if you need the original geodatabase.

Last Updated, May, 2006.

This layer replaces NHDLMP - National Hydrography Dataset Landmarks, Point, which was distributed in previous versions of FGDL.

Purpose:

The NHD is a national framework for assigning reach addresses to water-related entities, such as industrial discharges, drinking water supplies, fish habitat areas, wild and scenic rivers. Reach addresses establish the locations of these entities relative to one another within the NHD surface water drainage network, much like addresses on streets. Once linked to the NHD by their reach addresses, the upstream/downstream relationships of these water-related entities--and any associated information about them--can be analyzed using software tools ranging from spreadsheets to geographic information systems (GIS). GIS can also be used to combine NHD-based network analysis with other data layers, such as soils, landuse 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.

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 water bodies 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.

Supplemental_Information:

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>.

Time_Period_of_Content:

Time_Period_Information:

Single_Date/Time:

Calendar_Date: 20060501

Currentness_Reference: publication date

Status:

Progress: Complete

Maintenance_and_Update_Frequency: As needed

Spatial_Domain:

Bounding_Coordinates:

West_Bounding_Coordinate: -87.429040

East_Bounding_Coordinate: -79.872251

North_Bounding_Coordinate: 30.983191

South_Bounding_Coordinate: 24.492815

Keywords:

Theme:

Theme_Keyword_Thesaurus: NONE

Theme_Keyword: FWHYDROGRAPHY

Theme_Keyword: Hydrography

Theme_Keyword: Stream / River

Theme_Keyword: Lake / Pond

Theme_Keyword: Canal / Ditch

Theme_Keyword: Reservoir

Theme_Keyword: Spring / Seep

Theme_Keyword: Swamp / Marsh

Theme_Keyword: Artificial Path

Theme_Keyword: Reach Code

Theme:

Theme_Keyword_Thesaurus: ISO 19115 Topic Category

Theme_Keyword: inlandWaters

Place:

Place_Keyword_Thesaurus:

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

Place_Keyword: US

Access_Constraints: NONE

Use_Constraints:

THE DATA INCLUDED IN FGDL ARE 'AS IS' AND SHOULD NOT BE CONSTRUED AS LEGALLY BINDING. THE UNIVERSITY OF FLORIDA GEOPLAN CENTER SHALL NOT BE LIABLE FOR ANY DAMAGES SUFFERED AS A RESULT OF USING, MODIFYING, CONTRIBUTING OR DISTRIBUTING THE MATERIALS.

A note about data scale:

Scale is an important factor in data usage. Certain scale datasets are not suitable for some project, analysis, or modeling purposes. Please be sure you are using the best available data.

1:24000 scale datasets are recommended for projects that are at the county level. 1:24000 data should NOT be used for high accuracy base mapping such as property parcel boundaries. 1:100000 scale datasets are recommended for projects that are at the multi-county or regional level. 1:125000 scale datasets are recommended for projects that are at the regional or state level or larger.

Vector datasets with no defined scale or accuracy should be considered suspect. Make sure you are familiar with your data before using it for projects or analysis. Every effort has been made to supply the user with data documentation. For additional information, see the References section and the Data Source Contact section of this documentation. For more information regarding scale and accuracy, see our webpage at: <http://geoplan.ufl.edu/education.html>

Point_of_Contact:

Contact_Information:

Contact_Organization_Primary:

Contact_Organization: Florida Geographic Data Library (FGDL)

Contact_Address:

Address_Type: mailing address

Address: 431 Architecture PO Box 115706

City: Gainesville

State_or_Province: Florida

Postal_Code: 32611-5706

Contact_Electronic_Mail_Address: Web site: <http://www.fgdl.org>

Contact_Electronic_Mail_Address: Technical Support: <http://www.fgdl.org/fgdlfeed.html>

Contact_Electronic_Mail_Address: For FGDL Software: <http://www.fgdl.org/software.html>

Contact_Electronic_Mail_Address:

FGDL Frequently Asked Questions: <http://www.fgdl.org/fgdlfaq.html>

Contact_Electronic_Mail_Address: FGDL Mailing Lists: <http://www.fgdl.org/fgdl-l.html>

Data_Set_Credit: See dataset specific metadata.

Cross_Reference:

Citation_Information:

Other_Citation_Details: <http://nhd.usgs.gov/>

Data_Quality_Information:

Attribute_Accuracy:

Attribute_Accuracy_Report:

GeoPlan relied on the integrity of the attribute information within the original data.

Logical_Consistency_Report:

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

Completeness_Report:

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

Positional_Accuracy:

Horizontal_Positional_Accuracy:

Horizontal_Positional_Accuracy_Report:

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

This statement is generally true for the most common sources of NHD data. Other sources and methods may have been used to create or update NHD data. In some cases, additional information may be found in the NHDMetadata table.

Vertical_Positional_Accuracy:

Vertical_Positional_Accuracy_Report:

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

Lineage:

Source_Information:

Source_Scale_Denominator: 24000

Source_Citation_Abbreviation: FDEP

Source_Contribution: Spatial and Attribute Information

Process_Step:

Process_Description:

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

Process_Date: Unknown

Process_Step:

Process_Description:

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

Process_Date: 2004

Process_Step:

Process_Description: See dataset specific metadata.

Process_Step:

Process_Description:

GeoPlan downloaded this dataset from the Florida Department of Environmental Protection. The data was downloaded as a personal geodatabase and was in the following projection: Albers HPGN, Units: meters.

The feature class NHDPoint was converted to shapefile via ArcCatalog 9.2. Feature Type and Descriptions were joined to the shapefile based on the field FCODE. The join table was based of information gathered at: <http://nhd.usgs.gov/NHDinGEO_FCODEs_by_layer.pdf>

Additional details to be used in metadata were gathered from the following link: <http://nhd.usgs.gov/NHD.pdf>

- All records were upcased. - Changed projection file to FGDL Albers - DESC_ field was added and calculated based on FCODE Descriptions - A DESCRIPT field was added based on Feature Type - A FGDLAQDATE field was added based on date GeoPlan downloaded the data

Source_Used_Citation_Abbreviation: GeoPlan

Process_Date: 20070815

Spatial_Data_Organization_Information:

Direct_Spatial_Reference_Method: Vector

Point_and_Vector_Object_Information:

SDTS_Terms_Description:

SDTS_Point_and_Vector_Object_Type: Entity point

Point_and_Vector_Object_Count: 1429

Spatial_Reference_Information:

Horizontal_Coordinate_System_Definition:

Planar:

Map_Projection:

Map_Projection_Name: Albers Conical Equal Area

Albers_Conical_Equal_Area:

Standard_Parallel: 24.000000

Standard_Parallel: 31.500000

Longitude_of_Central_Meridian: -84.000000

Latitude_of_Projection_Origin: 24.000000

False_Easting: 400000.000000

False_Northing: 0.000000

Planar_Coordinate_Information:

Planar_Coordinate_Encoding_Method: coordinate pair

Coordinate_Representation:

Abscissa_Resolution: 0.002048

Ordinate_Resolution: 0.002048

Planar_Distance_Units: meters

Geodetic_Model:

Horizontal_Datum_Name: D_North_American_1983_HARN

Ellipsoid_Name: Geodetic Reference System 80

Semi-major_Axis: 6378137.000000

Denominator_of_Flattening_Ratio: 298.257222

Vertical_Coordinate_System_Definition:

Altitude_System_Definition:

Altitude_Datum_Name: National Geodetic Vertical Datum of 1929

Altitude_Resolution: 1.000000

Altitude_Distance_Units: meters

Altitude_Encoding_Method:

Explicit elevation coordinate included with horizontal coordinates

Entity_and_Attribute_Information:

Detailed_Description:

Entity_Type:

Entity_Type_Label: NHD24POINT_MAY06

Entity_Type_Definition: NHD24POINT_MAY06.DBF

Attribute:

Attribute_Label: COMID

Attribute_Definition: Uniquely identifies the occurrence of each feature

Attribute:

Attribute_Label: FDATE

Attribute_Definition: Date of last feature modification

Attribute:

Attribute_Label: RESOLUTION

Attribute_Definition: Code for source RESOLUTION

Attribute_Domain_Values:

Enumerated_Domain:

Enumerated_Domain_Value: 1

Enumerated_Domain_Value_Definition: local RESOLUTION

Enumerated_Domain:

Enumerated_Domain_Value: 2

Enumerated_Domain_Value_Definition: high RESOLUTION

Enumerated_Domain:

Enumerated_Domain_Value: 3

Enumerated_Domain_Value_Definition: medium RESOLUTION

Attribute:

Attribute_Label: GNIS_ID

Attribute_Definition: Unique identifier assigned by GNIS

Attribute:

Attribute_Label: GNIS_NAME

Attribute_Definition:

proper name specific term or expression by which a particular geographic entity is known

Attribute:

Attribute_Label: REACHCODE

Attribute_Definition:

Unique identifier composed of two parts. The first eight digits is the subbasin code as defined by FIPS The next six digits are randomly assigned squential numbers that are unique within a Catalog Unit

Attribute:

Attribute_Label: FTYPE

Attribute_Definition: Three digit integer value unique identifier of a feature type

Attribute:

Attribute_Label: FCODE

Attribute_Definition:

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".

Attribute:

Attribute_Label: COUNTY

Attribute_Definition: County

Attribute:

Attribute_Label: OBJECTID

Attribute_Definition: Internal feature number.

Attribute_Definition_Source: ESRI

Attribute_Domain_Values:

Unrepresentable_Domain:

Sequential unique whole numbers that are automatically generated.

Attribute:

Attribute_Label: DESC_

Attribute_Definition:

Description field, which holds a character string that contains all characteristics and values associated with a feature code.

Attribute:

Attribute_Label: DESCRIPT

Attribute_Definition: GeoPlan added field based on Feature Type.

Attribute_Definition_Source: GeoPlan

Attribute:

Attribute_Label: FGDLAQDATE

Attribute_Definition: Date GeoPlan acquired data from source.

Attribute_Definition_Source: GeoPlan

Attribute:

Attribute_Label: SHAPE

Attribute_Definition: Feature geometry.

Attribute_Definition_Source: ESRI

Attribute_Domain_Values:

Unrepresentable_Domain: Coordinates defining the features.

Attribute:

Attribute_Label: AUTOID

Attribute_Definition: Unique ID added by GeoPlan

Attribute_Definition_Source: GeoPlan

Overview_Description:

Entity_and_Attribute_Overview:

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>.

Distribution_Information:

Distributor:

Contact_Information:

Contact_Organization_Primary:

Contact_Organization: Florida Geographic Data Library (FGDL)

Contact_Address:

Address_Type: mailing address

Address: 431 Architecture PO Box 115706

City: Gainesville

State_or_Province: Florida

Postal_Code: 32611-5706

Country: United States

Contact_Electronic_Mail_Address: Web site: <http://www.fgdl.org>

Contact_Electronic_Mail_Address: Technical Support: <http://www.fgdl.org/fgdlfeed.html>

Contact_Electronic_Mail_Address: For FGDL Software: <http://www.fgdl.org/software.html>

Contact_Electronic_Mail_Address:

FGDL Frequently Asked Questions: <http://www.fgdl.org/fgdlfaq.html>

Contact_Electronic_Mail_Address: Mailing list for FGDL: <http://www.fgdl.org/fgdl-l.html>

Resource_Description: DOWNLOADABLE DATA

Distribution_Liability:

THE FGDL DATA AS PROVIDED BY CONTRIBUTING ORGANIZATIONS AND ANY PROGRAMMING SOFTWARE CREATED BY THE UNIVERSITY OF FLORIDA GEOPLAN CENTER (COLLECTIVELY THE 'MATERIALS') ARE COPYRIGHTED BY THE UNIVERSITY OF FLORIDA GEOPLAN CENTER FOR THE FGDL CONTRIBUTING AGENCIES AND ORGANIZATIONS (THE 'DATA PROVIDERS'). DO NOT REPRODUCE, REDISTRIBUTE OR RESELL THE MATERIALS, OR PROVIDE THE MATERIALS FOR FREE TO CUSTOMERS OR CLIENTS, OR PLACE THE MATERIALS FOR DOWNLOAD ON A WEBSITE. ADDITIONALLY, WHEN USING FGDL DATA OR SOFTWARE IN PROJECTS, MAPS, ETC.; YOU AGREE TO ACKNOWLEDGE THE FGDL AS A DATA SOURCE. THE MATERIALS ARE PROVIDED 'AS IS'. THE UNIVERSITY OF FLORIDA GEOPLAN CENTER MAKES NO REPRESENTATIONS OR WARRANTIES ABOUT THE QUALITY OR SUITABILITY OF THE MATERIALS, EITHER EXPRESSLY OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR NON-INFRINGEMENT. THE UNIVERSITY OF FLORIDA GEOPLAN CENTER MAKES NO WARRANTIES, GUARANTIES OR REPRESENTATIONS AS TO THE TRUTH, ACCURACY OR COMPLETENESS OF THE DATA PROVIDED BY THE FGDL CONTRIBUTING ORGANIZATIONS. THE UNIVERSITY OF FLORIDA GEOPLAN CENTER SHALL NOT BE LIABLE FOR ANY DAMAGES SUFFERED AS A RESULT OF USING, MODIFYING, CONTRIBUTING OR DISTRIBUTING THE MATERIALS.

Standard_Order_Process:

Digital_Form:

Digital_Transfer_Information:

Format_Name: ArcGIS Geodatabase

Format_Version_Number: 8.3

File_Decompression_Technique: tar and uncompress

Transfer_Size: 0.060

Technical_Prerequisites:

This data is intended for use with a Geographic Information Systems or Remote Sensing software package.

Metadata_Reference_Information:

Metadata_Date: 20070924

Metadata_Contact:

Contact_Information:

Contact_Organization_Primary:

Contact_Organization: Florida Department of Environmental Protection

Contact_Person: David S. Anderson

Contact_Position: NHD Coordinator

Contact_Address:

Address_Type: mailing address

Address: 3900 Commonwealth Boulevard M.S. 49

City: Tallahassee

State_or_Province: FL

Postal_Code: 32399

Country: USA

Contact_Voice_Telephone: (850) 245-8550

Contact_Voice_Telephone: 1 888 275 8747

Contact_Electronic_Mail_Address: David.S.Anderson@dep.state.fl.us

Metadata_Standard_Name: FGDC Content Standards for Digital Geospatial Metadata

Metadata_Standard_Version: FGDC-STD-001-1998

Metadata_Time_Convention: local time

Metadata_Extensions:

Online_Linkage: <http://www.esri.com/metadata/esriprof80.html>

Profile_Name: ESRI Metadata Profile

Metadata_Extensions:

Online_Linkage: <http://www.esri.com/metadata/esriprof80.html>

Profile_Name: ESRI Metadata Profile