My WebLink
|
Help
|
About
|
Sign Out
Home
8D Consent 2020 0928
CityHall
>
City Clerk
>
City Council
>
Agenda Packets
>
2020
>
Packet 2020 0928
>
8D Consent 2020 0928
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
10/8/2020 3:58:50 PM
Creation date
9/23/2020 12:22:44 PM
Metadata
Fields
Template:
CM City Clerk-City Council
CM City Clerk-City Council - Document Type
Agenda
Document Date (6)
9/28/2020
Retention
PERM
Document Relationships
Reso 2020-123 Clean Air Grant Funding with BAAQMD Class IV Bike Lanes
(Approved)
Path:
\City Clerk\City Council\Resolutions\2020
Reso 2020-124 Reduction in Vehicle Travel Lanes and Bicycle Lane on Fairmont Drive
(Approved)
Path:
\City Clerk\City Council\Resolutions\2020
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
103
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).
Download electronic document
View images
View plain text
<br /> <br /> <br /> <br />Page 11 <br /> <br /> <br />Fairmont Drive Class IV Bike Lane Installation Project November 2, 2018 <br />CUMULATIVE CONDITIONS ANALYSIS <br />DKS also evaluated the operation of Fairmont Drive under the cumulative condition AM and <br />PM peak periods. Forecast volumes for the Midday period were not available. The cumulative <br />scenario assumes that the transit-oriented development has been constructed. <br />Cumulative Conditions Operational Analysis <br />Cumulative traffic operations at the three study intersections and along the corridor were <br />assessed using Synchro software. Expected turn movement counts for the future year were <br />provided by the City of San Leandro. The AM and PM peak hour counts as well as roadway <br />and intersection geometry for all three signalized intersections are illustrated in Figure 4. <br />DKS assumed that the cycle length would change from existing conditions for the cumulative <br />year. However, to be conservative it was assumed that coordination priority would remain on <br />the Hesperian Boulevard corridor and the E. 14th Street corridor, as it is today. Therefore, <br />individual intersection timings were optimized but the Fairmont Drive corridor was assumed to <br />operate without coordination in the east-west direction. <br />As shown in Table 6, all study intersections are expected to operate at an acceptable LOS <br />during the Cumulative AM and PM peak periods. The detailed reports from Synchro are <br />included in Appendix B. <br />Table 7 shows the Arterial LOS analysis results. As shown, the corridor is expected to operate <br />at acceptable LOS eastbound during the AM peak period. However, the arterial is expected to <br />operate at LOS F westbound during the AM peak period and PM peak period and eastbound <br />during the PM peak period. Arterial operation improvement in the westbound direction during <br />the PM peak period as compared to existing conditions is due to signal timing modifications. <br /> <br />Table 6: Cumulative Delay (Seconds)/LOS <br />Study Intersection Intersection Control AM <br />Peak <br />PM <br />Peak <br />1) Fairmont Drive/Hesperian Boulevard Signalized 60.4/E 75.9/E <br />2) Fairmont Drive/Bayfair Drive Signalized 21.7/C 36.8/D <br />3) Fairmont Drive/E. 14th Street (SR 185) Signalized 53.9/D 49.9/D <br />Note: Signal retiming assumed for Cumulative condition. Reduction in delay from existing conditions <br />(current signal timing) is due to retiming. <br /> <br />Table 7: Cumulative Arterial LOS <br /> Study Segment Signal Delay <br />(s) <br />Arterial <br />Speed (mph) <br />Arterial <br />LOS <br />AM EB: Hesperian Boulevard to E.14th Street 58.7 10.2 E <br />WB: E. 14th Street to Hesperian Boulevard 149.3 5.1 F <br />PM EB: Hesperian Boulevard to E.14th Street 92.9 7.3 F <br />WB: E.14th Street to Hesperian Boulevard 59.2 9.9 F <br />174
The URL can be used to link to this page
Your browser does not support the video tag.