Contra Costa Sub-regional Action Plans for the Routes of Regional Significance Multimodal Traffic Service Objectives (MTSO)

Transcription

1 ATTACHMENT B Contra Costa Sub-regional Action Plans for the Routes of Regional Significance Multimodal Traffic Service Objectives () Draft Monitoring Report Prepared by Iteris, Inc. February 2018

2

3 TABLE OF CONTENTS ES Executive Summary Introduction Changes to Transportation System Additional Measures Methodology Intersection Analysis way Segment Analysis Transit Ridership Additional Performance Measures Monitoring Results Intersection Analysis way Segment Analysis Transit Ridership Additional performance measures Summary of Findings/Recommendations Appendices Monitoring Report (Draft) i

4 ES Executive Summary This report documents the monitoring results of Contra Costa County s multi-modal traffic service objectives (s). The s are applied to the roads of significance as designated by each Regional Transportation Planning Committee (RTPC) within the County. The monitoring efforts evaluate whether the transportation system achieves the standards adopted in the RTPC s 2014 Action Plan. The majority of s were monitored using the combination of (INRIX Analytics or Caltrans PeMS) commercial speed data, the manual turning movement counts, and in-field observations. The monitoring results are summarized below: Intersection Level of Service: A total of 231 intersections were monitored in. 6% (15) locations operated at lower than standards during the AM or PM peak period way Segment Level of Service: A total of 20 roadway segments in the East County were analyzed. Ten segments (in the AM peak) and eleven segments (in the PM peak) didn t achieve the standards Average Speed: All 16 monitored roadway segment in the Central County met the standards Index: A total of 34 roadway segment were monitored using delay index. 1% (5) segments didn t achieve the standards Duration of Congestion: One roadway segment was analyzed; it met the standard HOV Lane Utilization: A total of four roadway segments were monitored; all met the standards, except for the I-80 WB segment in the West County during the AM peak period Vehicle Ridership: A total of three roadway segments were monitored; none met the standards Vehicle Occupancy: A total of two roadway segments were monitored; neither met their standard Monitoring Report (Draft) 1

5 Transit Ridership: BART loading factors were monitored in Lamorinda; all monitored loading factors met the standard Maximum Side Street Wait Time: three out of the total of 13 roadway segments exceeded standards Several additional measures were monitored and reported this report at CCTA s request. Since no specific standards are defined in the Action Plans for these s, they are reported as informational only s: vehicle volumes, pedestrian or bicycle volumes, frequency of collision, bus ridership, pedestrian delay at the signalized intersection, and pavement condition. Monitoring Report (Draft) 2

6 1 Introduction As part of Contra Costa County s transportation planning and growth management responsibilities, Contra Costa County Transportation Authority (CCTA) regularly monitors the performance of the transportation system in Contra Costa. Two of the main components of this transportation performance monitoring effort are the Countywide Comprehensive Transportation Plan (CTP), and the monitoring of the Multimodal Transportation Service Objectives (s) as part of updates of the Action Plan for Routes of Regional Significance. The CCTA Action Plan designates and defines the County s transportation performance measures (for performance monitoring purposes) and the service objective for each of the designated intersections and roadway segments. On a quadrennial basis (i.e., once every four years) through the CCTA s Multi-Modal Monitoring program, CCTA evaluates the performance of the County s transportation system and identifies those monitored locations which operated below the predetermined standards (which were last updated in 2014) and highlights long-term transportation utilization, growth and congestion trends. CCTA has monitored the achievement of the level-of-service standards established in the County s Congestion Management Program since the first CMP in 1991; and CCTA has regularly maintained and updated this monitoring report since This monitoring report is divided into four chapters: Chapter 1 Introduction: provides an introduction and describes the background for the monitoring efforts Chapter 2 Methodology: documents the performance evaluation (analytical) methodologies and describes the underlying data sources Chapter 3 Results: presents the results the study s findings, divided into three parts including intersection analysis, roadway segment analysis and other reporting elements (e.g., pedestrian, bicycle and transit) Chapter 4 Summary of Findings: summarizes the monitoring results and highlights the locations that failed to meet the designated 2014 standards Monitoring Report (Draft) 3

7 1.1 Changes to Transportation System Since the last monitoring in, there were some significant changes made to the County s transportation system, including: State Route 4 / State Route 160 Connector Ramps State Route 4 East Widening: Loveridge to Somersville Interstate 680 Express Lane Conversion(s) Interstate 80 / San Pablo Dam Interchange Improvements 1.2 Additional Measures The following measurements are new in this monitoring, which are subject to the s identified in each Action Plan. Duration of congestion Average trail user delay Frequency of collision Pavement condition Monitoring Report (Draft) 4

8 2 Methodology This chapter describes the methodology and underlying assumptions used to quantify the performance on the intersections, roadway segments and transportation elements. This chapter of the report is divided into three sections by the type of monitored locations (roadway intersections, roadway segments and other transportation elements or facilities). 2.1 Intersection Analysis This section summarizes the two-step methodology of calculating the measures for the designated reported roadway intersections. The first step in the reporting process is to collect intersection turning movement count data, in accordance with CCTA s Technical Procedures. For reporting side street wait times, the number of signal cycles required for back of queue vehicles to clear the intersection was recorded during the AM and PM peak hours for 60 minutes (7:00 AM to 8:00 AM and 5:00 PM to 6:00 PM) at each intersection. The second step in the evaluation process is to evaluate the performance of the roadway intersection and report the mandated measures and compare the current performance of the roadway intersections to the performance thresholds in the CCTA Action Plan Data Collection The project team selected the data collection days to ensure that all count data were collected on Tuesdays, Wednesdays and Thursdays during AM and PM peak hours in April. The days in the following categories were removed or excluded from the data collection period: Public Holidays and School Vacations (including Spring Breaks); Special Events (no special events were observed to impact traffic conditions during the monitoring period); and Closures and Construction Activities Intersection Level of Service, V/C and Average Stopped The intersection Level of Service () measures were estimated using the Transportation Research Board s Highway Capacity Manual (HCM) 2000 and HCM 2010 methodologies. The Monitoring Report (Draft) 5

