Name: Planned Developments (PDs)

Display Field: NAME

Type: Feature Layer

Geometry Type: esriGeometryPolygon

Description: According to SECTION 2.125-M: PLANNED DEVELOPMENT (PD) of the Polk County Comprehensive Plan:SECTION 2.125-M: PLANNED DEVELOPMENT (PD) - The Polk County Comprehensive Plan establishes the Planned Development as a mechanism for increasing densities and intensities that may be permitted under certain circumstances, or using innovative design techniques, or providing a mixture of land uses. Planned Development may also be used to gain project design flexibility and to attach conditions where warranted. Planned Development shall comply with density bonus points as outlined in the Land Development Code. Planned Development also exists under different names in certain districts for different purposes such as:Suburban Planned Development (SPD) in the Residential Suburban Land Use designation pursuant to Policy 2.120-B;Rural-Residential Development (RRD) in the Agricultural/Residential-Rural (A/RR) Land Use designation pursuant to Policy 2.121-B;Rural Mixed-Use Development (RMD) in the Agricultural/Residential-Rural (A/RR) Land Use designation pursuant to Policy 2.121-C; Transitional Areas, pursuant to Policy 2.125-C; and Residentially Based, Mixed-Use Developments pursuant to Policy 2.125-H.According to Chapter 3 – Planned Developments within the Land Development Code:The Polk County Land Development Code establishes the Planned Development process as a mechanism for increasing densities and intensities which may be permitted under certain circumstances or using innovative design techniques. Planned Development may also be used to gain project design flexibility and to attach conditions where warranted. Planned Development exist under different names in certain districts. Refer to the following Sections:Section 303 Bfor Suburban Planned Developments in the Residential Suburban District.Section 303 Bfor Residentially Based Mixed‑Use Development for mixed‑use development in residential districts.Section 303 Bfor Residential Mixed‑Use Development in the Agricultural/Residential Rural (A/RR) district for mixed‑use developments and residential developments over 160 acres.Section 303 Bfor Rural Residential Development in the Agricultural/Residential Rural (A/RR) for strictly residential developments of under 160 acres.Additional policies throughout the Polk County Comprehensive Plan and Land Development Code provide guidance for development all types of planned Developments within the un-incorporated areas of Polk County. This is one dataset used to support both the Comprehensive Plan and Land Development Code. This data must be interpreted in conjunction with the other data and maps along with the objectives and policies of the “Polk County Comprehensive Plan” and “Polk County Land Development Code” as adopted and amended by the Polk County Board of County Commissioners. The most current documents can be viewed on the county's website at http://www.polk-county.net/compplanand http://www.polk-county.net/ldc.

Service Item Id: f332e34b00254644811574fc0b620746

Copyright Text: Last update - April 9, 2015. Polk County GIS/IT Division and Polk County Office of Planning and Development

Default Visibility: false

MaxRecordCount: 2000

MaxSelectionCount: 2000

Supported Query Formats: JSON, geoJSON, PBF

Min Scale: 0.0

Max Scale: 0.0

Supports Advanced Queries: true

Supports Statistics: true

Has Labels: false

Can Modify Layer: true

Can Scale Symbols: false

Use Standardized Queries: true

Supports Datum Transformation: true

Extent:

XMin: 640868.7566833682
YMin: 1217764.8071270287
XMax: 850253.3895823732
YMax: 1458913.5398956165
Spatial Reference: 102659  (2237)  LatestVCSWkid(0)

Drawing Info:

Renderer:
Simple Renderer:
Symbol:
Style: esriSFSVertical
Color: [0, 0, 0, 255]
Outline:
Style: esriSLSSolid
Color: [0, 0, 0, 255]
Width: 1
Label: N/A
Description: N/A
Transparency: 0
Labeling Info:

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: false
Supports Returning Geometry Centroid: false
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: true
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: null

Fields:

• OBJECTID ( type: esriFieldTypeOID, alias: OBJECTID )
• NAME ( type: esriFieldTypeString, alias: NAME, length: 30 )
• STATUS ( type: esriFieldTypeString, alias: STATUS, length: 30 )
• NUM ( type: esriFieldTypeInteger, alias: NUM )
• STR ( type: esriFieldTypeString, alias: STR, length: 64 )
• DESC_ ( type: esriFieldTypeString, alias: DESC_, length: 64 )
• YEAR_ ( type: esriFieldTypeInteger, alias: YEAR_ )
• PD ( type: esriFieldTypeString, alias: PD, length: 50 )
• ACRES ( type: esriFieldTypeDouble, alias: ACRES )
• Shape ( type: esriFieldTypeGeometry, alias: Shape )
• Shape.STArea() ( type: esriFieldTypeDouble, alias: Shape.STArea() )
• Shape.STLength() ( type: esriFieldTypeDouble, alias: Shape.STLength() )

Supported Operations:   Query   Query Attachments   Query Analytic   Generate Renderer   Return Updates

  Iteminfo   Thumbnail   Metadata