160 likes | 296 Views
City of Griffin: Unified Development Code (UDC) Commissioner Meeting. May 24, 2011. Key Points for Discussion: Overview Orientation to the UDC Table of Contents Example of Districts Use Table Discussion of Key Points Permitted Uses Zoning Criteria: Rezoning & the Comprehensive Plan
E N D
City of Griffin: Unified Development Code (UDC) Commissioner Meeting May 24, 2011
Key Points for Discussion: Overview Orientation to the UDC Table of Contents Example of Districts Use Table Discussion of Key Points Permitted Uses Zoning Criteria: Rezoning & the Comprehensive Plan New Development: Tree Requirements Conservation Subdivision Today’s Presentation
Rezoning Criteria: yes, no? • Trade-offs: • Provides legislative authority to deny; policy driven • But equal treatment: must use each time! • Is it a suitable use given nearby property? • Does it adversely affect the use/usability of nearby property? • Does current zoning allow reasonable economic use? • Will/could it cause burden on infrastructure or schools? • Does it conform w/ adopted land use plan & policy intent? • Are there changing conditions which give supporting grounds for either approval or disapproval?
Limited Tree Regulations? • For NEW development and COMMERCIAL redevelopment only • EXEMPT individual Residential lots • No clear cutting • Establish number of required tree cover on the site (“units” per acre) • Inventory existing trees on site; special weight for speciman trees • Indicate which will stay and which will go • Indicate replacement plan
Conservation Subdivision • Allow by-right in any residential zoning district • Conserves open space – 45% • Requires a mix of lot size • Consider allowing greater number of units as incentive • Integrate into surrounding by requiring lots on the perimeter to be compatible with lot sizes of adjacent
Next Steps: • Commissioners review key sections (e.g. use table); provide comments • Review by City Attorney and Staff; provide consultant consolidated comments • Consultant final revisions • June 14 consider adoption • Implementation: maintenance (amend as needed as code is tested; yearly review recommended)