9 analyses were performed using the Synchro intersection analysis software. The evaluation input data prepared by the project team included the turning movement volume (i.e., count) data, intersection geometry and roadway network data, and intersection signaltiming plans. The team consulted with CCTA staff to resolve conflicts when inconsistencies were identified between current timing plans and the Contra Costa member agency provided signal timing information. The Synchro intersection analysis software generated the vehicular delays (in seconds) and for the AM and PM peak hours of operation. The HCM s thresholds were established as a function of the intersection s vehicular delay values, as shown in Table 1. A value of A describes a state of very low traffic volumes and no significant traffic delays. This means that most of vehicles arrive during the signal s green time. On the other hand, a of F represents an intersection with high levels of congestion, over saturated traffic conditions, and long queues upstream of the intersection. For reporting, the average stopped delays were expressed in units of signal cycles the number of signal cycles needed to clear the intersection. The reported delays (in units of signal cycles) was estimated by dividing the average stopped delay (in seconds) by the signal s cycle length (in seconds per cycle). The previously described evaluation was performed for: 82 locations in the Tri Valley sub area (); 56 locations in the West County (); 41 locations in the East County (); 50 locations in the Central County (, V/C and Average Stopped ). Table 1: HCM 2010 & 2000 Level of Service Criteria for Signalized Intersections Level of Service Average Control General Description (seconds/vehicle) A 0-10 Free Flow B >10-20 Stable Flow (slight delays) C >20-35 Stable flow (acceptable delays) D >35-55 Approaching unstable flow (tolerable delay, occasionally wait through more than one signal cycle before proceeding) E >55-80 Unstable flow (intolerable delay) F > 80 Forced flow (congested and queues fail to clear) Monitoring Report (Draft) 6

10 2.1.3 Maximum Side Street Wait Time The Lamorinda Action Plan contains a for Side Street Wait Time. The maximum side street wait time is reported directly from field observations at each of the designated roadway intersections. The locations where side street wait time analyses were performed are: Pleasant Hill - Maintain a maximum wait time for drivers on side streets wishing to access Pleasant Hill or Taylor of one signal cycle or less; and Camino Pablo/ San Pablo Dam - The maximum wait time for drivers on side streets wishing to access San Pablo Dam or Camino Pablo should be no greater than one signal cycle. 2.2 way Segment Analysis This section summarizes the methods for data collection and data analyses for freeway and arterial roadway segment reporting. The vast majority of the roadway segment evaluations were performed using commercially available vehicular speed data (i.e., INRIX Analytics speed data). way travel time data were collected via floating car runs (sometimes called probe vehicles or tach runs) for roadway segments where the commercial speed data were unavailable or deemed insufficient because of sample size limitations Speed,, Index The average vehicular speeds, Level of Service (), and delay index estimation use similar inputs and data processing and evaluation techniques. Peak hour average vehicular speeds is the most influential variable (input) in the roadway segment estimation process. Further, the estimation and reporting processes are consistent with previous reporting periods Data Collection The roadway segment travel time data were collected (i.e., downloaded) from the INRIX Analytics website, or were obtained via floating car runs for segments where the INRIX data were not available. A) INRIX Data The downloaded segment-based INRIX data were filtered to remove: Holidays during the monitoring period; Monitoring Report (Draft) 7

11 Times outside the morning and afternoon peak periods (times outside the 6:00-10:00 A.M. and 3:00-7:00 P.M. windows); Days other than Tuesdays Thursdays; Data points impacted by construction and special events, as applicable; and Data points with low INRIX quality scores (INRIX data quality scores of 10 and 20) 1. Similar to CMP Monitoring, roadways undergoing short-term construction and/or with ongoing incidents were reviewed for anomalies in the reported vehicular speeds. To be conservative, the data collected on the segments which might have been impacted on those identified construction/incident days were excluded. This filtration process insures that the speeds data used in the monitoring is reflective of the traffic conditions experienced on an average workday by commuters. Additionally, data collected on days with significant weather events were removed. While there were some public holidays during the spring of, none occurred on Tuesdays, Wednesdays or Thursdays. Local schools were also in session during the data collection period. B) Floating Car Data The speed data for the Pleasant Hill segment between Geary and Taylor was supplemented with floating car runs, due to the insufficient sample size from INRIX data. In accordance with Technical Procedures 2, the floating data were collected on Tuesday, September 26, Data Processing The () performance measure computation is a four-step process that entails: 1) spatial conflation; 2) spatial coverage check; 3) temporal aggregation; and 4) computation of required performance measure. The following sections provide additional detail. Note that the floating car data were collected on the designated segment during the peak periods. Therefore, the steps one through three do not apply to the floating car data. 1 INRIX includes a data quality score that accompanies every INRIX data point. A score of 30 indicates data are exclusively generated from real-time sources; a mix of historical and real-time sources are used (indicated by a score of 20); and data are exclusively generated from historical data (indicated by a score of 10). 2 Technical Procedures, CCTA, January 16 Monitoring Report (Draft) 8

12 1) Spatial Conflation Raw INRIX data provides travel time data along each Traffic Message Channels (TMC) in one-minute intervals. A TMC is a relatively short section of a roadway, generally in the range of a half-mile or so. The first step of analysis includes mapping the INRIX TMCs (and the raw speed data to the County s segments. The INRIX-TMCCCTA-Segment mapping file completed for the County s CMP efforts was used as a starting point for Monitoring spatial conflation efforts. A thorough review of TMC links over each segment was performed. Figure 1 shows a schematic example of mapping or combining four TMC links to one reporting segment. Note that the end of the last TMC link does not align with the end of the Segment. In these instances, only the overlapping portion of the TMC is used in subsequent steps in the evaluation process. Figure 1: End points of and TMC do not align TMCs % 2) Coverage Check Prior to the temporal aggregation, a reality check was performed to assure that small sample estimation errors did not negatively impact the reliability of the reported s. The project team performed a check to ensure that time-periods with excess TMCs removals were not included in the further analysis. To do this, the team removed all one-minute time periods where the total mapped TMC data available was less than 99%. Using the 99% threshold, only a small minority of the time periods were flagged as having inadequate sample size. In these cases, the threshold was lowered to 70% to ensure adequate sample size. The number of oneminute data points for segment varies as a result of removing data points during this filtering process. The team selected a minimum sample size threshold for sample sizes of 100 observations (i.e., data points). Locally collected floating car surveys were performed where the segment failed the minimum sample size criteria. In the monitoring, this occurred at only one location - Pleasant Hill between Geary and Taylor. Monitoring Report (Draft) 9

