My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
Item 12 - Select Locally Preferred Alternative for the First Street Multimodal Boulevard Study
Clerk
>
Agenda Packets / Staff Reports
>
City Council (2004 - Present)
>
2026
>
05/05/2026 Regular, HA
>
Item 12 - Select Locally Preferred Alternative for the First Street Multimodal Boulevard Study
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
4/29/2026 11:42:36 AM
Creation date
4/29/2026 11:38:58 AM
Metadata
Fields
Template:
City Clerk
Agency
Public Works
Item #
12
Date
5/5/2026
Destruction Year
P
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.
/
233
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
Select Locally Preferred Alternative for the First Street Multimodal Boulevard Study <br /> May 5, 2026 <br /> Page 8 <br /> STAFF RECOMMENDATION AND NEXT STEPS <br /> Staff recommends approval of Option 2 — Enhanced Bicycle and Pedestrian Zone <br /> Concept as the Locally Preferred Alternative. <br /> This option delivers optimal safety design features, particularly for pedestrians and <br /> bicyclists, through reduced crossing distances, separated facilities, and traffic calming <br /> measures. It maintains compatibility with existing transit operations while enhancing <br /> reliability through signal priority improvements. Importantly, it achieves these benefits <br /> without requiring right-of-way acquisition or reliance on external service changes. <br /> Compared to the other alternatives, Option 2 provides the greatest overall benefit with <br /> manageable trade-offs, including a modest increase in travel time of approximately 1.5 <br /> minutes in the westbound direction. It represents a practical, balanced solution that <br /> advances the City's Vision Zero goals, supports multimodal mobility, and reflects both <br /> community input and technical analysis. <br /> Selection of an LPA at this time will allow the City and OCTA to complete final design <br /> plans, specifications, and engineering estimates by the December 2026 grant deadline <br /> and position the project to competitively pursue construction funding. Construction <br /> funding pursued will include, but not be limited to, the Transit Rail and Intercity Rail <br /> Capital Program (TIRCP) through CaISTA, the FY26 Safe Streets and Roads for All <br /> (SS4A) grant program from the US Department of Transportation, and Caltrans' Active <br /> Transportation Program (ATP), Local Partnership Program (LPP), and Solutions for <br /> Congested Corridors Program (SCCP). <br /> At present, construction funding has not been secured, and implementation will be <br /> contingent upon future grant awards. Construction costs are estimated to be <br /> approximately $45 million. Due to the reliance on securing grant funds and timelines <br /> related to the grant process, Staff estimates that construction would not commence until <br /> 2028, at the earliest, and in all cases would be scheduled to not commence until other <br /> major corridor projects such as Bristol Street widening and Warner Avenue widening <br /> are completed. <br /> ENVIRONMENTAL IMPACT <br /> There is no environmental impact associated with the action. Staff will return in the future <br /> for Council approval of environmental clearance in accordance with CEQA when project <br /> plans are completed for the selected Locally Preferred Alternative. <br /> FISCAL IMPACT <br /> Planning, environmental clearance, and final engineering for the selected LPA are fully <br /> funded through the REAP 2.0 grant, which expires in December 2026. With Council's <br /> selection of the LPA, staff will begin seeking grant opportunities to fund the construction <br /> of the LPA. <br />
The URL can be used to link to this page
Your browser does not support the video tag.