U.S. Geological Survey --------------------------------------------------------------------------- Metadata for CORRIDOR Table of Contents Identification_Information Abstract Purpose Supplemental Information Data_Quality_Information Spatial_Data_Organization_Information Entity_and_Attribute_Information Detailed Description Overview Distribution_Information Metadata_Reference_Section --------------------------------------------------------------------------- Identification_Information Citation_Information Originator: Musser, Jonathan W. Publication_Date: 1996 Title: River Corridors With Mean Annual Flow Greater Than 400 CFS Edition: 1.0 1.1 Datum change from 1927 to 1983 (North American Datum of 1983) Series_Information Series_Name: Digital Data Series Publication_Information Publication_Place: Atlanta, GA Publisher: U.S. Geological Survey Online_Linkage: http://csat.er.usgs.gov/statewide/layers/corridor.html Scale_Denominator: 100000 Description Abstract The river corridor layer is a subset of the digital information contained in the 1:100,000 U.S. Geological Survey Hydrography Digital Line Graph Data for the State of Georgia. The file contains the digital stream reach representations that are impacted by the Georgia State Law that defines "the protection of river corridors" (HB No. 643, see reference 1). Georgia State Law (Section 12-2-8, as amended, of Article 1, Chapter 2, Title 12 of the Official Code of Georgia, Annotated) defines protected river corridors as 100 foot strips of land that flank major river reaches with a mean annual flow of 400 cubic feet per second or greater. These include the lakes that fall in these stream reaches. Please note that while the digital representations of the stream reaches that meet the criteria of having a mean annual flow of 400 cfs or greater are contained in this file, the digital representations of the 100 foot strips, described in the law, are not contained in this file. Purpose These river corridors were designated by Georgia State Law (Section 12-2-8, as amended, of Article 1, Chapter 2, Title 12 of the Official Code of Georgia, Annotated) The law states that "these corridors are of vital importance to Georgia in That they help preserve those qualities that make a river suitable as a habitat for wildlife, a site for recreation, and a source for clean drinking water. River corridors allow the free movement of wildlife from area to area within the state, help control erosion and river sedimentation, and help absorb flood waters." (HB No. 643, see reference 1) Supplemental_Information Procedures_Used A determination was made on each major river where the mean annual flow exceeded 400 cubic feet per second (cfs). A primary data source for this determination was the most current annual streamflow data report (see reference 2). In some cases it was found that the confluence of two major rivers having mean annual flows of 300-400 cfs, met the exceedence criteria. If the exceedence point could not be determined from the most current annual streamflow data report (see reference 2), the most nearby streamflow gage record was examined. If the mean annual flow at the gage was above or below 400 cfs, then the drainage areas at locations upstream or downstream were determined and multiplied by the cubic feet per second per square mile yield for the respective river basin locations until the exceedence point was found. (see references 3 and 4) Every stretch of river downstream was marked as being greater than 400 cfs mean annual flow. River sections that exceeded that exceeded 400 cfs mean annual flow were delineated on 1:24,000 scale U.S. Geological Survey topographic maps. These Topo Maps were then used to extract the rivers with mean annual flow of 400 cfs or greater from the 1:100,000 U.S. Geological Survey Digital Line Graph Hydrography. ArcEdit was used to mark each arc section that met the exceedence criteria. All other hydrographic features were removed. Revisions None Reviews_Applied A map of the river corridors was produced and compared to the original data source for accuracy. Location of the segment points was used for comparison since the original data were located on 1:24,000 scale topographic maps and the digital representations were matched to existing 1:100,000 scale digital data. Corrections were made when necessary. Overlay process repeated. Colleague review July 25, 1996 by Thomas R. (Bob) Dyar and Jack Alhadeff. Digital data was reviewed with respect to positional accuracy, contextual accuracy, attribute accuracy, topological consistency, and metadata content. Approved by Georgia District Chief, Tim Hale, on July 26, 1996. Related_Spatial_and_Tabular_Data_Sets None Other_References_Cited 1. Georgia House Bill Number 643 as passed by both the Georgia House and Senate (By representatives Porter of the 119th, Jamieson of the 11th and Baker of the 51st). 2. Stokes, W.R. III, McFarlane, R.D. and Buell, G.R., Water Resources Data Georgia Water Year 1989, U.S. Geological Survey, Water-Data Report GA-89-1, U.S. Geological Survey, Doraville, GA 1990. 3. Carter, R.F. 1983, Storage Requirements For Georgia Streams, Open-File Report 82-557, U.S. Geological Survey, Doraville, GA 1983. 4. Carter, R.F., Hopkins, E.H., and Perlman, H.A., Low-Flow Profiles of the Upper Savannah and Ogeechee Rivers and Tributaries in Georgia, Water Resources Investigation Report 88-4047, U.S. Geological Survey, Doraville, GA 1988. Notes None Time_Period_of_Content Single_Date/Time Calendar_Date: 1990 Currentness_Reference All data current as of 1990 Status Progress: Approved for release by Tim Hale Georgia District Chief Maintenance_and_Update_Frequency None planned Spatial_Domain Bounding_Coordinates West_Bounding_Coordinate: -85.48489072 East_Bounding_Coordinate: -81.11100328 North_Bounding_Coordinate: 34.98108652 South_Bounding_Coordinate: 30.34174353 Keywords Theme Theme_Keyword_Thesaurus: None Theme_Keyword: river corridor hydrography 400 cfs stream protection Place Place_Keyword_Thesaurus: None Place_Keyword: State of Georgia Stratum Stratum_Keyword_Thesaurus: None Stratum_Keyword: Temporal Temporal_Keyword_Thesaurus: None Temporal_Keyword: Access_Constraints None Use_Constraints U.S. Geological Survey 1:100,000 scale Hydrography DLGs were used as stream bank delineations. These are represented by a combination of single line and double line stream features as determined by generalization of the 1:100,000 scale cartography. These data represented the best available digital location of river banks. These data do not represent the 100 foot strips that are described in the law. Scale dependent as noted. See section 391-3-16-.04 Criteria for River Corridor Protection, paragraph (2) (m) as well as other portions of the law. (HB No. 643, see reference 1) Point_of_Contact: See Data_Set_Credit U.S. Geological Survey, National Mapping Program Georgia Department of Natural Resources, Geologic Survey Security_Information Security_Classification_System: None Security_Classification: UNCLASSIFIED Security_Handling_Description: None Native_Data_Set_Environment: dgux UNIX, ARC/INFO version 7.0.4 Cross_Reference Originator: U.S. Geological Survey Publication_Date: January 1993 Publication_Time: Title: 1:100,000-Scale Digital Line Graph (DLG) Data Hydrography and Transportation Edition: Geospatial_Data_Presentation_Form: Series_Information Series_Name: US GeoData Issue_Identification: Publication_Information Publication_Place: Reston, VA Publisher: U.S. Geoglogical Survey Other_Citation_Details: CD-ROM Online_Linkage: Larger_Work_Citation: --------------------------------------------------------------------------- Data_Quality_Information Attribute_Accuracy Attribute_Accuracy_Report: See Logical_Consistency_Report: Chain-node topology present. Completeness_Report The initial work of determining which rivers have a mean annual flow of 400 cfs or greater was checked as well as the transfer of this information to digital form. Positional_Accuracy Horizontal_Positional_Accuracy Horizontal_Positional_Accuracy_Report: Horizontal positional accuracy is based upon the use of USGS source quadrangles which are compiled to meet National Map Accuracy Standards (NMAS). NMAS horizontal accuracy requires that at least 90 percent of points tested are within 0.02 inches of the true position. The digital data are estimated to contain a horizontal positional error of less than or equal to 0.003 inches standard error in the two component directions relative to the source quadrangle. Comparison to the graphic source is used as control to assess digital positional accuracy. Cartographic offsets may be present on the graphic source, due to scale and legibility constraints. Digital map elements require edge alignment between data sets. Data along each partitioned edge internal to the original 100,000 scale quadrangle, and data along the quadrangle edge, are tested against the adjacent data set using PROSYS; tests check for positional accuracy between data sets within a 0.02 inches tolerance. Features with like dimensionality, and with or without like attribution, that are within the tolerance are adjusted by moving the feature equally in both data sets. Features outside the tolerance are not moved. All disconnects are identified by edge matching flags that document the mismatch. This file has undergone digital revision. Accuracy of these digital data meets the class 1 positional accuracy specifications in the draft United States National Cartographic Standards for Spatial Accuracy. Digital map elements require edge alignment between data sets. Data along each partitioned edge internal to the original 100,000 scale quadrangle, and data along the quadrangle edge, are tested against the adjacent data set using the USGS Production System (PROSYS); tests check for positional accuracy between data sets within a 0.02 inches tolerance. Features with like dimensionality, and with or without like attribution, that are within the tolerance are adjusted by moving the feature equally in both data sets. Features outside the tolerance are not moved. All disconnects are identified by edge matching flags that document the mismatch. Quantitative_Horizontal_Positional_Accuracy_Assessment: Horizontal_Positional_Accuracy_Value: 40 meters Horizontal_Positional_Accuracy_Explanation: Resolution as reported Vertical_Positional_Accuracy Vertical_Positional_Accuracy_Report: Vertical positional accuracy is based upon the use of USGS source quadrangles which are compiled to meet NMAS. NMAS vertical accuracy requires that at least 90 percent of well defined points tested be within one half contour interval of the correct value. Comparison to the graphic source is used as control to assess digital positional accuracy. This file has undergone digital revision. Accuracy of these digital data meets the class 1 positional accuracy specifications in the draft United States National Cartographic Standards for Spatial Accuracy. Lineage: See Cloud_Cover N/A --------------------------------------------------------------------------- Spatial_Data_Organization_Information Direct_Spatial_Reference_Method: Vector Point_and_Vector_Object_Information SDTS_Terms_Description SDTS_Point_and_Vector_Object_Type: Point Point_and_Vector_Object_Count: 0 SDTS_Point_and_Vector_Object_Type: String Point_and_Vector_Object_Count: 2746 SDTS_Point_and_Vector_Object_Type: GT-polygon composed of chains' Point_and_Vector_Object_Count: 0 --------------------------------------------------------------------------- Spatial_Reference_Information Horizontal_Coordinate_System_Definition Planar Map_Projection: Map_Projection_Name: ALBERS Longitude_of_Central_Meridian: -83.5 Latitude_of_Projection_Origin: 23 Latitude_of_First_Standard_Parallel: 29.5 Latitude_of_Second_Standard_Parallel: 45.5 False_Easting: 0.00000 False_Northing: 0.00000 Geodetic Model Horizontal_Datum_Name: North American Datum of 1983 Ellipsoid_Name: GRS 80 Semi-major_Axis: 6,378,206.4 Denominator_of_Flattening: 294.98 --------------------------------------------------------------------------- Entity_and_Attribute_Information Detailed_Description Entity_Type Entity_Type_Label: CORRIDOR.AAT Entity_Type_Definition: No attributes present Entity_Type_Definition_Source: ARC/INFO Attribute: Attribute_Label: - Attribute_Definition: No attributes present Attribute_Definition_Source: ARC/INFO Attribute_Domain_Values Enumerated_Domain Enumerated_Domain_Value: - Enumerated_Domain_Value_Definition Enumerated_Domain_Value_Definition_Source: Attribute: Attribute_Label: FNODE# Attribute_Definition: Internal number of from-node Attribute_Definition_Source: Computed Attribute_Domain_Values Enumerated_Domain Enumerated_Domain_Value: Sequential unique positive integer Enumerated_Domain_Value_Definition Enumerated_Domain_Value_Definition_Source: Attribute: Attribute_Label: TNODE# Attribute_Definition: Internal number of to-node Attribute_Definition_Source: Computed Attribute_Domain_Values Enumerated_Domain Enumerated_Domain_Value: Sequential unique positive integer Enumerated_Domain_Value_Definition Enumerated_Domain_Value_Definition_Source: Attribute: Attribute_Label: LPOLY# Attribute_Definition: Internal number of poly to left of arc Attribute_Definition_Source: Computed Attribute_Domain_Values Enumerated_Domain Enumerated_Domain_Value: Sequential unique positive integer Enumerated_Domain_Value_Definition Enumerated_Domain_Value_Definition_Source: Attribute: Attribute_Label: RPOLY# Attribute_Definition: Internal number of poly to right of arc Attribute_Definition_Source: Computed Attribute_Domain_Values Enumerated_Domain Enumerated_Domain_Value: Sequential unique positive integer Enumerated_Domain_Value_Definition Enumerated_Domain_Value_Definition_Source: Attribute: Attribute_Label: LENGTH Attribute_Definition: Length of arc in coverage units Attribute_Definition_Source: Computed Attribute_Domain_Values Enumerated_Domain Enumerated_Domain_Value: Positive real numbers Enumerated_Domain_Value_Definition Enumerated_Domain_Value_Definition_Source: Attribute: Attribute_Label: CORRIDOR# Attribute_Definition: Internal feature number Attribute_Definition_Source: Computed Attribute_Domain_Values Enumerated_Domain Enumerated_Domain_Value: Sequential unique positive integer Enumerated_Domain_Value_Definition Enumerated_Domain_Value_Definition_Source: Attribute: Attribute_Label: CORRIDOR-ID Attribute_Definition: User-assigned feature number Attribute_Definition_Source: User-defined Attribute_Domain_Values Enumerated_Domain Enumerated_Domain_Value: Integer Enumerated_Domain_Value_Definition Enumerated_Domain_Value_Definition_Source: Overview_Description Entity_and_Attribute_Overview No attribute tables. Entity_and_Attribute_Detail_Citation: Not Available --------------------------------------------------------------------------- Distribution_Information Distributor Contact_Person_Primary Contact_Person: Jonathan W. Musser Contact_Organization: U.S. Geological Survey Contact_Position: Hydrologist Contact_Address Address_Type: mailing address Address: U.S. Geological Survey 3039 Amwiler Road Suite 130 City: Atlanta State_or_Province: GA Postal_Code: 30360-2824 Country: USA Contact_Facsimile_Telephone: 770-903-9199 Contact_Electronic_Mail_Address: jwmusser@usgs.gov Standard_Order_Process Digital_Form Digital_Transfer_Information Format_Name: ARCE ARC/INFO Export format File_Decompression_Technique: gzip Format_Name: SDTS Spatial Data Transfer Standards (FIPS 173) File_Decompression_Technique: gzip & tar Digital_Transfer_Option Online_Option Computer_Contact_Information Network_Address Network_Resource_Name: http://csat.er.usgs.gov/statewide/layers/corridor.html ------------------------------------------------------------------------ --------------------------------------------------------------------------- Metadata_Reference_Section Metadata_Date: 19980109 Metadata_Contact: bdmoudry Metadata_Standard_Name: FGDC Content Standards for Digital Geospatial Metadata Metadata_Standard_Version: 19940608 Metadata_Time_Convention: Local Time Metadata_Security_Information: Metadata_Security_Classification_System: None Metadata_Security_Classification: UNCLASSIFIED Metadata_Security_Handling_Description: None --------------------------------------------------------------------------- Last modified: 2008-03-20