Reminder: Buses replace Link trains between Westlake and Northgate after ~10pm from Oct. 6-8 as part of Sound Transit’s rotating monthly maintenance program.
News and commentary from the past week.
News:
- Puget Sound ferry service returns after 23 ferry engine room workers staged a “sick out” amid tensions over low wages and long hours (KUOW). Also well-covered by The Stranger.
- Zahilay Proposes Advancing RapidRide R Funding to Spur Bus Upgrades (The Urbanist).
- Deadline Approaches for Outside Ideas to Curb Costs on Ballard Light Rail (The Urbanist).
- The push to Reconnect Fremont across Aurora (Fremont Neighbor).
- Paid Parking Could Expand to West Seattle, Upper Queen Anne (The Urbanist). Also on West Seattle Blog and the SDOT Blog.
- Nathan Vass’ Deciding to See is a Finalist for the Washington State Book Awards (The Urbanist).
- New Night Bus routes offer regional connections 24/7 (The Platform)
- KCRHA Consultant Finds the “Missing” $8 Million; Strauss’ RV Ban Moves Forward (PubliCola).
- The Seattle area’s most extreme bedroom communities (The Seattle Times, $; free via SPL)
- King County Metro apprenticeships offer a chance to shift gears (The Seattle Times, $; free via SPL)
- WSDOT’s Cascadia Program exploring regional high-speed rail in coordination with statewide I-5 needs (WSDOT Blog).
Commentary:
- Editorial: Sound Transit CEO Constantine’s contract, bonus show disconnect (The Seattle Times, $; free via SPL). Erica C. Barnett noted the Times’ disapproval of this bonus but tacit approval of SPD’s significantly larger bonuses for senior officers despite SPD’s difficulties.
- Greater Seattle: Bike and Scooter Share Could Soon Lap 2025’s Record-Setting Numbers (PubliCola).
- Trailhead Indirect: Discovery Park (City Hikes)
- What Are the Big Issues Facing Small Businesses? (South Seattle Emerald).
- Op-Ed: Seattle’s Utility Fee Policy Echoes Redlining (The Urbanist).
This is an Open Thread.

