My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
2017 Remand – Applicant Final Rebuttal 5-3-17
>
OnTrack
>
PDT
>
2013
>
PDT 13-1
>
2017 Remand – Applicant Final Rebuttal 5-3-17
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
5/8/2017 4:00:24 PM
Creation date
5/5/2017 8:47:03 AM
Metadata
Fields
Template:
PDD_Planning_Development
File Type
PDT
File Year
13
File Sequence Number
1
Application Name
OAKLEIGH COHOUSING
Document Type
Public Comments
Document_Date
5/3/2017
External View
Yes
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
10
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
Eugene Planning Commission <br />May 3, 2017 <br />Page 6 of 10 <br />and expressly concurs with Mr. Weishar's analysis that Oakleigh Lane is safe to serve <br />the PUD: <br />The applicant's engineer addresses the intermittent parking concerns raised by <br />appellants. Intermittent parking is a common feature City wide and acts as a <br />built in traffic calming feature on most local urban roadways. The applicants <br />engineer has provided testimony and analyses for roadway operations and <br />safety, including evidence and analyses demonstrating the roadway has <br />adequate capacity to serve existing and proposed development. The applicant <br />examined the crash history of the entire roadway and concluded that there is no <br />evidence that would indicate a safety issue. The applicant's engineer also <br />provided discussion and evidence supporting the roadway's adequacy for basic <br />ingress and egress to the development site, for all modes of travel. The <br />applicant's engineer indicated the lack of the urban features should not be <br />interpreted as being unsafe or inadequate. City staff concurs with the <br />applicant's engineer and finds the existing Oakleigh Lane to be adequate to <br />serve the development site. <br />The opponents attempt to remotely challenge the City of Eugene's Public <br />Works department with an analysis prepared by a second engineer, a Mr. Saberian, <br />who apparently works out of Santa Rosa, CA or maybe in Beaverton. In either case, as <br />with Ms.' Nemariam, Mr. Saberian was not provided with a copy of any of the <br />professional analysis prepared by professional Traffic Engineer Michael Weishare <br />when he reviewed Public Works concurrence in that analysis. Saberian Analysis, p. 1 <br />(listing documents considered). Moreover, he provides no independent analysis of <br />Oakleigh Lane, its capacity, crash rates, speed, etc. that would refute either Mr. <br />Weishar's analysis of actual traffic safety or the City of Eugene's concurrence in that <br />analysis. Accordingly, Mr. Saberian's remote analysis provides no basis for the City to <br />question its own Public Works determination that the Oakleigh Lane is adequate to <br />serve the PUD site. <br />In addition to Public Works professional opinion that Oakleigh Lane is <br />adequate to serve the site, the Fire Marshal's office independently provided testimony <br />that Oakleigh Lane would not be an impediment to emergency response and that the <br />PUD will provide safety improvements: <br />Applicable Question: <br />Does the existing Oakleigh Lane, serving as a fire department access to existing <br />dwellings and proposed development, exhibit, produce or create a significant <br />risk to emergency response actions? <br />1. The existing Oakleigh Lane in and of itself does not exhibit si ni 'cant risk to <br />emergency response actions. <br />a. Currently there is a single fire hydrant located at approximately half the <br />current length of Oakleigh Lane on the north side of this lane. This <br />provides the required water supply for firefighting capability. <br />
The URL can be used to link to this page
Your browser does not support the video tag.