13 3) Temporal Aggregation In this step, the one-minute intervals for each segment were aggregated to peak periods. The peak hour speeds were estimated in 15-minute moving average time-periods, e.g., from 6:00 to 7:00 A.M., then from 6:15 to 7:15 A.M., etc. Next, the lowest peak hour speed (during the peak period) was used as an input to the and delay estimation process, which is described in the next section. 4) Compute Required Performance Measure (Speed,, and Index) The procedure of calculating and delay index is in conformance with CCTA s Technical Procedures. For floating car runs, the speeds were averaged to estimate the peak hour speed. The assignment process is consistent with previous reporting efforts and consistent with legislative requirements from the California Government Code as shown in Table 2 for freeway segments, and Table 3 for arterial street segments. Table 2: Freeway Level of Service s (HCM 1985) Traffic Speed Level of Service (miles/hour) A 60 B 57 C 54 D 46 E 30 F < 30 Table 3: Arterial Level of Service s (HCM 1985) Traffic Speed Level of Service (miles/hour) A 55 B 50 C 45 D 40 E < 40 Monitoring Report (Draft) 10

14 The Index is an expression of the amount of time required to travel between two points during the peak hour as compared to a baseline. The numerator of the delay index formula, the free flow travel time is defined as the time it takes to traverse a roadway segment at the posted speed limit. The denominator of the delay index formula measured or actual peak hour travel time experienced by motorists, which was the peak hour speed identified in the third step as mentioned above Duration of Congestion, HOV Lane Utilization The Tri-valley Action Plan includes s for duration of congestion for the mixed flow or general-purpose lanes on I 680 south of SR 84. The duration of congestion captures or measures the number of congested hours per average workday. standards for HOV lane utilization (in vehicles per hour) were established in the East County and West County Data Collection Vehicular speed data were downloaded from the Caltrans PeMS website for the vehicle detector station (VDS) locations along the freeway s segments during non-holiday Tuesdays, Wednesdays and Thursdays for the months of February, March, and April of Data Processing Duration of congestion is defined as the number of congested hours during a normal or average non-holiday workday. The standard of no more than five (5.0) hours was established for I 680 south of SR 84 in the Tri-valley. First, the five-minute speeds were aggregated to each half-hour periods for each PeMS detector location. Second, a congested half-hour period was flagged if it performed at a speed below 35 miles per hour. Finally, the number of congested half-hour periods were summed and reported as total (daily) hours of congestion. HOV lane usage is measured by the number of vehicles using the HOV lane at the highest HOV volume along the reporting section. The East County established standard for freeways with HOV lane utilization exceeding 600 vehicles per lane in the peak direction during the peak hour. The maximum volume was identified by aggregating five-minute traffic volumes (obtained from the Caltrans PeMS website) to peak hour volume. Monitoring Report (Draft) 11

15 2.2.3 Average Vehicle Ridership The Tri-valley Action Plan contains a for I 580 and I 680 that specifies the ratio of total person commute trips to vehicles used for commuting on I 580 and I 680 increased by 10% from 1.1 to Data Collection Average vehicle ridership was estimated using data from the Bay Area Manage Lane Report published by Caltrans in and Average Vehicle Occupancy The standard for average vehicle occupancy is included in the Lamorinda Action Plan. It is a measure of the average number of passengers (including the driver) per vehicle on Pleasant Hill and Camino Pablo/ San Pablo Dam. The standards include: Increase the average vehicle occupancy on Pleasant Hill /Taylor to at least 1.3 during the peak commute hours by 2018; and Increase the average vehicle occupancy on Camino Pablo/San Pablo Dam to at least 1.3 during the peak commute hours by Data Collection Vehicle occupancy data were collected from a stationary position along Pleasant Hill and Camino Pablo/ San Pablo Dam. Video data captured traffic flow during AM and PM peak periods on May 23 rd and May 25 th,. In accordance with the Technical Procedures, the data were collected on mid-week workdays (i.e., Tuesdays, Wednesdays and Thursdays) on non-holiday days while local area schools were in session Data Processing The field data were reported in 15-minute intervals during AM and PM peak periods. The occupancy counts were then aggregated to estimate the average per peak period vehicle occupancy. Monitoring Report (Draft) 12

16 2.3 Transit Ridership The usage of public transit was monitored in the East County and the Lamorinda. There is no specified goal in the East County Action Plan. Lamorinda o Maintain an hourly average transit load factor (ratio of passengers to seats) of 1.5 or less when approaching Lafayette Station westbound and Orinda Station eastbound during each and every hour of service. East County o A measure of the average number of riders boarding a fixed-route bus during an hour of scheduled bus service when persons may board with a fare or pass. o A measure of the average number of weekday riders on all BART trains between the Bay Point and North Concord Stations Data Collection The transit ridership data were obtained directly from Tri Delta Transit, LAVTA and BART Description and Method of Calculation For East County, the average ridership per service hour was derived from the ridership for Tri Delta Transit fixed-route buses in a sample month (May ); BART passenger counts between the Bay Point and North Concord Stations (April ) were averaged to obtain the average number of weekday riders. For Lamorinda, BART ridership approaching the Lafayette Station westbound and Orinda Station eastbound was tallied and then averaged per service hour. 2.4 Additional Performance Measures The Tri-valley and Lamorinda Action Plans now contains s not reported in the previous monitoring cycles. Pedestrian and Bicycle Volumes: The Tri-valley Action Plans includes a for pedestrian and bicycle volumes using Iron Horse Trail (directly measured from field observations). Monitoring Report (Draft) 13

