Open Thread 14: Rural Transit

Thoughts on car dependency from rural America. (InDefenseOfToucans)

Link remains at 15-minute service with single-tracking at Othello and Rainier Beach stations through September 17.

Phase 2 of the T Line opens September 16. This extends Tacoma Link to what we might call Tacoma’s First Hill.

Page 2 has an article on a Jefferson Street funicular in Seattle’s First Hill.

King County explores redeveloping a 9-block government district downtown. This includes the North of CID Link station alternative.

A step by step guide to improving a city’s transit. (RMTransit video)

Trolleybuses vs battery buses. (City for All video)

Montreal transit and urbanism. (CityNerd video)

Non-transit interlude: Why Shakespeare plays can’t be presented the original way. (J Draper video)

This is an open thread.

217 comments

Sound Transit Board approves Spring 2024 opening for East Link starter line

East Link testing on 112th Ave SE, photo credit the author’s wife

The Sound Transit Board green-lighted the much-anticipated East Link Starter Line (ELSL) earlier today, approving a resolution that authorizes up to $43 million on implementing passenger revenue service in Spring 2024. Previously, the Board had approved $6 million to study the idea of a phased East Link opening, per the urging of King County Councilmember Claudia Balducci.

Earlier in the year, boardmembers representing Snohomish County had expressed concern that opening the ELSL in 2024 might detract from a timely opening for the Lynnwood Link Extension (LLE). However, Sound Transit staff determined no schedule impacts from the ELSL on the LLE, which is on track for a Fall 2024 opening. Nonetheless, Lynnwood Link is expected to operate at lower frequencies until the I-90 connection to the Eastside operations and maintenance facility (OMF) is complete.

With the ELSL’s approval, service levels will be formally laid out in the 2024 Service Plan, which is anticipated for a board vote later in October. In the meantime, initial readiness plans call for a 16 hour service span with constant 10 minute headways across the day using 2-car trains.

The ELSL will also only operate between Redmond Technology Station (serving the Microsoft campus) and South Bellevue Station. Since it does not directly duplicate any existing services, it remains to be seen whether or not Sound Transit will adjust service levels on the 550 or 556 when the starter line opens.

Ridership on the ELSL is forecasted at 6,000 daily boardings. Given the ubiquity of remote work and ample parking along the corridor, I expect ridership to be relatively muted until the I-90 connection is complete and Bel-Red is more fully built out.

Although East Link and the year 2023 have suffered an irreparable divorce, it’s encouraging to see the ELSL come to fruition, thanks to hard work from Sound Transit staff and championing from councilmember Balducci.

178 comments

Open Thread 13: Hope

Hope for American transit: things are getting better. (RMTransit video)

Top 10 US metros with the highest bus ridership per capita. Seattle is #4. (CityNerd video)

Washington congressional delegation asks FTA to fund Cascadia high-speed rail study. ($)

Trolleybuses vs battery buses. (City for All video)

The advantages of green tram tracks; i.e., grass between the rails. (City for All video)

A Taylor Swift fan from Canada vlogs her Seattle light rail weekend. (Keri Pratt video)

This is an open thread.

309 comments

Metro 8: Connections Comprehensive

(Part of a series highlighting high-performing transit routes in the Puget Sound region)

Route 8, King County Metro, in Seattle. North points down and to the right. Illustration using Google Maps.

Metro 8 performs well at all times of the week, with its particular strength being the amount of rides it carries for its level of service. Its total ridership is eighth among Metro routes, with 4,828 rides per weekday, but it does that with fewer platform hours than anything above it on the list, which is the reason it performs so well on rides per platform hour. It places second in that metric among Metro routes on weekdays, carrying 34.7 rides per platform hour during peak periods and 32.3 daytime off-peak. That means a single 8 trip taking 45 minutes provides a ride to an average of 26 people. I was interested in what accounted for its success, so, as I did with RapidRide A, I went looking for answers. I took the light rail to Mt. Baker, where I hopped on the 8 heading north.

Riding the 8 on that weekday afternoon, it was interesting to me how much the 8 felt like two routes in one. The first section, which aligns north-south mainly on MLK Way, runs through the leafy pre-war neighborhoods of the Central District. The trip during this leg was fast and lightly boarded. With the exception of a clutch of people who boarded at the deviation to 23rd Avenue (near the excellent Communion restaurant), the bus was almost empty.

The north-south leg of the 8 runs through the leafy neighborhoods of the Central District. Photo: Google Maps.

