My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
Item A: Introduction to Access Management
COE
>
City of Eugene
>
Council Agendas 2010
>
CC Agenda - 02/08/10 Work Session
>
Item A: Introduction to Access Management
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
6/9/2010 1:03:00 PM
Creation date
2/5/2010 10:27:52 AM
Metadata
Fields
Template:
City Council
City_Council_Document_Type
Agenda Item Summary
CMO_Meeting_Date
2/8/2010
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
38
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 />EC 9.5500 Multiple-Family Standards. Removes regulations related to access connections within the <br />public right-of-way to distinguish differences and authority between driveways and access <br />connections. <br /> <br />EC 9.6505 Improvements-Specifications. Clarifies that street and alley improvements include <br />sidewalks, street lights, and street trees as part of the street improvements and that improvement <br />requirements for streets adjacent to development are the same as within the development; removes <br />redundant references to private street regulations from this section. <br /> <br />EC 9.6703 Driveways and Internal Circulation. Clarifies and coordinates driveway regulations with <br />the new access connection provisions. <br /> <br />EC 9.6735 Public Access Required. Requires land use and building permit applications include <br />locating access connections in compliance with EC 7.420 in the approval process. <br /> <br />EC 9.6745 Setbacks-Intrusions Permitted and EC 9.6750 Special Setback Standards. Requires <br />special setbacks when the abutting street is not improved with curb, gutter, sidewalk, street trees and <br />street lights and proposes changing the “default” width of special setbacks from the maximum street <br />width established by Table 9.6870 to the minimum width required by Table 9.6870. For <br />discretionary land use decisions, the City will still have the ability to require more than the minimum <br />setback width, so long as the requirement is consistent with adopted standards. <br /> <br />EC 9.6840 Reserve Strips. Clarifies reserve strips may be used to prevent access to arterial and <br />major collector streets. <br /> <br />EC 9.6870 Street Widths and EC 9.6873 Slope Easements. Changes the “default” width of streets <br />from the maximum street width established by Table 9.6870 to the minimum width required by Table <br />9.6870. For discretionary land use decisions, the City will still have the ability to require more than <br />the minimum street width, so long as the requirement is consistent with adopted standards. Since <br />Table 9.6870 does not provide a range for alley widths, language has been added that would allow <br />the City to reduce the width with discretionary land use decisions. Redundant construction standards <br />in section (1) are being removed and slope easements in section (2) are being moved to their own <br />code section 9.6873. <br /> <br />EC 9.8030 Adjustment Review Approval Criteria. Provides adjustment approval criteria for street <br />and alley improvements; driveway and internal circulation, and access connection location <br />requirements. Adjustment criteria for street and alley improvements would allow applicants to meet <br />paving requirements under a Temporary Surfacing Permit when full improvements are unwarranted. <br />The adjustment criteria for driveway and internal circulation would allow applicants to shorten <br />driveway stacking requirements when an alternative traffic safety study demonstrates safe ingress <br />and egress and doesn’t result in a hazard for vehicles, bicycles, and pedestrians and doesn’t <br />negatively impact the efficient use of the public right-of-way. The adjustment criteria for public <br />access would allow applicants to adjust the location of their access connection in the following <br />cases: when physical conditions preclude compliance with EC 7.420; when an alternate location will <br />still provide safe and efficient access; when the proposed development doesn’t impact an existing <br />access connection; or when access connections on a secondary street create traffic patterns <br />inconsistent with the surrounding area. <br /> Z:\CMO\2010 Council Agendas\M100208\S100208A.doc <br /> <br />
The URL can be used to link to this page
Your browser does not support the video tag.