Welcome Cappyitol Hill Traffic Study Open House
Wednesday, June 11th 2014
Purpose of the Study
• Investigate transportation problems related to State Highways in the Capitol Hill Community
• Engage residents and stakeholders to identify and evaluation a range of possible solutions and outcomes
• Outcomes may include projects for UDOT and or Salt Lake City to fund and implement in the future Study Timeline
We are here
Project Start Analysis of Develop Discuss options with 2nd Public – December Public Input Options – Capitol Hill Comm. Open House 2013 ‐ Jan/Feb February Council –May ‐ June
Initial Public Traffic Analysis of options – Formulate Open House Feb‐May short and – January long‐term plans ‐ June Previous Work
We held an Open House in January
We solicited your input on traffic problems
We collected your ideas for solutions
We grouped and ranked solutions
Tonight’s We performed traffic analysis on the top solutions Discussion Traffic Trends
Historic Average Daily Traffic Volume on SR‐186 2012 Average Daily Traffic 25,000 (Values represent vehicles per day)
20,000
15,000 Day
rr
pe Victory Road: 500 North to
Beck Street
10,000 Columbus St: 300 North to 500 North Vehicles
5,000
0 2002 2003 2004 2005 2006 2007 2008 2009 2010 2011 2012 Safety Trends
Where are Crashes Occurring? Crash Diagram for the (Higher bars represent more crashes) Victory Rd/Zane Ave/ Columbus St/ 500 N Area (2008‐2012) Purpose of a State Highway
• Fac ilita te CtiConnections bbtetween Utah communities • State Route 186 (SR‐186) stretches from Parleys Canyon, through downtown and the Capitol Hill area, and up to Beck Street • SR‐186 is part of a larger network of state highways
• Support UDOT’s Four Strategic Goals: • Preserve Infrastructure • Optimize Mobility • Zero Fatalities • Strengthen the Economy
Traffic Performance Measures
1. Total System Delay (hours) 2. Victory Road Corridor Delay (seconds per vehicle) Represents the total vehicle delay Represents the average delay experienced in the area common to experienced by northbound all alternatives. vehicles on the Victory Road corridor during the busiest Measured during the busiest 15 15 minutes of the PM peak hour. minutes of the PM peak hour. Measured in seconds of delay per vehicle
3. Conflict Points Represents the number of conflict points at the 500 North/Columbus Street/Victory Road intersection areas. A conflict point is any point where 2 vehicle movements conflict. Provides an indication of safety conditions ‐ the more conflict points, the more opportunities for collisions
Existing: 103 total conflict points Roundabout at 500 North: 79 total conflict points No Left Turns at Zane: 41 total conflict points
71 conflict points 71 conflict points 9 conflict points
32 conflict points 32 conflict points 8 conflict points Traffic Performance Summary
Total System Victory Road Alternati ve CflitConflict PPitoints Delay Corridor Delay (hours) (seconds/vehicle) Baseline 67.5 150 103
A1 ClColum bus S/St/5 00 N Signa l ‐ 2.9 + 2.1 +/‐ 0 Full Access at Zane Ave, Columbus St A2 Columbus St/500 N Signal ‐ 1.1 + 2.0 ‐62 “Right‐in/right‐out” at Zane Ave, Columbus St A3 Columbus St/500 N Signal ‐ 383.8 + 888.8 ‐71 No Access at Zane Ave, Columbus St B Columbus St/500 N Roundabout + 1.6 + 8.7 ‐24
C 300 N/State St Signal ‐ 4.4 + 14.3 +/‐ 0
D 300 N/State St Roundabout + 2.1 + 24.1 +/‐ 0 300 W/North Temple Widening E + Improve 300 W Timing ‐ 0.9 + 0.8 +/‐ 0 + Move UTA bus stop F Median on Victory Rd + 1.2 + 10.7 ‐20 + One‐way Columbus St north of Zane Ave G Restricted Traffic on Victory Rd + 36.1 ‐ 34.9 +/‐ 0 (HOV/HOT/Odd‐even License Plate Days) HOne‐way Circulation around Capitol + 7.0 ‐ 66.8 ‐19 A1: Columbus St/500 N Signal Full Access at Zane Ave, Columbus St
Description Add a signal to the Columbus Street/500 North intersection to reduce delay from side streets and improve ease of access onto Columbus Street.
Do not restrict access at Zane Avenue, Columbus Street.
Traffic Measures Baseline vs Alternative Notes
Total System Signal reduces wait Delay 67.5 ‐ 2.9 times on 500 North (hours)
Victory Road Signal creates delay Corridor Delay 150 + 2.1 for Victory Road (seconds/vehicle) through traffic
No changes to Conflict Points 103 +/‐ 0 number of conflict points
Other Issues
Access Property Impacts • Traffic signal facilitates access to and from 500 • Likely widening of Columbus Street near 500 North during peak hours North to fit left‐turn lanes • Queuing from the signal may block access to Zane Avenue Neighborhood Cut‐through Traffic • The signal may encourage some traffic to divert from Zane Avenue to 500 North Safety • May reduce collisions for vehicles turning onto Columbus Street from 500 North Miscellaneous • May increase rear‐end collisions for vehicles • May need advance signal warning for traffic coming up the hill on Victory Road. approaching signal southbound on Victory Road A2: Columbus St/500 N Signal Right‐in/Right‐out at Zane Ave, Columbus St
Description Add a signal to the Columbus Street/500 North intersection to reduce delay from side streets and improve ease of access onto Columbus Street.
No left turns to or from Zane Avenue, Columbus Street.
Traffic Measures Baseline vs Alternative Notes
Total System Signal reduces wait Delay 67.5 ‐ 1.1 times on 500 North (hours)
Victory Road Signal creates delay Corridor Delay 150 + 2.0 for Victory Road (seconds/vehicle) through traffic
Significant conflict Conflict Points 103 ‐62 point reduction at Zane Ave
Other Issues
Access Property Impacts • Traffic signal facilitates access to and from 500 • Likely widening of Columbus Street near 500 North during peak hours North to fit left‐turn lanes • Queuing from the signal may block access from Zane Avenue Neighborhood Cut‐through Traffic • The signal may encourage some traffic to divert from Zane Avenue to 500 North Safety • Left‐turn restrictions at Zane Avenue my push • Simplification of conflict points at Zane drivers to use 500 North Avenue may reduce collisions • May reduce collisions for vehicles turning onto Columbus Street from 500 North Miscellaneous • May increase rear‐end collisions for vehicles • May need advance signal warning for traffic coming up the hill on Victory Road approaching signal southbound on Victory Road A3: Columbus St/500 N Signal No Access at Zane Ave, Columbus St
Description Add a signal to the Columbus Street/500 North intersection to reduce delay from side streets and improve ease of access onto Columbus Street.
Close access to or from Zane Avenue, Columbus Street.
Traffic Measures Baseline vs Alternative Notes
Total System Signal reduces wait Delay 67.5 ‐ 3.8 times on 500 North (hours)
Victory Road Signal creates delay Corridor Delay 150 + 8.8 for Victory Road (seconds/vehicle) through traffic
Drastic conflict Conflict Points 103 ‐71 point reduction at Zane Ave
Other Issues
Access Property Impacts • Traffic signal facilitates access to and from 500 • Likely widening of Columbus Street near 500 North during peak hours North to fit left‐turn lanes • Traffic signal will have to serve all access in the immediate area Neighborhood Cut‐through Traffic • Vehicles that used Zane Avenue must reroute to Safety the signal at 500 North • Elimination of all access at Zane Avenue may reduce collisions • May reduce collisions for vehicles turning onto Columbus Street from 500 North Miscellaneous • May increase rear‐end collisions for vehicles • May need advance signal warning for traffic coming up the hill on Victory Road. approaching signal southbound on Victory Road B: Columbus St/500 N Roundabout
Description Install a roundabout at the Columbus Street/500 North intersection to reduce delay from side streets and improve ease of access onto Columbus Street.
Traffic Measures Baseline vs Alternative Notes
Total System Added delay on Victory Road Delay 67.5 + 1.6 outweighs reduced (hours) delay on side streets
Victory Road Roundabout creates Corridor Delay 150 + 8.7 delay for Victory (seconds/vehicle) Road through traffic
Roundabout has fewer conflict points Conflict Points 103 ‐24 than a typical intersection
Other Issues
Access Property Impacts • Roundabout facilitates access to and from 500 • Likely widening to fit roundabout circle North during peak hours only for certain directions • Queuing from the roundabout may block access to Zane Avenue Neighborhood Cut‐through Traffic • The roundabout may encourage some traffic to divert from Zane Avenue to 500 North
Safety • May reduce collisions for vehicles turning onto Miscellaneous Columbus Street from 500 North • May need advance signal warning for traffic • May increase rear‐end collisions for vehicles approaching roundabout southbound on Victory coming up the hill on Victory Road Road C: 300 N/State St Signal
Description Add a signal to the 300 North/State Street intersection to improve ease of access from westbound 300 North
Traffic Measures Baseline vs Alternative Notes
Total System Signal reduces wait times for Delay 67.5 ‐4.4 westbound 300 (hours) North traffic
Victory Road Signal creates delay Corridor Delay 150 + 14.3 for corridor through (seconds/vehicle) traffic
No changes to Conflict Points 103 +/‐0 conflict points at 500 North
Other Issues
Access Property Impacts • Signal facilitates access to State Street from • Signal can fit within existing footprint 300 North • Signal produces long queues on State Street which can block access to side streets Neighborhood Cut‐through Traffic • Queuing on State Street may encourage Safety commuters to utilize Main Street • May reduce collisions for vehicles turning onto Sta te Stree t from 300 NNthorth • Signal produces extensive queuing coming up Miscellaneous the hill on State Street which may lead to • Signal mast arms could encroach on view of increased rear‐end collisions Capitol building coming up State Street D: 300 N/State St Roundabout
Description Add a roundabout to the 300 North/State Street intersection to improve ease of access from westbound 300 North
Traffic Measures Baseline vs Alternative Notes
Total System Added delay on State Street Delay 67.5 + 2.1 outweighs reduced (hours) delay on 300 North
Victory Road Roundabout creates Corridor Delay 150 + 24.1 delay for corridor (seconds/vehicle) through traffic
No changes to Conflict Points 103 +/‐0 conflict points at 500 North
Other Issues
Access Property Impacts • Roundabout facilitates access to State Street • Widening to fit roundabout circle would impact from 300 North Capitol grounds and/or properties to the south • Roundabout produces long queues on State Street which can block access to side streets Neighborhood Cut‐through Traffic • Queuing on State Street may encourage commuters to utilize Main Street Safety • May reduce collis ions for vehic les titurning onto State Street from 300 North Miscellaneous • Roundabout produces extensive queuing • Roundabout likely would need to be sized to coming up the hill on State Street which may accommodate Capitol service and delivery lead to increased rear‐end collisions vehicles E: 300 W/North Temple Widening Improve 300 W Corridor Timing and Relocate UTA Bus Stop
Description Widen intersection to feature dual southbound left‐turn lanes (300 West to North Temple) and dual westbound right‐turn lanes (North Temple to 300 West).
Improve timing on 300 West for north/south flow and move UTA bus stop back from intersection corner
Traffic Measures Baseline vs Alternative Notes
Total System Added lanes result Delay 67.5 ‐0.9 in slight decrease to (hours) system delay
Victory Road Minimal effect on Corridor Delay 150 + 0.8 Victory Road (seconds/vehicle) corridor
No changes to Conflict Points 103 +/‐0 conflict points at 500 North
Other Issues
Access Property Impacts • No changes to Capitol Hill neighborhood • Widening to fit extra lanes may impact adjacent access property
Neighborhood Cut‐through Traffic • No significant impacts anticipated Miscellaneous Safety • Coordination required with UTA to investigate • Dual right‐turn lanes may decrease visibility impacts to transit riders and feasibility of moving for pedestrians crossing 300 West bus stop • Dual right‐turn lanes encroach on existing • Need to consider how to accommodate existing shared bike lane shared bike lane on North Temple F: Landscaped Median on Victory Rd One‐way Columbus Street North of Zane Avenue
Description Add a landscaped median on Victory Road to narrow travel lanes and slow traffic entering the Capitol Hill area
Restrict Columbus Street to one‐way northbound travel north of Zane Ave
Traffic Measures Baseline vs Alternative Notes
Total System Slower speeds on Victory Road results Delay 67.5 + 1.2 in slight increase in (hours) delay
Victory Road Slower speeds and traffic diverted from Corridor Delay 150 + 10.7 Columbus Street (seconds/vehicle) increases delay
Conflict point Conflict Points 103 ‐24 reduction at Zane Ave
Other Issues
Access Property Impacts • Southbound travel from Columbus Street will • No significant impacts to property anticipated have to divert to Zane Avenue or 500 North
Neighborhood Cut‐through Traffic • Southbound Columbus Street traffic will divert through other streets
Safety Miscellaneous • May reduce collisions for vehicles at Zane • Salt Lake City and UDOT would need to agree on Ave/Columbus St/Victory Road maintenance plan for the median G: Restricted Traffic on Victory Rd HOV/HOT/Alternating Odd‐Even License Plate Days
Description Restrict traffic volumes on Victory Road from Zane Avenue to Beck Street through High Occupancy Vehicle (HOV), High Occupancy/Toll (HOT), or alternating odd‐even license plate days
Traffic Measures Baseline vs Alternative Notes Major increase in Total System system delay due to Delay 67.5 + 36.1 increased volumes (hours) on 300 West and North Temple Victory RdRoad Su bstantial decrease in delay on Corridor Delay 150 ‐34.9 Victory Road (seconds/vehicle) corridor
No changes to Conflict Points 103 +/‐0 conflict points at 500 North
Other Issues
Access Property Impacts • Access to Capitol Hill neighborhood from • No significant impacts to property anticipated Victory Road heavily restricted Neighborhood Cut‐through Traffic • Likely significant cut‐through traffic in Capitol Hill neighborhood to avoid Victory Road restrictions
Safety Miscellaneous • Need to ensure corridor checkpoint areas do • Need to work out enforcement and maintenance not create safety hazards issues and policies H: One‐way Circulation Around Capitol
Description Convert the roadways around the Capitol to a one‐way, counter‐clockwise circulation system
Traffic Measures Baseline vs Alternative Notes
Total System Increase in wait times on side Delay 67.5 + 7.0 streets around (hours) Capitol
Victory Road Free movements at intersections Corridor Delay 150 ‐66.8 around Capitol (seconds/vehicle) streamlines flow
Conflict point Conflict Points 103 ‐19 reduction at 500 North
Other Issues
Access Property Impacts • Out‐of‐direction, circuitous travel required to • No significant impacts to property anticipated access side streets and parking lots around Capitol Neighborhood Cut‐through Traffic • Likely significant cut‐through traffic in Capitol Hill neighborhood to avoid out‐of‐direction travel on one‐way roads Safety Miscellaneous • Potential increase in pedestrian/vehicle • Significant lane alignment changes needed at conflicts at East Capitol Boulevard parking area each intersection around Capitol Promising Alternatives
Alternative Issues to Resolve A2: Columbus Street/500 North Signal Advance signal warning and/or way to lower speeds for “Right‐in/right‐out” at Zane Ave, Columbus St southbound traffic on Victory Road Define where to widen road to fit intersection turn lanes
A3: Columbus Street/500 North Signal Advance signal warning and/or way to lower speeds for No access at Zane Ave, Columbus St southbound traffic on Victory Road Define where to widen road to fit intersection turn lanes
F: Median on Victory Road Ensure median does not create a sight distance obstruction + One‐way Columbus Street north of Zane Ave Formulate a maintenance plan agreeable to UDOT and Salt Lake City H: One‐way Circulation around Capitol Develop one‐way reconfigurations for each intersection around the Capitol
Coordinate with Salt Lake City regarding potential bicycle and pedestrian impacts on East Capitol Boulevard
Investigate potential for increased neighborhood cut‐through traffic Next Steps
• Review Comments
• ItIncorporate ffdbkeedback iitnto fina l analliysis
• Look to resolve lingering issues
• Develop final alternatives