My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
Agenda Packet 12-10-18 Work Session
COE
>
City of Eugene
>
Public Meetings
>
City Council
>
2018
>
12-10-2018
>
Agenda Packet 12-10-18 Work Session
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
12/7/2018 9:38:48 AM
Creation date
12/7/2018 9:34:10 AM
Metadata
Fields
Template:
City_Council
City_Council_Document_Type
Agenda Packet
City_Council_Meeting_Type
Work Session
City_Council_Meeting_Date
12/10/2018
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
124
PDF
Print
Pages to print
Enter page numbers and/or page ranges separated by commas. For example, 1,3,5-12.
After downloading, print the document using a PDF reader (e.g. Adobe Reader).
View images
View plain text
58 <br /> <br />Strategy 1: Remove land use code barriers <br />Option Explanation <br />such as a church—into <br />residential). <br />adjustment review, which adds cost and process time to a housing project <br />and allows for appeals. <br />4-A. Improve the adjustment <br />review process for <br />adaptive re-use. <br />5. Enable more multi-family <br />development along key <br />corridors. (See glossary for <br />a map of Eugene’s key <br />corridors.) <br />No new information based on straw poll <br /> <br />5-A: Create a ‘key corridor <br />overlay’ (with design <br />standards), which <br />allows multi-family <br />development on all <br />key corridors. <br />Minimal new information based on straw poll <br />A medium-impact way to implement the community vision established in <br />Envision Eugene along corridors. This option would enable multi-family <br />development in areas currently zoned for single-family use along portions <br />of Coburg and River Road, for example. Relates to Option 3b, which would <br />allow only missing middle housing types along these corridor segments. <br />Relates to Option 11, which would enable development envisioned across <br />the community by changing zoning to match the Comprehensive Plan map <br />(see map in Glossary). <br />5-B: Reduce parking <br />requirements for <br />certain multi-family <br />housing types along <br />key corridors <br />A way to reduce development requirements and costs for housing that is <br />envisioned along the key corridors. <br />6. Replace current code with a <br />form-based code. <br />For a more complete explanation of form-based code see <br />https://formbasedcodes.org/definition/ <br />Rewriting the entire land use code as a form-based code (focused on the <br />design, shape and size of the buildings, rather than the uses inside them) <br />would be a very large undertaking, involving extensive public <br />involvement, legal review, and a formal adoption process. Impact on <br />housing availability and diversity would be long term and limited because <br />the form-based code would only apply as redevelopment or new <br />development occurs. <br /> <br />Form-based codes could also be used for specific areas of the city. Codes <br />that include form-based standards already exist in the Franklin <br />Boulevard/Walnut Street area, and at the Downtown Riverfront. These <br />codes are typically developed to implement a visioning and master <br />planning process for special areas of the city. <br />6-A: Create a city-wide <br />form-based code, <br />which would replace <br />the current land use <br />code. <br />6-B: Create form-based <br />codes in certain areas. <br />7. Remove neighborhood- <br />specific zoning. <br />No new information based on straw poll <br />December 10, 2018, Work Session - Item 2
The URL can be used to link to this page
Your browser does not support the video tag.