My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
Item B: Minor Code Amendments
COE
>
City of Eugene
>
Council Agendas 2008
>
CC Agenda - 06/04/08 Work Session
>
Item B: Minor Code Amendments
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
6/9/2010 1:14:07 PM
Creation date
5/30/2008 10:14:13 AM
Metadata
Fields
Template:
City Council
City_Council_Document_Type
Agenda Item Summary
CMO_Meeting_Date
8/6/2004
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
30
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
would require a minimum of one parking space for the first <br />bedroom and an additional .5 parking spaces per each <br />additional bedroom. Fractions would be rounded up to the <br />next whole number. Currently, one space is required for each <br />dwelling unit or apartment, regardless of the number of <br />bedrooms. <br /> <br />8. Stormwater Destination: The stormwater provisions of the Eugene Code do not require 9.6790 <br />Encourage On-Site Infiltration as a or encourage selection of a particular stormwater destination, 9.6791 <br />Preferred Approach and Restrict Fill instead allowing a developer to choose any existing destination <br />and Disturbance of Drainage Ways that has the capacity. This amendment would indicate that on- <br />site infiltration is the preferred stormwater destination for <br />development in the River Road-Santa Clara Basin. This <br />amendment would also add a provision to the land use code to <br />restrict fill of drainage ways under the same conditions as <br />listed in the Stormwater Management Manual. <br /> <br />9. Flag Lots Definition and This amendment would strengthen and clarify the existing the 9.0500 <br />Development Standards definition of a “flag lot.” Additionally, the amendment would 9.2761(4) <br />clarify that the existing R-1 Low Density Residential flag lot 9.2775 <br />standards also apply to new flag lots in the R-2, R-3 and R-4 <br />zones. Currently the code is unclear on flag lot standards for <br />the R-2, R-3 and R-4 zones. The flag lot standards include <br />requirements for minimum driveway paving widths and <br />materials, building setbacks, use restrictions and land division <br />regulations. <br /> <br />10. Lot Width and Lot Frontage This amendment would revert the lot width and lot frontage 9.2760 <br />Standards minimums for lots in the R-2 Medium Density Residential, R-9.2761(9) <br />3 Limited High Density Residential and R-4 High Density Table 9.2760 <br />Residential zones (currently 20 feet) to those in effect prior to <br />the land use code update of 2001 (35 feet). Lesser widths <br />would be allowed, down to 20 feet, subject to an approved site <br />review plan, planned unit development, or cluster subdivision. <br />Also, unless otherwise approved through a planned unit <br />development or cluster subdivision, at no point, for the entire <br />extent of the lot, shall the side lot lines be less than 20 feet <br />apart. <br /> <br />11. Add Definition of Alley Access This amendment adds a definition or “alley access only 9.0500 <br />Only Lot/Parcel and Clarify lot/parcel” to define a lot without street access, clarifies that 9.2761(10) <br />Existing Prohibition the creation of alley access only lots/parcels is prohibited in 9.5500(11)(c) <br />residential zones unless approved through a cluster <br />subdivision in the R-1 zone or a planned unit development in <br />any residential zone, and amends the multiple-family standards <br />to allow development sites to take direct access to a street, if <br />the abutting alley is less than the minimum width required (20 <br />feet) to serve as primary access. The intent of this amendment <br />is to strengthen and clarify the City Council’s previous <br />direction to prohibit alley access lots/parcels. <br /> <br />12. Exclude Area within Private This amendment would clarify that the portion of a lot that 9.2751(1)(c) <br />Streets from Residential Lot Areas includes private or public streets is not included in the lot area 9.2761(1) <br />calculations in residential partitions or subdivisions, and clarify <br />that when calculating density, the area within public and <br />private streets is excluded. <br /> <br />Summary of Proposed Minor Code Amendments 3 <br />
The URL can be used to link to this page
Your browser does not support the video tag.