Station Name Creep

Jarrett Walker tweeted today about a piece he wrote a few years back on his blog regarding corporate naming for train stations. While I agree that it is a pretty dumb idea to have mindless corporate naming rights (“get on the train at Bank of America, change at Gillette and get off three stops later at Novartis”), station names in Boston have changed, rather drastically, over the years. Someone dropped in from 1950 would barely recognize station names today, even though the lines in the core of the city haven’t changed in the past 50 years. So, where appropriate, I think name changes are not the end of the world, and if they help direction finding without overly-lengthening the name, may help.

Here’s a quick rundown:

Haymarket was originally Union-Friend, named for nearby streets. It was extensively rebuilt in the 1970s. (Wikipedia)

Government Center was originally Scollay (and Scollay Under for the Blue Line), named for the square above. It was obliterated by the Government Center construction in the 1960s (when the line was rerouted and the neighborhood leveled. (Wikipedia)

Hynes was originally Massachusetts, named for the Mass Ave. It then changed to Auditorium, then to Hynes Convention Center-ICA and, when the ICA moved, to Hynes Convention Center. During automated station announcements, the announcement sounds choppy at the end, as they just clipped the audio file when the station was renamed. (Wikipedia)

Prudential was originally Mechanics, named for the meeting hall which stood nearby, and changed when the Pru was built in the 1960s. (Wikipedia)

Kendall and Charles have both been modified to Kendall-MIT and Charles-MGH over the years.
Downtown Crossing was originally Washington, Winter and Summer. This is one of several Orange Line stations which has offset platforms named after multiple streets (and Washington was named after Washington Street of course). The Orange Line came first here, and the station wasn’t renamed to a single transfer point until 1967, when Winter and Summer were dropped, and 1985, when it as changed to Downtown Crossing. So although things didn’t change from 1944 to 1965, Tom Lehrer’s Subway Song today would be out-of-date. (Wikipedia)
Washington Street was originally the only street along Boston Neck and carried the Post Road to New York. As the main street, intersecting streets changed names when they crossed Washington (which doesn’t help the whole Boston is impossible to navigate thing). And because the BERy named subway stations for their intersecting streets, different platforms got different names (the Washington Street Subway had no center platforms). So, Friend-Union, Winter-Summer and …
Chinatown was originally Boylston and Essex. Boylston on the southbound side, Essex going north. Was it a problem that there was a separate Boylston station a block away? Apparently not. (Wikipedia)
State was originally Milk and State on the Orange Line and Devonshire on the Blue Line. It was, for a time, actually called State/Citizens Bank as Citizens was trying to get the whole area renamed for them, but that lapsed and the name reverted to State. (I don’t think any system maps were ever displayed with this travesty of a name.) State was probably retained over other names because it is located at the old State House, in addition to being on State Street. Along with Park, it is the only main transfer station that hasn’t been renamed completely. (Wikipedia)
Aquarium was originally Atlantic (for the Avenue, not the ocean). 
There’s a good animated GIF of the changes over time here.

Midnight Marathon Tips

Recently we’ve been on about the Midnight Marathon, when 700+ cyclists take a train to the Boston Marathon start line and, at midnight, bike back. Well, the race sold out, we posted some suggestions (*) on how to participate if you didn’t snag a ticket (we did). Today the Boston SOS asked for suggestions on their website. As a bike commuter, professional evangelizer and possible blowhard, here are some suggestions to having a safe, fun ride:

  • Choose a comfortable bike right for the conditions. I, for instance, have three bikes to choose from:
    •  I could take my road bike. The pros: it’s fast and rides dreamily. The cons: do I want to have my carbon bike jostled amongst other bikes on the train, if the road is wet it won’t be that great a ride, it doesn’t have a fender, and I’d have to wear by not-walky bike shoes. Also, if I want to carry a bag (with layers and street shoes, perhaps) it’s less conducive to a comfortable riding position.
    • I could ride my mountain/commuter bike. The pros: it’s reasonably road-worthy. There’s less of a chance of flatting out compared with the road bike. I can walk in the cleats, and it’s a little more comfortable from a bag position. Oh, and it has a fender if it’s wet. The cons: it’s certainly not up to roadie speed, but it’s also no slouch. So I might not be taking pulls, but I can probably do some drafting. Plus, I got the brakes repaired last spring. The granny gear is a little sticky to get in and out of, but I doubt I’ll need it on the mostly-downhill route. I’ll probably go this direction, unless I really want to go fast. But in the dark, speed is not necessarily your friend.
    • I could ride a Hubway. The pros: pretty comfy for short rides, and it has a basket. The cons: It’s heavy as sin. And slow—good luck breaking 20 mph except on the longest downhill. It’s a bear to get on to the train. And at the end of the ride, I’d have to bike it back to Central and then walk home at 2:00. Oh, wait, I’d be on a Hubway. 3:00. Plus, if they don’t waive fees (they probably will) it’s a pricey ride.
  • Wear comfortable clothing, bring layers, and if it might rain, bring something rainworthy. Last year, we stood in the rain for an hour while everyone detrained, and then the first uphill to Hopkinton was pretty wet. It wasn’t cold—the next day would be scorching hot, remember—but with wind and rain it was not a good time to be in jeans. This year looks dry and seasonably cool, with temperatures during the ride in the upper 30s and light winds. Certainly bring and wear gloves. And remember that at 20 mph there’s a bit of a wind chill. Brr!
  • Bring some flat-fixin’ stuff. Other people will have it, sure. And bicyclists love each other. (Last week, after I blew out a tire in Arlington, a passerby brought me a new tube and floor pump. Hooray!) But still. Bring a patch kit, and maybe even a spare tube. If you can’t use it, someone else can.
  • Bring lights. You know what, bold isn’t enough here. BRING LIGHTS. And while we are at it, WEAR A HELMET. First, lights. State law stipulates a front headlight and a rear reflector or light. Bring a rear light. Or two. The more light, the merrier. Sure, everyone else will have lights. But there are cars along the route. And you want them to see you. Plus, everyone else has lights which is really cool:

    While we’re at it, helmets. For god’s sake, wear a helmet. I do not need to explain this.
  • Obey the laws. The lights are a law. Staying in the right lane is a law. Not running red lights is a law. While you might skip the letter of the law, at least comply with the idea of the law. Don’t get hurt, and don’t unnecessarily piss off motorists (not that you’ll see many). And don’t bike down 135 at 40 mph in the left lane. The roads are open to traffic. There’s just not much of it.
  • Don’t get your ass kicked by the police. Okay, that was a Chris Rock reference; more to the point: if the cops show up, do what they say. Last year, a couple of Southborough cops showed up at Southborough, and then left when they saw there wasn’t much fuss. But last year pretty much no one knew what was going on except those of us on the train. This year, we’ve been all over the Globe and social media, so there might be cops out patrolling in various towns along the route. They’re there for our safety. Be nice to them.
  • Know the route. The route is well-marked and pretty intuitive. Basically, follow the port-a-johns. A quick primer for the route:
    • Start on Route 135. It’s downhill at the start. A lot.
    • There is a traffic light in Ashland on a downhill. You might be going 40, so you might have to brake. A lot.
    • There are DIAGONAL RAILROAD TRACKS on both sides of Framingham. Last year it was wet and there were lots of crashes and some injuries here. Even if it’s dry, slow down and turn to cross them perpendicular. And let others know about it, too.
    • 135 merges with 16 in Wellesley, but there’s no real turn.
    • You’ll begin to see some more traffic around Route 128.
    • About a mile after 128—half a mile past the Woodland T stop and Newton Wellesley—the course turns up Commonwealth Avenue at mile 17.4. These are the Newton Hills. There’s a firehouse on your right. (I grew up a block from here, too.) Take a right on to Commonwealth. If you get to West Newton and the Mass Pike entrance, you’ve gone (a mile) too far.
    • There are three major hills in Newton. The first climbs about 100 feet over half a mile, and there is then a gradual descent to Walnut Street (City Hall). For there, it’s another 100 feet up Heartbreak Hill, followed by a flat section across Centre Street. Then it’s another 100 feet up to Hammond Street, followed by a screaming descent through BC.
    • Once you cross in to Boston, traffic will pick up. The streetcar tracks are in the median to your left.
    • At about mile 22, you take a right on to Chestnut Hill Avenue and a left on to Beacon Street. A few very important notes:
      • Chestnut Hill Avenue has embedded streetcar tracks. Stay in the right lane to avoid these. There shouldn’t be much traffic, but this is not a place to speed up. I can tell you from experience that if you put your wheel in the track you will go down. The one time I did that I somehow flipped over the bike, unclipped and somehow landed on my feet, but I wouldn’t want to try that again.
      • At the bottom of the hill in Cleveland Circle, you take a left on to Beacon. There’s a pretty elaborate light, and you’ll be taking a left on to the inbound lanes to the right of the streetcar tracks in the median.
      • Speaking of which, holy streetcar tracks, batman. There are lots of tracks in Cleveland Circle. Slow the fuck down and don’t die, okay?
    • Beacon Street is nicely paved and has a bike lane. And some traffic. Watch the downhill in to the light at Washington Square.
    • After Kenmore Square, the marathon route crosses under Mass Ave. At the Bowker Overpass (Charlesgate) get over to the left (there’s a left-hand bike lane) to go through the underpass.
    • The marathon route then takes a right on to Hereford. This street is one way in the opposite direction. It’s only two blocks, and it’s not well-traveled at this time of night. Plus it may already be closed to traffic and certainly won’t have any parked cars. Still, go slowly and watch for oncoming traffic. Or go another block to Gloucester (not quite the official course).
    • Take a left on Boylston. And sprint to the finish!
  • Hang out at the end, especially if you are an early finisher. The marathon folks had no issue with us hanging around in their finish pens last year; how nice of them! Cheer on your compadres as they come down Boylston. Make some friends, and see if there’s anyone going home in your direction (or to an all-night eatery; stupid Boston won’t let us drink after 2 a.m.). Then, once you’re ready, head home. With 1000 cyclists (or so), for the first few miles, you might have some company.
It should be fun!
(*) According to the Midnight Marathon FAQ, bikes won’t be allowed on other trains. However, according to MBTA policies, they are. If you are taking another train (9:20 to Franklin, 8:30 to Framingham) consider printing out or having on your phone the MBTA bike policies, and be firm but polite with both MBCR staff and non-biking customers. Kindness goes a long way. And if they don’t let you on and you’re still keen to ride, you can probably bike to the start by the time the train loads, travels, unloads and then we all make our way to the start.

Moving Bicycles, part deux

Update: the train sold out in 12 hours.

A few weeks ago, I wrote about trainloads of bicycles. The Boston Globe has an article about the bike train, and it’s trending in their most viewed list. It should  be exciting; I’m hoping the line for tickets isn’t too long over at South Station (I’m headed over there later to buy my ticket).

Now, it’s entirely possible that fewer than 700 bicyclists will buy tickets, and there will be no mad rush or secondary market. It’s also possible the train will sell out. (I’m only buying one ticket, buying extras to make a profit seems a bit uncouth.) In that case, here is Ari’s Unofficial Guide (I’ve written other unofficial guides in the past) To Getting To Southborough If You Can’t Get On The Train. In order of feasibility:

  1. Take the 8:30 and bike out to Hopkinton from Framingham. It’s 7 miles from Framingham to Hopkinton, which is only 4 miles further than the ride from Southborough. The train gets in at 9:20, which gives you a good hour and a half to bike up the hill to the start. If you were really keen, you could bike out to Southborough (6.5 miles) and join the ride there. One caveat is that they may be somewhat reticent to put a bunch of bikes on this train, but since Framingham is the final stop getting all the bikes off won’t delay any other passengers. Just make sure to leave room for the “normals” on the train. Need to kill an hour? There’s a bar in Ashland right on the course. Hopkinton isn’t dry, but there don’t seem to be many bars there. Update: The MBCR tweeted that it is a “regular train with room for only a few bikes.” So if you take it, arrive early, board early, and then get ready to get off quickly in Framingham. This train turns and is the 9:45 back to Boston, so it can’t stand to get delayed by an hour. Make sure to leave a couple of cars bike-free for non-cyclists. And consider buying a higher-zone pass to give the T some extra dollar bills.
  2. Take the 9:20 to Franklin. At 13.1 miles, this is a longer ride than the Framingham option, but it does leave a bit later. The train gets in to Franklin at 10:12, more than half an hour before the extra train gets to Southborough. From there it’s a ride mostly along back roads with one big hill at the end in to Hopkinton (the ride from Norfolk, the stop before Franklin, is not much longer, and you get an extra 7 minutes to ride). It’s probably a very nice ride, but you should be able to ride it in an hour to meet the rest of the gang from the Extra. Assuming a 45 minute run time, the Extra will arrive at 10:45 and should be done unloading by 11:15, and it’s a 15 minute-or-so ride to the start from there. If you can ride 12 m.p.h. you should be able to get to the start around the same time. (i.e. don’t try to do this on a Hubway, but if you’re a roadie, you should be fine.) See the suggestions above to keep the train, and yourself, on schedule.
  3. Just get on your bike and ride! Who’s not up for a metric century in the dark, anyway? You could trace Paul Revere’s footsteps (that’s what the holiday is all about—it’s not just a random day off for government workers) and ride up the Minuteman to Lexington and on to Concord. (This is more like 70 miles, and more if you follow Paul Revere’s route through Charlestown and Medford.) Then drop south to Cortaville/Southborough, meet the train, and ride on.
  4. Play coy, catch the 11:00 to Framingham and ride from there. For this option, get on the 11:00 train and buy a ticket to Framingham. Tell the conductor that you live there and are riding home, and that is within the bike regulations of the T. The train gets in to Framingham at 11:50, so you would have plenty of time to detrain and bike backwards on the course to go and meet the rest of the ride (or just hang out in Framingham; the first riders will shoot down the early hills in 15 minutes easily). You wouldn’t get the full experience, but it would work, in a pinch. Major caveat: even if you cite policy, they might not let you on this train.
  5. Play coy and try to catch the 11:00 to Southborough. (Not Suggested) Word on the street is that bikes won’t be allowed on the late train. There’s a canard that it will be full from Red Sox traffic from the game which starts at 1:00; I don’t believe this. But they don’t want a ton of bikes clogging the train and slowing it down; that’s why they’re running the extra. Still, it might work as an option, but I wouldn’t suggest it. If you were to take it, you’d arrive at midnight, and have a tough time getting to Hopkinton by the start, although you could probably catch some stragglers. If you are going to do this, I’d suggest buying a ticket to Worcester, claiming that’s your final destination, and getting off at Southborough. Unless there’s no one else getting off there. Have fun biking home from Worcester. (Actually, this train turns in Worcester and runs back to South Station, so you’d get a nice, dark train ride. Fun!) Anyway, don’t do this.
Whatever you do, be sure to express gratitude towards the MBCR employees—who are mostly volunteering for the event!—and the T in general. And ride safe.

How do you move 1000 bicyclists by train?

This seems like it should be a rhetorical question. It’s not.

In 2010, about 70 bicyclists got onboard the late train to Worcester at 11:00, biked to the start of the Boston Marathon at midnight, and rode back in to the city. In 2011, 250 bikers showed up. Last year, by most estimations, 750 bicyclists made the trip, 150 on an early twilight ride and 600 on the traditional midnight ride.

If history is any guide—if the event triples again in size—2000 bicyclists will attempt to cram aboard the train and get 25 miles west to Hopkinton. Even if the growth of the event slows, a good 1000 bicyclists will likely show up to the event. (It is being advertised as “limited space” right now—we’ll see what happens.) The issue here is that with 600 bicyclists last year, the MBTA (well, really the MBCR, which operates commuter rail service) had to couple two trains together with 14 cars in order to accommodate these travelers. Any significant increase will have to have advanced planning, or some riders will get left behind.

While no one will lose their job if they can’t fit on the train (i.e. no one is missing work due to an overcrowded train), it would be lost revenue for the T, and bad publicity. The event garners some news coverage and probably will continue to do so, and if these cyclists are unable to cram aboard the Midnight Marathon train they’re less likely to take their bikes aboard trains the rest of the summer, and genrally at off-peak times. This is discretionary ridership which adds revenue without adding operating costs (or crowding rush hour trains). It’s in the T’s best interest to make sure everyone gets onboard and happy.

The problem is that unless changes are made, the train is nearly maxed out. So, there need to be some strategies to maximize the number of cyclists per train, streamline boarding and detraining, and have enough room to get everyone to Southborough, and staging them not in an intersection. Oh, and garner enough revenue for the MBTA that it is worthwhile to run extra trains to accommodate these passengers.

Maximizing cyclists on each train. Last year, when lines of cyclists snaked through South Station and on to the platforms, there were few guidelines to maximizing the number of bikes on board. The T ran single-level coaches (so cyclists didn’t have to haul bikes up and down stairs—this is probably for the best) with, for the most part 2-3 seating. For the most part, bikes were set in to the three-seat side of the car, and people sat in the couplets. This meant that, for all intents and purposes, 40% of the seats on the train were occupied.

This can be improved. With a minimal bit of cajoling, three bikes can be fit in each row. This means that every six rows of seats can see 15 bikes and 15 passengers. How? The first row has three bikes and two seats, so there’s a leftover passenger. The second row has three bikes and two seats, so there are now two leftover passengers. This goes on until you get to the sixth row which has five extra passengers and, very conveniently, five seats. Fill those up and start from scratch. You’ve raised capacity from 40% to 50%. With a seven car train and 120 seats per car, you can now accommodate 420 passengers.

How do you assure that there are three bikes per seat? Get volunteer riders-turned-ushers to enforce these rules. Have them walk down the cars from either end and assure there are three bikes to a seat and nothing goes empty. This doesn’t have to fall on T employees (who were mostly amazed at the turnout last year); I’m sure a couple dozen volunteers could be marshalled in to showing up at 8 to make sure everyone gets on the train. I’d probably be one.

Streamline boarding and detraining. Boarding is relatively simple at South Station. It’s time consuming, but with wide, level platforms it is relatively easy. The goal should be to get people on the train early, and board multiple cars at once. Last year people seemed to board one car until it was full and then move to the next. If we know how many bikes can fit in each car (and we should, see above) we can shepherd carloads of cyclists down the platform to the further-down cars and have everyone board at the same time.

Last year was that the extra train called in didn’t arrive until after 10, and people spent a while waiting (although the service did leave on time). If there are multiple trains, when a train is full, it should go. Last year the train had to be staged—detrained in sections—which more than doubled the time it sat at the station. In fact, here’s an idea. The 11:00 train makes all stops to Southborough. It should be boarded full except for one car, which can be reserved for “normal” passengers, and leave at 11:00 and make all stops. A second special train could begin boarding a bit later—say, at 11:00—and make an express run to Southborough (in about 35 minutes). It could cross over at some point and detrain on the inbound track (since it would then turn back to Boston) at the same time as the first train, doubling the speed people can get off. If there was a need for three trains, an early express could make a run out to Southborough and clear the tracks before the later trains arrived. It’s not like there is a lot of traffic on the line on Sunday evenings, so all of this would be possible.

In fact, there is a large parking lot on the inbound side, which would be a better place to assemble than last year when cyclists took over the streets (not that there was much traffic).

Sell and collect tickets. This worked well last year, for the most part. One change is that this year many participants may use smart phones to buy their tickets, and a question is whether there would be an issue with checking these tickets en masse. A certain suggestion would be to cordon off the platform at boarding time, and check tickets before boarding, so conductors wouldn’t have to ply the coaches en route.

Finally, it might be advisable to suggest that Midnight Marathoners buy a higher-zoned ticket to help the T cover the costs of this train. If the ride organizers told everyone to buy a Zone 8 one-way ticket, it would only be a dollar or two more for each rider, but it would be a few thousand extra for the cash-strapped T. Furthermore, requesting that riders buy a specific ticket ahead of time (Zone 9, for instance, which otherwise serves only the TF Green airport) could give a pretty good read on expected turnout. They are doing a tremendous service to the community by running extra-long trains, or extra sections, and putting a little extra money—which most anyone riding their bike at midnight on Marathon Monday can afford—in their coffers is good for all.

Let the market decide how many spaces to build

There’s a lot of chatter about a proposed development on an otherwise-unused piece of land in Allston. It’s been mentioned in the Boston Globe, on The Atlantic Cities and elsewhere. It’s not the size of the development, but what it lacks: the property owner plans to build 44 apartments without a single private parking space.

Boston, like most other cities, has minimum parking requirements for new development. This is the case even though much of the older housing stock has no parking, and it still perfectly habitable and in many cases quite desirable. But since the 1950s, adding housing without adding lots of parking has been frowned upon. In order to have even a chance to get the plan through the zoning board, the developer, Sebastian Mariscal, is throwing out all sorts of mitigation efforts. These include public green space, private gardens for each unit, storage units, bike parking (two spots per unit) and storage lockers. But he goes further still: he proposes making each resident sign a lease addendum that, while living in the development, they will not own a car.

It is this rather radical part of the plan that has gotten a lot of attention, and in some cases, praise. I don’t fault Mariscal for proposing it, but he shouldn’t have to. The minimum number of parking spaces a developer builds should be dictated by the market, not by the zoning board of appeals. If a developer wants to build a lower number of parking spaces than would be allowable, they should darn well be able to. Forcing them to build more spaces increases the cost of each unit, which in turn reduces the amount of housing available, which in turn raises the cost for everyone.

Neighbors may whine about the potential for reduced parking availability clogged streets and gridlock, but their complaints should fall on tin ears. There is no guaranteed right to parking. Especially in a neighborhood like Allston, which, as the Atlantic points out, is mostly pavement, there should be ample parking available to those who need it. If the area is developed enough that there is a dearth of parking (and 44 units won’t do this), someone who owns a driveway or parking lot will rent spaces. Then residents can use the marketplace to decide between the cost of a guaranteed, monthly parking spot and the time it takes to search for street parking.

Cities should have a vested interest in making sure that parking is not overbuilt. Too much parking raises the cost of housing, detracts from street life and, as cost for parking falls, disincentivizes the use of alternative modes of transportation. But disallowing projects because they fail to provide parking only serves to drive up the cost of housing, increase congestion and pollution and, in turn, detract from the city’s tax base as less housing is built. In addition, if more parking is built than required, it can lead to half-empty concrete parking hulks which have too much sunk cost to be converted to another use (see: Kendall Square). Plus, Allston has plenty of parking, even though you don’t need a car. The proposed housing is a stone’s throw from a drug store, a major supermarket, half a dozen bus lines and the streetcar. It’s a place that doesn’t need parking. So why force it to be built?

Toronto has allowed a skyscraper—first proposed in 2011—to go forward with 42 stories, 315 units and no parking spaces. The developer said “if we couldn’t sell a unit without providing a parking spot, then we wouldn’t be selling those units. The proof is in the pudding—we sold 270 units without parking in nine days.” And, so far, Toronto has not (yet) devolved in to a gridlock of traffic looking for a parking space.

Lack of parking is a perfect instance in which the free market should take charge. It’s high time that cities stop meddling in developers way and let them build the housing they want to build, whether it has “enough” parking or not.

Literal NIMBY

Down the street from where I live in Cambridgeport, there is a church which has closed and is slated to be redeveloped. (This is not without precedent, there is a church a couple of blocks away which was also turned in to apartments.) In a neighborhood with some of the highest rents in the city and a very tight market, more supply will serve to both stabilize prices and to add tax base from a previously un-taxed parcel.

Of course, there are people who are against development. People in Central Square push parking lots over density, and claim more housing will turn the area in to an uninhabitable hellscape. That’s silly, but that’s up the street. There’s an organization which wants to “save” 56 Magazine by—well, by keeping it a mostly unused, run-down church building. They claim that Cambridge needs more communal space. This might be true, but they want to subvert the free market to keep a religious institution, well, something. Even as the demographics of the city have changed and there are many fewer church-goers to fill these spaces. And even though there’s a perfectly good park not a block away. Oh, yeah, it’s in a perfectly walkable neighborhood, one of twelve examples profiled by Julie Campoli in her book Made for Walking.

So who are these 56 Magazine people? Well, I’m not completely sure, but their address is interesting. It’s 60 Magazine. And for the record, there is no 58 Magazine. So, quite literally, these are NIMBYs. Or, maybe NIMSYs—not in my side yard. I took a picture:

So the people who live in the house to the right don’t want construction and activity in the building to the left. So they are trying to create a non-profit advocacy group about it. At least they’re transparent about it—or at least their address.

On US Olympic Bids

The Boston Globe has a column today about US Olympic bids, touting smaller cities chances at bidding for the summer games, including Boston. While Boston could probably hold a summer Olympics (hey, Atlanta did to, well, not quite universal acclaim), it might be a bit of overkill. The city doesn’t need the new baseball stadium (well, it does, but Fenway will live forever) that Atlanta did to justify building an Olympic stadium, the transit system would be strained between venues. While some sports, like rowing and sailing would have terrific natural venues, others, namely high profile events like swimming and track and field, would require major stadium investments the city does not need to make. (The timing would have been right around 2000 to build a stadium the Patriots could have then used, but they have a perfectly good field in Foxboro.)

Plus, the 2024 Olympics are probably not going to go to the US anyway. The bids for 2020 are down to Istanbul, Tokyo and Madrid. Rumor has it that the IOC may look more towards Africa and Asia beyond then, particularly if Tokyo or Madrid wins in 2020. And while it is true that the US will not have hosted a summer games in 28 years, they hosted in 1984 as well (so that makes two in 40 years) and a city would probably have to come in with a strong bid to have a chance. (Chicago and New York flailed for 2012 and 2016.)

The winter games, on the other hand, might make more sense to bid. First of all, there are many fewer cities which can host a winter games. South America, Australia and Africa are out. In recent years, the IOC has moved away from awarding the games to tiny alpine towns as the games—and lucrative spectators—have grown. While the next two Olympics are in smaller cities, they are nowhere near the towns of a few thousand which hosted the games in 1992 and 1994. (Pyeongchang is quite small, but the indoor events in 2018 are taking place in the larger city of Gangneung.) In addition, the trend in recent years has been to have valley-mountain Olympics, where indoor-based venues are held in one location (generally in a city) and outdoor events held at a location further afield.

The Winter Olympics generally rotate between Europe, Asia and North America. The North Americans would be up for the games again in 2022, but a bid appears unlikely, and a European city (Munich was second in 2018 and would be a strong contender, as would Oslo and others) will likely see the games. In 2016 it will have been 16 years since a North American Winter Olympiad, and 24 since the games were held in the US.

So a US city would be a strong contender with a good enough bid. Unlike the summer Olympics, which can be held pretty much anywhere, there are a few course requirements which dictate where the winter games can be held (in addition to the need for snow). The first is the Downhill ski event, which requires a vertical drop of at least 800 meters (2600 feet). A not-high-or-steep-enough hill has been a thorn in the side of Quebec City’s hopes for the games (even though it would otherwise make a great host); Montreal would have to look south across the border for enough elevation and multinational bids are not well-received by the IOC. The second issue is that there is an altitude limit of 1800 meters (5800 feet) as the maximum height for cross country ski courses, so while they don’t need to start much lower (they only need 25 meters of climb) this becomes an issue for many western venues which only see snow up high. (In 2002, Soldier Hollow just barely squeaked in under the height limit.)

There are also other considerations. A city which would not need to build much new infrastructure (both for indoor arenas and for transportation) would certainly be ahead of a city that did. In addition, it should be assumed that housing for athletes would be built anew and then converted by the city to suit its needs (most of the cities here could use new housing stock). Finally, a city with some winter sports pedigree would be more likely to host the games than one which just happened to be near a ski slope.

Here are some potential cities, and issues which arise with each. I’ve highlighted each category in either Green (good), Yellow (would need some improvements), Orange (could be a major issue) or Red (would preclude the games, such as the ski slope height in Quebec). I’ll assume that, for every location, a Nordic venue would require full snow making.

Boston:

  • Alpine: Several locations within 2-3 hours have adequate elevation, but may require new construction, potentially in an ecologically sensitive area.
  • Nordic: Several potential locations near the city.
  • Indoor Arenas: Existing arenas could be used with minor modifications.
  • Urban Infrastructure: Existing infrastructure could handle in-city traffic, modifications may be required to outlying events.
  • Other: Strong local winter sports history, especially hockey. 
New York:

  • Alpine: While there is a potential location in the Catskills, it is an ecologically sensitive area and there would likely be dramatic opposition to construction there. This might preclude New York as a candidate. (Large-enough downhill venues in New York or Vermont are several hours away and would require major infrastructure investments to be nearby, although a joint Placid/NYC bid might be doable.)
  • Nordic: Several potential not too far from the city. If you wanted to get creative, you could hold cross country ski events in Van Cortlandt Park in the Bronx adjacent to the 1 Train, home to what is probably the world’s most famous cross country running venue, which has the requisite climb (this might requiring transporting snow from off-site). This would require using the bridges over the Henry Hudson Parkway, but at 11m wide, they’d be plenty wide enough to meet standards, and the park has enough topography for the necessary climbs. (edited 2018)
  • Indoor Arenas: Existing arenas could be used with minor modifications.
  • Urban Infrastructure: Existing infrastructure could handle in-city traffic, modifications may be required to outlying events.
  • Other: Strong local winter sports history, especially hockey.
Albany:

  • Alpine: Whiteface is about 2 hours from the city and could be used.
  • Nordic: Several potential locations near the city.
  • Indoor Arenas: New infrastructure would likely be required to handle events. Some events could be held in New York City arenas, but this would create a long distance between outlying areas.
  • Urban Infrastructure: Existing infrastructure would need to be significantly upgraded.
  • Other: A small city without much major winter sports pedigree.
Minneapolis:

  • Alpine: The highest elevation in the state is 2300 feet. The lowest is 600. In the state. (This would kill bids from other Midwestern cities as well).
  • Nordic: Several potential locations in the city.
  • Indoor Arenas: Existing arenas could be used with minor modifications.
  • Urban Infrastructure: Existing infrastructure could handle in-city traffic, modifications may be required to outlying events.
  • Other: Strong local winter sports history, especially hockey and Nordic skiing. 
Denver:

  • Alpine: Many locations nearby.
  • Nordic: Areas below 1800m receive very sporadic snow and would require new construction and massive snow making / snow hauling efforts. However, such an area, unless it was easily accessible to the urban core, would not be utilized after the games as there is natural snow skiing nearby.
  • Indoor Arenas: Existing arenas could be used with minor modifications.
  • Urban Infrastructure: Existing infrastructure could handle in-city traffic, modifications may be required to outlying events.
  • Other: Strong local winter sports history, especially hockey and Alpine skiing. However, Denver bid for and then turned down the 1976 games, which is still a cause of bitterness with the IOC. They would need a very strong bid to overcome this. (Colorado’s politics have changed dramatically, however, in the past 40 years.)
Salt Lake City:

  • Alpine: Many locations nearby
  • Nordic: Soldier Hollow.
  • Indoor Arenas: Existing arenas could be used with minor modifications.
  • Urban Infrastructure: Existing infrastructure could handle in-city traffic, some modifications may be required to outlying events.
  • Other: The city hosted the games in 2002, and the USOC would probably want to run another city’s bid if it were up to snuff. 
Reno:

  • Alpine: Many locations in the Tahoe area.
  • Nordic: All developed Nordic areas are well above 5800 feet (the level of lake Tahoe is 6200). A new area would have to be built at a lower elevation where snow would be more sporadic and require snow making, and would not be used after the games because there is good natural snow nearby.
  • Indoor Arenas: New infrastructure would be required.
  • Urban Infrastructure: New infrastructure would be required.
  • Other: While the Lake Tahoe area has a strong winter sports pedigree, Reno itself does not. 
Seattle:

  • Alpine: Many locations nearby
  • Nordic: Several mountain locations
  • Indoor Arenas: Most existing arenas could be used with minor modifications, but a new ice arena might be necessary.
  • Urban Infrastructure: Existing infrastructure could handle in-city traffic, modifications may be required to outlying events.
  • Other: While the mountainous areas near Seattle have a strong winter sports history, Seattle itself does not—for instance, it is the only large city on this list without a professional hockey team.
Looking at this list, Minneapolis would be out lacking mountains and New York likely would as well (unless it partnered with Lake Placid, which would vault it up the list, given, for instance, that there are three major ice arenas Brooklyn, Manhattan and Newark). Reno and Albany are both rather small, and each has a venue issue (Reno with no low-enough Nordic venue, Albany with a far-away Alpine hill). That leaves Denver, Salt Lake City, Seattle and Boston. Denver and Salt Lake both have historic issues. Salt Lake hosted recently and the US would probably want to run another city. Denver would make a fine host (with the exception of finding a suitable Nordic venue) but 2026 would be the 50th anniversary of their snub (the only time a city has turned down the games) and the IOC holds grudges almost to the degree that they take bribes.
So that leaves Seattle and Boston. Seattle would make a fine host, although it doesn’t have a strong winter sports history to the extent that some other cities do (for instance, it has no major pro or college hockey team) and thus might need a major new ice venue. So that leaves Boston.
Boston, I think, would do well with the winter games. With several college venues, the city would have no problem hosting the indoor sports; there are several arenas that could host curling and speed skating (with the added bonus of curling fans in Canada being a not-too-long car trip away). Preliminary hockey rounds could be held in cities across New England (Providence, Hartford, Worcester, Burlington, Manchester, Portland) bring the Olympics to nearby cities and freeing up venue space in town for skating events. Like any new Olympic city, Boston would have to build a sliding center to accommodate the sliding events, and ski jumps for jumping. Oh, and a speed skating event. That brings us to the Nordic and Alpine venues.
There is a website promoting the 2026 games (which has a Facebook page, too—with more likes than the summer page—and an article about it) and it hits on some of the same issues I do here. It promotes Fenway as an Olympic stadium (that would be fun; it did host the Winter Classic a few years back) but it sort of glosses over the Alpine and Nordic events. It mentions locations in New Hampshire and Vermont and—that’s about it. In other words, no, please don’t put the Nordic events at Bretton Woods.
Here are some things I think.
For Nordic, elevation is not an issue, except that there needs to be enough height differential for a homologated course. The main issue would be the ability to make and keep snow, and any venue in or south of Boston would be iffy (and climate change could render this whole operation moot). However, to the north and west, it would probably be fine. There needs to be room for 10 kilometers of trail, two stadia (for Nordic and Biathlon) and decent access for spectators. An added bonus would be a location which allowed for continued use after the games. Here are some options:
  • Mary Cummings Park in Burlington is owned by the City of Boston and underutilized. It would have space for stadiums and the requisite elevation differential. It is far enough inland that it is probably cold enough to make snow, there is a major water storage facility which could provide water and pressure. It is not on an existing rail line, but could be connected to transit by buses (in fact, the 350 bus already passes the venue hourly). Politically, it’s owned by the City of Boston but barely used for anything, so it might be easy to redevelop for active recreation. Along with Prospect (below), it is probably the closest feasible venue to Boston.
  • Just as close, and also somewhat underutilized and owned by the City of Waltham, Prospect Park could have a heck of a cross country course. There has been a move in recent years to steeper hills, and a course which climbed the old ski hills a couple times would really test the skiers. Transit is a bit of an issue (the 70A passes nearby, and the southern end of the park is only a mile from downtown Waltham) although a light rail or commuter rail spur could be built along the old Mass Central to serve the southern end of the park. (This could actually be built as a loop branching off of the current Fitchburg Line just west 128 and looping back through North Waltham; three miles of existing right of way would not be terribly expensive.) A temporary stadium could be built in the parking lots of some of the nearby office parks to the west of the park, which would also have spectator parking. The park already has several manmade structures (water tanks, radio towers and the like) but would need to have trails built, although it could enhance the current eroded trails, especially along the old ski hill. Snowmaking might be an issue, but it’s no warmer, really, than Mary Cummings.
  • Great Brook Farm State Park has a ski concession and the requisite elevation (barely). Snow making temperatures would not be an issue, but water capacity might. Transportation capacity is limited, although buses from rail lines nearby would be feasible, albeit on narrow roads. In addition, building trails in the park might be an ecological issue in the rural town. 
  • Wachusett Mountain would be a fine location for a Nordic venue. Elevation is available to the northwest of the mountain or east (south of Wachusett Lake) or northeast of Route 140. It would also have room for a sliding facility and jumping area. It is further from Boston, but if combined with snowboarding and some smaller-hill ski events it could justify a four-mile rail spur to serve the complex. Such a spur could be utilized in the future to serve this facility. This would probably be the best option.
  • The Wapack Range has the requisite snow and elevation for Nordic venues, although it would be constrained by infrastructure with steep, narrow roads. Windblown was talked about as a Nordic venue a few years ago, and Mount Watatic in Massachusetts might be suitable a well, but Wachusett seems like a better bet.
  • The Merrimack Valley in New Hampshire would have several potential venues near potential rail transit and current highways.
  • Brattleboro has an existing ski jump which could be used for jumping events. It’s only an hour drive from Wachusett (albeit on Route 2) and the state and feds are putting a lot of money in to upgrading the rail line from Springfield to Vermont, which is within a mile of the ski jump.
  • Further north in New Hampshire, several current ski areas could host events, but obviously are further and have more access issues.
Here’s how the Wachusett area could be set up to host jumping, sliding, Nordic and smaller downhill and snowboard events:

View Wachusett in a larger map

For Alpine the main issue is finding somewhere with 800 meters of elevation. I’d suggest holding snowboarding events at Wachusett, and building a sliding, Nordic and potentially jumping area nearby to justify infrastructure improvements (including a rail spur from the Fitchburg commuter line, which could support one-hour rail serve to Downtown Boston). For downhill events, there are several options, but most are further from Boston:

  • There are a couple of resorts in New England with enough elevation to hold an Olympic-level downhill event (or which would need very minor modifications to meet the criteria). They are, however, rather far from Boston. Killington has more than enough elevation, and its main issue is that it is 25 miles from the nearest Interstate (although compared to the Sea-to-Sky highway in 2010, this is a minor issue). More importantly, Killington’s downhill is not well suited for the event. In Vermont, Sugarbush would also qualify, but it is a more-than-three hour drive from Boston. In Maine, Sugarloaf would be a fine venue, but it is four hours from Boston. No mountain in New Hampshire comes close to the required vertical.
  • There are a few areas which have the requisite elevation for a purpose-built downhill slope but wouldn’t be usable for a variety of reasons. Several of these can be tossed out immediately, such as Tuckerman Ravine (which is USFS very-protected land, has frequent visibility issues, avalanches and will not have a lift constructed, ever), Mount Moosilauke (ecological impediments, Dartmouth owns the whole thing) and Camel’s Hump (ecological). Although in Sapporo they did build a downhill course in a national park, and then let it revegetate after the games.
This leaves areas with 2600 foot downhills, good road connections and nearby downhill areas to serve other events. The first two that stick out for me are near Loon Mountain, the north side of the Winooski River in Vermont and Ascutney:
  • Loon is probably the best option. It is a two-hour, all-interstate drive from Boston (and if rail service were extended to Concord, New Hampshire, it would preclude the need to dramatically limit traffic on the gridlocked southern portion of I-93; the venue itself would be accessible by rail, although it might be a good excuse to extend carpool lanes and use them for bus service during the games) and the current mountain could easily support every event except the downhill. One option would be to build a new trail from the top Scar Ridge just east of Loon to the Kancamagus highway below. This would have a major visual impact, however, and would barely make it to the requisite height requirement. It would, however, require only one new lift from the current summit of Loon. The second Loon option would be to look across the valley. It would require a new trail to be built on the southern flank of Mount Liberty, but this construction would not impinge on the current Osseo hiking trail, and would rise only to about 3800 feet. It would require a stadium below, but this could be built somewhere in the vicinity of the condo developments along the Kancamagus. The hill would have southern exposure, and require snowmaking to guarantee snow. With both there options, the main issue would be ecology and forest service bureaucracy—they both extend in to the fragile subalpine zone and any trees cut would take years to regenerate even if the trail was only used for the one event. 
  • Another option is along the Winooski River in Vermont. Just south of Bolton Valley, there is just enough elevation to run from about 3000 feet to the Winooski River below. It would require a short lift from the Bolton, and would have minimal impact since the construction would be limited to mostly northern hardwood forest areas (rather than subalpine timber, and not forest service land). It is only about three hours from Boston, and all on the interstate, and is on a current passenger rail route as well. It too has southern exposure, however, which would be a consideration for snowmaking. 
  • A third option is Mount Ascutney in Vermont. Ascutney had a ski area in operation until quite recently, but this would not likely suffice for a downhill run. It had a vertical drop of just 1800 feet, and while it could be extended to the top of the mountain, that would only add about 500 feet. The Northwest side of the mountain, where it is located, bottoms out at 800 feet, and with a summit elevation of 3100, it would be hard to squeeze in 800m (2624 feet). The east side, however, holds some promise. The mountain drops off quickly in to the Connecticut River, which is below 400 feet, just enough vertical drop to qualify (and likely the lowest elevation base for an Alpine run in Olympics history). A ski run could be built along the current road and power line which reach the top of the mountain, which would minimize ecological impact. The trail could be built mostly on the northern side of an east-running ridge, so snow retention would not be a major issue. The base of the run would end at Interstate 91, so access would be less of an issue. It’s not a straight shot from Boston but all on highways. There is a nearby rail station in Claremont and the rail line runs across the river, but it would be a push to have service from Boston (the direct rail connection via Concord was abandoned years ago; service could be run via Worcester, Amherst and Brattleboro). 
Obviously this is just a tiny piece of the puzzle—a Boston Olympiad would have many other hurdles to overcome. But as far as bidding for the summer games versus the winter, I think the winter makes much more sense. Most of the in-city venues would be in place; the only requirements would be a speed skating facility (under $100m in recent games, and convertible to a variety of other uses). Conte Forum, Agganis Arena, Conte Forum and Matthews Arena could be used for events like curling and short track, while the TD Garden hosts marquee events like ice hockey and figure skating. (The DCU and Dunkin Donuts centers in Worcester and Providence could also host larger events; they have higher capacities than the venues in town.) The Olympics are fraught with cost overruns and whether it’s a good idea, financially, to host is up for discussion. But Boston would have to build no new venues in the city (in 2014 and 2018, nearly all venues will be newly-built) and wouldn’t have to cut entirely new alpine ski trails (also the case in 2014 and 2018). Thus, the city could, with minimal investment (certainly less than the $50 billion being spent in Sochi), put on a formidable games, and might be the best contender in the US to host.

Putting pencil to paper, and looking at what other recent venues in Western Hemisphere (Salt Lake and Vancouver) have spent, here’s a quick ballpark:

Arena events:
Vancouver: Rogers Arena, capacity 18,000 and others (capacity 6,000 to 14,000)
Salt Lake City: Maverik Center, capacity 10,000
Boston: TD Garden (final games), DCU Center and Dunkin Donuts Center (preliminary games)
Comments: Being a hockey hotbed (moreso than, say, Salt Lake) hockey would likely be well-attended. There would be no issue filling up venues in Worcester and Providence, which are right near rail stations with easy service to Boston. The Garden could be used for skating for most of the games, and then hockey for the final games. Smaller events (curling, short track, ice dancing) could be held at Conte, Matthews and Agganis, and potentially at the Tsongas Arena in Lowell.

Freestyle Skiing / Snowboarding:
Vancouver: Cypress Mountain
Salt Lake City: Deer Valley
Boston: Wachusett
Comments: I assume that Wachusett’s 1000 feet of vertical is enough for these events. They’d probably take over the mountain for two weeks, but I’m sure Wachusett would like the free publicity and infrastructure improvements. Cost to retrofit the mountain: $10m.

Alpine Skiing: See above. If you could hold the downhill somewhere like Sugarbush, you could probably get away with minor additional costs. If you wind up building a new downhill run, it may well run $50m.

Nordic Skiing: The cost to build Soldier Hollow was $22m (about $30m adjusted for inflation). The venue in Whistler included ski jumps and cost $120m.

Jumping: If you build it in Brattleboro, maybe $10m to upgrade the facilities there to Olympic standards. If you have to build it from scratch somewhere like Wachusett, it’s probably another $50m. In Utah, the jumping venue was paired with the sliding venue and cost $75m in the late 1990s, so about $90m today.

Sliding: The Whistler Sliding Centre cost $105m to build. If a Wachusett-area venue could share infrastructure with nearby events, it might cost somewhat less.

Oval: The skating oval in Salt Lake cost $30m, but in Vancouver cost more than $150m. These are the biggest arenas for the winter games, and they’re pretty useless for anything else. It is highly doubtful that the Reggie Lewis Center or even the BCEC could be retrofitted, so you’d have to build this somewhere it could be converted to a better use, or somewhere out of the way enough where you’d want a bunch of indoor sports fields. Figure $100m, minimum.

So for the arenas, you get:

  • Freestyle/Snowboarding: $10m
  • Alpine: $10m-100m
  • Nordic/Jumping/Sliding: $100m-200m, depending on whether you use Brattleboro and how you combine the venues.
  • Oval: $100m-150m
  • Olympic stadium: I think we can all agree on Fenway, figure $30m-40m for that.
So, give-or-take, you have a range of $250m to $500m for the venues. That’s peanuts, compared to Sochi.
But then you have the other expenses. You have to build a village (I’d volunteer the Beacon Park area for this), figure $1b for that (although it can then all become housing, so it might be a wash). My pet project would be grade separating the Grand Junction to allow rapid-transit service from Allston to Kendall to North Station. Figure $1b there, but that dramatically improves mobility and capacity for the T. If you had events in Providence, Worcester and Lowell, it would be a great excuse to electrify and upgrade those commuter rail lines, which would be $2b, but would dramatically improve service on those lines as well.

So that’s $4b of infrastructure. Add in 10% contingency, and it costs you $5b. Oro 10% of Sochi, and you’re not left with a bunch of hotels no one will ever use again.

The cost of doing nothing

The worst traffic in New England is on I-93, going north and south into and out of Boston. When highways were canceled in 1970s and money put towards transit, I-93 was left doing the duty of two highways south of the city (since the Southwest Corridor was nixed) and four to the north (where Routes 2 and 3 were meant to access the city via Cambridge, and Route 95 was to be routed over the Northeast Expressway). The phrase that comes to mind is “three quarts of [something] in to a two quart pail.” There is simply not the roadway capacity to handle the traffic on this road in the morning or evening, there are choke points at other interchanges, and as a result traffic is backed up for several hours each morning and evening, turning a 60 minute drive from Manchester to Boston in to a two- to three-hour ordeal.

The corridor from Concord, N.H. to Boston has frequent bus service, but these buses sit in the same traffic as everybody else until a short carpool lane just to the north of Boston. There is no rail service beyond Lawrence and Lowell, meaning that alternatives to driving require many motorists to travel I-93 to some extent. New Hampshire is spending $800 million to widen its section of the road, and is leaving space for future rail transit and building bus park-and-ride facilities. However, under the previous Republican administration, the state refused to study rail transit service. That vote was reversed recently, and New Hampshire will commission a study of rail service north of the border. *

As usual, opponents come out of the woodwork whenever transportation dollars are slated to be spent on anything other than King Car. “Where are you going to find a few million dollars?” they exclaim, “When you just spent a billion on widening a roadway!” It’s a waste of taxpayer dollars! A boondoggle! It will never pay for itself!

Tell me, again, who is paying the billion dollars to widen 93? Oh, wait, that is a necessary public investment.

There are several salient issues here:

  • Widening the roadway in New Hampshire makes some empirical sense, and going northbound will eliminate a traffic-knotting lane drop at the border. However, the bigger issues have to do with infrastructure further south in Massachusetts not being able to handle more cars from the north. So widening the roadway will not aid many travelers, and may in fact make overall traffic worse where people want to go.
  • I-93 would be a good candidate for a proper HOV, or perhaps HOV/Toll lane, which would aid bus traffic and encourage carpooling, and given the number of buses on I-93 would benefit a high number of road users.
  • In regards to rail, and to echo a frequent sentiment at the California High Speed Rail Blog, the cost of doing nothing is not zero. In other words, if there are no changes made to transportation between New Hampshire and Boston, there are significant costs which New Hampshire will incur. We’ve already seen that the cost of widening I-93 in New Hampshire is nearly $1 billion. What are the costs of poor access to the Boston job market for New Hampshire residents? Of lower property values because of decreased demand due to this limited access? Of time spent in cars in traffic for hours per day? Of tourists who don’t take a weekend trip because of traffic on Friday evening?
First, how widening in New Hampshire doesn’t help traffic down south, or the three quarts in a two quart pail issue. New Hampshire can widen I-93 within its borders all it wants, but driving solely I-93 in New Hampshire gets you from nowhere to nowhere. No offense meant—there are not the major, growing job centers in Southern New Hampshire as there are in Massachusetts. Much of the traffic on I-93 is destined for offices along 495 and 128 in the Bay State, or further south in Boston. Adding space on this section of I-93 will ease some congestion in the state, but it will only lead to more cars traveling southwards in to an existing wall of traffic. The utility of the road for everyone, but especially for New Hampshire commuters, is not enhanced by this project.
Every morning, from 6 a.m. until 9, 10 or even 11, traffic on I-93 grinds to a halt. It first slows in Lawrence, where traffic backing up off of I-495 can slow the commute. Even as the roadway widens from three lanes to four, traffic slows south of 495 as it approaches the wholly inadequate interchange at 128, where traffic backs up off the mainline and through the tight cloverleaf. From there, traffic sometimes eases through the Middlesex Fells, but the roadway then narrows from four lanes to three, one of which is a carpool-only lane. Although traffic no longer backs up off of the Central Artery (which cost, ahem, $15 billion to replace), it’s sufficiently squeezed down that there are only so many cars which can find their way in to the downtown tunnel. Mitigating the 128 interchange is no easy task and will probably cost on the order of $200 million or more. Adding capacity to the roadway through Somerville is a non-starter, and this squeeze will probably never be expanded.
There is a way to increase the utility of the highway without widening it, which is to change the demand model for the roadway by introducing an HOV facility. Right now, there is a 2.5 mile long carpool lane on the southbound side of the roadway from Medford to Boston. This saves carpoolers, and buses, a few minutes on their morning commute, since the lane starts before the Somerville lane drop. However, it is otherwise inadequate in several manners. It provides no access to the Storrow Drive off ramp, which serves major employment centers in Boston and Cambridge. It also reintegrates traffic on to the Central Artery where it has to merge across several lanes to exit. Most importantly, however, it starts far too far south, and during peak hours the traffic jam starts far before the lane becomes available. Oh, right: there’s no HOV lane going northbound.
I-93 is the most heavily-traveled interstate bus corridor in to Boston of any length. Between 7 and 10 each morning, 27 buses travel from 495 to Boston (mostly private carriers from Hanover, Concord, Manchester, Nashua and Andover, Mass.). Another 21—Logan Express and MBTA—enter at or near 128, and 21 more MBTA buses enter the roadway in Medford. Most of these buses sit in traffic with everyone else. Once they access the carpool lane, and assuming they are operating at or near capacity, they transport 3500 people—about 1200 per hour, even though there is only a bus every three minutes. The capacity of a lane full of single occupancy vehicles is only about 1800, and in heavy traffic, it’s less. A better facility might also see buses coming down I-95 shift to 495 and 93 to avoid traffic on Route 1 as well, and encourage more people to ride.
And these are the statistics without any major benefits for ridership. These buses cope with the same traffic as everybody else in the morning and in the evening. Their operators are hamstrung by unpredictable traffic conditions which can cause schedules to run an hour late, or more. And there is no real time savings for riders. There is definitely a cost benefit versus driving, but the buses can’t go any faster than cars on their own. However, an HOV lane the full length of I-93 in Massachusetts would dramatically improve these commutes. It could be built for minimal cost by cannibalizing a lane off the current roadway. It would only require infrequent entrances, and exits before Boston would have to be minimized to preclude the possibility of the mainline backing up in to the HOV lane. It would allow buses to standardize schedules, and attract new ridership based on time savings—many of whom would otherwise be on their own in cars on the road. 
An HOV lane would also attract carpoolers, and to keep the traffic flowing a minimum of three passengers might be feasible during high demand times. This might encourage slugging from these far-flung park-and-rides in to the city. If the time savings were high enough—and at times avoiding traffic on I-93 can save an hour or more—many single-drivers would be keen to grab a couple of new friends for the ride.
Finally, this project could be paid for by tolling the carpool lane depending on the traffic conditions. At certain times of day, allowing single drivers to travel the length of the lane for $10 or more would raise significant revenue and allow those who wanted to avoid traffic to do so. While often derided as “Lexus Lanes” such a system would be optimized first for traffic conditions and then for revenue. If the HOV facility was near capacity from carpools and buses alone, the price could be astronomical. If the rest of the road was mostly free-flowing, it would be low enough to entice a few drivers to save a few minutes without breaking the bank. And revenue from this lane could go to paying for the initial improvements, as well as funding parallel transit options.
Finally, The Cost of Doing Nothing Is Not Zero. Basically, inaction on transit in this corridor will have negative repercussions throughout the region. Quashing a study because rail will require a subsidy (as opposed to $800 million highway widening projects, which apparently pay for themselves) is as bad policy as it is politics. Rail service would provide access to jobs in Boston from New Hampshire, but also access to job sites in New Hampshire from Boston. In theory, rail service would run express from Boston to Lowell in 40 minutes or less, and then provide access to the Spit Brook Road area, Downtown Nashua, Manchester Airport, Downtown Manchester and Concord. With gas prices poised again to break $4 per gallon, precluding access except by car—even to dense, downtown areas—is a good way to stagnate long-term growth.
New Hampshire has to realize that most of its population lives within the “commute-shed” of downtown Boston, and it is inextricably linked to the larger city to the south, even as it derides it with shouts of Taxachusetts and worse. If New Hampshire’s goal is to provide better access on I-93—and it seems that it is—it has to have some sort of alternative from Massachusetts to actually improve the access that I-93 provides. Whether this is a high occupancy facility or rail transit—or some other mode—is a valid question. Whether it should be studied, however, is not.

( * It should be noted that while the Amtrak Downeaster services has several stops in New Hampshire, it is funded solely by the State of Maine. New Hampshire benefits dramatically from the service, which transports hundreds of Granite Staters to Boston every day.)