The second leg of the route was much busier. This is the section that runs east-west from Madison Valley to Uptown, ending a block from Climate Pledge Arena. Almost immediately after the bus turned west, a large group of people boarded outside an apartment complex. The bus was suddenly busy, and it remained so through the end of my trip, despite big turnovers of people at the major stops. As we passed through Capitol Hill and South Lake Union, people came and went so rapidly that it was hard to keep track. Finally, the bus stopped, and I realized (after everyone else had debarked) that this was the end of the line. I wandered around, bought a sandwich, and looked for a way to get home.  

What makes the 8 successful on its productivity measures? It has the benefit of going through some very dense places of Seattle, plus serving points of interest like Seattle Center. But it is hardly unique in this regard. In fact, its performance (on total ridership, on rides per platform hour) is better than other routes that serve even denser areas, like Routes 2 and 10. Those routes have similar frequencies throughout the day to the 8, so frequency cannot explain it, either. The 8 does avoid deviations, except the one to 23rd Avenue. That counts in its favor, but that alone does not make a route a top performer.

The 8 (in yellow) and the 2 (in orange) both run through areas of high residential density. Both are strong routes, but the 8 has higher daily ridership and rides per platform hour. Map by author.

Judging from how busy that east-west leg was, I would argue that the major, useful connections along its east-west leg account for its success. In less than three miles of travel, it makes connections to Link, RapidRides C, D, and E and the 40 and 48 bus lines. All of those are among King County’s busiest transit lines, and a rider on the 8 can access any corridor that they would like. Because it runs cardinally east-west and makes perpendicular connections with those lines, it is the most direct route to connect them. In this city where so many travel routes run north-south, it makes sense that a route providing a useful connection with all of them would be highly productive. I believe that is what we have here.

There are other ways to conceptualize the 8. It takes an indirect route between Mt. Baker and Uptown, meaning it is not good for end-to-end travel. But it does connect the midpoints of the route to either end, directly. You could think of the 8 as two routes, heading west and south from Madison Valley, that just happen to be through-routed with each other for efficiency’s sake. The 8 also is a part of what Jarrett Walker calls a “spiderweb grid,” playing the role of a circumferential by joining routes radiating from Downtown on two sides. One of the interesting things about the study of transit is there are so many ways to think about how a single line fits into a larger network. When you consider all the possible connections and routes a person could take, the possibilities are almost limitless.

Overall, the 8 suggests the importance of transfers in the success of a transit line. It doesn’t serve downtown. It does not have a clear niche to serve a particular type of travel pattern. Yet because of the way it connects to other routes, it becomes significant and useful enough to count among Metro’s best-performing services. There is a larger lesson to this observation: after all, even though this series is focused on high-performing lines, it ultimately does not matter where a single line can get you, but where the whole transit network can get you – and how quickly. Each individual line is subordinate to its position in a greater network, a greater ecosystem. By making so many quality connections to other routes, the 8 points to the importance of all the other routes that enable it to succeed.

The 8 near its terminus in Uptown. Photo from 2015. Photo: Google Maps.
44 comments

Bus Restructure for Lynnwood Link

I’ve come up with a few suggestions based on the latest proposal for Metro’s network following Lynnwood Link (P3). My goal was to improve the proposal while retaining as much of it as possible. As has been the case in the past, I’ve made a map to make it easier to understand the suggestions:

As with the previous maps, you can make it full page (in its own window) by selecting the little rectangle in the corner. Selecting individual routes highlights them, making them easier to see (with a short explanation as necessary). There are different “layers”, visible on the legend (to the left). For example, you can hide or display the routes that haven’t changed. Feel free to ask questions in the comments if there is any confusion.

I would not expect every suggestion to be implemented. I’ve listed each one in the order of importance, starting with the most important first:

65 and 77

The 65 is back to what was suggested in P2. The 125th/130th corridor is one of the most important in the area. Not only is it the fastest way for someone to get from Lake City to Link, but also the fastest way to get to Aurora and Greenwood Avenue. There are several reasons why making this corridor part of the 65 is better than the proposed 77:

  1. Avoids the awkward turn in Lake City mentioned previously.
  2. More bus stops in Lake City. The stops on the 65 manage to be within walking distance of almost all of the apartments in Lake City. In contrast, the proposed 77 only covers a subset of the area, before heading south on Lake City Way, leaving a significant gap in coverage. For example, this versus this. The 65 would provide a much shorter walk for a lot of people looking for the fastest way to Link (or Bitter Lake, Ingraham High School, Aurora, Greenwood, etc.).
  3. More one-seat connections. Both the P2 version of the 65 and the P3 version of the 77 serve Bitter Lake and Ingraham High. Connecting those areas to Nathan Hale High School, Wedgwood, Children’s Hospital, the U-Village and the east part of the UW adds a lot of value. In contrast, south of Lake City, the main destinations on the 77 are Roosevelt and the UW — areas served by Link. I don’t see too many people sitting through the hairpin set of turns to get from Roosevelt to Bitter Lake — they will simply take Link and transfer. The P3 version of the 77 appears to be two buses awkwardly glued together, whereas the P2 version of the 65 works for a lot more trips.
  4. Good match of frequency. The proposed 65 is not as frequent as the 72, but is still a lot more frequent than the 77 . While I feel that Lake City Way should have good frequency between Northgate Way and Roosevelt, it isn’t as important as the critical 125th/130th corridor. The frequency on the P2 version of the 65 is much better than the P3 version of the 77.

