Name: Provo Zoning

Display Field: ZONE

Type: Feature Layer

Geometry Type: esriGeometryPolygon

Description: Feature class edit log:'Ordinance 2008-01: added Feb 12, 2008 (SC3)Ordinance 2008-03: added Feb 12, 2008 (RAPD)Ordinance 2008-09: added May 15, 2008 (SDP4)Ordinance 2008-12: added May 15, 2008 (PRO-A20)Ordinance 2008-13: added May 15, 2008 (PF)Ordinance 2008-14: added May 15, 2008 (R18)Ordinance 2008-18: added May 15, 2008 (R110)Ordinance 2008-26: added August 27, 2008 (PRO-A20)Ordinance 2008-27: added August 27, 2008 (RC)Ordinance 2008-28: added August 27, 2008 (FI)Ordinance 2008-30: added November 12, 2008 (R16A)Ordinance 2008-32: added November 12, 2008 (RC)Ordinance 2008-35: added? (Repeal of PRO zone)Ordinance 2008-36: added November 12, 2008 (RC)'Zone Map correction - January 26, 2009: The R110PD rezone at the Stone Gate development was not drawn properly (2000-20 - effective May 28, 2000). A portion on the east-southeast side was not rezoned to R110PD from A15 as it should have been. Also, a small adjacent area south was not changed from A15 to R110PD as was an area around the northeast entrance.'Ordinance 2008-41: added February 3, 2009 (PRO-R22)Ordinance 2008-43: added February 4, 2009 (PRO-R23)Ordinance 2008-44: added February 4, 2009 (R17)Ordinance 2009-03: added March 4, 2009 (ITOD)Ordinance 2009-05: added March 5, 2009 (PRO-R24)Ordinance 2009-06: added March 5, 2009 (PF)Ordinance 2009-09: added March 18, 2009 (PF)Ordinance 2009-13: added March 19, 2009 (PF)Ordinance 2009-15: added ? (PRO-R25)Ordinance 2009-24: added June 10, 2009 (CG, R16)'Zone Map Correction - June 22, 2009: The rezone for the Waterford development at 4303 Foothill Dr (Ordinance 1999-33) was drawn according to parcel boundaries at the time rather than the legal description submitted to the Recorder's Office. The legal description boundary conforms to the plat map and what is built today. This correction results in an orphaned section of the old PF zone on the west side of the development.'Ordinance 2009-29: added August 20, 2009 (PRO-R26)Ordinance 2009-30: added August 24, 2009 (R18)Ordinance 2009-34: added October 13, 2009 (PRO-R27)Annexation Ordinance 2009-01: added November 3, 2009 (R120)Ordinance 2009-35: added November 3, 2009 (R120PD)Annexation Ordinance 2009-02: added November 3, 2009 (R120)Ordinance 2009-37: added November 4, 2009 (SDP5)Ordinance 2009-42: added January 12, 2010 (PRO-R28)Ordinance 2009-45: added January 12, 2010 (PRO-R29)'Zone Map Correction - February 17, 2010: The home at 1611 N JORDAN AVE was found to have been incorrectly placed in the PF zone covering Grandview Elementary School. Sometime after 1990 it appears within the PF zone, but there is no historical rezone data indicating any zone change. It was changed back to the adjacent R110 designation.'Annexation Ordinance 2010-01: added October 13, 2010 (R120)Ordinance 2010-16: added October 21, 2010 (PRO-R30)Ordinance 2010-31: added January 4, 2011 (FC, GW, DT1, DT2) 'Zone Map Correction: January 13, 2011: The SC3 zone at 5020 N on the west side of University Ave only covered part of the parcel directly north of 5020 N. It was determined by reviewing the historical rezone feature class that the boundary should have been extended to the north side of the parcel according to ordinance1999-45. 'Ordinance 2010-24: added February 14, 2011 (PRO-R31)Ordinance 2010-26: added February 15, 2011 (PRO-R32)Ordinance 2010-33: added February 15, 2011 (PRO-R33)Ordinance 2010-36: added February 15, 2011 (Boundary Line Adjustment with Orem)Ordinance 2010-37: added February 15, 2011 (PO)Ordinance 2011-22: added October 3, 2011 (PRO-R34)Ordinance 2011-23: added October 3, 2011 (A11)Ordinance 2011-25: added December 8, 2011 (M1)Ordinance 2012-03: added March 12, 2012 (CG)Ordinance 2012-10: added June 27, 2012 (RC)Ordinance 2012-29: added December 6, 2012 (DT1)Ordinance 2012-30: added December 6, 2012 (R16)Ordinance 2012-31: added December 6, 2012 (WG)Ordinance 2012-32: added December 10, 2012 (FC2)Ordinance 2012-37: added December 10, 2012 (LDR)Ordinance 2012-39: added December 10, 2012 (CG)Ordinance 2012-40: added December 10, 2012 (PF)Ordinance 2012-45: added December 11, 2012 (SC1)Ordinance 2013-02: added November 19, 2013 (R18)Ordinance 2013-06: added November 20, 2013 (LDR)Ordinance 2013-08: added November 20, 2013 (CMU)Ordinance 2013-11: added December 11, 2013 (CHDR)Ordinance 2013-12: added December 16, 2013 (R2)Ordinance 2013-26: added December 30, 2013 (LDR)Ordinance 2013-30: added December 17, 2013 (CG)Ordinance 2013-35: added December 18, 2013 (SC1)Ordinance 2013-43: added December 19, 2013 (TF)Ordinance 2013-44: added December 19, 2013 (R18)Ordinance 2013-45: added December 19, 2013 (R110)Ordinance 2013-48: added December 23, 2013 (HDR)'Zone Map Correction: December 26, 2013: The PF zone around the airport has been out of date for years. A large gap between the airport PF zone and the Provo City boundary NW of airport and up along the Utah Lake State Park was extended to the city boundary. A portion of the north end of the main airstrip was still A110. It was switched to PF along Provo City parcel boundaries. The very southern tip of the same airstrip was A120. It was switched to PF as well along Provo City parcel boundaries.'Annexation Ordinance 2014-04: added January 5, 2015 Ordinance 2014-05: added April 1, 2014 (R18)Ordinance 2014-08: added June 9, 2014 (SDP4 - an ordinance correcting an error and returning a portion to R120)Ordinance 2014-09: added April 2, 2014 (HCF)Ordinance 2014-12: added July 28, 2014 (MDR)Ordinance 2014-16: added July 28, 2014 (PF)Ordinance 2014-19: added July 30, 2014 (R110)Zone Map Correction: December 17, 2014: Found that the HCF zone from 2014-09 and the R18 zone from 2014-05 were not added to the zoning layer. Corrections were made to the zoning map layer in the database and the July 31, 2014 official zoning map was reprinted. All copies that could be found with the error were thrown away. Some have surely been sold over the last several months from the Community Development front desk. The pdf file in the map library (S:\Map Library\Zoning) was replaced. After this, zone 2014-29 (HCF) needs to be added, the Champion Safe Annexation needs to be checked to see if it has finally passed, and a new map issued with a new date.Ordinance 2014-29: added January 5, 2015 (HCF)Ordinance 2015-01: added April 6, 2015 (R18, R110)Ordinance 2015-04: added April 6, 2015 (R18)Ordinance 2015-07: added April 6, 2015 (PIC)Ordinance 2015-09: added April 6, 2015 (LDR)Ordinance 2015-10: added April 6, 2015 (MDR)Ordinance 2015-11: added April 7, 2015 (CMU)Ordinance 2015-17: added August 25, 2015 (R110 - Annexation Ord 2015-01)Ordinance 2015-18: added September 9, 2015 (R110)Ordinance 2015-25: added September 16, 2015 (R18)Ordinance 2015-26: added September 29, 2015 (R110)Ordinance 2015-27: added September 29, 2015 (PF)Ordinance 2015-29: added October 26, 2015 (HCF)Ordinance 2015-32: added March 10, 2016 (R120, SDP4, SDP5 - Annexation Ordinance)Ordinance 2015-33: added March 14, 2016 (Deannexation)Ordinance 2015-42: added March 14, 2016 (CG)Ordinance 2015-43: added March 15, 2016 (R110)Ordinance 2015-46: added March 15, 2016 (MDR)Ordinance 2016-07: added Sept 7, 2016 (R2PD)Ordinance 2016-10: added Sept 27, 2016 (LDR)Zone Map Correction: August 4, 2016: Community Development determined that a small, single-lot PF zone at the north end of Scenic Dr (4344 N Scenic Dr) was not supposed to be PF. It was merged with the adjacent R110 zone.Ordinance 2016-14: added Sept 27, 2016 (PRO-A20)Ordinance 2016-16: added Sept 27, 2016 (HCF)Ordinance 2016-18: added Sept 29, 2016 (LDR)Ordinance 2016-25: added January 19, 2017 (R110)Ordinance 2016-33: added January 19, 2017 (DT1)Ordinance 2016-36: added April 12, 2017 (R110)

Copyright Text:

Default Visibility: false

MaxRecordCount: 1000

Supported Query Formats: JSON, geoJSON, PBF

Min Scale: 0

Max Scale: 0

Supports Advanced Queries: true

Supports Statistics: true

Has Labels: false

Can Modify Layer: false

Can Scale Symbols: false

Use Standardized Queries: true

Supports Datum Transformation: true

Extent:

XMin: 1573116.2834321111
YMin: 7236422.6542061865
XMax: 1630133.0827841014
YMax: 7288527.013579935
Spatial Reference: 102743  (3566)

Drawing Info:

Renderer:
Simple Renderer:
Symbol:
Style: esriSFSSolid
Color: [210, 247, 220, 255]
Outline:
Style: esriSLSSolid
Color: [110, 110, 110, 255]
Width: 0
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 )
• ZONE ( type: esriFieldTypeString, alias: Zone, length: 12 )
• DESCRIPTION ( type: esriFieldTypeString, alias: Description, length: 255 )
• URL ( type: esriFieldTypeString, alias: Zoning URL, length: 100 )
• SHAPE ( type: esriFieldTypeGeometry, alias: Shape )
• CODE_URL ( type: esriFieldTypeString, alias: City Code URL, length: 100 )
• 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