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>
Specification of offshore, coastal and Great Lake network nodes and links on NOAA, followed by direct digitization of specified nodes and links. Process Date: 1995
Merging of inland and offshore waterway networks. A specialized program was written to merge the two networks. In general, Vanderbilt node locations were accepted as authoritative when both data sets had the same elements. This meant moving an Oak Ridge link incident to that node. If the link was classified geographically ocean or Great Lakes, and a Vanderbilt link or chain existed with the same ID and endpoints, the Oak Ridge link was discarded, after transfer of Oak Ridge attributes. If the Oak Ridge link was within 2 km of the new end nodes' location: and 1) if a duplicate Vanderbilt link existed with a higher source code, it replaced the Oak Ridge link, or 2) the Oak Ridge link was moved by a logistic adjustment to the new location. (This causes modest disruption to the preponderance of the shape, yet assured that the angle of approach to the displaced end node location was preserved.) If the link was functionally classed "deep draft" and a duplicate Vanderbilt link had an authoritative source code, the Oak Ridge link was replaced. Otherwise an additional shape point was added at the end to snap to the new node location without disrupting the original link shape. If the link had a Vanderbilt duplicate with the same ID, the Oak Ridge link was so flagged to be manually resolved. The composite network was then cleaned manually, resolving all cases of still remaining duplicate links and deciding case-by-case how to smooth or otherwise accommodate a highly displaced Oak Ridge shape into the Vanderbilt digitized node location, using TIGER shorelines as a background. Process Date: 1994
Heads-up digitizing of WWAY10 to add shape points to inland waterways where straight links still existed. Incorporation of comments from users (Vanderbilt, ORNL, and USACE Waterborne Commerce Statistics Center) of WWAY10 and error correction. Process Date: 1995
Upgrades to link shape and attribute data based on information from US Army Corps of Engineers CWIS projects as published in their digital projects notebook. Includes the addition of new links, removal of unnecessary links/nodes, and splitting of links to more effectively relate the digital waterway network to the physical network as maintained by the Corps of Engineers. Process Date: 1999
GeoPlan, during the QA/QC process included the following aspects: 1.) Clipped the dataset to the State of Florida boundary 2.) Reprojected data to FGDL Albers HPGN 3.) DESCRIPT added to attribute table based on SYSTEM 4.) FGDLAQDATE field added to attribute table 5.) Upcased all character records