FLORIDA GEOGRAPHIC DATA LIBRARY DOCUMENTATION

TITLE: NATIONAL HYDROGRAPHY DATASET - LINEAR HYDROGRAPHIC LANDMARKS 1:100K - NOVEMBER 2011

Geodataset Name:       NHD100LINE_NOV11
Geodataset Type:       SHAPEFILE
Geodataset Feature:    Polyline
Feature Count:         454
GENERAL DESCRIPTION:
This data set contains routes representing linear NHD hydrographic landmark features that are not core to the network. 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. Medium resolution NHD is based on the content of the U.S. Geological Survey (USGS) 1:100,000-scale Digital Line Graph (DLG) hydrography data, integrated with reach-related information from the U.S. Environmental Protection Agency Reach File Version 3.0 (RF3). The FDEP is the NHD data steward for Florida. When received from FDEP, 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.
DATA SOURCE(S):                    U.S. Geological Survey, U.S. Environmental Protection Agency, USDA Forest Service, Florida Department of Environmental Protection
SCALE OF ORIGINAL SOURCE MAPS:     24000
GEODATASET EXTENT:                 State of Florida
PUBLICATION DATE: 20100506 TIME PERIOD OF CONTENT: Begin Date: 19990623 End Date: 20111109 DOWNLOAD LINK: http://www.fgdl.org/metadataexplorer/explorer.jsp

FEATURE ATTRIBUTE TABLES:

Datafile Name: NHD100LINE_NOV11.DBF
ITEM NAME WIDTH TYPE
OBJECTID
4 OID
Shape
4 Geometry
ComID
4 Integer
Permanent_
40 String
FDate
36 Date
Resolution
4 Integer
GNIS_ID
10 String
GNIS_Name
65 String
LengthKM
8 Double
FType
4 Integer
FCode
4 Integer
ThinnerCod
2 SmallInteger
FCODE_DESC
125 String
DESCRIPT
30 String
FGDLAQDATE
36 Date
AUTOID
4 Integer
SHAPE.LEN
0 Double

FEATURE ATTRIBUTE TABLES CODES AND VALUES:

Item
Item Description
OBJECTID Internal feature number.

Shape Feature geometry.

ComID Uniquely identifies the occurrence of each feature

Permanent_ 40-char GUID value that uniquely identifies the occurrence of each feature in The National Map.

FDate Date of last feature modification

Resolution Resolution Code for source resolution
1 = Local

2 = High Resolution

3 = Medium Resolution


GNIS_ID Unique identifier assigned by GNIS

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

LengthKM Length of linear feature Albers Equal Area

FType Three digit integer value unique identifier of a feature type. For a text description of each value see the DESCRIPT field.

FCode Five-digit integer value comprised of the feature type and combinations of characteristics and values. For a text description see FCODE_DESC

ThinnerCod Ordinal value designed to allow selection of progressively more dense networks. Least dense network=1.

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

DESCRIPT Description field, which holds a character string that contains all characteristics and values associated with a feature code.
Area to be Submerged = Known extent of the intended lake that will be created behind a dam under construction.

Bay/Inlet = Water area that is an opening of the sea/ocean into the land, or of an estuary, lake, or river into its shore.

Bridge = Structure spanning and providing passage over a waterway, railroad, or other obstacle.

Canal/Ditch = Artificial open waterway constructed to transport water, to irrigate or drain land, to connect two or more bodies of water, or to serve as a waterway for watercraft.

Dam/Weir = Barrier constructed to control the flow or raise the level of water.

Flume = Open, inclined, artificial channel constructed of wood, metal, or concrete; generally elevated.

Foreshore = Part of a seashore between high-water and low-water marks.

Hazard Zone = Area identified as a danger to maritime navigation.

Lock Chamber = Enclosure on a waterway used to raise/lower vessels as they pass from one level to another.

Inundation Area = Area of land subject to flooding.

Rapids = Area of swift current in a stream or river, characterized by standing waves or by boulders and rocks.

Sea/Ocean = Great body of salt water that covers much of the earth.

Special Use Zone = Area where distinctive types of maritime activities occur.

Spillway = Constructed passage for surplus water to run over or around a dam.

Stream/River = Body of flowing water.

Submerged Stream = Old river course inundated by an impounded water body.

Wash = Usually dry portion of a stream bed that contains water only during or after a local rainstorm or heavy snowmelt.

Water Intake/Outflow = Structure through which water enters or exits a conduit.

Area of Complex Channels = Area where a stream or river flows in an intricate network of interlacing channels.


FGDLAQDATE Date GeoPlan acquired data from source.

AUTOID Unique ID added by GeoPlan

SHAPE.LEN Length in meters


