CITY LIMITS - DERIVED FROM FLORIDA PARCEL DATA - 2017

www.fgdl.org

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

Spatial and Attribute Information

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 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 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 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 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 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.

Dataset copied.

Internal feature number.

ESRI

Feature geometry.

ESRI

2010 ANSI Codes for Places - Place or county subdivision FIPS code.

Census - ANSI

Code given to cities for use by BEBR.

GeoPlan

Name of the City, or Municipality, represented.

GeoPlan

County in which city is located.

GeoPlan

Number of tax code numbers used to derive city limit.

GeoPlan

Value associated with the tax code # as defined by the DOR parcel data field 'TAXAUTHCD'.

GeoPlan

Notes containing information about city limit.

GeoPlan

Acres.

GeoPlan

Based on the field NAME.

GeoPlan

The date GeoPlan acquired the data from the Source.

GeoPlan

Unique ID added by GeoPlan

GeoPlan

Area in meters

GeoPlan

Perimeter in meters

GeoPlan