There are two standard reasons why public transit should limit branching. The first is that it reduces frequency on the branches; this is Jarrett Walker’s reason, and distantly the reason why New York doesn’t interline more than two subway services anywhere except 60th Street Tunnel. The second is that it makes schedules more fragile, first because services have to be scheduled more precisely to alternate among branches, and second because delays on one branch propagate to the others. And yet, rail and bus networks still employ branching, due to benefits including better coverage and focusing frequency where demand is the highest. This is especially common on regional rail, where all services are scheduled and often interact with the mainline network, so the second problem of branching is present no matter what. Metro systems instead have less branching, often because they only serve dense areas so that the main benefits of branching are absent. But what about buses?
I posit that bus branching is more valuable in low-density areas than in high-density areas. If an area only has demand for a bus every 30 minutes, and some farther-out places only have demand for an hourly bus, then it’s fine to branch the route in two. The bus would only be useful with some timed transfers at the inner end – maybe it’s feeding a regional train station with a train every half hour – but the Zurich suburbs have half-hourly clockface schedules with timed bus/rail connections and maintain high mode share for how low their density is.
In the other direction, look at Manhattan specifically. I’ve been looking at its bus network even though I’m only supposed to redesign Brooklyn’s. I’ve mentioned before that my epistemology is that if the presence of factor A makes solution B better, then the absence of factor A should make solution B worse. I noticed that the Brooklyn bus network has very little branching: the only route numbers that branch are the B41 and B38, and the only routes with different numbers that share the majority of their lengths are the B67 and B69 (which reverse-branch). However, Manhattan has extensive branching: the M1/2/3/4 share the Madison and Fifth Avenue one-way pair, and the M101/102/103 share the Third and Lexington one-way pair. Understanding why would be useful even if I only care about Brooklyn: if there is a good reason for Manhattan buses to branch then I should consider adding branching in Brooklyn where appropriate, and even if it’s inappropriate, it’s useful to understand what special circumstances make branching good in Manhattan but not in Brooklyn.
As it is, I don’t believe the branching in Manhattan is useful for Brooklyn. This comes from several reasons, at least one of which implies it’s not really useful for Manhattan either, and by extension for other high-density regions.
You can run a bus that comes every half hour on a schedule, making it possible to interline two hourly routes evenly. With some discipline you can go down to 15 minutes, or possibly even 10: Vancouver runs 12-minute limited buses on 4th Avenue on a clockface schedule with on-board fare collection and shared lanes, but there is signal priority at nearly all intersections and relatively little car traffic since the West Side’s street network is rich in arterial roads and distributes cars across other routes (i.e. Broadway, 12th, and 16th Avenues).
In contrast, it’s not really feasible to run buses on a schedule when they come every 5 minutes. There can be a printed schedule, but buses won’t follow it reliably. Once frequency hits about once every 3 minutes, regular street buses bunch so much that adding more buses doesn’t increase passenger capacity, but even in the 5-10 minute range, schedules are less important than headway management, unless the bus has extensive BRT treatments reducing schedule variance. This means that if a bus comes every 10 minutes and is scheduled on headway management, then branching the route means each branch gets service every 20 minutes scheduled on headway management as well. Few passengers would want to ride such a route. This is the worst region for branching, the 7.5-15 minute range in which branches force passengers to use buses that are both infrequent and irregular.
The highest-frequency routes can branch with less risk. If a 5-minute bus branches in two, then each branch gets 10-minute service, at which point reliable schedules are still desirable but not absolutely necessary. How much service do the Manhattan bus trunks run? In the following scheme, peak means the busiest hour in the morning in the peak direction, and off-peak means the lowest frequency between the morning and afternoon peaks, which is usually around 11 am.
M1: 13 buses per hour peak (8 limited, 5 local), 5 off-peak (all local)
M2: 9 peak, 4 off-peak
M3: 6 peak, 6 off-peak
M4: 12 peak (5 limited, 7 local), 6 off-peak (all local)
M101: 6 peak, 6 off-peak (8 in the busiest off-peak hour, 2-3 pm)
M102: 5 peak, 4 off-peak
M103: 5 peak, 4 off-peak
What we see is that Manhattan branches precisely in the worst frequency range. The buses are frequent enough that it’s not possible to run them on a timetable without either much better segregation from traffic than is feasible (even waving away politics) or massive schedule padding, but they still require passengers in Upper Manhattan to wait 10-15 minutes for their specific branch. One might expect that Bus Time would make it easier on passengers by telling them where the bus is, but no, ridership has actually fallen since apps were introduced (and this fall predates the entry of app-hailed TNCs into the city). It turns out passengers like being able to rely on easily memorable clockface schedules, or else on frequencies so high that they only need to wait 5 minutes, not 15.
The street network
Even one-time visitors to New York notice that the avenues in Manhattan are all one-way. This features prominently in the Manhattan bus network, which employs consistent one-way pairs on First/Second, Third/Lex, Madison/Fifth, and Ninth/Tenth. Moreover, again as every visitor to New York knows, Central Park occupies a large blob of land in the middle, interrupting Sixth and Seventh Avenues.
The upshot is that there are more north-south routes north of 110th Street than south of it. This is roughly the branch point on the three trunks that branch (First/Second only carries the M15). In Harlem, there’s demand for buses on Lenox (i.e. Sixth) and Seventh, both of which are two-way there. There’s also commerce on an interpolating route, Manhattan/St. Nicholas, which is effectively 8.5th Avenue in most of Harlem. Farther west, Ninth/Columbus is no longer a useful through-route north of 110th, but instead Tenth/Amsterdam is two-way, and one of the two buses using the Columbus/Amsterdam one-way pair on the Upper West Side, the M11, indeed goes two-way on Amsterdam north of 110th.
This situation occurs very frequently in cities without gridded street networks. One trunk route will split in two, heading to different former villages that were incorporated into the city as it industrialized and grew. Manhattan is unusual among gridded cities in that its avenues are one-way, forcing buses into one-way pairs south of Harlem that, together with Central Park, ensure there are more useful routes north of 110th than south of it. But among cities without a planned street network this is typical.
As a check, let’s look at the bus networks in two ungridded American cities: Boston and Providence. Do they have a lot of interlining, involving one trunk route splitting in two farther out? Yes, they do!
Here is Providence. Going west of Downcity, there are two major routes to Olneyville, Westminster and Broadway, but beyond Olneyville there are four main streets, so each of the two inner corridors carries two bus routes, and one of these four routes even splits in two farther out. Going north, Charles Street carries four routes, branching off at various locations. Going east there’s a bus tunnel to College Hill carrying many routes, but even outside the tunnel, the one-way pair on Angell and Waterman carries three buses, which split in East Providence. And going south and southwest, Broad Street carries multiple routes, and one of its branches, Elmwood, carries two, splitting farther south.
Here is Boston. Unlike in Providence, buses don’t converge on city center, but on subway stations, so the map is much less clean. However, we see the same pattern of trunk routes splitting into branches. For example, going south of Ruggles, many routes go southeast to Dudley and then south on Warren Street, splitting to various destinations in Dorchester, Mattapan, and Hyde Park on the way. Going southwest of Forest Hills we see many routes use Washington Street, some staying on it and branching in Dedham and some veering west to West Roxbury and branching there. Elsewhere in the system we see the same pattern going north of Maverick and Oak Grove, northeast of Malden, west of Harvard (briefly on Mount Auburn), and northwest of Alewife.
One-seat rides and reverse-branching
I have repeatedly criticized the practice of reverse-branching on subway networks, especially New York, in which two train routes share tracks in an outlying area (such as Queens Boulevard) and then split heading into the center (such as Eighth Avenue on the E versus Sixth Avenue on the F). I did so on the same grounds that any branching is suspect: it reduces frequency on specific routes, and makes the schedule more fragile as delays propagate to more of the network. Moreover, the issue of schedule fragility gets worse if many routes share tracks at some point during their journey, whereas with conventional branching there are only two or three branches per trunk and the trunks form self-contained systems. Finally, reverse-branching lacks the main benefit of conventional branching, as it does not concentrate traffic in the core, where there’s most demand.
These issues are present on bus networks, with two modifications:
- The value of one-seat rides is somewhat higher. Transferring between buses is less nice than transferring between subways: in a Dutch study about location decisions, people’s disutility of out-of-vehicle time on buses was 1.5 times as high as on trains.
- Buses can overtake each other and, even without overtakes, run much closer together than trains. The limiting factor to capacity on buses is schedule fragility and bunching and not stopping distances. This means that reverse-branching is less likely to lead to cascading delays – buses do not have a 2-minute exclusion zone behind them in which no buses may enter.
This means that reverse-branching is more defensible on buses than on trains. However, even then, I don’t think it’s a good idea. At least in Manhattan, reverse-branching consists of avenues in Upper Manhattan that have buses going to both the East Side and the West Side: the M7 (serving the Ninth/Tenth pair) and the M102 both run on Lenox, and the M4 and M104 (running on Broadway to Midtown) both run on Broadway in Morningside Heights. These splits both reduce the frequency available to bus riders and should be eliminated. East-west service should be provided with high-quality bus routes on the main streets, especially 125th (which needs a full subway) but also 116th, 135th, 145th, and 155th.
The snag is that grids don’t work well unless they are complete. The Manhattan grid isn’t complete through Upper Manhattan, because 116th and 135th are discontinuous, without a direct connection from Central Harlem to Morningside Heights and West Harlem. However, the M7 route duplicates the 2 and 3 trains, so it’s not necessary for east-west connectivity. The M4 route doesn’t duplicate the subway, but does duplicate the M101, which runs on 125th Street and Amsterdam (and isn’t a reverse-branch because the M11 terminates shortly after 125th), so it’s not useful by itself.
Should buses branch?
There is one solid reason for buses to branch: if the street network has more major routes closer to the center than in outlying areas, then buses running on the outer arterials should come together close to the core. This is common enough on cities with haphazard street networks. It may also be reinforced if there are weak circumferential streets (Sydney is one such example). In contrast, cities with gridded street plans, even broken grids like those of Brooklyn and Tel Aviv, should have little to no bus branching.
If a bus does branch, it should ideally be extremely frequent on the trunk, so that even the branches have decent headway-based service. I’m not willing to commit to a maximum headway, but Barcelona and Toronto both have at worst 8-minute headways on their bus grids, so if that is indeed the maximum then a bus shouldn’t branch if its off-peak frequency is worse than every 4 minutes and better than every 10-20 (the more reliable the timetable is, the lower the upper limit is, since it’s possible to run on a timetable at higher frequency). In my case of interest, Brooklyn, there is exactly one bus route that comes at least every 4 minutes off-peak: the B46 on Utica runs 16 buses per hour in each direction, counting both local and limited (SBS) routes.
The area in which buses absolutely should not branch – strong interconnected networks of arterials (not necessarily grids – Paris’s network counts too), running buses every 5-15 minutes off-peak – is exactly where most strong bus networks are. It’s rare to have a bus that has extremely high frequency all day, because in most functional city such a bus would be a subway already; as it is, Utica has long been New York’s second priority for subway service, after Second Avenue. So for the most part, the places where buses are the strongest are precisely those where branching is the most deleterious. Low-frequency networks, perhaps connecting to a suburban train station with a timed transfer, should add bus branching to their planning toolkit, but high-frequency urban networks should not.
I do not know how to code. The most complex actually working code that I have written is 48 lines of Python that implement a train performance calculator that, before coding it, I would just run using a couple of Wolfram Alpha formulas. Here is a zipped version of the program. You can download Python 2.7 and run it there; there may also be online applets, but the one I tried doesn’t work well.
You’ll get a command line interface into which you can type various commands – for example, if you put in 2 + 5 the machine will natively output 7. What my program does is define functions relevant to train performance: accpen(k,a,b,c,m,x1,x2,n) is the acceleration penalty from speed x1 m/s to speed x2 m/s where x1 < x2 (if you try the other way around you’ll get funny results) for a train with a power-to-weight ratio of k kilowatts per ton, an initial acceleration rate of m m/s^2, and constant, linear, and quadratic running resistance terms a, b, and c. To find the deceleration penalty, put in decpen, and to find the total, either put in the two functions and add, or put in slowpen to get the sum. The text of the program gives the values of a, b, and c for the X2000 in Sweden, taken from PDF-p. 64 of a tilting trains thesis I’ve cited many times. A few high-speed trainsets give their own values of these terms; I also give an experimentally measured lower air resistance factor (the quadratic term c) for Shinkansen. Power-to-weight ratios are generally available for trainsets, usually on Wikipedia. Initial acceleration rates are sometimes publicly available but not always. Finally, n is a numerical integration quantity that should be set high, in the high hundreds or thousands at least. You need to either define all the quantities when you run the program, or plug in explicit numbers, e.g. slowpen(20, 0.0059, 0.000118, 0.000022, 1.2, 0, 44.44, 2000).
I’ve used this program to find slow zone penalties for recent high-speed rail calculations, such as the one in this post. I thought it would not be useful for regional trains, since I don’t have any idea what their running resistance values are, but upon further inspection I realized that at speeds below 160 km/h resistance is far too low to be of any consequence. Doubling c from its X2000 value to 0.000044 only changes the acceleration penalty by a fraction of a second up to 160 km/h.
With this in mind, I ran the program with the parameters of the FLIRT, assuming the same running resistance as the X2000. The FLIRT’s power-to-weight ratio is 21.1 in Romandy, and I saw a factsheet in German-speaking Switzerland that’s no longer on Stadler’s website citing slightly lower mass, corresponding to a power-to-weight ratio of 21.7; however, these numbers do not include passengers, and adding a busy but not full complement of passengers adds mass to the train until its power-to-weight ratio shrinks to about 20 or a little less. With an initial acceleration of about 1.2 m/s^2, the program spits out an acceleration penalty of 23 seconds from 0 to 160 km/h (i.e. 44.44 m/s) and a deceleration penalty of 22 seconds. In videos the acceleration penalty appears to be 24 seconds, which difference comes from a slight ramping up of acceleration at 0 km/h rather than instant application of the full rate.
In other words: the program manages to predict regional train performance to a very good approximation. So what about some other trains?
I ran the same calculation on Metro-North’s M-8. Its power-to-weight ratio is 12.2 kW/t (each car is powered at 800 kW and weighs 65.5 t empty), shrinking to 11.3 when adding 75 passengers per car weighing a total of 5 tons. A student paper by Daniel Delgado cites the M-8’s initial acceleration as 2 mph/s, or 0.9 m/s^2. With these parameters, the acceleration penalty is 37.1 seconds and the deceleration penalty is 34.1 seconds; moreover, the paper show how long it takes to ramp up to full acceleration rate, and this adds a few seconds, for a total stop penalty (excluding dwell time) of about 75 seconds, compared with 45 for the FLIRT.
In other words: FRA-compliant EMUs add 30 seconds to each stop penalty compared with top-line European EMUs.
Now, what about other rolling stock? There, it gets more speculative, because I don’t know the initial acceleration rates. I can make some educated guesses based on adhesion factors and semi-reliable measured acceleration data (thanks to Ari Ofsevit). Amtrak’s new Northeast Regional locomotives, the Sprinters, seem to have k = 12.2 with 400 passengers and m = 0.44 or a little less, for a penalty of 52 seconds plus a long acceleration ramp up adding a brutal 18 seconds of acceleration time, or 70 in total (more likely it’s inaccuracies in data measurements – Ari’s source is based on imperfect GPS samples). Were these locomotives to lug heavier coaches than those used on the Regional, such as the bilevels used by the MBTA, the values of both k and m would fall and the penalty would be 61 seconds even before adding in the acceleration ramp. Deceleration is slow as well – in fact Wikipedia says that the Sprinters decelerate at 5 MW and not at their maximum acceleration rate of 6.4 MW, so in the decpen calculation we must reduce k accordingly. The total is somewhere in the 120-150 second range, depending on how one treats the measured acceleration ramp.
In other words: even powerful electric locomotives have very weak acceleration, thanks to poor adhesion. The stop penalty to 160 km/h is about 60 seconds higher than for the M-8 (which is FRA-compliant and much heavier than Amfleet coaches) and 90 seconds higher than for the FLIRT.
Locomotive-hauled trains’ initial acceleration is weak that reducing the power-to-weight ratio to that of an MBTA diesel locomotive (about 5 kW/t) doesn’t even matter all that much. According to my model, the MBTA diesels’ total stop penalty to 160 km/h is 185 seconds excluding any acceleration ramp and assuming initial acceleration is 0.3 m/s^2, so with the ramp it might be 190 seconds. Of note, this model fails to reproduce the lower acceleration rates cited by a study from last decade about DMUs on the Fairmount Line, which claims a 70-second penalty to 100 km/h; such a penalty is far too high, consistent with about 0.2 m/s^2 initial acceleration, which is far too weak based on local/express time differences on the schedule. The actual MBTA trains only run at 130 km/h, but are capable of 160, given long enough interstations – they just don’t do it because there’s little benefit, they accelerate so slowly.
Unsurprisingly, modern rail operations almost never buy locomotives for train services that are expected to stop frequently, and some, including the Japanese and British rail systems, no longer buy electric locomotives at all, using EMUs exclusively due to their superior performance. Clem Tillier made this point last year in the context of Caltrain: in February the Trump administration froze Caltrain’s federal electrification funding as a ploy to attack California HSR, and before it finally relented and released the money a few months later, some activists discussed Plan B, one of which was buying locomotives. Clem was adamant that no, based on his simulations electric locomotives would barely save any time due to their weak acceleration, and EMUs were obligatory. My program confirms his calculations: even starting with very weak and unreliable diesel locomotives, the savings from replacing diesel with electric locomotives are smaller than those from replacing electric locomotives with EMUs, and depending on assumptions on initial acceleration rates might be half as high as the benefits of transitioning from electric locomotives to EMUs (thus, a third as high as those of transitioning straight from diesels to EMUs).
Thus there is no excuse for any regional passenger railroad to procure locomotives of any kind. Service must run with multiple units, ideally electric ones, to maximize initial acceleration as well as the power-to-weight ratio. If the top speed is 160 km/h, then a good EMU has a stop penalty of about 45 seconds, a powerful electric locomotive about 135 seconds, and a diesel locomotive around 190 seconds. With short dwell times coming from level boarding and wide doors, EMUs completely change the equation for local service and infill stops, making more stops justifiable in places where the brutal stop penalty of a locomotive would make them problematic.
New York is unique among the major subways of the world in the extent of interlining its network has. All routes share tracks with other routes for part of the way, except the 1, 6, 7, and L. The advantage of this system is that it permits more one-seat rides. But the disadvantages are numerous, starting with the fact that delays on one line can propagate to nearly the entire system, and the fragile timetables lead to slower trains and lower capacity. New NYCT chief Andy Byford just released a plan calling for investment in capacity, called Fast Forward, focusing on accessibility and improved signaling, but also mentioning reducing interlining as a possibility to increase throughput.
I covered the interlining issue more generally in my article about reverse branching, but now I want to explain exactly what it means, having learned more about this issue in London as well as about the specifics of how it applies to New York. In short, New York needs to reduce the extent of reverse branching as much as possible to increase train speed and capacity, and can expect serious gains in maximum throughput if it does so. It should ultimately have a subway map looking something like this:
Lessons from London
In London, there is extensive interlining on the Underground, but less so than in New York. The subsurface lines form a complex interconnected system, which also shares tracks with one branch of the Piccadilly line, but the Northern, Central, Victoria, Jubilee, and Waterloo and City lines form closed systems (and the Bakerloo line shares tracks with one Overground line). The Northern line reverse-branches: it has two central trunks, one through Bank and one through Charing Cross; one southern segment, with through-trains to both trunks; and two northern branches, each sending half its trains to each trunk. The other closed systems have just one trunk each, and as a result are easier to schedule and have higher capacity.
As the Underground moves to install the same high-capacity signaling on more and more lines, we can see what the outer limit of throughput is on each system. The Northern line’s new moving-block signaling permits 26 trains per hour on the Bank trunk and 22 on the Charing Cross trunk. When the Battersea extension opens, reverse branching on the south will end, pairing the older line to Morden with Bank and the new extension with Charing Cross, and capacity will rise to 32 tph per trunk. Planned improvements to transfer capacity at Camden Town, the northern branch point, will enable TfL to permanently pair each northern branch with one central trunk, raising capacity to 36 tph per trunk. Moreover, TfL expects moving block signaling to raise District line capacity from 24 tph to 32, keeping the current reverse branching. The Victoria line already runs 36 tph and the Jubilee line soon will too, while the Central line runs 35 tph. So 36 vs. 32 seems like the difference coming from the final elimination of reverse branching, while more extensive reverse branching reduces capacity further.
The reason complex branching reduces capacity is that, as delays propagate, the schedule needs to incorporate a greater margin of error to recover from unexpected incidents. It also slows down the trains, since the trains are frequently held at merge points. The general rule is that anything that increases precision increases capacity (such as automation and moving block signaling) and anything that reduces precision reduces capacity; reverse branching reduces timetable precision, because each train can be delayed by incidents on more than one line, making delays more common.
What deinterlining in New York entails
NYCT has its work cut out for it when it comes to deinterlining. There are eight different points in the system where reverse-branching occurs – that is, where lines that do not share track in Manhattan (or on the G trunk outside Manhattan) share tracks elsewhere.
- The 2 and 5 trains share tracks on the Nostrand Avenue Line.
- The 2 and 5 also share tracks in the Bronx.
- The A and C trains share tracks on the two-track narrows through Lower Manhattan and Downtown Brooklyn.
- The A and D share the express tracks on Central Park West while the B and C share the local tracks.
- The E and F share the express tracks on Queens Boulevard, while the M and R share the local tracks, the E and M share the tunnel from Queens to Manhattan, and the N, R, and W share a different tunnel from Queens to Manhattan.
- The B and Q share tracks in Brooklyn, as do the D and N.
- The F and G share tracks in South Brooklyn.
- The M shares the Williamsburg Bridge tracks with the J/Z but runs in Manhattan on the same tracks as the F.
NYCT should work to eliminate all of the above reverse branches. The easiest to start with is #6: the junction at DeKalb Avenue should be set to keep the B and D trains together and to keep the N and Q together rather than to mix them so that the B shifts to the Q tracks and the D to the N tracks. This requires no changes in physical infrastructure, and has especially high benefits as the junction delays trains by several minutes in each direction. Moreover, the loss of one-seat rides is minimal: the BDFM and NQRW run closely parallel in Manhattan and intersect with a transfer at Herald Square in addition to the inconveniently long BQ/DNR transfer at Atlantic Avenue.
Another relatively easy reverse branch to eliminate is #8, a recent introduction from the 2010 service cuts. Previously, today’s M route in Queens and Manhattan was covered by the V train, which turned on the Lower East Side, while the M ran the same route as the J/Z, merging onto the R and thence the N in Brooklyn at rush hour. Today’s route is thus an M-V merger, which railfans including myself hoped would help decongest the L by creating an alternative route from Williamsburg to Midtown. Unfortunately, such decongestion has not happened, perhaps because gentrification in Williamsburg clusters near the L and not near the J or M.
Fixing the reverse-branching at DeKalb Avenue and on the Williamsburg Bridge is painless. The other reverse branches require a combination of hard decisions and new infrastructure.
Fixing reverse branches #3 and #4 requires no capital investment, just political will. Reverse branch #4 is there because there’s demand for two routes’ worth of capacity in the tunnel from Brooklyn but there’s only one express line on Eighth Avenue, and that in turn is the result of reverse branch #3; thus these two issues should be tackled together.
NYCT should decide between having the A and C trains run express between 145th and 59th Streets and the B and D trains run local, or the other way around. This is not an easy decision: either Washington Heights or Grand Concourse would get consigned to local trains. North of 145th the total number of boardings is 102,000 at B/D stations compared with 79,000 on the A/C, but conversely Concourse riders can change to the express 4 trains whereas Washington Heights’ only alternative is the local 1. However the A and C run, express or local, the E should run the opposite in Manhattan – it can merge to either the local or express tracks – and the express trains should continue to Brooklyn. The map I made doesn’t distinguish local from express service, but my suspicion is that Washington Heights should get express trains, on account of its long commutes and lack of fast alternatives.
The same problem of harshness occurs in reverse-branch #5. In theory, it’s an easy fix: there are three track pairs in Queens (Astoria, Queens Boulevard local, Queens Boulevard express) feeding three tunnels to Manhattan (63rd, 60th, and 53rd Streets). In practice, the three Manhattan trunks have astonishingly poor transfers between them in Midtown. Nonetheless, if it does nothing else, NYCT should remove the R from Queens Boulevard and route all 60th Street Tunnel trains to Astoria; together with fixing DeKalb Avenue, this would separate the lettered lines into two closed systems, inherited from the BMT and IND.
However, undoing the connection between the BMT and the IND probably requires constructing a transfer station in Long Island City between Queensboro Plaza and Queens Plaza, which involves a few hundred meters of underground walkway. Even then, the connection cannot possibly be convenient. The saving grace is that Eighth Avenue, Sixth Avenue, and Broadway are close enough to one another that passengers can walk to most destinations from any line.
Subsequently, NYCT should make a decision about whether to send express Queens Boulevard trains to 63rd Street and Sixth Avenue and local trains to 53rd and Eighth, as depicted in the above map, or the other way around. The problem is that the merge point between 53rd and 63rd Street Tunnels is one station east of Queens Plaza, at a local station, and thus the true transfer point is Roosevelt Avenue, far to the east. Riders on the local stations west of Roosevelt would get no choice where to go (though they get little choice today – both the E and M serve 53rd Street, not 63rd). The argument to do things as I depict them is to give the local stations access to 53rd Street; the argument to switch the lines is that there is more demand on 53rd than 63rd and also more demand on the express tracks than the local tracks, so the busiest lines should be paired. However, this in turn runs into turnback capacity limitations on the E in Manhattan, at the World Trade Center bumper tracks.
Potentially, NYCT could try to convert 36th Street into an express station, so that passengers could connect cross-platform. But such a dig would be costly and disruptive to operations. There were plans to do this at 59th Street on the 1/2/3 a few decades ago, for the transfer to the A/B/C/D, but nothing came of them.
Where new infrastructure is needed
The remaining reverse branches get increasingly more difficult. Already #7 requires new turnouts. The South Brooklyn trunk line has four tracks, but there’s not enough demand (or space in Manhattan) to fill them, so only the local tracks are used. There are occasional railfan calls for express service using the F, but it’s better to instead use the express tracks to segregate the G from the F. The G could be turned at Bergen Street on the local tracks, while the F could use the express tracks and then transition to the locals on new turnouts to be constructed at Carroll Street.
Also in the category of requiring new turnouts is #1: Rogers Avenue Junction is set up in a way that briefly forces the 2, 3, and 5 trains to share a short segment of track, limiting capacity. This can be resolved with new turnouts just east of the junction, pairing Nostrand Avenue Line with the local tracks and the West Side and the portion of the Eastern Parkway Line east of Nostrand with the express tracks and the Lexington Avenue Line. Trains on Eastern Parkway could either all go local, or keep the current mixture of local trains to New Lots (currently the 3) and express trains to Utica (currently the 4), skipping a total of two stations. This fix also reduces passengers’ access to one-seat rides, but at least there is a reasonable cross-platform transfer at Franklin Avenue, unlike on Queens Boulevard or at 145th Street and St. Nicholas.
And then there is #2, by far the most difficult fix. Demand on the White Plains Road branch in the Bronx is too strong to be a mere branch: the combined number of boardings at all stations is 166,000 per weekday, and besides, the line branches to Dyre Avenue near its outer end and thus needs the frequency of either a trunk or two branches to ensure adequate service to each other branch. This is why it gets both the 2 and 5 trains. There is unfortunately no infrastructure supporting a switch eliminating this track sharing: the 4 and 5 trains could both use this line, but then the 2 has no way of connecting to Jerome Avenue Line without new tunnels.
On the map, I propose the most obtrusive method of fixing this problem: cutting the 3 trains to a shuttle, with a new pocket track at 135th Street, letting passengers transfer to the 2, ideally cross-platform. With all through-trains running on the 2, there is no need (or space) for the 5 on White Plains Road, and instead the 5 should help boost the frequency on Jerome Avenue. In addition, some work is required at Woodlawn, which currently has bumper tracks, fine for a single branch but not for a non-branching trunk line (the bumper tracks on the L limit throughput to 26 tph no matter how good the electronics are).
Additional infrastructure suggested by deinterlining
Deinterlining is a service increase. Lines that today only get half or two-thirds service would get full trunk frequency: Second Avenue Subway would get the equivalent of the Q and N trains, the Astoria Line would get the entirety of 60th Street Tunnel’s capacity, Eighth Avenue would get more express trains, and 63rd Street Line and the South Brooklyn Line would get more than just the half-service of the F. With six track pairs on the lettered lines through Midtown and six north and east (Central Park West*2, Second Avenue, Astoria, Queens Boulevard*2), there is no room for natural branching to give more service to busy areas than to less busy ones.
One solution to this situation is targeted development on weak lines. Even with half service, South Brooklyn has underfull F trains, and Southern Brooklyn’s B, D, N, and Q trains aren’t much busier, making this entire area an attractive target for upzoning.
However, it’s more interesting to look at lines with extensions that suggest themselves. Second Avenue Subway has the obvious extension north to Harlem in phase 2, and a potential subsequent extension under 125th Street to Broadway, which is less obvious but popular among most area railfans (including one of my inside sources at NYCT). The Astoria Line has a natural extension to LaGuardia, ideally elevated over Ditmars to capture local ridership on Astoria as well as airport traffic; while the steel el structures in New York are soundboxes, it is possible to build quieter els using concrete (as on the 7 el over Queens Boulevard in Sunnyside) or a mixture of concrete columns and a steel structure (as on the Metro 2 and 6 els here in Paris).
The Nostrand Avenue Line provides an especially interesting example of a subway extension suggested by deinterlining. The terminal, Flatbush Avenue, was intended to be temporary, and as a result has limited turnback capacity. To prevent it from constraining the entire 2 route, which became the city’s most crowded even before Second Avenue Subway began decongesting the 4 and 5, it would be prudent to extend the line to Sheepshead Bay as the city intended when it planned the line in the 1910s.
In contrast, a subway extension under Utica, a stronger bus corridor than Nostrand with a strong outer anchor at Kings Plaza, loses value under deinterlining. It could only get a branch and thus have lower capacity than Nostrand. It would also definitely force branching on the express trains, whereas without such an extension they could run as a single unbranched line between Woodlawn and New Lots Avenue via Jerome Avenue, Lexington Avenue, and Eastern Parkway. A Utica subway should wait until there is political will to fund an entirely new crossing into Manhattan, presumably via Williamsburg to help decongest the L.
A second extension I have occasionally mooted, a subway under Northern, loses value even more. Such a subway would be a fourth trunk line in Queens and have to come at the expense of capacity on Queens Boulevard. It is only supportable if there is an entirely new tunnel to Midtown, passing under the mess that is the tracks in Long Island City.
A deinterlined New York City Subway
Fast Forward proposes moving block signaling on the most crowded subway segments, but typically only on trunks, not branches, and in some cases not even entire trunks. But in the long term, New York should transition to moving blocks and automation on all lines – at the very least the highly automated system used on the L, but ideally fully driverless operation, in recognition that wages are going up with economic growth but driver productivity isn’t. Simultaneously, deinterlined operations should allow tph counts in the mid 30s or even more (Metro 13 here runs 38 tph and Metro 14 runs 42).
Instead of the potpourri of lines offered today, there would be fewer, more intense lines. Nomenclature would presumably change to deal with the elimination of some services, clarifying the nature of the subway as a nine-line system in which five lines have four tracks and four lines have two. Each of these fourteen track pairs should be able to support a train every 90-105 seconds at the peak; not all lines have the demand for such frequency, and some have capacity-limiting bumper tracks that aren’t worth fixing (e.g. the 1 at Van Cortlandt Park), but many lines have the infrastructure and the demand for such capacity, including the express lines entering Midtown from Uptown or Queens.
Off-peak, too, service would improve. There is ample capacity outside rush hour, but turning the system into one of lines arriving every 4-5 minutes with strategic transfers rather than every 8-10 minutes would encourage people to take the trains more often. The trains would simultaneously be faster and more reliable, since incidents on one line would wreck service on other trains on the same line but leave the rest of the network unaffected.
With service improvements both during and outside rush hour, New York could expect to see substantial increases in ridership. Raising peak frequency from the current 24 tph to 36 tph on the busiest lines (today’s 2/3, 4/5, A/D, and E/F) is equivalent to building an entirely new four-track subway trunk line, and can be expected to produce similar benefits for passengers. The passups that have become all too familiar for riders on the 4, L, and other busy trains would become a thing of the past unless ridership rose 50% to match the increase in capacity.
In my writings about metro network design I’ve emphasized the importance of making sure every pair of intersecting lines have a transfer. Moreover, I’ve argued that missed connections often come from having very wide stop spacing, because large metro networks have very closely-spaced lines in the core, and if the stop spacing in the core is too wide, as in Moscow, then lines will frequently cross without transfers. In contrast, in Paris, where the Metro has very closely-spaced stops, there is only one missed connection on the Metro, between Lines 5 and 14. However, what’s missing from this discussion is what to do on lines that, due to network design, have to run express and miss some connections. This question mattered to most RER lines and currently matters to Crossrail and Crossrail 2, and will be critical in any New York regional rail plan.
I claim that the most important connections to prioritize should be to,
- The busiest lines.
- Lines that are orthogonal to the newly-built express lines.
But before explaining this, I’d like to go over the scale of the underlying problem of prioritizing transfers. For a start, look at the Underground in Central London:
Crossrail is the dashed gray line. Between Paddington and Liverpool Street, it intersects seven north-south lines, including five in rapid succession on the West End; stopping at all of Bond Street, Oxford Circus, Tottenham Court Road, and Holborn would slow down too much what’s intended to be an express relief line to the Central line.
Stopping between two stations and having transfers to both is possible – look at Farringdon-Barbican and at Moorgate-Liverpool Street – but results in very long transfer times. The RER has opted for this solution at Auber, which is located between the Opera and Saint-Lazare, with a transfer stretching over three successive stations on Line 3, leading to legendarily labyrinthine transfers between the RER and the Metro:
Observe that in contrast with the RER A’s convoluted transfer at Auber, the RER B simply expresses between Chatelet-Les Halles and Gare du Nord, missing the connection to the east-west Lines 3, 8, and 9 and the north-south Line 7, and only connecting to the circumferential Line 2 via a long underground passageway. The reason for this is that a transfer station at Bonne Nouvelle or Sentier would be very expensive to construct; the RER’s stations were all extremely costly, and the RER A’s record of $750 million per km for the Nation-Auber segment remains unbroken outside the Anglosphere. On Crossrail (the recordholder in cost per km outside the US, soon to be overtaken by Crossrail 2), it’s the stations that drive up costs as well, and the same problem is even more acute in New York.
The tension is then between the network effects of including more transfer points, and the costs and slowdowns induced by stopping more often. The first point in my claim at the beginning of this post follows immediately: it’s more valuable to stop at transfer points to busier lines. The RER A misses Line 5 entirely, as does the express Line 14, because Line 5 is so weak that it’s not worth it to detour from Gare de Lyon through Bastille to connect to it; the oldest plans for the RER A had a stop at Bastille and not at Gare de Lyon, but under SNCF’s influence the system was redesigned to connect to the train stations better and thus Bastille was replaced.
Whereas the RER A in theory connects to every north-south one except the weakest (although the second strongest after Line 4, Line 13, has an even longer connection than at Chatelet), Crossrail does the opposite. The busiest station in London excluding mainline stations is Oxford Circus, thanks to the three-way transfer of the Bakerloo, Victoria, and Central lines; the Victoria line is the busiest in the system per km (although the longer Northern and Central lines have more riders), and it’s certainly the busiest north-south trunk line. However, plans to have a transfer to both Bond Street and Oxford Circus were rejected in favor of a connection to Bond Street alone. The reason is that London’s low-capacity passageways get congested, and TfL’s hamfisted solution is to omit critical transfers, a decision also made at the Battersea extension of the Northern line, which will miss a connection to the Victoria line at Vauxhall.
This brings me to the second transfer priority: it’s the most important to connect to orthogonal lines. The reason is that parallel lines, especially closely parallel lines, are less likely to generate transfers. New York’s four-track subway lines have very high volumes of local-express transfers, because those are easy cross-platform interchanges; as soon as any walking between platforms is required (for example, on the Lexington Avenue Line at 59th and 86th Streets), transfer volumes fall dramatically. In Paris, transfers between Line 1 and the RER A happen, but usually for longer-distance travel; I find it faster to take Line 1 from Nation to Chatelet than to take the RER A, even without any transfer, purely because it’s easier to get between the street and the Metro platforms at both ends.
This issue was never really in contention when Paris built the original RER system. The one place where the RER prioritized a transfer to a same-direction Metro line over an orthogonal one, Gare du Nord, is such an important destination for commuter and intercity trains that it’s obviously justified to prioritize it over an easier connection to Line 2. However, more recently, the RER E has seen this issue surface with the location of the infill Rosa Parks station. The RER E could have sited a station at the intersection with Line 5, but Line 5 goes northeast and serves much the same area as the RER E, so the network effects from an interchange would be weak. Instead, the station is sited to interchange with the circumferential T3 tramway, which opens up a connection toward Nation and eventually toward Porte d’Asnieres.
In London, the same question is critical to the central route of Crossrail 2. The current plan has three Central London stops: Victoria, Tottenham Court Road (with a transfer to Crossrail), and Euston-St. Pancras. But Victoria itself is not much of a destination, and of the two lines served, the District and the Victoria, the Victoria line is parallel to Crossrail 2 rather than orthogonal to it. The purpose of Crossrail 2 is to add north-south capacity through the West End to decongest the Victoria line and reduce the shuffle at Victoria station between mainline trains and the Underground; to this end, there’s no need to stop at Victoria station itself.
To this effect, Martha Dosztal proposes moving Crossrail 2 to Westminster or possibly Charing Cross. Instead of spending $2 billion on a station at Victoria, London would need to spend probably a comparable amount on a station that interchanges with lines that go northwest-southeast like Jubilee or Bakerloo rather than on the parallel Victoria line; moreover, Westminster and Charing Cross both have connections to the District line, so Crossrail 2 would still connect to all three east-west Underground lines.
Finally, the application to New York is the most delicate. New York’s scores of missed connections come from deliberate indifference on the IND’s part to transfers with the older lines rather than any systematic attempt at prioritizing important interchanges; the older IRT and BMT systems have between them just two missed connections (3/L in Brooklyn, 4-5/R-W in Lower Manhattan). But including better connections in the event the city builds more rail lines remains critical. Second Avenue Subway gets this right by having a cross-platform transfer to the east-west F; there’s no transfer to the north-south Lexington Line, but this is less important given Second Avenue’s role as a Lexington relief line.
Regional rail transfers are especially circumscribed in New York given the system’s nature as a few short tunnels: new tunnels across the Hudson, and ideally a connection between Penn Station and Grand Central. This is why there is little room for improving connectivity between the subway and what I call Lines 1-3 of New York regional rail. However, the priorities I’m advocating in this post suggest two important things about Penn Station: first, it’s important to reopen passageways to Sixth Avenue to allow connections to the NQRW and BDFM trains; and second, it’s not important to have a connection to the 7 at Hudson Yards, as IRUM proposes.
On more speculative lines involving longer tunnels, the same priorities point to my proposed stopping pattern in and around Lower Manhattan. What I call Line 4, a north-south line from Grand Central to Staten Island stopping at Union Square and Fulton Street would intersect the east-west subways: the 7 at Grand Central, the L at Union Square, and PATH and most Brooklyn-bound trains at Fulton Street. The only missed subways – the F/M at Houston Street and the N/Q at Canal – go mostly north-south (except the M, which has a same-platform transfer with the J/Z, connecting at Fulton). Likewise, what I call Line 5, connecting from Pavonia to Atlantic Terminal, would connect to most north-south subways at Fulton Street.
Ideally, it’s better to make every interchange, and subway builders around the world should aim for very long-term planning in order to prevent missed connections in the future. However, when the inevitable changes happen and missed connections are unavoidable, there are emergent rules for which are more important: busier lines are more important than less busy lines, and less obviously, lines that are orthogonal to the new line are more important than ones that are parallel. These priorities make it possible to build express lines that maximize regional connectivity with minimal loss of travel time due to making local stops.
Last week, I wrote about which regional rail lines should run local and express trains and which should only run locals. I gave various guidelines, specific to that mode of transportation. The same question makes a lot of sense for subways (or elevated lines), and is especially important for large cities building new metro networks, typically in developing countries. The key difference is that subway trains almost always run so frequently that the only way to have local and express services is to build four-track mainlines, like in New York. So really, this is a question about when it’s useful to build four-track subways instead of two-track subways.
The cost of a four-track subway is higher than that of a two-track subway. However, the difference depends on the method of construction. Cut-and-cover four-track subways do not appear to be much more expensive than two-track subways; in the 1900s, New York had little to no cost premium over London or Paris. The First Subway’s underground segments, slightly less than half of which are four-track, cost $39 million per km in today’s money, compared with about $29 million per km in Paris in the same era (see sources in this post). The Metropolitan line in London cost about the same: £1.3 million for 6 km in the early 1860s, or about $30 million per km.
In contrast, boring four tracks appears to cost twice as much as boring two. It’s hard to find examples, since four-track bores are extremely rare; the examples I do know, such as the East River Tunnels and the tunnel carrying the Lexington Avenue Line under the Harlem River, are short. There are bound to be efficiencies in engineering and sitework reducing the cost of boring, just as there are with cut-and-cover, but the majority of the cost of tunneling is the boring and the systems. The majority of the rest is stations, and the local stations can be built for not much of a premium over stations on a two-track line, but the express stations require considerably more excavation.
What this means is that cities that build cut-and-cover should probably aim to build four tracks rather than two. In retrospect, Paris should have built Metro Line 1 with four tracks: the narrowest street segment, Rue de Rivoli, runs for 3 km and is about 20-23 meters wide, which can take four tracks if there are only local platforms, and everything else is at least 30 meters and could take four tracks and express platforms. The only express station under Rivoli would probably be Chatelet, where there is a wide square where the station footprint could expand.
The question of whether to use cut-and-cover today is a separate issue. It’s easier for the first few lines than for subsequent lines, which have to cross under the old lines. Nonetheless, it’s still in use, for example in China; the lack of express tracks on Chinese subways has led to criticism on some railfan forums, particularly by Japanese railfans, who are used to the fast express trains of the JRs through urban areas. But in India, the longest underground segment in Delhi, on the Yellow Line, appears to be bored, running deep under Old Delhi. The one potential pitfall is that bored tunnels, while generally more expensive to construct than cut-and-cover tunnels if wide streets are available, are nimbler, making it easier to build lines to high standards, with wide curves.
The two obvious benefits of express subways are speed and capacity. New York averages a decent speed, just under 30 km/h, buoyed by express trains that average about 36 km/h. When frequency on both the local and express tracks is adequate, which it regrettably isn’t most of the time in New York, it’s possible to use cross-platform local/express transfers to improve trip times even for people on the local stations.
The capacity benefits are sometimes compromised by transfers. In New York, the express tracks are consistently more crowded than the local tracks on the main lines, and the Upper West Side in particular sees the city’s most overcrowded trains on the express tracks run alongside the second least crowded on the local tracks. However, on the East Side, the local and express trains under Lexington are both quite full. The number of passengers they carry would overwhelm any two-track line: to carry the same number of passengers on just two tracks at the current peak frequency, each train would need about 2,100 passengers, more per unit of train floor area than the most crowded Tokyo Metro lines.
There are also indirect effect of four-tracking. The most distant stations are presumably express-only, or, if not, passengers will transfer to an express train at the first opportunity. This means that adding local stops does not increase trip times for passengers far out, which in turn argues in favor of tighter stop spacing on local trains, to provide more coverage. Evidently, New York has one of the smallest interstations (on local trains) of any major metro network in the world, surpassed only by Paris, which built the Metro without regard for the suburbs. Second Avenue Subway, built with just two tracks, has wider stop spacing than other Manhattan north-south mainlines, missing 79th Street, with the planned phase 2 stopping at 106th instead of 103rd and 110th.
I have hammered repeatedly that metro systems need to avoid three pitfalls of network planning:
- Tangential lines, starting as radial farther out but becoming circumferential closer in rather than staying radial and serving city center.
- Reverse-branching: a common trunk in an outlying area splitting into branches in city center, the opposite of the more normal branching arrangement.
- Missed connections, in which two lines intersect without a transfer.
It is easier to miss connections when the stop spacing is wider, because city centers are so small that line 1 can easily miss the road that line 6 will later run under. The Paris Metro has just one missed connection (M5/M14), and the city made a failed effort in the 1900s to bring Line 5 to what would be the transfer station, Gare de Lyon. New York has only two missed connections among the lines built from 1900 to the 1920s (Junius/Livonia on the 3/L, Bowling Green/Whitehall on the 4-5/RW), both of which are easy to fix; the city’s tens of misses come from a deliberate decision to avoid transfers in the lines built in the 1930s. Systems with wider stop spacing have more opportunities for missed connections, such as Tokyo, Shanghai, and Moscow.
Four-track mainlines short-circuit this problem doubly. First, fewer lines are required to provide the same coverage and capacity. On the eve of the Great Depression, New York had six subway mainlines, three with four tracks and three with two, and 2 billion annual riders. Even if a city insists that all transfer stations be express (which is the case in New York among lines built before the 1930s, though at one station express platforms were only retrofitted decades later), there are fewer potential intersections; at city center, even the express lines are unlikely to have very wide stop spacing.
Moreover, it’s fine to miss transfers on express lines. The reason missed connections are so bad is that the alternative option typically requires a three-seat ride. For example, the 1 passes between Columbus Circle-59th Street and 50th Street without a connection to the E train, leaving connecting passengers with one of two options: ride to Times Square and transfer there, which is both a detour and a very long walk between the platforms, or change to the B or D at 59th and then again to the E at 53rd; the latter option is the faster one, saving about 5 minutes of in-vehicle time and 3 minutes of transfer time.
But if one of the transfers is cross-platform, then a three-seat ride is less onerous. This is especially true if this transfer is local/express on a long shared trunk line, where the transfer stations usually don’t get as crowded as between two separate trunks. This means that it’s possible, if there is no better option, to have local-only transfers. Two of the top stations in New York, 53rd/Lex and Columbus Circle, are local-only transfers.
Small cities don’t need to think about express trains very much. Transit cities with about 2 million people in their metro areas, such as Vienna, Stockholm, Prague, Budapest, and Hamburg, make do with a handful of metro lines, sometimes supplemented by regional rail. But as they grow, the number of urban rail lines they need grows to the point that a coherent two-track network is too difficult, not to mention too slow. Paris manages to make do with the RER acting as the express layer, but outside India and Pakistan, cities that are just beginning to build their metro networks don’t have large legacy commuter rail networks to leverage for express service. In Africa between the Sahara and South Africa, nearly everything has to be built from scratch, and the same is true of Bangladesh and much of Southeast Asia and Latin America.
Moreover, in developing countries, a large number of cities either are megacities or can expect to grow to that size class soon. This is less true in Latin America, nearly all of which has at- or below-replacement birth rates, already high urbanization rates, and negative net migration (thus, the main case for four-track subways in Bogota hinges on the fact that the city has absurdly wide roads for cut-and-cover, not on future scale). However, in poor countries with high birth rates and low urbanization rates, cities can expect to increase their population many times over in the next few decades. Lagos and Dhaka are already huge, and midsize cities such as Nairobi, Kampala, Dar es Salaam, Addis Ababa, Khartoum, Accra, Abidjan, Douala, and Sanaa can expect to grow to that size class within a generation, as can midsize cities in countries with lower birth rates, such as Chittagong, Hanoi, and Ho Chi Minh City. In such cities, transportation planning should presume much greater scale than may seem warranted today.
A smaller-scale version of this principle can be found in cities that are growing rapidly due to immigration, especially Singapore but also Sydney, Melbourne, Toronto, Vancouver, and Stockholm. Such cities might want to consider infrastructure investments based not on their present-day population levels, but on those that they can expect after 30 more years of high migration rates. Vancouver and Stockholm are too small for express subways no matter what, and Toronto has already built its central spines with two tracks (and is upgrading its regional rail network to act as an express layer), but Singapore, Sydney, and Melbourne should all think about how to plan for the possibility that they will have 10 million people within 50 years.
Two weeks ago I wrote about the Brooklyn bus redesign I’m working on with Eric Goldwyn. The MTA, which is aware of our efforts, came up with its own plan. So far details are scant; there is a presentation available online, which talks about goals (“network redesign,” “higher frequency”) but no specifics (“a more gridded network,” “6-minute off-peak frequency on the main routes”).
At least so far, the goals seem solid. The MTA has the following list of improvements:
- Redesign the network from top to bottom based on customer input, demographic changes, and travel demand analysis. Provide better connectivity and more direct service in every neighborhood
- Optimize the existing network with community consultation by removing closely-spaced and underutilized stops and making street design changes on select corridors in coordination with NYC DOT
- Expand off-peak service on strategic routes using a toolbox of service strategies including increased frequency and demand based service adjustments
- Expand Traffic Signal Priority (TSP) to allow an approaching bus to hold a green light or shorten a red light
- Seek exclusive busways on priority corridors to give buses full access in major congested areas
- Identify opportunities for new bus lanes and queue jumps in 2018
- Advocate for strengthened NYPD enforcement of bus lanes to keep bus stops and travel lanes clear throughout the system
- Recommend dedicated transit-priority traffic teams to focus enforcement in key areas to ensure buses move quickly through trouble spots
- Use Bus Lane Enforcement Cameras mounted on buses to automatically identify violations and issue tickets. Advocate for legislation to expand beyond the existing 16 authorized routes
- Install tap readers to speed up the boarding process so buses spend less time waiting at stops
- Introduce all-door boarding to allow riders to get on through any door of the bus
- Explore options for a future cashless system to maximize reductions in boarding time
- Expand fare enforcement on regular bus service to reduce evasion and restore fare revenue
The main problems only appear toward the end, with the implementation of off-board fare collection and all-door boarding. The insistence on “fare enforcement,” which could mean regular proof of payment (POP) inspections but could also mean worse, such as armed cops (not practiced in New York on SBS but practiced on some other US systems, like BART) or holding the bus during inspection (which New York does practice, unlike Berlin and other German-speaking cities). Overall I’m relatively sanguine about Andy Byford specifically – he’s not American and is not used to American levels of police militarization.
However, another aspect of the POP proposal is troubling: the connection with tap readers. The plan’s full text (which is barely more detailed than what I quote above) mentions that POP should come with the so-called New Fare Payment System, or NFPS, which New York is currently planning to roll out starting in 2019, continuing until 2023. The NFPS is based on worst industry practices cobbled from American and British ideas. Here is my second post ever, discussing the plans for smartcards in New York in 2011. New York ignored (and keeps ignoring) the smartcard implementations in a number of East Asian cities in its zeal to make people treat their credit card as a transit fare card, ensuring the agency can surveil all passengers; perhaps Americans lack the values of freedom and individual privacy of Japan and Singapore.
New York also ignored (and keeps ignoring) the POP implementations in cities with paper tickets, such as most of Central Europe. Smartcards are not required for POP: the German-speaking world has POP with paper tickets, as did Vancouver on SkyTrain and some bus lines even before the Compass Card debacle. In Singapore I saw a ticket inspection on a bus even before EZ-Link; I had a magnetic farecard at the time. Given the enormous waste coming from making passengers line up and pay the driver, it’s imperative to move toward POP as soon as possible, even if it means equipping inspectors with MetroCard readers rather than smartcard readers. MetroCard may only last for five years if the NFPS schedule doesn’t keep slipping, but handheld magnetic card readers are a cheap technology whereas making buses idle while passengers dip cards one at a time is not so cheap.
The zeal to go cash-free is the final troubling aspect of New York’s ideas about fare payment, especially when bundled with the idea that the bank card is the fare card. Not everyone has a local bank account. Tourists don’t (and even cards that are supposed to work abroad don’t always). Low-income city residents don’t, either: 11.7% of New York households have no bank account, and they disproportionately appear to be in poverty, judging by which neighborhoods they are most concentrated in. The MTA has always treated anonymous smartcards as an afterthought, and going cash-free means there is no recourse for the unbanked or even for many tourists.
Nor is cash-free operation even necessary. An on-board farebox is compatible with POP. In this system, riders can board from any door, and the driver will begin moving as soon as all passengers have boarded, even if not all passengers have paid yet. Riders with valid transfers or season passes need not do anything. Riders with a pay-per-ride smartcard and no transfer should tap their card at a validator at any bus door or bus stop (validators are cheap that blanketing the system with them is practically free). The remaining passengers should walk to the farebox and pay there; perhaps some busy stations should get fareboxes, as all SBS stops do in New York today, but if the MTA only expects a few smartcard-free, non-transfer passengers at a stop, then having them pay on board a moving bus should not be a problem.
I’d like to stress that other than the ongoing hiccups of the English-speaking world with fare payment systems (hiccups that it seems to export to Paris), the plan appears good, from what few details the MTA has released. There are plans for increasing the average distance between bus stops, adding more bus lanes, getting serious about signal preemption, raising off-peak frequency, and letting passengers board from all doors. The MTA really is noticing that its bus system is collapsing and really is making serious plans to avert a death spiral.
I’ve recently started working part-time on a project for the Marron Institute at NYU about bus restructuring in Brooklyn; at the end of this summer, I expect to release a proposal for service upgrades and a new map. I’m working on this with Marron scholar Eric Goldwyn, who is funded by the TWU, which is worried that ridership collapse may lead to service cuts and job losses, but I’m funded directly by Marron and not by the union.
Some of what’s likely to appear in the final report should be familiar to regular readers of this blog, or of Human Transit, or of the work TransitCenter has been doing. As I wrote in Curbed earlier this year, bus operating costs in New York are unusually high because the buses are slow, as the main operating costs of buses scale with service-hours and not service-km. Thus, it’s important to speed up the buses, which allows either providing higher frequency at the same cost or the same frequency at lower cost. A bus speedup should include systemwide off-board fare collection and all-door boarding (common in the German-speaking world but also in San Francisco), wider stop spacing, dedicated lanes wherever there is room, and signal priority at intersections; the TWU is an enthusiastic proponent of off-board fare collection, for reasons of driver safety rather than bus speed.
While bus speedups are critical, their impact is not as Earth-shattering as it might appear on paper. New York’s SBS routes have all of the above features except signal priority, and do save considerable time, but are still slow city buses at the end of the day. Brooklyn has two SBS routes: the B44 on Nostrand, averaging 15 km/h (local B44: 11.3), and the B46 on Utica, averaging 13.7 (local B46 on the shared stretch: 10.8). Their speed premiums over the local routes are toward the high end citywide, but are still 30%, not the 200% speed premium the subway enjoys. Moreover, the speed premium over non-SBS limited routes is 15-20%; put another way, between a third and a half of the speed premium comes purely from skipping some stops.
I mentioned in my last post that I met Carlos Daganzo at Berkeley. Daganzo was responsible for the Barcelona bus redesign, Nova Xarxa; you can read some details on Human Transit and follow links to the papers from there. The guiding principles, based on my conversation with Daganzo and on reading his papers on the subject, are,
- Barcelona has high, relatively uniform density of people and jobs, so there’s no need for buses to hit one CBD. Brooklyn has about the same average residential density as Barcelona, but has a prominent CBD at one corner, but as this CBD is amply served by the subway, it’s fine for buses to form a mesh within the subway’s gaps.
- Nova Xarxa involved widening the stop spacing in Barcelona from less than 200 meters to three stops per km, or a stop every 300-350 meters; Daganzo recommends even wider stop spacing.
- While Barcelona’s street network is strictly gridded, the buses don’t run straight along the grid, but rather detour to serve key destinations such as metro stops. This is an important consideration for Brooklyn, where there are several distinct grids, and where subway stops don’t always serve the same cross street, unlike in Manhattan, where crosstown routes on most two-way streets are assured to intersect every north-south subway line.
- The percentage of transfers skyrocketed after the network was implemented, standing at 26% at the end of 2015, with the model predicting eventual growth to 44%, up from 11% before the redesign.
- The network was simplified to have 28 trunk routes, the least frequent running every 8 minutes off-peak.
The high off-peak frequency in Barcelona is a notable departure from Jarrett Walker’s American network redesigns; the evidence in Houston appears mixed – ridership is about flat, compared with declines elsewhere in the country – but the percentage of transfers does not seem to have risen. Jarrett says in his book that having a bus come every 10 minutes means “almost show-up-and-go frequency” with no need to look at schedules, but his work in Houston and more recently in San Jose involves routes running every 15 minutes.
Moreover, unreliable traffic in these car-dominated cities, in which giving buses dedicated lanes is politically too difficult, means that the buses can’t reliably run on a schedule, so the buses do not run on a clockface schedule, instead aiming to maintain relatively even headways. (In contrast, in Vancouver, a less congested street network, with priority for all traffic on the east-west main streets on the West Side, ensures that the buses on Broadway and 4th Avenue do run on a fixed schedule, and the 4th Avenue buses have a 12-minute takt that I still remember four years after having left the city.)
I’ve talked about the importance of radial networks in my posts about scale-variant transit. I specifically mentioned the problem with the 15-minute standard as too loose; given a choice between an untimed 15-minute network and a timed 30-minute network, the latter may well be more flexible. However, if the buses come every 5 minutes, the situation changes profoundly. Daganzo’s ridership models have no transfer penalty or waiting penalty, since the buses come so frequently. The models the MTA uses in New York have a linear penalty, with passengers perceiving waiting or transferring time on the subway as equivalent to 1.75 times in-motion time; bus waiting is likely to be worse, since bus stops are exposed to the elements, but if the average wait time is 2.5 minutes then even with a hefty penalty it’s secondary to in-vehicle travel time (about 18 minutes on the average unlinked bus trip in New York).
Unfortunately, that high frequently does not exist on even a single bus line in Brooklyn. Here is a table I created from NYCT ridership figures and timetables, listing peak, reverse-peak, and midday frequencies. Five routes have better than 10-minute midday frequency: the B12, the B6 and B35 limited buses, and the B44 and B46 SBSes, running every 7, 7.5, 8, 8, and 6 minutes respectively. In addition, the B41 limited and B103 have a bus every 9 and 7.5 minutes respectively on their trunks, but the B41 branches on its outer end with 18-minute frequencies per branch and the B103 short-turns half the buses. Another 14 routes run every 10 minutes off-peak, counting locals and limiteds separately.
The problem comes from the split into local and limited runs on the busiest buses. The mixture of stopping patterns makes it impossible to have even headways; at the limited stops, the expected headway in the worst case is that of the more frequent of the two routes, often about 10 minutes. The average ridership-weighted speed of Brooklyn buses is 10.75 km/h. An able-bodied passenger walking at 6 km/h with a 10-minute head start over a bus can walk 2.25 km before being overtaken, which can easily grow to 3 km taking into account walking time to and from bus stops. To prevent such situations, it’s important to run buses much more frequently than every 10 minutes, with consistent stopping patterns.
This does not mean that NYCT should stop running limited buses. On the contrary: it should stop running locals. The SBS stop spacing, every 800 meters on the B44 and B46, is too wide, missing some crossing buses such as the B100 (see map). However, the spacing on the B35 limited is every 400 meters, enough to hit crossing buses even when they run on one-way pairs on widely-spaced avenues. The question of how much time is saved by skipping a stop is difficult – not only do different Brooklyn buses give different answers, all lower than in Manhattan, but also the B35 gives different answers in different directions. A time cost of 30 seconds per stop appears like a good placeholder, but is at the higher end for Brooklyn.
The question of how many stops to add to SBS on the B44 and B46 has several potential answers, at the tight end going down to 400 meters between stops. At 400 meters between stops, the B44 would average 13 km/h and the B46 12 km/h. At the wide end, the B44 and B46 would gain stops at major intersections: on the B44 this means Avenue Z, R, J, Beverly, Eastern Parkway, Dean, Halsey, and Myrtle, for an average interstation of 570 meters and an average speed of 14 km/h, and on the B46 this means Avenue U, Fillmore, St. John’s, and Dean, for an average interstation of 610 meters an average speed of 13 km/h. Consolidating all buses into the same stopping pattern permits about a bus every 2.5 minutes peak and every 4 minutes off-peak on both routes.
On the other routes, consolidating local and limited routes required tradeoffs and cannibalizing some peak frequency to serve the off-peak. While it may seem dangerous to limit peak capacity, there are two big banks that can be used to boost off-peak frequency: time savings from faster trips, and greater regularity from consolidating stop patterns. The B82 is an extremely peaky route, running 7 limited and 10 local buses at the peak and just 6 buses (all local) for a four-hour midday period; but there is a prolonged afternoon shoulder starting shortly after noon with another 6 limited buses. Some peak buses have to be more crowded than others just because of schedule irregularity coming from having two distinct stop patterns. Consolidating to about 15 buses per hour peak and 10 off-peak, cannibalizing some frequency from the peak and some from the shoulders, should be about neutral on service-hours without any additional increase in speed.
The sixth post on this blog, in 2011, linked to frequent maps of Brooklyn, Manhattan, and Bronx buses, using a 10-minute standard. There has been some movement in the top buses since 2011 – for one, the B41 route, once in the top 10 citywide, has crashed and is now 16th – but not so much that the old map is obsolete. A good place to start would be to get the top routes from a 10-minute standard to a 6-minute standard or better, using speed increases, rationalization of the edges of the network, and cannibalization of weak or subway-duplicating buses to boost frequency.
Thanks to the invitation of Adina Levin’s Friends of Caltrain, I came to the Bay Area for a few days, giving two talks about regional rail best industry practices in front of Friends of Caltrain, Seamless Bay Area, and SF Transit Riders. My schedule was packed, including a meeting with a world-leading expert in transportation systems in which I learned about the Barcelona bus service changes; a Q&A about both general and Bay Area-specific issues for Bay City Beacon subscribers; and several other meetings.
My two talks were in Mountain View and San Francisco, and used the same slides, with minor corrections. Here are the slides I used in San Francisco; I consolidated the pauses so that each page is a slide rather than a line in a slide. This was also covered in Streetsblog, which gives more background and gives some quotes from what I said during the presentation, not printed in the slides.
Unlike in my NYU presentation last year, I did not include a proposed map of service improvements. The reason is that in the Bay Area, there are more questions than answers about which service should use which piece of infrastructure. This makes fantasy maps dangerous, as they tend to fix people onto one particular service pattern, which may prove suboptimal based on decisions made elsewhere in the system. This is not a huge problem in New York or Boston, where the alignments naturally follow where the stub-end commuter lines are, with only a few questions; but in the Bay Area, the situation is more delicate, because big questions like “can/should Caltrain get a trans-Bay connection from San Francisco to Oakland and the East Bay?” can go either way.
The role of redevelopment in the area is especially important. Unlike New York, Paris, or other big transit cities, San Francisco does not have much density outside the city proper, Oakland, or Berkeley. Moreover, there is extensive job sprawl in Silicon Valley, which contributes to a last-mile problem for public transit; usually first-mile access is a bigger problem and high-end jobs tend to cluster near train stations. But conversely, the high incomes in the Bay Area and the growth of the tech industry mean that everywhere TOD is permitted in the core and the suburbs, it will be built. This impacts decisions about the total size of transit investment.
At present-day development patterns, San Francisco proper really doesn’t need more rail construction except Geary and the Downtown Extension, depending on construction costs. But general upzoning makes Geary worth it even at $1 billion per km and opens up the possibilities of four-tracking Caltrain within the city (which means expanding some tunnels), giving the N-Judah dedicated tracks and a dedicated tunnel under Mission, and extending the Central Subway to the north and northwest. The land use in the Richmond and Sunset Districts today supports a fair amount of transit, but not new subways if there’s no cost control.
Governors Andrew Cuomo (D-NY) and Phil Murphy (D-NJ) announced that they would cooperate to form a Lower Hudson Transportation Association, or LHTA, to supersede what they described as antiquated 20th-century thinking and bring the region’s transportation into the 21st century. LHTA would absorb the transportation functions of Port Authority, which senior New York state officials speaking on condition of anonymity called “irredeemably corrupt,” and coordinate planning across the region. Negotiations with the state of Connecticut are ongoing; according to planners in New Jersey, the timing for the announcement was intended to reassure people that despite the lack of federal funding for Gateway, a lower-cost modified version of the project would go forward.
But the first order of business for LHTA is not Gateway. The governors’ announcement mentioned that LHTA would begin by integrating the schedules and fares throughout the region. By 2019, passengers will be able to transfer between the New York City Subway and PATH for free, and connect from the subway to the AirTrain JFK paying only incremental fare. Engineering studies for removing the false walls between PATH and F and M subway platforms are about to begin.
Commuter rail fare integration is also on the table. Currently, the fare on the subway is a flat $2.75. On commuter rail, it is higher even within New York City: a trip between Jamaica Station and New York Penn Station, both served by the E line of the subway, is $10.25 peak or $7.50 off-peak on the Long Island Railroad (LIRR). The governors announced that they would follow the lead of European transportation associations, such as Ile-de-France Mobilités in Paris, and eliminate this discrepancy under LHTA governance, which also includes revenue sharing across agencies. Detailed studies are ongoing, but in 2019, LHTA will cut commuter rail fares within New York City and several inner cities within New Jersey, including Newark, to be the same as the subway fare, with free transfers.
Simultaneously, LHTA will develop a plan for schedule integration, coordinating New Jersey Transit, the LIRR, Metro-North, and suburban bus agencies. In order to make it easier for suburban passengers to reach commuter rail stations, the suburban buses will be timed to just meet the commuter trains, with a single ticket valid for the entire journey. Today most passengers in the suburbs drive to the commuter rail stations, but the most desirable park-and-rides are full. Moreover, the states would like to redevelop some of the park-and-rides as transit-oriented development, building dense housing and retail right next to the stations in order to encourage more ridership.
Moreover, the LIRR and New Jersey Transit’s commuter trains currently stub-end at Penn Station in opposite directions. LHTA is studying French and German models for through-running, in which trains from one suburb run through to the other instead of terminating at city center. Planners within several agencies explain that the systems on the Long Island and New Jersey side are currently incompatible – for example, LIRR trains are electrified with a third rail whereas New Jersey Transit trains are electrified with high-voltage catenary – but reorganizing these systems for compatibility can be done in a few years, well before the Gateway project opens.
In response to a question about the cost of this reorganization, one of the planners cited the Swiss slogan, “electronics before concrete.” Per the planner, electronics include systems, electrification, and software, all of which are quite cheap to install, whereas pouring concrete on new tunnels and viaducts is costly. The planner gave the example of resignaling on the subway: the New York Times pegged the cost of modernizing subway signals at $20 billion, and this could increase capacity on most lines by 25 to 50 percent. But the cost of building the entire subway from scratch at today’s costs in New York is likely to run up to $200 billion.
But while the immediate priorities involve fare and schedule integration, LHTA’s main focus is the Gateway project. There are only two commuter rail tracks between New Jersey and Penn Station, and they are full, running a train every 2.5 minutes at rush hour. The Gateway project would add two more tracks, doubling capacity. The currently projected cost for the tunnel is $13 billion, but sources within New York said that this number can be brought down significantly through better coordination between the agencies involved. This way, it could be funded entirely out of local and state contributions, which add up to $5.5 billion. When pressed on this matter, officials and planners refused to say outright whether they expect $5.5 billion to be enough to cover the tunnel, but some made remarks suggesting it would be plausible.
Previous estimates for the costs of Gateway adding up to $30 billion include substantial extra scope that is not necessary. Sources on both sides of the Hudson report that the main impetus for the formation of LHTA was to coordinate schedules in a way that would make this extra scope no longer necessary. “With last decade’s ARC, there was a cavern under Penn Station to let trains reverse direction and go back to New Jersey,” explains one of the planners; ARC was a separate attempt to add tracks to the Hudson rail crossing to Penn Station, which Republican Governor Chris Christie canceled in 2010 shortly after his election. “With Gateway, there was the plan for Penn Station South, condemning an entire Manhattan block for the station for $7 billion. With the plans we’re developing with LHTA we don’t need either Penn South or a cavern to let trains run between stations.”
Moreover, some planners suggested reactivating plans to connect Penn Station and Grand Central as part of Gateway. They refused to name a cost estimate, but suggested that at the low end it could be funded out of already-committed state money. Under this plan, there would be through-running between not just New Jersey Transit and the LIRR but also Metro-North, serving the northern suburbs of New York and Connecticut. Sources at the Connecticut Department of Transportation said they are studying the plan and have reservations but are overall positive about it, matching the reports of sources within New York, who believe that Connecticut DOT will join LHTA within six months.
Officials are optimistic about the effects of LHTA on the region both privately and publicly. The joint press release referred to the metro area as “a single region, in which decisions made in far apart areas of New York nonetheless affect people in New Jersey and vice versa.” Planners in both states cited examples of friends and family in the other state who they would visit more often if transportation options were better. With better regional rail integration, they said, people would take more trips, improving regional connectivity, and take fewer trips by car, reducing traffic congestion and pollution.
I’ve discussed before the topic of missed connections on subway systems, both here and on City Metric. I’ve for the most part taken it for granted that on a rapid transit network, it’s important to ensure that whenever two lines intersect, they offer a transfer. This seems like common sense. The point of this post is not to argue for this principle, but to distinguish two different kinds of missed connections: city center misses, and outlying misses. Both are bad; if I had to say which is worse I’d say it’s the city center miss, but city center misses and outlying misses are bad for distinct reasons.
A useful principle is that every pair of rapid transit lines should intersect, unless one is a shuttle, or both are circumferential. If the city is so large that it has multiple circular lines at different radii (Beijing has two, and London vaguely has two as well depending on how one counts the Overground), then they shouldn’t intersect, but rapid transit networks should be radial, and every radial line should connect to every other line, with all radial-radial transfers ideally located within the center. City center misses weaken the network by making some radials not connect, or perhaps connect at an inconvenient spot. Outlying misses often permit more central transfers, and their problem is that they make it harder to transfer to the better or less crowded radial on the way to the center. London supplies a wealth of examples of the latter without the former.
What counts as a missed connection?
Fundamentally, the following picture is a missed subway connection:
The red and blue lines intersect without a transfer. Even if a few stations later there is a transfer, this is a miss. In contrast, the following picture is not a missed connection:
It might be faster for riders to transfer between the southern and western leg if there were a station at the exact physical intersection point, but as long as the next station on the red line has a transfer to the blue line it counts, even if the blue line has one (or more) stations in the middle. Washington supplies an example of this non-miss: it frustrates riders that there’s no connection between Farragut West and Farragut North, but at the next station south from the intersection on the Red Line, Metro Center, there is a transfer to the Blue and Orange Lines. London supplies another pair of examples: the Northern line and the Waterloo and City line appear to intersect the District line without a transfer, but their next station north from the physical intersection point, Bank, has an in-system transfer to Monument on the District.
There are still a few judgment calls in this system. One is what to do at the end of the line. In this case, I rule it a missed connection if the terminal clearly has an intersection without a transfer; if the terminal is roughly between the two stations on the through-line, it doesn’t count. Another is what to do about two lines that intersect twice in close succession, such as the Bakerloo and Hammersmith and City lines in London, and Metro Lines 4 and 10 in Paris. In such cases, I rule that, if there’s just one station on the wrong side (Paddington on Bakerloo, Mabillon on M10) then I rule it a single intersection and allow transfers at the next station over, by which standard London has a missed connection (Edgware Road has no Bakerloo/H&C transfer) and Paris doesn’t (Odeon has an M4/M10 transfer).
How many missed connections are there?
there are three missed connections on the Metro there is one missed connection on the Metro (update: see comments below): M9/M12, M5/M14, M9/M14. As I discuss on City Metric, it’s no coincidence that two of these misses involve this miss involves Line 14, which has wide stop spacing. Narrow stop spacing makes it easier to connect within line-dense city centers, and Paris famously has the densest stop spacing of any major metro system. M9/M12 and M9/M14 morally should connect at Saint-Augustin and Saint-Lazare, but in fact there is no in-system transfer. M5/M14 should connect at Gare de Lyon, but when M5 was built it was not possible to get the line to the station underground and then have it cross the Seine above-ground, so instead it meets M1 at Bastille, while M14 doesn’t serve since it expresses from Gare de Lyon to Chatelet. A fourth missed connection is under construction: the extension of M14 to the north misses M2 at Rome, prioritizing long stop spacing over the connection to the M2/M6 circumferential.
In Tokyo, there are many misses. I am not sure why this is, but judging by line layout, Tokyo Metro and Toei try to stick to major roads whenever possible, to avoid tunneling under private property, and this constrains the ability of newer lines to hit station locations on older lines. If I understand this map correctly, there are 19 missed connections: Ginza/Hibiya (Toranomon and Kasumigaseki should connect), Ginza/Mita, Ginza/Yurakucho, Ginza/Shinjuku, Marunouchi/Mita (Ginza and Hibiya should connect), Marunouchi/Yurakucho, Asakusa/Yurakucho, Asakusa/Hanzomon, Hibiya/Namboku, Hibiya/Yurakucho (Tsukiji and Shintomicho should connect), Hibiya/Hanzomon, Hibiya/Shinjuku, Hibiya/Oedo, Tozai/Oedo, Tozai/Fukutoshin, Mita/Oedo, Chiyoda/Oedo twice, and Oedo/Fukutoshin. Oedo is particularly notable for being a circumferential line that misses a large number of transfers.
In New York, there are even more misses. Here the culprit is clear: the two older layers of the subway, the IRT and BMT, have just two missed connections. One, 3/L at Junius Street and Livonia Avenue, is an outlying miss. The other is central: Bowling Green on the 4-5 and Whitehall on the R-W should connect. But the newer layer, the IND, was built to drive the IRT and BMT into bankruptcy through competition rather than to complement them, and has a brutal number of misses: ABCD/2-3, ACE/1-2-3, AC-F/2-3-4-5, AC-G/2-3-4-5-BQ-DNR, BD/NQRW, BDFM/NQRW, BD/JZ, E/1, E/F, M/NW, R/7, F/BD-NQ, F/NRW, F-Q/4-5-6, F/NW, G/7, G/JMZ. Counting individual track pairs, this is 46 misses, for a total of 48 including the two IRT/BMT misses; I’m excluding local-only transfers, such as Columbus Circle and 53rd/Lex, and counting the 42nd Street Shuttle as an express version of the 7, so it doesn’t miss the BDFM transfer.
Finally, London only has eight misses. In Central London there are three: the Metropolitan or Hammersmith and City line misses the Bakerloo line as discussed above, and also the Victoria line and Charing Cross branch of the Northern line at Euston. The other five are outlying: the Central line misses the Hammersmith and City line at Wood Lane/White City, and its branches miss the Piccadilly line’s Uxbridge branch three times; the fifth miss is Metropolitan/Bakerloo. But one more miss is under construction: the Battersea extension of the Northern line is going to intersect the Victoria line without a transfer.
The difference between the two kinds of miss
Many misses are located just a few stations away from a transfer. In New York, some misses are just a station away from a transfer, including the G/7 miss in Long Island City, the E/1 miss between 50th Street and 59th Street, and several more are a few stations away, such as the various BDFM/NQRW misses. In London, these include two of the three Central London transfers: there is an H&C/Bakerloo transfer at Baker Street and an H&C-Met/Victoria transfer at King’s Cross-St. Pancras. As a result, not counting the Waterloo and City line, only two trunk lines in the system do not have any transfer: the Charing Cross branch of the Northern line and the Metropolitan/H&C line.
On a radial network, if two lines don’t have any transfer, then the network is degraded, since passengers can’t easily connect. In New York, this is a huge problem: some station pairs even within the inner networks require two transfers, or even three counting a cross-platform local/express transfer. My interest in subway networks and how they function came about when I lived in Morningside Heights on the 1 and tried socializing with bloggers in Williamsburg near the JMZ.
In Paris the three misses are also a problem. Line 4 is the only with a transfer to every other main line. Line 9 intersects every other line, and Line 14 will when its northern extension opens, but both miss connections, requiring some passengers to take three-seat rides, in a city infamous for its labyrinthine transfer stations. Fundamentally, the problem is that the Paris Metro is less radial than it should be: some lines are laid out as grid routes, including Lines 3, 5, and 10; moreover, Lines 8, 9, 12, and 13 are radial but oriented toward a different center from Lines 1, 4, 7, and 11.
In London, in contrast, there is almost no pair of stations that require a three-seat ride. The Charing Cross branch of the Northern line doesn’t make any stop that passengers from the H&C or Met line can’t get to from another line with one interchange (Goodge Street is walking distance to Warren Street). A bigger problem is the lack of interchange to the Central line on the west, which makes the connections between the H&C stations on the west and some Central line stations awkward, but it’s still only a small number of stations on each line. So the problem in London is not network robustness.
Rather, the problem in London is severe capacity limitations on some lines. Without good outlying interchanges, passengers who want to get between two lines need to ride all the way to the center. Most likely, passengers between the Piccadilly and Central line branches to the west end up driving, as car ownership in West London is relatively high. Passengers without a car have to instead overload the Central line trunk.
The same problem applies to misses that are strictly speaking not missed connections because the two lines do not actually intersect. In Paris, this occurs on Line 7, which swings by the Opera but doesn’t go far enough west to meet Lines 12 and 13. In London, the best example is Hammersmith station: the H&C and District lines have separate stations without an interchange, but they do not intersect since it’s the terminus of the H&C line and therefore I don’t count it as a miss. But morally it’s an outlying miss, preventing District line riders from changing to the H&C line to reach key destinations like Euston, King’s Cross, and Moorgate without overloading the Victoria or Northern line.
In New York this problem is much less acute. The only outlying misses are the 3/L and the ABCD/2-3; the 3/L connects two very low-ridership tails, so the only serious miss is on the Upper West Side. There, passengers originating in Harlem can walk to either line, since the two trunks are two long blocks apart, and passengers originating in Washington Heights can transfer from the A-C to the 1 at 168th Street; at the other end, passengers bound for Midtown can transfer at Columbus Circle, using the underfull 1 rather than the overcrowded 2 and 3.
The role of circumferential lines
Outlying transfers are useful in distributing passengers better to avoid capacity crunches, but they are incidental. They occur when formerly competing suburban lines get shoehorned into the same subway network, or when two straight roads intersect, as in Queens. But the task of distributing passengers between radial lines remains important and requires good connections between as many pairs of radials as possible.
The usual solution to this is a circumferential line. In Moscow, there are several missed connections in the center (Lines 3/6, 3/7, 6/9) and one more planned (8/9), but the Circle Line helps tie in nearly all the radii together, with just one missed connection (to Line 10 to the north) and one more under construction (to Line 8 to the west). The point of the Circle Line is to allow riders to connect between two outlying legs without congesting the center. This is especially important in the context of Moscow, where there are only a handful of interchange stations in the center, most of which connect more than two lines.
In London, the Overground is supposed to play this role. However, the connections between the Underground and Overground are weak. From Highbury and Islington clockwise, the Overground misses connections to the Central line, the Victoria line, the main line of the District line, the Piccadilly line, the Hammersmith and City line, both branches of the Northern line, and the Piccadilly line (it also misses the Metropolitan line, but that’s on a four-track stretch where it is express and local service is provided by the Jubilee line, with which there is a transfer). Much of this is an unforced error, since the Underground lines are often above-ground this far out, and stations could be moved to be better located for transfers.
In New York, the only circumferential line is the G train, which has uniquely bad transfers, legacy of the IND’s unwillingness to build a system working together with the older subways. Triboro RX (in the original version, not the more recent version) would play this role better: with very little tunneling, it could connect to every subway line going counterclockwise from the R in Bay Ridge to the B-D and 4 at Yankee Stadium. On the way, it would connect to some major intermediate centers, including Brooklyn College and Jackson Heights, but the point is not just to connect to these destinations in the circumferential direction but also to facilitate transfers between different lines.
Going forward, cities with large metro network should aim to construct transfers where feasible. In New York there are perennial proposals to connect the 3 and L trains; these should be implemented. In London, the missed outlying transfers involve above-ground stations, which can be moved. The most important miss, White City/Wood Lane, is already indicated as an interchange on the map, but does not to my understanding have an in-system transfer; this should be fixed.
Moreover, it is especially important to have transfers from the radial lines to the circumferential ones. These improve network connectivity by allowing passengers to change direction (from radial to circumferential, e.g. from east-west to north-south within Queens), but also help passengers avoid congested city centers like outlying radial-radial transfers. Where circumferential lines don’t exist, they should be constructed, including Triboro in New York and Line 15 in Paris; where they do, it’s important to ensure they don’t miss connections the way the Overground does.