USER NOTES:
Points, nodes, lines, and areas conform to topological rules.  Lines intersect only at 
nodes, and all nodes anchor the ends of lines.  Lines do not overshoot or 
undershoot other lines where they are supposed to meet.  There are no duplicate 
lines.  Lines bound areas and lines identify the areas to the left and right of the lines. 
Gaps and overlaps among areas do not exist.  All areas close.
The completeness of the data reflects the content of the sources, which 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.
GeoPlan relied on the integrity of the attribute information within
the original data.
In May, 2011, the existing Florida NHD100K, NHD 24K as downloaded May 2, 
2011 from the USGS NHD, Hydrologic Units, GNIS alternate names and 
relationships were combined into one file geodatabase for public distribution and 
use.  Notable changes to the database since the previous download in December 
2010 are as follows:  Full photo revision to Lower Suwannee (03110205) and 
Apalachee Bay-St. Marks (03120001) sub basins; Partial photo revision to 
Withlacoochee (03100208) and Lower Suwannee (03110205) sub basins; Removal 
of duplicate features within Myakka (03100102) sub basin; Database maintenance 
was performed on Oklawaha (03080102), Choctawhatchee Bay (03140102), Cape 
Canaveral (03080202), Lower Choctawhatchee (03140203), Pea (03140202), 
Yellow (03140103), Escambia (03140305), St Marys (03070204), Nassau 
(03070205), Kissimmee (03090101), Big Cypress Swamp (03090204), 
Caloosahatchee (03090205), Florida Southeast Coast (03090206), Myakka 
(03100102), Manatee (03100202), Little Manatee (03100203), Hillsborough 
(03100205), Aucilla (03110103), Alapaha (03110202), Lower Suwannee 
(03110205), Apalachee Bay-St. Marks (03120001), Lower Ochlockonee 
(03120003), Chipola (03130012), New (03130013), Apalachicola Bay (03130014), 
St. Andrews-St. Joseph Bays (03140101), Perdido (03140106) and Perdido Bay 
(03140107) sub basins. Database maintenance may include some photo revision, 
however its focus is on correcting topology, feature attribute and network errors.

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.

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.

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.

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

The Florida Geographic Data Library is a collection of Geospatial Data
compiled by the University of Florida GeoPlan Center with support from
the Florida Department of Transportation. GIS data available in FGDL is
collected from various state, federal, and other agencies (data sources)
who are data stewards, producers, or publishers. The data available in
FGDL may not be the most current version of the data offered by the
data source. University of Florida GeoPlan Center makes no guarantees
about the currentness of the data and suggests that data users check
with the data source to see if more recent versions of the data exist.

Furthermore, the GIS data available in the FGDL are provided 'as is'.
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 data sources. 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
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

REFERENCES:
http://nhd.usgs.gov/

http://nhd.usgs.gov/NHDv2.0_poster_6_2_2010.pdf

http://www.dep.state.fl.us/water/watersheds/nhd-about.htm

DATA LINEAGE SUMMARY:
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

In May 2010, the existing NHD 100k, NHD 24K as downloaded in March 2010, Hydrologic Units (subbasins only), GNIS alternate names and relationships were combined into one file geodatabase for public distribution and use. Process Date: 05/06/2010
An extraction from the national NHD of just the features associated with the State of Florida was performed and the result database was stored in a staging area for use by the Florida NHD Stewardship team and other interested parties. Process Date: 03/18/2010
GeoPlan Center downloaded the NHD GeoDatabase from the Florida Department of Environmental Protection in November 2011. The data was exported to shapefile and defined with the FGDL Albers projection file. This data was originally produced by U.S. Geological Survey in cooperation with U.S. Environmental Protection Agency, USDA Forest Service, and other Federal, State and local partners. The Florida Data Stewards (FDEP) then update the data. The original metadata from USGS is used with the original publication date, however, the time period of content has been changed to the last update made by FDEP. The following poster was used to populate FCODE field with its associated description: http://nhd.usgs.gov/NHDv2.0_poster_6_2_2010.pdf Upcased all fields FCODE_DESC field added and calculated based on description. DESCRITP field added based on FTYPE description FGDLAQDATE added based on date downloaded from source Renamed GDB feature class from NH Line to nhd100line_apr11.shp Process Date: 20120309
MAP PROJECTION PARAMETERS:

Projection                          ALBERS
Datum                               HPGN
Units                               METERS
Spheroid                            GRS1980
1st Standard Parallel               24  0  0.000
2nd Standard Parallel               31 30  0.000
Central Meridian                   -84 00  0.000
Latitude of Projection's Origin     24  0  0.000
False Easting (meters)              400000.00000
False Northing (meters)             0.00000

DATA SOURCE CONTACT (S):

Name:
Abbr. Name:
Address:


Phone:

Web site:
E-mail:
Contact Person:
         Phone:
        E-mail:
Florida Department of Environmental Protection (FDEP) OTIS/GIS Section
USGS
2600 Blair Stone Rd, MS 6520
Tallahassee, FL
32399-2400


http://www.dep.state.fl.us/gis/ GIS.Librarian@dep.state.fl.us

FGDL CONTACT:
Name:                   FLORIDA GEOGRAPHIC DATA LIBRARY
Abbr. Name:             FGDL
Address:                Florida Geographic Data Library
                        431 Architecture Building
                        PO Box 115706
                        Gainesville, FL  32611-5706
Web site:               http://www.fgdl.org

Contact FGDL: 

      Technical Support:	        http://www.fgdl.org/fgdlfeed.html
      FGDL Frequently Asked Questions:  http://www.fgdl.org/fgdlfaq.html
      FGDL Mailing Lists:		http://www.fgdl.org/fgdl-l.html
      For FGDL Software:                http://www.fgdl.org/software.html