Geodataset Name:       NHD24POINT_OCT14
Geodataset Type:       SHAPEFILE
Geodataset Feature:    Point
Feature Count:         1358

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:                  20141022
TIME PERIOD OF CONTENT:            Begin Date: 19990623    End Date: 20141022
DOWNLOAD LINK:                     http://www.fgdl.org/metadataexplorer/explorer.jsp

FEATURE ATTRIBUTE TABLES:

Datafile Name: NHD24POINT_OCT14.DBF

FEATURE ATTRIBUTE TABLES CODES AND VALUES:

Item	Item Description
OBJECTID	Internal feature number.
Shape	Feature geometry.
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
ReachCode	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
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
FCODE_DESC	FCODE description field, which holds a character string that contains all characteristics and values associated with a feature code.
DESCRIPT	GeoPlan added field based on FTYPE. Contains text description of feature type. Gaging Station = Structure used to measure the characteristics of a hydrographic feature. Gate = Structure that may be swung, drawn, or lowered to block an entrance or passageway. Lock Chamber = Enclosure on a waterway used to raise/lower vessels as they pass from one level to another. Rapids = Area of swift current in a stream or river, characterized by standing waves or by boulders and rocks. Reservoir = Constructed basin formed to contain water or other liquids. Rock = Concreted mass of stony material. Sink/Rise = Place at which a stream disappears underground or reappears at the surface in a karst area. Spring/Seep = Place where water issues from the ground naturally. Water Intake/Outflow = Structure through which water enters or exits a conduit. Waterfall = Vertical or near vertical descent of water over a step or ledge in the bed of a river. Well = Pit or hole dug or bored into the earth for the extraction of oil, water, other fluids, or gases.
FGDLAQDATE	Date GeoPlan acquired data from source.
AUTOID	Unique ID added by GeoPlan

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.

Attribute accuracy report: 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.

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/NHD.pdf http://www.dep.state.fl.us/water/watersheds/nhd-about.htm

DATA LINEAGE SUMMARY:

