The Official MBTA System Map

In that case, will SL1/3 just be able to turn into the bus tunnel from D Street? Either way, this still looks like it'd be reasonable to drop the Congress St. stop. Otherwise, it's effectively doing the same stop twice, mere seconds apart. People who would have alighted at Congress St. could just get off at WTC, adding seconds to their trip. Meanwhile it would (slightly) speed up the trip for what looks like the vast majority of the bus trying to get to South Station.
That is the plan. And you're right, dropping the stop would seem reasonable at that point, but the Remix map actually shows the Congress St stop but not the actual WTC station on SL1/3, which makes absolutely zero sense. So until any further information is released, I'm going with the stopping pattern I've shown.
(but also, you know, this is straying pretty far from any talk of map design)
As is inevitable in this thread, a map is nothing without the system it's describing.
 
The picture @Riverside shared makes the sequence clear, but one of the instances where non-geographically-accurate diagrams can cause confusion. The Congress St. stop is at WTC. They are essentially the same stop twice, but on the line diagram, they're shown two stops apart.
This can be somewhat ameliorated by using the "official" name for the stop (insofar as the automated announcement on the bus is the "official" name): Congress St at World Trade Center -- or on a map, Congress St at WTC or Congress St/WTC.
Actually, why does the Congress St. stop exist? It wouldn't save much time to skip it, but some. And in my experience, it's a pretty quiet stop compared to all the people trying to get to South Station. Does anyone have numbers handy, out of curiosity?
Adding on to the numbers @TheRatmeister presented, I've always assumed that the stop was included because they wanted to avoid complaints from business travelers going to conferences at the WTC, coming from the airport -- it's been a long trip and it'd be maddening to get stuck on the bus when it's literally driven right by your destination. (Especially if it gets stuck in rush hour traffic.) To your point, it's bad design to have the route go in a loop, but it's also bad rider experience to force riders to go the long way around when it's easy to drop them off.
In that case, will SL1/3 just be able to turn into the bus tunnel from D Street? Either way, this still looks like it'd be reasonable to drop the Congress St. stop. Otherwise, it's effectively doing the same stop twice, mere seconds apart. People who would have alighted at Congress St. could just get off at WTC, adding seconds to their trip. Meanwhile it would (slightly) speed up the trip for what looks like the vast majority of the bus trying to get to South Station.
Hmm, I'm not sure I agree with that calculus. There are three traffic lights between Congress St/WTC and the actual World Trade Center station. I don't know the exact timing of those lights, but assuming an average cycle of 60-90 seconds, and assuming the bus is held, on average for half that time at each light (30-45 seconds), that's roughly another 2 minutes on the trip. (And sometimes it will be more, if they get really unlucky.) That's obviously not terrible, but I think it's non-trivial.

The entire fact that there isn't a direct connection from the TWT into the Silver Line's tunnel is the real culprit here. Everything else is mitigation of that, and I think at least some mitigation is appropriate.

Here's the hot take: replace SL1 with a pair of Logan Express services, one express to South Station and one to the Seaport. With a bus lane on Congress St that is guaranteed right-on-red, the Seaport route could limit itself to 2 lights (Seaport Lane and Silver Line Way) before getting right back on the highway.

1740590507936.png
 
New York’s MTA just released a new system map with a number of variants.

 
Pretty big mistake (15 doesn't go to Savin Hill) made it onto the Wards Maps merchandise, the map hasn't been posted on mbta.com yet so we'll see if it gets fixed before going officially live.
Screenshot 2025-08-24 at 12.27.07.png
 
I've been wanting to do a version that aligns Copley and Back Bay for that nice clean 39 line for a while, but I finally made it work. The main drawback is that it nearly doubles the spacing between Mass. Ave and Back Bay which looks a bit awkward. Is it worth it? I'm still not sure.
map_redesign_2029_newerest.png
map_redesign_2029_newerer.png
 
I've been wanting to do a version that aligns Copley and Back Bay for that nice clean 39 line for a while, but I finally made it work. The main drawback is that it nearly doubles the spacing between Mass. Ave and Back Bay which looks a bit awkward. Is it worth it? I'm still not sure.
It's worth it! It's a viable transfer between Orange and Green, which is only evident when you draw the map with the stations aligned. As for the distance, it's not that noticeable.
 
It's irrelevant until there's a fare-free transfer between the two.
I think the underlying relevant factor that we actually want to show is that: Copley and Back Bay are close together -- close enough that they can be used as substitutes with a short walk. (As compared to, say, Arlington vs. Tufts Medical Center.)

Simply aligning the two stops on a map, to me, doesn't show this well enough. On the current map from @TheRatmeister, there's not much difference between Copley-Back Bay vs. Arlington-TMC.

Where such "horizontal alignment" works better is at conveying distance from downtown: Copley and Back Bay are parallel on the north-south axis, and so are Symphony and Mass Ave, Heath St and Jackson Square, etc. This is of course a valuable dimension, but it's orthogonal to "station closeness".
 

Back
Top