University of Florida GeoPlan Center 20040101 vector digital data State of Florida http://www.fgdl.org The Public Land Survey System (PLSS) is a legal land reference system created to facilitate the inventory and transfer of property. This system is divided into township, range, and sections. This shapefile contains PLSS boundaries to the township and range level. Further PLSS data down to the section level can be found on the FGDL website. This dataset was created by GeoPlan using data from the Bureau of Land Management (BLM) combined with existing PLSS data to fill in known gaps. This polygon shapefile was created to facilitate the inventory and transfer of property. 20040101 publication date Complete As needed -87.725923 -79.869136 31.130290 24.519656 None planningCadastre None TRS PLSS Townships Ranges ISO 19115 Topic Categories planningCadastre None Florida None THE DATA INCLUDED IN FGDL ARE 'AS IS' AND SHOULD NOT BE CONSTRUED AS LEGALLY BINDING. 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. A note about data scale: 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: Florida Geographic Data Library (FGDL) GIS Specialist Data Manager mailing

431 Architecture PO Box 115706

Gainesville Florida 32611-5706 Mailing list for FGDL: http://www.fgdl.org/fgdl-l.html For FGDL Software: http://www.fgdl.org/software.html FGDL Frequently Asked Questions: http://www.fgdl.org/fgdlfaq.html Technical Support: http://www.fgdl.org/fgdlfeed.html Web site: http://www.fgdl.org Version 6.2 (Build 9200) ; Esri ArcGIS 10.7.1.11595 GeoPlan relied on the integrity of the attribute information within the original data. This data set was modified by GeoPlan center in 2002 using GIS techniques to summarize sections. This eliminated many slivers and drastically reduced the size of the dataset. This causes the county boundary field in the shapefile to be slightly inaccurate. Sections that cross over county boundary lines will only get one county name. This data set documents how the original PLSS looked when it was created in the early 1800's. This, along with the original field notes, serve as the documentation for many legal boundaries in Florida. These boundaries are set and the data layer will not change. 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. This data is provided 'as is' and its horizontal positional accuracy has not been verified by GeoPlan This data is provided 'as is' and its vertical positional accuracy has not been verified by GeoPlan SUWANNEE RIVER WATER MANAGEMENT DISTRICT SOUTH FLORIDA WATER MANAGEMENT DISTRICT ST. JOHN'S RIVER WATER MANAGEMENT DISTRICT FLORIDA RESOURCES & ENVIRONMENTAL ANALYSIS CENTER SOUTH WEST FLORIDA WATER MANAGEMENT DISTRICT 0 None GeoPlan Spatial and Attribute Information The original data was in both DLG and Coverage format depending on the source. Source data was converted to coverage. The data then existed in previous versions of FGDL (i.e. FGDL V3 or less) as county data sets. The coverages were merged together. Next the eliminate command was run in ArcInfo Workstation. Then the Coverage was converted to a shapefile and a dissolve was executed. The dissolve was used in order to change all sections with multiple polygons into one section. unknown This dataset was created by GeoPlan using information from two sources, the Bureau of Land Management (BLM) Public Land Survey System (PLSS) Data Download and the Florida Geographic Data Library (FGDL). The first layer, from the BLM, contained data on the township and range level. However, this dataset had a few gaps across the state. These holes were filled in using the layer from FGDL. This layer had more detailed information, breaking the townships and ranges into sections. These sections were dissolved, using the ArcMap tool, into the larger townships and ranges so that they would match the data from the BLM. The BLM layer was projected into the projection type matching the FGDL layer, FGDL Albers. After the FGDL layer was dissolved on township and range, the features from the FGDL layer that filled in the holes found in the BLM layer were selected and exported to a new layer. Some spatial discrepancy was present between the two layers, even though both had the same projection information (the BLM layer was projected into the correct projection), FGDL Albers. To repair these discrepancies, the layer from FGDL was edited using the Spatial Adjustment tool in conjunction with the Editor toolbar. The specific Spatial Adjustment method used was Rubbersheet. The rubbersheet process followed these steps: - Start an edit session, select the proper layer to edit, in this case the FGDL layer - Ensure the Spatial Adjustment toolbar is present on the toolbar section - In the Spatial Adjustment menu, hover over "Adjustment Method" and click "Rubbersheet" - In the Spatial Adjustment menu, click on "Set Adjust Data...", click "All features in these layers" and ensure the only layer being altered (the FGDL layer) is selected, click "OK" - Make sure the Snapping toolbar is present and is set to snap to vertexes, and not to edges - Now that all the preliminary settings are in place, select vertices from the FGDL layer and move them to the nearest vertex from the BLM layer - Periodically, in the Spatial Adjustment menu, click "Adjust" to move the vertices to the new locations selected and save edits to ensure work is not lost After the Rubbersheet process was completed for all features of the layer where edits were necessary, the Integrate tool was used. This tool ensures that micro-scale discrepancies between polygon boundaries are repaired so they are right on top of each other. In the Integrate tool, two layers were used to repair the gaps, one with the features created by BLM and one with features created by GeoPlan. The BLM layer was ranked first and the GeoPlan layer was ranked second. The distance threshold was 0.5 meters. The GeoPlan layer was then merged with the non-integrated BLM data to ensure that no points were altered from the BLM data. This created the final layer. Then, the attribute information had to be edited using Xtools so that the merge could be completed effectively. After the merge, attribute information was cleaned so that it met GeoPlan's requirements. Fields were added, edited, or deleted so that the current fields are: FID, Shape, TOWN, TOWN_DIR, RANGE, RANGE_DIR, LABEL, F_SOURCE, DATEMODIFI, DATECREATE, FGDLAQDATE, DESCRIPT. All of the records were upcased. GeoPlan 20160308 Vector GT-polygon composed of chains 1892 NAD 1983 HARN Florida GDL Albers 24.0 31.5 -84.0 24.0 400000.0 0.0 coordinate pair 0.0001 0.0001 meter D North American 1983 HARN GRS 1980 6378137.0 298.257222101 PLSS_TR_2004 PLSS_TR_2004.DBF GeoPlan OBJECTID Internal feature number. ESRI Sequential unique whole numbers that are automatically generated. Shape Feature geometry. ESRI Coordinates defining the features. TOWN Township Number GeoPlan TOWN_DIR Township Direction (N=North, S=South) GeoPlan RANGE Range Number GeoPlan RANGE_DIR Range Direction (E= East, W=West) GeoPlan LABEL GeoPlan added field combining Township, Township Direction, Range, and Range Direction GeoPlan F_SOURCE Source of Feature Information GeoPlan DATEMODIFI Undefined by source BLM DATECREATE Undefined by source BLM FGDLAQDATE The date GeoPlan acquired the data from the source GeoPlan DESCRIPT GeoPlan added field based on LABEL GeoPlan AUTOID Unique ID added by GeoPlan GeoPlan SHAPE.AREA Area in meters GeoPlan SHAPE.LEN Perimeter in meters GeoPlan Florida Geographic Data Library (FGDL) GIS Specialist Data Manager mailing