Process description: In June 2013, the existing Florida NHD100K and NHD 24K as downloaded April 10, 2013 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 24K NHD database since the previous download in December 2012 are as follows: Full photo revision to Lake Okeechobee (03090201), Hillsborough (03100205) and Alafia (03100204) sub basins; Full photo revision to portions of Peace (03100101), Withlacoochee (03100208), Choctawatchee Bay (03140102), miscellaneous updates in Big Cypress Swamp (03090204) and Everglades (03090202); miscellaneous edits/additions of stream gages, dams and other point event features by USGS. The database includes a network using the NHD24 NHDFlowline featureclass. The Utility Network Analyst tool can be used to trace routes through the network, however please note that if you set the results of the trace as selected features and zoom to selected, you may zoom to a scale that is outside the NHD24 dependency settings. Process Date: 20130601 Process description: Data updated in ArcSDE/DataMiner and MapDirect. Metadata updated. Process Date: 20130824 Process description: In November 2013, the existing Florida NHD100K and NHD 24K as downloaded November 12, 2013 from the USGS NHD, Hydrologic Units, GNIS alternate names and relationships were combined into one file geodatabase for public distribution and use. Notable edits in the 24K NHD database since the previous download in April 2012 were in the following subbasins: Withlacoochee (03100208), Peace (03100101), Upper St. Johns (03080101), Kissimmee(03090101), Florida Southeast Coast (03090206), Choctawhatchee Bay (03140102), Lower Choctawhatchee (03140203) and assorted network improvements made by USGS staff. Process Date: 20131101 Process description: Data updated in ArcSDE/DataMiner and MapDirect. Metadata updated. Process Date: 20131208 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: 20140512 Process description: In May 2014, the existing Florida NHD100K and NHD 24K as downloaded May 12, 2014 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 24K NHD database since the previous download in November 2013 are as follows: Aerial imagery revision to priority WBIDs ( Waterbody IDs provided by DEP Water Assessment Section), other WBIDs and network improvements by USGS to Tampa Bay (03100206), Crystal-Pithlachascotee (03100207), Withlacoochee (03110203), Charlotte Harbor (03100103), St. Andrew-St. Joseph Bays (03140101), Vero Beach (03080203), Everglades(03090202), Blackwater (03140104), Manatee (03100202), Econfina-Steinhatchee (03110102), Caloosahatchee (03090205), Perdido (03140106), Florida Southeast Coast (03090206), Lake Okeechobee (03090201), Cumberland-St. Simons (03070203),Santa Fe (03110206), Alapaha (03110202), Aucilla (03110103), Lower Ochlockonee (03120003), Cape Canaveral (03080202), Nassau (03070205), Upper Suwannee (03110201), Myakka (03100102), Chipola (03130012), Pensacola Bay (03140105),Upper St. Johns (03080101), Lower St. Johns (03080103), Oklawaha (03080102), Little Manatee (03100203), Waccasassa (03110101), Apalachee Bay-St. Marks (03120001), Western Okeechobee Inflow (03090103), Northern Okeechobee Inflow(03090102), St. Mary's (03070204), Daytona-St. Augustine (03080201), Kissimmee (03090101), Lower Suwannee (03110205), Big Cypress Swamp (03090204), Peace (03100101), Yellow (03140103), . The database includes a network using the NHD24NHDFlowline featureclass. The Utility Network Analyst tool can be used to trace routes through the network, however please note that if you set the results of the trace as selected features and zoom to selected, you may zoom to a scale that is outside the NHD24 dependency settings. Process Date: 20140512 Process description: In October 2014, the existing Florida NHD100K and NHD 24K as downloaded October 22, 2014 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 24K NHD database since the previous download in May 2014 are as follows: Geographic Information Names System (GNIS) specific updates, aerial imagery based updates to prioritized Florida DEP Waterbody IDs (WBIDs), and/or additional aerial imagery based updates to St. Mary's (3070204), Nassau (3070205), Upper St. Johns (3080101), Lower St. Johns (3080103), Daytona-St. Augustine (3080201), Cape Canaveral(3080202), Vero Beach (3080203), Kissimmee (3090101), Big Cypress Swamp (3090204), Caloosahatchee (3090205), Florida Southeast Coast (3090206), Crystal-Pithlachascotee (3100207), Econfina-Steinhatchee (3110102), Aucilla (3110103),Apalachee Bay-St. Marks (3120001), Lower Ochlockonee (3120003), Apalachicola (3130011), New (3130013), Apalachicola Bay (3130014), St. Andrew-St. Josephs Bays (3140101), Choctawhatchee Bay (3140102), Yellow (3140103), Blackwater(3140104), Pensacola Bay (3140105), Perdido (3140106), Perdido Bay (3140107), Lower Choctawhatchee (3140203) and Escambia (3140305) sub basins. Process Date: 20141022 Process description: An October 22, 2014 copy of the Florida NHD was obtained from the USGS for purposes of updating the Florida Dept. of Environmental Protection Agencies SDE data. For this release, a new field called Parent_Feature was added to the NHDFlowline featureclass. Using Field Calculator, the Parent_Feature attribute for flowline features with FType not equal to Artificial Path were updated to the FType. For artificial pathflowlines, a series of analyses using the relationship between the WBArea_Permanent_identifier field and the Permanent_identifier fields of each of the NHDArea and NHDWaterbody featureclasses facilitated the update of the Parent_Feature attribute. Several ?select by location analyses further provided updated to the ?Parent_Feature. Several hundred artificial paths remained after exhausting multiple analysis options and were ultimately individually inspected to see the relationship between the artificial path and the feature for which it was within. Process Date: 20141201 Process description: Changes in the October 2014 download of the Florida NHD include new and updated NHD Point Events. These EventTypes follow the same format as the FCodes in the other featureclasses. Added detail has been incorporated for stream gages. Stream gages are now listed as being active (with continuous or partial data) or inactive. Dams are still included, but like the others, the code has changed. Past layer files referencing the NHDPointEvents featureclass will need updated symbology to link to the new codes. The layer file used on the FDEP DataMiner application has been updated to reflect the updates. New codes are as follows: 57001 - Stream Gage, Active, Continuous data; 57002 - Stream Gage, Active, Partial data; 57003 - Stream Gage, Inactive; 57100 - Dam. Process Date: 20141208 Process description: Data updated in the GIS library Process Date: 20150107 GeoPlan Center downloaded the NHD GeoDatabase from the Florida Department of Environmental Protection in February 2015. 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 following poster was used to populate FCODE and FTYPE fields with their associated description: http://nhd.usgs.gov/NHD.pdf FCODE_DESC field added and calculated based on description. DESCRIPT field added based on FTYPE description FGDLAQDATE added based on date downloaded from source Renamed GDB feature class from NHDPoint to nhd24point_oct14.shp Process Date: 20150306

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
FDEP
2600 Blair Stone Rd, MS 6520
Tallahassee, FL
32399-2400



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

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