My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
9-28-15 Planning Commission Record
>
OnTrack
>
PDT
>
2013
>
PDT 13-1
>
9-28-15 Planning Commission Record
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
4/27/2017 4:32:34 PM
Creation date
9/21/2015 12:38:11 PM
Metadata
Fields
Template:
PDD_Planning_Development
File Type
PDT
File Year
13
File Sequence Number
1
Application Name
OAKLEIGH COHOUSING
Document Type
Planning Commission Meeting
Document_Date
9/21/2015
External View
Yes
Jump to thumbnail
< previous set
next set >
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
346
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).
Download electronic document
View images
View plain text
may be guided by the Oregon Department of Land Conservation and <br />Development's Neighborhood Street Design Guidelines, June 2001. <br />[Section] 56. Appendix D Section D102.2 of the OFC is amended to provide: <br />D102.1 Access and Loading. Facilities, buildings or portions of buildings <br />hereafter constructed shall be accessible to fire department apparatus by way of <br />an approved fire apparatus access road with an asphalt concrete or other <br />approved driving surface capable of supporting the imposed load of fire <br />apparatus weighing at least 80,000 pounds. <br />Thus, although the statutes allow Eugene to adopt standards for a Low Volume Residential <br />street, such as Oakleigh Lane, that are narrower than the standards in the IFC code, Eugene did <br />not do that. <br />Instead, section 55, adopted through code provisions adopted by City Council, requires that a <br />fire apparatus access road meet both the OFC requirements and the street standards adopted by <br />the City. Thus, a Low Volume Residential street, such as Oakleigh Lane, that provides the only <br />fire apparatus access road to a new development must have at a minimum a 45-foot right-of- <br />way, and an unobstructed, 20-foot wide pavement of adequate bearing strength. <br />Further, the Eugene Code doesn't adopt any "clear width" standards to supersede the EFC <br />standards for "clear width," presumably because the right-of-way minimums in <br />EC Table 9.6870 for all categories of street (except alleys) are 40 feet or greater, which is plenty <br />to allow for the EFC requirement of 20 to 26 foot clear width. <br />Commissioners must reject any attempt by the applicant or Deputy City Attorney to claim that <br />ORS 368.039 somehow allows the Planning Commission to interpret EC 9.8320(5) and (6) to <br />entirely ignore the long stretch of Oakleigh Lane from River Road to the proposed development <br />or to not require that Oakleigh Lane meet adopted street standards and/or Eugene Fire Code <br />fire apparatus access road standards. <br />EUGENE FIRE CODE REQUIREMENTS PROTECT PUBLIC SAFETY <br />This section walks you through the 2014 Oregon Fire Code provisions that are adopted into the <br />Eugene Fire Code and found in Attachment J, incorporated herein. Page numbers refer to the <br />numbers at the bottom of the 2014 OFC pages. <br />"Fire Apparatus Access Road" is defined on page 26 as "A road that provides fire apparatus <br />access from a fire station to a facility, building or portion thereof. This is a general term <br />inclusive of all other terms, such as fire lane, public street, private street, parking lot lane and <br />access roadway." <br />Oakleigh Lane is the only road that can serve as a fire apparatus access road to the proposed <br />OMC development; and, obviously, the entirety of Oakleigh Lane is necessary to satisfy the <br />definition. <br />Section 503.1 (page 67) specifies where a fire apparatus access road is required. <br />Trautman Appeal Testimony PDT 13-1 Page 11 August 31, 2015 <br />36 <br />
The URL can be used to link to this page
Your browser does not support the video tag.