FLORIDA GEOGRAPHIC DATA LIBRARY DOCUMENTATION TITLE: SUBWATERSHED - 12-DIGIT HYDROLOGIC UNIT BOUNDARIES FOR FLORIDA - DECEMBER 2017 Geodataset Name: NHDWBD_HUC12_DEC17 Geodataset Type: SHAPEFILE Geodataset Feature: Polygon Feature Count: 1686 |
|
GENERAL DESCRIPTION:
|
|
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: Unknown GEODATASET EXTENT: State of Florida |
FEATURE ATTRIBUTE TABLES:
Datafile Name: NHDWBD_HUC12_DEC17.DBF
ITEM NAME | WIDTH | TYPE |
OBJECTID
|
4 | OID |
SHAPE
|
4 | Geometry |
TNMID
|
40 | String |
METASOURCE
|
40 | String |
SOURCEDATA
|
100 | String |
SOURCEORIG
|
130 | String |
SOURCEFEAT
|
40 | String |
LOADDATE
|
36 | Date |
GNIS_ID
|
8 | Double |
AREAACRES
|
8 | Double |
AREASQKM
|
8 | Double |
STATES
|
50 | String |
HUC12
|
12 | String |
NAME
|
120 | String |
HUTYPE
|
254 | String |
HUMOD
|
30 | String |
TOHUC
|
16 | String |
NONCON_AC
|
8 | Double |
NONCON_KM
|
8 | Double |
HUTYPE_DSC
|
20 | String |
DESCRIPT
|
120 | String |
FGDLAQDATE
|
36 | Date |
AUTOID
|
4 | Integer |
SHAPE.AREA
|
0 | Double |
SHAPE.LEN
|
0 | Double |
FEATURE ATTRIBUTE TABLES CODES AND VALUES:
Item | Item Description | |
OBJECTID |
Internal feature number. |
|
SHAPE |
Feature geometry. |
|
TNMID |
(short for The National Map Identification) is a unique 40-character field that identifies each element in the database exclusively. TNMID is an automatically assigned code that stays with each element. When an element is updated or changed, TNMID links the element to the metadata record and documents the change. TNMID is also used to maintain relationship classes in the normalized data model. When an element is deleted or split, TNMID stays with the original element and is not used again. When an element is split, new permanent identifiers are assigned to the resultant parts. |
|
METASOURCE |
Unique identifier that links the element to the metadata tables. This ID is generated and assigned automatically by the database and remains with the object permanently. |
|
SOURCEDATA |
A space provided for a brief description of the type of base data used to update or change the current WBD. The WBD In-State Steward completes this field as part of the metadata form |
|
SOURCEORIG |
The description of the agency that created the base data used to improve the WBD. The WBD In-State Steward completes this field as part of the metadata form. |
|
SOURCEFEAT |
Like TNMID, SourceFeatureID is a long, unique code. This code identifies the parent of the feature if the feature is the result of a split or merge, and it is automatically generated and assigned |
|
LOADDATE |
Represents the date when the data were loaded into the official USGS WBD ArcSDE database. The field is the effective date for all feature edits, and it is automatically generated. |
|
GNIS_ID |
Preassigned numeric field that uses a unique number to relate the name of the hydrologic unit to the GNIS names database. This field is automatically generated in the database. |
|
AREAACRES |
Common to all polygon feature classes and is calculated at the 12-digit hydrologic unit from the intrinsic area value maintained by the GIS software; therefore, acreage values may vary from user calculations, depending on the projection of the data. North American Albers Equal Area Conic, North American Datum 1983 is the required projection to use for calculation. If the units of the area field are stored in square meters, then use the conversion factor 0.0002471. For example, 40,469,446 square meters multiplied by 0.0002471 = 10,000 acres. |
|
AREASQKM |
Calculated at the 12-digit hydrologic unit from the intrinsic area value maintained by the GIS software; therefore, the square kilometer values may vary from user calculations, depending on the projection of the data. North American Albers Equal Area Conic, North American Datum 1983 is the default projection. |
|
STATES |
The States or outlying area attribute identifies the State(s) or outlying areas that the hydrologic unit falls within or touches. The U.S. Census Bureau 1:100,000-scale State layer will be used to establish State boundaries in the derivation process. The two-letter U.S. Postal Service State abbreviation is assigned. If a hydrologic unit crosses into Canada, the two- letter Canada Post abbreviation for the Province is used. If a unit crosses into Mexico, the MX designation is used. If more than one abbreviation is used, they are separated by commas, without spaces, and are sorted in alphabetical order. This field is populated by the In-State Steward at the 12-digit hydrologic unit |
|
HUC12 |
The HUC12 field is a unique 12-digit hydrologic unit code. |
|
NAME |
The 16-digit hydrologic unit name refers to the GNIS name for the geographic area in which the hydrologic unit is located |
|
HUTYPE |
The 10-digit hydrologic unit type attribute is the single- letter abbreviation for Watershed type from the list of official names provided below. Use the single type that most closely describes the 10-digit hydrologic unit (see coastal examples in fig. 10).
|
|
HUMOD |
The 10-digit hydrologic unit modification attribute is a two-character, uppercase abbreviation(s) for either (1) the type of modification to natural overland flow that alters the natural delineation of a 10-digit hydrologic unit or (2) the special conditions GF-groundwater flow, GL-glacier, IF-ice field, KA- karst, and NC-noncontributing area. The value of the HUMod field helps to indicate where the modification to the 10-digit hydrologic unit is located. If more than one abbreviation is used, then separate them by commas without spaces and list them from most to least predominant. There are future plans to derive this field at the 10-digit unit from the information on the HUMod from the lines and the HUMod at the 12-digit unit upon check in. Once that process is in place the content will be overwritten. Previous versions of this guideline did not provide the same number of modification choices check metadata or contact the principal WBD In-State Steward for more information.
|
|
TOHUC |
The 12-digit hydrologic unit ToHUC code attribute is the code for the 12-digit hydrologic unit that is downstream from and naturally receives the majority of the flow from another 12-digit hydrologic unit. For special cases when a downstream code cannot be assigned, identify which of these exceptions applies: If a hydrologic unit flows into an ocean or the Gulf of Mexico, then populate this field with the value OCEAN. If a hydrologic unit drains into either Canada or Mexico, then use the appropriate value CANADA or MEXICO. If a hydrologic unit is a closed basin, then populate this field with the value CLOSED BASIN. |
|
NONCON_AC |
The noncontributing area attribute represents the area, in acres, of hydrologic units that do not contribute to downstream accumulation of streamflow under normal flow conditions (section 3.5.3). If a noncontributing area is on the boundary between two or more hydrologic units, then determine the low point along the noncontributing area boundary, and associate the noncontributing area with the hydrologic unit adjacent to the low point on the boundary. The value is the total acreage of the noncontributing areas within a hydrologic unit. North American Albers Equal Area Conic, North American Datum 1983 is the required projection to use for calculation. If the units of the area field are stored in square meters, then use the conversion factor 0.0002471. |
|
NONCON_KM |
The noncontributing area attribute represents the area, in square kilometers, of hydrologic units that do not contribute to downstream accumulation of streamflow under normal flow conditions (section 3.5.3). If a noncontributing area is on the boundary between two or more hydrologic units, then determine the low point along the noncontributing area boundary, and associate the noncontributing area with the hydrologic unit adjacent to the low point on the boundary. The value is the total square kilometers of the noncontributing areas within a hydrologic unit. North American Albers Equal Area Conic, North American Datum 1983 is the required projection to use for calculation. If the units of the area field are stored in square meters, then use the conversion factor 0.0002471 |
|
HUTYPE_DSC |
Description based on HUTYPE field. See HUTYPE for more information. |
|
DESCRIPT |
GeoPlan added field based on NAME |
|
FGDLAQDATE |
Date GeoPlan acquired from source. |
|
AUTOID |
Unique ID added by GeoPlan |
|
SHAPE.AREA |
Area in meters |
|
SHAPE.LEN |
Perimeter in meters |
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. |
|
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 |
|
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 |
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 n/a |
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