With the 65 being sent to Bitter Lake, the 77 can cover the area between Lake City and the station (30th, 25th, etc.). Northbound, the bus would turn left on 127th, then right on 30th. If 127th turns doesn’t work, then 130th might. Either way, it wouldn’t make a detour, like the proposed 77; there would be fewer turns, with the bus always headed the same basic direction. Going the other way, it is even faster, as it simply stays on 30th until it merges with Lake City Way.

348 Replacing 67

Most of the suggestions here are revenue neutral (or close to it). In this case though, the changes would save service hours. That is why I think it is so important. Most of the routes in the P3 proposal have very poor frequency. This change allows the buses to run more often, with no additional funding. This is critical if we are going to have a good transit system.

This comes with trade-offs, but rather minor ones. Some riders along the 15th NE corridor lose their one-seat ride to Northgate, but they gain a one-seat ride to Roosevelt and the U-District. The route complements buses like the 61 and 75 (which go to Northgate). It is a bit faster to get to Northgate Station instead of Roosevelt Station, but a large portion of the riders heading to Link will take crossing buses to 130th or 145th station anyway (or the 61 to Northgate). For those in between the major cross-streets, this still provides a fairly fast connection to Link (via Roosevelt) while providing a new one-seat connection for everyone along the corridor. The only significant loss is for people along 5th Avenue NE (between Northgate Way and 103rd). They lose their one-seat wrap-around ride to Maple Leaf, Roosevelt and the U-District. The alternative for those riders is to take a different bus and transfer or walk about five minutes and catch the same bus.

This change could be justified without the time savings. With the time savings, I believe it is critical.

72 and 333

This is a relatively minor change that could have very positive benefits. As of right now, Lake City is directly connected to Shoreline Community College (SCC) via the 330. While the bus does not run often, it performs quite well — in the top 25% of routes in rides per platform hour and passenger miles per platform hour, which is striking given its low frequency. This restores that one-seat connection, while providing other benefits.

The current 330 pathway is a faster connection between SCC and Link, while also getting lots of riders along the way. It is also the fastest way to get from Aurora to SCC. Someone from either end of Aurora (transferring via the RapidRide E) could get to the college much faster. Combining this section with the 72 is a better balance of frequencies. The 72 runs often (for good reason). In contrast, the 333 is not slated to run as often, and this looks to be the strongest section. By having the 72 operate this vital section, headways should be better (now, and in the future).

Under the current proposal, riders from the east can stay on the bus as it goes through SCC. My guess is very few would do that though. It simply takes too long for the bus to weave its way so far west, only to have it turn around and weave its way east. Shoreline Community College is a much better terminus.

345 and 365

Extending the 345 to SCC gives it a stronger anchor. The college is the second most popular stop for that line (second only to Northgate Transit Center). About 40% of the people who board at Four Freedoms head west (to get to SCC) not east (to get to the hospital and Northgate). This restores that connection.

With the 365, service is restored to most of Meridian. The section on 5th is basically an add-on (I don’t expect many riders to “round the horn” and take a bus from Meridian to 5th). Overall, the changes to the 345 and 365 would provide better coverage (and probably significantly more ridership) at little additional cost.

U-District Routing

I’ve largely ignored the subject of through-routing in the U-District. This is a tricky subject, with a lot of trade-offs. I don’t have access to the information (such as reliability data) that would allow me to make a more informed decision. In terms of frequency and total travel time, the 77-75 or 45-72 seem like possibilities. I don’t think the 348 could be through-routed with another bus, simply because it is long. Speaking of which, I also accept that there will be service on Roosevelt Way through the U-District, even though I could make a strong argument for consolidating service on The Ave (University Way). I don’t feel as strongly about that issue as I do the suggestions made on the map.

Deadline for comments is August 27. Please let Metro know what you think.

59 comments

Link Month of Reductions

