My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
Business Retention and Development Committee Agenda and Packet 2009 06 01
PORTAL
>
BOARDS COMMISSIONS COMMITTEES RECORDS (20.000)
>
BUSINESS RETENTION & DEV COMMITTEE
>
2006-2019 Business Retention and Development Committee Agendas and Packets
>
2009 Business Retention and Development Committee Agendas and Packets
>
Business Retention and Development Committee Agenda and Packet 2009 06 01
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
3/10/2021 2:09:33 PM
Creation date
5/29/2009 10:58:14 AM
Metadata
Fields
Template:
City Council Records
Doc Type
Boards Commissions Committees Records
Supplemental fields
Test
BRADPKT 2009 06 01
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
21
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).
Show annotations
View images
View plain text
<br />. The future traffic volumes do not justify the need to construct a loop on-ramp. <br />Providing a double left-turn lane on the bridge deck would result in a future LOS <br />(AM Peak C and PM Peak B) sufficient to satisfy CDOT standards and consistent <br />with the standards CDOT, RTD and communities along the US-36 corridor have <br />agreed to for the planned US-36 improvements. <br /> <br />. The loop on-ramp is not included in the FEIS for US-36. Adding it would require <br />obtaining a new NEPA environmental clearance for the work resulting in <br />additional costs and project delays. <br /> <br />. The loop on-ramp would require the acquisition of right of way from the Outback <br />Restaurant. At best this would make parking that is already crowded more <br />difficult and undermine the Outback's revenues and at worst, it could force the <br />Outback out of business. <br /> <br />. Construction of the loop on-ramp would generate considerable construction noise <br />adjacent to a restaurant and hotel. <br /> <br />. The horizontal and vertical alignments of the loop on-ramp would require CDOT <br />approval. <br /> <br />. The loop on-ramp would require the reconstruction of the westbound off-ramp. <br /> <br />. The loop on-ramp would require the reconstruction of the westbound on-ramp <br />from southbound McCaslin Blvd to US-36 and possibly require additional right of <br />way from Colony Square. <br /> <br />. The loop on-ramp could require the reconstruction of the RTD bus stop located <br />adjacent to the westbound on-ramp to US-36. <br /> <br />. The loop on-ramp would require the widening of westbound US-36 in order to <br />accommodate the lane width of the loop on-ramp. <br /> <br />. The loop on-ramp would create a new conflict on the east side of McCaslin Blvd <br />between motorist accessing the loop on-ramp and bicyclists / pedestrians. <br /> <br />. The amount of time it would take to design, environmentally clear and acquire <br />right of way for the construction of the loop on-ramp would be longer and more <br />expensive and leave a smaller amount of funds available for construction. <br /> <br />. It has not been determined if the impacts of a loop on-ramp with respect to the <br />US-36 improvements would permit construction of the loop under Phase 1. <br /> <br />. It has not been determined how much of the loop on-ramp would require <br />reconstruction in order to construct the ultimate US-36 and McCaslin Blvd <br />Interchange improvements. <br /> <br />. The loop on-ramp would impact RTD queue jump improvements to be <br />constructed in 2009. <br /> <br />. Improving the LOS of the Northbound to Westbound traffic through the McCaslin <br />intersection with a loop does not guarantee faster access to US-36, as that will <br />depend on the capacity of US-36, and may result in faster travel through <br />McCaslin only to experience the a longer delay in the metered queue for access <br />to US-36. <br /> <br />2 <br /> <br />20 <br />
The URL can be used to link to this page
Your browser does not support the video tag.