17 Crash frequency: The Tri-valley and Lamorinda Action Plan includes s for vehicle crash frequency and/or pedestrian or bicycle injury crash frequency. The collision data were obtained from the Caltrans Statewide Integrated Traffic Records System (SWITRS) for the calendar year Average Trail User at Major Crossings: The Tri-valley Action Plans includes a for pedestrian delay at the signaled intersection. The delays (in units of seconds) were determined by the cycle length and the green times for vehicles when pedestrians are prohibited to enter crosswalk with an assumption of uniform pedestrian arrival rate. Pavement Condition: The Tri-valley Action Plans includes a for Iron Horse Trail that measures the relative comfort of the trail for its users using the pavement condition. This was reported using Pavement Condition Index. Frequency of Lane Closure: The Lamorinda Action Plan includes a for the frequency of lane closure. Inventory of pedestrian and bicycle facilities: The Lamorinda Action Plan includes a for the inventory of pedestrian and bicycle facilities. Monitoring Report (Draft) 14

18 3 Monitoring Results This chapter summarizes the results from the monitoring at the designated roadway intersections and segments. 3.1 Intersection Analysis This section on roadway intersection analysis is divided into two sub-sections: 1) Intersection Level of Service () and Volume-to-Capacity ratio (V/C), and 2) Average Stopped and Maximum Side Street Wait Time. The intersection analysis monitoring results are summarized in Table 4 for Tri-valley County, Table 5 for the East County, Table 6 for the West County and in Table 7 for the Central County sub-region Intersection and V/C The and/or V/C ratios were analyzed for 231 locations: 82 locations in the Tri Valley sub area, 56 locations in the West County, 41 locations in the East County, and 50 locations in the Central County. Of these 231 locations, 13 locations currently exceed the standard threshold either in the AM and/or PM peak periods. The following locations are reported for each sub-region: Tri Valley: two (2) locations operate at a lower : T9: San Ramon Valley /Alcosta ; (HCM 2010 AM Peak); and T60: Stanley /Murrieta. (HCM 2000 AM and PM Peak) West County: five (5) locations operate at a lower : W1: San Pablo /John Muir Parkway; (HCM 2010 AM and PM Peak, HCM 2000 PM Peak) W5: San Pablo /Rumrill ; (HCM 2010 and 2000 PM Peak) W30: San Pablo /Richmond Parkway; (HCM 2010 and 2000 PM Peak) W49: Richmond Parkway/Westbound I-80 Ramps/Blume Drive; (HCM 2010 AM and PM Peak) and W55: Richmond Parkway/Pittsburgh. (HCM 2010 and 2000 PM Peak) Monitoring Report (Draft) 15

19 East County: four (4) locations operate at a lower : E12: Main Street/Delta ; (HCM 2010 and 2000 AM and PM Peak) Stop Control E23: Bailey /Leland ; (HCM 2010 AM Peak) E24: Railroad /Leland ; (HCM 2010 AM Peak) and E31: Lone Tree Way/West Tregallas. (HCM 2010 PM Peak) Central County: all locations operate at an acceptable level for and/or V/C standards. The V/C standard threshold of 1.5 for Central County intersections on Pacheco Blvd, Pleasant Hill Rd, Taylor Blvd, Treat Blvd, and Ygnacio Valley Blvd reflect the level of congestion on a given roadway. All intersections analyzed with V/C are at an acceptable level. Monitoring Report (Draft) 16

20 Table 4: Intersection Draft Results Tri Valley Sub Area Intersection ID Facility Cross Street T1 T2 T3 T4 T5 T6 T7 T8 T9 T10 T11 T12 Danville Danville Hartz Hartz San Ramon Valley San Ramon Valley San Ramon Valley San Ramon Valley San Ramon Valley San Ramon Valley Sycamore Valley Sycamore Valley Sycamore Valley HCM Method (sec) AM (sec) Livorna E C 33.6 C Stone Valley PM E D 36.3 D Diablo E C 24.6 C Railroad (South) Sycamore Valley Crow Canyon Norris Canyon Bollinger Canyon Alcosta Northbound I 680 Ramp Southbound I 680 Ramps Brookside Drive E C 29.8 C E C 41.1 D E D 46.9 D E D 36.2 D E D 52.1 D E F 58.8 E E B B 21.5 C B E B B 8.5 A B E B B 11.5 B B Monitoring Report (Draft) 17

21 Intersection ID Facility Cross Street HCM Method (sec) AM (sec) PM T13 T14 T15 T16 T17 T18 T19 T20 T21 T22 T23 T24 T25 Sycamore Valley Camino Tassajara Camino Tassajara Crow Canyon Crow Canyon Crow Canyon Crow Canyon Crow Canyon Crow Canyon Crow Canyon Bollinger Canyon Bollinger Canyon Bollinger Canyon Camino Tassajara Sherburne Hills Crow Canyon Blackhawk Bollinger Canyon Northbound I 680 Ramp Southbound I 680 Ramp Crow Canyon Place Camino Ramon Alcosta Dougherty Northbound I 680 Ramp Southbound I 680 Ramp Sunset Drive Chevron Circle E B C 17.1 B B E B B 14.1 B C E D D 43.4 D D E C C 28.9 C D E B B 19.0 B C E C B 29.6 C C E C C 46.2 D D E E C 53.0 D D E B B 15.6 B C E B B 22.9 C C E C B 22.4 C C E D C 67.8 E D E D D 31.8 C D T26 Bollinger Camino E C F 41.5 D F Monitoring Report (Draft) 18

