My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
Item 4: Public Hearing on Ordinance on Minor Land Use Code Amendments
COE
>
City of Eugene
>
Council Agendas 2005
>
CC Agenda - 10/24/05 Mtg
>
Item 4: Public Hearing on Ordinance on Minor Land Use Code Amendments
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
6/9/2010 12:46:36 PM
Creation date
10/21/2005 9:35:47 AM
Metadata
Fields
Template:
City Council
City_Council_Document_Type
Agenda Item Summary
CMO_Meeting_Date
10/24/2005
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
76
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 />9.6810 Requires new local streets to Code does not allow flexibility Create an exception provision <br /> intersect with other streets at from the 600' standard except allowing requests for <br /> intervals of 600' or less for physical constraints. Some exceptions to the 600' standard <br />@) larger subdivisions may provide while maintaining street <br /> a thorough network of streets, connectivity and emergency <br /> but have an intersection slightly access objectives. <br /> > 600' , requiring another <br /> unnecessary street. <br />9.6815(2) Adjustment Review regarding Adjustment review process is Eliminate requirement for <br /> street connectivity redundant. Street connectivity separate adjustment review and <br />@ is already evaluated as part of instead, fold in same <br /> land use application requirements into an exception <br /> (subdivision, partition, PUD, process as part of the primary <br /> etc). Any requests for land use application review. <br /> exceptions can be handled This will consolidate all street <br /> through the main application. connectivity discussion without <br /> changing any actual <br /> requirements. <br />9.6820; Cul-de-sac requirements Language describing when a Clarify circumstances in which <br />9.80~)(b) cul-de-sac vs. alternative exceptions to cul-de-sac design <br /> designs (i.e. hammerheads) can can be requested and granted. <br /> be used is confusing. <br />9.6870 (table) Cul-de-sac design standards Right-of-way (ROW) and Revise the table to specify <br />@ paving width requirements are consistent right-of-way <br /> not consistent with other standards for cul-de-sacs <br /> adopted public works standards <br />9.6885(2) Tree preservation plans requires Requirement is limited to Revise standard to allow <br /> report from certified arborist certified arborists. In some landscape architects as well as <br />@ cases, landscape architects are certified arborists to provide the <br /> better equipped to look at required report. <br /> broader site design options to <br /> improve tree preservation. <br /> Especially relevant when tree <br /> health/vitality are not key <br /> factors. <br />9.7015 Completeness Review: Language is not consistent with Revise language to ensure <br />@ Timeline for response to more recently adopted State consistency with State Law. <br />incomplete applications Statutes which puts burden on <br /> the applicant to inform city of <br /> their intention to provide <br /> missim! information. <br />9.7020 Waiver of time lines Current language implies any Clarify limitation on timeline <br />@ timeline can be waived, waivers consistent with state <br /> however a recently adopted statutes (maximum of 245 <br /> state statute limits time waivers days). <br /> for land use applications. <br />
The URL can be used to link to this page
Your browser does not support the video tag.