My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
Public Comment
>
OnTrack
>
TIA
>
2016
>
TIA 16-7
>
Public Comment
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
6/26/2017 12:30:41 PM
Creation date
1/12/2017 11:35:49 AM
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/12/2017
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.
/
272
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
reason, as this intersection is a popular crossing for those shopping at Albertsons. <br />No mitigation is proposed at E 32nd and Hilyard where vehicles making a left turn <br />from E 32nd onto Hilyard southbound are already having great difficulty (as noted <br />in the TIA). The recommendation of the TIA is to prune hedges to 12 inches to <br />improve visibility. This is not adequate. The limiting factor for this maneuver is the <br />need to have both lanes of Hilyard clear before attempting the left turn. Further <br />analysis in the TIA is required to determine how many such turns could possibly <br />be accomplished in a peak hour. The TIA indicates that 17 additional southbound <br />left turns from E 32nd would be added to the existing level, for a total of 58 turns <br />during the PM peak. Is this even possible? The TIA does not appear to consider <br />the fact that these left turns from E 32nd will also conflict directly with the 118 left <br />turns from southbound traffic on Hilyard onto E 32nd (52 of which are generated <br />by the development). The inability of vehicles to make this left turn from E 32nd <br />will likely cause significant cuing which may affect both left and right turns. The <br />dedicated left turn lane on the E 32"d entrance onto Hilyard must be <br />maintained and possibly lengthened. A median refuge on Hilyard at E 32nd <br />would greatly facility this movement and should be evaluated as a <br />mitigation option. The TIA should address the conflict between southbound <br />left turns from Hilyard onto E 32nd and westbound left turns from E 32nd <br />onto Hilyard, as noted above. <br />The inability of traffic from the proposed development to move south or west <br />from the site is likely to generate use of alternative routes on neighborhood <br />streets. Taking E 32nd to Alder Street north to E 30th and then turning south on <br />Hilyard is one of the movements that can be anticipated, but is not included in <br />the TIA. Taking Alder Street to E 30th to go west on Amazon Parkway is another <br />likely alternative route from the proposed development. Using Alder street for <br />westbound movements onto E 30th can also be reasonably anticipate, but is also <br />not included in the TIA. These are clear reasons why the Alder/E32nd and <br />Alder/ E 30th intersections need to be included in the TIA and the traffic <br />volumes on this section of Alder need to be evaluated. Installation of traffic <br />calming on this section of Alder Street may be needed to mitigate traffic <br />increases from the proposed development. <br />A further problem resulting from the difficulty moving southward from this site is <br />that E 31St may become an alternate route for both southbound and westbound <br />traffic. Consider a resident of the proposed development desiring to go to the <br />post office who doesn't want to wait for the very difficult left turn out of E 32nd <br />onto Hilyard to reach E 33rd. The obvious alternate route would be to head north <br />Fodor & Associates - Page 8 <br />
The URL can be used to link to this page
Your browser does not support the video tag.