22 Intersection ID Facility Cross Street T27 T28 T29 T30 T31 T32 T33 T34 T35 T36 T37 T38 T39 T40 T41 T42 T43 T44 Canyon Bollinger Canyon Alcosta San Ramon Valley Alcosta Dougherty Dougherty Dougherty Tassajara Tassajara Tassajara Tassajara Dublin Dublin Dublin Dublin Dublin Dublin San Ramon Ramon Alcosta Northbound I 680 Ramps Southbound I 680 Ramps Village Parkway Westbound I-580 Ramps Dublin Amador Valley HCM Method (sec) AM E D E E D C (sec) PM 56.0 E 65.7 E E C 45.1 D E B B 16.9 B B E B 17.0 B E E D 28.9 C Fallon E C C 23.1 C D Dublin E Gleason E C 18.9 B Westbound I-580 Ramps E Amador Plaza E C 41.1 D Regional Street Hacienda Drive Fallon San Ramon Viiage Parkway Amador Valley E E 24.5 C E E E E F D Monitoring Report (Draft) 19

23 Intersection ID Facility Cross Street T45 T46 T47 T48 T49 T50 T51 T52 T53 T54 T55 T56 T57 T58 T59 T60 T61 T62 Fallon Fallon El Charro Stanley Isabel Isabel Isabel Isabel First Street First Street North Canyons Parkway North Canyons Parkway / Portola Holmes Street Holmes Street Airway Stanley Hopyard Hopyard Gleason Drive Eastbound I-580 Ramps Westbound I-580 Ramps E E E HCM Method (sec) AM (sec) Isabel E D 14.9 B Airway Jack London Vallecitos Vineyard Eastbound I-580 Ramps Westbound I-580 Ramps Collier Canyon Isabel Ave Extension Murrieta Blvd/4th Street Concannon Eastbound I-580 Ramp Murrieta E E E E PM E B 18.9 B E A 8.2 A E E E E E E F F Owens Drive E D 68.5 E Stoneridge Drive E D 39.9 D Monitoring Report (Draft) 20

24 Intersection ID Facility Cross Street T63 T64 T65 T66 T67 T68 T69 T70 T71 T72 T73 T74 T75 T76 T77 T78 T79 T80 Hopyard Hopyard Hopyard Santa Rita Santa Rita Santa Rita Santa Rita Stanley Stanley Stoneridge Drive Stoneridge Drive Stoneridge Drive Sunol Sunol Sunol West Las Positas Bernal Bernal Eastbound I-580 Ramps West Las Positas HCM Method (sec) AM (sec) PM E D 19.5 B E C 35.3 D Valley E C 33.5 C West Las Positas E C 25.3 C Valley E D 45.2 D Eastbound I-580 Ramps Stoneridge Drive Valley /Bern al E D 40.9 D E E 75.8 E E D 36.7 D Main Street E C 18.9 B West Las Positas Northbound I 680 Ramps Southbound I 680 Ramps Bernal Northbound I 680 Ramps Southbound I 680 Ramps Hacienda Drive Northbound I 680 Ramps Southbound I 680 Ramps E C 38.2 D E B 8.3 A E B 14.1 B E D 34.4 C E C 46.1 E E C 21.8 C E C 21.1 C E C 29.8 C E B 20.9 C Monitoring Report (Draft) 21

25 Intersection ID Facility Cross Street T81 T82 Hacienda Drive Hacienda Drive Eastbound I-580 Ramps Westbound I-580 Ramps HCM Method (sec) AM (sec) PM E C 14.1 B E B 8.8 A Monitoring Report (Draft) 22

26 Table 5: Intersection Draft Results West County Sub Area Intersection ID Facility Cross Street W1 W2 W3 W4 W5 W6 W7 W8 W9 W10 W11 W12 W13 W14 W15 W16 W17 W18 San Pablo San Pablo San Pablo San Pablo San Pablo San Pablo San Pablo San Pablo San Pablo San Pablo San Pablo San Pablo San Pablo San Pablo San Pablo Dam San Pablo Dam San Pablo Dam San Pablo Dam John Muir Parkway Pinole Valley HCM Method (sec) AM (sec) PM E F D F E E A B 13.8 B B Appian Way E C C 39.6 D D Hilltop Drive E D C 57.7 E E Rumrill E D C 98.3 F D El Portal Drive E C C 33.5 C C 20 E D D 47.4 D D San Pablo Dam McBryde Westbound I 80 Ramps Eastbound I 80 Ramps / Roosevelt E C C 37.2 D D E C C 27.4 C C E D B 22.9 C D E B C 30.7 C D Barrett E C C 34.2 C C Cutting Central Westbound I 80 Ramps Eastbound I-80 Ramps /Amador Street E C C 27.5 C C E D C 47.2 D C E C C 35.9 D C E D C 49.7 D E El Portal Drive E D D 32.0 C D Appian Way E E C 50.4 D D Monitoring Report (Draft) 23

27 Intersection ID Facility Cross Street W19 W20 W26 W27 W28 W29 W30 W31 W32 W33 W34 W35 San Pablo Dam San Pablo Dam Cutting San Pablo /Parker San Pablo San Pablo San Pablo San Pablo San Pablo San Pablo San Pablo San Pablo Castro Ranch Bear Creek Carlson HCM Method (sec) AM (sec) PM E C C 27.5 C C E D 63.6 E D C 24.1 C Willow E A 9.4 A Sycamore Tennant Richmond Parkway Robert H Miller Drive E B C 13.3 B C E B B 74.3 E A E E C 98.7 F C E C B 26.1 C B Church Lane E C B 35.9 D C Potrero E C C 27.5 C B Schmidt Lane E B B 13.8 B B Carlson E E C 45.9 D C W36 23rd Street Rheem D B C 12.6 B C W37 23rd Street Barrett D B B 19.2 B B W38 W39 W40 W41 W42 23rd Street 23rd Street Appian Way Appian Way Appian Way Macdonald Cutting Tara Hills Drive-Canyon Drive Westbound I-80 Ramps Eastbound I-80 Ramps D A A 12.4 B A D C B 31.9 C C D D C 40.9 D C D C D 22.9 C D D A A 11.3 B B Monitoring Report (Draft) 24

