View In:   ArcGIS Online Map Viewer

Name: CountyLimits

Display Field: NAME

Type: Feature Layer

Geometry Type: esriGeometryPolygon

Description: This boundary line is described as follows in the Florida Statutes, Chapter 7.29:"Hillsborough County.—The boundary lines of Hillsborough County are as follows: Beginning at the northeast corner of section one in township twenty-seven south, range sixteen east; thence east on the north line of township twenty-seven south to the line between ranges twenty-two and twenty-three east; thence south on said range line to the line between townships thirty-two and thirty-three south; thence west on said township line to the south bank of Tampa bay; thence in a direct line to a point midway between Egmont and Passage Keys in the Gulf of Mexico; thence westerly to the boundary of the State of Florida; thence northerly on the boundary of the State of Florida to a point in the Gulf of Mexico due west of the northern shore of Mullet Key; thence due east to a point one hundred yards due west of the northernmost shore of Mullet Key; thence in a line one hundred yards from the shore line around the southern portion of Mullet Key to a point one hundred yards due east of the easternmost shore of Mullet Key; thence due north to a point due east of the northernmost shore of Mullet Key; thence due east to the middle waters of Tampa Bay; thence in a northerly direction through the middle waters of Tampa Bay and Old Tampa Bay to a point where the range line between ranges sixteen and seventeen east strikes said shore; thence north on said range line to the place of beginning."Additional Notes: The west, north, east, and south inland boundary lines were made coincident to an internal public land survey system (PLSS) layer, which was derived from survey CAD files. The township lines contain a vertex, or change of direction, at every half-mile and the county boundary line follows the same methodology. In areas crossing water, the boundary follows the Florida Statutes description; however, where there is no specific direction given through the Tampa Bay Waters, the boundary line was drawn approximately in the middle waterways between Hillsborough and Pinellas. During the review process, the following resources were referenced: historical Hillsborough County imagery (1938, 1942, 1943, 1951, 1957, 1984), NAIP imagery (2021/2022), U.S. Coast and Geodetic Survey Coast Chart #77 (1879), Tri-County Map of Tampa Bay Area (1959), Pinellas County Land Survey Report (1985).This layer was submitted to the Census Bureau in May 2025 for the annual Boundary & Annexations Survey

Copyright Text: Hillsborough County Information & Innovation Office, Performance, Data, & Analytics Department, Geospatial Services Division, Applied GIS Section, Florida Statute 7.29

Default Visibility: true

MaxRecordCount: 2000

MaxSelectionCount: 0

Supported Query Formats: JSON, geoJSON, PBF

Min Scale: 0.0

Max Scale: 0.0

Supports Advanced Queries: true

Supports Statistics: true

Can Scale Symbols: false

Use Standardized Queries: true

Supports ValidateSQL: true

Supports Calculate: true

Supports Datum Transformation: true

Extent:

XMin: 353255.15504282713
YMin: 1163228.2431365699
XMax: 638614.2657539137
YMax: 1396325.4245790765
Spatial Reference: 102659  (2237)  LatestVCSWkid(0)

Drawing Info:

Renderer:
Simple Renderer:
Symbol:
Style: esriSFSSolid
Color: [252, 201, 218, 255]
Outline:
Style: esriSLSSolid
Color: [110, 110, 110, 255]
Width: 0
Label: N/A
Description: N/A
Transparency: 0
Labeling Info:

Feature Draw Order:

N/A

Advanced Query Capabilities:

Supports Statistics: true
Supports OrderBy: true
Supports Distinct: true
Supports Pagination: true
Supports TrueCurve: true
Supports Returning Query Extent: true
Supports Query With Distance: true
Supports Sql Expression: true
Supports Query With ResultType: true
Supports Returning Geometry Centroid: true
Supports Binning LOD: false
Supports Query With LOD Spatial Reference: false
Supports Percentile Statistics: true
Supports Having Clause: true
Supports Count Distinct: true
Supports Time Relation: false
Supports Sql Format: false
Supports Query Analytic: true
Supports Query With Current User: true

HasZ: false

HasM: false

Has Attachments: false

HTML Popup Type: esriServerHTMLPopupTypeAsHTMLText

Type ID Field:

Fields:

• OBJECTID ( type: esriFieldTypeOID, alias: OBJECTID, editable: false, nullable: false, defaultValue: null, modelName: OBJECTID )
• StateFipsCode ( type: esriFieldTypeString, alias: StateFipsCode, editable: true, nullable: true, length: 2, defaultValue: null, modelName: StateFipsCode )
• CountyFipsCode ( type: esriFieldTypeString, alias: CountyFipsCode, editable: true, nullable: true, length: 3, defaultValue: null, modelName: CountyFipsCode )
• CountyNationalStandardCode ( type: esriFieldTypeString, alias: CountyNationalStandardCode, editable: true, nullable: true, length: 8, defaultValue: null, modelName: CountyNationalStandardCode )
• GeographicIdentifier ( type: esriFieldTypeString, alias: GeographicIdentifier, editable: true, nullable: true, length: 5, defaultValue: null, modelName: GeographicIdentifier )
• Name ( type: esriFieldTypeString, alias: Name, editable: true, nullable: true, length: 50, defaultValue: null, modelName: Name )
• AreaDescriptionName ( type: esriFieldTypeString, alias: AreaDescriptionName, editable: true, nullable: true, length: 50, defaultValue: null, modelName: AreaDescriptionName )
• Shape__Area ( type: esriFieldTypeDouble, alias: SHAPE.STArea(), editable: false, nullable: true, defaultValue: null, modelName: SHAPE.STArea(), required: true )
• Shape__Length ( type: esriFieldTypeDouble, alias: SHAPE.STLength(), editable: false, nullable: true, defaultValue: null, modelName: SHAPE.STLength(), required: true )

Templates:

• Name: CountyLimits
  Description:
  Prototype:
  AreaDescriptionName: null
  Name: null
  StateFipsCode: null
  CountyFipsCode: null
  CountyNationalStandardCode: null
  GeographicIdentifier: null
  
  Drawing Tool: esriFeatureEditToolPolygon

Capabilities: Query

Sync Can Return Changes: false

Is Data Versioned: false

Supports Rollback On Failure: true

Supports ApplyEdits With Global Ids: false

Supports Query With Historic Moment: false

Supports Coordinates Quantization: true

Child Resources:

Supported Operations:   Query   Query Analytic   Append   Validate SQL   Generate Renderer   Return Updates   Iteminfo   Thumbnail   Metadata