The Effect of Transit Signal Priority on Bus Rapid Transit Headway Adherence
BYUgregmacfarlane@byu.edu WCG
michael.sheffield@wcg.us BYU
loganbennett93@gmail.com BYU
gschultz@byu.edu
2021-06-01
Abstract
We report the results of an experiment to evaluate the impact of transit signal priority (TSP) on headway adherence for a bus rapid transit (BRT) system in Provo / Orem, Utah. The bus requests TSP based on its unpublished schedule, but users perceive only a headway. Quantile regression models estimated on raw timepoint data from the BRT system reveal that TSP significantly improves headway adherence, after controlling for peak times, direction, and cumulative trip dwell time. We also find that requiring the bus to be 2 minutes late before requesting TSP improves headway adherence more than allowing all buses to request TSP.
1 Questions
Transit signal priority (TSP) allows traffic signals to flexibly accommodate transit vehicles. This may involve extending a green phase until the vehicle passes, triggering an early green if there is a vehicle waiting at the light, or even running specific transit-only phases. TSP helps transit vehicles maintain on-time performance (Liu et al., 2018; Sheffield et al., 2021), but often TSP will only engage at a signal if the vehicle is running behind its schedule, thus minimizing automobile delay when the bus is otherwise on schedule (Ni et al., 2020).
In 2018, the Utah Transit Authority (UTA) launched the Utah Valley Express (UVX) Bus Rapid Transit (BRT) system in Provo and Orem, Utah. The system — mapped in Figure 1.1 — connects two commuter rail stations, two major universities (Brigham Young and Utah Valley), and commercial districts in Orem and Provo. UVX has TSP on 44 of the 47 traffic signals along its route. A transit vehicle requests TSP when the vehicle is behind its schedule; the signal controller may then grant the TSP based on a set of rules. For example, the signal will not grant TSP to transit vehicles traveling in the same direction in consecutive signal cycles. Specifically, at least two “clean” cycles must run before the signal controller will grant TSP again.
<- wesanderson::wes_palette("Darjeeling1")
dj1 <- st_read("data/uvx_map.geojson", quiet = TRUE)
uvx <- uvx %>% filter(st_is(., "POINT"))
uvx_stops <- uvx %>% filter(st_is(., c("MULTILINESTRING", "LINESTRING")))
uvx_line if(!knitr::is_latex_output()){
leaflet() %>%
addProviderTiles(providers$Esri.WorldGrayCanvas) %>%
addPolylines(data = uvx_line) %>%
addCircleMarkers(data = uvx_stops, label = ~(name))
else {
} <- st_bbox(uvx_line)
pbox <- get_map(c(lon = mean(pbox[c(1, 3)]), lat = mean(pbox[c(2, 4)]) ),
map_back zoom = 13, source = "google", maptype = "roadmap", color = "bw")
ggmap(map_back, extent = "device") +
coord_sf(crs = st_crs(3426), expand = FALSE) +
geom_sf(data = uvx_line, inherit.aes = FALSE, lwd = 1, color = dj1[1]) +
geom_sf(data = uvx_stops, inherit.aes = FALSE, size = 5, stroke = 1, shape = 21,
fill = "white", color = dj1[5]) +
theme(axis.line = element_line(color = NA)) +
xlab("") + ylab("")
}
Though the TSP system is based on a schedule, UTA does not publish a schedule for UVX. Instead it is expected that a bus will arrive on a specific headway: 6 minutes in the peak period and 10 minutes in the off-peak. UVX vehicles depart their initial time point on this schedule, but then proceed to the end of the route without consideration as to whether the vehicle is running ahead or behind its “schedule” as understood by the TSP system. It is unclear whether the actualized headway is affected by a schedule-based TSP system, potentially creating frustration for riders or inefficient operations. The research questions are therefore:
- Does schedule-based TSP improve headway adherence for rapid transit systems?
- What is the effect of other controlling factors — specifically time period, direction of travel, and cumulative stop dwell time — on headway adherence?