Facebook
TwitterAttribution 4.0 (CC BY 4.0)https://creativecommons.org/licenses/by/4.0/
License information was derived automatically
Zoning Overlays and Regulatory Plans
Contact Information: zoning@phoenix.gov
Facebook
TwitterAttribution 4.0 (CC BY 4.0)https://creativecommons.org/licenses/by/4.0/
License information was derived automatically
A grid system that breaks down the City of Phoenix into smaller sections for Planning and Zoning purposes.
Contact Information: zoning@phoenix.gov
Facebook
TwitterAttribution 4.0 (CC BY 4.0)https://creativecommons.org/licenses/by/4.0/
License information was derived automatically
Proposed Zoning data is intended to better inform residents of current rezoning activities in their community. Rezoning cases are typically requested from property owners to allow for a new use or to apply a different set of development standards (i.e. setbacks, building heights, and densities) that are not already permitted in the existing zoning district designated for their property.
Zoning regulations are intended to protect existing land uses and assure that uses are compatible with each other and with available public facilities and services. Through the rezoning process, land use and other factors are evaluated to determine the appropriateness of a specific rezoning proposal. Final approval of a rezoning request is granted by the Phoenix City Council at a public hearing.
Contact Information: zoning@phoenix.gov
Facebook
TwitterDigitized zoning maps for three time points during Phoenix’s 20th Century development: 1930-1941 (Phoenix’s original adoption of zoning), 1955 (onset of postwar expansion), and 1970 (major annexation and planning for growth, including the city’s incorporation of large agricultural areas for urban expansion).
Facebook
TwitterThe City of Phoenix (COP) zoning boundaries were digitized from a hard copy data set, by contract, in 1991. Since that time, updates to the data have been made on an ongoing basis as land is rezoned. The layer is digitized at a relatively small scale, from approximately 1:10 to 1:10,000. Changes are made when inconsistencies are found.Contact Information: zoning@phoenix.gov
Facebook
TwitterAttribution 4.0 (CC BY 4.0)https://creativecommons.org/licenses/by/4.0/
License information was derived automatically
Facebook
TwitterAttribution 4.0 (CC BY 4.0)https://creativecommons.org/licenses/by/4.0/
License information was derived automatically
A General Plan provides the vision and policies that determine how a city will grow and develop. The General Plan was reviewed by the public and village planning committees in the fall of 2014. The Planning and Development Department has developed an updated draft based on the community's feedback. The General Plan Update was unanimously approved by the Planng Commision on January 13, 2015. The Phoenix City Council is scheduled to review and possibly take action on the General Plan at the February 17, Neighborhoods Housing and Development Subcommittee and the City Council Formal meeting on March 4, 2015.
Contact Information: zoning@phoenix.gov
Facebook
TwitterThis Zoning feature class is an element of the Oregon GIS Framework statewide, Zoning spatial data. This version is authorized for public use. Attributes include zoning districts that have been generalized to state classes. As of June 30, 2023, this feature class contains zoning data from 229 local jurisdictions. DLCD plans to continue adding to and updating this statewide zoning dataset as they receive zoning information from the local jurisdictions. Jurisdictions included in the latest version of the statewide zoning geodatabase:
Cities: Adams, Adrian, Albany, Amity, Antelope, Ashland, Astoria, Athena, Aurora, Banks, Barlow, Bay City, Beaverton, Bend, Boardman, Bonanza, Brookings, Brownsville, Burns, Butte Falls, Canby, Cannon Beach, Carlton, Cascade Locks, Cave Junction, Central Point, Chiloquin, Coburg, Columbia City, Coos Bay, Cornelius, Corvallis, Cottage Grove, Creswell, Culver, Dayton, Detroit, Donald, Drain, Dufur, Dundee, Dunes City, Durham, Eagle Point, Echo, Enterprise, Estacada, Eugene, Fairview, Falls City, Florence, Forest Grove, Fossil, Garibaldi, Gaston, Gates, Gearhart, Gervais, Gladstone, Gold Beach, Gold Hill, Grants Pass, Grass Valley, Gresham, Halsey, Happy Valley, Harrisburg, Helix, Hermiston, Hillsboro, Hines, Hood River, Hubbard, Idanha, Independence, Jacksonville, Jefferson, Johnson City, Jordan Valley, Junction City, Keizer, King City, Klamath Falls, La Grande, La Pine, Lafayette, Lake Oswego, Lebanon, Lincoln City, Lowell, Lyons, Madras, Malin, Manzanita, Maupin, Maywood Park, McMinnville, Medford, Merrill, Metolius, Mill City, Millersburg, Milton-Freewater, Milwaukie, Mitchell, Molalla, Monmouth, Moro, Mosier, Mount Angel, Myrtle Creek, Myrtle Point, Nehalem, Newberg, Newport, North Bend, North Plains, Nyssa, Oakridge, Ontario, Oregon City, Pendleton, Philomath, Phoenix, Pilot Rock, Port Orford, Portland, Prescott, Prineville, Rainier, Redmond, Reedsport, Rivergrove, Rockaway Beach, Rogue River, Roseburg, Rufus, Saint Helens, Salem, Sandy, Scappoose, Scio, Scotts Mills, Seaside, Shady Cove, Shaniko, Sheridan, Sherwood, Silverton, Sisters, Sodaville, Spray, Springfield, Stanfield, Stayton, Sublimity, Sutherlin, Sweet Home, Talent, Tangent, The Dalles, Tigard, Tillamook, Toledo, Troutdale, Tualatin, Turner, Ukiah, Umatilla, Vale, Veneta, Vernonia, Warrenton, Wasco, Waterloo, West Linn, Westfir, Weston, Wheeler, Willamina, Wilsonville, Winston, Wood Village, Woodburn, Yamhill.
Counties: Baker County, Benton County, Clackamas County, Clatsop County, Columbia County, Coos County, Crook County, Curry County, Deschutes County, Douglas County, Harney County, Hood River County, Jackson County, Jefferson County, Josephine County, Klamath County, Lane County, Lincoln County, Linn County, Malheur County, Marion County, Multnomah County, Polk County, Sherman County, Tillamook County, Umatilla County, Union County, Wasco County, Washington County, Wheeler County, Yamhill County.
R emaining jurisdictions either chose not to share data to incorporate into the public, statewide dataset or did not respond to DLCD’s request for data. These jurisdictions’ attributes are designated “not shared” in the orZDesc field and “NS” in the orZCode field.
Facebook
TwitterAttribution 4.0 (CC BY 4.0)https://creativecommons.org/licenses/by/4.0/
License information was derived automatically
City of Phoenix Development Impact Fee Areas.
Contact Information: zoning@phoenix.gov
Facebook
TwitterAttribution 4.0 (CC BY 4.0)https://creativecommons.org/licenses/by/4.0/
License information was derived automatically
Infill Development District provides flexibility for development in designated areas served by the light rail and existing public infrastructure.
Contact Information: zoning@phoenix.gov
Not seeing a result you expected?
Learn how you can add new datasets to our index.
Facebook
TwitterAttribution 4.0 (CC BY 4.0)https://creativecommons.org/licenses/by/4.0/
License information was derived automatically
Zoning Overlays and Regulatory Plans
Contact Information: zoning@phoenix.gov