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.

Friday, March 9, 2018

The Boring Company? More like The Infeasible Company

I should start a series on completely infeasible plans. Elon Musk's tweet today about the boring company prioritizing bicycles and pedestrians shows just how completely outlandish his car-skate tunnel proposal is. Yonah (yes, we are on a first name basis, thank you) has a good Twitter thread about how point-to-point transit systems are inherently inefficient and are basically just what we have for cars. But the video brings up some technical issues showing why the proposal to go everywhere fast actually goes nowhere fast.

Acceleration/Deceleration Tunnel Length

Let's assume for a moment that Musk is able to bring down the cost of tunneling by a factor of 10 (a heady assumption which Alon doesn't believe). According to his own FAQ, this would bring the cost of tunneling to about $100 million per mile. Which would be relatively impressive, although Seattle manages to build tunnels for $300 million per mile, including systems (track, electrification, stations, etc). So how much is he proposing to tunnel? Further down his thread, he says he'd have thousands of small-stations designed to bring you close to your destination, and that each would be the size of a parking spot. That's the size of the station on the surface. What's more important, and more expensive, is the size of the station underground.

His plan is to have the car skate slot cars (which, I'll point out, don't exactly exist) travel at a speed of 125 mph. There will be trunk lines which will ferry a steady stream of cars at this speed. But to gain any efficiency in these trunks, car-skates will have to accelerate to speed before they can merge in to traffic, much like a freeway has long ramps to let cars accelerate to speed to merge in. Of course, highway merges and acceleration zones are generally designed for 60 or 70 mph, and design guidelines are up to 2000 feet.

How long would the car-skate acceleration zones be? Well, let's assume an acceleration speed of 10 miles per hour per second. This is equivalent to zero to 60 in six seconds: not quite the acceleration of a Tesla, but quite fast (about 0.5 G): a speed at which you definitely wouldn't want standees (subway trains max out at about 3 mph/s for this reason). But assuming everyone is seated, the top potential acceleration may be faster, but a margin for error may be needed to move in to a gap in traffic (like when you enter a freeway, you don't just gun your engine to top speed, you match the speed of other traffic and then move in to an open spot). If you start from a dead stop and accelerate to 125 miles per hour, you'll cover about 1/4 miles before you're at top speed. (This is a linear relationship, so if you did limit it to 3 mph/s, you'd be tripling the length of the acceleration tunnels.)

So take that as the length of tunnel required to depart each station. And double it. Because you have to decelerate at a similar rate from the other direction. So now you have to build 1000 stations each with half a mile of tunnel just to arrive and depart before you've built a single mile of main line tunnel. That 500 miles of tunnel or, by Musk's rosy calculations, $50 billion dollars. It increases the size of each station by a factor of 100—at least—and increases the size where it's most expensive to build: underground. Theoretically, a single deceleration zone could serve multiple stations: car-skates could slow down off a trunk line and then proceed at a slower speed to the final car-skate elevator (every time I write this sentence I chuckle at the outlandishness, and also Mitt Romney). But then you're building just as many access tunnels (although maybe you keep your mainline tunnel costs down but just making the trip times longer). Or you could decelerate on the main line, but then you may slow cars behind you. (As we'll see later, though, the number of cars in the system is not the rate limiting factor, so this might be attainable and save a bit of time. However, the movie does not show this.)

Ability to Serve Multiple Locations

Take another look at the video. The car sits in a plaza, people get in to the car, the car descends down some sort of elevator and then it reaches the slot car stage and accelerates away. The elevator must use hydraulics, because there's nowhere for the pulleys for a counterweight to hide above ground. Hydraulic elevators don't require overhead equipment, but they're also not very fast, running at a maximum of 200 feet per minute, although existing car elevators are really slow (and given the size and complexity of the elevator shown here, even 100 fpm seems quite fast). To clear utilities and other existing infrastructure and keep construction costs down, these tunnels will likely be at least 50 feet underground, so that's a minimum of 30 seconds of elevator time, but probably closer to a minute. Then the car-skate has to leave the elevator, another car-skate has to come on to it, and then after going up, the people have to get on and off. So they cycle time of a single trip at each station will be about two minutes, maybe 1:30 at best, if the elevator is fast and no one holds the door for their late-running friend.

If we assume two minutes, that means that a maximum of 30 car-skates per hour can serve each station. So while Musk promises that you'll be able to get to any number of 1000 stations, in reality, you'll only be able to get to about 30 within any hour, and only one every two minutes. Let's assume you want service to your destination within 10 minutes: on one of the next five car-skates to depart. There would be a 1-in-200 chance that a car-skate would be going your way. Even if there were five car-skates departing simultaneously from each station, your chances would be pretty slim. And that would drive up the costs of building the system in the first place; no longer would it be "just one parking spot."

Capacity


Which brings us to capacity. The car-skate Musk shows has a capacity of maybe six people, since it's the size of a parking space. We already calculated that a single space can provide about 30 trips per hour, so 180 people per space, if you can fill every origin-destination to perfect capacity. That's a big if, and assumes that every time you drop off six people, you're picking up six more. The problem is that traffic does not flow perfectly bidirectionally, which is why a freeway may have gridlock in one direction and free-flow in another, or why a bus may be packed full running towards the city in the morning but empty going out. (As a more extreme example: half an hour before a Dodger game, you'd have a lot of demand to get to Chavez Ravine, but not much leaving.)

