My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
Resolution 2008-26
PORTAL
>
CITY COUNCIL RECORDS
>
RESOLUTIONS (45.160)
>
2000-2009 Resolutions
>
2008 Resolutions
>
Resolution 2008-26
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
3/12/2021 2:48:08 PM
Creation date
7/11/2008 2:16:41 PM
Metadata
Fields
Template:
City Council Records
Doc Type
Resolution
Signed Date
6/17/2008
Ord/Res - Year
2008
Ord/Res - Number
26
Original Hardcopy Storage
7D5
Supplemental fields
Test
RES 2008-26
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).
Show annotations
View images
View plain text
t <br />L1S ?+:~ ~:~,rzr,inc~r <br />.,, <br />Project No. NH 0361-(f7~(14133) <br />• Evaluate extension of climbing lanes on US 36 between McCaslin Boulevard and Table Mesa to bus-only lanes as well as <br />the use of shoulders for transit during peak travel periods. Identify 'triggers' for when this design approach would be <br />considered. <br />• Examine low cost options to connect US 36 managed lanes to north I-25 bi-directional HOT lanes. Evaluate opportunities <br />to facilitate travel time savings for buses not able to operate in managed lanes. <br />• Assess specific premium components to support BRT transit operations. This assessment would consider, but would not <br />be limited to, special vehicles, service image and identify treatments such as bus wraps, signal priority strategies (such as <br />queue jump lanes) at interchanges, prepaid boarding, boarding and alighting all doors, specialized marketing, <br />transportation demand management, adequate parking and local transit service and connections. <br />• Identify logical projects with independent utility based on available funding. <br />• Research, analyze, and seek alternate funding mechanisms and project delivery methods to maximize the construction of <br />identified logical projects as early as possible. <br />• Examine the feasibility of retaining the westbound I-27Q access to Broadway. <br />PHASING AND IMPLEMENTATION STEPS <br />The PAC has placed a high priority on congestion relief through the extension of the managed lanes in the initial phase of <br />construction. Accordingly, the phasing and financing plan will focus on initially constructing useful components that improve transit <br />time consistent with the preferred alternative. All implementation phases will be developed concurrently with the engineering, <br />design, and construction analysis on the preferred alternative. These phases will be developed consistent with community <br />priorities, agency approval, and the availability, eligibility and appropriate uses of reasonably available funding sources. <br />Stakeholders will aggressively pursue financing options in partnership with CDOT and RTD. Alternative financing options and <br />project delivery methods such as design-build will be considered to accelerate implementation. The phasing plan should be <br />sufficiently flexible to accommodate the requirements of specific funding sources as they become available. <br />FUTURE STAKEHOLDER ENGAGEMENT <br />Future stakeholder engagement is necessary to complete the FEIS and reach a Record of Decision for the U.S. 36 Corridor. As <br />the PAC's combined alternative advances through the FEIS analysis, the agencies will meet with stakeholders at established <br />project milestones to share findings, gather input, and address concerns. The PAC will be an important forum for evaluation, <br />communication and public involvement in development and analysis of the phased ROD, Regular project updates will also be <br />provided through established stakeholder meetings, project newsletters, project website and public meetings. <br />Page 3 of 3 <br />
The URL can be used to link to this page
Your browser does not support the video tag.