28 Intersection ID Facility Cross Street W43 W44 W45 W46 W47 W48 W49 W50 W51 Appian Way Carlson Carlson Central Central Central Richmond Parkway Castro Street Castro Street Fitzgerald Drive-Sarah Drive Bayview Central HCM Method (sec) AM (sec) PM D C C 34.3 C D D D D 25.3 C C D C B 20.5 C B Pierce Street D B B 12.6 B B Westbound I-80 Ramps Eastbound I-80 Ramps Westbound I-80 Ramps /Blume Drive Eastbound I-580 Ramps Westbound I-580 Ramps D B B 14.2 B C D B B 25.7 C C D F B 64.4 E B D B 21.2 C D C 35.9 D W52 Castro Street Hensley Street D C 48.9 D W53 Castro Street Mills Street D A 6.5 A W54 W55 W56 W57 W58 W59 W60 W61 Richmond Parkway Richmond Parkway Richmond Parkway Richmond Parkway Richmond Parkway Richmond Parkway Richmond Parkway Richmond Parkway Gertrude Pittsburgh D B C 31.2 C D D D F 59.4 E F Parr D D F 40.6 D C Hensley Street D C C 19.1 B C Barrett D B B 18.5 B C McDonald D B C 18.5 B C Eastbound I-580 Ramps Westbound I-580 Ramps D C C 34.6 C B D C B 29.7 C B Monitoring Report (Draft) 25

29 Table 6: Intersection Draft Results East County Sub Area Intersection ID Facility Cross Street E1 E2 E3 Railroad Railroad Railroad Westbound SR-4 Ramps /California Eastbound SR-4 Ramps Buchanan HCM Method (sec) AM (sec) PM E C 16.1 B E C 39.8 D E D 23.1 C E4 Main Street Neroly E C C 26.8 C C E5 Main Street Big Break E B C 48.5 D D E6 Main Street Oakley /Empire E B C 18.3 B B E7 Main Street Cypress E C C 43.1 D C E8 E10 E11 Brentwood 18th Street- Main Street Main Street Balfour E D D 51.3 D D Southbound SR-160 Ramps Northbound SR-160 Ramps D C B 29.5 C B D B B 13.0 B B E12 Main Street Delta D F 51.3 F E13 E14 E15 E16 E17 E18 Brentwood Brentwood Brentwood Brentwood Walnut Walnut Lone Tree Way D C C 33.6 C C Sand Creek Central Blvd- Sycamore D C C 28.5 C C D B B 17.2 B B Oak Street D C C 25.4 C C Oak Street D C B 22.6 C B Balfour D C D 34.4 C C Monitoring Report (Draft) 26

30 Intersection ID Facility Cross Street E19 E20 E21 E22 Walnut Bailey Bailey Bailey Marsh Creek Willow Pass Westbound SR-4 Ramps Eastbound SR-4 Ramps HCM Method (sec) AM (sec) PM D C C 36.2 D D E C C 32.7 C C E C C 17.6 B B E C C 28.7 C C E23 Bailey Leland E F D 53.0 D C E24 E25 E26 E27 E28 E29 E30 E31 E32 E33 E34 E35 E36 E37 Railroad Somersville Somersville Somersville Somersville Lone Tree Way-A Street Lone Tree Way Lone Tree Way Lone Tree Way Lone Tree Way Lone Tree Way Lone Tree Way Lone Tree Way Lone Tree Way Leland D E E 47.0 D F Westbound SR-4 Ramps Eastbound SR-4 Ramps Delta Fair Buchanan Westbound SR-4 Ramps Eastbound SR-4 Ramps West Tregallas James Donlon Deer Valley Hillcrest Empire Fairview O'Hara D C C 24.7 C C D C B 33.9 C B D C C 40.5 D D D C D 27.4 C D D C C 21.4 C C D C C 28.2 C C D D B F C D C D 28.0 C D D C D 28.6 C D D C C 29.8 C C D C D 34.3 C D D D D 49.8 D D D D D 42.6 D D Monitoring Report (Draft) 27

31 Intersection ID Facility Cross Street E38 E39 E40 E41 E42 Hillcrest Hillcrest Hillcrest Leland Buchanan Westbound SR-4 Ramps Eastbound SR-4 Ramps Deer Valley Loveridge Loveridge HCM Method (sec) AM (sec) PM D A C 4.5 A C D C C 37.2 D C D C C 32.1 C C D C D 30.9 C C D C C 17.9 B C Monitoring Report (Draft) 28

32 Table 7: Intersection Draft Results Central County Sub Area Intersection ID Facility Cross Street C3 C11 C16 C17 C18 C19 C20 C22 C23 C24 C25 C27 C28 C31 C32 C33 Pacheco North Main Street Treat Treat Treat Treat Treat Ygnacio Valley Ygnacio Valley Ygnacio Valley Ygnacio Valley Ygnacio Valley Ygnacio Valley Ygnacio Valley Pacheco Pacheco or V/C AM HCM 2000 Results V/C or (sec) & V/C Results v/c or PM HCM 2000 Results V/C or (sec) & V/C Results v/c or John Muir C D 0.50 Geary E 41.2 D 61.3 E Clayton D D 0.90 Cowell E D 0.97 Oak Grove E D 0.98 Bancroft E / / 0.87 D / 0.72 D 1.17 Oak D C 0.80 Clayton C D 0.78 Alberta Way D D 0.88 Ayers D E 0.90 Cowell E 1.02 E Bancroft E / / 0.86 D 1.08 Walnut 47.8 / 0.85 D C C 0.98 Civic Drive E / / 0.77 D / 0.80 D 1.22 Shell B B 0.43 Howe B B 0.53 Monitoring Report (Draft) 29

33 Intersection ID Facility Cross Street C34 C35 C36 C37 C38 C39 C40 C41 C43 C44 C45 C46 C47 C49 C50 C51 C52 Pacheco Pacheco Pacheco Pacheco Taylor Taylor Taylor Taylor Taylor Pleasant Hill Pleasant Hill Pleasant Hill Pleasant Hill Treat Treat Treat Treat or V/C AM HCM 2000 Results V/C or (sec) & V/C Results v/c or PM HCM 2000 Results V/C or (sec) & V/C Results v/c or Morello C E 0.80 Arthur C C 0.65 Blum / WB SR-4 Ramps D E 0.85 Center D D 0.82 Ruth Drive D C 0.47 Norse Drive D D 0.54 Morello Ave D D 0.55 Apollo Way B B 0.68 Grayson E C 0.71 Paso Nogal C C 0.63 Devon B B 0.62 Westover Drive B B 0.33 Grayson D D 0.91 Jones C D 0.99 Cherry Lane C D 0.75 Carriage Drive C B 0.64 Winton Drive A B 0.77 Monitoring Report (Draft) 30

