My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
Applicant Response to Public Comment
>
OnTrack
>
TIA
>
2016
>
TIA 16-7
>
Applicant Response to Public Comment
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
6/26/2017 12:27:38 PM
Creation date
1/11/2017 3:53:28 PM
Metadata
Fields
Template:
PDD_Planning_Development
File Type
TIA
File Year
16
File Sequence Number
7
Application Name
Amazon Corner
Document Type
Public Comments
Document_Date
1/10/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.
/
4
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
Traffic Concerns: <br />The bulk of comments express concern that the TIA as submitted is inadequate from various <br />perspectives and/or does not cast a wide enough net; that further and broader study should be <br />required. <br />We are not traffic engineers, nor do we purport to understand the science, standards, or data <br />behind the analysis. Therefore, we rely on experts for that - City Transportation Planners who <br />establish the requirements, Professional Traffic Engineers who collect and analyze the data, <br />and national organizations who establish the standards by which such analysis is to be <br />conducted in order to produce results by which decision-makers can make informed decisions. <br />To the best of our knowledge and ability we have fulfilled every standard and requirement set <br />forth for this project and every similar development in our community. It seems many <br />commentators take issue with TINs in general and how they are performed. These may all be <br />valid points and, if so, then one should focus such effort on changing the system by which traffic <br />is studied and analyzed, and the requirements set forth by public agencies that are applied to <br />development projects. Under the current system, it is unreasonable to expect that expanding <br />the study area would produce a different result from a traffic analysis perspective. <br />To put things into perspective, the City of Eugene 2013 Traffic Flow Map indicates a daily <br />average of 23,300 vehicle trips along Hilyard Street between 30th and 33rd Avenues. One can <br />imagine that the current number is higher, four years later. However, using the 2013 numbers, <br />the projected number of daily trips from the proposed development (990) along this same <br />section represents roughly a four percent increase in daily traffic. According to our Traffic <br />Engineer, this section of Hilyard (the primary route of travel for the development) has capacity <br />for 31,000 average daily trips, indicating a growth capacity of 33 percent from the 2013 number. <br />This project would contribute roughly three percent of that total if/when the roadway reaches <br />capacity. <br />Since the project location is highly conducive to access via alternative transportation modes, <br />coupled with our efforts to reinforce and encourage these, the vehicular impact described above <br />is expected to be minimized. <br />Pedestrian and Bicycle Safety: <br />Regarding pedestrian safety and the existing condition of unsafe pedestrian and bicycle <br />crossing across Hilyard, we engaged in discussion with Public Works Transportation Planning <br />very early in our planning process and we specifically identified this as an issue. Because this <br />has been identified as a current issue, and will potentially worsen with the proposed <br />development, we intend to continue discussions with the City to determine where and how a <br />protected crossing can appropriately be incorporated into the project. <br />
The URL can be used to link to this page
Your browser does not support the video tag.