Sunday, July 1, 2018

Bus shuttle upsides: Finding opportunities from irregular operations

Starting next weekend, the Lowell Line will shut down on weekends for nearly six months, to allow the installation of Positive Train Control (PTC) and expedite track work for the Green Line extension. These are worthy and necessary projects. PTC will make the Commuter Rail system safer and more reliable, and GLX will bring better transit options to tens of thousands of daily riders.

No one likes a bus shuttle, but they do give us an opportunity to try new and innovative service patterns. Yet the T has taken the Lowell Line schedule and made it all but unusable, nearly tripling the duration of a trip from Lowell to Boston, while at the same time ignoring nearby resources—the 134 bus and the Haverhill Line—which would be duplicated by the Commuter Rail replacement service. TransitMatters recently wrote about how the MBTA could optimize Orange Line shuttles in Roxbury and Jamaica Plain using parallel Commuter Rail service, and this page has written about how the MBTA could optimize the Alewife-Harvard shuttle. This is a similar idea.

The Lowell Line dates to the 1830s—one of the first railroads in the world—when the Boston and Lowell Railroad was built as a freight line to serve the factories on the Merrimac. Its proponents underestimated the potential for passenger traffic and for the most part avoided existing town centers, yet the fast travel time—a stagecoach trip took most of a day, and even in 1835 the B&L made the trip in under an hour—attracted significant passenger traffic: an early lesson in the concept of "induced demand." Two centuries later, the trip is still reasonably fast, direct and, because it was originally built to avoid town centers, hard to approximate with buses on nearby streets.

The railroad runs 25 miles from Boston to Lowell, while a bus zigzagging to serving each station runs 35, nearly all on narrow, local roadways. No wonder the schedule from Wellington to Lowell requires an hour and forty-five minutes. This is the reason that permanent replacement Commuter Rail service with buses on the weekend which is floated from time to time is a non-starter: buses are unable to efficiently make intermediate stops in town centers over a long distance. Rail service can, and, with the implementation of Regional Rail elements (i.e. level boarding platforms, faster-accelerating electric trains), could do so more quickly and efficiently than it does today.

As proposed, the Lowell Line bus replacement schedule makes use of Wellington’s proximity to I-93, and buses begin there, rather than downtown. This is similar to the busing taking place this summer on the Worcester Line, where buses have connected to the Green Line at Riverside. Yet for the Worcester Line, the T provides express service from Framingham to Riverside (which is significantly faster than the local route) and local service to serve stops in between. For the stations in Newton, no service is provided, but nearby bus routes, and the Green Line, provide service without slowing the trip from further out.

A similar concept could be applied to the Lowell Line. There is no redundant service for the outside portion of the route: a bus trip making each stop from Lowell to Anderson/Woburn is scheduled to take 45 minutes, as long as the full rail trip from Lowell to Boston. From there, rather than wending their way through Woburn, Winchester and Medford, replacement service could run express down I-93 to Wellington, reaching the Orange Line in an hour and, with a transfer, getting a traveler North Station in 1:15, not a particularly fast trip, but better than a two-hour crawl. For trips to and from Winchester and West Medford, no additional service would be required: it’s already there in the form of the 134 bus.

The 134 runs almost the exact same route as the proposed replacement shuttle. It passes through Winchester Center, within a stone’s throw of Wedgemere, and a half mile from West Medford (which is served directly by several other bus routes), from which it continues to Wellington. The service is provided hourly, which is more frequent than the Commuter Rail shuttles, so intermediate travelers from, say, Winchester to Lowell could ride into Wellington, and connect to a bus to Lowell. To provide the same span of service would require that a few buses—two on Sunday morning and two each evening—be extended by a few stops to Winchester (this might be something small enough that it could be done in the short term, without waiting for a new schedule). Most passengers would find taking the 134 as convenient, if not more so, than the replacement shuttles.

This idea would also save the T operating costs. The current Lowell Line shuttles are scheduled to take 1:45 from Lowell to Wellington, and 1:45 back. Running directly from Anderson/Woburn to Wellington would cut this to an hour, saving nearly 90 minutes of operating time for round each trip. With 16 round trips each weekend, this would save 22 hours of operation. Extending a few 134 trips to Winchester would claw back three or four additional hours of service, but it would still result in 18 hours of operating hours saved each weekend. Given that this project is slated to run from now until December, it will affect 20 weekends of service, and if a bus costs $125 per hour to operate, this would save the MBTA $45,000 in operating costs.

Another option, rather than running buses to Anderson/Woburn and on to Wellington, would be to skip the Anderson/Woburn stop—which is a large park-and-ride, so people using it could park at other, nearby stations—and run directly from Wilmington to Reading instead and connect to Haverhill Line service. This train runs parallel to the Lowell Line only a mile to the east, and Reading would be roughly a 40 minute ride from Lowell. The Haverhill Line weekend schedule would have to be increased slightly to provide the same level of service that the Lowell Line does: currently the Haverhill Line is served by only six trains on a weekend day, with three hours between trains. With the Lowell Line shut down, Keolis should have some additional staff available for these trains, since the net operation would still be less than the Lowell Line running. This would not only better-utilize existing resources and provide a better product to the traveling public on the Lowell and Haverhill lines (although the cost savings from less busing may be canceled out by running more trains), but it would draw in new riders to the Haverhill Line with more frequent service.

This table assumes a cost of $125 per hour for bus service, $750 per hour for rail service (estimated here), and that each train would only require a single bus.

AlternativeTravel Time
Lowell↔Boston
Bus HoursTrain HoursCost:
per weekend | total
Local bus to Wellington2:00560$7000 | $140,000
Express bus to Wellington1:15380$4750 | $95,000
Bus to Haverhill Line1:10269$10,000 | $200,000

Assuming you'd need two buses to handle any instances with more than 50 riders, the calculation would be:

AlternativeTravel Time
Lowell↔Boston
Bus HoursTrain HoursCost:
per weekend | total
Local bus to Wellington2:001120$14,000 | $280,000
Express bus to Wellington1:15760$95,000 | $180,000
Bus to Haverhill Line1:10529$13,250 | $265,000

While the Reading/Haverhill Line alternatives cost more (because they require more railroad operations) passengers would pay a Commuter Rail fare from Reading, nor does it take in to account additional Haverhill ridership, which would recoup some of this expense. Another alternative would be to have Amtrak's Downeaster trains stop at Reading for bus passengers to Lowell, although capacity may be an issue. These estimates do not take a detailed look at how buses would be deployed, although the current schedule seems to show buses laying over at Wellington and Lowell for more than an hour, hardly an efficient use of resources. The Haverhill Line alternative, in particular, would allow a bus to make a round-trip in two hours, matching the frequency of improved train service there.

The installation of PTC gives us opportunities to experiment with different replacement service. Instead of simply drawing a line on a map, the T should be creative in leveraging existing infrastructure to provide the best possible product to the traveling public, while at the same time finding ways to reduce operating costs. These often go hand-in-hand, and the Lowell bus service is an example of how, with some small changes, the T could save time for its passengers and money for itself.

Saturday, May 5, 2018

A "vehicular cyclist" goes swimming

Let's imagine, for a moment, that John Forester (who is this? read on) teaches swimming lessons.

First, he assembles potential swimmers in a classroom. He lectures them on the particulars of swimming for several hours, noting that not everyone is cut out to be a swimmer, and that if they're not comfortable in deep water at first they shouldn't even try. Then they go to the pool. Do they start blowing bubbles, then move to kick boards, and slowly become comfortable with swimming? Nope, straight in to the deep end (the pool has no shallow end). If you don't make it, you get fished out, and told to do something else when it's warm outside. A few people probably don't make it out, but then they were never cut out to be swimmers in the first place. They should have thought about that before jumping in a deep pool.

A few people, however, survive. These are probably people who are young, fit, and maybe stubborn. Some of them might go on to swim a lot. They may go to a lap pool, take the lane, and swim back and forth, becoming more and more comfortable with deep, open water. But most of the newer swimmers are discouraged. Without infrastructure for beginners, they're left clinging to the edge of the pool, scared to move away without some kind of safety net from infrastructure which allows them to ease in to swimming. So they get out, and never come back. Forester is undeterred: he tells them they won't be able to swim if they're not planning to be "effective swimmers", and that they can't become effective swimmers if they start in the shallow end of the pool.

So what happens if everyone is taught how to swim by John Forester? First of all, not many people swim. It may be a nice warm summer day, but most people will be too afraid to enjoy the water, because they've been taught that it is dangerous unless you're able to swim a 100 meter freestyle in under two minutes. What this means is that without many swimmers, there's little demand for swimming facilities. Sure, some serious swimmers will go and find lakes and rivers to fulfill their needs, but most people will find other pastimes. That's fine with Forester. In his mind, if everyone learns to swim, they'll probably just crowd the serious swimmers out of the pool altogether.

We don't teach swimming this way. But for many years, it's how we attempted to teach people to ride bikes. Who is John Forester? He's what we'd call a "vehicular cyclist." He came up with the phrase. And he argued that he was right, and for many years, people listened. But he is little more than a privileged white male imposing his ideas on a public which doesn't want them. It's a good thing he never instructed swimming.

The Outside/In podcast had a great episode (to be fair, most of their episodes are, hi Sam) about the history of vehicular cycling. What the mantra vehicular cycling says is that there shouldn't be cycling infrastructure; rather, cyclists should behave like cars, taking the lane when necessary, and that better, safer infrastructure would just have people riding bikes cast off to side paths and banned from the road. He became a force for decades, and during that time, very few people actually rode bikes, and most of the people who were were fit men comfortable at 25 mph making a left in traffic.

Forester is nearing 90 now and is unrepentant, taking his opinions to the grave. Good riddance. In the past 15 years, his followers have been seen for the charlatans they are, and we've slowly, and often begrudgingly, begun to build infrastructure for people riding bikes which is safer and more welcoming. Like magic, more people are riding bikes. No one has banned bikes from the road because we've build bike lanes, and people comfortable in the road are free to use it. Some do. Most don't. But there are a lot more people in the latter camp.

This past week, I was at a meeting discussing what the City of Cambridge is planning for South Mass Ave (believe it or not, I have some thoughts on this). Someone suggested at a breakout session (the city did a great job of setting up the meeting to have people talk to each other) turn boxes so people who weren't comfortable making a left could do so. A local vehicular cyclist—who will remain nameless to protect the guilty (but needless to say, he's an older, white male, fancies himself a bicycling expert, and I've told him he is culpable in the deaths of many cyclists because he has argued against bike lanes for years)—said "you wouldn't need that if they made a vehicular left."

I snapped. [I'm paraphrasing]
You know what? Not everyone is comfortable doing that. Not everyone wants to shift across two lanes of traffic to get in to the left lane to make a turn, then sit in a line of cars waiting for a turn light, and if they don't move fast enough the car behind them will honk at them, or worse. No one is keeping you from undertaking that movement, but other people should have a safer option. Imagine if you were a woman, or a person of color. Imagine if you weren't as strong as you are. Put yourself in someone else's shoes. Your ideas have been proven wrong for years, and a lot of people have been injured or died because they've tried biking on the roads as you'd have them designed and all you do is blame them for not being out in the lane of traffic moving fast enough. Don't give me this baloney where you tell me that 'if they only knew how to bike correctly, they would have been fine.' That's nonsense. You're asking people on bikes to jump in to fast-moving traffic with cars and trucks and buses. That's fine for you. But it's not for everyone. So what we get is more fast moving traffic, and fewer people on bikes. Apparently that's what you want."
I'm not about to let these people get a single word in edgewise. Their time has long since passed. Vehicular cycling is dying, clung to by a few old men. It's failed, with often tragic results. It's time for it to be relegated to the dustbin of history entirely. I'm all for an open discourse, but I am done—done—giving time of day to vehicular cyclists.

Thursday, April 12, 2018

Cambridge NIMBYs revisionist history

Every so often, you wonder what goes through the minds of people who don't want to build more housing where there's high demand. (Which works. The market works.) In Cambridge, there is a contingent of people who live near Fresh Pond and don't want to build more housing because there's been too much development there already (or something). They'll trot out all the tired canards: climate change (the solution to which is obviously to make people live further away from jobs and transit), traffic (the solution to which is obviously to make people live further away from jobs and transit), impact to natural resources (even if the housing is being built on brownfield sites which haven't been wetlands for decades or centuries) and the like. Does it make sense? No, of course not!