August is the month ot Link maintenance. Service will be reduced for five weeks from August 12th to September 16th to replace sagging tracks over weak soil at Royal Brougham Way, to replace platform tiles at Othello and Rainier Beach, to inspect high-voltage power equipment, to build track ties for East Link near International District, to replace aging rails in the downtown tunnel, and probably other things. This was the best time they could find during the short dry season between major public events, although there will still be a couple ballgames during it. Service levels will be like this:

  • Phase 1: August 12-13: The downtown tunnel is closed. A bus replacement operates between Capitol Hill and SODO Stations. Trains run every 15 minutes (instead of 10). The bus shuttle runs every 10 minutes.
  • Phase 2 & 3: August 14-20: Like the April reduction was. Link is single-tracked between Westlake and Stadium (meaning both directions use the same platform). Trains run every 15 20 minutes. All trains terminate at Pioneer Square, and all passengers transfer to the other platform to continue north or south. This time the transfer isn’t timed, so you could be waiting a long or short time. Royal Brougham Way will be open for pedestrians and bicycles but not cars.
  • Phases 4 & 5: August 21-September 3: Othello and Rainier Beach stations are single-tracked. Trains run every 12 minutes.

Update 8/15/2023: Phase 2 & 3 frequency is now 20 minutes.

Details on phases 1-3 | Seattle Times coverage ($) | Announcement on phases 1-3 | Announcement on phases 4-5 | More details on phases 1-5 (click “Link Light Rail” and read the whole section).

More below the fold.

Continue reading “Link Month of Reductions” | 72 comments

Streamlining I-90 commuter service

Prior to the pandemic, I-90 was a major transit commuting corridor, composed of overlapping Metro and Sound Transit routes with an array of different service patterns. The convergence of these routes at both Eastgate and Mercer Island often meant sub-5 minute headways and crush-loaded buses in the peak.

The post-pandemic landscape is far grimmer: the 212 (formerly the workhorse of Eastgate-Seattle peak service) has been curtailed dramatically with only three buses an hour in the peak, the 214, 216, and 217 are due to be discontinued next month, and the 554 runtime is often bogged down by its routing via Rainier. With sudden trip cancellations fueled by the ongoing driver and mechanic shortage added on top, I-90 transit service is a shell of its former self.

Continue reading “Streamlining I-90 commuter service” | 105 comments

Transportation Events August 2023

Meetings

Sound Transit:

There was a Citizens Accessibility Committee Meeting on August 1 (details), and on August 3, a public hearing on the 2023-2028 Transit Development Plan (details), an Executive Committee Meeting (details), and a Rider Experience & Operations Committee Meeting (details).

Community Oversight Panel Meeting: Wednesday, August 9, 5:30pm – 8:15pm. details

System Expansion Committee Meeting: Thursday, August 10, 1:30pm – 5:00pm. details

Board of Directors Meeting: Thursday, August 24, 1:30pm – 4:00pm. details

King County Metro:

Transit Advisory Commission Meeting: Tuesday, August 15, 6:00pm – 8:00pm. details

Regional Transit Committee Meeting: Wednesday, August 16, 3:00pm. details

Continue reading “Transportation Events August 2023” | 36 comments

Pierce Transit Trying to Salvage BRT Project

On July 10, the Pierce Transit Board of Commissioners gathered to examine a new plan for the Pacific Avenue Bus Rapid Transit (BRT) project, which would build the first line in Pierce County’s “Stream” BRT network. The hope was that this would be a workable solution to the financial problems that have been growing for the project. However, the transit benefit has been watered down in the new plan, and financial risks remain. Because of these problems, the project’s future looks uncertain.

The Pacific Avenue BRT project was initiated with funding from the Sound Transit 3 ballot measure. The project planned to add a BRT line, named the “Community Line,” on Pacific Ave (SR 7), with exclusive right-of-way, wider stop spacing, advance fare payment, level boarding, and other amenities. It would run with 10-minute frequency from Downtown Tacoma to Spanaway, with a deviation to serve Tacoma Dome Station.

The original Community Line BRT plan included 3.3 miles of exclusive right-of-way on Pacific Avenue (SR 7), through Tacoma, Parkland, and Spanaway in Pierce County.

However, the cost of the project expanded due to COVID-related delays, inflation, and planning mistakes. The initial concept planned for 3.3 miles of bus lanes and business-access-and-transit (BAT) lanes to be added to Pacific Avenue without reducing general-purpose lanes. But new lanes and stations turned out to require unplanned road widening, which would add major costs for buying neighboring land. Converting general-purpose lanes to bus lanes to avoid these costs never seemed to be on the table. By early 2023, the project estimate had increased to $311 million, a total that exceeded the available budget by over $100 million.

Continue reading “Pierce Transit Trying to Salvage BRT Project” | 26 comments