You'd be lucky to get half of this theoretical maximum, so it's probably more like 100 people per space. With 1000 stations, that means you'd have a maximum capacity of about 100,000 people per hour. That's actually pretty high, although on par with a medium-sized subway system; Chicago, for instance, has 1460 subway cars each capable of holding about 80 passengers, or about 120,000 people at any given time. (Musk's trip times would be shorter, so the rate limiting factor would not be how many people he could move through the system, but how he could get them in and out.) This, of course, assumes a balanced load, i.e. that every space would have similar numbers of people going up and down at all times of day, which isn't exactly the case. So you'd have a lot of full downward trips in residential areas in the morning, but once people got off downtown, the car-skate elevators would be empty going down for their next trip.

But remember our costs! Just building the station access tunnels would cost $50 billion. So to serve a CTA-level of ridership (half a million daily passengers) you'd need to spend $100,000 per rider in capital costs. Plus, these costs don't scale: to double the number of riders you'd have to double the number of access tunnels (or, perhaps more expensively, build more car-skate elevators). You haven't even built a single mile of main travel tunnel (or anything else) and you already have the largest single construction project in history.

Merging Tunnel Boring Machines

Let's say you solve the $50 billion dollar question above (good luck). Now you're ready to build your system. Put those TBMs in the ground and go! Not so fast. Tunnel boring machines don't exactly merge well. Go back and watch Musk's video. Once the car-skate accelerates to speed, it then merges in to the existing tunnel. But that's not how TBMs work. When you run a TBM, you build a pit to put it in the ground, dig a tunnel, break through, and pull it out of a separate extraction pit at the end. (In the case of the Chunnel, two of the TBMs were just aimed down and left in place, with the tunnel completed above them.) But connecting two tunnels isn't easy or cheap, you have to basically do it by hand: the connection and egress tunnels for the Chunnel were an engineering challenge.

Now, imagine two tunnels merging. TBMs are designed to leave a round, sealed tunnel behind them. But to merge tunnels, you'd have to merge to almost-parallel tubes. So for a long distance, several hundred feet if not longer, you'd have to cut open the side of one TBM and the allow the other to cut merging in to it, or to hand-dig or hand-mine the entire length (this might not be too bad with hard material, but in clay, sand, mud or anything beyond hard rock it's, uh, not easy). That drives up costs exponentially. And you'd have to do this for every single station. So remember our $50 billion number? It might have an extra zero on the end by the time all is said and done.

The video shows car-skates zooming through an open cavern with supports in between the tunnels. Maybe this is shown for effect. But in reality, this kind of infrastructure can't be built. It certainly can't be built with tunnel boring machines, and would probably be impossible without razing the entire city and starting anew. And while tunnels may be relatively safe during earthquakes (he's starting this in LA, after all), jacking the entire city up on to supports probably wouldn't pass muster.

Other Tunnel Costs

So far, we've addressed the cost to build the acceleration and deceleration tunnels to get people in and out of Musk's system and arrived at a cost of $100 billion (I'm doubling the $50 billion cost, and I think that's more than generous) to serve a moderately-sized city. Of course, there are a few other costs involved. First, you need the trunk line tunnels, and because you have to be able to get from any one tunnel to any other tunnel, you'll need a lot of them, a lot of merges, and a lot of ramps between them. You'll need either long, gradually curved tunnels to connect them (because at 125 mph, you can't go around sharp curves, you'd need about a half mile curve radius to keep G forces at comfortable levels) or lots of deceleration and acceleration zones to slow down and make sharper curves (which require many more merges which aren't cheap). In a subway, changing from one direction to another is easy, either the whole train slows down and goes through a junction and around a curve, or people get off of one train, go down a flight of stairs, and get on to another. When you have to create a system with dozens of tunnels all linked together, it gets a bit trickier.

And that's just what's underground. You also need 1000 stations above ground. Back to the video, note that the car-skate itself is about the size of a parking space, but there's also a plaza with people milling about. You can't build either of these easily in an existing right-of-way, because existing rights-of-way are home to utilities underground which make digging down difficult and costly. So to save money, you'd have to buy several hundred square feet of property all over the city. You also need to build emergency egress locations (subways have these quite frequently), ventilation shafts, fire suppression systems and the like. None of these is huge, but you need a lot of them: 1000 stations, and probably as many vent shafts and stairwells and the like. Each would have property acquisition costs, construction costs, permitting issues, utility relocations, and certainly unforeseen complications.

More stations = more cost

Our example has 1000 stations, but is this enough? A city like Boston or Chicago has about 10,000 people per square mile; New York has more,  LA has fewer. Even so, this would mean interconnecting 100 square miles with stations and tubes. If you have 1000 stations in 100 square miles, you'd have about a 31-by-31 grid, or a station about every third of a mile. This would provide good accessibility: putting everyone within about a 7 or 8 minute walk of a station. Of course, it wouldn't be appreciably better than, say, Chicago's gridded bus network, and the cost would be somewhat higher. Plus, in dense areas you'd need more stations because of the limited capacity for each of about 100 passengers per hour, but you'd still have to build the same density further out to keep it in a short walking distance from most homes.

But that's only one million people. Consider Los Angeles: 12 million people in 1600 square miles. To serve Los Angeles, you'd need to build a system 16 times larger than we've calculated. 16,000 station access tubes alone would cost $1.6 trillion. The rest of the infrastructure would probably double that (add in engineering costs, repair depots, etc., and it probably goes higher). So to build this level of infrastructure in LA would be $3 trillion or more, or $250,000 per person. That's one sixth of the GDP of the US, four times LA's annual GDP, and at a per-person rate, five times the per capita income.

But, yeah, the video sure looks cool.

Monday, January 22, 2018

Optimizing traffic on Storrow Drive

Personal Strava heat map via here.
While it may not be news to many regular readers, in addition to riding bikes and transit advocacy, I dabble in running. Living in Cambridge, one of my regular routes is along the Charles River. According to Strava, I’ve run the section between the BU footbridge and the Harvard Bridge 132 times although this is certainly an under-count due to both GPS issues as well as times when I didn’t run Strava (contrary to public belief, if it isn’t on Strava it is still possible that it did happen). Long story, short: I run along Storrow Drive a lot.

And I’ve noticed something as I navigate the narrow section of path above the buried Muddy River: the lane allocation westbound in the area of the Bowker Overpass is not optimal. As a narrative, proceeding west from Mass Ave:
  • 3 lanes passing under the Harvard Bridge
  • These split in to two 2-lane "barrels", one feeds Kenmore/Fenway, immediately splitting in to two lanes on to the Bowker Overpass and one to Beacon St, the other feeds two lanes west along Storrow Drive.
  • This second barrel is then met by the flyover from the Bowker Overpass, which is, in turn, fed by two lanes from the Bowker and one lane from Beacon St.
  • This ramp merges down to one lane, and then merges in to the Storrow Drive mainline, with a very short merge area (the signs, in fact, say “no merge area”) with poor sight lines as the merge is on the concave inside of a curve.
No Merge Area = No good.
It is this last section which is worst. If you attempt to enter Storrow Drive from Beacon Street, you have to merge in to:
  1. the two-lane Bowker ramp
  2. then merge from two lanes to one on the Bowker Ramp and 
  3. then merge on to Storrow Drive
all within a span of 900 feet. The final merge is on to Storrow Drive with poor sight lines, high traffic speed, and no merge area. None of this is good. If these ramps were rationalized, however, these three merges could be replaced by a single merge, including the worst bottleneck at the entrance from Charlesgate to Storrow Drive, going from a dangerous merge to a continuous stream of travel. The state did this circa 2009 (you can see it on HistoricAerials here) but apparently didn't change enough of the signage, which caused confusion further back, and some people complained, and rather than trying to make it work, they gave up. Old habits die hard. But we should make an effort to change them, rather than revert back to dangerous, inefficient roadways. The road was restriped to its current condition in 2011. There's no word from the Universal Hubbian masses that it got appreciably better then: people probably got used to it, but it was too late.

This time, let's not give up. Let's get some data. Mine is anecdotal and circumstantial: anecdotal because when I observe the area there always seem to be more drivers exiting Storrow Drive to Charlesgate than continuing west and circumstantial because proceeding west on Storrow, the next exit point is at River Street, so there is relatively little reason to get on Storrow rather than to take the Turnpike (except, perhaps, to avoid a toll). So rather than splitting in to four, the three lanes under the Harvard Bridge could feed in to three separate lanes going to Fenway via Charlesgate, Beacon St and west on Storrow. The ramp from Charlesgate would then maintain a single lane on to the overpass, which would eliminate a further merge. So we need these data.

Now, here's some real data. In the morning peak hour, 3400 vehicles per hour approach the ramp to Charlesgate. 2100 take the ramp, 1300 stay on Storrow, and 800 enter Storrow from Charlesgate. In the evening, 2000 take the ramp, and 2250 stay on Storrow, then joined by 1300 from Charlesgate. So the pinchpoint may be whether a single lane is able to handle 2250 vehicles; a quick spot count on a Thursday night in December showed about 2000 vehicles per hour during this peak time. This may well be a tight fit. But there are certainly single-lane ramps that handle more traffic (the ramp from 95 north to 128 north, for example). By observing the traffic flow, it is apparent that when Charlesgate backs up (not infrequent on normal days, to say nothing of evenings with Red Sox games), the left two lanes become de facto off-ramp lanes, with only the right lane open for through traffic. Codifying this would make the system safer and more efficient.

Here is the layout of the current ramps at Charlesgate, with orange areas showing the current merges, and yellow areas showing "sorting" areas where drivers have to choose the required lane. The proposal would simplify this, since each lane would lead to a specific destination, and signage could be improved. (This sign not only doesn't accurately represent reality—the two right lanes both lead to Newton and Arlington—but it's far too late for an errant driver to safely correct course. The next sign back has the same images, but slightly different, if somewhat more correct, information. Let's ignore for a moment the tiny, white-on-blue destination sign no one could reasonably expect to read at 40 mph. If changed, the signs on the Harvard Bridge could read
 Fenway    Kenmore Sq    Newton/Arlington 
above each lane.)



Here is the proposal:



Note that three of the four major merges in Storrow-Charlesgate complex disappear. Just by repainting lines on the road (and likely some physical chicanes to keep Boston Drivers from creating two lanes where they shouldn’t) we can decrease the number of merges by 75%. The one merge left occurs on the longest, straightest portion of the entire complex, and on low-speed ramps, with about 500 feet to merge: three times longer than the merge area when the ramp enters Storrow Drive. And other than signage and paint, there would be no infrastructure costs associated with this sort of project.

Why would a transit-bike advocate like me care about cars? Two reasons. First of all, system efficiency. This is a clear example of where some minor changes could be implemented to create a safer system with less friction, less idling, and less pollution. But the second is that this could be used to improve conditions for bicyclists and pedestrians. Why? Because maintaining the two lanes of Storrow Drive require a pinch point on the Paul Dudley White Path where it narrows from a width of 10 to 12 feet down to 8. If this portion of Storrow were narrowed to a single lane, it would provide plenty of room to widen the bike path and provide a better experience here for cyclists and pedestrians.

Should this be the end state of these ramps? Certainly not. Once the Longfellow is completed, the accident-waiting-to-happen ramp from Storrow to Mass Ave will be rendered redundant and should be closed to eliminate the crossing of the busy sidewalk and bike lane there. In the medium term, Peter Furth makes a strong case that surface roadways could probably handle the traffic, which would be cheaper to build and maintain (the current bridge structures date to the 1960s and are functionally obsolete). In the long run, Storrow Drive and the Charlesgate complex act as mainly as a last-mile distributor from the suburbs to urban job centers. The roads are "necessary" because we don't have a functional transit system to allow easy travel between the north and south sides of the city (especially between the northern portion of Boston and the Longwood Medical Area complex). With a regional rail connection coupled with congestion-based road pricing (other than political obstinacy, there's little to keep the DCR from erecting EZ-Pass gantries and tolling the roadway, and the DCR could certainly use the money) we could return the riverbanks to something closer to James and Helen Storrow's vision. It's not much, but improving these lanes, at least, would be a start.

Wednesday, November 15, 2017

Let's talk about safe streets in Cambridge

I'm tired of going to public meetings. Especially meetings organized by businesses in Cambridge where they accuse bicycle advocates of top-down planning which is making the roads unsafe, open the meeting by saying they don't care about data ("then why are we here?") and close by saying the want to collect anecdotes. They go on to complain that there has been no public process (which is interesting, given I've been part of a lot of this process) and say that the facilities are unsafe because they think they look unsafe. Let's look at some of their "arguments" and break them down, and then let's give the public some talking points for pushing back at subsequent meetings.

1. Don't let "them" set the meeting agenda. If a meeting is billed as a "community" meeting, it should be led by the community. If the businesses are taking charge, before the start the meeting, go up to the dais and propose the following: that the meeting be led by a combination of the community members and the business association. Have a volunteer ready to go. If they refuse, propose a vote: let the people in attendance vote on the moderator. If they still refuse, walk out. (This obviously doesn't go for city-led meetings, but for these sham public meetings put on by the business community which are only attended by cyclists if we catch it.)

2. Ask them about business decline data. I don't believe they have it. They claim that business is down because of the bike lanes, but ask by how much, and how many businesses. There is very likely a response bias here. Which businesses are going to complain to the business community about sales being down? The ones with sales which have gone down. Better yet, come armed with data, or at least anecdotes. Go and ask some businesses if their sales have been harmed by the bike lanes. Find ones which have not. Cite those.

3. There has been plenty of public process. The anti-bike people claim that there has been no public process, and that the bike lanes have been a "top-down" process. These arguments are disingenuous, at best. The Cambridge Bicycle Plan was the subject of dozens of meetings and thousands of comments. If residents and businesses didn't know it was occurring, they weren't paying attention. It would also do them some good to come to the monthly Bicycle Advisory Committee meetings, where much of this is discussed (they're open to the public; and committee members take a training on public meeting law to make sure procedures are carried out correctly). These are monthly, advertised meetings. If you don't show up, don't complain about the outcome.

Then there's participatory budgeting. The bike lanes on Cambridge and Brattle streets rose directly from participatory budgeting. This was proposed by a citizen, promoted by citizens, vetted by a citizen committee and voted on by citizens. Yet because the Harvard Square Business Association didn't get a voice (or a veto), it was "top down." They'd propose a process where they dictate the process, which is somehow "grassroots." This is untrue. Don't let them get away with this nonsense. The bike lanes are there because of grassroots community activism. If they don't like them, they had their chance to vote. They lost.

4. Bike lanes cause accidents. After the meeting, a concerned citizen (a.k.a. Skendarian plant) took me aside to tell me a story about how the bike lanes caused an accident. I didn't know what to expect, but they told me that the heard from Skendarian that a person parked their car and opened their door and a passing car hit the door. I was dumbfounded. I asked how the bike lane caused the accident and was told the bike lane made the road too narrow. He liked the old bike lanes, so he could open his door in to the bike lane. So if you hear this story, remember, this was caused by a car hitting a car. And if someone says that bike lanes require them to jaywalk to reach the sidewalk, remind them that 720 CMR 9.09(4)(e) says that a person exiting a car should move to the nearest curb, so crossing the bike lane would be allowable.

5. Data. The anti-bike forces will claim they don't want to use data. There's a reason: the data do not work in their favor. They may claim that the data don't exist. This is wrong. The Cambridge Police Department has more than six years of crash data available for download, coded by location and causation; the Bicycle Master Plan has analyzed his to find the most dangerous locations. Who causes crashes? More than 99 times out of 100: cars. (Note: object 1 is generally the object assumed to be at fault.)


When I dowloaded these data last year, there were 9178 crashes in the database. If someone mentions how dangerous bicyclists hitting pedestrians is, note that in six years, there have been five instances where a cyclist caused a crash with a pedestrian. (This shows up as 0.1% here, it's rounded up from 0.05%. Should this number be less? Certainly. But let's focus on the problem.). There have been 100 times as many vehicles driving in to fixed objects as there have been cyclists hitting pedestrians. Maybe we should ban sign posts and telephone poles.

--

I've written before about rhetoric, and it's important to think before you speak at these sorts of meetings (and, no, I'm not great about this). Stay calm. State your points. No ad hominem (unless someone is really asking for it, i.e. if you're going after the person who says they don't care about bicycle deaths, yeah, mention that). Also, don't clap. Don't boo. Be quiet and respectful, and respect that other people may have opinions, however wrong they may be. When it comes your turn, state who you are and where you live, but not how long you have or haven't lived there. When they go low, go high. We're winning. We can afford to.

Saturday, November 4, 2017

Cambridge Council Endorsements

I know you've all been waiting for it … the Official Amateur Planner 2017 Cambridge City Council endorsements!

I've lived in Cambridge for 6 years now, served on the Bicycle Committee for most of that time and gone to more council and zoning meetings than I care to admit. I'm making these endorsements based on two criteria: bicycle safety and progressive development policy (with a bit of transit thrown in). A bit of background:

1. Bicycle safety has become a hot button issue in Cambridge in recent years as more and more people have embraced cycling to work, and our infrastructure hasn't kept up. There is some talk that the recent activism, especially among younger voters, will change the makeup of the electorate in Cambridge this year. Nominally, all candidates are for safe cycling, but in reality, some are more than happy to sell out to the interest of the minority of people driving in Cambridge. After several "pop-up" lanes were installed this spring, there was a bit of "bikelash" in Cambridge, with some City Councilors calling for a moratorium until we could figure out how to make bike lanes not impact—well, something. They're not sure. Let's call it "easy parking and the free flow of traffic." Most insidious: the Harvard Square Business Association trying to kill bike lanes because cars. Councilors Simmons, Toomey and Maher supported this. they're off the list. (They also got their comeuppance: hundreds of cyclists, three hours of public comment and a meeting that ran until after midnight; I doubt they'll be pulling this sort of stunt any time soon.) Craig Kelley, based on several interactions, is kind of wishy-washy on safe cycling infrastructure, and while he often touts himself as a cyclist, he often veers in to the vehicular cycling realm. Sorry, Craig. For others, and for new candidates, I'll defer to the Cambridge Bicycle Safety group's list.

2. Development. Here, most candidates fall in to two camps, the Cambridge Residents Alliance and A Better Cambridge. Both are nominally aligned with allowing more development, but only one—A Better Cambridge—actually follows through. There are a few arguments against additional density and development, none of which hold water:

  • Gentrification. In Cambridge, this has already happened. So new luxury housing is not going to "improve" neighborhoods and increase existing rents, despite what CRA may say. This is, in general, grade-A horse manure.
  • Road/transit congestion. This too is a red herring. Cambridge itself is not that congested, most people bike, walk and take transit to work. It's the getting to Cambridge part. More local housing will mean more bike/walk/transit commutes, and the answer is not to build less housing, but to improve connections to Cambridge. Yet the CRA won't take a position on reducing parking minimums.
  • Open space. There is an argument for keeping some Open Space. But for an organization like CRA, open space becomes "parking lots." This needs no further explanation. (Apparently they have softened it to "it can be redeveloped for affordable housing"—good idea—"but only if the parking is replaced." Just, no.
There have been recent pushes by small groups of residents to downzone parts of Cambridge (I'm not sure if the CRA took a position on this, but they claim that Cambridge faces "over-development"; however, I know ABC opposed it wholeheartedly.) I don't like going to these meetings and don't want to have to go to more! Let's get councilors who we know won't buy in to this nonsense. 

A local zoning case in point: There used to be an autobody shop and a couple of businesses in a decaying, single-story building at 78 Pearl Street. These were non-conforming uses, built before the area was zoned C. The land was bought and the businesses relocated. It would have been a perfect opportunity to build a mixed-use, multifamily dwelling with apartments sized appropriately for the area. However, because of the zoning, mixed-use was out (even though it was replacing businesses!) and in place of the building went 78 and 80 Pearl: 4 bedroom, 3.5 bathroom (as a friend said: "oh, so everyone can poop in their own toilet!") single-family houses (on tiny lots) for $1.75 to $2 million. Two units instead of six. There are plenty of examples of non-conforming uses which could never be built today but fit in fine with the neighborhood. But given the land values, and the zoning, developers are forced to build this type of low-density, pseudo-suburban housing which is completely unaffordable.

So, while some CRA-endorsed candidates are beyond excellent on bicycle infrastructure (Jan Devereaux in particular, but she's past president of the very NIMBY Fresh Pond Residents Alliance, so there's that), this page can not endorse anyone who is endorsed by the CRA. If you're voting just based on bikes, she should be on your list.

There is some "whataboutism" going on with some anti-development types who say that the fault lies in other cities and towns not doing their part. This is true, but it's no reason for Cambridge not to develop more housing as well. Remember when Homer Simpson ran a campaign for garbage commissioner with the slogan "can't someone else do it?" Can't someone else do it is not a logical policy. Yes, there would be less pressure on local housing prices if the Newtons of the world did their part. But it's no reason for Cambridge to keep density down.  

Oh, then there's Tim Toomey. He's already out for a number of reasons (when he was a Councilor and State Rep, he was making more money than the governor, so don't feel bad if he loses his job, his pension should be just fine), but please leave him off your ballot entirely. He quashed the idea of running commuter rail to Cambridge because he was afraid of big, bad trains running on train tracks, so instead everyone from the Metrowest/Turnpike corridor drives. More congestion! More pollution! Progress! Thanks, Tim.

So with these criteria in mind, here are the official Amateur Planner-endorsed candidates. It's easy to remember: they all begin with "M":
  • Alanna Mallon: I met Alanna when she was canvassing. She gets it. I think she didn't get the Bike Safety endorsement because she holds back a bit on implementation of bike lanes. But from my conversation, she is very much in favor of transit and bike lanes, and will be an ally on the Council.
  • Marc McGovern: Marc has been on the Council since I've lived in Cambridge, and has been on the right side of the debate the whole time. I look forward to him serving another term.
  • Adriane Musgrave: I may have talked to Adriane longer than I talked to Alanna! (Note to candidates: knocking on my door helps.) She also very much "gets it" and is super data-driven and wonky. That's my kind of candidate!
So there you have it. If these three candidates are on the City Council, the future is bright. I will be ranking them #1, 2 and 3. (I'm not giving away my order.) If you live in Cambridge, vote how you wish. But I would urge you to vote for these candidates.

(I don't live in Boston, but here's my at-large council endorsement for Michelle Wu, of course. )

Friday, October 27, 2017

Thinking Big? Let's Think "Realistic" First

The MBTA's Fiscal and Management Control Board, according to their slides, wants to “think big.”

Thinking big is a laudable goal. The only problem is that big thinking requires feasibility, and it is a waste of everyone’s time and energy if the big thinking is completely outside the realm of what can reasonably occur or be built.

Case in point: combining Park Street and Downtown Crossing into one “superstation.” The first reason this won’t happen is that it doesn’t need to happen: with the concourse above the Red Line between the two stations, they are already one complex. (#Protip: it’s faster to transfer between the Red Line at Park and the Winter Street platform on the Orange Line—trains towards Forest Hills for the less anachronistic among us—by walking swiftly down the concourse rather than getting on the train at Downtown Crossing.) But there are several other reasons why this is just not possible.

Tangent track

To build a new station between Park Street and Downtown Crossing would require tangent, or straight, track. If you stand at Park, however, you can’t see Downtown Crossing, because the tracks, which are separated for the center platform at Park, curve back together for the side platforms at Downtown Crossing. This curve is likely too severe to provide level boarding, so the track would have to be realigned through this segment. So even if it were  easy to build a new complex here, the tracks would have to somehow be rebuilt without disrupting normal service. That’s not easy.

Winter Street is narrow. Really narrow.

The next, and related, point: Winter Street is very narrow: only about 35 feet between buildings. Park Street Station is located under the Common, and the Red Line station at Downtown Crossing is located under a much wider portion of Summer Street: those locations have room for platforms. Winter Street does not. Two Red Line tracks require about 24 feet of real estate: this would leave 5.5 feet for platforms on either side before accounting for any vertical circulation, utilities and the like. Any more than that and you’re digging underneath the century-old buildings which give the area its character. That’s not about to happen. And Winter Street would be the only logical location for the station; otherwise it would force long walks for transferring passengers.
Summer Street (foreground) is wide.
Winter Street (background) is narrow.
The fact that so many streets change names crossing Washington?
Well, that's just confusing.

Note the photograph to the right. The current Downtown Crossing station is located between Jordan Marsh on the left and Filene's on the right (for newer arrivals: the Macy's and the Millenium building), where Summer Street is about 60 feet wide, enough for two tracks and platforms, and it's still constrained, with entrances in the Filene's and Jordan Marsh buildings. Note in the background how much narrower Winter Street is. This isn't an optical illusion: it's only half as wide. The only feasible location for such a superstation would be between the Orange and Green lines, but the street there is far too narrow.

Passenger operations

The idea behind combining Downtown Crossing and Park Street is that it would simplify signaling and allow better throughput on the line operationally. But any savings from operations would likely be eaten by increased dwell times at these stations. At most stations, the T operations are abysmal regarding dwell times; Chicago L trains, for example, rarely spend as much time in stations as MBTA trains do, as the operator will engage the door close button as soon as the doors open. At Park and Downtown Crossing, however, this is not the case. Long dwell times there occur because of the crowding: at each station, hundreds of passengers have to exit the train, often onto a platform with as many waiting to board. This is rather unique to the T, and the Red Line in particular, which, between South Station and Kendall, is at capacity in both directions. Trying to unload and then load nearly an entire train worth of passengers at one station, even with more wider doors on new cars, just doesn’t make sense.

If Park and Downtown Crossing were little-used stations, it would make no sense to have two platforms 500 feet apart, and combining them, or just closing one, would be sensible. (Unlike New York and Chicago, the Boston Elevated Railway never built stations so close that consolidation was necessary.) But they are two of the busiest stations in the MBTA system, both for boardings and for transfers. Given the geometry of the area, both above and below ground, calling this a big idea is risible. Big ideas have to, at least, be somewhere in the realm of reality. Without a 1960s-style wholesale demolition of half of Downtown Boston, this is a distraction. The FMCB has a lot to do: they should not spend time chasing unicorns.

Better Headways? Geometry gets in the way, not just signals.

In addition to a spending time on infeasible ideas like combining Park and Downtown Crossing, the FMCB and T operations claims that it would only take a minor signal upgrade (well, okay, any signal upgrade wouldn't be minor) to allow three minute headways on the Red Line. Right now, trains come every 4 to 4.5 minutes at rush hour (8 to 9 minutes each from Braintree and Ashmont); so this would be a 50% increase. Three minute headways are certainly a good idea, but the Red Line especially has several bottlenecks which would have to be significantly upgraded before headways can progress much below their current levels. New signals would certainly help operations, but they are not the current rate limiting factor for throughput on the line.

There are four site-specific major bottlenecks on the line beyond signaling: the interlocking north of JFK-UMass (a.k.a. Malfunction Junction), the Park-Downtown Crossing complex, the Harvard curve, and the Alewife terminal. (In addition, the line’s profile, which has a bi-directional peak along its busiest portion, results in long dwell times at many stations.) Each of these is it’s own flavor of bottleneck, and it may be informative to look at them as examples of how retrofitting a century-old railroad is easier said than done. This is not to say that a new signaling system shouldn’t be installed: it absolutely should! It just won’t allow for three minute headways without several other projects as well. From south to north:

JFK-UMass

This is likely the easiest of the bottlenecks to fix: it’s simply an interlocking which needs to be replaced. While the moniker Malfunction Junction may not be entirely deserved (the Red Line manages to break down for many other reasons), it is an inefficient network of special track work which dates to the early 1970s and could certainly use an upgrade. In fact, it probably would be replaced, or significantly improved, with the installation of a new signal system.

Park/Downtown

Right now, Park and Downtown Crossing cause delays because of both signaling and passenger loads. For instance, a train exchanging passengers at Downtown Crossing causes restricted signals back to Charles, so that it is not possible for trains to load and unload passengers simultaneously at Park and Downtown Crossing. Given the passenger loads at these stations and long dwell times at busy times of day, it takes three or four minutes for a train to traverse the segment between the tunnel portal at Charles and the departure from Downtown Crossing, which is the current rate-limiting factor for the line. If you ever watch trains on the Longfellow from above (and my new office allows for that, so, yeah, I’m real productive at work), you can watch the signal system in action: trains are frequently bogged down on the bridge by signals at Park.

A new signal system with shorter blocks or, more likely, moving blocks would solve some of this problem. A good moving block system would have to allow three trains to simultaneously stop at Park, Downtown Crossing and South Station. So this would be solved, right? Well, not exactly. Dwell times are still long at all three of these stations: as they are among the most heavily-used in the system. Delivering reliable three-minute headways would help with capacity, but longer headways would lead to cascading delays if trains were overcrowded. There’s not much margin for error when trains are this close together. Given the narrow, crowded stairs and platforms at Park and Downtown crossing, the limiting factor here is probably passenger flow: it might be hard to clear everyone from the platforms in the time between dwells. And it is not cheap to try to widen platforms and egress. A new signaling system would help, but this still may be a factor in delivering three minute headways.

The Harvard Curve and dwell times

Moving north, the situation doesn’t get any easier to remedy. When the Red Line was extended past Harvard, the President and Fellows of Harvard College would not allow the T to tunnel under the Yard, so the T was forced to stay in the alignment of Mass Ave. This required the curve just south of the station, which is limited (and will always be limited) to 10 miles per hour. The curve itself is about 400 feet long, but if any portion of the train (also about 400 feet long) is in the curve, it is required to remain at this restricted speed. So the train has to operate for 800 feet at 10 mph, which takes about 55 seconds to operate this segment alone. Given that with Harvard’s crowds, it has longer dwell times due to passenger flow, traversing the 800 feet of track within the station and tunnel beyond takes more than two minutes under the best of circumstances.

Would signaling help? Maybe somewhat, but not much. Even a moving block signal system would not likely allow a train to occupy the Harvard Platform with another train still in the curve. Chicago has 25 mph curves on the Blue Line approaching Clark/Lake and operates three minute headways, but they also frequently bypass signals to pull trains within feet of each other to stage them, something the T would likely be reticent to do. It may be possible to operate these headways but with basically zero margin for error. Any delay, even small issues beyond the control of the agency, would quickly cascade, eating up any gains made from running trains more frequently. This is a question of geometry more than anything else: if trains could arrive and leave Harvard at speed, it wouldn’t be an issue. But combining the dwell time and the curve, nearly the entire headway is used up just getting through the station.

Alewife

The three issues above? They pale in comparison to Alewife. Why? Because Alewife was never designed to be a terminal station. (Thanks, Arlington.) The original plan was to extend the Red Line to 128, with a later plan to bring it to Arlington Heights. But these plans were opposed by the good people of Arlington, and the terminal wound up at Alewife. The issues is that the crossover, which allows trains to switch tracks at the end of the line, didn’t. It wound up north of Russell Field, along a short portion of tangent track between the Fitchburg Cutoff right-of-way and the Alewife station, and about 900 feet from the end of the platform. If a train uses the northbound platform, it can run in to the station at track speed (25 mph, taking 50 seconds), unload and load at the platform, and allow operators to change ends (with drop back crews, this can take 60 seconds), and then pull out 900 feet (25 mph, taking 30 seconds) and run through the crossover at 10 mph (45 seconds). That cycle takes 185 seconds, or just about three minutes, of which about a minute is spent traversing the extra distance in and out of the station. If the train is crossing over from one track to the other would foul the interlocking, causing approaching trains to back up. And since this is at the end of the line, there’s significant variability to headways coming in to the station, so trains are frequently delayed between Alewife and Davis waiting for tracks to clear.

Without going in to too much detail, the MBTA currently has a minimum target of about 4 minute headways coming out of Alewife. Without rebuilding the interlocking—and there’s nowhere to do this, because it’s the only tangent portion of track, and interlockings basically have to be built on tangent track—there’s no way to get to three minute headways. In addition, the T is in the enviable position of having strong bidirectional ridership on the Red Line. In many cities, ridership is unbalanced: Chicago, for example, runs three minute headways on their Red Line from Howard at peak, but six minutes in the opposite direction from 95th (this results in a lot of "deadheading" where operators are paid to ride back on trains to get back to where they came from). The T needs as many trains as it can run in both directions, so it has to turn everything at Alewife (never mind the fact that there’s no yard beyond; we'll get to that). This also means that T has to run better-than-5-minute headways until 10 a.m. and 8 p.m. to accommodate both directions of ridership. While this means short wait times for customers, it incurs extra operational costs, since these trains provide more service than capacity likely requires and, for instance, we don't need a train leaving Alewife every four minutes at 9:30, except we have to put the trains somewhere back south.

In the long run, to add service, Alewife is probably unworkable. But there is a solution, I think. The tail tracks extend out under Route 2 and to Thorndike Field in Arlington. The field itself is almost exactly the size of Codman Yard in Dorchester. Assuming there aren’t any major utilities, the field could be dug up, an underground yard could be built with a new three-track, two-platform station adjacent to the field (providing better access for the many pedestrians who walk from Arlington, with Alewife still serving as the bus transfer and park-and-ride), a run-through loop track, and a storage yard. I have a very rough sketch of this in Google Maps here.

Assuming you could appease local population and 4(f) park regulations, the main issue is that field itself is quite low in elevation—any facility would be below sea level and certainly below the water table. But if this could be mitigated, it would be perhaps the only feasible way to add a yard to the north end of the Red Line. And it is possible that a yard in Arlington, coupled with some expansion of Codman (which has room for several more tracks) could eliminate the need for the yard facility at Cabot Yard in Boston, which is a long deadhead move from JFK/UMass station. While the shops would still be needed the yard, which sits on six acres of real estate a ten minute walk on Dot Ave from Broadway and South Station, could fetch a premium on the current real estate market.

This wouldn’t be free, and would take some convincing for those same folks in Arlington, but operationally, it would certainly make the Red Line easier to run. Upgrades to signals and equipment will help, but if you don’t fix Alewife, you have no chance of running more trains.

Overall, I'm not trying to be negative here, I'm just trying to ground ideas in realism. It's fun to think of ways to improve the transit system, but far too often it seems that both advocates and agencies go too far down the road looking in to ideas which have no chance of actually happening. We have an old system with good bones, but those bones are sometimes crooked. When we come up with new ideas for transit and mobility, we need to take a step back and make sure they'll work before we go too much further.

Today's glossary:

  • Deadhead: running out of service without passengers. All the cost of running a train (or, if an operator is riding an in-service train, all the costs of paying them), none of the benefits.
  • Headway: the time between train arrivals
  • Tangent track: straight track


Editor's note: after a busy first half of the semester, I have some more time on my hands and should be posting more than once every two months!