(Unless, of course, you bought your house 30 years ago for a song and have seen it appreciate it to the point that you're blinded to the housing cost and availability crisis around you. And you remember the days when Cambridge had 20% fewer residents and traffic wasn't so bad and the Red Line wasn't full. You can't have both: your home value has appreciated because of the increase in traffic, not in spite of it.)

Has Cambridge done its part? Hardly. The city has an arduous process to permit new development, and while more housing has been in the pipeline in recent years, it's not nearly enough. It is true that Cambridge does more than many of our more suburban neighbors. But that shouldn't be an excuse to sit back and wait for someone else to build the housing our region needs.

Yet here we are, with several hundred residents in the Fresh Pond area signing a petition for a "pause" for housing development. It's an absurd stance, to paraphrase: a complete and total shutdown of housing development until we can figure out what's going on. Their arguments are just as specious as as the the premise, and today this page will analyze their latest opinion piece and poke the holes necessary to ensure that well-informed discourse takes place, not discourse where one of the parties uses scare tactics to poison the dialogue.

Original in indented italics. My comments in plain text:
There’s a new housing construction clash in Cambridge, this time over a letter signed by more than 600 people hoping to push the pause button on decades of virtually unrestrained development. 
That's their opening. "Virtually unrestrained development." In a city where you have to spend 45 minutes in front of a zoning board (and certainly hours of preparation) to add a second dwelling unit to a house which was built as a two-family household when it was originally built. For something which won't really affect anyone. These are the same people who rail against protected bike lanes because it affects their parking space: when you don't get what you want through the public process, demand the public process is shut down. Doesn't work that way, nor should it. But please, go on.
Ah, yes, from the days when Alewife had genuine community.
It led to the submission of a zoning petition to be taken up by the City Council next week, demanding that the council weigh in on an essential question: What kind of communities shall be shaped by new housing, affordable and not? In a cash- and resource-rich city, why should we continue to allow the process be driven by developers focused on short-term profit rather than by urban planners and city officials focused on building genuine communities?
I'm confused. Is there something less genuine about people who move in to new apartment buildings? Most of the development in the Alewife area is taking the place of things like old industrial buildings or dilapidated night clubs. And the city may be cash-rich, but it doesn't have the resources to build new housing. Instead, the way it works is that the private sector builds new housing, and then the owners pay taxes on it. What a novel concept!
To help understand why we need more attention on city- and citizen-directed planning rather than mostly out-of-town developers of luxury rentals,
This is what we have! Who do you think sits on the planning board, and the other boards which support it? Who votes? This is a false comparison, conflating "city- and citizen-directed planning" with "out-of-town developers." But those operate together! City-directed planning is the process through which out-of-town developers of luxury rentals (and really, of anything) create housing. It's not as if out-of-town developers run the process.
one need only approach the town from the west and consider the so-called communities that have taken shape with the current “anything goes” approach.
Define "anything goes." While you may not love every piece of the development in the Alewife corridor, every project goes through a thorough zoning process. And it turns out that if you build enough luxury rentals, the overall cost of housing will come down.
By car from Belmont and Arlington on Route 2,
Apparently, the best way to understand Cambridge is from a highway.
one’s gaze is first drawn to the right, where virtually uncontrolled development sprawls across the Alewife wetland, suggesting “No Vision” vs. “Envision” Cambridge. 
Areas in yellow are impervious surfaces today. Red are
buildings. A few new parking lots near the right-most
buildings aren't shown. But those parking lots are now parks!
What about this development is "virtually uncontrolled"? If you look at the area south of Route 2, the majority is protected wetlands. It's not virtually uncontrolled. It's actually quite controlled! Here's where the revisionist history comes in: there's actually significantly less development there now than there was 50 years ago. In 1969, much of what is now the Alewife Brook Reservation was a series of parking lots, which have since been removed, remediated and turned in to a park. So, removing a parking lot and turning it in to a park is "no vision"? If that's the case, what should we envision instead? We have six acres of new parkland in the Alewife thanks to the lack of vision of the planners there. If that's what we're fighting against, I'd hate to think what we're fighting for.
Rounding the corner, one passes dilapidated, “brutalist” Alewife T architecture – untouched by enhancements or landscaping since its creation 30 years ago. 
The Alewife station is brutalist (although relatively functional, and could work better with, say, bus lanes in and out), and it is dilapidated, but it is certainly not the fault of the City of Cambridge, or that we've built too much housing.
One wonders about the asbestos-contaminated brownfield lurking behind the chain-link fence around Jerry’s Pond, across from the Rindge Towers and Jefferson Park, the largest concentration of affordable housing in the city. More than a half-century has passed since the contaminants were left there by W.R. Grace. 
In addition to having nothing to do with this housing "pause", this is kind of a chicken and egg problem. The public housing was built there probably because the nearby land uses made the land undesirable for other housing (and when the housing was built in the 1960s, there wasn't the kind of market pressure which would today turn a clay pit in to housing without governmental intervention).
Though a process with community input concluded the safest approach at the time was containment, one cannot help wondering if such corporate neglect would have been permitted in a more affluent neighborhood.
But now I'm even more confused. There was a community process, which is supposed to be good, but here you don't like the outcome, so it's a corporation's fault. If a corporation develops housing, it's bad. But if a corporation neglects an area, it's also bad. "We can't win, don't build any housing!" Finally, such neglect probably wouldn't have occurred in an affluent neighborhood, but the case is that an affluent neighborhood probably wouldn't have had such land uses next to it in the first place. (In other words: there's no quarry in the midst of Observatory Hill.) This is not an excuse for not cleaning up Jerry's Pond (for which there are new plans to remediate and clean), but also not a reason to stop building housing in the region. This whole paragraph is pablum. We can walk and chew gum at the same time. We can clean Jerry's Pond and build more housing: in fact, the new city revenue from the new housing may allow us more funding for laudable projects like the Jerry's Pond clean up.
Stopped at the Alewife light with a head swivel to the right, one’s gaze is drawn into “The Triangle,” a dead-end neighborhood without a name that presents like a Chinese flash city and corporate annuity for institutional investors. 
I mean, some of us call it Cambridgepark Drive. Is not having a name really that much of a sin? Also, this neighborhood has been developed over 30 years (it had a planning process at least as far back as 1979!), adjacent to the Alewife T station. It's not perfect transit oriented development (there's way too much parking) and, yes, it has corporate owners (not sure what the China hang-up is). Also, those corporate investors pay two-thirds of the city's property taxes. So that's something.
It offers egress, 
Not sure what "egress" means here, since it's a dead end, right?
impenetrable traffic jams during rush hours and virtually no amenities to suggest community.
Okay, yeah, it offers impenetrable traffic jams. So, let's do something about that. Lots of that traffic is coming from the west trying to get in to Alewife. Why? People can't afford to live in Cambridge! There are buses, and they're full, but they're no faster than the traffic they sit in. Bus lanes—which would be feasible if we put on our thinking caps—could attract a lot of these drivers if they provided a faster trip than driving. And amenities, you know how you get amenities? Build more housing! Amenities don't spring up unless there are people to use them. More people = more amenities. (Setting aside the connection to two bike paths, many walking paths and a 10 minute walk to the Whole Foods and Trader Joes across the tracks may actually count as amenities.)
Finally, up and over the railroad bridge to the south it is hard not to wonder about the dead trees, never-cleaned sidewalk grime, permanently graffiti-ridden “Alewife Parkway” plaque
Yes, the Alewife Brook Parkway bridge is a mess. It was built long-enough ago it wasn't built with sidewalks nearly wide enough. It is also a state-owned property, so beyond the purview of the city. But let's stop building housing anyway. Of course, we could build a new bridge. How do we do that? Well, it would certainly help if we had a developer build the bridge integrated with a new development.
and a mall owner and city lacking initiative to create safe and aesthetic pedestrian passage to shopping, Danehy Park and West Cambridge. Pedestrians are instead obliged to navigate a sea of traffic and parked cars. 
 And, yes, the city could probably do a better job of traffic management in the Alewife area, by incentivizing bicycling, walking and transit use. And the mall owner, which built the mall in the '70s, could have built a better mall then. But it's not a reason to not build more housing, in fact, it is a reason to build more. More local housing will mean more customers arriving by foot, giving the owner and incentive to build a more reasonable pedestrian environment to accommodate these customers, or risk losing them.
Desperately needed affordable housing should be built, but not through abandoning good planning. It should exist within the context of a city vision – one that ensures the evolution of livable communities with access to green spaces, public transit, schools, meeting areas, shopping – and safe, sensible pathways connecting our neighborhoods. 
Let's see what the Alewife area has:

√ green space, much of which has recently been reclaimed
√ public transit
√ schools (nearby and accessible by pathways, and an easy Red Line trip to CRLS for older kids)
-  meeting areas should be integrated in to new development
√ shopping across the bridge
√ safe pathways, although more are needed
Aspects of these are evident, but for such vision to take better shape, a brief pause on development is needed so we can access the nearly complete recommendations of our city-paid planning consultants. Let’s leave behind an era of disconnected, developer-driven Triangles in favor of one led by our own world-class planners, city leaders and citizens.
This doesn't make sense! What are the benefits of this "pause"? What will be done better, or differently, if we have this pause? How long do you propose this pause? Why not call it what it is: a moratorium? What in this entire article gives you an argument for a pause? And what's so disconnected about Alewife, anyway? It sits on the Red Line. It has good walk/bike paths leading to green space, and to Davis Square, Belmont and Arlington (and Lexington and Bedford and beyond). It has sidewalks to the mall, which could be improved, but are an argument for building more housing, not against it! The disconnnectedness of Cambridgepark Drive has nothing to do with housing development, and can be mitigated without any sort of housing moratorium.

Much of what has been built has been built over the course of three decades (Alewife didn't exactly open yesterday). Projects like these have plenty of vetting through various city boards and committees: if you don't believe me, go to a bicycle committee meeting where the committee vets every large project to make sure it complies with the city's bicycle ordinance, and this was a couple of pages in otherwise thick permitting documents. We have a great staff at the city and a lot of interested citizens. If you are interested in improving the built environment the best thing you can do is to get involved. But the city's goal should be to permit as much housing as it can, not to stop development in its tracks. Doing so, and ensuring that the housing crisis is exacerbated, is about the worst thing you can do.

Sunday, April 1, 2018

Springtime thoughts on Seattle, Rhode Island (and Calgary)

Spring break! Woo!

What do I do on spring break? Apparently I travel places and look at their transportation networks.

Amongst other things! Last year I went to Calgary to visit a friend living there for the year (and to go skiing). This year it was Seattle for a cousin's bat mitzvah, to see friends (and to go skiing). And then I came back to Boston (Thanks to TG for the UG) and spoke at a conference in Rhode Island (where another speaker talked about Seattle). My only regret was not spending the $10 in BART fare to get to the In N Out in Millbrae during my layover there (but I did get BART to call me brilliant). Next time.

In any case, since Yonah came back from Canada tweeting about things, I am going to write up some thoughts in a blog post (old school, I know).

Calgary

I visited friends last year in Calgary, because they were only there for a year. After a day at Canmore and Lake Louise (Advice: "remember that you're skiing and to look away from the amazing view every so often.") I browsed my way around the city itself (after visiting November Project, of course), particularly interested in how a relatively new city in the Texas of Canada has such high transit use. It helps to have no downtown freeways and a progressive parking fee scheme (and high parking prices), and bus service which has grown along with the C-Train. (Much detailed here, by Yonah.) The C-Train is the stand-out service, carrying more than 300,000 passengers daily, with the routes converging on a single, at-grade segment downtown.

Outside of the city, the trains run in highway medians and rights-of-way with full signal priority, but downtown they don't. With level boarding and four-car trains, the trains are able to move in sync one light cycle every stop, allowing 30 trips per hour per direction, carrying 24,000 passengers. Each four-car light rail train carries as many passengers as an eight-car L train in Chicago, and after 35 years, the system has reached capacity. A third line is planned to be built in a subway under the city (Edmonton's also-successful light rail uses a subway downtown).

Seattle
One bus came two minutes before
it departed … but these arrival signs
sure are nice!

Before going to Seattle proper, I found myself in Bellingham for a cousin's bat mitzvah. While I didn't have the chance to ride the local transit network, I did note that it had a 15-minute network, not bad for a town with under 100,000 people (albeit many of them college students). Then it was off to the main event. The only city in the US to grow transit ridership in the last year. The 206. Seattle.

What has Seattle done right? They invest in transit, most recently voting on a 20-year, $50 billion package to expand to build 110 miles of light rail which will carry 600,000 passengers, building a system that may carry as many passengers daily as the CTA, WMATA or MBTA's rail systems. This isn't a streetcar (they have one of those too, although it's dubious how effective it is) but a heavy-duty system where three-car trains match the capacity of bigger-city subway trains. I rode most of the line four times, each including the section along MLK south of downtown where it runs in a center median on a city street. Despite a top speed of only 35 mph, it is given nearly full signal priority: in the trips I took, accounting for 15 miles of travel and 48 grade crossings we only had to stop for a signal twice; the other 96% of the time the train was lined through the crossings at track speed. Imagine what that would do on, say, the B Line in Boston. 

The Link is ready to go north.
Yet Seattle seems to have learned that for a high-capacity, trunk line, grade crossings don't really make sense, so new lines are mostly in private rights of way. The extension to the University of Washington is in a 3.2 mile, $1.7 billion dollar tunnel which was completed on time and under budget. It dead-ends at the U-Dub for now, but is planned to go further north (there are bizarre garage doors at the end of the platform) and Seattle may run in to the same issue Calgary faces: a single segment of line nearing capacity. But that's a good problem to have. And Seattle has found a sweet spot and is building tunnels at a cost of about $300 million per track per mile, stations included. At that rate, the North South Rail Link in Boston would cost about $4 billion.

So many bus lanes!
But it's not just heavy construction. I follow Dongho Chang on Twitter (you should too!) to see a constant barrage of bus and bicycling infrastructure in another city. Seattle does overnight things which seem to take years in Boston. I'm sure it's more complex than that, but Seattle is a fast growing city which seems to be planning for the future, not one ignoring growth until it's too late. What does this get you? Bus lanes seemingly anywhere there's a long traffic queue to jump by. As I'd coincidentally learn in Providence, an investment by the city in transit such that the number of people living within a 10-minute walk of a bus which comes at least every 10 minutes will rise from 25% to 72%. And this in a city barely half as dense as Boston, Cambridge and Somerville. But when the buses aren't always overcrowded and/or slow, and when they have priority lanes to get them by traffic queues, people use them. The light rail is nice, but most Seattle commuters ride the bus.

See, adding a protected bikeway isn't that hard.
Are all the roads wide enough there's plenty of room for bikes and transit? Hardly. The roads are no wider than many of the main streets in Boston. Spring Street a road with parking, a bike lane, two lanes of traffic, and a bus lane. It used to look like most roads in Boston (Beacon, Tremont, etc): three lanes of traffic and two parking lanes. Now: two lanes of traffic, a bike lane and a bus lane. Bike lanes get real protection. It's not rocket science: if you make transit fast and biking safe, people will use them. The point is not to abolish the use of cars, but to make other options more competitive.

Then there's land use. Seattle is not a very dense city, but it's growing quickly. From 1980 to now, Boston has grown from 562,000 to 673,000, gaining 20%. Seattle has gone from 494,000 to 704,000, gaining 40%. So the new light rail line? The surrounding area was rezoned. It's sprouting four-to-six story buildings with reduced parking requirements. Land use, housing and transportation go hand-in-hand. I'm sure what Seattle is doing isn't perfect, but at least they're trying.

One thing I did notice were the dockless bike share bikes around town. I'm not sure what to make of the dockless systems: I'm used to Hubway in Boston (although I've been using it less and my own bike more, partially because they moved the nearest rack about 50 meters further from my house, which matters for short trips!) and not knowing where a bike might be could be troublesome. I'd also wonder how well the bikes work in a hilly city like Seattle. The jury is still out, it seems, and the ridership numbers aren't huge given the number of bikes, but the up-front costs are certainly lower, and I'll remain interested in which model works best there and elsewhere.

Oh, and it has an all-night bus network, too. And this bus driver, who writes this blog. And there goes my evening.

Rhode Island


In Rhode Island, I saw a presentation about Seattle.
I stepped off a plane in Boston and got on a train 9 hours later to Rhode Island to be a panelist talking about regional rail in the, well, the region. I traded $4 for an hour of sleep and took Amtrak down and then a plodding MBTA train back, illustrating how messed up the Providence Line is (big idea: Strava, but for transit). The panel was a good discussion and was well-attended; it's hard to remember what was said when you're saying some of it, but I think there is still a lot for people to learn about how the rail network works (and doesn't work) in the region. I did get to poll the audience and as usual, they underestimated the percentage of people using Commuter Rail to get in to Boston. We talked about level boarding, electrification, and all the things the T really should be doing between Boston and Providence.

Just as interesting was the afternoon panel, and some of the remarks at the start. The governor talked about tearing down the 6-10 Connector and replacing it with bicycle- and pedestrian-friendly infrastructure after the community said it didn't want a bigger highway (hear that, MassDOT?). The state also has a transportation master plan that looks like more than the Commonwealth's laundry list of projects thrown in to a blender and spit out. So, something to learn from our neighbors to the south.

Thursday, March 29, 2018

A short history of the new early morning bus service

Back in the halcyon days of March, 2016, I wrote a series of blog posts about overnight transit after the T unceremoniously axed late night transit service. I had them all planned out (if not fully written) and posted the first one at 8:30 on a Thursday morning before I went to work. (My blog posts in Pacific Time for no apparent reason.) The first post was about how the T should be clearer about when and where it provides early morning transit service, rather than burying the details on paper schedules and webpages.

It was popular, apparently. Several thousand views that day alone and it's still one of the most read posts on this page. It caused a shouting match of sorts on Universal Hub with one commenter saying the current schedules which showed the trips with five-point-font notes were adequate (I'm still not sure why) which resulted in Stuart Spina stepping in and dropping the mic:
Is it really that hard to just publish a special Sunrise timetable?  
AND CAN THE BUSES ACTUALLY BE SIGNED UP FOR THEIR ROUTES!!!???  
Frank's voice tells you when the doors open that the bus is "Route 192 with service to Haymarket" and yet the sign says "39 HAYMARKET" "39 VIA FOREST HILLS"…
But the best part was an email I received from the T at 11:52 a.m., barely four hours after the blog post went live from a service planner there:
Greetings. The MBTA received the following customer feedback this morning, which referenced your blog post. I can’t vouch for what he says are errors in your post, but I thought you might be interested to hear it. 
Issue Reported by the customer: Customer called to say that there is a website called amateurplanner.blogspot.com that gives a list of all the early morning bus trip . The problem is the blog is not giving out correct information. mainly on the 57 to boston and rts 117 leaving haymarket and the 109 . He would like to know if mbta could create a separate schedule in the packets for the early morning bus trip , He states that everyone does not know how to read the schedules and that’s why there is little ridership. This would stop independent bloggers from giving out incorrect information. 
As for your post, I agree that the information may be difficult to find for some users, but just like all other bus schedule info, it is available on our paper and HTML schedules for the relevant routes (e.g., the 194 trips shows up on both the 89 and 93), as well as our GTFS feed. The 191-194 numbers are purely for internal purposes in our scheduling software, and not as some sort of obfuscation. They are so different from the normal routes that we decided they should have separate route numbers rather than be listed as a variant of a normal route. Most users would likely find the normal route numbers less confusing, so that’s what the public sees when they see these trips on schedules or Trip Planner. Just as these trips are listed under the normal routes that make up the early morning trips, if you plan a trip with Google Maps or Trip Planner that uses the 194, it will display it as 89/93. 
I can see how a separate page about early AM routes might be helpful to some folks, but if I were a regular 89 or 93 rider, I would still want to have the early AM options for my route on my paper schedule for those routes, since that’s what I care about—not early AM options for the other side of town. I’ll bring up this idea for a separate sunrise service page with my colleagues, and also discuss whether we can improve how these early AM trips are described.
Let's unpack that a bit. First, in the letter written to the T, it's unclear exactly going on. A customer called to tell the T there is a website. Wait, really? Someone read my blog and was so incensed they called the T? And then they tip their hand. Note they go to "he would like to know …" and "He states …" Wait, who states? The customer? Or the website? I am convinced to this day that the T called themselves up and sent in this comment, particularly because it was sent to me barely four hours after the blog post went up.

If so, it would be either the quickest the T has ever responded to anything, or a testament to the fact that they really should have better things to do.

My response was that my information was not wrong (although I made some clarifications) and as Stuart pointed out it is confusing when the ASA announcement is different from the bus's head sign. And what would preclude keeping that information on the paper maps, as well as creating a special website? They're not mutually exclusive.

I thought my post was equivocal and fair. But apparently I'd touched a nerve.

Long story short: a week later, we'd (we = TransitMatters) proposed the entire night bus plan on this blog and in Commonwealth Magazine. Since then, we've been through several iterations of the plan with the T in fits and starts, and we're working on launching a 24/7 bus route pilot in addition to earlier service (and a dedicated web page for it, although I think some mapping would help) on these additional routes. It's been two years, but hopefully this is the start of building, as I called it two years ago: robust, equitable and efficient overnight transit.

Extend Red-Blue to … Kendall?

At some point on the Internet, I've scoffed at the idea of extending the Blue Line across the Longfellow Bridge (somehow) and then run along Main Street to some superstation at Kendall (which there's not room for) and then making a turn on the Grand Junction right-of-way (or something). I still do. You couldn't reliably run the Blue Line and Red Line together on the Longfellow and they have separate loading gauges so would need different tracks at Kendall. To facilitate a Red-Blue Connector, it makes sense to stub-end the Blue Line at Charles Station and provide an easy answer to Kendall Square.

Or does it?

This would be a short and pointless blog post if the first paragraph was 100% true. Plus, I've written that blog post before. Twice.

One of the trickiest things about the Red-Blue Connector is shoehorning a good, useful terminal in to the space under Charles Circle. It's not easy. You'd have to dig a wide tunnel, or long tail tracks, or dig out pocket tracks or tail tracks under a busy roadway and the supports for the Red Line. It would be somewhat difficult to build any sort of functional terminal: there's just not the space. You could put something under Storrow Drive (technically Embankment Road) and Ebersol fields, which would result in a decent terminal, but you'd have to dig up and rebuild the fields, and you'd be digging adjacent to the river. It would provide for good operations; you could stack in several tracks for layover, storage and recovery, rather than using crossovers and/or the Bowdoin Loop.

So Ebersol would work for operations, but you're still pushing more people in to the Red Line and the already-overburdened Kendall and Charles stations, and forcing every Kendall-bound Blue Line passenger to transfer (albeit an easier transfer than exists today). There's another potential terminal. It's bigger than Ebersol, would allow increased capacity across the Charles, the potential for further expansion and, oh, yeah, it's already somewhere where a huge hole is going to be built in the near term.

I'm speaking of the Volpe site recently bought by MIT. Since they're going to be digging a big hole, it would make sense to put something useful in it, not just more parking. It is an extra 3000 feet to tunnel from Charles Circle to Volpe, but it's mostly in a shallow river and free from utility considerations (as far a I can tell). In theory, this should be relatively cheap tunneling: it could be done in a similar manner to the Ted Williams Tunnel: building tubes off-site, digging a trench, and sinking the tubes in to place, except downscaled by a significant factor: the width of two Blue Line trains is narrower than two highway lanes. The river is 12 to 15 feet deep just downstream of the Longfellow, so it would need to be excavated down about that much to accommodate current depths. The TWT required digging through muck and in to bedrock at times to accommodate a shipping lane clearance at low tide, but the Charles has no such river traffic. The disposal and mitigation of the sludge on the river bottom may be the trickiest part, although it would be beneficial to start cleaning up the muck on the bottom of the Charles River.


Then there's the Broad Canal. This should be easy. It's 15 feet deep, doesn't need clearance for anything more than kayaks (although the waste heat from the power plant would have to be accounted for), and could be easily coffer-dammed, dug out, cleaned up, and filled in with several feet of water sheet above. To make up for any displaced water volume (hello, Waters of the United States), the canal above could be extended, Lechmere-style, to a water feature figuring in prominently in the new Volpe development.


What does this get you? A lot, actually. First of all, designing a subway loop terminal in Volpe's basement would add minimal marginal cost to the development and would make it extremely transit-oriented, and add value to the project: there'd be no need to trek through the Marriott to Kendall Square to the Red Line for trips downtown. (Do you need a loop? Probably not, but if you can get MIT to dig the hole, you might as well put a good terminal down there, although if you wanted to run trains through to Binney and beyond in the future, you could build a simpler island platform with tail and storage tracks beyond.) This north/east side of Kendall is booming. In the past 10 years, several blocks have been rebuilt from gravel lots to job sites and residential developments: below is the same corner in 2011 and 2017, for instance. It would also bring transit a bit closer to the no-man's-land in the mile between Kendall and Lechmere. With Volpe as the linchpin of several thousand more jobs and residents, expanding transit should be a priority in Kendall.

2011
2017
This plan would also give the Kendall area a direct connection to more of Downtown Boston, East Boston, the HYM Suffolk Downs site Boston is proposing for Amazon (but will be developed no matter where Amazon goes), and, most importantly, the airport (this could—maybe—provide the impetus to build a better connection to the airport from the Blue Line). It would provide more capacity across the Charles—although the north-of-Boston portion Red Line is most full from Central to Kendall—and more importantly would take some traffic out of the Kendall Station, which was never really designed for the number of people using it today.

Further down the road? The Volpe site hemmed in by Biogen to the west, but a right-of-way could be preserved over to Binney Street where a further extension could easily reach the Grand Junction. From there, much is possible. A line to Sullivan Square and Assembly via the Grand Junction. A line in the other direction linking Kendall to Allston, and then further west. Once GLX is complete, the Blue Line will be the only transit line which terminates in Downtown Boston, which is operationally inefficient. This would give it a terminal at both ends to improve operations.

I'm not sure how much this costs; I haven't been able to find a good breakdown of the order-of-magnitude for the costs for the TWT. (I did speak to Fred Salvucci about it, and he said it was the cheapest and easiest part of the Big Dig to build, although that's a pretty low bar.) I also can't find information about the specific cost of the "Haymarket North Extension" tunnel costs, but that project seemed not to have broken the bank (as far as I can tell, the below-ground portion of that line did not use boring machines). Searching the Globe archives, the entire Haymarket North project cost $180 million at the time, equivalent to $750 million today. That number includes: the five miles of the line to Oak Grove, some tricky engineering building between buildings from Haymarket to the river, and the B&M holding up the state for $18 million ($95 million today) to build the line through Charlestown (This is than half, considering 1970s inflation, of what the state would pay a couple years later to buy the entirety of the Boston and Maine lines in Massachusetts east of Fitchburg: $39.5 million, $170 million today). For this proposal, the state would only have to negotiate over a small portion of Broad Canal Way, and its owner—an REIT—would stand to benefit from better transit to the airport so might be willing to make the price right.

In any case, if Charles Station was built as a through station and not a terminal, it would reduce construction costs there (where they're expensive) and improve operations. The station could even be built with side platforms to keep the width of the subway narrower. The Volpe terminal could be built basically for free if it was integrated in to the overall Volpe development. The question comes down to the cost of the underwater tunnel. If it's reasonable—and it seems that it would be—this would make a lot of sense. What about transfers from further north on the Red Line? This would preserve the full functionality of the Red-Blue connector, except it would work even better. And if the North South Rail Link ever obviated the need for the Grand Junction to function as a freight corridor, the Blue Line could easily be extended west or north.

Thursday, March 15, 2018

Mass Ave reimagined: Charles River to Central Square

In the fall of 2016, I took a course at MIT with Fred Salvucci (who also happens to be my research advisor here) called Urban Transportation Planning. Without knowing about my previous work on Central Square, the assignment arc for that semester was to critically analyze Mass Ave in Cambridge between Central Square and the Charles River and present findings to the City of Cambridge. When I emailed Fred and said “uh, just so you know, I sort of did this assignment already for my blog a few weeks ago” is response was something along the lines of “great, do more.”

So I did more. I expanded the scope of the project to the entirety of the corridor, created GIS maps of the corridor with current and future street layouts, analyzed traffic counts and population, and created cross-sections in Streetmix between Central Square and the river. I then put these in to a Word Doc, with text and images separately, turned it in, and thought “I should rewrite this for my blog.”

That was more than a year ago.

It turns out that taking a 10,000-word document and getting it in to a web-ready, blog-ready format is a bit harder than meets the eye. But after watching bus upon bus get stuck on Green Street, and the bike lanes in Central Square constantly choked with livery and delivery vehicles, it’s time to get it on the web: a vision of a people-first Mass Ave in Cambridge. This post may depart a bit from the usual (poor excuse for) prose on this site with a bit less sarcasm than usual, but hopefully will be as informative as posts have been in the past.

Oh, and it’s long. Real long. Happy (?) reading.

Massachusetts Avenue has not always been Cambridge’s thoroughfare; in fact, it has not always been called Massachusetts Avenue. Until the Harvard Bridge provided the newest connection between Boston and Cambridge in 1891 (the only newer bridge between the cities is the Eliot Bridge far upstream) traffic between the two cities passed mainly across the West Boston or Cambridge (now Longfellow) Bridge downstream or the Cottage Farm (now Boston University) Bridge upstream. Mass Ave wasn’t even called such; Main Street stretched from the Longfellow to Harvard Square, beyond that was North Avenue.

In the past 125 years, Massachusetts Avenue has become the iconic street of Cambridge and, it could be argued, one of the most recognizable streets in the world, if not for the street itself but what lies along it. In a barely four mile stretch are Harvard and MIT, two of the world’s leading universities, three world-renowned music institutions (Symphony Hall, the New England Conservatory and Berklee College of Music), and Boston Medical Center. In Cambridge the street hosts the national or global headquarters of several major pharmaceutical corporations, and Boston University and Northeastern University lie just off the corridor as well. The Harvard Bridge has even spawned its own unit of measurement; the bridge spans 364.4 Smoots ±1 ear from Boston to Cambridge, something which can’t be said of 5th Avenue, Michigan Avenue, Sunset Boulevard or the Champs Elysees.

History: Mass Ave and Pattern Breaks

During this century and a quarter, Mass Ave has had three distinct “pattern breaks” when the use of the corridor has shifted. When the Harvard Bridge was built in 1891, the first electric streetcars had only rolled down the streets of Boston three years prior and it would be another decade until the first automobiles appeared. For the first 20 years of its life, Mass Ave was dominated by foot traffic and streetcars. (In fact, the first streetcar to use the Tremont Street Subway originated in Allston and rolled through Central Square early on the morning of September 1, 1897.)

The first pattern break occurred in the early 1910s, when the street was torn up for the construction of the Cambridge-Dorchester subway (now the Red Line). This dramatically changed the travel patterns through Central Square: no longer did streetcars run through the square; most now terminated in Central for a transfer downtown. Central Square became a major subway-surface transfer point between surface cars and subway trains. (The Boston Elevated Railway generally built complex subway-surface transfer stations like the Streetcar tunnel at Harvard or facilities in Sullivan and Dudley Squares. Central was the only major transfer point built with no separate infrastructure for streetcars, likely because the square had already developed and there was no room to do so. Even Kendall, which served only a couple of streetcar routes, had a streetcar loop-turned-busway until it was rebuilt in the 1980s.)

The next pattern break occurred more slowly in the 1950s and 1960s. The last streetcars rolled through Central Square in the early 1950s and the center-of-street-boarding streetcars and safety zone platforms were replaced with side-of-street bus stops as Central slowly went from being a transit node to a vehicular intersection. While the northern portion of Mass Ave was rebuilt with a median (and without streetcar stops) in the 1950s, Mass Ave wasn’t appreciably widened in Central Square, although it likely would have changed dramatically had the Inner Belt highway been built as planned, this delay and eventual cancellation may have saved the street from 1960s-era urban renewal. Still, the removal of the streetcar facilities led to an auto-dominated square, with wide expanses of pavement at the Prospect-Mass and Mass-Main intersections and a reduction in the mass of many of the buildings (so the owners could save property taxes) resulting in many of the single story buildings and parking lots today.

In the past decade, vehicle traffic volumes on Mass Ave have decreased while at the same time transit use and cycling has increased: bike counts have more than doubled in the past decade and Red Line ridership in Central has doubled since 1988. Unfortunately, the allocation of road space has not kept up with these changes. It’s time to design a new pattern break for Mass Ave’s infrastructure to catch up with the behavioral pattern break of its users.

The Context of Massachusetts Avenue

Massachusetts Avenue is home to some of the richest human capital in the world, yet it is congested at best and dangerous at worst. The street hosts several MBTA bus routes and the MASCO shuttle, but the passengers on these buses are regularly subjected to congestion delays despite, at rush hour especially, outnumbering people in cars. Several cyclists have died on the street in recent years, and the bike lanes installed in the past two decades are inadequate and outdated; they provide little protection from car doors and passing or turning vehicles and are frequently used by drivers as convenient double parking spaces. Parts of the street, when not congested, are straight and wide, encouraging motorists to travel at high rates of speed, which is not conducive to a safe environment for other users.

Cambridge has made improvements to the avenue between Central Square and Memorial Drive in recent years. It’s hard to believe that a decade ago Lafayette Square was a sea of pavement (now a park) and bicycle lanes were not yet installed. This roadway was narrowed in many places from four lanes to three. While it was an improvement, it was also a missed opportunity: the street still prioritizes cars over other users. No provisions were made for transit users, and the roadway is still focused mostly on providing throughput and parking for automobiles, with transit users and cyclists a decided afterthought.

Cambridge is growing—the population is up 15% from 1990 to levels not seen since the 1950s, and Kendall Square is continuing its transformation from a collection of parking lots in to one of the major high tech centers of the world—but traffic is not. On Mass Ave at Sidney Street, it has declined 30%, from 19,400 in 1999 to 13,600 in 2013. While demand may have required four lanes in the 1950s before the regional highway system was built, it does not today: the worst congestion in Cambridge is due mainly to downstream effects (throughput issues in Boston often back Mass Ave across the Harvard Bridge). Over this same time period, transit ridership is up, and the proportion of Cambridge residents and workers commuting by car is down: the majority now walk, bike and take transit to work.

Ridership on most transit serving Central Square is growing. Data from
MBTA Blue Books.
How to Analyze Mass Ave

So the question must be asked: if the majority of the users of Massachusetts Avenue (and Cambridge in general) do not travel in cars, why is most of the roadway given over to traffic and parking? The right-of-way should be reapportioned based on the current use of the roadway and future trends. The City has laudable mode shift goals and has made progress towards attaining them. However, it is important that the design of the city’s streets is commensurate with these goals: empty roadways will lead to induced demand as more people rely on single occupancy vehicles, while slow transit and dangerous cycling facilities will provide a disincentive towards non-auto modes. This creates a vicious cycle as more vehicles cause more danger for pedestrians and cyclists and more congestion for transit users. (Providing faster and more reliable transit provides a virtuous cycle: more passengers require more frequent service, which reduces wait times and increases demand further.) Vehicle throughput on Mass Ave is important, but it has been the singular top priority for far too long. This must change.

The long term goals for Mass Ave need to be about prioritizing the safety and throughput of all users, in four major groups: pedestrians, cyclists, transit users and motorists. It is hard to argue that safety of all users should come before throughput in any design (within reason) and the safety of users can be relatively easily ordered as follows by vulnerability:
  • Pedestrians
  • Cyclists
  • Transit users
  • Motorists
Note that this is not a linear scale: safety for pedestrians and bicyclists is much more important than for other users, since they are far more vulnerable users. Safety between different groups is very much correlated: a road which is safe for pedestrians and cyclists is almost always safer for motorists as well.

Once you solve for safety, the next step is to solve for throughput. Ordering users here is a bit more complex. It may be best to order modes by the current number of users on the roadway, as well as the potential. For instance, if transit was faster and more frequent, the roadway could accommodate many more transit users, and there are already more transit users on Mass Ave than people in cars at rush hour. (The 1 bus, which is an important crosstown route between the Red Line and Orange and Green Lines, is often slower than making a connection downtown due to congestion on Mass Ave. If it were reconfigured as a bus rapid transit line through Cambridge and Boston, it could reduce the strain on the overburdened Red Line.) The MASCO shuttle runs at or above capacity on Mass Ave as well, and providing it bus lanes would make its trip significantly faster than it does today. The City and MBTA could work with MASCO to provide easier access to the service for the general public (it is currently open to the public, but requires a separate fare paid with a Harvard ID, a high barrier to entry for casual users) in exchange for the use of transit lanes.

Likewise, a safer road for cyclists may attract many more cyclists (as Cambridge has provided safer cycling infrastructure in recent years, bicycle counts have more than doubled). Cambridge has a bicycle network plan to add separated bicycle facilities to most major roadways, including all of Mass Ave. This post will attempt to do just that.

On the other hand, the number of motorists on the roadway is constrained both by the roadway width and layout as well as upstream and downstream bottlenecks: it would be difficult to add many users to Mass Ave without widening other roads far afield from the corridor. Pedestrians are numerous along the avenue, but are far more able to withstand bottlenecks within reason, although by no means should be plan to narrow sidewalks in the middle of Central Square and other high-pedestrian areas.

With this in mind, throughput goals should be ordered as follows:
  • Transit users
  • Bicyclists
  • Pedestrians
  • Motorists
This is not to say that we should kick motorists to the curb (so to speak). But when looking at various segments of the roadway, it is a good guideline to see if our priorities are askew. For instance, are we arguing against separated bicycle facilities (or protected bike lanes or “PBLs”) to maintain parking on both sides of the street? Are we forcing hundreds of bus passengers to narrow, crowded stops to facilitate a left turn used by only a few motorists an hour? Are we creating space for vehicle queues where we could instead have a transit lane to allow bus passengers to pass slow-moving traffic?

This post will use this approach to consider the stretch of Mass Ave between Memorial Drive and Central Square. West of Central Square, Mass Ave is quite narrow: the street is only 44 feet wide. This section has the least traffic and is rarely congested, and while a complete streets treatment may be warranted, it would not be possible to provide transit lanes and PBLs even with all parking eliminated. (North of Harvard Square is beyond the scope of this post, but that section of street was redesigned in the 1950s to eliminate safety island streetcar stops and build a wide highway-like road, a design which begs to be rethought. In fact, the city actively campaigned against the safety islands for the streetcar, which may have helped lead to its demise. The cars operating from the North Cambridge carhouse to Arlington Heights, Waverley and Watertown were the last cars operated by the MTA which didn’t feed the Central Subway in Boston. Whether streetcar service would have survived with the city’s support is an open question. This page has some opinions on that.) It will break the Avenue in to two parts: one stretching from Memorial Drive to Sidney Street, and a second from there through Central Square past City Hall. It will then discuss strategies to implement best implement this plan in the short and longer term. For the most part, it will attempt to rebuild the roadway within the current curbs and right-of-way, although in several areas will propose shifting curbs and, in a few, widening the right of way in to currently-unused space.

Legend for maps. Data generally
from City of Cambridge.
A few notes on syntax:
  • Mass Ave will be referred to as westbound towards Harvard Square and eastbound towards Boston. Cross streets will be referred to as northbound and southbound. 
  • All cross sections will be looking west, with the Cambridgeport side on the left and the Area 4 side on the right.
  • PBL = Protected Bike Lane, also known as a separated bicycle facility or a cycletrack. PBLs can either be sidewalk level or at street level, and can be set off by curbing, bollards or parked cars and a painted median. Sidewalk level PBLs are generally preferred.
  • Bus stops are generally shown as “floating bus stops” which allow some traffic (bikes, or bikes and cars) to pass to the right. Bus lanes are generally best located in the middle of the street, especially since curbside lanes preclude any other curbside use.
  • All street cross-sections are from the Streetmix.net website.
  • Each map shows the current condition of the street on top, an the proposed layout below.
MIT: Memorial Drive to Sidney Street

Memorial Drive and the Harvard Bridge

Before focusing on the Cambridge portion of Mass Ave, a note should be made about the Harvard Bridge. The bridge carries tens of thousands of bus passengers, motorists and cyclists daily between Boston and Cambridge, but is too often choked with traffic, especially eastbound in the evening, when queues often back up across the bridge and in to Cambridge. Bicycle lanes were only recently extended all the way across the bridge (previously, merge zones at the end were quite dangerous for cyclists) but are still suboptimal for bicycle safety, with storm drains on the right and fast-moving traffic on the left. When not queued, vehicles drive quite fast—especially motorists exiting Storrow Drive who are used to highway speeds (it is possible to drive directly from I-93 to Mass Ave without encountering a traffic light or pedestrian until exiting Storrow)—on the straight, wide roadway.

For traffic traveling westbound, there are neither concurrent walk signals with a green phase nor a “no turn on red” sign, so pedestrians either have to wait for a walk signal which is still often crossed by traffic or walk against the signal, despite through traffic having a green light. (This is an extremely busy pedestrian area.) Without any commercial traffic, this right turn could easily be made more severe with more restrictions (or even rebuilt as a raised crossing to further slow traffic) and priority could be given to pedestrians instead of cars. As for transit, it receives no priority, and there are frequently three or four buses stuck in a queue on the bridge. When this is the case, however, these buses carry more passengers than every other car on the bridge.

The bridge is maintained by MassDOT, with the cities maintaining the approaches at either end. The bridge environment could certainly be improved with better separation for bike lanes, narrower travel lanes to curb speeds, and bus lanes to prioritize transit users crossing the bridge. A more outside-the-box idea would be to cantilever an additional six feet of sidewalk on either side of the span and move the bike lanes to the right side (in both senses) of the crash barrier, allowing five lanes of traffic: through bus lanes and queue space at either end of the bridge. Extending bus lanes in to Boston would be necessary as well. This would require cooperation of both cities and multiple state agencies: certainly a high bar to clear but by no means an impossibility. This post will assume that this is indeed possible.




Memorial Drive to Vassar Street

Crossing the bridge, Mass Ave bisects the campus of MIT. The roadway varies in width but the right-of-way is generally 90 feet, while there are two westbound lanes from Memorial Drive past Albany Street, the eastbound roadway narrows from two lanes to one lane in front of MIT. There are small street trees planted along the curb, but they are overshadowed by the stately oaks on MIT’s campus.

The main actor against a more balanced street here is parking. While there is the need for some short-term parking (or perhaps just pick-up/drop-off space) in this corridor, two-hour parking is by no means the best use of this space. If the average space is used by 15 vehicles per day, the 28 spaces between Memorial Drive and Vassar provide parking for 420 users per day, which is barely 1% of the total throughput of the street, yet it accounts for 16% of the right-of-way. Parking at MIT, while somewhat constrained, is still ample: the institute has parking available on Amherst Street (which it controls), along Vassar Street and in many lots and garages.

The usual fallacy that removing street parking will harm small business doesn’t even ring true unless we consider MIT and it’s $14 billion endowment as a small business. The city would have to work with MIT to reallocate parking, but this should not be a particularly heavy lift, especially since charging for parking on Memorial Drive could allow better turnover and availability in the area. One other displaced user would be the tour buses which park along Mass Ave in front of MIT. These users should not be prioritized but still accommodated, and MIT and the city should work to find off-street parking for these buses (perhaps in the lot adjacent to Mass Ave and Vassar Streets or on Amherst Street) where they will be out of harm’s way.

For westbound traffic coming off of the bridge, the left turn to Memorial Drive could be eliminated, and bus lanes extended across the bridge. Traffic wishing to access Memorial Drive westbound can take a right on to Memorial Drive and use the U-turn to the east to go westbound, a move often called the “Michigan Left” because of the preponderance of its use in the Great Lakes State. The right turn from the bridge to Memorial Drive could be sharpened and perhaps raised to slow vehicles in this high-pedestrian area. Rather than two lanes through campus, through traffic would be funneled in to a single lane, with the left lane reserved solely for buses. The bike lane would be moved to a sidewalk-level lane, which would move cyclists from the “door zone” of parked cars to a safer facility (as is planned for the entire corridor to Central Square). Westbound cyclists would have a specific bike light at the Amherst Street T intersection, which could be set to flashing red during the Amherst portion of the cycle to allow bikes to proceed after yielding to pedestrians since there are no vehicular conflicts.



The large MIT crosswalk could be rebuilt as a raised cross similar to the crosswalk in Kendall Square to slow traffic, although it likely needs to retain a signal due to the higher volumes of vehicle and pedestrian traffic. The bicycle facilities would create a slightly wider roadway and may require a slightly longer light cycle for pedestrians than exists today. Floating bus stops—not a new concept, but rather a direct descendant of streetcar safety islands which were first used in Cambridge in 1922—would be placed to the west of the crosswalk and accessed during the pedestrian phase. Past the bus stop, the left lane’s exclusive use for buses would end and allow left turns to Vassar Street. Approximately four parking/loading spots would be provided on the north side of the roadway.

The Vassar Street intersection will be changed dramatically and discussed in detail below.

Coming east from Vassar Street, a single through vehicle lane will be provided to the left with buses and turns into and out of the MIT bus loop on the right. The separated bicycle facility will run to the right of the bus lane, moving in to the current sidewalk right-of-way before the bus stop. (the right-of-way may need to be widened slightly here with MIT’s cooperation). Coming east crosswalk will serve two purposes, both to allow the passage of pedestrians and to allow the swapping of the bus and general purpose travel lanes. When the bus stop is occupied by a bus, the next cycle will have a transit only phase for eastbound traffic, allowing the bus to proceed diagonally to the left-side bus lane before a green light appears for general purpose traffic (a right-side bus lane could be retained across the bridge, but might not be preferable). Making this switch allows vehicles to move to the right side of the roadway, where several parking or loading spaces are provided, and for the transit vehicles to move to the center lanes for a speedy trip across the bridge. These spaces require some extra road width, but can be attained by moving the cycle track on to the sidewalk, which is quite wide between the crosswalk and Amherst Street; some cooperation between MIT and the City would likely be necessary. (See cross-section B-B.) Between there and the river, three exclusive lanes would be provided for cyclists, motorists and transit. (See cross-section A-A.) Since the bridge is controlled by a separate entity from the rest of the street, side transit lanes could be retained until bus lanes were installed on the bridge of the agencies' schedules didn't match.





Mass Ave and Vassar Street

The acute angle from Mass Ave to Vassar Street requires
trucks to roll up on to the sidewalk—which is often
filled with pedestrians—to make a right turn.
Vassar Street is one of the most complex and quite possibly the most dangerous intersection in the Mass Ave corridor. It has been the location of the death of a cyclist in 2011, and many more close calls. The roads do not cross at a right angle, and there is significant turning traffic. The crosswalks are long and askew, and turning vehicles often block the bike lane only to wait for pedestrians to cross before they are able to make their turn (if they don’t “take initiative” and attempt to weave through the crowds). A short term fix would be to make the right lane of Mass Ave westbound right-turn only, and have a red turn light for most of the signal's cycle, but a green arrow during the exclusive left turn phase on Vassar Street. This would be similar to the setup where at the corner of Granite, Waverly and Brookline streets north of the BU Bridge, and the new phased right turn light on Comm Ave immediately south of the bridge. This would allow safe passage by cyclists and pedestrians during the Mass Ave phase, and an exclusive turn for cars when the street is already blocked. This would require that the eastbound side of Mass Ave become a single through lane (with the left lane for left turns only; this is already the de facto use of that lane) and might require three westbound lanes: a left turn lane, the current through lane, and a right lane for queuing cars waiting for the light. This, however, would preclude the start of the bus lane on the eastbound side of the street, so the tradeoffs would have to be examined.

In the longer run, since Vassar Street is home to Cambridge’s first cycletrack and, if it intersects with a protected bicycle facility on Mass Ave will require a different treatment. (As an earlier iteration of a PBL—in fact, one of the first in the nation—the facility is somewhat substandard, and separation must be extended on Vassar through the Mass Ave intersection. If built today, it would likely look much more like the Western Avenue facility.) This intersection begs for a better a better design. Luckily, there is one: a protected intersection.

Protected intersections are used commonly in Europe (especially in the Netherlands) and the first have recently been installed in the United States. The City of Boston is planning one along Commonwealth Avenue in the area of Boston University. A protected intersection moves cyclists adjacent to crosswalks and creates sharper turns for drivers, decreasing speeds and allowing for better sightlines. In addition, it allows left-turning cyclists to cross the intersection and then take a left, rather than having to merge in and out of traffic. With intersecting PBLs, such a treatment is often required.

This intersection is generally large enough for a PBL, but some modifications to the intersection would need to take place. The east and west corners would have to be extended to provide better bicycle crossings and queueing space. This would require a sharper turn for traffic turning from Mass Ave east to Vassar south, although this is a relatively rare movement. The eastern corner would need to be rebuilt as well, since the current shallow curve does not serve the purposes of a protected intersection to calm traffic and allow better sight lines. This is a more frequently-used movement, and congestion may be exacerbated by this change.

This could be mitigated by eliminating the right turn there altogether and providing more queue space for right turns on to Albany further west, as this post proposes. This intersection is frequently choked by cars attempting to turn from both lanes, with left-turning cars stymied by eastbound traffic and right-turning cars waiting for a constant stream of cyclists and pedestrians. Removing this turn would allow better throughput towards Albany Street, mitigating backups towards Memorial Drive. For most motorists, the extra one or two minutes to access Kendall Square is negligible, and Vassar is a narrow, often congested street. As discussed later in this post, the Albany Street intersection could be reconfigured to better accommodate this traffic.






Vassar Street to Albany Street

The section between Vassar and Albany Streets is unlike any other in the corridor: it has a mid-block railroad crossing of the Grand Junction line. There is minimal queue space between the two streets, and the area is often congested, causing backups through the intersections at peak hour. Other than parking lots and MIT deliveries, there are no abutters requiring access to the street which is bounded by two parking lots, the blank brick wall of a warehouse and a small laboratory which faces on to Albany Street. Even if redeveloped, it will likely never be an opportunity for placemaking with the rail line and delivery corridor running through the center. While this post generally calls for the downsizing of the streetscape, in this case, it calls for additional traffic lanes. By providing a wide roadway in this section, queues would be minimized in adjacent segments and the potential lights at Vassar and Albany to impact each other would be minimized.

This additional space is not free, of course, but the right-of-way here can be widened: the 90-foot right-of-way could easily be widened by ten feet or more on the north side. This assumes that PBLs would be located to the right of the travel lanes. Most likely, this would require a new PBL on the south side of the current roadway to account for two mature trees abutting the road, and moving the northernmost PBL in to the area occupied by the sidewalk and the sidewalk in to unused space and a parking lot owned by MIT. Obviously, MIT’s cooperation here would be required.

For westbound traffic, this would allow two lanes of traffic east of the Grand Junction widening to three beyond. These three lanes would allow an exclusive lane for each turning movement at Albany Street, the busiest single junction east of Central Square during the morning peak hour (and the busiest cross street by total vehicles). Going eastbound, Albany Street splits in to Albany and Portland with no stop sign or other traffic control device, so queuing space is not an issue, traffic entering Albany is unlikely to back up across Mass Ave (in fact, Mass Ave is often the bottleneck itself, and Albany backs up from Mass Ave south towards the BU bridge). The three lanes could be used exclusively for left, straight and right movements to clear traffic out of the short queue from Vassar Street, with the bus stop relocated west across Albany (far-side bus stops are generally preferred). With the right turn at Vassar disallowed, a number of steps could be taken to ease the right at Albany. First, the bike lane would be curved slightly and curb extended to allow for better sightlines between through cyclists and turning vehicles. Second, two lanes could be provided on Albany eastbound towards Portland (at the expense of a few parking spots) to mitigate any queueing issues. (See cross-section F-F.)

Coming eastbound, two lanes would be provided approaching Albany, with the potential for the left lane to be a turn lane with an exclusive phase. These two lanes would continue past a floating bus stop (the bus would stop in the right travel lane, with the cycle facility running to the right of the boarding platform) widening to three past the Grand Junction. This would allow the right lane to serve buses and right turns exclusively (there are only about 15 right turns per hour, or one every three light cycles, so this movement is minimal) with the middle lane for straight traffic and the left lane a queue for left turns, which often have to wait for opposing traffic to clear. With such a lane, an exclusive left turn phase could be provided, as this is an important movement for traffic and for the EZRide shuttle. (See cross-section E-E.)

Albany Street to Sidney Street

West of Albany Street, the corridor becomes much less complex, at least until Lafayette Square. Side streets are narrow and have little traffic, and there are few driveways to preclude the use of a protected bicycle facility on both sides. By moving the bike lanes to the right of the parking, the current layout of the roadway would be largely unchanged with two lanes westbound (where there are sometimes queues which form from Central Square) and one eastbound. Little parking would be lost. (See cross-section H-H.)  This would be one of the easiest portions of the roadway to rebuild since few changes would take place other than protected cycling facilities, and could be done quite quickly to improve conditions for cyclists without major impacts to other users. One change that could be made would be to cut back the corner at Landsdowne and Mass Ave for right-turning traffic. This is the turn made by buses laying over on Franklin Street (and in this plan, more buses would use this layover) and it is a tight, acute turn for buses. If the gas station were bought or taken by the city (a similar gas station taking allowed the repurposing of Lafayette Square), it could be used as a pocket park in addition to providing a better turn radius.




Central Square: 

Sidney Street to Inman Street 

[If you've read my original post on Central Square, this uses a lot of it as its basis. There's some new thinking here and updated graphics, but if you're familiar with that post, you can probably skim over a bit of it.]

Central Square is complex. I often cite it as an example of the difficulties autonomous vehicles will have operating in urban environments; the number of human cues and interactions between the tens of thousands of users of Central Square—most of them not driving—is intense (this is the topic of another post entirely). The complexity and confusion of Central Square is its saving grace: traffic rarely moves fast enough to do much harm. Still, the roadway is often congested, it is no place for a beginner cyclist, vehicles frequently pull across the bike lane or make illegal U-turns, and that doesn’t even get in to the transit users.

Transit on Green Street is frequently blocked by delivery
vehicles. It shouldn't be there in the first place.
Central Square is, at its heart, a transit node. The Red Line below carries more passengers through the Square than all other modes combined, and as many passengers board and alight from the Red Line as vehicles pass through the streets above. It also serves half a dozen MBTA bus routes, and the MASCO shuttle, which collectively carry more than 30,000 passengers per day, with the bus stop on Mass Ave processing dozens of buses per hour. Most other such bus nodes and transfer points in Boston were built with some sort of separated subway-surface transfer facility like Harvard, Lechmere, Ashmont, Kenmore, Ruggles or Forest Hills, and former such facilities at Massachusetts (now Hynes) and the former Egleston station on the Washington Street Elevated. Not Central. Not only are bus passengers served by curbside stops, but some of these stops are along Green Street, a narrow street a block away. A new bus user would have trouble simply finding the bus stop, to say nothing of the luck needed to get a seat on a 70 bus at rush hour. (The geometry of these streets is not conducive to bus operations, notable are the poor “one way” sign at Pearl Street and Green Street, encased in a tube of concrete after too many chance encounters with the CT1 bus making a turn, and the 47 bus, which swings practically in to the opposing traffic lane to make the right turn from Mass Ave to Pearl Street.)

Yet if you look at a cross section of Central Square, it’s mostly used for cars and parking. Despite ample and inexpensive space available in nearby lots and garages, street parking is provided on both sides of the street. (This is the case despite the fact that the majority of users of Central Square likely arrive by foot, bicycle and transit.) The only exception to this is between Pearl Street and Prospect Street, where the curb plays host to a major bus-subway transfer point (and the City still finds curb space for loading zones and taxicabs). But Central Square will not be solved merely by trying to shove more uses through this already congested area unless we take a step back and look beyond Mass Ave, at which point there are some intriguing options.

For most of the length of Mass Ave, there is no useful parallel street. Unlike the grids of many cities, Cambridge’s streets, while mostly straight, run in any number of directions, rarely running parallel for more than a few hundred yards. Many gridded cities—most cities in the United States are built on some sort of grid—use “one way pairs” to better manage traffic (although sometimes to the detriment of the urban form) but the layout of Boston means such a scheme is basically unheard of. Yet, in a small sense, Central may be the exception, and this may provide an interesting solution.

Between Landsdowne Street and Putnam Avenue, Green Street parallels Massachusetts Avenue for just shy of a mile. This distance may not seem particularly impressive, yet it is twice the length of any other street paralleling Mass Ave anywhere along its 16-mile route from Boston to Lexington. The section of Green Street west of Central Square is narrow and residential in character and adding significant traffic there would be difficult politically. However, from Pleasant Street east, there are only a few residences, and the street serves mostly commercial properties, as well as several bus routes. This post will argue that these bus routes should be relocated to Mass Ave to provide better connections and amenities, and that general eastbound traffic on Mass Ave should be relocated to Green Street, which will be reconfigured to run eastbound. While the number of vehicles will increase, hundreds of buses will be removed from the street daily, a sensible tradeoff for the abutters of the street.

This, in a sense, would spread the users of Mass Ave across 140 feet of right-of-way (Green Street and Mass Ave combined), making Green Street an extension of Mass Ave. Westbound traffic would remain as is, and buses would use an exclusive busway through the center of the square, mitigating congestion and allowing passengers to transfer to and from the Red Line adjacent to the bus stops rather than forcing many to use inadequate stops on a side street. Eastbound traffic would be relocated to Green Street, allowing the two streets to serve, for a short distance, as a one-way pair, with the goal not to improve and increase traffic throughput, but to improve transit flows and safety for cyclists and pedestrians.

This can be imagined in several steps. Rather than moving intersection-by-intersection, I’ll detail the entire corridor, since it is being proposed as a major rethinking.

1. Green Street is rerouted to run eastbound. This allows all of the traffic from Mass Ave to be shunted south on Pleasant Street by the Post Office and then left on to Green. (Franklin would probably also be flipped from east to west, which would have the added benefit of eliminating the Franklin/River intersection, which has very poor sight lines.) Green would be two lanes wide, with one lane for through traffic and the other for deliveries and drop-offs and potentially parking between Magazine and Brookline, and turn lanes where necessary. The street is 24 feet wide, which is wide enough for two 12-foot travel lanes. The sidewalks would remain as is, with significantly less use since they would no longer be used for bus stops (the bus stops are frequently so crowded that pedestrians are forced to walk in the street).

Once past Pearl Street, traffic would be able to filter back to Mass Ave. Some traffic would take Brookline Street, mostly to zigzag across to Douglass Street and Bishop Allen. Some traffic destined to Main Street could turn here but most would continue east to Sidney or Landsdowne. At Sidney, signals would be changed to allow a straight-through move on Sidney Extension to Columbia and Main, and there would no longer be a left turn allowed from Mass Ave to Sidney Extension. (This would be the new hazardous materials detour for traffic unable to pass through the downtown tunnels.) Traffic going towards Boston could continue on Green Street as far as Landsdowne, where the diagonal street allows for less severe turns.

Eastbound traffic on Green Street is preferable to rerouting westbound traffic via Bishop Allen, for several reasons. First, it's probably good from a political and practical sense to have some vehicular access to Mass Ave, so only one direction of traffic should be rerouted. Otherwise you wind up with some dead-ended narrow streets abutting the square. Complete streets include cars. They just don't make them the priority. Second, the right turn for through traffic from Mass Ave to Bishop Allen would be very hard to figure out; the Sidney Extension-Main-Columbia turn would be implausible with increased traffic. Douglas Street is only 20 feet wide and is probably too narrow for trucks. Norfolk is 24 feet wide, but then you're creating a busy turn right in the middle of the square.

2. Mass Ave eastbound is rerouted to Green Street. As described above, all traffic from Mass Ave eastbound would be diverted to Green Street at Pleasant. Traffic wishing to turn left on to Prospect would take a right on Pleasant, and a left at Western, which is the current traffic pattern. Light timings would be changed at Western to allow for additional traffic, although they are already optimized for north-south traffic, which is significantly higher than east-west traffic on Mass Ave. The current right-turn lane from Prospect to Mass Ave would be repurposed as a bus-only lane. Mass Ave westbound would remain mostly is.

3. A two-way busway would be built on the south side of Central Square from Pleasant to Sidney. Eastbound buses would be exempt from the turn to at Pleasant to access Green Street and instead proceed directly down Mass Ave. East of Pearl Street, this busway would allow for some general traffic: right turns from Brookline Street to Mass Ave and left turns from Mass Ave to Pearl. (See cross-section K-K.) The busway would also allow emergency vehicles (including from the nearby firehouse) to bypass gridlock in Central Square, creating BRT elements in one of the most congested areas of the 1 bus route (as opposed to, say, the Silver Line in Roxbury, which has bus lanes on the least congested part of the route but in mixed traffic in the most congested areas). Bus stops would be consolidated between Pearl and Essex for both better access to the Red Line and to ease confusion about which buses stop in which stops: with the exception of the rush-hour 64 bus extension to Kendall, all buses would stop in the same location. This 160-foot long section could accommodate four 40-foot buses at the same time. (See cross-section L-L.)

Since Central is a terminal for most routes, buses are required to turn around, and would be able to loop as follows:
  • 1 is a through route. The CT1, which should be consolidated in to the 1 bus since recent stop elimination have made the routes mostly redundant, could loop via Pleasant-Green-Western.
  • 47 would go left from Brookline to the busway. Its loop and layover would be made via Pleasant-Green-Western. A single-bus layover would be retained at the end of Magazine Street. This would eliminate the need for passengers to walk a block to transfer.
  • 64, when not operating through to Kendall, would loop via University Park, but instead of serving stops on Green Street, it would loop back to the busway. Left turns would be allowed for buses from the Mass Ave busway to Western.
  • 70/70A would loop via University Park as above, making inbound and outbound stops on Mass Ave, eliminating the walk to Green Street and the inadequate boarding facilities there
  • 83 and 91 would use a left-turn lane for buses only on Prospect Street (this is currently a painted median; the 30-foot-wide street would allow a bus lane here) to allow access to the busway. An actuated signal there would allow a left turn phase when necessary (approximately ten seconds every ten minutes, which would have a negligible effect on other traffic). Buses would then loop and layover in University Park like the 70. This would allow these routes to serve the growing University Park area, which has seen significant redevelopment in recent years. 

4. Eastbound bus stops would remain largely where they are on the south side of Mass Ave, but any pull-ins and bulb-outs would be removed to allow vehicles to maneuver more freely. (The additinal crossing distance would be mitigated by the bus platform mid-street; see cross-section L-L.) Westbound bus stops would be placed in the center of the roadway; one between Pearl and Essex (approximately 160 feet long) and another east of Sidney Street (60' long, for the 1 Bus only; more on the Sidney Street intersection later on, see cross-section I-I), where those buses (and general traffic turning left on Sidney and Pearl streets) would be shunted to the left of the floating bus stops. These stops would be ten feet wide at Pearl Street and eight at Sidney, significantly wider than the current stops on Green Street, and built with modern amenities and shelters. The 1600 square foot bus stop at Pearl Street would provide waiting space for 400 to 500 passengers at three to four square feet per passenger (see MBTA crowding policy). Pedestrians transferring between the Red Line and westbound buses would have to cross just the westbound traffic lanes of Mass Ave, no longer making the trek to and from Green Street. West of Essex Street, the bus lanes would jog to the right to allow clearance between the head house and elevator for the main entrance to the Central Square station. (See cross-section M-M.) The bus platform—which could be raised to allow level boarding akin to the Loop Link in Chicago—would span the distance between the Pearl and Essex crosswalks, allowing access from both ends of the platform. (The sidewalk/bus platform for eastbound buses would also be raised to allow level boarding.) The MASCO shuttle would also use this corridor.

5. In between the westbound bus stop and the westbound traffic would be a 10- to 12-foot-wide center-running protected bicycle lane, running from Sidney to Inman. Except where adjacent to the firehouse, it would be raised above grade and separated from traffic; most minor cross streets would allow only right turns to and from Mass Ave. At either end, a separate bicycle signal phase would allow cyclists to move from existing bicycle facilities to the center of the roadway (more on this in subsequent section). This would eliminate the constant conflicts between cyclists, motorists and buses. Bicycle traffic calming measures would be required in the vicinity of the bus stop at Pearl Street with high pedestrian traffic, but cyclists would otherwise have an unobstructed trip from Sidney to Inman (with traffic lights at Brookline and Prospect, where a bicycle phase or two-stage turn boxes might be necessary for right turns). For turns to Prospect and Western, bike boxes would be provided to allow two-stage turns. For turns to minor streets, cyclists could use areas adjacent to crosswalks to move between the PBL and the curb. Since bike lanes in Central Square are frequently blocked by vehicles, this would wholly eliminate these issues.

Why not side-of-street PBLs, which are generally considered to be best practice? A few reasons:
  • Red Line head houses. If it weren't for the location of the Red Line head houses, it would probably make more sense to have side bike lanes, but we should assume that the Red Line infrastructure are immovable and constrain the width of the street in this area.
  • Right turns. While turns from the bike lane to adjacent streets are somewhat more difficult for cyclists, putting the bicycle facility in the center of the roadway eliminates right-hook turn hazards. 
  • Bus-Subway transfer passengers. Since Central is one of the busiest bus-subway transfers in the MBTA system without an off-street facility, it requires large bus stops to accommodate passengers (the current stops are grossly inadequate). To accomplish this, it would need to pull the cyclists far back from the street, which would create more severe turns to allow the cyclists to clear the head houses on one side and the bus stops on the other. Since the eastbound stop is busier for waiting passengers—handling boardings for the 1, CT1 and 47, which at peak times account for a full busload of passengers every three minutes—floating it would require a larger bus stop than the westbound stop (which, at peak boarding times, only serves the 70, 83 and 91, and a few 1 bus passengers traveling from Central towards Harvard). Integrating the eastbound stop with the sidewalk allows for more overflow.
  • Pedestrian traffic, especially between the buses and the subway. A successful PBL would need significant separation from the sidewalks to avoid becoming choked with pedestrians. In high-pedestrian areas, this is easier to accomplish in the middle of the road than it would be alongside the sidewalks; since this proposal separates the eastbound bus stop from the bicycle facility. Passengers moving between the outbound Red Line and 70, 83 and 91 buses will have to board at a station adjacent to the PBL, but there are fewer of these passengers than those waiting for the 1, 47 and CT1 in the morning. 
  • The busway creates the need for a buffer between the westbound travel lane and the buses, which is a good place for the cyclists; with side-running lanes it would require additional buffer space on each side. It does create two points of conflict on either end of the PBL to transition from the existing lanes (which are already at signalized intersections, so it would require only a short additional phase) but otherwise have relatively clear sailing for cyclists devoid of the current maze of turn lanes, parking spaces and taxi stands. 
  • Finally, side-of-street bicycle facilities would mostly preclude the use of curb space for vehicles, which is necessary for loading, pick-up and drop-off zones in Central Square.
It's worth noting that there were similar challenges in placing bicycle lanes near North Station, with extremely high pedestrian activity, as well as bus and shuttle drop off areas, and the solution there was similar: to put the bicycling facility in the center of the street. There are even lights now in operation which allow cyclists to cross from a side-of-street facility to the center, much the same as would be required in Central.

The bicycle facility could be placed on an adjacent street, but this would be both a practical and optical detriment of cyclists. As a practical matter, it would require cyclists to take a longer and less attractive route, causing cyclists to use other modes. It would also make it harder for cyclists to reach the businesses in Central Square, which do not generally front on to Bishop Allen or Green streets. From an optics standpoint, it would once again show that the street was designed first for motorists, with cyclists an afterthought. In any case, many cyclists would ignore lanes on a parallel street leading them to travel in shared vehicular lanes in Central, which would solve little.

Beyond Green Street and Bishop Allen, there are few if any parallel streets to accommodate cyclists. The nearest such street is Broadway, which runs from Harvard Square to Kendall, which would require cyclists destined for the Harvard Bridge to detour to the point that most cyclists would likely vote with their feet and stay on Mass Ave, even if it were more dangerous. Other streets, such as Broadway, also traverse more residential areas, with many more driveways and which would require the removal of significant residential parking to install bicycle facilities, a bit third rail of Cambridge politics.

6. The westbound lanes of Mass Ave would be 20 to 24 feet wide, allowing the current travel lane as well as a wide area for a loading zone for area businesses, a taxi stand and other pick-ups and drop-offs near the transit station and, in places, a wider sidewalk. (This is also a width required by the fire department.) These uses would no longer conflict with bicycle traffic in an adjacent lane. Some street parking could be provided, but it is probably best relegated to side streets nearby or parking lots (there are generally few on-street spots today). It is important to provide loading zones, as the businesses in the area do need service from suppliers which often have little choice but to use the bike lanes to load and unload today. Separating the bike lanes, and providing specific loading facilities, will remove this as an issue.








N.B.: there is no way to show headhouses in Streetmix, so the information signs are used instead.







Central Square Signals:

Mass Ave and Sidney

The two intersections at either end of the treated area will both need to be reconfigured and retimed to allow traffic throughput as well as transition cyclists and buses between in and out of the mid-street bike facility and busway. The intersection at Sidney Street was rebuilt in the late 2000s and despite its complexity, it by-and-large works. The best feature of the intersection isn’t even the roadway itself but the adjacent plaza, Jill Brown-Rhone park. What was once a sea of asphalt and a gas station is now one of the best-used parks in the city. From frequent dances, bands and the omnipresent consumers of Toscanini’s ice cream (currently relocated to East Cambridge for the redevelopment of its building), the park is a testament to what can come from the reappropriation street space for a different use.

Currently, the Mass Ave and Sidney intersection has three light phases, one for traffic going straight on Mass Ave, a second for traffic going straight on Sidney and a third of left turns from Mass Ave east to Sidney Extension and Mass Ave west to Sidney, and corresponding right turns (the right turn from Sidney north to Mass Ave east is the only movement allowed from Sidney). These phases are coordinated with the light at Main, Sidney Extension and Columbia to mitigate queueing on the short piece of Sidney Extension. These phases would have to change to allow for a bicycle cycle to move cyclists between the right-side PBLs to the east of Sidney and the center PBLs to the west. This phase could be quite short—perhaps only 10 or 15 seconds—as many cyclists can cross the intersection in a few seconds. At the same time, cyclists from Mass Ave could make turns on to Sidney Street, and the right turn from Sidney Extension to Mass Ave west could be allowed for motorists.The proposed phases are as follows as a 75 second cycle:
  1. Straight-through vehicular traffic on Mass Ave and Main Street, broken in to three streams by the floating bus stop (westbound traffic, buses and Pearl Street turns, eastbound traffic). Concurrent walk signals on Mass Ave, with right and left turns allowed (turn traffic is relatively low). The only restricted turn would be the left from Mass Ave east to Sidney Extension, which would not be allowed at any time (traffic from Mass Ave to Main or Columbia would mostly be on Green Street and could use the straight-through move on Sidney). This phase would last about 25 seconds
  2. Straight-through vehicular traffic on Sidney Street. The current vehicle-bike-vehicle lane on Sidney Extension south would be retained, but the right side bike lane would be eliminated and cyclists would be allowed to continue straight on Main and cross the plaza in a designated area. (More information about this below.) Unprotected turns would be allowed between Sidney and Mass Ave with concurrent walk signals. Main Street westbound would also have a straight signal on to Columbia. This phase would probably last about 25 seconds.
  3. The bicycle phase on Mass Ave would allow cyclists to move between the side PBLs and the center PBL on Mass Ave. Concurrent walk signals east and west on Mass Ave. To clear traffic from Sidney Extension queued from phase 2, a left turn from Sidney to Columbia would be signaled, and a right turn across an active sidewalk (this is currently the phasing structure). Adjacent right turns from Columbia to Sidney Extension would also be permitted. This short signal would be only long enough to clear any queues from Sidney on to Main/Columbia, probably only about 10 seconds.
  4. A fourth phase would be necessary to provide a crossing of Columbia west of Sidney Extension. At 3.5 feet per second this would require 13 seconds of crossing time. The bicycle crossing on Mass Ave would remain active, as would the crosswalks in Phase 3. At 15 seconds, this would provide a combined phase of about 25 seconds.





Perhaps the trickiest current movement at Lafayette Square is the left-right movement for a cyclist from Main Street to Mass Ave. Thanks to a citizen request (guess which citizen), a bike box was installed at the end of Main Street to allow a cyclist to move in front of traffic and prepare for the turn; otherwise a cyclist is required to take a left across a stream of traffic. The cyclist then uses the right hand turn lane to make a sharp, sweeping turn on to Mass Ave, often with car traffic immediately to the left. This could be reworked by allowing cyclists to proceed straight on Main Street and across the plaza (a shared roadway here could also accommodate fire apparatus pulling out of the firehouse and, in the long term, buses from Mass Ave to Main Street if the 70 were ever extended to Kendall Square, as some plans propose).

A bike crosswalk would have to be installed adjacent to the crosswalk across Columbia to allow cyclists to make this maneuver (non-standard, but not-unprecedented and doable in this context), as well as adjacent to the crosswalk to the PBL at the west end of the plaza. It could be coupled with a limited-use lane for firetrucks to cross over the park area in emergencies, but would otherwise be a shared space. Some cyclist calming would be in order as well (ramps would help this) as this is a high pedestrian area. There is a similar facility with a bicycle-only crossing of a sidewalk at the corner of Concord and Garden streets west of Harvard Square. Here, this would allow cyclists to take a safer, more direct route, and also allow a green light for vehicles during part of the bicycle phase at Mass and Sidney to clear out right-turning queues on Sidney Extension.

Mass Ave and Inman/Pleasant

The other end of the treated area is a bit more congested than Lafayette Square, with all traffic on Mass Ave taking a right on Pleasant and Inman feeding across to Pleasant as well. However, the signal phasing is much easier than at Mass and Sidney. The current phase has a straight movement for Mass Ave, a turning movement for Inman Street in both directions and an all-walk signal for the crosswalks. This would largely stay the same, with a couple of added signals and phases. This is planned for approximately 90 seconds.
  1. Inman southbound right and left. All vehicles southbound on Inman going left would be forced to turn right on to Pleasant. If Pleasant were striped with two parallel lanes (at 25 feet wide, it is plenty wide enough, but would require removing four parking spots) this would allow traffic to turn concurrently from Mass Ave west and Mass Ave east on to Pleasant. This adds a signal for the current unsignaled turn from Mass Ave west to Pleasant Street south. (20 seconds)
  2. Bicycle phase between the side-PBLs and the center PBL. During this phase, buses could also turn left from the busway on to Pleasant Street. This is required for the 47 and CT1 buses. (20 seconds)
  3. Walk phase for all crosswalks. At this time, westbound buses (1 and MASCO) would cross diagonally from the westbound busway to the eastbound travel lane, but then wait at the crosswalk for the next phase, a queue jump to allow them to leave the busway ahead of adjacent westbound traffic. (20 seconds)
  4. Westbound and eastbound traffic on Mass Ave. Eastbound traffic would turn right, except for buses which would continue straight in to the busway. (30 seconds)
  5. This actuated phase would allow a bus arriving during phase 4 to make the diagonal crossing and continue through the light, while still allowing eastbound traffic to make the turn on to Pleasant Street. (10 seconds, borrowed from Phase 4, if actuated).





There is potential for reduced throughput at this intersection and would have to be modeled—especially on Mass Ave—but it already has lower traffic than areas to the east. Two lanes are provided westbound because of this reduced capacity. It may be necessary at this location—and at Pearl Street—to install a gate to minimize the number of errant drivers in the busway, although the bus layover at Magazine Street and Green Street is seldom-if-ever used by vehicles as a straight-through move from Magazine to Prospect.

Other Intersections

There would also be changes to other intersections along the corridor. Western and Prospect would remain mostly unchanged, although buses would be allowed to make the left turn on to Western for the trip west. There would be the addition of the short bus-only left turn lane from Prospect to Central Square for the 83 and 91 buses, this would be actuated by the buses and would only require one ten-second cycle approximately every ten minutes, less than 2% of the overall throughput of the intersection. The only other street which would allow access across the PBL would be Brookline Street, which would otherwise remain unchanged. Finally, the left turn from Mass Ave to Pearl Street, which is currently an unsignaled turn from an exclusive turn lane, would remain unsignaled, with cars turning left and buses continuing straight. Depending on compliance, a gate may be necessary to keep cars out of the busway (although enforcement by Cambridge and Transit police may keep drivers from erring, some drivers unfamiliar with the area may follow a bus in to the busway despite any number of signs).

Green Street would have to be resignaled as well. The current intersection at Western/River/Magazine may become less complex, as traffic which currently has to merge out of Magazine and Green with a very short queue before the light would be turned. Pearl and Green streets would remain a four-way stop, and four-way stops or signals may be required at the Green Street crossings of Brookline and Sidney due to increased traffic. However, several intersections on Mass Ave in Central Square currently operate without signals, and this may be possible on Green Street as well.

Implementation Strategies

The sorts of changes proposed here would be a sea change for Mass Ave in Cambridge, and would likely have both broad support and broad opposition. Unfortunately, Cambridge frequently bows to opposition (and any sort of change), such as reneging on bicycle facilities on Pearl Street because of a few complaints about parking spaces. It would thus be important to work with transit and bicycling groups as well as business and community stakeholders to build a coalition of support for this sort of project before implementation. Working with other stakeholders would be imperative as well. MIT controls much the property on both sides of the corridor east of Sidney Street and while it should, in theory, be in the Institute’s best interest to promote safer and more efficient traffic, they must be involved from the start. MIT would lose about three quarters of the parking in front of the main entrance at 77 Mass Ave, but considering the mode share of visitors to campus (the majority coming by foot, bicycle or transit) it is anachronous to have most of the space in front of the campus devoted to a few parked cars.

The most drastic changes, however, take place in Central Square. Rather than a single owner, the Square is home to many businesses, large and small, and some would certainly bemoan the loss of a single parking space in front of their business. (This is despite the fact that businesses regularly overestimate the number of customers arriving by car and underestimate other modes.) A concerted effort would be required to assure businesses that deliveries could still be made (by designating convenient loading zones on Mass Ave and adjacent streets) and that patrons could still arrive by car, but that nearby parking lots and the Green Street garage would be a better option. The City could even promote use of the garage during construction with short-term discounts for parking there. Working with City staff, committees and the City Council would be important to put forth a united front for improving Mass Ave in general and Central Square in particular.

The hardest of these groups to organize will be transit users. While pedestrian and cycling advocates have longstanding interest groups and city committees, the City’s transit committee is much younger, as are groups such as TransitMatters and LivableStreets representing the interests of transit users. Meeting with those groups and selling the idea of a signature infrastructure improvement in Cambridge prior to public plans would allow for mobilization of transit users interested in a better experience, rather than letting the conversation get hijacked by parking interests as is so often the case.

Finally, the City should view this as an opportunity, not a threat. In 2015, the organization People for Bikes named the Western Avenue Cycle Track the best new cycling infrastructure in the country, despite the objections of some City Councilors, who worried that narrowing the street would cause increased traffic congestion (it has not). Western Avenue should be a blueprint for Cambridge, and rebuilding Mass Ave would be a connecting piece of infrastructure on a grander scale. If Western Avenue was named the top new cycling infrastructure in the country, imagine what the impact of a forward-thinking, transit-bicycle-pedestrian priority Mass Ave as a showpiece of the future of Cambridge in the 21st Century.