34 Intersection ID Facility Cross Street C53 C54 C55 C56 C57 C59 C60 C61 C62 C63 C64 C65 C66 C67 C68 C69 C70 Treat Treat Treat Treat Treat Ygnacio Valley Ygnacio Valley Ygnacio Valley Ygnacio Valley Ygnacio Valley Ygnacio Valley Ygnacio Valley Ygnacio Valley Ygnacio Valley Ygnacio Valley Ygnacio Valley Ygnacio Valley or V/C AM HCM 2000 Results V/C or (sec) & V/C Results v/c or PM HCM 2000 Results V/C or (sec) & V/C Results v/c or Oak Grove Plaza B C 0.64 San Simeon Drive C C 0.56 Navarone Way B B 0.72 Turtle Creek B B 0.54 Bel Air Drive B B 0.67 North California North Main Street D D D D 0.95 North Broadway D D 1.01 Homestead C D 1.09 Tampico Drive B C 0.92 La Casa Via C D 0.99 San Carlos Drive E F 0.90 Wiget Lane D C 1.04 Via Monte C B 0.72 Crystyl Ranch Michigan Park Highlands B C B B B C 0.53 Monitoring Report (Draft) 31

35 3.1.2 Average Stopped The Action Plan for the Central County includes a for the average stopped delay of vehicles, measuring how many cycles it takes to pass through an intersection. Table 8 shows the results of the average stopped delay. All intersections analyzed in the Central County meet or pass the average stopped delay threshold. Table 8: Average Stopped Central County Sub Area Sub Area Facility Cross/Street Segment (cycle) Observed AM PM Bailey Concord Bailey Clayton Treat Clayton Central County Treat Cowell Treat Oak Grove Ygnacio Valley Clayton Ygnacio Valley Alberta Way Ygnacio Valley Cowell Monitoring Report (Draft) 32

36 3.1.3 Maximum Side Street Wait Time The Action Plan for the Lamorinda area includes a of the maximum wait time for vehicles on a side street crossing a major street. The maximum number of cycles a vehicle should wait on a side street in Lamorinda is one cycle. Table 9 shows the results of the side street wait time analysis for 13 intersections. All intersections have acceptable wait times in the PM peak hour. On the other hand, three intersections have an observed side street wait time longer than the standards in the AM peak hour. Table 9: Side Street Wait Time Lamorinda Sub Area Sub Area Facility Cross/Street Segment Pleasant Hill Rancho View Drive (cycle) Observed Results AM PM AM PM Pleasant Hill Green Valley Drive Pleasant Hill Reliez Valley Pleasant Hill Spring Hill 1 1 Pleasant Hill Deer Hill 1 1 Camino Pablo Wildcat Canyon 1 1 Lamorinda Camino Pablo Monte Vista one or 1 1 Camino Pablo Los Amigos Court less 1 1 Camino Pablo Manzanita 2 1 Camino Pablo North Lane 1 1 Camino Pablo Miner 1 1 Camino Pablo Orinda Way 1 1 Camino Pablo Camino Sobrante 2 1 Monitoring Report (Draft) 33

37 3.2 way Segment Analysis Overall, the following location did not meet the standards: 1) Central County: One (1) location operated at a delay index that did not meet standards 2) East County: Ten (10) AM Peak and eleven (11) PM Peak locations operate at a not meeting standards 3) Lamorinda: Two (2) AM Peak and three (3) PM Peak locations operate at a not meeting standards 4) West County: One (1) location operate at a not meeting standards 2) Tri-valley: I-80 Westbound (AM peak hour) failed to meet the standards for the Duration of Congestion and HOV-Lane Utilization 3) Tri-valley: All (PM peak period) locations failed to meet the standards for average vehicle ridership 4) Lamorinda: All locations failed to meet the standards for vehicle occupancy This remainder of section on way Segment Analysis is divided into four parts: 3.2.1), Speed and Index 3.2.2) Duration of Congestion, HOV Lane Utilization 3.2.3) Average Vehicle Ridership 3.2.4) Average Vehicle Occupancy 3.2.1, Speed, and Index The delay index, average speed, and are determined by the peak hour speed computed in the same manner as previously described, using INRIX Analytics speed (and/or travel-time) data. Monitoring Report (Draft) 34

38 The results for the Central County, East County, Lamorinda County, Tri-valley County and West County are summarized in Table 10 through Table 15. Route Limits Dir Alhambra Alhambra Clayton Clayton Contra Costa Contra Costa Pacheco Pacheco Pleasant Hill Arch Street to Taylor Arch Street to Taylor Treat to Kirker Pass Treat to Kirker Pass Center to Astrid Drive Center to Astrid Drive Warren Street to Center Warren Street to Center Geary to Taylor Table 10: way Segment Analysis Central County Length (mile) NB 4.77 Measure AM Peak Observed Results PM Peak Observed Results SB EB WB Peak NB 3.52 Hour Speed (mph) SB NB SB NB * * 26.0 Monitoring Report (Draft) 35

39 Route Limits Dir Pleasant Hill Taylor Taylor SR-242 SR-242 SR-4 SR-4 I-680 Geary to Taylor Withers to Contra Costa Withers to Contra Costa I-680 to State Route 4 I-680 to State Route 4 Between Central County sub-area boundarie s Between Central County sub-area boundarie s Between central sub-area boundarie Length (mile) Measure AM Peak Observed Results PM Peak Observed Results SB * * 27.3 NB SB NB 3.07 s Between central I-680 sub-area boundarie s * Floating car runs conducted on 9/26/ Index SB EB WB NB SB Monitoring Report (Draft) 36

