This dataset has been updated from the previous version on FGDL 3.0.
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.
This data set comes from the USGS revised DLG ftp site. There are two hydrography datasets: HY24P and HY24L. Hy24P has polygon features and HY24L has line features.
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.
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 poly 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 characters
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