Identification_Information: Citation: Citation_Information: Originator: McFadden, Keith W. Publication_Date: 1/30/2003 Title: HU12_polygon Edition: Version 3.0 Geospatial_Data_Presentation_Form: vector digital data Publication_Information: Publisher: U.S. Geological Survey Other_Citation_Details: U.S. Geological Survey and U.S. Department of Agriculture, Natural Resources Conservation Service, 2009, Federal guidelines, requirements, and procedures for the national Watershed Boundary Dataset: U.S. Geological Survey Techniques and Methods 11-A3, 55 p. Online_Linkage: http://datagateway.nrcs.usda.gov/ Description: Abstract: This derivitive data set is a digital map of the 12-digit hydrologic unit boundaries for Georgia and parts of Alabama, South Carolina, North Carolina, Florida, and Tennessee. The boundaries were delineated on 1:24,000 7.5 minute USGS topographic quadrangles which were scanned into a digital image and vectorized interactively on a computer graphic display. The hydrologic unit polygons are tagged with the appropriate 8, 10, and 12 digit codes. (Release 2.0, June 2001) Purpose: A watershed approach to investigations and management of water resources requires mapping of appropriate level hydrologic unit boundaries. The purpose of the hydrologic unit coverage is to provide an accurate, standardized GIS coverage of watershed boundaries through the fifth and sixth (10 and 12 digit) hydrologic unit scale using nationally accepted, consistent methods. Supplemental_Information: Procedures_Used: NOTE: Beginning in Feb. 1999 with the Coosa/Tallapossa basins, all scanning, digitizing, and attribute assignments were transfered to the USGS Center for Spatial Analysis Technologies (CSAT). Methods and procedures remained essentially the same. METHODS FOR SELECTION AND DELINEATION OF HYDROLOGIC UNIT BOUNDARIES Methods for the selection, delineation, and mapping of Hydrologic Unit areas are described by Seaber and others (1987), Landers (1997), the NRCS (1995, draft), and an unfinished guideline being produced by the Federal Geographic Data Committee (FGDC). The most interpretive aspect of hydrologic unit mapping is the selection of watersheds and their downstream outlets for definition as official hydrologic units. Criteria for these selections in Georgia are described in Landers (1997). These criteria agree with the FGDC guidelines, and with the NRCS Guidelines (where applicable). Selected hydrologic units were reviewed for consensus by the Georgia Interagency Hydrologic Unit Group in 1996. The selected fourth, fifth, and sixth (8-, 10-, and 12-digit, respectively) hydrologic units were delineated on clean, unfolded, paper 1:24,000 scale USGS topographic quadrangle maps by experienced personnel. Each line was checked and color coded on each map by an experienced hydrologist. The initials of the delineator and checker are on each quad map, and on a quality assurance review sheet. The line work of the digital GIS coverage created from the quad maps was reviewed by two lead hydrologists (Mark Landers and Roger McFarlane) of the Georgia District office, and hydrologic unit codes were assigned to each basin. Revisions to line work from this review, and the correct attribution of HU codes for each polygon were also checked. The original paper quad maps are currently stored in the USGS, Georgia District office. METHOD OF SCANNING PAPER QUADRANGLE MAPS Paper 1:24,000 7.5 minute USGS topographic quadrangle maps were received from the Georgia and Alabama District offices. The maps were unrolled, portions unfolded, and placed on a flat surface for several days to acclimate. Each map was scanned into a digital TIF image on a PC based scanning system utilizing a Contex FSS 3012t Full Scale Scanner. The maps were scanned in 256 shade grayscale at 150 dpi. Each TIF image was given a name created from the state abbreviation and delineation project quad number. The TIF images were transferred via FTP to a Silicon Graphics Indy workstation running Arc/Info 7.1.1. METHOD OF GEO-REFERENCING SCANNED QUADRANGLE MAPS Each image was geo-referenced to a decimal degree coordinate system using the REGISTER command of Arc/Info 7.1.1. The latitiude and longitude of the four corners of the quadrangles were used as the reference points. The transformation RMS error for each quadrangle was recorded and tabulated in the .RMS database file, which is included as a dataset table. After all quadrangles were registered, the RMS errors were summed and averaged, and any quadrangles with a higher than average RMS error were reregistered. The registered TIF images were transformed and the collar information clipped by the RECTIFY command using the quadrangle boundary as a clipping box. This allowed the images to be seamlessly displayed on the computer screen for easier digitizing and minimizing the error in lines crossing quadrangle boundaries. METHOD OF VECTORIZING DELINEATED BOUNDARIES FROM SCANNED MAPS The geo-referenced images were divided into 11 groups based on the name of the image. A group of images was assigned to a qualified GIS operator for vectorization. Each image was loaded into the ArcView 3.0a software on a PC-based, Data General, or Silicon Graphics system for vectorization. The image was displayed on the screen at a scale of 1:12,000 as a background for interactive digitizing of the delineated boundaries. Lines were digitized with enough vertices to represent the delineated boundaries with a minimal visual deviation while staying within the required time frame for completion. The digital linework for each quad was saved as an ArcView shapefile in a central storage location. METHOD OF FINAL COVERAGE CREATION The individual ArcView shapefiles were imported into ArcInfo 7.1.1 coverages through the SHAPEARC command. All coverages were appended together to create a single Arc/Info coverage. The scanned images were displayed in ArcEdit as the background with the coverage as the edit coverage. The display was set to the extent of each of the scanned quadrangles and the coverage linework was checked for completion and accuracy. Lines found to be unacceptable or incomplete through a visual inspection, were redigitized. Special attention was given to those lines which crossed quadrangle boundaries and corrections made to those lines if needed. Dangling lines were corrected to form closed polygons. The coverage was then UNSPLIT to remove excessive pseudo-nodes and built as a polygon coverage. Polygons were checked for closure and corrected as needed. Lines were assigned a number, HUCLINE, to tag them as being 8, 10, or 12 digit hydrologic boundaries. Polygons were assigned a 12-digit number, HUC, according to the 1:250,000 paper plots of ennumerated hydrologic units as supplied by the Georgia District office. Three region feature layers, HUC8, HUC10, and HUC12, were created by using the REGIONDISSOLVE command on the polygon layer with HUC as the grouping item. The region layers, HUC8, HUC10, and HUC12, represent the areas defined as 8-digit, 10-digit, and 12-digit hydrologic units. Attributes were added to the polygon and region layers to aid in selecting, identifying, and displaying hydrologic units based on various permutations of the hydrologic unit code. Revisions: Several interim versions were passed between the Georgia and Tennessee District offices. Those versions were not distributed outside of the two offices. pre 01/14/98 - Several versions of the linework only were sent to the Georgia office for review and correction summaries 01/14/98 - Imported the Florida linework into the coverage 01/15/98 - First version with closed polygons 01/22/98 - First version with tagged polygons and regions 01/23/98 - First version with tagged attributes sent to Georgia for inital review and correction summary 02/18/98 - Minor corrections were made to the linework and polygons Coverage was sent to Georgia for review 03/02/98 - Several unneeded outlying arcs were deleted from and documentation was rewritten. 03/03/98 - Documentation updated. Coverage exported and sent to Georgia for colleague review 03/30/98 - Completed Ga. District colleague review. Updated documentation. 05/19/98 - Added name attribute columns. Revised title and coverage name. 09/30/98 - Combined Chattahoochee/Flint, and Oconee basins. Added .LUT table for Basin names, and removed name fields from attribute tables. 07/20/99 - Data for Coosa/Tallapoosa basins digitized at CSAT and merged with existing basins. Regions re-built and additional names added to LUT. 09/01/99 - Savannah and Ogechee basins digitized at CSAT merged into exist basins. Regions re-built and attributes added. 12/27/99 - Added in South Ga. basins between Flint and St. Marys basins. Some minor topological corrections made, all ID's renumbered, removed sliver polygons, rebuilt regions. 6/1/2000 - Final data for Tennesee basins added. Some corrections made to basins along Florida border and in area of Fl.,Ga, and Al. 6/1/2001 - Release of version 2.0. Incorporates changes to basins made along Ga-Fla. border as well as changes to line attributes. 11/14/01 - Updated missing basin names and attribute codes on Ga-Fla. border. 2/8/02 - Updated attribute data to meet NRCS and Federal Standards. 1/30/03 - Removed Region topology, combined 10 & 12 digit attributes to .PAT Reviews_Applied_to_Data: The selection of watersheds for definition as hydrologic units was reviewed by State of Georgia, Environmental Protection Division and the Georgia Interagency Hydrologic Unit Group. Each quad map delineation was checked by USGS personnel. The digital line work was checked by personnel of the USGS Tennesse District and Georgia District. Final colleague review was conducted by Keith McFadden and Jack Alhadeff (USGS), and Tom Mettille (Ga. GIS Data Clearinghouse). Related_Spatial_and_Tabular_Data_Sets: - Other_References_Cited: Landers, Mark N., 1997, Hydrologic unit mapping in Georgia: Proceedings of the 1997 Georgia Water Resources Conference, pp. 70-72 Natural Resources Conservation Service, 1995, DRAFT National Instruction 170-304: 'Mapping and digitizing watershed and subwatershed hydrologic unit boundaries' Seaber, P.R., Kapinos, F.P., and Knapp, G.L., 1987, Hydrologic Unit Maps: U.S. Geological Survey Water Supply Paper 2294, 63 pgs. U.S. Geological Survey, 1975, Hydrologic unit map--1974. State of Georgia: U.S. Geological Survey, scale 1:500,000. 1 sheet. Notes: - Time_Period_of_Content: Time_Period_Information: Multiple_Dates/Times: Single_Date/Time: Calendar_Date: 6/1/2000 Single_Date/Time: Calendar_Date: 02/08/2002 Single_Date/Time: Calendar_Date: 10/01/2010 Currentness_Reference: publication date Status: Progress: Approved for release Maintenance_and_Update_Frequency: As needed Spatial_Domain: Bounding_Coordinates: West_Bounding_Coordinate: -85.376856 East_Bounding_Coordinate: -80.768063 North_Bounding_Coordinate: 35.124664 South_Bounding_Coordinate: 30.199302 Keywords: Theme: Theme_Keyword_Thesaurus: None Theme_Keyword: HUC Theme_Keyword: Hydrologic Units Theme_Keyword: Hydrologic Unit Code Theme_Keyword: Region Theme_Keyword: Sub-region Theme_Keyword: Basin Theme_Keyword: Sub-basin Theme_Keyword: Watershed Theme_Keyword: Watershed Boundaries Theme_Keyword: boundaries Theme_Keyword: Subwatershed Theme_Keyword: WBD Theme_Keyword: Watershed Boundary Dataset Place: Place_Keyword_Thesaurus: None Place_Keyword: Georgia Place_Keyword: Alabama Place_Keyword: South Carolina Place_Keyword: North Carolina Place_Keyword: Tennesee Place_Keyword: Florida Stratum: Stratum_Keyword_Thesaurus: None Stratum_Keyword: None Temporal: Temporal_Keyword_Thesaurus: None Temporal_Keyword: None Access_Constraints: None Use_Constraints: The data set depicts watershed boundaries at a detail suitable for scales of 1:24,000 or smaller. This is not the original dataset. Edits or updates should not be made to this version Point_of_Contact: Contact_Information: Contact_Organization_Primary: Contact_Organization: U.S. Geological Survey Contact_Person: Keith W. McFadden Contact_Address: Address_Type: mailing and physical address Address: 3039 Amwiler Rd. Suite 130 City: Atlanta State_or_Province: Ga. Postal_Code: 30360 Country: US Contact_Voice_Telephone: 770-903-9100 Contact_Facsimile_Telephone: 770-903-9199 Contact_Electronic_Mail_Address: keithmc@usgs.gov Hours_of_Service: 8:00am to 5:00pm M-F Data_Set_Credit: Mark Landers, Keith McFadden (USGS), and Jimmy Bramblett (NRCS) Security_Information: Security_Classification_System: None Security_Classification: Unclassified Security_Handling_Description: None Native_Data_Set_Environment: Microsoft Windows XP Version 5.1 (Build 2600) Service Pack 3; ESRI ArcCatalog 9.3.1.3500 Cross_Reference: Citation_Information: Series_Information: Publication_Information: Data_Quality_Information: Attribute_Accuracy: Attribute_Accuracy_Report: See Entity_Attribute_Information Quantitative_Attribute_Accuracy_Assessment: Attribute_Accuracy_Value: See Explanation Attribute_Accuracy_Explanation: Attribute accuracy is described, where present, with each attribute defined in the Entity and Attribute Section. Logical_Consistency_Report: There are no unclosed polygons, intersections without nodes, or polygons without labels or with more than one label. Arc/Info's topological correction program CLEAN was used to correct intersections without nodes, identify unclosed polygons and remove duplicate lines with the same beginning and ending nodes. All sliver polygons were removed either using eliminate, merge or manually in ArcEdit. Positional_Accuracy: Horizontal_Positional_Accuracy: Horizontal_Positional_Accuracy_Report: - Quantitative_Horizontal_Positional_Accuracy_Assessment: Horizontal_Positional_Accuracy_Value: 12.5 meters Horizontal_Positional_Accuracy_Explanation: Resolution as reported Vertical_Positional_Accuracy: Vertical_Positional_Accuracy_Report: - Lineage: Source_Information: Source_Citation: Citation_Information: Source_Scale_Denominator: 24000 Type_of_Source_Media: paper Source_Time_Period_of_Content: Time_Period_Information: Single_Date/Time: Source_Currentness_Reference: publication date Source_Citation_Abbreviation: USGS DRG24 Source_Contribution: Georeferenced Raster USGS Topological Map Series Source_Information: Source_Citation: Citation_Information: Originator: NOAA - Office of Coastal Survey Title: NOAA Raster Navigational Charts Geospatial_Data_Presentation_Form: raster digital data Other_Citation_Details: NOAA Raster Navigational Charts (RNC) Georgia series 06/29/2010. NOAA RNCs are geo-referenced, digital images of NOAA navigational charts. Online_Linkage: http://www.charts.noaa.gov/RNCs/RNCs.shtml Source_Scale_Denominator: 40000 Type_of_Source_Media: paper Source_Citation_Abbreviation: NOAA_RNC Source_Contribution: NOAA Raster Nautical Charts Source_Information: Source_Citation: Citation_Information: Originator: Coastal Georgia Watershed Review Team Title: Coastal Concept Lines and Attributes Geospatial_Data_Presentation_Form: vector digital data Other_Citation_Details: Coastal concept lines Cooperators: Source_Scale_Denominator: 40000 Type_of_Source_Media: paper Source_Citation_Abbreviation: GACoastalHUC12 Source_Contribution: Coastal watershed concept lines and attributes provided by the Coastal Georgia Watershed Review Team on 20091210. Source_Information: Source_Citation: Citation_Information: Originator: National Oceanic and Atmospheric Administration Publication_Date: Sept 1994 Title: Salinity Characteristics of South Atlantic Estuaries Publication_Information: Publication_Place: Silver Spring, MD Other_Citation_Details: Orlando, S.P., Jr., P.H. Wendt, C.J. Klein, M.E. Pattillo, K.C. Dennis, and G.H. Ward. 1994. Salinity Characteristics of South Atlantic Estuaries. Silver Spring, MD: National Oceanic and Atmospheric Administration, Office of Ocean Resources Conservation and Assessment. 117 pp. Source_Scale_Denominator: NA Type_of_Source_Media: paper Source_Citation_Abbreviation: Estuaries,1994 Source_Contribution: Tidal Anti-Node definition and locations of watersheds crossing estuaries. Tidal Anti-Node (Definition) - a point where the tidal wave traveling through one channel meets the wave from another causing a convergence of the flow during flood (Estuaries,1994). Process_Step: Process_Date: 20000517 Process_Time: 1505 Source_Produced_Citation_Abbreviation: None Process_Step: Process_Description: KEITHMC DOCUMENT BASINS24K UPDATE KEITHMC Source_Used_Citation_Abbreviation: None Process_Date: 20000602 Process_Time: 1448 Source_Produced_Citation_Abbreviation: None Process_Step: Process_Description: Meta_ID: GA02 / NCGC02, edit out duplicate huc12 polygons with attributes agreed upon by state office. Process_Date: 200709 Process_Step: Process_Description: Meta_ID: GA03 (Sub-Region 0315) - Updates to polygons and linework from USGS Water Science Center, Salt Lake City, Utah. Details: Watershed boundary lines adjusted to USGS DRG24. Attributes HU_12_NAME field populated, HU_10_NAME field updated to conform to National WBD and GNIS naming structure. HU_10_DS, HU_12_DS, HUC_10, and HUC_12 numeric fields updated to conform to WBD dowstream numbering order (i.e. huc must flow into higher numbered huc). Process_Date: 201001 Process_Step: Process_Description: Meta_ID: GA04 (Interior) - Updates to polygons and linework from USGS Water Science Center, Salt Lake City, Utah. Details: Watershed boundary lines adjusted to USGS DRG24. Attributes HU_12_NAME field populated, HU_10_NAME field updated to conform to National WBD and GNIS naming structure. HU_10_DS, HU_12_DS, HUC_10, and HUC_12 numeric fields updated to conform to WBD dowstream numbering order (i.e. huc must flow into higher numbered huc). Source_Used_Citation_Abbreviation: USGS 1:24000 base Process_Date: 201010 Process_Step: Process_Description: Meta_ID: GA05 (Coastal) - Updates to polygons and linework from USGS Water Science Center, Salt Lake City, Utah. Coastal Delineation Processes (Huc10 units along coastline): Input watershed boundary lines in accordance with the Coastal Georgia Watershed Review Team (GACoastalHUC12) (Estuaries,1994). Refined boundary lines to 24k DRGs and NOAA Bathemetry (USGS DRG24) (NOAA_RNC). Shoreline to 100 meter buffer (LINESOURCE "Buffer100") from NOAA_RNC MLLW and corrected to the International Maritime Organization's COLREG Demarcation Lines across inlets as delineated on NOAA_RNC, input NOAA three nautical mile offshore boundary as agreed upon by Coastal Georgia Watershed Review Team. Source_Used_Citation_Abbreviation: USGS 1:24000 base Source_Used_Citation_Abbreviation: NOAA_RNC Source_Used_Citation_Abbreviation: GACoastalHUC12 Source_Used_Citation_Abbreviation: Estuaries,1994 Process_Date: 201010 Process_Step: Process_Description: Meta_ID: GA06 Details: Edits submitted to correct HUC10 coding in Georgia. Process_Date: 201011 Process_Step: META_ID: GA07 Process_Description: The Line Mods, HU_Level, Linesource, DS codes and states were checked, the following meta ids were used for any updates. Source_Used_Citation_Abbreviation: Process_Date: 201109 Process_Step: META_ID: GA08 Process_Description: Updates by USGS, Salt Lake City: Edits to names. Source_Used_Citation_Abbreviation: Process_Date: 201112 Process_Step: META_ID: GA09 - HU_Level updates, HUC10 code updates where the HUC10 code did not match the HUC12 code, DS code updates, Name Updates, Mod Updates Process_Description: edits by USGS Water Science Center in Salt Lake City, Utah. Source_Used_Citation_Abbreviation: Process_Date: 201205 Spatial_Data_Organization_Information: Direct_Spatial_Reference_Method: Vector Point_and_Vector_Object_Information: SDTS_Terms_Description: SDTS_Point_and_Vector_Object_Type: G-polygon Point_and_Vector_Object_Count: 1595 SDTS_Terms_Description: SDTS_Point_and_Vector_Object_Type: Label point Point_and_Vector_Object_Count: 2471 SDTS_Terms_Description: SDTS_Point_and_Vector_Object_Type: GT-polygon composed of chains Point_and_Vector_Object_Count: 2471 SDTS_Terms_Description: SDTS_Point_and_Vector_Object_Type: Point Point_and_Vector_Object_Count: 0 SDTS_Terms_Description: SDTS_Point_and_Vector_Object_Type: Composite object Point_and_Vector_Object_Count: 403 SDTS_Terms_Description: SDTS_Point_and_Vector_Object_Type: Composite object Point_and_Vector_Object_Count: 1992 SDTS_Terms_Description: SDTS_Point_and_Vector_Object_Type: Composite object Point_and_Vector_Object_Count: 2 SDTS_Terms_Description: SDTS_Point_and_Vector_Object_Type: Composite object Point_and_Vector_Object_Count: 9 SDTS_Terms_Description: SDTS_Point_and_Vector_Object_Type: Composite object Point_and_Vector_Object_Count: 12 SDTS_Terms_Description: SDTS_Point_and_Vector_Object_Type: Composite object Point_and_Vector_Object_Count: 54 Spatial_Reference_Information: Horizontal_Coordinate_System_Definition: Geographic: Latitude_Resolution: 0.000000 Longitude_Resolution: 0.000000 Geographic_Coordinate_Units: Decimal degrees Geodetic_Model: Horizontal_Datum_Name: North American Datum of 1983 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_Resolution: 0.000122 Altitude_Encoding_Method: Explicit elevation coordinate included with horizontal coordinates Entity_and_Attribute_Information: Detailed_Description: Entity_Type: Entity_Type_Label: HU12_polygon Entity_Type_Definition: Polygon attribute table Entity_Type_Definition_Source: ARC/INFO Attribute: Attribute_Label: HUC_12 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: ACRES 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: NCONTRB_A 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: HU_10_GNIS 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: HU_12_GNIS 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: HU_10_DS 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: HU_10_NAME 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: HU_10_MOD 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: HU_10_TYPE 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: HU_12_DS 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: HU_12_NAME 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: HU_12_MOD 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: HU_12_TYPE 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: META_ID 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: STATES Attribute_Definition: Intersection of polygon with states Attribute_Definition_Source: ESRI Attribute_Domain_Values: Unrepresentable_Domain: Positive real numbers that are automatically generated. Attribute: Attribute_Label: Shape_Length Attribute_Definition: Length of feature in internal units. Attribute_Definition_Source: ESRI Attribute_Domain_Values: Unrepresentable_Domain: Positive real numbers that are automatically generated. Attribute: Attribute_Label: Shape_Area Attribute_Definition: Area of feature in internal units squared. Attribute_Definition_Source: ESRI Attribute_Domain_Values: Unrepresentable_Domain: Positive real numbers that are automatically generated. Attribute: Attribute_Label: META_ID Attribute_Definition: Feature geometry. Attribute_Definition_Source: ESRI Attribute_Domain_Values: Unrepresentable_Domain: Sequential unique whole numbers that are automatically generated. Attribute: Attribute_Label: Shape Attribute_Definition: Feature geometry. Attribute_Definition_Source: ESRI Attribute_Domain_Values: Enumerated_Domain: Enumerated_Domain_Value: Positive real numbers Attribute_Domain_Values: Unrepresentable_Domain: Coordinates defining the features. Attribute: Attribute_Label: HUC_8 Attribute: Attribute_Label: HUC_10 Detailed_Description: Entity_Type: Entity_Type_Label: ga_hu12_utm.pat Entity_Type_Definition_Source: ARC/INFO Attribute: Attribute_Label: FID Attribute_Definition: Internal feature number. Attribute_Definition_Source: ESRI Attribute_Domain_Values: Enumerated_Domain: Enumerated_Domain_Value: - Attribute_Domain_Values: Unrepresentable_Domain: Sequential unique whole numbers that are automatically generated. Attribute: Attribute_Label: Shape Attribute_Definition: Feature geometry. Attribute_Definition_Source: ESRI Attribute_Domain_Values: Enumerated_Domain: Attribute_Domain_Values: Unrepresentable_Domain: Coordinates defining the features. Attribute: Attribute_Label: AREA Attribute_Definition: Area of feature in internal units squared. Attribute_Definition_Source: ESRI Attribute_Domain_Values: Enumerated_Domain: Attribute_Domain_Values: Unrepresentable_Domain: Positive real numbers that are automatically generated. Attribute: Attribute_Label: PERIMETER Attribute_Definition: Perimeter of feature in internal units. Attribute_Definition_Source: ESRI Attribute_Domain_Values: Enumerated_Domain: Attribute_Domain_Values: Unrepresentable_Domain: Positive real numbers that are automatically generated. Attribute: Attribute_Label: GA_HU12_UTM# Attribute_Definition: Internal feature number. Attribute_Definition_Source: ESRI Attribute_Domain_Values: Enumerated_Domain: Attribute_Domain_Values: Unrepresentable_Domain: Sequential unique whole numbers that are automatically generated. Attribute: Attribute_Label: GA_HU12_UTM-ID Attribute_Definition: User-defined feature number. Attribute_Definition_Source: ESRI Attribute_Domain_Values: Enumerated_Domain: Attribute: Attribute_Label: HUC_8 Attribute_Definition: 8-digit Hydrologic Unit Code Attribute: Attribute_Label: HUC_10 Attribute_Definition: 10-digit Hydrologic Unit Code Attribute: Attribute_Label: HUC_12 Attribute_Definition: 12-digit Hydrologic Unit Code Attribute: Attribute_Label: ACRES Attribute_Definition: Area in acres, calculated Attribute: Attribute_Label: STATES Attribute_Definition: Intersection of polygon with states Attribute: Attribute_Label: NCONTRB_A Attribute_Definition: Non-contributiong drainage area Attribute: Attribute_Label: HU_10_DS Attribute_Definition: Downstream HUC10 Attribute: Attribute_Label: HU_10_NAME Attribute_Definition: Name of watershed Attribute: Attribute_Label: HU_10_MOD Attribute_Definition: Modification information Attribute: Attribute_Label: HU_10_TYPE Attribute_Definition: watershed type Attribute: Attribute_Label: HU_12_DS Attribute_Definition: Downstream HUC10 Attribute: Attribute_Label: HU_12_NAME Attribute_Definition: Name of sub-watershed Attribute: Attribute_Label: HU_12_MOD Attribute_Definition: Modification information Attribute: Attribute_Label: HU_12_TYPE Attribute_Definition: sub-watershed type Attribute: Attribute_Label: HU_10_TYPE Attribute_Definition: sub-watershed type Attribute: Attribute_Label: HUC_10 Attribute_Definition: 10-digit Hydrologic Unit Code Attribute: Attribute_Label: HUC_12 Attribute_Definition: 12-digit Hydrologic Unit Code Attribute: Attribute_Label: HUC_2 Attribute_Definition: 2-digit Hydrologic Unit Code Attribute: Attribute_Label: HUC_4 Attribute_Definition: 4-digit Hydrologic Unit Code Attribute: Attribute_Label: HUC_6 Attribute_Definition: 6-digit Hydrologic Unit Code Overview_Description: Entity_and_Attribute_Overview: This is a description of attributes by field from the Federal guidelines, requirements, and procedures for the National Watershed Boundary Dataset (2009) 1) Polygon attributes Huc_8 : Eight Digit Hydrologic Unit Code A unique 8-digit code from the USGS map series "Hydrologic Unit Maps". The same number was used in every record that pertains to a subwatershed that resides within the same 8-digit sub-basin.Numbers were assigned in an upstream to downstream fashion. Where no downstream/upstream relationship could be determined numbers were assigned in a clockwise fashion. Huc_10: Ten Digit Hydrologic Unit Code This field provides a unique 10-digit code for each watershed. This same number was used in every record that pertains to a subwatershed that resides within the same 10-digit watershed. Numbers were assigned in an upstream to downstream fashion. Where no downstream/upstream relationship could be determined numbers were assigned in a clockwise fashion. Huc_12: Twelve Digit Hydrologic Unit Code This field provides a unique 12-digit code for each subwatershed. Numbers were assigned in an upstream to downstream fashion. Where no downstream/upstream relationship could be determined numbers were assigned in a clockwise fashion. Acres: Acres Area of subwatershed including non-contributing areas calculated to acres as a whole number, no decimals. The "Acres" field was calculated from the "Area" field. States: States The "States" field includes the names of all state(s) that the subwatershed falls within. The 2-digit postal abbreviation in upper case and in alphabetical order was used, separated with a comma. Ncontrb_a: Non-Contributing Area Drainage areas that do not flow toward the outlet of any hydrologic unit are considered non-contributing. If a non-contributing area is on the boundary between two or more hydrologic units, the non-contributing area is associated with the hydrologic unit adjacent to the low point on the boundary. This attribute should be the total of the non-contributing areas within a hydrologic unit calculated in acres. Hu_10_ds: Fifth Level Downstream Hydrologic Unit Code This field has the 10-digit code of the 5th level hydrologic unit that is receiving the majority of the flow from the watershed that the 6th level HU falls within. Outlets created by ditching or other artificial drainage were not considered for this field. If an HU flows into an ocean or the Gulf of Mexico, this field was populated with "OCEAN" and if a HU flows into one of the Great Lakes the term "LAKE" was used. If a HU flows across international borders, "CANADA" or "MEXICO" was used depending on which country the HU drains into. If an HU is a closed basin, then the term "CLOSED BASIN"was used. Hu_10_name: Fifth Level Hydrologic Unit Name This field used officially recognized names only. This field was populated by following the directions in subsection 6.3 "Watershed and Subwatershed Naming Protocol". The name used to attribute the watershed was used only once within a 4th level unit. Hu_10_mod: Fifth Level Hydrologic Unit Modifications This field identifies any type of modifications to natural overland flow that alters the location of the hydrologic unit boundary for a 10-digit watershed. This field shows the most significant to least significant modification(s) to the watershed boundary. One or more of the following abbreviations was used. SC - Stormwater Canal or Drainage Canal ID - Irrigation Ditch IT - Interbasin Transfer BC - Barge Canal or Navigation Canal SD - Stormwater Ditch PD - Pipe Diversion CD - Channel Diversion NC - Noncontributing Area KA - Karst LE - Levee NM - No Modifications OC - Overflow Channel or Flume DM - Dam at outlet or HU boundary GC - General Canal/Ditch PS - Pumping Station DD - Drainage Ditch SI - Siphon AD - Aqueduct RS - Reservoir TF - Transportation Feature (road, railroad, docks etc.) GF - Ground-Water Flow MA - Mining Activity UA - Urban Area GL - Glacier IF - Ice Field OF - Overbank Flow OT - Other Hu_10_type: Fifth Level Hydrologic Unit Type This field was populated with the hydrologic unit type from the list provided that most closely identifies the watershed. S - "Standard" hydrologic unit - Any land HU with drainage flowing to a single outlet point, excluding non-contributing areas. This includes areas or small triangular wedges between adjacent HU's that remain after classic hydrologic units are delineated. Some examples include "true", "classic", "composite", and "remnant" hydrologic units. C - "Closed Basin" hydrologic unit - A drainage area that is 100% non-contributing. This means all surface flow is internal, no overland flow leaves the hydrologic unit through the outlet point. F - "Frontal" hydrologic unit - Areas along the coastline of lakes, oceans, bays, etc. that have more than one outlet. These HU's are predominantly land with some water areas at or near the outlet(s). M - "Multiple Outlet" hydrologic unit An area that has more than one natural outlet; for example, an outlet located on a stream with multiple channels. This does not include frontal or water hydrologic units, hydrologic units with artificial interbasin transfers, drainage outlets through karst or ground-water flow, or outlets that cross a stream with an island. This code should be used only in rare instances. W - "Water" hydrologic unit - Hydrologic units that are predominantly water with adjacent land areas, ex. lake, easturies, harbors. I - "Island" hydrologic unit - A hydrologic unit that is one or more islands and adjacent water out to the toe of the shore face. U - "Unclassified" hydrologic unit - A hydrologic unit that can't be defined or doesn't fit into one of the types that have been listed. Hu_12_ds: Sixth Level Downstream Hydrologic Unit Code This field was populated with the 12-digit code of the 6th level hydrologic unit that is receiving the majority of the flow from the subwatershed. Outlets created by ditching or other artificial drainage were not considered for this field. If a HU flows into an ocean or the Gulf of Mexico it was populate with "OCEAN" and if a HU flows into one of the Great Lakes the term "LAKE" was used. If a HU flows across international borders, "CANADA" or "MEXICO" was used depending on which country the HU drains into. If an HU is a closed basin, this field was populated with the term "CLOSED BASIN". Hu_12_name: Sixth Level Hydrologic Unit Name Officially recognized names were used in this field. This field was populated by following the directions in subsection 6.3 "Watershed and Subwatershed Naming Protocol". The name used to attribute the subwatershed was used only once within a 4th level unit. Hu_12_mod: Sixth Level Hydrologic Unit Modifications This field identifies any type of man-made modification(s) to natural overland flow that alters the location of the hydrologic unit boundary for a 12-digit subwatershed. One or more of the following abbreviations was chosen for this field. SC - Stormwater Canal or Drainage Canal ID - Irrigation Ditch IT - Interbasin Transfer BC - Barge Canal or Navigation Canal SD - Stormwater Ditch PD - Pipe Diversion CD - Channel Diversion NC - Noncontributing Area KA - Karst LE - Levee NM - No Modifications OC - Overflow Channel or Flume DM - Dam at outlet or HU boundary GC - General Canal/Ditch PS - Pumping Station DD - Drainage Ditch SI - Siphon AD - Aqueduct RS - Reservoir TF - Transportation Feature (road, railroad, docks etc.) GF - Ground-Water Flow MA - Mining Activity UA - Urban Area GL - Glacier IF - Ice Field OF - Overbank Flow OT - Other Hu_12_type: Sixth Level Hydrologic Unit Type This field was populated with the hydrologic unit type from the list provided that most closely identifies the subwatershed. S - "Standard" hydrologic unit - Any land HU with drainage flowing to a single outlet point, excluding non-contributing areas. This includes areas or small triangular wedges between adjacent HU's that remain after classic hydrologic units are delineated. Some examples include "true", "classic", "composite", and "remnant" hydrologic units. C - "Closed Basin" hydrologic unit - A drainage area that is 100% non-contributing. This means all surface flow is internal, no overland flow leaves the hydrologic unit through the outlet point. F - "Frontal" hydrologic unit - Areas along the coastline of lakes, oceans, bays, etc. that have more than one outlet. These HU's are predominantly land with some water at or near the outlet(s). M - "Multiple Outlet" hydrologic unit An area that has more than one natural outlet; for example, an outlet located on a stream with multiple channels. This does not include frontal or water hydrologic units, hydrologic units with artificial interbasin transfers, drainage outlets through karst or ground-water flow, or outlets that cross a stream with an island. This code should be used only in rare instances. W - "Water" hydrologic unit - Hydrologic units that are predominantly water with adjacent land areas, ex. lake, easturies. I - "Island" hydrologic unit - A hydrologic unit that is one or more islands and adjacent water out to the toe of the shore face. U - "Unclassified" hydrologic unit - A hydrologic unit that can't be defined or doesn't fit into one of the types that have been listed. 2) Line attributes Hu_level: Hydrologic Unit Level This field provides the means to create cartographically pleasing maps. This field is populated with the highest hydrologic unit level (smallest number) for the line (arc) represented by the record. The attribute was recorded using numbers 1 through 6 representing each level with 1 being the highest and 6 the lowest level. An example would be if a line represents a region, subregion, basin, subbasin, watershed, and subwatershed boundary, then this cell was populated with a 1 (Region). Below is a list of numbers used for each level. Level Digit# Name 1 2 Region 2 4 Subregion 3 6 Basin 4 8 Subbasin 5 10 Watershed 6 12 Subwatershed Linesource: Line Spatial Data Source The Linesource indicates the base map source(s) used to delineate at 1:24,000 scale. The field was populated using one of the standardized code(s) listed below. If more than one code was used, then a comma was used to separate the codes. TOPO24 - Delineation from hardcopy 1:24,000 scale topographic maps TOPO25 - Delineation from hardcopy 1:25,000 topgraphic maps, only Alaska and Caribbean TOPO63 - Delineation from hardcopy 1:63,360 topographic maps, only Alaska and Caribbean DRG24 - Delineation from 1:24,000 scale Digital Raster Graphics DRG25 - Delineation from 1:25,000 Digital Raster Graphics, only Alaska and Caribbean DRG63 - Delineation from 1:63,360 Digital Raster Graphics, only Alaska and Caribbean DEM10 - Derived from 10 meter Digital Elevation Model DEM30 - Derived from 30 meter Digital Elevation Model NED30 - Derived from 30 meter National Elevation Dateset Model EDNA30 - (formally NED-H), derived from 30 meter Elevation Derivatives for National Applications BATH"scale" (ex. BATH24) - Interpreted from NOAA 1:24,000 scale bathymetric data HYPSO"scale" (ex. HYPSO24)- Delineated from 1:24,000 scale contour data ORTHO"scale" (ex. ORTHO12) - Interpreted from 1:12,000 scale Ortho-imagery DEDEM10 - Drainage enforced 10 meter Digital Elevation Model DEDEM30 - Drainage enforced 30 meter Digital Elevation Model GPS - Derived from Global Positioning System LIDAR - Derived from LIDAR IFSAR - Derived from IFSAR data OTH - Other UNK - Unknown All other reference and source maps not listed should be noted in the metadata. Meta_id: Metadata ID Number The Metadata ID is a code that identifies which metadata file applies to the arc. In most cases there is only one metadata file. However, in some cases more than one metadata file was used to identify different groups and/or procedures used to produce the lines. The metadata ID is a 4-character code starting with the 2-letter state postal code, followed by a 2-digit sequence number. For example "OK01", "ID02", etc Entity_and_Attribute_Detail_Citation: U.S. Geological Survey and U.S. Department of Agriculture, Natural Resources Conservation Service, 2009, Federal guidelines, requirements, and procedures for the National Watershed Boundary Dataset: U.S. Geological Survey Techniques and Methods 11-A3, 55 p. Distribution_Information: Resource_Description: Downloadable Data Standard_Order_Process: Digital_Form: Digital_Transfer_Information: Transfer_Size: 21.553 Metadata_Reference_Information: Metadata_Date: 20101007 Metadata_Contact: Contact_Information: Contact_Organization_Primary: Contact_Organization: U.S. Geological Survey Contact_Person: Keith W. McFadden Contact_Address: Address_Type: REQUIRED: The mailing and/or physical address for the organization or individual. City: REQUIRED: The city of the address. State_or_Province: REQUIRED: The state or province of the address. Postal_Code: REQUIRED: The ZIP or other postal code of the address. Contact_Voice_Telephone: 770-903-9100 Contact_Facsimile_Telephone: 770-903-9199 Contact_Electronic_Mail_Address: keithmc@usgs.gov Metadata_Standard_Name: FGDC Content Standards for Digital Geospatial Metadata Metadata_Standard_Version: FGDC-STD-001-1998 Metadata_Time_Convention: local time Metadata_Security_Information: Metadata_Security_Classification_System: None Metadata_Security_Classification: Unclassified Metadata_Security_Handling_Description: None Metadata_Extensions: Online_Linkage: http://www.esri.com/metadata/esriprof80.html Profile_Name: ESRI Metadata Profile