My thoughts on Cascadia HSR: as long as the state is considering the ridiculous speed range of 160 to 250 mph with a straight face, nothing will ever get built. Globally, 250 kph is the normal threshold on new lines. That’s about 160 mph. 250 mph (400 kph) would be the fastest train in the entire world. I’m not sure that train manufacturers even build rolling stock capable of those speeds. We should plan for 250 to 300 kph maximum (that’s 160 to 187 mph). There’s only one operational high speed line outside of China (which has many 350 kph lines) and France (which has many 320 kph lines).
Within the context of the I5 corridor, staying within the I5 ROW will probably save hundreds of billions of dollars and will yield a train that is an enormous improvement over the current status quo. Even with sub-optimal station locations in a freeway right of way as needed, a “measly” 250 kph (150 mph) HSR line would be well over twice as fast as the existing train. That’s Seattle to Portland in 90 minutes! Surely we can all agree that’s a large enough improvement to be worth a very large (but not astronomical) sum.
The fact that WSDOT is seriously considering a 400 kph (250 mph) line with hourly service is a cruel joke. It flies in the face of hundreds of years of railway operations best practices (minimizing capital expenditures and maximizing train movements). It just does not make sense. I know for a fact that the WSDOT rail division has many thoughtful, practical, and pragmatic people working in it. Maybe this is all a result of trying to look good for FRA Corridor ID HSR planning. But it’d be nice if we had the ambition to have “good enough” rail service in an international context rather than “best in class”. T
I get your point but they make trains that go that fast. Not many, but a few. But I agree. The perfect is the enemy of the good. We will keep pursuing bullet trains on a corridor that doesn’t justify it. As a result, we delay the work that could (and should) be done to provide speed and service levels that are much better than driving or flying.
It reminds of The Spine. It is quite likely that without agencies pursuing a train from Tacoma to Everett we would have HOV-3 lanes on I-5 along those corridors. It is not completely analogous since a bus could be faster for some trips than Link will ever be (even if The Spine is complete). Getting from Downtown Tacoma to Seattle would be considerably faster (and avoid a transfer). Tacoma Dome Link will instead speed up trips between places like Fife and Star Lake.
Yes, but I still don’t see how WSDOT can say “250 mph” with a straight face when there aren’t even any services planned to go that fast. Just say 125 to 200 mph – that’s the actual range that HSR exists in currently.
And yes, this is a clear “perfect is the enemy of good”. Good would be a new corridor good enough for consistent 125 to 175 mph operations. We could even stretch to 200 mph in stretches. But the Cascadia HSR is just not realistic at this stage and it really does make me sad.
Of course it isn’t realistic to have bullet trains from Portland or Vancouver to Seattle. But if you are going to have bullet trains (which would likely take decades) then top speeds between 160 to 250 mph are possible. But again, that’s not the problem. The problem is that they are too focused on trying to replicate the Shinkansen instead of just making the more conventional trains a lot faster. Look at page 44 here (https://www.aawa.us/site/assets/files/7322/2006_washington_state_long-range_plan_for_amtrak_cascades.pdf). If we had followed that plan we would take 2:30 to get to Portland and 2:37 to get to Vancouver. All of this is without the major changes that California is trying to build (where the trains will hit a top speed of 350 km). It makes sense for California. San Fransisco to L. A. is far enough — and the cities are big enough — that running that fast (or even faster as technology slowly gets better) — is very important. But it just doesn’t make sense for the Pacific Northwest. Seattle and Portland aren’t that far apart. Seattle and Vancouver are even closer. None of the cities are big enough to justify that kind of investment, either.
Keep in mind, they seriously maglev for this. Maglev! For Seattle to Portland. Could maglev could get you those kind of speeds? Definitely. Would it be worth it? Of course not.
One thing to look for is whether somebody confused kilometers with miles and quoted the wrong speed, and it got published in other media without anybody noticing. 250 mph and 250 km/h is suspicious, as was 125 mph and 125 km/h earler.
High speed rail would be really cool, but I doubt it would be worth the price tag, especially at this juncture. I’ve heard an estimate in the ~$100 billion range, with many sections at slower speeds due to tight corners and challenging geography. We’re already having trouble with cost increases on other projects like the I-5 bridge to Portland and ST3, we should focus on overcoming those first.
At $100B, it’s probably not worth building. But surely an alignment that makes speed compromises to maximize the portion of the alignment spent in publicly owned rights of way (i.e., I5) and planned in conjunction with I5 works would come out under that. Particularly if WSDOT allowed for shrinking space dedicated to cars (I can dream on this okay). Maybe it’d still be 2 hours to Portland, but the downstream impacts would be significant.
In addition to intercity services being a whole lot better, it’d also mean we could stand up actually good regional rail in the major cities. Even something like a Sounder-equivalent running hourly between Olympia and Seattle making all local stops would be a game-changer compared to the 3 transfer slog that exists now. Granted, this could be remedied by a better bus connection, but freeway running buses making stops is always a longer time delay than a train making a stop. And in the Portland area, it’s hard to state how much better a 10 minute train to Vancouver would be than the proposed 45 minute MAX slog (even if I’m broadly pro-MAX on the Interstate Bridge).
MAX Yellow Line is scheduled at 26 minutes from Union Station to Expo Center. It’s a half mile onward to a Hayden Island Station and another mile and a half to Waterfront Station (at most), so two more miles at 25 is five minutes. Add a minute for the Hayden Island stop and you’re at a total of thirty-two minutes, not a “45 minute MAX slog”.
Now, if you mean from Pioneer Courthouse Square, yes, it stretches to almost that, especially with the typical long delay at Union Station waiting for a slot on the Steel Bridge. But rail service won’t take a rider to PCS, nor can one board a regional train at Waterfront Station; Vancouver’s depot is two-thirds of a mile west of the active center of the city. though fairly convenient to the Waterfront District via the Grant Street underpass and Seventh Street.
Tom,
I wasn’t being literal in my description of MAX travel times. My point is that regional rail (via a new I5 alignment) would be much faster as a Portland – Vancouver link. Running in the vicinity of I5 would also relieve Vancouver of its poorly located station.
blumdrew, “Regional Rail” won’t run “down the I-5 right-of-way” through North Portland and Vancouver. That’s a certainty. There’s insufficient width through North Portland and wide and fairly deep crossings of two creeks in Vancouver. And a steeeeep grade up from the Lewis River to Ilani.
Maybe it could follow I-205 which is flatter, but I don’t know how you’d get to downtown Portland from there. The Banfield is already squeezed between UP/MAX and the hospital. I guess you could use the UP track since they send almost all their freights via the original line along Marine Drive nowadays. But the median of I-205 is already taken for MAX for a couple of miles south of the airport. And using the UP means backing in or out of Portland Union Station for “through” trains that orginate or terminate in Eugene.
You still have that grade south of the Lewis River with I-205. No, there will never be “regional rail” on an all-new right-of-way between Portland and Seattle. I’m sorry; the topography just doesn’t support it. NP got there first.
Tom,
This is in the context of an I5 corridor plan when WSDOT is actively “pursuing” high speed rail. The literal I5 corridor is simply my assumption of the cheapest option, provided flexibility with number of car lanes is considered. The point is that a high speed line should be built as cost effectively as possible, and I would assume saving billions on right of way would give I5 a leg up. The specifics of where stations may or may not go isn’t the point; it’s that if the state thinks HSR is a good idea (which it does), they should also plan for local trains on the same line (because we have a dearth of publicly owned rail lines suitable for pax service)
NO! “The State” meaning the Democratic party machine thinks spending money is a good idea. And, guess what… it works! They keep a firm grip on power. Remember, the rail division of WSDOT was gutted the last time revenue (i.e. taxes) fell short of what they wanted to spend. It was never restored. Regardless of High Speed Rail that means freight operations have suffered. Sure improving freight operations benefits UP and BNSF but it also make the State more competitive with other west coast ports, helps reduce pollution AND has a major knockoff benefit for passenger rail. Follow the money, there is no real interest in rail, period/exclamation point from the legislature which is who determines where the money is squandered.
I think it is hard to say whether it’s worth building or not. Many bizarre innovations take some kind of vision to makes sense of it.
I think the problem is how to get that kind of money and stay on budget and time to deliver it.
Maybe WSDOT has the vision we don’t have or maybe it is stupid.
“Democratic party machine thinks spending money is a good idea.”
Because that’s literally how civics work. You spend and invest on infrastructure projects to improve your residents lives and expand the economic value of a region. Blaming the democrats on wanting to invest in the state’s future is honestly missing the forest for the trees.
The obsession with austerity for the sake of it is why we are behind peer countries with extensive rail systems. The Shinkansen project was over budget when it opened, but you do hear any Japanese person complain about the inital cost anymore, no. It’s just a footnote in Japan’s rail history now.
This is why I don’t care for the people complaining about the cost of infrastructure, things just cost a lot. Now do I think we should be trying to bring down costs, definitely. RATP was able to build an extension of Line 14 in Paris to Saint-Denis for around $250mil/km, but they only got there after spending a generation investing into building an in house engineering and design department that also has standardized a bunch of things in the construction and permit process. This isn’t something that can be built quickly overnight, this is a 20-30 year process to get there and a political will to step on the toes of a bunch of different stakeholders to make necessary changes.
“The State” meaning the Democratic party machine thinks spending money is a good idea. And, guess what… it works! They keep a firm grip on power.”
“Because that’s literally how civics work… The obsession with austerity for the sake of it”
I almost made the same complaint but I figured Bernie knows the money goes to services because we’ve talked about it enough. The problem with austerity as an absolute value is it pretends the spending is in a vacuum and the money just disappears rather than going to things. But we’ve called Bernie out on that enough. The reason the public is fine with the spending is they want the government to provide a robust set of services — things every state should provide. So the politicians who spend are literally doing the job they were elected to. That’s why they get reelected. That may be Bernie’s point, even if he words it in a confusing and provocative way.
The fiscal problem is that the federal tax policies were changed in the 1970s to funnel money to the to 1%, so the government has been starved of resources to provide the full range of services it should. The state government has tied itself in knots due to Eyman initiatives, and that affects counties and cities too.
Finland and the Scandinavian countries have the best-run governments, and New Zealand is first for citizens approving of their government’s direction, and that’s because those governments provide the services that are needed, have a low rate of public corruption (that siphons off money), and there’s a high rate of trust between individuals. In other words, they don’t follow austerity for some ideological reason. They’re pragmatic and do what’s needed. So Washington state needs to be more like that.
The Amtrak Cascades long-range plan did a comparative cost/benefit study of various speeds. It found that every level up costs exponentionally more in track quality, train quality, power consumption, and looser curves/grades.
Cascades’ current speed limit is 79 mph. The next levels up are 90, 110, 125, and on from there. The sweet spot for Cascades is 110 mph. This could be achieved in two phases, going up to 90, then 110. This would lead to a 90-minute travel time to Portland (or better). This is perfectly acceptable for a trip a few times a week or year. We don’t need to support daily commuters from Portland to Seattle demanding a 30-minute travel time. If they want 30 minutes, they can live in Everett or Tacoma. Levels above that speed have diminishing returns on a cost/performance ratio.
The state HSR boosters and corporate partners (e.g., Microsoft) are shooting for the moon rather than giving the best adequate transit. Focus on getting Cascades up to 90 or 110, and frequency up to hourly or every 15 minutes. That’s all we need. We can talk again once we have comprehensive regional and local transit in all cities both large and small.
Mike, 110 wouldn’t get you a reliable 90 minutes between Portland and Seattle, unless you skipped all the intermediate stations except Tacoma. And even then you’d be hard-pressed to get below 110 minutes or so (1:50). You can’t run any faster through the stretch from Lakewood to Freighthouse Square than trains go now. There are too many grade-crossings and most really can’t be overpassed; South Tacoma Way is too close. Unless Napavine Hill gets a third track on a completely different alignment, the passenger track won’t have a wider curve at the top of the grade; Napavine is right there limiting options to avoid the sharp curve. There are also several more tight curves south of Woodland that are dictated by topography and can’t be straightened significantly. So the average speed is going to be eighty-ish even with 110 top speeds.
You certainly can’t go blasting through the strip of little towns from Tenino to Vader at 110, especially Chehalis, because too many pedestrians would be killed. Brightline has shown that people simply do not understand HOW QUICKLY a passenger train running at that speed arrives at a crossing.
And it’s only going to be one track that supports the higher speeds, not all three. So when there’s a meet between two passenger trains, for the distance that it runs on the shared tracks between cross-overs the inferior train will be traveling at 79. That has to be built into the schedule. Even though BNSF is “two-main track” they tend to run right-hand directionally, so that means that in most meets the train the DS will move to the freight track will be the northbound so that it slots into the northbound flow.
[I’m assuming that in most places the new track would be on the east side of the right-of-way because that’s the side from which The Bypass approaches at Nisqually Junction. Most pictures of grade crossings south of there on Google Maps show more room on that side. But, if the west side is chosen for the new track, the DS would be moving the southbounds over. In any case, the new track should not cross the existing ones unless in the most extreme circustances. Pick a side at the beginning of the project and stay there. The station in Centralia might have to be modified in some way to accommodate an east-side track, perhaps with an underpass.]
Anyway, being right at two hours would be good enough for most people, I think, especially since both Seattle and Portland have excellent “last mile” transit that interfaces directly with the regional service.
I don’t think getting existing ROW upgraded 110 mph will be a game changer. It will just be 110 mph top speed 5% of the time and then slowly getting worse after its open year. Because this track is shared with heavy freight rail which does more damage to track when it pulls the brake, it won’t live to the design speed for long.
If state is not ready to dump tons of money into a new true HSR corridor, they should just fund more Amtrak Cascades trips. Improving an existing corridor that is also heavily used by freight rail is not a good investment.
I’d argue that it is ok that Amtrak Cascades is as slow as it is today as long as it is on schedule. Train travel time between Portland and Seattle is still competitive unless you assume there is no traffic at I-5. The problem is always that often time people don’t just go from Downtown Seattle to Downtown Portland, which is a problem faster true HSR won’t solve neither.
HZ, the State would own the third track, and BNSF’s dispatchers would be careful to keep freights off it because they’d have to pay trackage rights. Sure, occasionally there will be a breakdown on one of the railroad-owned tracks and a few priority freights might use the passenger track, but they’d be the high-value I/M trains, which are lighter on the track than freight-all-kinds or unit trains.
The passenger track won’t enter a downward spiral. MOW crews would be keeping it aligned and smooth anyway.
I wish some of the excitement around HSR was redirected to improving Cascades service. I think hourly service between Portland and Seattle would be transformative and we have plans on the table to make that happen.
This! Reducing wait+travel time is accomplished far more cheaply, and much sooner, by adding more runs. Also, find ways to reduce dwell time at stations.
The current runs often sell out. The demand for more frequency exists.
And Cascades could add whistle stops at Kent and/or Auburn. HSR just provides fast connections between one point in Seattle and one point in Portland.
Ross and Delta are right. The distance between Seattle and Portland or Seattle and Vancouver is on the short side of HSR’s “golden zone” of 200 to 400 miles. There’s not enough of a market for Portland to Vancouver to tilt things. Reliable “higher speed” will attract ridership for much less per rider in capital cost than would true HSR.
BNSF would like to see a separate track the entire distance between Nisqually Junction and Vancouver Washington, but there’s not enough room in some places along the Columbia and Cowlitz Rivers for one, and the diagonal up the face of the ridge on Napavine Hill would require a lot of landfill or greatly deepening the notch on the uphill side. WSDOT plans at least initially to have 79 mph segments through those pinch-points.
And of course, passenger trains can’t run at 110 through the string of little towns north of Centralia and south of Chehalis or through Chehalis itself. It would be the real “Brightline West”. Similarly, several grade crossings north and south of Centennial Station are going to have to be over- or under-passed to support 110 as well, and a separate bridge span would be required to cross the Nisqually. It’s not just “add a third track”, though fortunately the existing right-of-way is fairly well insulated from the surrounding developments. There would have to be a pair of those long high-speed cross-overs between the new passenger track and the existing adjacent track about every ten miles to allow seamless meets.
All that said, reliable service at 110 means that, even with five intervening stops (Tacoma, Centennial, Centralia, Kelso, and Vancouver), elapsed time between downtown Seattle and downtown Portland would be a bit above two hours.
Seattle-Vancouver BC would be much harder. The trackage between Ballard and Everett along the Sound is super-scenic, but can’t be made faster because of the curves and frequent trespasses. North of Everett to Mount Vernon is very doable, except Marysville itself will always be slow; the tracks go right through downtown and are, at this time at least, not grade separated at any crossing.
The strip between Blanchard and Bellingham is irremediable other than by a super expensive five mile tunnel or a completely new alignment along I-5, which has a significant grade at both ends. The section through Whiterock BC will never be high speed either, because it’s the city’s waterfront with frequent pedestrian crossings. And of course, there are the immigration complications, but those would be true for “true” HSR as well.
Vancouver BC requires Canada to upgrade its tracks. Neither the provincial nor federal governments have been interested in this. So it can run high speed to the Canadian border, then conventional speed the rest of the way, stopping to wait for freight trains on Canadian tracks.
I can’t find the old reports but I remember the detailed plans for improving speeds to Vancouver (substantially) just assumed the trains would go along the coast from Downtown Seattle up to Everett. Much of the work is get rid of the crossings. This speeds up the really slow sections and makes the fast sections even faster. It is also an iterative thing. This should be a good thing. Both parties should focus on getting the most bang for the buck. Keep chipping away and making pieces faster. The old report includes this idea (it mentions a “midpoint” in the process where travel times are substantially better than now but not as good as they would be in the future). We’ve actually done some of it. But instead of focusing on improving in this manner we have this ridiculous idea that we will build something fast and new like California is building.
“. The trackage between Ballard and Everett along the Sound is super-scenic, but can’t be made faster because of the curves”
Or, they could purchase light weight trains with tilting ability on curves. Amtrak showed how this decreases travel time by running a turboliner from Portland to Seattle in something like 2:30 in 1974, even using the line along Puget Sound between Nisqually and Tacoma.
Yes, we could have had the WashDOT goal 50 years ago. Or 30 years ago, when the Talgos (but not light weight locomotives) were purchased. We decided it wasn’t a priority, for some reason.
So the question is, who is “we”? There was the will to invest in Talgo which was “state of the art” back then. But then not the will to actually use it? Now we’re the better part of a century behind the curve. We’ve bought new (nice!) train sets that are capable of 125mph but going to run them at roughly half that speed. WSDOT really should be rebranded as WSDoHwys at this point.. or WSDoh!
The federal government didn’t allow lightweight trains on mainline tracks until a few years ago, and I think now you have to go through a process to get approval for in a particular corridor.
The problem isn’t the light weight trains. They were already approved for use. The problem was the locomotives.
The locomotives used are really heavy.
The Colorado Railcar DMU weighed about half that of the current locomotives. They met all the collision requirements.
Passenger locomotives need to be based on that type of structure, not the underframe of a freight locomotive.
IF HSR were chosen between Seattle and Vancouver BC — it’s unrealistic now in an era of hostility between the two old neighbors, but that might change — the right thing is to bypass Bellingham and follow the NP route from Mt Vernon/Sedro-Wooley up to Sumas and thereby also serve the eastern suburbs in BC.
But Cascades service should not skip Bellingham, which has been a steady supporter since the 1970’s.
I remain skeptical that even with tilting trains that the speeds between Ballard and Everett can be raised very much. There are too many I/M trains on The Northern Transcon plus north-south traffic to and from Canada they’d have to avoid. Freights will never go faster than about 40 on that trackage, and there’s no room for a third track except by widening the fill into the Sound. That’s a non-starter for most citizens.
Optimistically, I think freight is going to have to confront a reckoning over the next couple decades, as renewables become substantially cheaper than oil and coal. My understanding is that over a third of freight cargo is now oil and coal, and, as that goes away, margins will shrink, and high profit loads on the mainlines that they have relied on after common carrier rates were eliminated.
It may provide an opening that perhaps the class 1 railroads would welcome, for government to step in, take over the tracks, and allow for upgrades and electrification. And hence allow for investments in passenger rail that don’t exist now.
Optimistically.
I pretty much agree that 250 mph is not a reasonable goal.
The major city is Seattle. Portland and Vancouver are the only major cities within 600 miles and both are less than 180 miles from Seattle. Because flying takes lots of upfront wait time in addition to taxiway and actual flight time, 90 minutes in train travel time to either city would still be amazing! So I’m more than content with 125 mph trains. Even 90 or 100 mph would be nice.
I’m sure there are those that want a fast way between Vancouver BC and Portland. But is a train serving that city pair that significant to warrant the extra probably 100s of billions? Probably not.
To me, the intercity rail goals should be more focused on getting more trains and more reliable trains instead. That probably means some behind-the-scenes dealing with BNSF. But I’d much prefer having trains leave every hour but take 30-45 minutes longer than trains that leave every 2.5-4 hours.
Before much faster trains get planned, I think there two more important things for intercity rail. One is a need to plan for adding a stop in Kent or. Auburn — even if it means closing the Tukwila stop. And the other is a need for directly connecting to State government functions in Olympia more reliably and frequently. These are much easier to achieve, particularly when TDLE opens.
Finally, Sounder and Cascades need to be branded and strategized as one corridor with different station stops.
Nobody is going to support a rail project that is barely faster than Amtrak, and might cost $150B to build. You get people to support it by saying it will might go 240 mph, and will cost as little as $24B dollars to build.
I disagree. Improvements to frequency and reliability would make a world of difference. Better speed is certainly sweeter, but without frequency and reliability the service is somewhat unfulfilling even if it is has segments with wildly faster speeds.
Al, BNSF won’t sell enough more slots south of Nisqually Junction for a meaningful increase in frequency unless a third track is built in most places. If the State is going to assume that burden, the track should be physically separated by several extra feet where that’s possible and should be built with wider curves, again where possible.
And the State should retain ownership so that BNSF dispatchers have a strong incentive to keep freights off it except in emergencies. The State would be wise to have its own Maintenance of Way staff to maintain the higher standards of passenger track.
Al, have you been out to Pinehurst Station yet? It’s been open a week. I want someone to tour the station, station area, and ride the route 77 few times, then write about their findings here. Would you be willing to do that?
Are you able to offer an advance? It would help cover Al’s travel expenses.
You’ve given me an idea. I do consider myself to be this blog’s leading Pinehurst neighborhood expert. I think I’ll go check it out myself. Btw, it’s good to see Metro finally installed some bus shelters there.
I’ve been to Pinehurst Station a couple times. It is pretty much exactly as I expected. The escalators up to the platform are a little longer than I thought they would be but still pretty short. It is a much shorter ride from the surface to the platform then just about every station not in Rainier Valley. There are side platforms. This means that you need to choose a side before you go up. Fortunately this is quite intuitive since the trains follow the same pattern as the cars (driving on the right) and everything is out in the open. If you are on the train you exit to the right. This is unusual and you could see folks lined up on the wrong side and then switch after the announcement.
Things on the surface are a work in progress. There is still a lot of construction going on but the bus stops are there. There are shelters of course (I don’t know why anyone thought there wouldn’t be). What is odd is that the westbound bus stop has a reader board (telling you when the next bus will arrive). I suppose this is handy in some ways but there is only one bus. Reader boards are most useful when you have several buses. One arrives just as you get to the bus stop and you have to choose very quickly (this has happened to me more than once at Northgate). I guess you want to build a bus stop for the network you want not the network you have.
In an ideal world the station would straddle the street but the walks from the bus stop to the station are fairly short. For a westbound bus you have to cross 5th. This is an easy street to jaywalk since it is narrow and very few cars go north of 130th there. To reach the eastbound bus you need to cross 130th. This is a four lane road so I expect most people to just wait for the light. The traffic light cycle is not ideal since it favors drivers coming off the freeway too much. This may be temporary given all the construction. There is only one lane for cars to queue up before turning, eventually there will be two. While not ideal the transfer from bus to train is better than most and about as good as any in our system.
The problem — as expected — is with the network. The 77 only runs every fifteen minutes midday. Worse yet, it drops to half hour after 7:30 pm. I saw a couple riders get off the train and start running towards the stairs (they had obviously looked at an app telling them the bus would arrive soon). They didn’t make it. There were a few Lime bikes there and they were contemplating renting those. This was at about 8:00 pm (not exactly late night). The routing is one reason for the terrible headways. The 75 overlaps in an area that doesn’t need overlapping. This is a big waste of service that could easily pay for better headways on an east-west bus.
There are other issues that have been mentioned before. The 77 essentially makes a ‘7’. While the routing number is clever this is a stupid pattern for a bus. (I guess we should be thankful there is no 88). Just as the bus gets to the heart of Lake City it turns. There is construction in Lake City which doesn’t help matters. But when the work there is done the terrible routing will remain. In general the bus situation in Lake City is terrible right now if you are trying to go southbound on Link. There are a lot of options but none of them are good.
Another problem with the 77 is that it is paired with the aforementioned 75. This is a very long route that has several potential bottlenecks. Sure enough, I’ve noticed the bus being way off schedule.
Overall I would grade things as follows:
Station Itself: A-
Bus Stops: B
Bus Service Levels and Routing: D
I thought the 77 was 15 minutes full time. A station that’s primarily for bus feeders needs a frequent feeder. Otherwise you’re disincentivizing people from traveling after 7pm, or incentivizing them to shift their trips so they’ll get back home by 7. That’s almost as bad as not having transit service at all, because it doesn’t fully address the mobility problem. It’s a first step to build something better from, but it doesn’t fully utilize the investment in Pinehurst station.
I understand that Metro has limited service hours and this is a revenue-neutral restructure, but that doesn’t change the fact that this is a drag on ridership, on the transformative potential of transit, and on people’s willingness to downsize their number of cars, and on their willingness to live in the 125th/130th corridor.
Thanks, Ross! Good point about it should have straddled the street, especially since there’s currently almost nothing on the north end of the station, except for the drop-off/pick-up loop.
I’m flattered that you trust my observations! Thanks!
I have yet to visit the station. I’ve been away on a work assignment and I’ve been too busy to explore the station since I returned a few days ago.
Ross summarizes it pretty well. I would add only a few possible comments:
The videos that I’ve seen have I-5 road noise roaring in the background. It may be a very loud station. What do others think?
The platforms look merely adequately wide and the videos show poles that stick out in some places. It looks to me to be easy to walk into one if someone isn’t paying attention. Is this a concern?
I’m a big believer in down escalators. There doesn’t appear to be room for them.
I’m curious how people are getting dropped off to then board Link. I expect the loop is used for pick-ups — but sometimes people hop out of cars in other, potentially unsafe spots when rushing to catch a train. I did see a pullout on Fifth Ave but I haven’t a clue how it’s actually signed.
It may be a week or even two before I can explore. There’s no reason for me to go to this station (as it lacks walkable destinations) so a visit would mainly be just to satisfy my curiosity.
@Mike — I agree. It is the result of a very bad planning process. They waste service hours with poor routing and then we can’t run the buses frequently enough. Hopefully it will get a bump after the levy passes but it could be so much better with sensible routing.
@Sam — Yes, and it gets worse. They have escalators, stairs and elevators on the north end (that hardly anyone uses). This increases the cost. I’m a fan of redundancy but you really only need it with elevators. They should have added a couple elevators and saved money. But the big cost hit was in the station placement itself. They didn’t calculate the hill slop correctly when they started. They figured going to the north would be easier since it would be less disruptive. Turns out the hillside is very steep there. Thus it turned out that building the station (with escalators to the north) was a lot more expensive than they thought. Instead of a simple, cheap station it became a simple, expensive station. Kind of like Ballard Link (where they follow a flat corridor with very few crossing for much of the way). I honestly don’t have any idea why they thought West Seattle Link was going to be cheap.
@Al — It is similar to every other freeway station. It is close to the freeway and not exactly quiet. But it isn’t as bad as crossing the freeway (on the many bridges). There is plenty of room to get on the station with no significant obstacles. I just came back from London and the whole thing is palatial in comparison (and you don’t need to mind the gap). There are no down escalators but it isn’t that far down. There are elevators (of course). Again, it is all relative. Our system is known for having fancy stations but very long walks to the platform (with the obvious exception being the surface stations). This station has a relatively short walk to the platform while everything else is good which is why I give it such a high grade.
Oh, and I happened to experience Lynnwood Link station for the first time as well. Like Pinehurst Station it is mainly designed as a bus intercept. There are a ton of buses that go there. Unfortunately, it takes a lot longer to get from the platform to a bus. The signs at the transit center aren’t great, either. I only saw a map of Community Transit routes, not one showing where to pick up buses going this way and that. (Maybe that was just me.) It isn’t always possible for various reasons but the simple approach (like that at Pinehurst Station) is generally better.
“There are a ton of buses that go there. Unfortunately, it takes a lot longer to get from the platform to a bus. The signs at the transit center aren’t great, either.”
Certainly the transfer at Pinehurst is more efficient than Lynnwood City Center. The transfer setup path at Lynnwood is visually pretty but it’s needlessly hostile to a user. From the lack of a down escalator that forces ruders down 65 stair steps to the unprotected walkway to the transfers to the acute angle in the path, it’s a pretty good case study in hostile transfer design.
RossB nailed it. The mediocre station could be improved with more bus service frequency.
And it will not be that costs by the time it would get started anyway. Something as mundane as light rail has skyrocketed in cost to the point where this system would probably cost half a trillion dollars by the time they actually break ground. California should give us a good price tag idea and then double it to account for inflation to the year it completes here.
Yeah but I’m not worried about the speed because they can’t even afford to build a train to Ballard from Westlake and I’m supposed to believe they can build a train going at any speed from Portland to Vancouver. The federal government is 40 trillion in debt already and probably hit 50 trillion in a few years so they are not going to pay for this. Washington is in a budget crisis where it can’t even run it’s ferries. Construction costs are skyrocketing and will only keep going up. California is literally incinerating money on cahsr and they are a bigger economy than Japan and still can’t get it done… There’s no way they will build this at any speed.
Yeah, that project was always a total give-away to contractors. But the HSR project from LA to Las Vegas would seem to have better bang for the buck and was initiated with mostly private money. I don’t know the convoluted corporate structure but Brightline/Virgin/Richard Branson just declared a form of bankruptcy in Florida. It’s not that the company/project is failing. Actually quite the opposite, it’s building customer base and increasing revenue. But in part because of COVID and probably overly optimistic assumptions in the first place it has a cash flow problem. The major investors backed the plan to restructure the debt and are still all in. I haven’t heard any recent updates on LA to Vegas but I’m sure it will have the same problems if (hopefully) it opens.
“that project was always a total give-away to contractors”
How else can you build high-speed rail that will eventually go between Los Angeles and the Bay Area (which has been needed for four decades and other countries would have, to reduce their dependence on airplanes), without building high-speed rail?
There may be tradeoffs and questionable dealmaking re the exact routing, or doing the middle first. But the underlying fact remains that Southern California has 23 million people, the Bay Area has 8 million, the Sacramento metro has 2 million, and even Fresno has 2 million and Bakersfield has 1 million (the cities are Seattle-sized). That generates a lot of trips between them. It’s like New York, London, Cologne, or regions in Japan. They should be on the most efficient and environmental mode: rail, and high-speed rail at that.
Gentlemen, get your facts straight on CalHSR. Yes, the IOS is costing about six times the initial estimate, but there is a very good reason for that.
The original proposal from Arnold’s CalTrans assumed that the tracks would be in the middle of I-5 from the foot of The Grapevine to the eastern foot of Pacheco. There would be station stops at nowhersvilles thirty to forty-five miles west of the Central Valley cities. The idea was that, “Hey! The 5 has a wide median that we already own, let’s use it for HSR. No land acquisition costs!”
[Well, not none. A small percentage of that 200 miles would have to have exited from the median because of a too-sharp curve or too-steep grade inthe roadway. But it was relatively speaking a footnote.
The populations of the Central Valley cities and their mostly Republican public officials were outraged at having to pay taxes to support something that so obviously failed to meet their needs.
The rest of the State, being Blue and generous essentially said, “That’s absolutely right. Change the route to serve those cities. It will only take fifteen minutes more!”
So the Authority didXso, but in so doing ran right into the stratospheric costs of building a new fully grade-separated railroad through some of the most valuable agricultural land in the world.
Then, to stir the pot, fossil fuel interests and think-tanks began a multi-umyear campaign to alienate the farmers who would be impacted to refuse to negotiate and instead force condemnation, which can take years.
Try it be noted that the flacks of the fossil industries were nowhere to be found when the right-of-way to raise US99 to freeway status in the 1960’s. That took more land than does the HSR right-of-way.
Oh, sorry Mike. This was supposed to go as a reply to Bernie. Can’t see enough on a phone.
The mainstream naysayers don’t usually understand that California HSR is about relieving airports. There is nowhere viable to put in a new airport or significantly expand an existing one.
Sure the cost is ridiculous due to a number of factors, but the cost (and disruption to people’s lives) of expanding or adding two or three major airports would be even more ridiculous.
Cascadia HSR is not about relieving airports. That’s because a much lower percentage of the air travelers fly between the cities on the proposed line. Shifting many air travelers to rail would barely help airport crowding.
I see HSR in the PNW serving a different purpose than relief on air travel. HSR in the PNW would the region feel smaller and more connected to each other in a megaregion of 10 million people. I see the closest comparison to us is Benelux Region, Paris to Amsterdam rail corridor, or the in planning BalticRail corridor that’ll serve Lithuania, Latvia, and Estonia. All three regions more or less are straight lines with some small branches to funnel people to the main line. The I-5 corridor is no different. We have 3 major cities (Vancouver, Seattle, Portland), 2 state capitols (Olympia & Salem), and 3 college towns (Bellingham, Corvallis, and Eugene). So you’d have a well varied mix of travel pairs for people taking the train. I’d take it now because of my professional association I have a membership with as I’d be able to go to events down in Oregon for a day trip. But other trip pairs would be for medical appointments, festivals, concerts, sports events, business trips, visiting family and friends, etc. Like there’s a lot of reasons for us to be building such an infrastructure project in our region.
“The highest speed recorded on the Shinkansen network for conventional rail is 443 km/h (275 mph), achieved by the Class 955 (300X) in 1996,[11] while a speed of 603 km/h (375 mph) was achieved by the L0 Series Maglev in 2015 on the Yamanashi Maglev Test Line (part of the Chūō Shinkansen).[12]”
https://en.wikipedia.org/wiki/Shinkansen
They normally run 160 to 200 mph, though faster is possible.
There seems little chance the agencies can find sufficient ROW or funding for high speed rail. There are many other transportation priorities.
I hope they focus instead on improving the Cascades (e.g., frequency, speed, span) and implementing variable tolling on the limited access highways. Toll revenue should not be used for capital but instead for maintenance; the toll rates should be set to optimize flow; improved flow would help all modes: freight, transit, general purpose traffic. At times of no congestion, the toll rates would be zero. The state could chose to provide reduced rates to low income househoulds; the overhead gantries will not know how much the households paid for the transponders.
Sadly, there is a Federal Law that prohibits tolling of any Interstate facility that was built with Federal funds. Previously existing toll facilities like the set of “Turnpikes” between Chicago and New York are exempted from the tolling prohibition.
It is also legal to toll a stretch of an Interstate facility that is being replaced by a needed new structure or where additional capacity is added. However only the replacement facility or the added capacity can be tolled, and only until it has been paid for. There appears to be some loosening on the requirement that tolling end for some replacement facilities.
So, I-5 between Seattle and Portland can’t be “variably tolled” without a change in Federal Law. Such a change is inconceivable, full stop.
It drives me mad that it takes 6 years to cut the ribbon for reinforced pavement and more bus shelters – all to save 2 minutes on travel time (referring to the R-Line).
I have an idea that I think this blog should hear on transit:
A seasonal shuttle from Star Lake Station to Redondo Beach. Redondo Beach seriously needs an alternative way of getting to other than driving or walking down a steep hill (which isn’t ADA friendly). My seasonal shuttle idea is inspired by the Golden Gardens Direct, and could be a pilot project funded via grants from the cities of Kent and Des Moines. The shuttle would run every 30 minutes.
We’ve got to use Star Lake Station in a different way rather than commuting. One of the reasons Star Lake’s ridership is poor is due to the lack of surplus land and poor bus integration.
This is a good idea and can’t cost much. You’re right about Redondo being a long walk from the A Line. One 30-foot bus could do this and give good service.
“You’re right about Redondo being a long walk from the A Line.”
Speaking of the A Line, that’s another major transfer from the Redondo Beach seasonal shuttle. The shuttle would connect both the A Line and the 1 Line which would account for high ridership by grabbing the core corridors in South King County to Redondo Beach.
So the benefit isn’t just Star Lake Station here, also Pacific Hwy South.
Des Moines had a community shuttle from Angle Lake station to the Des Moines waterfront when Link terminated at Angle Lake. The city paid for it. This could be a model for your Redondo concept.
“Des Moines had a community shuttle from Angle Lake station to the Des Moines waterfront when Link terminated at Angle Lake. The city paid for it. This could be a model for your Redondo concept.”
You mean the 635? My model was the Golden Gardens Direct, but I mean this shuttle and the 635 are similar because they’re both “Link to water” and they are in South King.
Ways to add riders at every station has merit. The challenge is doing it in a way that doesn’t end up overcrowding the segments through Downtown that have the heaviest use. That’s a design dilemma if any rail system that lacks a strong day-long attractor at the end and so many “feeder” ( nearby mostly residential walkable land uses, feeder buses, or parking structures) stations in a row.
For Star Lake, it looks quite tough to come up either great ways to add ridership. It simply doesn’t have the walkable land use redevelopment potential of other South King stations as the only one that abuts an interstate, the one with the most restrictive surrounding terrain, and the one that’s hardest to have a bus layover there. Sure the garage can be promoted but that’s about it.
The best feature it has is that it’s an easy walk from 272nd — with the platform even reachable via ramps so without using any stairs or an elevator (albeit a bit more circuitous). The other South King stations aren’t positioned as well to allow for a major east-west arterial to offer a on-street drop-off or pick-up spot in both directions. Sadly, the street design there makes any on-street stopping rather dangerous. It’s probably why Metro 183 (only every 30 minutes) pulls into the station driveway loop instead.
By the way, I hope that ST creates a parking garage utilization report now that we’ve opened all the new Link ones. Are they all full? Depending on occupancy, they can be used and even monetized in new ways.
For example, BART finally decided to monetize its parking via an app and allow for overnight parking while struggling to restore its financial viability, especially after pandemic ridership losses. (https://www.bart.gov/guide/parking)
Al, I expect that most folks that would take Link to a Redondo shuttle are from south of Downtown Seattle. Sure a few from farther north will go once to see the beautiful view, but they won’t burden DSTT.
Yes. Certainly Redondo Beach can be considered a South King thing. Recreational trips are also not usually at commute hours.
Maybe it should even go more easterly to RapidRide I? I could see more East Hill folk being interested in getting to Redondo Beach than Seattle folk would be.
I could also see that going by Federal Way Link would then connect with lots more bus routes.
Al, yes. That stretch of the county along 272nd — from southeast of Kent to Puget Sound is strangely empty. But soon enough it will fill in. Perhaps it can be done more rationally than the rest of the South King Subarea was developed.
As an Oklahoman and transit enthusiast, this blog gives me a glimmer of (likely) false hope.
I found out why the ST Express route 556, unlike the route 550, isn’t in-service between the Bellevue TC and the Bellevue Library. The layover space in front of the library will be getting charging infrastructure for Stride, so the route 556 is going to have to move.
Really? I thought they just cut it because it wasn’t really necessary. If I recall correctly, Bellevue TC will be getting the Stride charging infrastructure.
STRIDE won’t layover at Bellevue TC, so it has to go somewhere like 532/535 do.
Perhaps after 535 is gone, 556 can do that loop which is nice because it can stop north of Bellevue Square.
It could be that both the Bellevue library and the Bellevue TC are getting Stride chargers, since both S1 and S2 will terminate in Bellevue. IDK. Anyway, I was told that the Bellevue library layover space will be getting Stride chargers.
That one stop trip, between the Bellevue Library and the Bellevue TC was somewhat popular on the route 550. I wouldn’t say loads of people rode between the two points, but it was a pretty steady light ridership. I could never figure out why the route 556 made the BTC the official last in-service stop, since it’s going to the library anyway. (Btw, if you ask the driver, some will let you ride to the library anyway).
Charging infrastructure for a bus that is running 99% on the freeway… WTF? Talk to Toyota about how they designed the Prius… no infrastructure required. I guess Bellevue Library makes more sense than say Hospital Station or, gee… maybe the two bus bases 1/2 a mile away and out of DT
ManhattenBellevue?So, who’s getting the money for the design and build of these charging stations???
Bernie, the Prius is a hybrid; it charges itself while running on the small gasoline engine. The STRide buses will (supposedly) be “BEV’s” or “Battery Electric Vehicles”. They must be charged from an external source.
I remember somewhere it says ST was also going to adopt some pavement induction charging concept on I-405. I am not sure if that idea is still alive.
I don’t think it is crazy to run BEV bus on freeway. LA does that already. Some Tesla models have longer range than my combustion engine car.
More studies….wow so Cascadia high speed rail latest studies concluded that it is worth studying a study about how to study high speed rail in case there’s ever any money to fund a study about how to actually build it?
You got a problem with that :-/ Sort of comes back to the basic way ST is run. A board of politicians given a pot of money and the chance to make that pot bigger. They care about getting reelected and doling out send money is a way to get votes. Transit… the only people that care are already going to vote for the person with a D by their name so they don’t matter.
The state doesn’t want to spend the big money to build it, but it has legislators and private backers clamoring to pursue it, so it spends the small money for another study to advance it one step without committing to it.
That’s usually how big corridor study is phased.
The kickoff stage figures out how to study the corridor next. Otherwise who would do that work?
Why are some people overly worried about the state spending a hundred billion dollars on it, when there’s no concrete proposal to do so, the current steps don’t lead all the way to a proposal, and the state hasn’t identified where the money will come from? This could be just spending a few million dollars on a few steps that leads to something that stalls and never gets to the proposal stage. Then we don’t have to worry about it. We just have to worry about how all that work wasn’t applied to incrementally improving Cascades, which could have the same effective benefit for a fraction of the money and time.
So if the HSR vision never goes anywhere, it’s just political show and a futile exercise. That’s sad, but a lot of politics is like that, and it can’t be extracted out when influential billionaires are pushing that vision and the state is listening. Meanwhile the state is still functioning. They could solve the problem in one stroke by taking our advice and accelerating Cascades’ long-range plan and reinstating the portions that have been watered down (full 110 mph service, maximum frequency). But they aren’t interested, and that’s the only thing worth telling them, so there’s nothing else to do or worry about.
I think many of us are wondering about how to transmute the hype and momentum around high speed rail into action to improve the existing Cascades service.
“I think many of us are wondering about how to transmute the hype and momentum around high speed rail into action to improve the existing Cascades service.”
Unfortunately that’s like asking how to convince ST to build an automated Ballard line and cancel the bad DSTT2 design. We’ve tried repeatedly on both issues and failed, and we don’t know much more to do. But at least this HSR vision is still at a preliminary conceptual stage. The state build it until it has a concrete project proposal and a funding source.
The state is pursuing its Cascades long-range plan. It updated it in 2004 (there are STB articles about it), and is now doing the second step of a 20-year plan. The problem is it has had this plan since the 1990s and it won’t just fully fund it and just do it; instead it proceeds in a piecemeal manner on-and-off manner using the trickle of annual funds Cascades gets. And it has watered down the alternatives instead of fully going for its goal in the 2000s. The legislature has full control of this. It could prioritize and accelerate this using its existing transportation resources, and identify additional resources to fully implement it now. But it has to stop wasting resources on an HSR vision that’s getting in the way.
Citing top speed is usually not as informative as citing projected travel time between major cities.
China has quite a few 350 kmh corridors with trains running slower than paralleled 250 kmh corridor because some of those more recently-built 350 kmh corridors are busier with fewer limted-stop trains. It doesn’t occur to me that WSDOT would ditch all small/mid-size city stops along the HSR corridor, so shooting for a 250 mph design speed is pointless. It is like running 80 mph BART train on NYC subway track. It won’t reach top speed enough to justify the investment.
Which is why 110 on a State-owned third track is a big improvement. It allows frequency improvements that BNSF won’t agree to on its pretty much maxed-out existing plant.
Today, a Link Fare Ambassador made an announcement I’ve never heard them make before. He actually did it twice. Right after Symphony, and again right after Pioneer Square. This was a Redmond-bound 2 Line train in the Downtown Seattle Transit Tunnel. As soon as he got on, he said to everyone on board … “This train is not going to the airport. It’s going to Bellevue. We’re going eastbound, not southbound. It usually catches 1 or 2 people per train.” Then him and his partner checked everyone’s fare, and got off on Mercer Island.
If, like he said, every day, probably on most every southbound train, someone accidentally gets on the 2 Line instead of the 1 Line, shouldn’t that be an automated onboard announcement?
I’ve seen some kinds of non-airport warnings in the PM peak for the past few months. I think it was station audio announcements but I don’t 100% remember. And trains say via airport. I’ve never seen a fare agent or security agent on the train say it. So I think ST is trying to make the announcements, but it’s not every time or always in the same way. Late before University Street station was renamed, the announcement was changed to say “University Street. Remain on train for University of Washington campus”, so it could do the same for CID, if it can do it only on 2 Line trains.
It’s an easy mistake to make. I was coming down the escalator at Capitol Hill and there was a train already sitting at the platform. I quickly hopped on — only to find out it was the wrong train.
Since both lines have been running for only a few months, it’s easy for a rider to assume that there are only 1 Line trains like it was for 15 years prior.
There probably should be an additional electronic sign above the end of the escalator or stairs. The ones already there today can be hard to find when a rider has only a second or two to make a decision.
They already have the plane icon on 1 Line trains. I think the bigger signage improvements are for Northbound/Southbound platforms (or East/Westbound for the 2 Line-exclusive stations), to coordinate with the announcements like “1 Line to Lynnwood City Center at Northbound Platform in two minutes”.
Overall though, link signage has gotten pretty good (or I’ve gotten used to it). Apple Maps needs exit numbers/letters on their transit layer and Google Maps needs to start recommending the right exit (not just a random one). But at least the exit signage is pretty good on Link—many other systems in the US are really bad at that, like Boston.
Oh and “International District/Chinatown” should eventually be renamed to “Chinatown-International District”
One confusing thing ST should change is the next-arrival displays at the top of the northern mezzanine-platform escalators at Westlake. The sign says either Federal Way/Redmond or Lynnwood but the display right in front of it has both mixed. A typical message is “Lynnwood Now, DT Redmond 4”. How many people go down to the wrong platform because of these displays?
I think those are intended for passengers transferring (and coming up the stairs). But I agree, they could be confusing for new riders.
While we’re on the digital signage topic, it’d be great if the signs in the entrances to westlake (and I think university district) would consistently show the next departures to know how much I should rush to get to the platform in time.
If they’re transferring it doesn’t matter. They have to go to the other platform now, and wait however long it waits for the next train. Seeing the arrival time before they get to the platform wouldn’t make a difference, except maybe to tell them to run to the other platform because it’s coming in 1 minute.
But running requires going up and down stairs, so it’s not fast in any case, and they could injure themselves or others on the stairs, and they might miss the train anyway. In any case, the maximum wait is 10 minutes unless it’s late at night or Link is off-schedule, and in the combined 1/2 Line segment it’s maximum 5 minutes. Maybe not worth running for.
The only other benefit of a display at the top of the escalator you’re coming from is for the psychological reassurance of knowing how long you’ll wait. But that won’t make the wait any shorter than not having the display. And it’s not that big a deal to go to the other platform and then find out when the train will come, since you can’t make it come any sooner anyway. The time people most need next-arrival displays psychologically is when they’re standing at the platform being impatient: it helps them to think, “5 minutes, that’s five 1-minute blocks…. Three down, two to go…”