University of Florida GeoPlan Center 20150101 SHAPE Gainesville, FL University of Florida GeoPlan Center State of Florida www.fgdl.org 1990 This dataset contains the boundaries of Florida's 67 counties. The interior county boundaries are from the US Census Bureau's TIGER data. The coastal boundaries are generalized and are used by Florida Department of Transportation's Efficient Transportation Decision Making (ETDM) process for display purposes. GeoPlan maintains 3 county boundary layers: COUNTYSHORE_AREAS, CNTBND, and COUNTY. These 3 layers will all have the same interior boundaries and different coastal boundaries. The interior boundaries come from the MAF/TIGER Database that is updated yearly by the US Census Bureau. The coastal boundaries differ in the following way: 1) COUNTYSHORE_AREAS - FWRI's detailed shoreline layer (updated periodically) 2) CNTBND - moderately generalized shoreline designed for ETDM display, sourced from historic US Census Bureau data 3) COUNTY - highly generalized shoreline designed for ETDM display, sourced from historic US Census Bureau data This dataset provides location and attribute information on all 67 of Florida's counties. 19900101 20150901 publication date Complete As needed -87.639356 -79.812215 31.042637 24.354695 None planningCadastre boundaries ISO 19115 Topic Categories boundaries planningCadastre None Southeast United States Southeast U.S Florida None 2000 None 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 University of Florida GeoPlan Center GIS Staff mailing

431 Arch Building

Gainesville FL 32611 US n/a n/a FGDL Mailing Lists: http://www.fgdl.org/fgdl-l.html Technical Support: http://www.fgdl.org/fgdlfeed.html For FGDL Software: http://www.fgdl.org/software.html FGDL Frequently Asked Questions: http://www.fgdl.org/fgdlfaq.html Version 6.2 (Build 9200) ; Esri ArcGIS 10.7.1.11595 USCB Tiger: https://www.census.gov/geo/maps-data/data/tiger-line.html GeoPlan relied on the integrity of the attribute information within the original data. Previous inconsistencies in previous versions of the county borders of Hernando, Sumter, Polk, and Osceola counties have been corrected. Since the last version of this datasets release, Dade County has changed its name from DADE to MIAMI-DADE. The new FIPS county code for Miami-Dade is 86; its previous FIPS code was 13. The FGDL Code has remained the same: C13. Certain node/geometry and topology (GT)-polygon/chain relationships are collected or generated to satisfy topological requirements. Some of these requirements include: chains must begin and end at nodes, chains must connect to each other at nodes, chains do not extend through nodes, left and right GT-polygons are defined for each chain element and are consistent throughout the transfer, and the chains representing the limits of the file (neatline) are free of gaps. The neatline is generated by connecting the four corners of the digital file, as established during initialization of the digital file. All data outside the enclosed region are ignored and all data crossing these geographically straight lines are clipped at the neatline. (Exception: During the QA/QC process all data is examined and if errors are found and corrections are possible, then data is corrected accordingly. This process is documented in the Process_Step.) Data within a specified tolerance of the neatline are snapped to the neatline. Neatline straightening aligns the digitized edges of the digital data with the generated neatline, that is, with the longitude/latitude lines in geographic coordinates. All internal polygons are tested for closure. Certain attributes and/or entities, e.g. closure line, convey data quality information. When information to be encoded in the subfield is known to be not applicable (undefined, not relevant), then the subfield is valued by a string of "9s"; and when the information to be encoded is relevant but unknown (or missing), then the subfield is valued by a string of "9s." 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 UNITED STATES CENSUS BUREAU-TIGER/Line Files unknown vector digital data http://www.census.gov/ftp/pub/geo/www/tiger 100000 onLine 19900101 19900101 Ground conditions GeoPlan Spatial and Attribute Information This layer is made up of 2 sources. 1) The interior county lines are derived from the latest TIGER county boundary. This can be downloaded here: ftp://ftp2.census.gov/geo/tiger/TIGER2015/COUNTY/ 2) The coastal boundary was taken from COUNTY. Major changes to boundaries include the following: Martin/St. Lucie Other minor changes can be seen around the state because of the new method of replacing all interior boundaries with the latest TIGER data. In past versions of CNTBND only the major changes were made. Python script county_boundaries.py was used to do the following: -Used Dissolve, Intersect, and Spatial Join command to replace interior boundaries with updated TIGER boundaries -Add TIGERNAME field based on county name in TIGER data -Add DESCRIPT field based on county name -Add FGDLAQDATE based on date acquired from source GeoPlan 20151119 Vector GT-polygon composed of chains 67 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 COUNTY_SEP15 COUNTY_SEP15.DBF USCB OBJECTID Internal feature number. ESRI Sequential unique whole numbers that are automatically generated. Shape Feature geometry. ESRI Coordinates defining the features. TIGERNAME County name taken from TIGER data. TIGER NAME County Name GeoPlan DESCRIPT GeoPlan added field based on NAME GeoPlan FGDLAQDATE Date GeoPlan acquired data from source. 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) mailing

431 Architecture PO Box 115706

Gainesville Florida 32611-5706 US Web site: http://www.fgdl.org For FGDL Software: http://www.fgdl.org/software.html FGDL Frequently Asked Questions: http://www.fgdl.org/fgdlfaq.html Mailing list for FGDL: http://www.fgdl.org/fgdl-l.html Technical Support: http://www.fgdl.org/fgdlfeed.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 20200303 University of Florida GeoPlan Center GIS Staff physical

431 Arch Building

Gainesville FL 32611 n/a n/a FGDL Frequently Asked Questions: http://www.fgdl.org/fgdlfaq.html For FGDL Software: http://www.fgdl.org/software.html Technical Support: http://www.fgdl.org/fgdlfeed.html FGDL Mailing Lists: http://www.fgdl.org/fgdl-l.html FGDC Content Standard for Digital Geospatial Metadata FGDC-STD-001-1998 local time