My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
Item 3: Action - Minor Land Use Code Amendments
COE
>
City of Eugene
>
Council Agendas 2005
>
CC Agenda - 11/28/05 Mtg
>
Item 3: Action - Minor Land Use Code Amendments
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
6/9/2010 12:42:21 PM
Creation date
11/22/2005 1:22:02 PM
Metadata
Fields
Template:
City Council
City_Council_Document_Type
Agenda Item Summary
CMO_Meeting_Date
11/28/2005
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
91
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
<br />along street frontages, it also maintains a requirement for buffering along interior property lines (even though <br />its unclear if this was intended). However, it does resolve the "canyon effect" potential by requiring at least 15' <br />of separation betlveen buildings. <br /> <br />57)9.6810 <br /> <br />This loosens the criteria for which the exception shall be granted based on lInot <br />creating excessive travel lengths. 11 <br /> <br />The provision was established according to standards for creating Pedestrian <br />friendly and walkable developments. <br /> <br />But your criteria do not differentiate between travel lengths for autos or for humans <br />on foot. Doesn't it need to specifically address pedestrian travel lengths and define <br />what is excessive? <br /> <br />Response: One of the approval criteria for most land use applications is that the project develop a street system <br />with block lengths of 600' or less. In addition to that criterion, the code also requires several others components <br />related to streets, transit, pedestrian and bicycle access. This proposed amendment would be limited to the 600' <br />standard. All other provisions addressing circulation and access for all modes 'would remain in effect. [n other <br />words, all other criterion would need to be met in order to consider block lengths longer than 600'. <br /> <br />58) This adds to the trend of removing objective and clear code standards and <br />vesting all discretion for waiving provisions with staff. <br /> <br />Response: The code currently contains an adjustment review process related to street connectivity. Since street <br />connectivity is always considered as part of a land use application, the current code requires 2 separate <br />requests for the same project. This amendment essential~y consolidates these provisions by moving the <br />m{justment review process under the main land use application. For example, a subdivision application would <br />contain the street connectivity alijustment process rather than processing the same provisions in a separate <br />parallel request. This amendment will not change any of the criteria for adjustment, the public <br />notice/involvement process, or the decision making authority. <br /> <br />66) 9.7805, 9.7885 <br /> <br />Who is the decision making authority for the Industrial Corridor Agreement and <br />what will be the process to change the boundaries if this code revision is adopted? <br />What specific properties are affected by this change? <br /> <br />Response: The Council originally authorized the creation of the Industrial Corridor Agreement. That agreement <br />specified which parcels were included within the boundaries. The proposed amendment is limited to correcting <br />the figure included in Chapter 9. so that it accurately represents those parcels referenced in the approved <br />agreement. The figure currently shol-1.-'S some parcels in the Airport Road area li/hich should not be included <br />within the boundaries. No change to the agreement or the process to amend this agreement are proposed. <br /> <br />71) 9.8055 (1) <br /> <br />Does this create an automatic waiver authority for staff? Would it apply to potential <br />M37 claims? <br /> <br />Response: The code currently allows for flexibility in the design of cluster subdivisions. The proposed <br /> <br />4 <br />
The URL can be used to link to this page
Your browser does not support the video tag.