University of Florida GeoPlan Center 20191231 vector digital data Gainesville, FL University of Florida GeoPlan Center State of Florida www.fgdl.org This dataset contains city limits for the State of Florida. The data was compiled by the GeoPlan Center using tax code boundaries as defined in 2018 county parcel data from the Florida Department of Revenue (FDOR). This dataset is an update to the city limits shapefile par_citylm_2017.shp. The data was created to serve as base information for use in GIS systems for a variety of planning and analytical purposes. 20181228 publication date Complete As needed -87.285935 -79.872828 31.034950 24.505737 None Limit Municipality City Limit City Boundary Tax Code None boundaries planningCadastre ISO 19115 Topic Category planningCadastre bondaries None Florida None 2017 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 mailing and physical

431 Architecture bldg., PO Box 115706

Gainesville Florida 32611-5706 US data@fgdl.org For FGDL Software: http://www.fgdl.org/software.html FGDL Mailing Lists: http://www.fgdl.org/fgdl-l.html Technical Support: http://www.fgdl.org/fgdlfeed.html FGDL Frequently Asked Questions: http://www.fgdl.org/fgdlfaq.html www.fgdl.org Florida Department of Revenue and the 67 - County Property Appraisers. Version 6.2 (Build 9200) ; Esri ArcGIS 10.7.1.11595 Florida Geographic Data Library: http://www.fgdl.org/ For Department of Revenue info: http://floridarevenue.com/property/Pages/DataPortal.aspx 2010 ANSI Codes for Places http://www2.census.gov/geo/docs/reference/codes/files/st12_fl_places.txt GeoPlan relied on the integrity of the attribute information within the original data. Relied on the integrity of the attribute information within the original data layer. This data is provided 'as is' by GeoPlan and is complete to our knowledge. 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 Florida Department of Revenue (FDOR) 20141006 vector digital data Tallahassee, FL Florida Department of Revenue (FDOR) http://www.fgdl.org 0 onLine 20150820 Unknown GeoPlan Spatial and Attribute Information GeoPlan made the following edits: Islandia - was obtained from GeoPlan's 2010 'CITYLM'. All data was merged, creating a Statewide city limits dataset. Currently there are several counties that have parcel datasets with less than 100 percent completion, for these counties the absence of based data results in the absence of city limit boundaries for those areas. The resulting derived city limit dataset can only be as accurate as the base dataset. The Census Place layer from the 2010 Census was used to help determine some of the boundaries where PARCELS WITH NO DATA where located. Additionally the features where each buffered by 8m using the Feature Outline Mask in ArcGIS 10, in order to help clean up some of the city limit boundaries. GeoPlan 20111226 GeoPlan Center Process Steps: #Step 1 #From parcels directory dissolve by county on the TAXAUTHCD - Multi-part #Export to C:\kate\dissolve_tax\step1 folder #Step 2 #Add AUTOID Field and Calc in Step1 Folder #Step 3 #Add COUNTY Field and Calc in Step1 Folder #Step 4 #Remove TAXAUTHCD = '' #This makes files smaller #Export to Step4 Folder #Step 5 #Create Statewide layer via description in python Step 5 Script #Step 6 #Create City Layers #Export to Step6 Folder #Step 7 #Multi-part to Single part for each city layer #Export to Step7 Folder #Step 8 #Simplify polygon by 1 meter #Export to Step8 Folder #Step 9 #Integrate 1 meter in same folder #Step 10 #Repair Geometry 2x in same folder #Step 11 #Aggregate polygons 65 meter #Export to Step11 Folder #Computer will hit maximum number of features during processing, #so perform this aggregation step 4 times. #Step 12 #Aggregate polygons 100 meter #Export to Step12 Folder #Step 13 #Polygon to line #Export to Step13 Folder #Step 14 #Feature to Polygon #Export to Step14 Folder #Step 15 #Dissolve on ID field #Export to Step15 Folder #Step 16 #Create and Calculate AUTOID_NUM field with layer name in same folder #Step 17 #Put all cities together statewide via append. #Step 18 #Find and Replace to get number in AUTOID_NUM field. #Step 19 #Calc ID Field as AUTOID_NUM number. #Step 20 #Dissolve Statewide based on ID Field. #Step 21 #Join PLACENAME AND COUNTY names back over based on #table join via the ID and the AGG_NUM from the table. #Step 22 #Add and Populated TAXAUTHCD field with listed comma delimitated format. #ArcTool Box - Spatial Join #Target (POLY), Join (TAXAUTHCD POINTS) # ONE TO ONE #ADD Field For Map #(TAXLIST) #Merge Rule - Join - Comma Space #Right Click TAXLIST - Add Input Field Select TAXAUTHCD GeoPlan 20111226 This dataset is derived from county parcel data that was released by the Florida Department of Revenue (FDOR) in the winter of 2010, the data released captured parcel information from 12-20-2010. Within the county parcel datasets is information regarding tax codes in the field 'TAXAUTHCD'. In this field, a value, or id number, is listed that corresponds to a city. Using this field and ArcMap 9.3, the tax code boundaries were mapped and classified according to this tax code id#. These tax code id# were then used in a series of GeoProcessing steps to derive a city limit layer. After the creation of these cities all data was appropriately named and then merged to make one statewide dataset. GeoPlan 20111226 GeoPlan updated the city limits layer using the following steps in 2015: - The existing boundaries of the 2011 city limits layer were compared to the Florida Department of Revenue (FDOR) 2014 county parcel data. - City limit boundary vertices were manually updated to reflect any parcels that had tax code changes by snapping the city boundary layer to the 2014 parcel layer. - Abutting city limit boundary vertices were manually adjusted to remove slivers and gaps between the adjoining polygons. - Estero was added as newly incorporated city. - Annexations were added for Cape Coral, Fort Myers and Bonita Springs - ACRES field was updated. - DESCRIPT field was added and is based on the field titled NAME - FGDLAQDATE field was created and calculated with the date GeoPlan last updated the data. - The record ISLANDIA was removed - Added portion of MARINELAND that is within St. John's county - Joined BEBR ID data and Census PLACEFP data (http://www.census.gov/geo/reference/codes/place.html) - NOTE: The cities of Fanning Springs, Flagler Beach, Long Boat Key and Marineland are all listed twice because they each lie within in two different counties. GeoPlan 20150813 GeoPlan updated the city limits layer using the following steps in 2016: - The existing boundaries of the 2014 city limits layer were compared to the Florida Department of Revenue (FDOR) 2015 county parcel data. - City limit boundary vertices were manually updated to reflect any parcels that had tax code changes by snapping the city boundary layer to the 2015 parcel layer. - Abutting city limit boundary vertices were manually adjusted to remove slivers and gaps between the adjoining polygons. - Annexations were added for the following cities based on data obtained from BEBR: Altamonte Springs, Atlantis, Auburndale, Avon Park, Belleview, Bradenton, Brooksville, Bushnell, Callaway, Casselberry, Clearwater, Clermont, Cocoa, Crestview, Deland, Dundee, Dunedin, Edgewater, Eustis, Fernandina Beach, Fort Pierce, Fort Walton Beach, Greenacres, Groveland, Kissimmee, Lady Lake, Lake City, Leesburg, Longwood, Lynn Haven, Melbourne, Mount Dora, New Smyrna Beach, Niceville, Oak Hill, Ocoee, Oldsmar, Orange City, Orlando, Ormond Beach, Palatka, Panama City, Pinellas Park, Punta Gorda, Royal Palm Beach, Sanford, Sebring, Seminole, St. Augustine, St. Cloud, St. Lucie Village, Tarpon Springs, Tavares, Temple Terrace, Umatilla, Village of Palm Springs, Wauchula, West Melbourne, West Palm Beach, Wildwood, Winter Garden. - DESCRIPT field was calculated based on the field titled NAME. - FGDLAQDATE field was calculated with the date GeoPlan last updated the data. GeoPlan 20161021 GeoPlan updated the city limits layer using the following steps in 2018: - The existing boundaries of the 2015 city limits layer were compared to the Florida Department of Revenue (FDOR) 2017 parcel data. - City limit boundary vertices were manually updated to reflect any parcels that had tax code changes by snapping the city boundary layer to the 2017 parcel layer. - Abutting city limit boundary vertices were manually adjusted to remove slivers and gaps between the adjoining polygons. - If not already reflected in tax codes, annexations were added based on data obtained from the Bureau of Economic and Business Research (BEBR) (2777 parcels total). - Added NOTES field. - ACRES field calulated. - DESCRIPT field was calculated based on the field titled NAME. - FGDLAQDATE field was calculated with the date GeoPlan last updated the data. GeoPlan 20180531 GeoPlan updated the city limits layer using the following steps in 2019: - The existing boundaries of the 2017 city limits layer were compared to the Florida Department of Revenue (FDOR) 2018 parcel data. - City limit boundary vertices were manually updated to reflect any parcels that had tax code changes by snapping the city boundary layer to the 2018 parcel layer. - In some cases, boundaries were checked against pdf maps, webmaps, or spatial datasets accessed/downloaded from city or county websites. These sources were included in the NOTES field. - The recently incorporated cities of Indiantown and Westlake were added to the layer. - The recently disincorporated city of Hastings was removed from the layer. - Abutting city limit boundary vertices were manually adjusted to remove slivers and gaps between the adjoining polygons. - If not already reflected in tax codes, annexations were added based on data obtained from the Bureau of Economic and Business Research (BEBR). - In previous city limits layers, cities spanning multiple counties were added as seperate features (1 for each county). In this layer, cities spanning multiple counties were combined into one feature and all counties were listed in the COUNTY field. This brought the total record count from 416 to 412. - Added NOTES field. - ACRES field calulated. - DESCRIPT field was calculated based on the field titled NAME. - FGDLAQDATE field was calculated with the date GeoPlan last updated the data. GeoPlan 20191231 Vector GT-polygon composed of chains 412 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 PAR_CITYLM_2018 PAR_CITYLM_2018.DBF GeoPlan Center OBJECTID Internal feature number. Esri Sequential unique whole numbers that are automatically generated. Shape Feature geometry. ESRI Coordinates defining the features. PLACEFP 2010 ANSI Codes for Places - Place or county subdivision FIPS code. Census - ANSI BEBR_ID Code given to cities for use by BEBR. GeoPlan NAME Name of the City, or Municipality, represented. GeoPlan COUNTY County in which city is located. GeoPlan TAX_COUNT Number of tax code numbers used to derive city limit. GeoPlan TAXAUTHCD Value associated with the tax code # as defined by the DOR parcel data field 'TAXAUTHCD'. GeoPlan NOTES Notes containing information about city limit. GeoPlan ACRES Acres. GeoPlan DESCRIPT Based on the field NAME. GeoPlan FGDLAQDATE The date GeoPlan acquired the data from the Source. GeoPlan AUTOID SHAPE.AREA SHAPE.LEN Florida Geographic Data Library (FGDL) mailing

431 Architecture PO Box 115706

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

431 Architecture bldg., PO Box 115706

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