Category: Transportation
What is the MTA Reinventing, Anyway?
In the last few years New York’s MTA has gone through multiple cycles in which a new head talks of far-reaching reform, while only small incremental steps are taken. The latest is the MTA Transportation Reinvention Commission, which has just released a report detailing all the way the MTA could move forward. Capital New York has covered it and hosts the report in three parts. Despite the florid rhetoric of reinvention, the proposals contained in the report are small-scale, such as reducing waste heat in the tunnels and at the stations on PDF-pp. 43-44 of the first part. At first glance they seem interesting; they are also very far from the reinvention the MTA both needs and claims to be engaging in.
Construction costs are not addressed in the report. On PDF-p. 53 of the first part, it talks about the far-reaching suburban Grand Paris Express project for providing suburb-to-suburb rapid transit. It says nothing of the fact that this 200-km project is scheduled to cost about 27 billion euros in what appears to be today’s money, which is not much more than $150 million per km, about a tenth as much as New York’s subway construction. (Grand Paris Express is either mostly or fully underground, I am not sure.) The worst problem for transit in the New York area is that its construction costs are an order of magnitude too high, but this is not addressed in the report.
Instead of tackling this question, the report prefers to dwell on how to raise money. As is increasingly common in American cities, it proposes creative funding streams, on the last page of the first part and the first six pages of the second part: congestion pricing, cap-and-trade, parking fees, a development fund, value capture. With the exception of congestion pricing, an externality tax for which it makes sense for revenues to go to mitigation of congestion via alternative transportation, all of these suffer from the same problem: they are opaque and narrowly targeted, which turns them into slush funds for power brokers. It’s the same problem as the use of cap-and-trade in California.
One of the most fundamental inventions of modern government is the broad-based tax, on income or consumption. Premodern governments funded themselves out of tariffs and dedicated taxes on specific activities (as do third-world governments today), and this created a lot of economic distortion, since not all activities were equally taxed, and politically powerful actors could influence the system to not tax them. The transparent broad-based tax, deeded to general revenue through a democratic process, has to be spent efficiently, because there are many government departments that are looking for more money and have to argue why they should get it. Moreover, the tax affects nearly all voters, so that cutting the tax is another option the spending programs must compete with. The dedicated fund does neither. If the broad-based tax is the equivalent of market competition, a system of dedicated funds for various government programs is the equivalent of a cartel that divides the market into zones, with each cartel member enjoying a local monopoly. In this way there’s a difference between the hodgepodge of taxes the MTA levies and wants to levy and Ile-de-France’s dedicated 1.4-2.6% payroll tax: the payroll tax directly affects all Francilien workers and employers, and were it wasted, a right-wing liberal politician could win accolades by proposing to cut it, the way New York Republicans are attacking the smaller payroll tax used to fund the MTA.
The proposals of where to spend the money to be raised so opaquely are problematic as well. There is a set of reforms, based on best practices in Continental Europe and Japan, that every urban transit system in the first world should pursue, including in their original countries, where often only some of those aspects happen. These include proof-of-payment fare collection on buses, commuter trains, and all but the busiest subway systems; all-door boarding on buses; mode-neutral fares with free transfers; signal priority and bus lanes on all major bus routes, with physically separated lanes in the most congested parts; a coherent frequent bus network, and high off-peak frequency on all trains; and through-service on commuter rail lines that can be joined to create a coherent S-Bahn or RER system. As far as I can tell, the report ignores all of these, with the exception of the vague sentence, “outfitting local bus routes with SBS features,” which features are unspecified. Instead, new buzzwords like resiliency and redundancy appear throughout the report. Redundancy in particular is a substitute for reliability: the world’s busiest train lines are generally not redundant: if they have parallel alternatives those are relief lines or slower options, and a shutdown would result in a major disruption. Amtrak, too, looks for redundancy, even as the busiest intercity rail line in the world, the Tokaido Shinkansen, has no redundancy, and is only about to get some in the next few decades as JR Central builds the Chuo Shinkansen for relief and for higher speeds.
The only foreigners on the Commission are British, Canadian, and Colombian, which may have something to do with the indifference to best industry practices. Bogota is famous for its BRT system, leveraging its wide roads and low labor costs, and Canada and to a lesser extent the UK have the same problems as the US in terms of best industry practices. Swiss, French, German, Japanese, Spanish, and Korean members might have known better, and might also have been useful in understanding where exactly the cost problems of the US in general and New York in particular come from.
The final major problem with the report, in addition to the indifference to cost, the proposal for reactionary funding sources, and the ignorance of best industry practices, is the continued emphasis on a state of good repair. While a logical goal in the 1980s and 90s, when the MTA was coming off of decades of deferred maintenance, the continued pursuit of the maintenance backlog today raises questions of whether maintenance has been deferred more recently, and whether it is still deferred. More oversight of the MTA is needed, for which the best idea I can think of is changing the cycles of maintenance capital funding from five years, like the rest of the capital plan, to one year. Long-term investment should still be funded over the long term, but maintenance should be funded more regularly, and the backlog should be clarified each year, so that the public can see how each year the backlog is steadily filled while normal replacement continues. This makes it more difficult for MTA chiefs to propose a bold program, fund it by skimping on maintenance, and leave for their next job before the ruse is discovered.
I tag this post under both good categories (“good transit” and “good/interesting studies”) and bad ones (“incompetence” and “shoddy studies”) because there are a lot of good ideas in the report. But none of them rises to the level of reinvention, and even collectively, they represent incremental improvement, of the sort I’d expect of a city with a vigorous capital investment program and industry practices near the world’s cutting edge. New York has neither, and right now it needs to imitate the best performers first.
Toward a Tel Aviv S-Bahn
I have been thinking of alternatives to the current plan for a Tel Aviv Subway for several years now; last year I expounded on some principles for a better plan. As I mentioned last year, Tel Aviv’s subway system should be shaped roughly like the letter E, with a single north-south spine paralleling the rail mainline and three east-west lines intersecting the mainline at the city’s three main train stations. Today I would like to give more details about this system, with special focus on commuter rail. While thinking of how to create an optimal system serving the region’s secondary centers, I came upon an important principle used on the Paris RER and the Zurich S-Bahn, which past posts (including my own) on the subject downplayed in favor of city-center tunnels: namely, it is often correct to deviate from legacy alignments for a few kilometers in order to better serve a secondary center, even if it requires some greenfield tunneling.
Before I go on, I will note that this plan is intended to be politically neutral, in the sense of serving the dense primary and secondary urban centers of Gush Dan regardless of ethnicity, and with only weak regard for income. In my view, if there are anti-government riots in response to police shooting of a young minority, this is not a reason to deny service to the area; on the contrary, denial of social services is what creates the social alienation that contributes to rioting. But more than this, this plan assumes everyone travels to the same destinations, a reasonable approximation in a country with the level of social integration of the US or a monolingual European country, but a problematic one in Israel.
About 18% of Israel’s population is Arab, and another 12% is ultra-Orthodox; both groups are highly segregated, and have their own job centers. On 972Mag’s Hebrew-language sister site, Noam Sheizaf reports that MK Hanin Zoabi (the Knesset’s sole Arab woman), best-known for her incendiary rhetoric against the IDF, criticized the state’s emphasis on developing fast transportation to Tel Aviv on the grounds that Arabs, especially Arab women, typically work close to home. Incomes are much lower than those of mainline Jews as well: I have no ultra-Orthodox data, but making mild assumptions on income distribution within each decile from Central Bureau of Statistics data, per capita income from work is about $6,000 per year for Arabs, a bit higher than Romania excluding Bucharest, and $16,500 for Jews, a bit higher than Greece or Southern Italy. The best American analogy I can think of is the development of dedicated buses for Chinese immigrants in New York City proper and ultra-Orthodox Jews in the New York area, as both groups are very poor and have different centers bypassing Midtown and Lower Manhattan.
With this deliberate decision to ignore ethnic composition in mind, my plan is to build an E-shaped subway system, with the E’s southern leg turning north at its western end to provide a second north-south line in Central Tel Aviv. Here is a link to the map I currently think works the best. The brown lines are an electrified commuter rail system running at very high frequency between Tel Aviv HaHagana and Exhibition Center (currently called Tel Aviv University, though the station is quite far from the center of campus). Observe that the lines deviate from the current network in a few places:
* The circumferential service running along the Eastern Line loops to serve Elad better.
* There is a new branch into Kafr Qassem, passing much closer to Rosh HaAyin’s built-up area than the current Rosh HaAyin North station does.
* The Kfar Saba branch is completely redone. There are plans to connect it to the Coastal Railway concurrently with building a freeway along the same alignment, going due west from its current terminus alongside Route 531. The freeway should be scrapped – Israel is building too many of them, and insists of bundling every transit project with a freeway (even the currently proposed Red Line is planned to come together with a freeway tunnel through an alignment near Jaffa Road in South Tel Aviv, forcing the line to go deeper and raising its costs). Moreover, the connection west of Kfar Saba should be more direct. Conversely, east of Kfar Saba there is a right-of-way that can be used to send trains up to Tira, and perhaps farther into the Triangle, into Tayibe or Qalansawe.
* There is a new branch to Glilot and Herzliya Pituah, an edge city located a bit too far from the Herzliya train station to be a comfortable walk, especially along the wide, pedestrian-hostile access road.
* The line enters Netanya along a new alignment, with a short tunnel; the current Netanya station is at the edge of the built-up area.
* There is a reactivated branch serving Tsrifin.
* The route through Rishon LeZion avoids the current plans to connect Rishonim Station (Kiryat Simha on my map, to avoid confusing with Ramat HaSharon Rishonim) to the Ashdod Branch via Route 431, avoiding the Rishon LeZion built-up area. Rishon is a sprawling suburb, but has more than 200,000 people, and secondary centers; it is better to spend a bit more money, tunneling under the center of the city and going above-ground to its west to serve the College of Management Academic Studies, Israel’s largest independent (i.e. non-university) college.
These short tunnels are in line with construction in European cities: the Paris RER’s centerpiece is the connecting tunnels in central Paris, but as seen on this map, which includes chronology, the Charles-de-Gaulle branch opened in 1976, shortly before the RER B it connects to, and the Disneyland branch opened in 1977, concurrently with the RER A. The Zurich S-Bahn includes short greenfield tunnels to access the airport from both directions. The Stockholm commuter rail system includes a tunneled loop serving Arlanda, which was built for the Arlanda Express and then extended and used by the regular commuter trains. Usually these new tunnels serve airports or other new centers such as Disneyland, since the old secondary centers already have legacy lines, but in Israel, most towns’ train stations are located at the edge of the built-up area rather than in the center, and in the larger secondary cities, this justifies some additional tunneling.
On the same principle, the Jabotinsky subway line, which is otherwise elevated outside the Tel Aviv core, tunnels to reach central Petah Tikva, in lieu of the current plan to skirt the center of the city and go in tram mode to Petah Tikva Central Bus Station.
I expect most ridership, and by far most of the cost, to come from the subway lines, colored red, green, blue, and yellow; I call them subways, but out of the system’s 60 km, 27 are above ground and only 33 are underground, mainly in Tel Aviv proper and in the parts of Ramat Gan and Givatayim that do not have wide roads for a right-of-way. I chose names for political reasons: the north-south line is called the Jaffa Line since it passes through Jaffa, a low-income left-wing Arab area; the northern leg of the E is called the Jabotinsky Line since it runs largely along streets named after Zeev Jabotinsky, founder of Revisionist (right-wing) Zionism; the central leg of the E is called HaShalom Line since it intersects the mainline at HaShalom train station, and the peace process (shalom in Hebrew) is a cornerstone of the Zionist left; and the southern leg of the E is called HaTikva Line since it passes through HaTikva, a low-income right-wing Mizrahi neighborhood. I tried to steer clear of politics in the route choice: only the choice of names, constrained by the need to refer to features of the lines, is political.
In the remainder of the post, I will deal with possible objections to the proposal, and with various doubts and drawbacks.
1. Probably the biggest objection I expect is that the system skirts the proposed Tel Aviv CBD, which is District 6 on this map. Unlike the current plan, there are no tunnels under Namir Road, but rather the tunnels are farther west, in the city’s traditional center. This is deliberate. I do not have bus traffic data, but I do have frequency data for the most frequent buses, expressed in daily departures in both directions. It is in Hebrew on the Israeli Bike-to-Bus Rider blog; the key is that a gold medal denotes at least 4 buses per hour, a bronze one denotes at least 3, a silver one denotes at least 3 and at least 4 at and on the shoulders of the peak, and a V on the left column denotes at least 6 at rush hour. The bus route numbers are on the second column from the right. See also this frequent bus map to match route numbers to streets.
While I criticized the use of bus corridors for subway planning last year, noting that buses serve the wider Jerusalem Boulevard through Jaffa and not the narrower but more centrally-located Yefet Street, the map provides a rough guide to which regions and which directions of travel have the most demand. North-south travel along Ben Yehuda, Dizengoff, and Ibn Gabirol Streets and Namir Road is very popular. Ben Yehuda’s routes 4, 104, and 204, which HaTikva Line roughly parallels, have 642 buses per day. Dizengoff’s routes 5, 39, 72, 129, 172, and 239 have 1,071. Route 9, which runs along Ben Yehuda and Dizengoff in a one-way pair, has 162. Ibn Gabirol’s routes 24, 25, 125, 126, 189, and 289 have 986. And Namir Road’s routes 1, 40, 42, 51, 60, 71, 160, 171, 240, and 271 have 1,726. Despite the large number of buses on Namir, these buses closely parallel mainline rail, and moreover, there are 65% more buses on Ibn Gabirol and points west.
2. My plan ignores many active plans made by the state. This is on purpose: until such projects as combined freeway-rail lines are built, they should be opposed, since the road construction will ensure connectivity by road will be faster than by rail, frustrating any attempt to maintain a high public transit mode share. To my understanding, the most expensive portions of the planned subway, namely the underground parts, have not been built, and on the contrary there are constant schedule and budget slips; the current timetable calls for the completion of the Red Line in 2023, and the budget has slipped from 10.7 to 14 to 17 billion shekels; this is $200 million/km, accounting for PPP but not future inflation (if Israel holds to 2% inflation, it will be about $180 million/km), for a line that’s only 43% underground.
3. Four-tracking the mainline rail route through Tel Aviv is going to be expensive, since it requires building over or rerouting the Ayalon River. In the long run, rail growth makes such construction necessary: Israel’s economic geography forces all travel between the north and the south to go through or right next to Tel Aviv, which means potential travel demand is higher than through Stockholm, which is currently four-tracking its main route through T-Centralen to provide for both additional commuter rail and intercity rail service.
In the short run, there are two ways to cut initial costs. First, it may be the case that there is room for four tracks along the Ayalon right-of-way, as long as only two are served by station platforms. If that is true, then HaShalom should be reconfigured as a local station, with two nonstop tracks, while all trains should continue to stop at Tel Aviv Center and HaHagana, both of which already have more than 4 tracks. While HaShalom is Israel’s second busiest train station (see file here, shared by a forum member back in 2008: the leftmost column is total daily entries and exits), high-frequency local commuter rail service connecting it with Tel Aviv Center and HaHagana is an acceptable substitute if it saves a lot of money.
And second, Israel Railways runs very inefficiently, partly because of single-tracking and partly because of the use of slow-accelerating diesel locomotives. Peak traffic on the two-track mainline, excluding the third track (which is run as a captive single-track commuter line), is still in the single digits of trains per hour. While my plan calls for 10-minute peak frequencies on each of 5 branches, I believe that for a long while, several branches could make do with 20 minutes; with high-capacity signaling, and the use of the third track for emergencies if a train is late, 30 trains per hour are possible, permitting space for commuter trains as well as the four hourly intercity trains to Haifa, two to Beer Sheva, and future trains to Jerusalem.
4. Too much service to the north. The way the map is presented, without extra proposed extensions, the best-served part is District 6, which has almost no residential population: counting transfer stations twice and jurisdiction-boundary stations as belonging half to each jurisdiction, it has 1.5 stations for 4,600 residents, or 1 per 3,000. But the second best is District 3, the Old North, and even Herzliya is better-served than District 8, South Tel Aviv. It’s an unfortunate fact that Herzliya’s train station is located on a pedestrian-hostile road, between the two centers of Herzliya and Herzliya Pituah and beyond walking distance to both, requiring considerable additional construction; but it’s also possible to either eliminate the Herzliya Pituah commuter rail branch or cut the Jaffa Line to KKL Junction. The Old North needs this much service, because of the high demand for bus service along both Dizengoff/Ben Yehuda and Ibn Gabirol, as well as the presence of several major retail and entertainment centers, such as the Port, the Marina and waterfront hotels, and Dizengoff Center, making the neighborhood more than just residential.
5. Not enough service to the south, especially Holon. The official plan calls for building a second line going north-south from Tel Aviv University to Holon and Rishon LeZion, giving two north-south branches to the south (including the initial one to Bat Yam) versus one in my plan. I admit that the indirect service to Holon is problematic, but counter that the city is substantially less dense than Bat Yam, and moreover the east-west orientation of the Jaffa Line connects the two cities while giving Holon a transfer to a direct mainline rail connection to Tel Aviv. Rishon LeZion is completely cut from my subway plan, but gains a centrally-located commuter rail station.
South Tel Aviv has relatively little service, too, since the Jaffa Line and HaTikva Line have stops just outside it. The alternative I proposed within the map file, in which HaShalom Line is extended two more stops to Old Jaffa while the Jaffa Line is rerouted along the more southeasterly Shalma Road alignment, provides several more South Tel Aviv stations and makes Central Bus Station the Jaffa/HaTikva transfer point, at the cost of a detour that lengthens end-to-end trips as well as about 3 km of additional tunneling. In either case, the center of South Tel Aviv today is close enough to Central Bus Station to be serviceable, even if it’s only by one line rather than two.
6. Tight timed transfers. Unlike the simply-connected lines branching to the north, the lines to the south have multiple mergers, to be dealt with using timed transfers at Lod and Lod Junction. The plan is, using a 20-minute clockface schedule, to have Airport Branch trains leave 4 minutes before mainline Lod trains, be slowed down by the airport detour and the extra stops, and have a timed transfer with the Eastern Line at Lod Junction, which then has a timed transfer at Lod. This corresponds to a 4-minute slowdown as planned, but requires two successive transfers. I do not know to what extent this is robust, although given relatively low frequency per branch, I do not think it’s a trouble on a railroad with reliable trains and level boarding. Israel’s current diesel rolling stock is unreliable, but this can be fixed with EMUs, and there’s already level boarding.
7. Station locations. I tried keeping station spacing to one per kilometer, but ended up finding more good locations, so station spacing is slightly narrower. More fundamentally, at several spots, mainly east of Ayalon, I chose station locations based on destinations rather than street intersections. The tradeoff is that the destinations can provide better waiting spots than an intersection of two wide roads built for high car speeds, and by definition have something within walking distance, but street intersections make it easier to run connecting buses.
8. Quibbles on termini. These I am happy to be convinced about, including the eastern termini of HaTikva Line (on Twitter, Moshe Schorr proposes avoiding Kiryat Ono, and instead swerving southeast to serve Or Yehuda and Yehud), the southern terminus in Ashdod (it is possible for trains to enter the city on viaducts and serve it more centrally), and extensions or cutbacks to lines already mentioned.
9. Quibbles on routes. As with the termini, I am happy to make changes. These include the route through Ramat Aviv (the current map provides a stop on the south side of the Tel Aviv University campus, but it’s possible to instead take two sharp turns and serve Ramat Aviv Mall), and the routes of HaShalom and HaTikva lines through Ramat Gan and Givatayim, which could both be moved south. There are no compelling destinations west of the eastern anchors at Bar Ilan and the Bakum/Kiryat Ono and east of the neighborhoods abutting Ayalon such as HaTikva, which makes the routes more flexible.
The first two objections are the most fundamental, and the ones I feel the most strongly I am right again. The others are smaller changes, in descending order of importance, and do not conflict with the concept of an E-shaped rapid transit system supporting a single frequent S-Bahn spine.
Pedestrian Observations from Central Stockholm
I like Stockholm. There’s something reassuringly familiar about it, despite the language barrier, which I think comes from the fact that the Central Stockholm housing stock is of similar vintage as the residential parts of Manhattan. It even avoids New York’s most annoying (to me) architectural tic, the exposed brick. The buildings here are similar in style to the ones in New York (and more generally northern Europe), but most have smooth exterior, with enough variation of colors between buildings to make it interesting.
The streets here vary a lot in width, but outside the older sections of the city, they are never very narrow. In Gamla Stan (“the old town”), the medieval core of the city that is now a tourist ghetto, complete with stores selling Swedish flags or English-language books, there are some pedestrianized streets with single-digit building-to-building width. But in my part of the city – Roslagstull, near the outer end of what’s considered Central Stockholm – the street width ranges are almost identical to those of Manhattan. My street, Birger Jarlsgatan, is about 30 meters wide, while less important parallel streets are about 15 or 20. Like the rest of city center, it’s lined with almost uniformly mid-rise buildings, six to seven stories tall. See photos here, from Södermalm, and here, from Regeringsgatan, a street that for a portion of its length is elevated over intersecting streets.
A feature of Stockholm streets that I have not seen in other cities is that on-sidewalk bike lanes. While the overall sidewalk width on Birger Jarlsgatan is generous, the sidewalk is broken by the bike lane. The inner side of the bike lane is interrupted by trees, and the outer side by sidewalk cafes, and as a result, sometimes walking in the bike lane is unavoidable if one wishes to avoid walking in zigzags. In any case, cyclist traffic does not seem to be heavy; there is much more pedestrian traffic.
Crossing the street is rarely difficult. There are beg buttons at intersections, but the pedestrian light will turn green even without pressing them. The stoplight phasing is simple: most of Central Stockholm is on one of several grids, and even at intersections of two-way streets (one-way streets are uncommon, at least around Roslagstull), there are only two phases per stoplight cycle. Without grade-separated freeways in the city core, the worst streets for the pedestrians are the occasional freeway-like structure, or one of several excessively wide roads. I walk to work on one of those roads, Valhallavägen, and during the daytime, the cars’ noise and air pollution are uncomfortable unless I walk through the parking lots behind the street or the bus bay in its median.
The transit system is useful, though I almost never take it. This is a combination of very high fares (with my pay-per-ride smartcard, I pay 25 kronor per ride, about PPP$2.70) and a city core that’s small enough and pedestrian-friendly enough that I can get around most of it on foot. The pedestrian orientation of the streets matters: my apartment is 2.3 km from the CBD mall and 1.7 km from Stockholm University; but I will walk to the mall, whereas to get to and from a conference at SU, I didn’t walk on Roslagsvägen (which is almost a full freeway) but instead took the subway from my university, KTH, which is more centrally located within the city.
Of course, most people in the region don’t live in Central Stockholm, and for them the T-bana is a lifeline. Subway ridership here, excluding commuter rail, is about 900,000 per day (not weekday), not much lower than on the U-Bahns of much larger Berlin and Munich. As a curiosity, there are many light rail lines that connect outlying suburbs to a T-bana station, requiring a transfer to get to the CBD; the busiest, Roslagsbanan, is a narrow-gauge commuter rail system terminating next to KTH, with one T-bana branch, the T14, running parallel to it for a few stops before terminating. This is in addition to a mainline commuter rail system, with 267,000 daily passengers; this ratio of about one commuter rail rider to three subway riders is higher than anything most (see first two comments) in North America, but is much lower than in major European transit cities like Paris and London, where commuter rail and the metro have roughly equal ridership levels. Among the transit projects under construction in Stockholm is a new rail tunnel, which will increase the capacity of commuter rail.
Dispersing Expensive Centers: Edge City Version
This is somewhat of an addendum to my post before about dispersal of urban networks toward cheaper cities. I addressed the question of dispersal from rich, expensive metro areas, especially San Francisco, to cheaper ones, as a way of dealing with high housing prices. But more common is dispersal within metro areas: gentrification spilling from a rebounding neighborhood to adjacent neighborhoods that remain cheaper, and office space spilling from the primary CBD to the edge cities. I am going to address the latter issue in this post.
CBDs are expensive. They have intense demand for office space, as well as high-end retail and hotels. In many cities, there’s demand for office space even at the construction costs of supertall skyscrapers, going up to about $5,000-6,000 per square meter in privately-built New York towers. Zoning regimes resist the height required to accommodate everyone, and this is worse in Europe than in North America and high-income East Asia. Paris proper has many towers just above the 100 meter mark, but only three above 120. On a list of the tallest buildings in Sweden, not a single one above 100 meters is in central Stockholm, and the tallest within the zone are not in the CBD but in Södermalm; compare this with Vancouver, a metro area of similar size. But in the US, too, expanding CBDs is difficult in the face of neighborhood opposition, even in Manhattan.
The solution many cities have adopted is to put the skyscrapers in edge cities. Paris famously built La Defense, which has far more skyscrapers than the city proper does; Stockholm is building skyscrapers in Kista; London built Canary Wharf; Washington, the major US city with the tightest CBD height limits, sprouted skyscraper clusters in several suburbs in Maryland and Virginia. Ryan Avent proposed this as one solution to NIMBYism: in new-build areas, there are few residents who could oppose the new development. In contrast, near zoning-constrained CBDs, not only are there many residents, but also the land is so desirable that they are typically high-income, which means they have the most political power to oppose new development.
The problem with this solution is that those secondary CBDs are not public transit hubs. In Paris, this has created an east-west disparity, in which people from (typically wealthy) western suburbs can easily reach La Defense, whereas people from poorer ones need to take long RER trips and often make multiple transfers. In every transit city, the CBD is unique in that it can be reached from anywhere. To give similar accessibility to a secondary center, massive investment is required; Paris is spending tens of billions of euros on circumferential regional rail lines to improve suburb-to-suburb connectivity, expand access in the eastern suburbs, and ameliorate the east-west imbalance (see for example isochrones on PDF-pp. 20-21 of the links here). Those lines are going to be well-patronized: the estimate is 2 million daily passengers. And yet, the east-west imbalance, if nothing else, would be a lesser problem if instead of building La Defense, Paris had built up Les Halles.
The situation in other cities is similar. Kista is on one branch of one subway line, two stops away from its outer terminus. Living in Central Stockholm, my coworkers and I can get to KTH on foot or by bike, but a coworker who teaches at KTH’s satellite campus in Kista has a long commute involving circumferential buses (taking the subway and changing at T-Central would be even longer because of the detour). While many individual sub-neighborhoods of Central Stockholm are quite dense, the overall density in the center is not particularly high, certainly not by the standards of Paris or New York. A similar problem happens in Washington, where the biggest edge city cluster, Tysons Corner, is traditionally auto-oriented and was only just connected to Metro, on a branch. This always affects poorer people the worst, as they can’t afford to live in the CBD, where there is easy access to all secondary destination, and often are pushed to suburbs with long commutes.
There is a political economy problem here, as is usually the case with zoning. (Although in the largest cities skyscraper heights are pushing beyond the point of constant marginal costs, purchase prices at least in New York are much higher than construction costs.) The people living near CBDs, as noted before, are usually rich. The displacement of office space to the suburbs affects them the least, for three reasons. First, if they desire work within walking distance or short subway distance, they can have it, since their firms typically make enough money to afford CBD office rents. Second, since they live in the transit hub, they can access suburban jobs in any direction. And third, if the transit options are lacking, they can afford cars, although of course traffic and parking remain problematic. Against their lack of incentive to support CBD office space, they have reasons to support the status quo: the high rents keep it exclusive and push poor people away, and often the traditional mid-rise buildings are genuinely more aesthetic than skyscrapers, especially ones built in modernist style.
These concerns are somewhat muted in the US, where rich people decamped for the suburbs throughout the 20th century, and have supported zoning that mandates single-family housing in the suburbs, instead of staying in the city and supporting zoning that keeps the city mid-rise. This may have a lot to do with the formation of high-rise downtowns in American cities of such size that in Europe they’d be essentially skyscraper-free.
However, what’s worse in the US is the possibility of short car-free commutes to the edge cities. Where La Defense is flanked by suburbs with high residential density, and Kista’s office blocks are adjacent to medium-density housing projects for working- and middle-class people, American edge cities are usually surrounded by low-density sprawl, where they are easily accessible by car but not by any other mode of transportation. This is because the American edge cities were usually not planned to be this way, but instead arose from intersections of freeways, and developed only after the residential suburbs did. As those edge cities are usually in rich areas, the residents again successfully resist new development; this is the point made in Edgeless Cities, which notes that, in major US metro areas, growth has been less in recognizable edge cities and more in lower-density edgeless cities.
As with the possibility of dispersing innovation clusters from rich, expensive metro areas to poorer and cheaper ones, the already-occurring dispersal from city centers to edge and subsequently edgeless cities has negative effects. It lengthens transit commutes. Although in Tokyo, long commutes first arose as a problem of a monocentric CBD, and the city developed secondary CBDs as a solution, the situation in European cities an order of magnitude smaller is very different. It worsens housing segregation: the development of an edge city tends to be in the direction of the favored quarter, since that’s where the senior managers live, and conversely, higher-income workers can choose to move nearby for the short commute. Although nearly all metro areas have favored quarters, decentralization of jobs thus tends to lengthen the commutes of poor people more than those of rich people.
This is not quite the same as what happens when entire metro areas are forced to disperse due to housing cost. The agglomerations generally stay intact, since an entire industry can move in the same direction: smaller cities have just one major favored quarter with edge cities, and larger ones still only have a few, so that industries can specialize, for example in New York, biotech and health care cluster in the Edison-Woodbridge-New Brunswick edge city. Moreover, the specialized workers are usually high-income enough that they can stay in the central city or migrate to the favored quarter. San Francisco’s programmers are not forced to move individually to faraway poor neighborhoods; they move in larger numbers to ones near already gentrifying ones, spurring a new wave of gentrification in the process; were they to move alone, they’d lose the access to the tech shuttles. The negative effects are predominantly not on richer people, but on poorer people.
The problem is that even among the poor, there is little short-term benefit from supporting upzoning. If Paris, London, and Stockholm liberalize housing and office construction, the first towers built of both kinds will be luxury, because of the large backlogs of people who would like to move in and are willing to pay far in excess of construction costs. I am going to develop this point further in two posts, on what is best called NITBYism – Not In Their Backyard – but this means that the incentive for poor and peripheral populations is not to care too much about development in rich centers. The marginal additional building in a rich city center is going to go to the upper middle class; sufficient construction would trickle to the middle class; only extensive construction would serve the working class, and then not all of it.
In the US, the marginal additional building may actually displace poor people, if no new construction is allowed, simply by removing low-income apartments. It may even create local demand for high-income housing, for example by signaling that the neighborhood has improved. In San Francisco, this is compounded by the tech shuttles, as a critical mass of Silicon Valley-bound residents can justify running shuttles, creating demand for more high-income housing.
The amount of construction required to benefit the bottom half of the national income distribution is likely to be massive. This is especially true in France and the UK, which have sharp income differences between the capital and the rest of the country; their backlogs of people who would like to move to the capital are likely in the millions, possibly the high millions. Such massive construction is beyond the pale of political reality: the current high-income resident population is simply not going to allow it – when forced to share a building with the working class, it pushes for poor doors, so why would it want zoning that would reduce the market-rate rent to what the working class would afford? The only political possibility in the short run is partial plans, but these are not going to be of partial use to the working class, but of no use to it, benefiting the middle class instead. As a result, there is no push by the working class and its social democratic political organs to liberalize construction, nor by the small-is-beautiful green movement.
Ultimately, the attempt to bypass restrictions on urban CBD formation by building edge cities, like every other kludge, is doomed to failure. The fundamental problem of rich people making it illegal to build housing nearby is not solved, and is often made even worse. The commutes get worse, and the inequality in commutes between the rich and the poor grows. Office space gets built, where otherwise it would spread along a larger share of the medium-rise CBD, but for most workers, this is not an improvement, and the environmental effects of more driving have negative consequences globally. And once city center is abandoned to the rich, there is no significant political force that can rectify the situation. What seems like a workaround and an acceptable compromise only makes the situation worse.
Putting Rail Lines in Highway Medians
North Americans are in love with trains that go in highway medians. A large fraction of urban rail construction since World War Two, both light rail and full metro, has used highway medians as cheap at-grade rights-of-way to extend train service, often deep into the suburbs. Some proposed longer-range lines are supposed to go in medians as well: Florida had reserved space in the I-4 median for Orlando-Tampa high-speed rail, and Xpress West planned to go from Las Vegas to the outskirts of the Los Angeles area in the I-15 median. The Texas Central Railway, a private group backed by JR Central planning high-speed rail between Dallas and Houston, is considering several alignments, but markets the route as following I-45 (no mention of median) in some public discussions. In nearly all cases, both urban and intercity, it borders on incompetent to design rail lines in highway medians; intercity lines frequently follow highways on one side, but even that tends to be overrated in American discussions in my experience.
Urban Rail
For urban rail, the reason to use highways is that, in most of North America, they’re everywhere, and they’re usually equipped with generous medians and shoulders, allowing relatively cheap placement of rail tracks. Of note, this is generally not the cheapest option: construction on extant (often disused) rail rights-of-way tends to be cheaper. However, in many cases, a rail right-of-way is unavailable, hosts heavy freight traffic, has been permanently turned into a trail, or has commuter trains without integration into the rest of the urban transit network. Examples include the Dan Ryan half of the Red Line and both halves of the Blue Line in Chicago, the Orange and Silver Lines in Washington, the outer ends of BART, the Spadina line in Toronto, and several light rail lines. Often they run on one side of the road, but more frequently they’re in the median, which was often reserved for it when the road was built (as in Chicago and Calgary).
The problem is that nobody wants to live, work, or hang out next to a busy grade-separated road. Living or working a kilometer or two away, with easy access by car, is great for the driver, but within close walking distance, there is just too much noise, pollution, and blight, and the pedestrian environment is unwelcoming. The transit-oriented development in Metrotown and Arlington could not have happened next to a freeway. Christof Spieler frames this as a decision of spending more money on routing trains near where people live versus staying on the easy rights-of-way. But this isn’t quite right: the Expo Line in Vancouver was assembled out of an interurban right-of-way and a city center tunnel, both out of service; the line’s high ridership comes from subsequent development next to Metrotown and other stations.
Other times, the routing comes from a deliberate decision to integrate the trains with cars, with large park-and-rides at the ends. This is common on newer light rail systems in the US (though not Canada, as Calgary prefers integration with connecting buses) and in the Washington and San Francisco suburbs. This makes things even worse, by extending the radius within which the environment is built for cars rather than for people, and by encouraging the same park-and-ride construction elsewhere, along abandoned railroads and greenfield routes, where the preexisting environment is not car-oriented.
I do not want to categorically say that cities should never build urban rail alongside highways. But I cannot think of a single example in which this was done right. Calgary is a marginal case: it did build light rail along highways, and had some success with transit-oriented development, but those highways are arterials rather than freeways, and this makes the pedestrian environment somewhat better.
The situation is somewhat different for suburban rail, but usually the scale of suburban rail is such that there’s not much new construction, only reappropriation of old lines. These lines are long and the environments low-density, making it hard justify the costs of new lines in most cases. Where new suburban rail is built, for examples the Grand Paris Express, and various airport connectors, it is typically in environments with such expected traffic density that the rules for urban rail apply, and we tend to see more underground construction or usage of extant rights-of-way.
Intercity Rail
The reasons favoring highway alignments intercity rail in the US are somewhat different. Tellingly, HSR in Europe is frequently twinned with motorways. It is not about integration with cars, since those alignments are rarely if ever meant to have major stops in their middle. Instead, it’s about picking a pre-impacted alignment, where there are fewer property takings and fewer NIMBYs. This logic is sound, but I often see Americans take it to extremes when discussing HSR.
The first problem is that roads are almost never as straight as HSR needs to be. The design standards I have seen after briefly Googling give the radius of a motorway capable of about 120 km/h as, at a minimum, 500-700 meters. With these curves, trains, too, are capable of achieving about 120 km/h – less at 500 meters without tilting, more at 700 meters with tilting. The most recent high-speed lines are built with a minimum curve radius of 7 km; about the absolute minimum that can be done, with design compromises and tilting trains, is 4 km. This implies that the trains have to deviate from the motorway alignment whenever it curves. In flat regions the road curves are much gentler than the minimum, but still too sharp for full-speed running. Both Florida HSR and Xpress West noted that the trains would have to slow down whenever the Interstate curved, because the need to run in the median would prevent them from curving gently enough to maintain full speed.
Of note, the European examples of HSR running in motorway alignments have it running alongside the roads, not in the medians. I invite the reader to spend a few minutes following French LGVs on Google Maps and seeing this. This is because there invariably have to be small deviations from the road, which in a rural area are trivial when one runs next to the road but require viaducts when one runs between the road’s two carriages.
There may also be an issue regarding reusing the Interstates. To transit supporters who view HSR as a replacement for freeways, this has an element of poetic justice, or just plain practical reuse of infrastructure they think is obsolete. I chanced upon this while looking up Interstate design standards, but I’ve seen similar proposals elsewhere, as well as dissimilar proposals making use of interstate terminology, as a reminder of past national greatness. It comes from the same place as proposals to reuse auto factories to produce rolling stock: there’s a romantic aspect in addition to or instead of an economic one.
But the most fundamental problem is that the contentious experiences of the freeway revolts and modern-day NIMBYism have soured Americans on any process that involves brazen takings. What I mean by brazen is that carving a new right-of-way, especially through a populated area, looks obvious on a map. In contrast, sticking to a preexisting right-of-way and incrementally widening it or straightening curves is less controversial, even when it involves eminent domain as well, and opposition remains much more local, based on the specific properties being taken, rather than stated in general principles. I am not completely sure why this is so; my suspicion is that widening and straightening are more easily justified as things that must be done, whereas a new right-of-way looks gratuitous.
In either way, Americans have convinced themselves that NIMBYs are a major obstacle to infrastructure construction. While zoning is a notoriously NIMBY-prone process, infrastructure often isn’t. In the English common law world, expropriations are if anything easier than in France, where farmers are especially powerful, or Japan, where rioters threatened to block the construction of Narita Airport. NIMBYs are good at getting their names out in the media, but when it comes to blocking construction, they are relatively powerless; California HSR is facing NIMBYs in the Central Valley, many of whom are conservative and politically opposed to the project regardless of local impact, but so far they have not managed to delay construction.
However, NIMBYs are a convenient bogeyman for public projects, as their motives are openly selfish. They give charismatic, authoritarian leaders the opportunity to portray their infrastructure projects as battles between the common good and backward-looking parochial interests. As I’ve noted multiple times before, New York’s livable streets community (which is similar politically to the set of HSR supporters in the US) tends to overblow the importance of NIMBYs to the point of seeing NIMBYs even when the concerns have nothing to do with NIMBYism: see, for example, the reaction to the opposition of two Harlem politicians to a plan to speed up only the whitest bus route through the neighborhood.
Coordinated Planning and High-Speed Rail
High-speed rail and rapid transit both change economic geography, in that they compress distances along the lines built, emphasizing connections along the lines at the expense of ones perpendicular to them. I’ve written about this before, giving the example of the division of Uptown Manhattan into East and West Sides. In contrast to the similar implications for economic geography, we see different political treatment of transportation planning: rapid transit is usually planned centrally within a city, together with lower-capacity perpendicular forms of public transit, but there is less centralized planning of high-speed rail and connecting legacy lines.
It’s against this background that I’ve read two recent posts on Itinerant Urbanist, one advocating Northeast-wide intercity rail planning, and one expressing skepticism of plans to run trains from New York to Pittsfield along the Housatonic Railroad, whose southern end hosts the Danbury Branch. In the second post, Sandy shows how, even today, it is faster to get from New York to Pittsfield via Albany, along existing Amtrak routes, than it could be via the curvy Housatonic. The trains from New York to Albany are not HSR, but are some of the fastest in the US outside the Northeast Corridor, and that’s enough to obviate the need for some adjacent lines. But we can extend this analysis further, looking at potential HSR routes and identifying the effect on other regional and intercity lines mentioned in Sandy’s first post.
For our main example, consider Providence-Worcester. There is a direct line, the Providence and Worcester mainline, which hosts no passenger trains. I have previously called for running passenger service on the southern 25 km of the line, from Providence to Woonsocket, and integrating the schedules with MBTA trains to Boston and future HSR; in 2009, the Providence Foundation made a similar proposal, finding that it was possible to slot a reasonable frequency of in-state regional trains between the Providence and Worcester freight trains. Superficially, one might think that trains should not turn at Woonsocket, but go all the way to Worcester, a distance of 69 km, providing a key crosstown link in a New England-wide rail network.
The problem is that the presence of HSR makes the line completely useless for end-to-end traffic. HSR averages between 180 and 260 km/h, whereas regional trains average between 50 and 90, with a few trains overlapping with intercity rail going up to 120. This makes it worthwhile to go two to three times as long as the most direct route, if this can be done on high-speed lines.
It’s 70 km from Providence to Boston; from Boston to Worcester, it’s 71 along the present Worcester Line, while an HSR line following I-90 would be about 65, serving Worcester at an outlying station at the intersection with Route 122 (and the Providence and Worcester line), 6 km outside the legacy station. My attempt to work out a schedule for Providence-Boston gives about 20.5 minutes for nonstop HSR; Boston-Worcester is probably similar, giving 41 minutes plus a short transfer time. (Trains with intermediate stops would stop at Back Bay, and if the transfer can happen there, then it saves about 3 minutes total.) Let’s say the transfers at Boston are not optimized, and the total travel time is 50 minutes.
It is not easy to achieve this travel time on the legacy Providence and Worcester line: 69 km in 50 minutes is 83 km/h, and 63 km (from Providence to I-90 and Route 122) is 76. The latter speed is very ambitious, and the former even more so. While there are regional lines in New England that could approach 100, this is not one of them. The line hosts some freight traffic, so it requires additional sidings if passenger trains go at intercity rail speeds and not at regional rail speeds, which are similar to freight speeds. There is a significant commuter market at the Providence end, requiring more stops in Providence and its inner suburbs: the end-to-end travel time in the schedule I constructed for Providence-Woonsocket is 26 minutes, an average speed of 59 km/h. To get to I-90 in 50 minutes, trains would need to average 94 km/h north of Woonsocket; achieving this makes it almost impossible to stop anywhere in Massachusetts except Worcester, which defeats the purpose of the line. Worcester-Woonsocket is not important enough a travel market to reopen a passenger rail line for. For the same reason, there is no hope of achieving sufficient speed by including a mix of local and express trains: there’s not enough demand to support multiple service patterns.
The Providence-Worcester example is somewhat unfair in that it’s unlikely such a line could be activated without interstate cooperation in intercity rail planning. The same cooperation that could restore service on the Providence and Worcester line would first push for faster intercity trains on the Northeast Corridor, which would be the first step in obviating this direct line. I bring this up because it’s a very clean example of how the presence of HSR allows for circuitous routings on some city pairs, and how this should be reflected in rail planning. There are less clean examples, pitting a unified system with HSR as a trunk and branches feeding the trunk against potential in-state projects and priorities:
1. Unless HSR fares are designed to discourage this, the fastest way to get to New York from suburbs far out along the New Haven Line, and to a lesser extent the Northeast Corridor Line in New Jersey, would be to take commuter rail to New Haven or Trenton and then backtrack on HSR. This changes the optimal service patterns, away from express trains to New York and toward local trains in the outer service area, and this in turn influences planning for capacity improvement. For example, fitting HSR and commuter trains on existing tracks in New Jersey probably requires giving up express service south of Rahway, but at the outer end of the line, around Princeton Junction, going out to Trenton and backtracking on HSR would make this not as onerous as commuters may initially think. On the level of station design, the presence of backtracking means that stations may need to be reconfigured to have more access points from northbound to southbound platforms, to make transfers easier.
2. New Jersey Transit has plans from last decade to reactivate passenger rail service along the West Trenton Line. The presence of HSR makes West Trenton a less useful commuter rail station, to either Philadelphia or New York. In Philadelphia it remains useful if one wants to go to destinations on the Reading side of SEPTA, such as Temple University, or even Market East, but in New York, the nearest job center to West Trenton is Newark, which is on the Northeast Corridor. This means that better transit service from West Trenton to Trenton becomes a greater priority than direct rail service from West Trenton to New York.
3. There is a secondary rail line from New London to Norwich, passing next to Mohegan Sun. It is not very useful if intercity trains remain as they are, but the presence of HSR makes it a good feeder, and also allows trains to beat express buses for trips from New York to the casino.
4. It is vanishingly unlikely Pennsylvania will try to build in-state rail service to Erie. However, if it does, Erie-Pittsburgh service would be similar to Providence-Worcester service, with Cleveland fulfilling the same function as Boston in New England.
Difficult Transit
Many people have heard that certain regions are well-suited for these projects, for example the Northeast Corridor is unusually good for HSR because it links four major cities and several medium-size ones on a single line. By implication, there has to be a flip side, i.e. regions that are poorly-suited for HSR and cities that are poorly-suited for new rapid transit. If there weren’t – if every region were like the Northeast Corridor – then the ridership models would just have higher first-order estimates. Several proposals I’ve seen in comments and on my blogroll in the last few days are in areas where the urban geography makes it harder to justify such projects. These and a few others are the examples I will use in this post.
As usual, there’s a caveat that difficult does not equal bad. Some of these ideas are worth pursuing, but have more challenges that their easier counterparts do not, and if those challenges are solved, then they can perform well. One of the biggest success stories of modern rail investment, the TGV, is in an urban geography that’s not particularly conducive to rail: France’s secondary cities surround Paris in all directions (although Lyon and Marseille are collinear with Paris), the stub-end layout of stations in Paris and many other cities forces awkward branching, Lyon needed a business district to be built from scratch around Part-Dieu. France made this work, and it’s possible some of the projects on this list can be made to work in similar vein.
High-Speed Rail in Sweden
Project: greenfield HSR lines connecting Stockholm with Sweden’s major secondary cities, Gothenburg and Malmö.
The problem: Stockholm, Gothenburg, and Malmö do not lie on a straight line. The three cities are quite small by the standards of more populated countries: Stockholm has a bit more than 2 million people, Gothenburg has a bit less than a million, Malmö has 700,000. A line connecting just two of them, or even a Y-shaped line, is unlikely to get enough ridership to justify the construction costs of full HSR. There are no large intermediate cities: the largest, Linköping, has about 100,000 people. As noted above, French urban geography is not great for HSR, either, but at least the LGV Sud-Est could serve both Lyon and Marseille, and France’s greater population ensures that its secondary cities are large enough to generate enough traffic to fill an HSR line.
As a silver lining, Malmö is adjacent to Copenhagen, and the difficult part, bridging the Øresund, has already been done. While international lines tend to underperform, the tight cultural and economic connections between the Scandinavian countries make it likely that international projects within Scandinavia would be exceptions to the rule. Copenhagen would add another 2 million people at the end of the line. However, even that is unlikely to generate enough ridership to pay for 500-odd kilometers of greenfield HSR (plus a connection to Gothenburg).
Because of its poor urban geography for conventional HSR, Sweden has investigated cheaper solutions, allowing higher speeds on legacy track or on greenfield tracks built to lower standards. As a result, there is research into the possibility of high-speed tilting trains, running faster than the 250 km/h Pendolino. This research is likely to be useful in the UK and US, where the urban geography is better-suited for HSR but fully greenfield construction is obstructed by suburban development near the rights-of-way and by high construction costs, but the original context was faster speeds within Sweden.
High-Speed Rail in the Pacific Northwest
Project: greenfield HSR connecting Portland, Seattle, and Vancouver. This is not officially proposed anywhere that I know; current plans focus on incremental improvements to the Amtrak Cascades. However, every American HSR fantasy map I’ve seen (including the ones I’ve drawn) includes this link, since at least superficially based on city populations it would succeed.
The problem: getting out of the major cities involves a slog on curvy legacy track in areas where it’s hard to straighten the right-of-way. Heading north of Seattle, the route goes along the water, in terrain that is too hilly for an easy inland cutoff all the way to Everett, 50 km north. Getting out of Vancouver is also hard, because of suburban development in Surrey, and becomes even harder if one wants the Vancouver station to be Waterfront rather than Amtrak’s current stop, the less centrally located Pacific Central. The Northeast Corridor is said to have slowdowns near the major stations, leading to proposals to bypass them with new tunnels, but at no point are there 50 nearly-continuous km of low curve radii; the New Haven Line does not look as curvy, while the Shore Line farther east is easy to bypass on I-95.
The Seattle-Portland segment is much easier: the route heading south of Seattle is not constrained, and north of Portland it is possible to run alongside I-5. However, the most important intermediate cities, Tacoma and Olympia, can only be served with exurban stations, since getting into their centers would require the mainline to detour on curvy alignments.
Through-Run Commuter Rail in Chicago
Project: there are many proposals by transit activists to construct new infrastructure to enable through-running on Metra, analogous to Crossrail, SEPTA Regional Rail, the Paris RER, and multiple S-Bahns. Details differ, but other than the lines through Union Station, through-running generally means connecting Metra Electric to some of the lines feeding into Union Station from the north or the Union Pacific lines; UP-North is especially notable for serving dense neighborhoods and not having any freight traffic.
The problem: the layout of the lines entering the Chicago central business district makes it hard to build a coherent network. What I mean by coherent is that commuter lines can make multiple CBD stops to serve different CBDs, or different parts of the same CBD: in New York, a Penn Station-Grand Central connection would let trains serve both the West Side and the East Side. Look at the map proposed by Sandy Johnston, in the second link above: there is no station on the Near North Side, there is no connection from the West Loop stations to the Loop, and effectively lines are still going to be split between lines bound for the West Loop and lines bound for the Loop in the through-run system.
None of this is the fault of any of the people drawing these maps. To serve both the West Loop and the Loop, a line would have to go east-west in the vicinity of Union Station, where there is no legacy line pointing in the right direction. The options boil down to a long greenfield east-west subway, and an awkward transition to the preexisting east-west lines, BNSF (which is too far south) and UP-West (which is too far north), which to add another complication carry heavy freight traffic.
A system prioritizing north-south connections runs into different dilemmas, concerning the tradeoff between service to the Near North Side and easier connections to the rest of the North Side Metra lines. A north-south line connecting UP-North to Metra Electric through the Near North Side would be beautiful, and miss all other Metra lines and most L lines. Sandy’s proposal has Metra Electric swerving west to meet UP-North just north of its terminus at Ogilvie Transportation Center, meeting all L lines and potentially the North Side Metra lines but missing the job centers in the West Loop and Near North Side.
Rail to LaGuardia
Project: construct some rail extension to LaGuardia Airport. Which rail extension varies based on the proposal. The most mainstream proposal, in the sense that it was supported by Giuliani until it was torpedoed by neighborhood opposition, would have extended the Astoria Line east to airport grounds. More recent proposals from various activists have included not just the Astoria Line extension, but also a Northeast Corridor spur, an AirTrain from the Astoria Line, an AirTrain from Jamaica with JFK connections, a subway shuttle under Junction, and a subway running from the airport to 125th Street along the route of the M60 bus.
The problem: all of the above ideas face the same pair of problems. At the airport end, the airport competes with other urban destinations, rather than complementing them by lying on the same straight line with them. An extension from the west, such as the Astoria Line extension, needs to choose between serving the airport and serving the Astoria Boulevard corridor, which has high residential density and no nearby subway service; Astoria Boulevard itself is so wide that as with Queens Boulevard, an elevated line in its middle would be an improvement. Farther east, there is nothing that a LaGuardia extension could be continued to, because of Flushing Bay. An extension across the bay going to Flushing or College Point could be useful, but an extension of the 7 to College Point would be even more useful and avoid underwater tunneling. The bay, and more generally the Long Island Sound, dooms any proposal for a loop returning to the mainline, in the manner of Zurich Airport, while a spur would again compete for capacity with more important lines. Compare this with LAX, which, going along the Harbor Subdivision, is collinear with Inglewood, the Slauson corridor, and Union Station, and would have an easy connection to El Segundo.
At the other end, the question with every airport extension is, what does it connect the airport to? The answer for LaGuardia has to be the Upper East Side, where as I remember most riders originate; but there is no good way of connecting to the Upper East Side, which has no east-west subway line, and shouldn’t, as there are perhaps a hundred kilometers of higher-priority tunnels in the region. A connection to 125th Street is ruled out by the fact that Second Avenue Subway has an even better connection to 125th. The Astoria Line serves the Midtown hotel cluster well, and has a connection to the Lexington trains to the Upper East Side, but I doubt that it can beat a taxi across the bridge in non-rush-hour traffic.
Providence East Side Tunnel
Project: restore rail service through the East Side Rail Tunnel, with a new connection to Downcity at the western end and connections to new or restored rail lines in and beyond East Providence. In Jef Nickerson’s version, the trains are light rail and drop to the surface at the Downcity end. In mine, they continue elevated through Downcity, with a new station replacing Providence Station for both commuter and intercity rail. All versions include a stop at Thayer Street for Brown University service, should one be constructable at reasonable cost.
The problem: there’s no real need for local or regional service from the east along the tunnel (intercity service could be sped up by about half a minute to a minute by avoiding curves in Pawtucket). Light rail service would run into the problem of incredibly spread-out suburbanization east of Providence. Commuter rail would run into separate problems: the legacy lines go along the water in East Providence and don’t serve the town itself well; beyond East Providence, the line going north serves the same suburbs as the existing Providence Line minus Pawtucket, while the line going south would need extensive and costly restoration work to get to Fall River, and only passes through small and low-density intermediate points.
Cutting off Providence Station to move the city’s main station to the south is useful, but the only rail from Providence to Pawtucket and Woonsocket goes due north of Downcity and would be left out of this system. Shoehorning it to the same station that leads to the East Side Tunnel would produce every adverse impact of viaducts on cities: heavy visual impact coming from elevated-over-elevated grade separation, squeal coming from low curve radii, takings of condo buildings near the existing Providence Station.
California HSR Should Not Have Been Funded This Way
Last month, California made a budget deal for the formula that would be used to distribute its cap-and-trade revenues. The state’s cap-and-trade bill does not deed the money to the general budget but to a separate account, to be distributed based on a variety of goals including subsidies to programs that reduce greenhouse gas emissions. The recent deal is to give most of the money to transportation (including transit-oriented development): this year the budget gives $600 out of $850 million to transportation (see PDF-p. 6 here), of which $250 million will go to high-speed rail, and according to an informational hearing the long-term deal gives 80% of revenues to transportation, including 15% to high-speed rail. Transit bloggers who are not in the process of moving across oceans covered the issue last month as the deal was made: Streetsblog wrote about the plan, Robert Cruickshank wrote multiple times in support of the decision, and Bruce McFarling explained how HSR’s projected emissions reductions should entitle it to a share of the cap-and-trade proceeds.
In reality, although it’s a good thing that California HSR is getting funded, it’s a bad way of funding it, betraying both environmental incompetence and political mistrust. The basic problem is that the HSR project is not going to reduce emissions enough to justify 15% of the pot, nor is transportation such a big share of California’s emissions inventory to deserve 80%: it accounts for only 37% of statewide emissions. Electricity, and related sources of emissions such as building heating and industrial emissions, get far less than their share of emissions.
Bruce’s post runs the numbers on HSR, notes that the projections are currently $250-400 in construction costs per ton of CO2 reduction, and proposes that if cap-and-trade results in a carbon cost of $75 per ton then this justifies using the revenues for 20-35% of the cost of HSR. The projected revenue from cap-and-trade is a range whose top end is $5 billion statewide, corresponding to about $11 per metric ton; at this level, assuming HSR saves $250/t-CO2 means it should get 4.4% of its funding from emissions reduction, or (at the current cost of $53 billion in constant dollars) about $2.3 billion over the lifetime of the program. If the revenue is indeed $5 billion a year, this spending level is projected to be reached in 3 years.
For some evidence of what the state is really doing, consider how the deal comments on each share of the funding. The informational hearing details the investment strategy as follows:
25% for a permanent source of funding for transit operations, distributed based on greenhouse gas criteria.
20% for affordable housing and miscellaneous urban planning goals (including TOD), of which at least half must be for affordable housing (including TOD, again); the money is to be distributed based on “competitive GHG performance.”
15% low-carbon transportation, based on both long-term clean air and GHG goals.
13% energy, including electricity and building efficiency.
7% natural resources, waste diversion, and water projects.
15% HSR.
5% “new or existing” intercity rail, based on GHG criteria.
Note that internally to four categories, comprising 65% of the total funds, the hearing mentions greenhouse gas criteria. In three out of the four, comprising half of the funds, the hearing implies that the decision of how to distribute the funds will be based on competitive grants according to which project reduces emissions the most.
The key point here is that the state has effectively said what the best way is to ensure the spending side of cap-and-trade will reduce emissions optimally: projects will compete for scarce funding based on greenhouse gas criteria. Once it has made the political decision to distribute funds by a formula that disproportionately goes to transportation, it has no objection to using greenhouse gas criteria internally to each category. The problem is that the transportation projects in general and HSR in particular would never make it out of a grant process based on such criteria if they were not shielded from competition with non-transportation priorities.
There are two legitimate ways to distribute funds coming out of an externality tax, which is what cap-and-trade really is. One is to let the tax side do the work of reducing impact, and put the money into the general budget. This is common practice for most developed countries’ fuel taxes (though not the US’s). In this approach, HSR would compete with all of the state’s other budget priorities. If the state wanted to reduce other taxes against the cap-and-trade funds rather than raise spending, it could. If it wanted to spend the money on unrelated things, such as education, it could as well. There already is a more or less open and democratic budget process for this.
The other way is to reduce all political discretion, and distribute the funds based entirely on greenhouse gas criteria, without breaking the money into categories. The state seems to prefer this way, judging by its use of this process within each category. With other externality taxes there is another option, of giving the money directly to victims of the externality, e.g. spending cigarette taxes on lung cancer treatment; however, the bulk of damage caused by climate change is to developing countries, and spending cap-and-trade revenues on targeted aid to vulnerable developing countries is politically unacceptable.
The state’s hybrid approach is effectively a slush fund. High-level politicians, including Governor Jerry Brown, want to build a visible legacy, and HSR is far more visible than making household appliances consume less electricity. Emissions reductions are secondary to this concern. They’ll be happy to make their legacy a project that reduces greenhouse gas emissions, but they have no quantitative preference for projects that reduce emissions more than others. On the contrary, when they pull strings, they might even make decisions that make these projects less environmentally beneficial: the decision to connect Los Angeles to Bakersfield via Palmdale rather than directly has no technical merit, and judging by LA County’s support appears to be motivated by concerns for development in the Palmdale area. As the incremental cost of going through Palmdale is about $5 billion, nearly 10% of the HSR cost, the result is that the state is going to spend a substantial amount of cap-and-trade money on spurring more development in the High Desert exurbs.
Needless to say, when the cap-and-trade bill was passed, it did not state or even imply that the state could use the money to spur more development in the exurbs. The bill did not adopt a GHG-only approach, but listed several additional goals, none of which included transportation. Chapter 1, Part 2, paragraph h states,
It is the intent of the Legislature that the State Air Resources Board design emissions reduction measures to meet the state wide emissions limits for greenhouse gases established pursuant to this division in a manner that minimizes costs and maximizes benefits for California’s economy, improves and modernizes California’s energy infrastructure and maintains electric system reliability, maximizes additional environmental and economic co-benefits for California, and complements the state’s efforts to improve air quality.
There is an explicit mention of air quality, and explicit mentions of energy and electricity, which are only getting 13% of the funding despite accounting for 54% of emissions. Elsewhere the list of legislative intents includes vague terms such as technological leadership, but the only explicit mention of transportation in the bill is in paragraph c, which says that historically California provided leadership on several environmental issues, including emissions limits on cars as well as energy efficiency and renewable energy.
However, the cap-and-trade bill is older than the current administration, and the political priorities have changed. Since a regular budget process giving HSR the money it needs would run into opposition from competing priorities, it’s best to raid a new source of revenue, one without legislative inertia or established supporters directing the money to more useful purposes.
Hence, a slush fund.
What Elites Do Instead of Providing Services
I realized last year that even when they face a problem that is evidently about city services, city governments prefer to go for monuments that glorify their leadership. The most blatant example then was Cornell NYC Tech, the city-backed university whose campus construction alone is several times as expensive as the CUNY system per student. Since then I’ve tried to collect examples of power brokers proposing similar schemes, of which the worst is Larry Summers’ proposal to solve US inequality by spending public money on airport improvements. These are, to be frank, analogs of what American transit activists have to deal with routinely, with agencies preferring expensive iconic stations to ordinary capital and operating improvements in service.
The argument for Cornell NYC Tech is that New York needs tech entrepreneurs of the kind that Silicon Valley has, and that for that it needs its own Stanford. Instead of investing in STEM education across the CUNY system, or in its dedicated technological campus at the New York City College of Technology, it decided to start a private university from scratch, inviting other universities to bid on it. The city wanted Stanford to win the bid, but instead the winning bid was a joint effort by Cornell and the Technion, Israel’s technological university. The Technion was never run this way; it was started as a German-style technical university and is now a public university, funded and run on the same terms as the other Israeli public universities.
For Cornell NYC Tech, the city has lined up $2 billion in public and private funds for campus construction, expecting 2,000 students in 2037, which at 4% interest is $40,000 per student-year; annual capital and operating spending together, from all sources including tuition, is $16,000 per full-time equivalent student at the CUNY senior colleges and $11,000 at the CUNY community colleges (see PDF-page 65 of the budget request). This is the educational equivalent of airport connectors, which cities routinely spend several times per rider on as they would on ordinary subway extensions.
Summers’ proposal for airport improvements is in a way more frustrating, and more telling. He did not propose it as part of an independent infrastructure plan, but as a way to build public works to reduce US inequality, on the grounds that JFK is “an embarrassment as an entry point” and “the wealthiest, by flying privately, largely escape its depredations.” The proportion of people who fly privately is tiny; an income level at the bottom of the US top 1%, $400,000 per year, will buy you a lot of intercontinental business-class travel or some first-class travel, while affording a late-model Learjet requires an annual income of many tens of millions of dollars. Since poor people don’t fly as much as rich people, the users of JFK skew richer than the general city public.
My frustration comes from the fact that Summers is not trying to derail the conversation: he previously wrote about inequality as a problem and proposed standard center-left solutions, including raising taxes on capital gains and inheritances, supporting unionization, and (by implication) investment in public education. He clearly cares about the problem. He just seems to think that airport investment benefits the poor more than the rich. Most likely, this comes out of years of insider schmoozing with people so rich that they do own private jets, and generalizing to the considerably broader class of rich people.
In both cases, even on its stated merits, the proposal misses key facts about the situation. Silicon Valley began around Stanford, but once the initial tech cluster formed, it became independent of the university, so that even companies formed by people with no affiliation with Stanford or the Bay Area, such as Facebook, relocated to the area. New York is not going to grow its tech industry to the proportion of Silicon Valley’s by building an enterprise university any more than the Bay Area can become a world financial center by building affiliate universities for Columbia and NYU, from which many finance workers are recruited. As for JFK, like many of its users, when I arrive my first experience is the immigration line, a humiliating experience that involves fingerprinting and standing in line possibly for hours, depending on what terminal I use and what time I arrive. Public works will not solve that.
The problem with making even the merit-based argument is that public monuments are never truly merit-based projects. The decision-making process goes in the other direction: first the city elites (or, in case Summers’ proposal makes it into a national jobs bill, national elites) decide on something they want to see built, usually with the adjective world-class thrown in: a world-class university, a world-class airport, a world-class train station, a world-class office tower. The image of a world-class monument is more important than whether it works at its stated goal, such as improving education or transportation or fulfilling a need for class A office space.
Witness all the problems involving World Trade Center, which is being built entirely for prestige value, at enormous cost. The associated PATH station is $4 billion, almost as much as Second Avenue Subway, and about the same as 20 kilometers of subway in an average first-world city. One World Trade Center cost about $12,000 per square meter. I am not aware of any office tower in the world that is this expensive outside the WTC area and Hudson Yards; the tallest recent tower built in New York excluding 1 WTC, Bank of America Tower, cost about $5,500 per square meter in 2012 dollars, while the range I have seen for office towers in the 200+ meter range is about $2,500-6,000. Meanwhile, the WTC site struggles to find tenants: 1 WTC is almost half empty.
The sentiments after 9/11 ensured WTC would be rebuilt taller, regardless of actual demand in Lower Manhattan. Viewed through this lens, 1 WTC is not really about office space, but about proving a point about the power of US and New York to come back and not surrender to terrorism. This is why the transit spending went mainly to the PATH station and not to bringing the LIRR to Lower Manhattan, as proposed by the Regional Plan Association and studied officially in subsequent years: the LIRR project would’ve been about Lower Manhattan in general, without enhancing the specific prestige of WTC, while the billions poured into the WTC site and its PATH stations are all about the prestige.
Those other projects – various overrated transit schemes such as airport connectors, but also Cornell NYC Tech and Summers’ JFK proposals – are the same. They are not about what people living in, working in, or visiting the city need. They are not even about what they want. Whereas there was a citywide impulse to rebuild WTC taller after 9/11, there is no equivalent impulse to build an exclusive technical university, except among the power brokers. They are entirely about being able to say, “we have our own ___” and “I got that built.” It looks like development, but at best provides a fraction of the advertised value, and at worst provides nothing.
Whenever an urban project is proposed, the most important question to be asked is “what problem is this solving?”. Often, the problem is real, but there are much cheaper and less glamorous solutions. At other times, the project is a solution in search of a problem, and this is often detectable when proponents tout many unrelated benefits, almost as if the project can solve every major problem.
Compare this with solid public transit projects. Consider the lines I think North American cities should be focusing on, and the lines proposed in comments, especially as the Vermont subway in Los Angeles. In every single case, there are strong arguments for why the ridership of those lines would be high relative to the cost, and why existing subway lines (if any) and surface transit options are inadequate. The problem being solved is underserved neighborhoods with high transit demand, or in the case of the crosstown lines underserved origin-destination pairs in high demand. For other lines, not listed, there might be a separate argument regarding transit-oriented development: American cities tend to oversell TOD, as the problems with Hudson Yards show, but there do exist cases in which extending a subway line can allow dense development, or the construction of a new business district. But this involves figuring out where the development comes from – for example, the housing market may be very expensive, signaling high demand, or there may be projections of high future metropolitan population growth.
Usually, support for prestige projects to the exclusion of providing public services is the hallmark of moderates, along a broad arc from the center-left to the center-right. In the last few years, Republicans too far right to be called center-right have prioritized cutting taxes and spending and weakening the unions; signature projects conflict with their opposition to government spending. Conversely, urban leftist activists tend to oppose these prestige projects, on such grounds as gentrification, displacement, and private-sector involvement in public services.
The people in between those two ends are the ones most guilty of this kind of thinking. They are usually neo-liberal enough that they believe the government should champion market solutions and oppose industrial policy, and yet what they do is in many cases exactly industrial policy: Cornell NYC Tech is an attempt to curry favor with the technology industry. They are not so conservative as to believe government is always the problem, but the role they envision for government is to partner with the private sector to build public projects, which they tend to choose on grounds of what looks good rather than what provides the best public service. They know the buzzwords of urban politics well: for example, they’ll happily argue climate change to push a desired agenda that is usually only partly related to the problem, but lack the urgency of actual environmentalist activists and often also build roads and other dirty projects.
As with most bad things in politics, it’s a result of weak democratic institutions on the local level. American mayors tend to be elected dictators, and the opposition to them tends to be based on personality rather than ideology. In this non-ideological framework, the role of government is not to balance market and state solutions based on the voters’ preferences, but to aggrandize the leaders. Signature initiatives must appeal to the broad spectrum of non-ideological voters, so they can’t involve merely increasing spending on a chosen priority like education or transportation. Doing nothing is not an option – something has to be passed to remind people that the government still exists and has a purpose. The political incentives are against any incremental improvements that lead to tangible results, and for white elephants.
Airport Connectors
The most interesting transit planner in the world:
This principle is true primarily for large international airports. As I will explain, this is less true of smaller airports. But before going on, I would like to clarify a distinction between bad and overrated. Airport connectors, as I have argued many times, are overrated: city elites tend to like them disproportionately to their transit usage, as do many urban boosters, who think a comfortable airport connector is a necessary feature of a great global city. The result of this thinking (and also the main evidence we have that this thinking exists) is that airport connectors are built at much higher costs per rider than other transit projects: the JFK and Newark AirTrains cost more than $100,000 per weekday rider, much more than other recent rail projects in New York; even the far over-budget East Side Access, at current estimates, is about $60,000.
However, overrated does not mean bad. There exist airport connector projects with reasonable cost per rider. They’re still overrated, which means they’ll be built concurrently with even more cost-effective non-airport projects, but they’re good enough by themselves. As an example, take the Canada Line. The total cost was about $2 billion, and the latest ridership figure I have, from 2011, is 136,000 per weekday, ahead of projections. At $15,000 per rider, this is reasonable by European standards and very good by North American ones. Let us now look at the two branches of the line, to Richmond and the airport. Lacking separate cost data for them, I am going to estimate them at about $300 million each, as they are entirely above-ground; the airport branch is 4 km and the Richmond branch is 3 km, but the Richmond branch has an urban el and the airport branch doesn’t. For ridership data, we have this set of figures per station (which results in a Canada Line total of only 113,000). Boardings and alightings sum to 19,000 on the airport branch and 34,000 on the Richmond branch; we’re double counting intra-branch trips, but there presumably are very few of these. As we see, the Richmond branch is more cost-effective, but the airport branch holds its own – since the per-station data has a lower overall Canada Line ridership, the airport branch’s presumed cost per extra rider generated is less than that of the entire line! (This sometimes happens, even with branches that generate less ridership than the trunk.) Clearly, despite the fact that airport connectors are overrated, this is an example of a good project.
The importance of the overrated vs. bad distinction is then that good transit advocates need to be wary, since airport connectors that don’t work well might get funded anyway, ahead of more deserving projects. But there remain good airport connectors, and therefore we should discuss what features they might have. The answer given by city elites is typically “nonstop connection to the CBD,” often with a premium fare. But the good transit answer is more complicated, and the graphic at the top of the post is only a partial answer.
There is a difference between short- and long-distance air travel. In many cities it doesn’t matter much because there’s a single dominant airport – Beijing, Frankfurt, Zurich, Atlanta, Toronto – but in others there are multiple airports, with different roles. Often there will be a smaller, closer-in, older airport, serving mostly domestic flights, and a larger, farther away, newer international airport. Paris has Orly and Charles-de-Gaulle, Chicago has Midway and O’Hare, New York has LaGuardia and JFK (Newark is intermediate in its role, even if it’s the oldest), Los Angeles has Burbank and LAX (the other airports are somewhat outside this division), Dallas has Love Field and DFW, Tokyo has Haneda and Narita, Seoul has Gimpo and Incheon. Because those airports have different functions, they require different kinds of transportation links.
First, let us consider departing passengers. If they travel to another continent, their options are quite restricted: for example, if they live within driving distance of Atlanta, they’re flying out of Atlanta. Even if there are closer secondary airports (such as Greenville-Spartanburg and Chattanooga), they don’t offer such service – at most, they offer a connecting puddle jumper flight to the primary airport. In contrast, if they travel shorter distances, and live far from the primary airport, they could fly out of a secondary airport, or might just drive instead of flying: a 2-hour drive to the airport is comparatively more tolerable for an 8-hour intercontinental flight than for a 1.5-hour short-hop flight. For example, when I lived in Providence, my air trips were all to the West Coast or Europe, so I flew out of Boston or even New York; but when my sister visited, she chained trips and also visited her boyfriend, who at the time lived in North Carolina, and for the domestic leg of the trip she flew out of T. F. Green.
The result is that primary international airports draw their departing passengers from a much wider shed than mainly domestic airports. In metro areas with such separation of airports, the international airports – Charles de Gaulle, JFK, DFW, Incheon, etc. – draw riders from faraway suburbs and even from adjacent small metro areas, whereas the domestic airports draw riders primarily from the city and its nearby suburbs.
Now, let us consider arriving passengers. Destinations are more centralized than origins, but this is especially true for international trips than for domestic ones. Tourism trips are heavily centralized around a few attractions, which in most cities are in the CBD, or in specific locations: if you’re flying to the Paris region for tourism, your destination is either Paris proper or Eurodisney, rather than an average suburb. Business trips are also heavily centralized around the CBD and a few edge cities. Personal visits have no such concentration, and these are much more common for short-distance domestic flights than for long-distance international flights. I am unusual in that I live on a different continent from my parents; usually, people live within ground transportation or short-distance flying distance from family and friends, depending on the country they live in (short-distance flying distance is more common in the US). The result here is that arriving passengers at domestic airports are typically interested in visiting the CBD but often also the rest of the metro area, whereas arriving passengers at international airports are much more CBD- or tourist attraction-centric.
Some evidence for this difference can be found in looking at the Consumer Airfare Report, which has domestic O&D traffic counts between airport pairs. The primary international airport usually has a smaller percentage of its domestic O&D traffic going to shorter-distance cities. For example, at LAX, 13% of traffic is within California, and another 6% is to Las Vegas, Phoenix, and Tucson, within a 3-hour high-speed rail range. At Burbank, the corresponding figures are 42% and 21% respectively. The same pattern can be observed for O’Hare (8.6% of traffic is internal to the Midwest) and Midway (14.6%), and DFW (3% of traffic is internal to the Texas Triangle) and Love Field (27%).
The mode of transportation that best suits the needs of international airports is then mainline rail. On the one hand, it tends to be better than urban transit at serving trips that are dedicated to CBD service, since commuter rail is more radial than urban transit, and the stop spacing is typically also longer (although dedicated premium connectors are still often wastes of money). On the other hand, it can extend deep into the suburbs and to adjacent metro areas, and expand the airport’s draw. People can ride intercity (often high-speed) trains direct to the terminal at Frankfurt, Zurich, and Charles-de-Gaulle, and this allows those airports to be the primary international airports for metro areas in a wide radius: SNCF code-shares with airlines to connect people from Charles-de-Gaulle to Lyon, 400 km and 2 hours away by TGV.
This is not true of small domestic airports. A TGV connection to Orly would’ve been much less beneficial than the current connection to Charles-de-Gaulle: most of Orly’s traffic is short-distance, often competing with the TGV rather than complementing it.
With this distinction in mind, we should look at the situation at the major American airports. In California, the current plan is to have California High-Speed Rail serve both SFO (at Millbrae) and Burbank Airport; the original plan served Downtown Burbank instead of the airport, but the HSR Authority seems to have shifted its focus, and wants Burbank to be the southern terminus of the line, pending construction to LA Union Station. This is bad planning. Nearly two-thirds of Burbank’s traffic competes either with California HSR or with future tie-ins. People from Bakersfield and Fresno are unlikely to take a train to the airport to connect to a flight, since they can take a train the whole way, or drive directly to Las Vegas or Phoenix. People in Bakersfield and Fresno would be more interested in a connection to LAX, whose traffic complements rather than competes with intercity rail.
Los Angeles could build a connection to LAX, running both frequent electric commuter trains and high-speed trains on it. The Harbor Subdivision has existing tracks from Union Station almost the entire way to the airport, although the route is at-grade, with a large portion of it running next to Slauson Avenue, and most likely a major project like this would require viaducts. Only a short greenfield segment, elevated over Century, is required to reach the proposed Terminal 0 location, and that is only necessary if, as in Zurich and Frankfurt, LAX wishes to avoid a landside people mover. It is both bad transit and bad politics to build this only for nonstop trains: the route passes through reasonably dense urban neighborhoods, and should have 10-12 stops along the way, with some trains running local and others making only 1-3 stops, at major nodes such as Inglewood or the intersection with the Blue Line. There is room for passing sidings at the line’s midpoint, but the low top speed and the short length of the line is such that overtakes are only necessary if there are nonstop and local trains every 10 minutes. Such an airport connector would serve many different trips at once: HSR trips from Central Valley cities to LAX, arriving trips from LAX to Downtown LA (and, via transfers at intermediate stops, to the Westside), and local trips on the Slauson corridor. It’s a flexibility that modernized regional rail has, and that other modes of transportation, which can’t mix local and intercity traffic as well, lack.
Leaving California, let us look at New York. There are perennial proposals for a new connection to LaGuardia (via an extension of the N) and an additional connection to JFK (usually using the Rockaway Cutoff). There is also a new proposal for a Newark connection via PATH. With the distinction between short-distance domestic and long-distance international airports (Newark is intermediate between the two), we can analyze these proposals. Newark is the easiest to dispose of: the cost is extreme, $1.5 billion for 4 km above ground. It also has several design flaws: unlike the LAX connector I outlined above, this proposal is nonstop from Newark Penn, skipping the former South Street railroad station; the lack of intercity service improvement and the poor service to the Midtown hotel clusters doom it as a CBD connector.
The JFK proposals are problematic as well. The AirTrain connection to Jamaica is quite useful, since it lets people from all over Long Island connect to the airport. Improving JFK access hinges on improving service to Jamaica, then: through-service from New Jersey, higher off-peak LIRR frequencies, reelectrification with catenary to permit Amtrak send Northeast Corridor trains that aren’t needed for Boston service to Jamaica. East Side Access improves JFK access as well, since it allows LIRR trains to serve Grand Central, which is closer to the Midtown hotel clusters than Penn Station. Ideally there wouldn’t be an AirTrain connection, but it’s the best that can be done given existing infrastructure and given Jamaica’s importance. A Rockaway Cutoff connection, which branches from the LIRR Main Line west of Jamaica, would not help Long Islanders go to JFK; it would also not be able to carry intercity trains, since Amtrak trains to Jamaica can serve both airport riders and Long Island riders, each of which groups alone is too small to justify intercity trains on its own.
In contrast, LaGuardia proposals are better, since for a close-in, domestic airport, service to the entire city is more important. I remain somewhat skeptical – airport connectors are still overrated – but less dismissive than of Newark and JFK proposals. LaGuardia travelers from the Upper East Side, which as far as I remember supplies a majority of its departing traffic, would have to transfer at 59th Street; but they have to detour through 59th or 125th via taxi already, and the subway would not get stuck in Manhattan traffic. Conversely, there is much less need to connect the airport with the suburbs and with neighboring metro areas than there is with JFK, which means that there is no point in constructing people movers to the LIRR.
Finally, let us look at Chicago. O’Hare has the airport connection of a domestic airport rather than that of an international airport. There are plans for an express link to the Loop, but these do nothing for departing passengers from neighboring areas. While airport connectors tend to be overrated, express premium-fare links are especially overrated, since they give business travelers dedicated trains, on which they always find seats, without needing to commingle with lower-income riders.
However, some of the Midwestern high-speed rail proposals include a connection to O’Hare from the outlying metro areas, and this is good planning, assuming the cost is not excessive. SNCF’s proposal includes a bypass of Chicago that serves O’Hare, similar to the Interconnexion Est. A second step, if such a connection is built, is to attempt to connect regional lines to it, if they are electrified. This includes both inward connections, i.e. a frequent commuter rail connection to the Loop or West Loop with good connections (ideally, through-service) to other commuter lines, and outward connections, i.e. low-speed short-distance intercity lines, such as to Rockford.
In all of these cases, the common thread is that the connection to the airport does not need to be a premium service, marketed only to the business traveler. These services are never the majority of airport transit ridership: see Hong Kong, Tokyo, and London numbers on PDF-p. 28 here. However, it does need to provide service to both departing and arriving passengers, and for a major international airport, this requires good service to the suburbs and to adjoining metro areas. The optimal technologies are often bundled together with premium fares – high-speed rail is in many countries, mainline rail is in North America – but the benefits come from features of the technology and service pattern, rather than of the branding. Good transit projects connecting to airports will make sure to have the correct service reach, while at the same time not excluding local riders.
Pedestrian Observations 