431 Architecture PO Box 115706

Gainesville Florida 32611-5706 US FGDL Frequently Asked Questions: http://www.fgdl.org/fgdlfaq.html Web site: http://www.fgdl.org For FGDL Software: http://www.fgdl.org/software.html Technical Support: http://www.fgdl.org/fgdlfeed.html Mailing list for FGDL: http://www.fgdl.org/fgdl-l.html DOWNLOADABLE DATA The Florida Geographic Data Library is a collection of Geospatial Data compiled by the University of Florida GeoPlan Center with support from the Florida Department of Transportation. GIS data available in FGDL is collected from various state, federal, and other agencies (data sources) who are data stewards, producers, or publishers. The data available in FGDL may not be the most current version of the data offered by the data source. University of Florida GeoPlan Center makes no guarantees about the currentness of the data and suggests that data users check with the data source to see if more recent versions of the data exist. Furthermore, the GIS data available in the FGDL are provided 'as is'. 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 data sources. 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 shall not be liable for any damages suffered as a result of using, modifying, contributing or distributing the materials. 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 20200302 University of Florida GeoPlan Center mailing

Florida State University

131 Architecture PO Box 115706

UCC 2200

Gainesville FL 32611-5706 US maps@admin.fsu.edu data@fgdl.org FGDC Content Standard for Digital Geospatial Metadata FGDC-STD-001-1998 local time