USGS 1:24,000 HYDROGRAPHY - POLYGONS | |
Data format: SDE Feature Class File or table name: clay.DBO.Pond Coordinate system: Transverse Mercator Theme keywords: Hydrological Poly Features, USGS, United States Geological Survey |
|
Abstract:
This dataset contains Hydrological Poly Features from the USGS 1:24000 scale
DLG's. Lakes and ponds were added by heads up digitizing over the 2004 county
wide digital aerial photo mosaic. No new fields have been added.attributes were
added to some river and lake features not in the original data. All features both
old and newly digitized were reshapes or normalized to match the 2004 photo-
gaphy. The positional accuracy of this data is only as good as the 2004 source
data it was digitized over and the skills of the photo interpreter.
Polygon
This dataset has been updated from the previous version on FGDL 3.0. |
Metadata elements shown with blue text are defined in the Federal Geographic Data Committee's (FGDC) Content Standard for Digital Geospatial Metadata (CSDGM). Elements shown with green text are defined in the ESRI Profile of the CSDGM. Elements shown with a green asterisk (*) will be automatically updated by ArcCatalog. ArcCatalog adds hints indicating which FGDC elements are mandatory; these are shown with gray text.
This dataset contains Hydrological Poly Features from the USGS 1:24000 scale DLG's. Lakes and ponds were added by heads up digitizing over the 2004 county wide digital aerial photo mosaic. No new fields have been added.attributes were added to some river and lake features not in the original data. All features both old and newly digitized were reshapes or normalized to match the 2004 photo- gaphy. The positional accuracy of this data is only as good as the 2004 source data it was digitized over and the skills of the photo interpreter. Polygon This dataset has been updated from the previous version on FGDL 3.0.
The data was created to serve as base information for use in a county wide GIS systems for a variety of planning and analytical purposes.
The County also added to this data set newly digitized and reshapes ponds for positional accuracy and the most current and updates information available. The data was extracted from Cad As-built, and Construction plan files and head up digitizing over the County 2009 Aerial Photo in State Plane Coordinate Nad83 Harn and adjusted to match the imagery. This product has been compiled from the most accurate source data provided By a Licensed Surveyor, Professional Engineers, Clay County Engineering and Public Works Department.
publication date
Information from the Clay County Geographic Information System Division is provided for general reference purposes only and is not to be construed as a survey or legal document. Errors from non-coincidence of features from different sources may be present. The Clay County Geographic Information System makes every reasonable effort to ensure that the information provided herein is current and accurate. However, Clay County provides no warranties, expressed or implied, concerning the accuracy, completeness, reliability, or suitability of this data for any particular use or purpose. Clay County assumes no liability whatsoever associated with the use or misuse of such data.
431 Architecture PO Box 115706
Clay County IT/GIS Department Address: 477 Houston St. City: Green Cove Springs State: Florida Postal_Code: 32043 Country: USA Contact_Voice_Telephone: 904-541-3817 Contact_Facsimile_Telephone: 904-541-5806 Hours_of_Service: 7:30am to 4:30pm
Relied on the integrity of the attribute information within the original data layer.
Scale is an important factor in data usage. Certain scale datasets are not suitable for some project, analysis, or modelling 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. These data are based on interpretation of available information and should not be construed as legally binding.
Relied on the integrity of the attribute information within the original data layer.
Relied on the integrity of the attribute information within the original data layer.
Spatial and Attribute Information
The data was downloaded by the GeoPlan Center from the USGS. The files were orginally in DLG format. The source projection was UTM (zone 16 and 17) units - meters datum - Nad27 and spheroid - Clarke 1866. The DLG's were converted to coverage format, processed, then converted to shapefile. The following items were removed from the attribute table: Major1, Minor1, Major2, Minor2, Major3, Minor3, Major4, Minor4, Major5, Minor5, Phot_rev, Surf_ft, Surf_m, Below_m, Angle, Riv_mile, Position, Coinc_ft, Desc2, Desc3, Desc4, Desc5. These items were removed for ease of querying the database since most records contained no values for these items. The items Desc1, Desc2, Desc3, Desc4, and Desc5 are verbal descriptions which correspond to the Major/Minor code pairs. GeoPlan added the 'DESCRIPT' item based on DESC1-DESC5 to represent the value that was most descriptive.
GeoPlan, during the QA/QC process included the following aspects: 1.) Converted from dlg to coverage 2.) Separated utm zone 16 from utm zone 17 3.) Mapjoined 16's and 17's with net option 4.) Used aml to joinitem pcode values to .pat and acode to .aat 5.) Added major and minor codes up to five in order to ensure proper mapjoin 6.) Build with poly option 7.) Set tolerances with settol then increased fuzzy to 2 8.) Dropfeatures line for coverage 9.) Dissolve to get rid of extraneous boundary lines 10.) Run aml that adds descriptions and other fields based on major/minor pairs 11.) Alter fields to make sure that they are not over 10 characters 12.) Set Tolerances to FGDL Standards 13.) Set Precision to Double 14.) Upcased Fields that had lower case character 15.) Added DESCRIPT item based on the major/minor pair that is most descriptive 16.) Removed all items except Desc1 and Descript 17.) Converted to Shapefile
Dataset copied.
Dataset copied.
Dataset copied.
Dataset copied.
Dataset copied.
Dataset copied.
Dataset copied.
Dataset copied.
Dataset copied.
Dataset copied.
Dataset copied.
Dataset copied.
Dataset copied.
Dataset copied.
Dataset copied.
Dataset copied.
Dataset copied.
Dataset copied.
Dataset copied.
Dataset copied.
Dataset copied.
Dataset copied.
Dataset copied.
Dataset copied.
Dataset copied.
Dataset copied.
Dataset copied.
Dataset copied.
Dataset copied.
Dataset copied.
Internal feature number.
ESRI
Data attribute inherent to the ESRI shapefile format, which defines the data as a point, polyline, or polygon.
FGDL
431 Architecture PO Box 115706
THE FGDL DATA AS PROVIDED BY CONTRIBUTING ORGANIZATIONS AND ANY PROGRAMMING SOFTWARE CREATED BY THE UNIVERSITY OF FLORIDA GEOPLAN CENTER (COLLECTIVELY THE 'MATERIALS') ARE COPYRIGHTED BY THE UNIVERSITY OF FLORIDA GEOPLAN CENTER FOR THE FGDL CONTRIBUTING AGENCIES AND ORGANIZATIONS (THE 'DATA PROVIDERS'). DO NOT REPRODUCE, REDISTRIBUTE OR RESELL THE MATERIALS, OR PROVIDE THE MATERIALS FOR FREE TO CUSTOMERS OR CLIENTS, OR PLACE THE MATERIALS FOR DOWNLOAD ON A WEBSITE. ADDITIONALLY, WHEN USING FGDL DATA OR SOFTWARE IN PROJECTS, MAPS, ETC.; YOU AGREE TO ACKNOWLEDGE THE FGDL AS A DATA SOURCE. THE MATERIALS ARE PROVIDED AS IS.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 MAKES NO WARRANTIES, GUARANTIES OR REPRESENTATIONS AS TO THE TRUTH, ACCURACY OR COMPLETENESS OF THE DATA PROVIDED BY THE FGDL CONTRIBUTING ORGANIZATIONS. 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.
507 National Center