23
Welcome Welcome Ca p itol Hill Traffic Stud y Open House Wednesday, June 11 th 2014
WelcomeWelcomeCapitolHillTrafficStudyp yOpenHouseWednesday, June 11th 2014
Purpose of the StudyPurposeoftheStudy
• 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 TimelineStudyTimelineWe are here
Project Start – December
2013
Analysis of Public Input ‐ Jan/Feb
Develop Options –February
Discuss options with Capitol Hill Comm. Council – May
2nd Public Open House
‐ June
Initial Public Open House – January
Traffic Analysis of options –Feb‐May
Formulate short and long‐term plans ‐ June
PreviousWorkPreviousWorkWe 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 Discussion We performed traffic analysis on the top solutions
Traffic TrendsTrafficTrends2012 Average Daily Traffic(Values represent vehicles per day)25 000
Historic Average Daily Traffic Volume on SR‐186
(Values represent vehicles per day)
15,000
20,000
25,000
r Day
5,000
10,000
Vehicles per
Victory Road: 500 North to Beck Street
Columbus St: 300 North to 500 North
020122011201020092008200720062005200420032002
Safety TrendsSafetyTrendsWhere are Crashes Occurring?(Higher bars represent more crashes)
Crash Diagram for the Victory Rd/Zane Ave/ (Higher bars represent more crashes) y / /
Columbus St/ 500 N Area(2008‐2012)
Purpose of a State HighwayPurposeofaStateHighwayF ilit t C ti b t Ut h• Facilitate Connections between 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 EconomyStrengthen the Economy
Traffic PerformanceMeasuresTrafficPerformanceMeasures1. Total System Delay (hours)Represents the total vehicle delay
2. Victory Road Corridor Delay (seconds per vehicle)Represents the average delay
experienced in the area common to all alternatives.
Measured during the busiest 15 minutes of the PM peak hour.
experienced by northbound vehicles on the Victory Road corridor during the busiest 15 minutes of the PM peak hour.
Measured in seconds of delayMeasured in seconds of delayper vehicle
3. Conflict PointsRepresents 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 8 conflict points 32 conflict pointsp 8 conflict points
Traffic Performance SummaryTrafficPerformanceSummaryAlt ti Total System Victory Road C fli t P i tAlternative y
Delay(hours)
yCorridor Delay
(seconds/vehicle)
Conflict Points
Baseline 67.5 150 103C l b S / 00 Si lA1 Columbus St/500 N SignalFull Access at Zane Ave, Columbus St ‐ 2.9 + 2.1 +/‐ 0
A2 Columbus St/500 N Signal“Right‐in/right‐out” at Zane Ave, Columbus St ‐ 1.1 + 2.0 ‐62
A3 Columbus St/500 N Signal 3 8 + 8 8 71A3 gNo Access at Zane Ave, Columbus St ‐ 3.8 + 8.8 ‐71
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
E300 W/North Temple Widening+ Improve 300 W Timing ‐ 0.9 + 0.8 +/‐ 0+ Move UTA bus stop
F Median on Victory Rd+ One‐way Columbus St north of Zane Ave + 1.2 + 10.7 ‐20
G Restricted Traffic on Victory Rd(HOV/HOT/Odd‐even License Plate Days) + 36.1 ‐ 34.9 +/‐ 0
H One‐way Circulation around Capitol + 7.0 ‐ 66.8 ‐19
A1:ColumbusSt/500NSignalFullAccessatZaneAve,ColumbusSt
DescriptionAdd 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.
Baseline vs Alternative Notes
Total System Delay(hours)
67.5 ‐ 2.9 Signal reduces wait times on 500 North
Victory Road
Traffic Measures
Victory Road Corridor Delay(seconds/vehicle)
150 + 2.1Signal creates delay
for Victory Road through traffic
Conflict Points 103 +/‐ 0No changes to
number of conflict points
Property Impacts• Likely widening of Columbus Street near 500 North to fit left turn lanes
Access• Traffic signal facilitates access to and from 500 North during peak hours
Other Issues
North to fit left‐turn lanesNorth during peak hours• Queuing from the signal may block access to Zane Avenue
Safety
Neighborhood Cut‐through Traffic• The signal may encourage some traffic to divert from Zane Avenue to 500 North
• May reduce collisions for vehicles turning onto Columbus Street from 500 North
• May increase rear‐end collisions for vehicles coming up the hill on Victory Road.
Miscellaneous• May need advance signal warning for traffic approaching signal southbound on Victory Road
A2:ColumbusSt/500NSignalRight‐in/Right‐outatZaneAve,ColumbusSt
DescriptionAdd 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.
Baseline vs Alternative Notes
Total System Delay(hours)
67.5 ‐ 1.1 Signal reduces wait times on 500 North
Victory Road
Traffic Measures
Victory Road Corridor Delay(seconds/vehicle)
150 + 2.0Signal creates delay
for Victory Road through traffic
Conflict Points 103 ‐62Significant conflict point reduction at
Zane Ave
Property Impacts• Likely widening of Columbus Street near 500 North to fit left turn lanes
Access• Traffic signal facilitates access to and from 500 North during peak hours
Other Issues
North to fit left‐turn lanesNorth during peak hours• Queuing from the signal may block access from Zane Avenue
Safety• Simplification of conflict points at Zane
Neighborhood Cut‐through Traffic• The signal may encourage some traffic to divert from Zane Avenue to 500 North
• Left‐turn restrictions at Zane Avenue my push drivers to use 500 Northp p
Avenue may reduce collisions• May reduce collisions for vehicles turning onto Columbus Street from 500 North
• May increase rear‐end collisions for vehicles coming up the hill on Victory Road
Miscellaneous• May need advance signal warning for traffic approaching signal southbound on Victory Road
A3:ColumbusSt/500NSignalNoAccessatZaneAve,ColumbusSt
DescriptionAdd 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.
Baseline vs Alternative Notes
Total System Delay(hours)
67.5 ‐ 3.8 Signal reduces wait times on 500 North
Victory Road
Traffic Measures
Victory Road Corridor Delay(seconds/vehicle)
150 + 8.8Signal creates delay
for Victory Road through traffic
Conflict Points 103 ‐71Drastic conflict
point reduction at Zane Ave
Property Impacts• Likely widening of Columbus Street near 500 North to fit left turn lanes
Access• Traffic signal facilitates access to and from 500 North during peak hours
Other Issues
North to fit left‐turn lanesNorth during peak hours• Traffic signal will have to serve all access in the immediate area
Safety• Elimination of all access at Zane Avenue may
Neighborhood Cut‐through Traffic• Vehicles that used Zane Avenue must reroute to the signal at 500 North
yreduce collisions
• May reduce collisions for vehicles turning onto Columbus Street from 500 North
• May increase rear‐end collisions for vehicles coming up the hill on Victory Road.
Miscellaneous• May need advance signal warning for traffic approaching signal southbound on Victory Road
B:ColumbusSt/500NRoundaboutDescriptionInstall a roundabout at the Columbus Street/500 North intersection to reduce delay from side streets and improve ease of access onto Columbus Street.
Baseline vs Alternative Notes
Total System Delay(hours)
67.5 + 1.6Added delay on
Victory Road outweighs reduced
delay on side streets
Victory Road
Traffic Measures
Victory Road Corridor Delay(seconds/vehicle)
150 + 8.7Roundabout creates
delay for Victory Road through traffic
Conflict Points 103 ‐24Roundabout has
fewer conflict points than a typicalintersection
Property Impacts• Likely widening to fit roundabout circle
Access• Roundabout facilitates access to and from 500 North during peak hours only for certain
Other Issues
North during peak hours only for certain directions
• Queuing from the roundabout may block access to Zane Avenue
Safety
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 Columbus Street from 500 North
• May increase rear‐end collisions for vehicles coming up the hill on Victory Road
Miscellaneous• May need advance signal warning for traffic approaching roundabout southbound on Victory Road
C:300N/StateStSignalDescriptionAdd a signal to the 300 North/State Street intersection to improve ease of access from westbound 300 North
Baseline vs Alternative Notes
Total System Delay(hours)
67.5 ‐4.4Signal reduces wait
times for westbound 300
North traffic
Victory Road
Traffic Measures
Victory Road Corridor Delay(seconds/vehicle)
150 + 14.3Signal creates delay for corridor through
traffic
Conflict Points 103 +/‐0No changes to
conflict points at 500 North
Property Impacts• Signal can fit within existing footprint
Access• Signal facilitates access to State Street from 300 North
Other Issues
300 North• Signal produces long queues on State Street which can block access to side streets
Safety• May reduce collisions for vehicles turning onto St t St t f 300 N th
Neighborhood Cut‐through Traffic• Queuing on State Street may encourage commuters to utilize Main Street
State Street from 300 North• Signal produces extensive queuing coming up the hill on State Street which may lead to increased rear‐end collisions
Miscellaneous• Signal mast arms could encroach on view of Capitol building coming up State Street
D:300N/StateStRoundaboutDescriptionAdd a roundabout to the 300 North/State Street intersection to improve ease of access from westbound 300 North
Baseline vs Alternative Notes
Total System Delay(hours)
67.5 + 2.1Added delay on
State Street outweighs reduced delay on 300 North
Victory Road
Traffic Measures
Victory Road Corridor Delay(seconds/vehicle)
150 + 24.1Roundabout creates
delay for corridor through traffic
Conflict Points 103 +/‐0No changes to
conflict points at 500 North
Property Impacts• Widening to fit roundabout circle would impact Capitol grounds and/or properties to the south
Access• Roundabout facilitates access to State Street from 300 North
Other Issues
Capitol grounds and/or properties to the southfrom 300 North• Roundabout produces long queues on State Street which can block access to side streets
SafetyM d lli i f hi l t i t
Neighborhood Cut‐through Traffic• Queuing on State Street may encourage commuters to utilize Main Street
• May reduce collisions for vehicles turning onto State Street from 300 North
• Roundabout produces extensive queuing coming up the hill on State Street which may lead to increased rear‐end collisions
Miscellaneous• Roundabout likely would need to be sized to accommodate Capitol service and delivery vehicles
E:300W/NorthTempleWideningImprove300WCorridorTimingandRelocateUTABusStop
DescriptionWiden 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
Baseline vs Alternative Notes
Total System Delay(hours)
67.5 ‐0.9Added lanes result
in slight decrease to system delay
Victory Road
Traffic Measures
Victory Road Corridor Delay(seconds/vehicle)
150 + 0.8Minimal effect on
Victory Road corridor
Conflict Points 103 +/‐0No changes to
conflict points at 500 North
Property Impacts• Widening to fit extra lanes may impact adjacent property
Access• No changes to Capitol Hill neighborhood access
Other Issues
propertyaccess
Safety• Dual right turn lanes may decrease visibility
Neighborhood Cut‐through Traffic• No significant impacts anticipated
Miscellaneous• Coordination required with UTA to investigate impacts to transit riders and feasibility of moving• Dual right‐turn lanes may decrease visibility
for pedestrians crossing 300 West• Dual right‐turn lanes encroach on existing shared bike lane
impacts to transit riders and feasibility of moving bus stop
• Need to consider how to accommodate existing shared bike lane on North Temple
F:LandscapedMedianonVictoryRdOne‐wayColumbusStreetNorthofZaneAvenue
DescriptionAdd 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
Baseline vs Alternative Notes
Total System Delay(hours)
67.5 + 1.2Slower speeds on
Victory Road results in slight increase in
delay
Victory Road Slower speeds and
Traffic Measures
Victory Road Corridor Delay(seconds/vehicle)
150 + 10.7Slower speeds and
traffic diverted from Columbus Street increases delay
Conflict Points 103 ‐24Conflict point
reduction at ZaneAve
Property Impacts• No significant impacts to property anticipated
Access• Southbound travel from Columbus Street will have to divert to Zane Avenue or 500 North
Other Issues
have to divert to Zane Avenue or 500 North
Safety• May reduce collisions for vehicles at Zane
Neighborhood Cut‐through Traffic• Southbound Columbus Street traffic will divert through other streets
Miscellaneous• Salt Lake City and UDOT would need to agree on• May reduce collisions for vehicles at Zane
Ave/Columbus St/Victory Road• Salt Lake City and UDOT would need to agree on maintenance plan for the median
G:RestrictedTrafficonVictoryRdHOV/HOT/AlternatingOdd‐EvenLicensePlateDays
DescriptionRestrict 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
Baseline vs Alternative Notes
Total System Delay(hours)
67.5 + 36.1
Major increase in system delay due to increased volumes on 300 West and
North Temple
Vi R d S bstantial
Traffic Measures
Victory Road Corridor Delay(seconds/vehicle)
150 ‐34.9Substantial
decrease in delay on Victory Road
corridor
Conflict Points 103 +/‐0No changes to
conflict points at 500 North
Property Impacts• No significant impacts to property anticipated
Access• Access to Capitol Hill neighborhood from Victory Road heavily restricted
Other Issues
Victory Road heavily restricted
Safety• Need to ensure corridor checkpoint areas do
Neighborhood Cut‐through Traffic• Likely significant cut‐through traffic in Capitol Hill neighborhood to avoid Victory Road restrictions
Miscellaneous• Need to work out enforcement and maintenance• Need to ensure corridor checkpoint areas do
not create safety hazards• Need to work out enforcement and maintenance issues and policies
H:One‐wayCirculationAroundCapitolDescriptionConvert the roadways around the Capitol to a one‐way, counter‐clockwise circulation system
Baseline vs Alternative Notes
Total System Delay(hours)
67.5 + 7.0Increase in wait times on side
streets around Capitol
Victory Road Free movements at
Traffic Measures
Victory Road Corridor Delay(seconds/vehicle)
150 ‐66.8Free movements at
intersections around Capitol
streamlines flow
Conflict Points 103 ‐19Conflict point
reduction at 500 North
Property Impacts• No significant impacts to property anticipated
Access• Out‐of‐direction, circuitous travel required to access side streets and parking lots around
Other Issues
access side streets and parking lots around Capitol
Safety• Potential increase in pedestrian/vehicle
Neighborhood Cut‐through Traffic• Likely significant cut‐through traffic in Capitol Hill neighborhood to avoid out‐of‐direction travel on one‐way roads
Miscellaneous• Significant lane alignment changes needed at• Potential increase in pedestrian/vehicle
conflicts at East Capitol Boulevard parking area• Significant lane alignment changes needed at each intersection around Capitol
Promising AlternativesPromisingAlternativesAlternative Issues to ResolveA2: Columbus Street/500 North Signal“Right‐in/right‐out” at Zane Ave, Columbus St
Advance signal warning and/or way to lower speeds for southbound traffic on Victory Road
Define where to widen road to fit intersection turn lanes
A3: Columbus Street/500 North SignalNo access at Zane Ave, Columbus St
Advance signal warning and/or way to lower speeds for southbound traffic on Victory Road
Define where to widen road to fit intersection turn lanes
F: Median on Victory Road+ One‐way Columbus Street north of Zane Ave
Ensure median does not create a sight distance obstruction
Formulate a maintenance plan agreeable to UDOT and SaltFormulate 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 andCoordinate with Salt Lake City regarding potential bicycle and pedestrian impacts on East Capitol Boulevard
Investigate potential for increased neighborhood cut‐through traffic
Next StepsNextSteps• Review Comments
I t f db k i t fi l l i• Incorporate feedback into final analysis
• Look to resolve lingering issues• Look to resolve lingering issues
• Develop final alternativesDevelop final alternatives