40 Table 11: way Segment Analysis East County Route Limits Dir Deer Valley Prewett Ranch to Sand Creek Length (mile) NB 0.6 Measure AM Peak Observed PM Peak Observed D E D E Deer Valley Walnut Walnut Cypress Cypress Deer Valley Deer Valley Sellers Sellers Balfour Balfour Vasco Vasco Prewett Ranch to Sand Creek Camino Diablo to Vasco Camino Diablo to Vasco Sellers to Bethel Island Sellers to Bethel Island Antioch limit/marsh Creek Antioch limit/marsh Creek Laurel Extension to Cypress Laurel Extension to Cypress Deer Valley to Brentwood Deer Valley to Brentwood Marsh Creek to Alameda County Line Marsh Creek to Alameda County Line SB 0.6 D D D E NB 0.89 D E D E SB 0.89 D E D E EB 1.96 D E D E WB 1.96 D E D E NB 4.87 D D D D SB 4.87 way Segment D D D D NB 0.5 D E D E SB 0.5 D D D E NB 4.78 D E D E SB 4.78 D E D E NB D B D E SB D E D B Monitoring Report (Draft) 37

41 Route Limits Dir Byron Highway Byron Highway Marsh Creek Brentwood to Alameda County Line Brentwood to Alameda County Line Deer Valley to SR-4 Length (mile) Measure AM Peak Observed PM Peak Observed NB 8.04 D D D D SB 8.04 D C D C EB 5.03 D D D C Marsh Creek Camino Diablo Camino Diablo SR-160 SR-160 SR-4 SR-4 Deer Valley to SR-4 Marsh Creek to Vasco Marsh Creek to Vasco Between State Route 4 and the Sacramento County line Between State Route 4 and the Sacramento County line Between East County sub-area boundaries Between East County sub-area boundaries WB 5.03 D C D C EB 3.58 D E D D WB 3.58 D D D D NB SB EB Index WB Results SR-4 SR-4 Between East County sub-area boundaries Between East County sub-area boundaries EB Index WB Monitoring Report (Draft) 38

42 Table 12: way Segment Analysis Lamorinda County Peak Periods Route Limits Dir Camino Pablo / San Pablo Dam Camino Pablo / San Pablo Dam Pleasant Hill Pleasant Hill Moraga Way Moraga Way Moraga Way Moraga Way Mt Diablo Mt Diablo Moraga Way to Inspiration Trail Moraga Way to Inspiration Trail SR24 to Taylor SR24 to Taylor Moraga to Bryant Way Moraga to Bryant Way Moraga Way to Mount Diablo Moraga Way to Mount Diablo Happy Valley to Brown Happy Valley to Brown Length (miles) EB 3.8 Measure AM Peak Observed Results PM Peak Observed WB Index Results WB NB SB EB NB SB EB WB Monitoring Report (Draft) 39

43 Route Limits Dir SR-24 SR-24 Alameda County Line to I- 680 Alameda County Line to I- 680 Length (miles) Measure AM Peak Observed Results PM Peak Observed Results EB WB Monitoring Report (Draft) 40

44 Table 13: way Segment Analysis Lamorinda County Off-Peak Periods Start Time Measure EB Observed Results WB Observed Results 12:00:00 AM :00:00 AM :00:00 AM :00:00 AM :00:00 AM :00:00 AM :00:00 AM :00:00 AM :00:00 AM :00:00 AM Index :00:00 PM :00:00 PM :00:00 PM :00:00 PM :00:00 PM :00:00 PM :00:00 PM :00:00 PM Monitoring Report (Draft) 41

45 Route Limits Dir Length (miles) Measure AM Peak PM Peak Table 14: way Segment Analysis Tri-valley County Monitoring Report (Draft) 42

46 Observed Results Observed Results I-580 Between Tri-valley sub-area boundaries EB I-580 I-680 I-680 I-580 I-580 I-680 I-680 SR-84 SR-84 Between Tri-valley sub-area boundaries Between Tri-valley sub-area boundaries (southern monitoring end point is Washington ) Between Tri-valley sub-area boundaries (southern monitoring end point is Washington ) Between Tri-valley sub-area boundaries Between Tri-valley sub-area boundaries Between Tri-valley sub-area boundaries (southern monitoring end point is Washington ) Between Tri-valley sub-area boundaries (southern monitoring end point is Washington ) Between I-580 and I- 680 Between I-580 and I- 680 WB NB 27.4 Peak Hour Speed (mph) SB EB Index WB NB SB NB SB Monitoring Report (Draft) 43

47 Route Limits Dir SR-4 SR-4 I-580 I-580 I-80 I-80 I-80 to Cummings Skyway I-80 to Cummings Skyway Between West sub-area boundaries (western end point is the middle of bridge) Between West sub-area boundaries (western end point is the middle of bridge) Between west sub-area boundaries Between west sub-area boundaries Table 15: way Segment Analysis West County Length (miles) EB 4.72 Measure Index AM Peak Observed Results PM Peak Observed Results WB EB WB EB WB Monitoring Report (Draft) 44

48 3.2.2 Duration of Congestion and HOV Lane Utilization The duration of congestion and HOV lane utilization are determined from Caltrans PeMS peak hour speed and volume data. One location in the West County that did not meet the standard. The results of monitoring are shown in Table 16 through Table 18. Table 16: HOV Utilization East County Route Dir Peak Hour Observed Max Volume SR vehicles per lane WB AM (7:00-8:00) 1,755 EB PM (5:45-6:54) 1,810 Table 17: Duration of congestion Tri-valley County Route Limits Dir (hour) Observed I 680 SR 84 to County Line SB Table 18: HOV Lane Utilization West County Route Dir Observed Observed Peak Hour Max Volume Max Volume % Change 6:00-7:00 AM 945 1,399 48% EB 5:00-6:00 PM 1,169 1,349 15% I-80 10% 7:30-8:30 AM 1,401 1,430 2% WB 3:00-4:00 PM 1,130 1,511 34% *In the, the HOV lane usage on the I-80 was increase 43% from 2007 to Monitoring Report (Draft) 45