Category: Providence

Little Things That Matter: Railroad Junctions

One underrated difference between countries is how multi-tracked railroad junctions look. In France, double-tracked regional lines have grade-separated junctions that ensure no crossing oncoming traffic. For a plethora of examples, consult the RER track map and look at any bifurcation. Looking at Google Earth, the same is true near Tokyo. This is standard rapid transit practice anywhere I know of, and Paris and Tokyo both treat their regional rail systems like urban rapid transit.

In the US, this is not true. Even important, high-traffic mainline junctions are often flat – see for examples the Main Line-Hempstead Line junction on the LIRR (Queens Interlocking), and the Hudson-Harlem junction on Metro-North (Mo Interlocking). The major junctions involving the Northeast Corridor tend to be better, fortunately. Harold, the LIRR/NEC junction, is already grade-separated from oncoming traffic, and the current grade-separation project is only for same-direction traffic; and the junctions in New Jersey are grade-separated. The Kearny Connection splits the problem in half – it is grade-separated for NEC trains but requires Morris and Essex trains in opposite directions to cross each other at grade. However, even for NEC trains a few major problems remain, most notably Shell Interlocking between the Northeast Corridor and Metro-North in New Rochelle.

I suspect the problem is that double-tracked lines in the US are not consistently thought of as having one line in each direction. The arrival of centralized traffic control (CTC) has made wrong-direction running easy; some railroads ripped their second tracks, and the commuter lines that remained double-tracked freely run trains wrong-way during weekends or (as is the case on the Worcester Line) when there are freight trains on the line. At a few places, four-tracked segments on running track connect to two tracks in nonstandard ways: for example, at Providence Station, three of the four platform tracks merge into the southbound running track. The concept of having one track per direction and no crossing oncoming traffic, which is standard on the subway, doesn’t really apply to commuter rail, leading to scheduling problems.

In New York, there’s no alternative to grade-separating the worst junctions, including Mo, Queens, the Kearny Connection, and the unnamed Far Rockaway/Long Beach and Ronkonkoma/Port Jefferson junctions. Although frequent train service exists with flat junctions, the schedule is irregular and unreliable, and has few reverse-peak trains. Fortunately, this is a problem for commuter trains more than for intercity trains, for which schedule adherence is more important.

In Boston, the NEC itself has flat junctions at all of its branches. Fortunately, there are alternatives to concrete. The Franklin/Providence junction requires Franklin Line trains merging onto the NEC to cross oncoming Providence Line trains at grade, but lets them continue onto the Fairmount Line without conflict. Since the Fairmount Line is getting some investment and more frequency is under discussion, having additional trains serve the line is a net benefit, and all Franklin Line trains should go through Fairmount. The Needham Line branches at-grade, at a more constrained location, but there are plans to connect it to the Orange Line anyway, and much of its geography is suitable for subway service more than for a regional rail branch. This leaves the Stoughton Line, for which there’s no alternative, but fortunately Canton Junction is not a very constrained location and the junction is simple.

What’s the Infrastructure’s Highest Value?

A piece of land and infrastructure may have multiple uses. Land might be needed for urban development or for a highway. A two-track structure might be needed for freight or passenger service. A right-of-way might be needed for multiple kinds of rail, or a road, or a power line easement, or a park. In all cases, the correct policy choice is to allocate the land to the use that has the highest social value, and this use depends on the situation at hand. It should not be allocated to whatever one fancies.

Concretely, let us consider the following cases:

1. The High Line. Occasionally, railfans grumble about the linear park, and say it should’ve had passenger rail service instead; read the comments on Ben Kabak’s post on linear parks, or New York City subway forums. But in reality, the High Line is very useful as a park in a busy neighborhood that doesn’t have other parks. In contrast, it’s nearly worthless as a transit line: it’s parallel to a north-south subway that’s operating well below capacity, it would be nightmarishly difficult to connect to any existing line, and the only east-west service it could possibly be useful for is connecting to 14th Street, not the most important job destination in the city.

2. The Northeast Corridor in Rhode Island, south of Providence. The expansion of MBTA commuter rail southward into sprawling exurbs is a major failure of regional transportation policy. Providence is not all that congested by the standards of the larger Northeastern cities; auto-oriented commuter rail toward it is doomed to fail, and near-downtown parking is cheap and plentiful. (The commute market from Warwick and Wickford Junction to Boston is trivial.) In contrast, the line is perfect for intercity service, since it has relatively gentle curves outside city limits, and is straight south of East Greenwich. The South County project not only costs $200,000 per weekday rider, but also makes poor use of high-speed track. Since the line is more important as high-speed rail than as a commuter line, Amtrak should be more aggressive about demanding that commuter projects create their own capacity.

3. The Northeast Corridor in Maryland, north of Baltimore. For the same reasons as the MBTA extension’s eventual failure, MARC underperforms north of Baltimore. Although the line has extensive three- and four-track segments, the bridges are two-tracked, and high-speed rail should again be given priority, including canceling commuter rail if necessary. Ironically, because of more extensive four-tracking, the need for bypasses around Wilmington and perhaps North East, and the at-grade track layout, Perryville is quite easy to connect to Philadelphia by commuter rail without interfering with intercity rail.

4. Caltrain to San Jose, the MBTA to Providence, MARC to Baltimore. In contrast with the situation in points #2-3, those three lines are all useful commuter lines; they are all similar in that they connect two distinct cities that share suburbs, with a rump extension that exists purely for show (into Gilroy, Perryville, and soon to be Wickford Junction). Any and all high-speed rail use of these corridors should permit a reasonable frequency of commuter trains, with timed overtakes when possible and full four-tracking otherwise. On Caltrain, in particular, interference with commuter rail is one reason why the chosen Pacheco Pass alignment is inferior to the Altamont alignment.

5. The Lower Montauk Line. Despite perennial railfan desires (and an empty Bloomberg campaign promise, since scrubbed from his campaign website) to restore passenger service, there’s not much point in regional rail that stub-ends in Long Island City. To give an idea how much demand there is, the LIRR currently runs 5 trains per day per direction into Long Island City. Thus, the line is more useful for freight trains than for passenger trains. This will change if, and only if, there is a way to connect the line to Manhattan through the existing LIRR tunnels, or perhaps new tunnels, but then the cost is going to be orders of magnitude higher than just restoring service.

6. Urban freeways, e.g. the BQE. American freeways were built at a time when, even more so than today, land was allocated based on political power rather than any sort of social consensus or market pricing concept. While Japanese cities have to make do with 4-lane freeways due to high land costs and strong property rights protections, American cities demolished entire neighborhoods to make room for freeways with wide exclusion zones around them. The land occupied by some would be more useful for additional neighborhood housing growth than it is for a freeway. For example, the BQE hogs prime real estate in Williamsburg, right next to the under-capacity Marcy Avenue subway station, and to a lesser extent in the rest of Brooklyn and Queens, and this land could be used for high-density development instead.

More Track Maps

A kind reader sent me the two maps on Rich E Green’s now-offline website that I did not have, namely maps of all of Connecticut and Rhode Island. These join earlier maps I’d posted of the Northeast Corridor in Maryland, and the commuter railroads in the Mid-Atlantic, separated into Long Island, Metro-North and Empire South, and New Jersey Transit and SEPTA.

Update: based on request by the author, I took down all the maps, and scrubbed the links.

Followup on the Providence Line and Woonsocket Trains

There’s a pretty bad mistake in my post about MBTA-HSR compatibility: the length of the Boston-Providence line is 70 kilometers, not 67 as stated in the post. In my defense, 67 (42 miles) is what the official mileposts say, on Wikipedia and on the catenary poles along the line. In calculating travel times I used a mix of milepost and Google Earth data, leading me to slightly understate the travel time difference between future high-speed trains on the corridor and improved regional rail. The difference is small, but is important for choosing overtake locations.

The correct technical travel times for nonstop 300 km/h HSR and 160 km/h regional trains making all current MBTA stops are 19.25 and 38.75 minutes, respectively. It’s offset by just half a minute from the technical time I originally thought was correct, but more of the difference occurs near Providence than near Boston. The upshot is that the single-overtake option in Sharon is loose in the north, allowing an additional Boston-area stop, and extremely tight in the south, requiring 200 km/h trains and not necessarily allowing regional trains to stop at Pawtucket.

This doesn’t directly affect Woonsocket trains, for which my example schedule is based on Google Earth lines and should be considered accurate given the assumptions. However, in a comment, I’ve been linked to a 2009 Providence Foundation study of the feasibility of a regional train to Woonsocket, under present FRA regulations, achieving similar trip times to those I propose but with fewer stops. The service proposed is very good relative to the regulatory and organizational environment it has to deal with – the projected cost per rider is about $25,000, fairly low by US standards.

The Providence Foundation study also includes a timed transfer at Pawtucket between Woonsocket and Boston, something I did not originally think of. Since the exercise on this blog assumes organizational competence on the MBTA’s behalf, we can choose an overtake option that makes this work optimally with short turnaround and transfer times. We should also include fare integration in the scenario, something that doesn’t currently exist even just between the MBTA and Amtrak. Under some HSR operating scenarios, it could charge the same fare as low-speed rail on the same corridor and have integrated ticketing, making a Pawtucket transfer less useful than an HSR transfer at Providence. Under others – for example, an HSR fare surcharge as currently practiced on the Shinkansen or ICE – it is not possible, and while integrated ticketing is still possible and desirable, cost-conscious commuters would need a solution not involving intercity trains.

It turns out that a single-overtake option does not accommodate Pawtucket transfers well, even if a Pawtucket stop could be squeezed into the schedule. Consider the following 200 km/h schedule north of Providence, with the 7% pad, rounded to a half-minute:

Providence 0:11:30
Pawtucket-Central Falls 0:15
South Attleboro 0:18
Attleboro 0:22:30
Mansfield 0:28
Sharon Arrive 0:33:30, Depart 0:37:30
Canton Junction 0:40
Route 128 0:44
Readville 0:46:30
Hyde Park 0:48:30
Ruggles 0:54
Back Bay 0:56
Boston South 0:58

It’s possible to replace Readville with Forest Hills; the point is that there’s room in the schedule for it. The times above were chosen to make :00 the symmetry axis – i.e. southbound regional trains leave Boston at :02. Moving the symmetry axis is possible but requires giving up through-service to Warwick – the timetable would be too tight. Under this schedule, southbound regional trains would arrive in Pawtucket at :45, and HSR trains would arrive immediately after, at about :48; thus, southbound Woonsocket trains would arrive at the earliest at :50 and :20, timing them to just miss the northbound connection to Boston. Clearly, under such an option, the only way to provide satisfactory Woonsocket-Boston service is to connect to HSR at Providence.

The two-overtake schedule looks much better. It’s a tighter fit for Woonsocket trains between the faster MBTA and HSR trains, but once they fit, the transfer works well. Consider the following 160 km/h two-overtake schedule, with four-tracking between Readville and Route 128:

Providence 0:07
Pawtucket-Central Falls 0:10:30
South Attleboro 0:13:30
Attleboro Arrive 0:18, Depart 0:22
Mansfield 0:27:30
Sharon 0:33:30
Canton Junction 0:36:30
Route 128 Arrive 0:40, Depart 0:41
Readville Arrive 0:43, Depart 0:45
Hyde Park 0:47
Forest Hills 0:51:30
Ruggles 0:54
Back Bay 0:56
Boston South 0:58

Southbound MBTA trains arrive at Pawtucket at :49:30 and southbound HSR trains pass by Pawtucket at :44. Southbound Woonsocket trains have a window of about 1.5 minutes – they can arrive at Pawtucket between :51:30 (after the MBTA) and :53 (before the next HSR) to fit in on the same track pair used by the MBTA and HSR – but within that window they have a convenient transfer: 2.5-4 minutes to the next northbound MBTA train, at :55:30. Note that even in the off-peak, when MBTA trains would come every 30 minutes rather than every 15 minute, this works – we can just shift the slots used by MBTA and Woonsocket trains. Earlier arrival is good for the entire turnaround schedule for Woonsocket trains, which based on trip times would “like” to arrive at Providence at :58 and at Pawtucket at :51, though, if the Mineral Spring stop for Woonsocket trains is dropped, then :52 arrival is very comfortable at all ends.

The inclusion of Woonsocket service also favors ant6n’s proposed no-overtake schedule, in which Boston-Providence trains run at 200 km/h and skip stops near Boston and let Stoughton trains provide local service, and trains run every 20 minutes. It’s tight if MBTA trains stop at Pawtucket, but gives Woonsocket trains ample time for anything. Assuming a Pawtucket stop can be squeezed, for :58 Boston arrival northbound regional trains would depart Pawtucket at :27, i.e. southbound MBTA trains would depart at :33 and HSR would pass by at :35, right on their heels. Woonsocket trains could be slotted anytime between :37 and :47:30, where :41 would be optimal for their own turnaround times and :45-46 would provide the shortest robust connection.

Blackstone River Regional Rail

Following up on my proposal for improving regional and intercity rail service between Providence and Boston, let me propose a line from Providence to Woonsocket, acting as an initial line of a Providence S-Bahn. The basic ideas for how to run a small-scale regional railroad, as usual, come from Hans-Joachim Zierke’s site, but are modified to suit the needs of a line with a larger city at one end. It is fortunate that the road connecting the two cities is not a freeway, and takes 24 minutes, allowing good transit on the same market to be competitive.

RIPTA’s bus route 54 goes from Providence to Woonsocket, generally taking 53 minutes one-way, with a few express runs taking as little as 39; the frequency is about half-hourly both peak and off-peak. A regional line would effectively railstitute it. Lincoln Mall, which is on the bus route but not near the rail line, would be served by a branch bus with timed connections to the train. See map here, together with some proposed intermediate station locations. Depending on the stop pattern, additional buses could be replaced, most readily route 75.

To avoid degrading service, frequency must be at least half-hourly. Of course, complete fare and schedule integration with the buses is non-negotiable: the fare on the train should be the same as on the buses it’s to replace, and transfers should not cost extra money.

As in the case of Zierke’s proposal for regional rail in southern Oregon, this is impossible under FRA regulations. Unlike the case of MBTA-HSR compatibility, getting a waiver here is difficult, since RIPTA is a small agency and can’t afford to conduct the studies required for a waiver request. In addition, north of Pawtucket, the line is an active freight line owned by the Providence and Worcester Railroad, and passenger service with high platforms (low-floor equipment is ruled out by the high platforms at Providence) may well require a new passenger-dedicated single track, raising capital costs by tens of millions of dollars.

Nonetheless, in a regulatory environment more favorable to passenger rail, such a line can succeed. Travel time of about 25 minutes, comparable to driving, is realistic. The length of the line is 25.5 km, and could still support a minimum speed of about 90 km/h even in its curvier northern half. The technical travel time is about 15 minutes plus 1 minute per stop. To ensure one-way travel time remains well under 30 minutes, enabling two trains to provide half-hourly service, there’s a maximum of about 9 stops. The map above includes 7 stops I believe are necessary for the line’s success, and a few optional locations. The explicit assumption for the following schedule is 90 km/h speed north of Lincoln Junction and 120 km/h south of it. Together with 7% padding, we obtain:

Woonsocket 0:00
East Woonsocket 0:02
Manville-Cumberland Hill 0:06
Albion 0:09
Lincoln Junction 0:12
Valley Falls 0:16
Pawtucket-Central Falls 0:19
Mineral Spring 0:21
Providence Place Plaza Shopping Center 0:24
Providence 0:26

Trains meet south of Lincoln Junction, requiring at a minimum two tracks at and south of the station. If trains leave both ends simultaneously, then they stop at Lincoln Junction within 2 minutes of each other, making timing the connecting bus easier.

This meshes with the sped-up trains to Boston well. Travel time from the junction with the NEC in Pawtucket is 7:30 minutes, versus 3 minutes on a 200 km/h intercity trains. Under the one-overtake option, intercity trains arrive in Providence 3 minutes after regional trains from Boston, giving the DMUs an ample window to make local stops (8 minutes with a 2-minute headway and 15-minute Boston service), even with the flat junctions at the split in Pawtucket and at Providence Station. Under the two-overtake option, Boston regional trains arrive about 5 minutes after intercity trains assuming no additional stops in the Providence area; adding the same three stops made by Woonsocket trains to the Boston trains would turn this into 9 minutes, and the DMUs would have a window between the intercity and regional trains, combining to provide intense local frequency between Providence and Pawtucket.

In other words, capacity constraints at Providence do not exist under this service pattern, answering concerns raised in comments on a post Greater City: Providence. The post itself has important ideas for pleasant development near Providence Station, which is currently urban renewal hell. The only drawback of railstitution is that Kennedy Plaza is closer to the jobs of downtown Providence than the train station, and even with the trip time cut from 53 minutes to 26, it’s essential to provide easy pedestrian access from the station to nearby city destinations.

Modern DMUs have fuel consumption similar to that of buses and are maintained in the same shops, so with higher speed RIPTA can expect similar or lower operating costs and higher ridership. If a passenger-dedicated track is not required, then 9 high platforms, a passing siding, and 4 DMUs should suffice; capital costs would be very low, especially relative to ridership, and may well receive federal support. Based on Zierke’s German examples, daily ridership in the low to middle thousands would be good but realistic; 10,000 would be a miracle and 2,000 a bust.

(With thanks to Jef Nickerson for the idea.)

MBTA-HSR Compatibility

There is going to be major investment in the Northeast Corridor, and several possibilities, including Amtrak’s NEC Master Plan, call for running trains at higher frequency and somewhat higher speeds than today on the Providence Line, and assumes electrification of commuter service. Since the line is already being used by the MBTA, which according to Amtrak is limiting the number of intercity train slots for capacity reasons, this calls for a good measure of schedule integration, based on the principle of organization before electronics before concrete.

Amtrak’s Master Plan calls for three-tracking the entire Providence Line south to Attleboro (one viaduct excepted) instead, at a cost of $464 million – $80 million in Phase 1, $384 million in Phase 2 – in addition to money spent on unnecessary expansion at South Station. Such a cost is excessive, suggesting that better MBTA-HSR compatibility is required. Full-fat HSR programs go even further and avoid the Providence Line in favor of a greenfield alignment or an I-90 alignment, instead of making use of the existing high-speed track in Rhode Island and Massachusetts. To reduce costs, a better plan would four-track short segments for passing sidings, and time the overtakes. The principle is similar to that of the blended Peninsula plan in California, in the version proposed by Clem Tillier.

In many ways, for example the metro area populations involved and the current ridership level, the Providence Line is similar to the Caltrain line. The main difference is that the Providence Line has fewer stops and therefore can expect higher average speeds. In addition, the Providence Line is straighter and passes through less developed areas, so that even today Acela trains plow it at 240 km/h, and about 330 km/h is possible with true high-speed trains and higher superelevation.

In Switzerland, trains run as fast as necessary, not as fast as possible. In this context, this means running just fast enough to meet a good clockface schedule. Boston-Providence travel time on the MBTA today is about 1:10; for a good takt, this should be cut to about 55 minutes, allowing hourly service with two trainsets and half-hourly service with four.

For the purposes of schedule symmetry and avoiding switching moves at high speed, passing segments should have four tracks rather than three when possible. Costs should be controlled by making those passing segments much shorter than the three-tracking Amtrak proposes.

Finally, the timetables proposed here are based on the following performance assumptions: regional trains have a top speed of 160 km/h, accelerate like a FLIRT (45 seconds acceleration plus deceleration penalty), have an equivalent cant of 300 mm, and dwell at stations for 30 seconds. Intercity trains accelerate like an idealized N700-I, have an equivalent cant of 375 mm, and dwell for 60 seconds. The equivalent cant is by and large unimportant; the acceleration and dwell times for regional trains are. The approach into and out of South Station has a speed limit of 70 km/h through the 90-degree curve toward Back Bay, and 100 km/h to south of the curve at Back Bay; intercity trains are limited to 200 km/h south to Readville and 250 km/h south to the Canton viaduct, and, at the southern end, 225 km/h west of the curve in Attleboro and, curves permitting, 200 km/h in Rhode Island. Regional trains turn in 5 minutes, or 4 at a minimum, and intercity trains turn in 10 minutes at a minimum. Signaling allows a headway of 2 minutes at a speed of 200 km/h and 3 minutes at higher speed, but if a regional train starts from a siding stop, it can follow a high-speed train more tightly initially, say 1 minute, still far higher than a safe stopping distance, since the spacing rapidly increases over time. Grades are ignored; the Providence Line is flat enough that they’re not an issue. Timetables should be padded 7% from the technical time.

With the above assumptions, the technical time for regional trains is 38 minutes with the present stopping pattern, which yields 41 minutes with padding; this compares with 46 minutes for the fastest Acela. Clearly, if Acela service levels remain similar to what they are today – which includes the Master Plan, which calls for a 10% reduction in Boston-New York travel time (see page 40 on the PDF linked above) – there’s no need for passing segments. To raise travel time to 55 minutes, trains should make more frequent stops, and/or run to T. F. Green Airport always. Although the speed profile of regional and intercity trains would be different, the average speed would be the same, and given that the corridor has a small number of trains per hour of each type, this mismatch is no cause for concern. The $464 million Amtrak is proposing would then be a complete waste, and the federal government should spend any money toward this goal on electrifying more MBTA lines and funding EMUs.

However, in a scenario involving a significantly improved intercity service, the best technical time for nonstop Boston-Providence service with a top speed of 300 km/h decreases to about 19 minutes (20.5 with pad), and this makes overtakes necessary. A slowdown to 250 km/h only adds about one minute of travel time, so the operating pattern is almost identical.

If 15-minute service, both regional and high-speed, is desired, then regional trains can be about 11 minutes slower between successive passing segments, since 11 = 15-3-1 or 15-2-2. A single mid-line overtake is theoretically possible: 41-20.5 = 20.5 < 2*11. However, such an overtake would have to be exactly at the midline, and, in addition, there could be merge conflicts at Providence, whose station tracks include two on the mainline and two on one side of the mainline as opposed to one on each side.

It’s still possible, but tight, to have a single overtake at Sharon. The immediate station vicinity would be four-tracked; this is no trouble, since the area around the station is undeveloped and reasonably flat. In addition, there’s more than enough time in the Providence area, making the merge conflict a lesser problem. However, this is very tight near Boston South, beyond signaling capability unless four-tracking extends a few kilometers further north. One way to counter this problem is to slow high-speed trains by making them all stop at Back Bay and/or Route 128, adding precious minutes to the schedule but reducing the speed difference. Conversely, the current weekday pattern of Providence Line trains skipping Ruggles could be made permanent. There is no room for infill stops; the overtake would only add 4 minutes to regional train travel time, so there’s time to run further to the airport at 160 km/h, and even make an extra stop at Cranston.

Another possibility is to have two overtakes, taking advantage of existing four-tracking around Attleboro. The capital costs are similar; it would require four-tracking around Route 128, possibly extending north to Readville if an on-the-fly overtake is desired. The operating complexity is much higher, since there’s one more opportunity for a late train to mess up the entire schedule. However, there is plenty of slack south of Attleboro and north of Route 128 allowing for additional stops. Under this option, the train loses 4 minutes waiting at Attleboro and about 2.5 at Readville, since the overtake is not completely on-the-fly, raising travel time to 47.5 minutes. There’s no time for airport trains, not on the same takt. However, there’s space in the schedule for 5-6 infill stops in addition to Readville; Forest Hills, Pawtucket, Central Falls, and perhaps one more in each of Boston and Providence closer to city center.

In principle, it’s possible to extend this analysis to 10-minute service, with three overtake segments, at Route 128, Sharon, and Attleboro. In practice, this is operationally cumbersome, and the operating profits coming from filling six full-length high-speed trains from New York to Boston ought to be able to pay for four-tracking the entire line, even the viaduct.

Not included in this analysis are the branches. Those are not a worry since north of Readville there are three tracks, and frequencies on the other lines are low. The Stoughton Line is a bigger problem; however, with the three tracks through Boston, it could still be shoehorned. Electrifying it should not be difficult due to its short length, though the proposed Taunton extension would make it harder.

Providence’s Underused BRT

Providence’s best-kept transit secret is its BRT tunnel. Converted from a trolley tunnel in 1948, when the trolleys were replaced by buses, it’s a bus-only tunnel connecting Thayer Street in College Hill on the east with Main Street on the eastern edge of downtown on the west, smoothing out the steep grades of the neighborhood. On the surface, the slope from Main to Benefit, the next street to the east, is 15%; in the tunnel, it’s only about 5%. It’s decades older than the systems generally considered the primogenitors of BRT, such as Curitiba’s. It functions as normal open BRT, with six bus lines sharing the tunnel and branching out on the surface.

Whereas other cities do everything within their power to emphasize their BRT lines, sometimes even drawing them on maps as if they were rail lines, Providence keeps its BRT tunnel hidden. Instead, it emphasizes two bus lines – one using the tunnel, one not – by painting them to look like streetcars and calling them trolleys. On the Rhode Island bus map the tunnel does not even appear, but instead the two fake trolleys are given their own inset; the downtown Providence map does show the tunnel, but makes it impossible to trace the bus routes and see which corridors they serve outside the tunnel.

This carries over to developer and landlord blurbs, which can be taken as indications for how much development transit induces. When I looked for apartments in Providence, several listings noted the apartment was close to the trolley; none said anything about a bus tunnel.

The bus tunnel is equally hidden on the surface of the city’s streets. On Main Street, signs direct the traveler to the train station; I have not seen any that even tell one a bus tunnel exists. The station entering the tunnel is prominent once one knows where the tunnel is, but it’s at a location that’s easy to miss – too far north to be the best route from College Hill or Fox Point to downtown, and on only one of several reasonable routes to the train station.

At the Thayer Street portal, the situation is reversed – it’s easy enough to find the tunnel, but there’s no indication that there’s a bus stop in front of the tunnel, much less a shelter for said bus stop – see some vague photos on my photostream. I found out about the existence of the bus stop only when I saw a bus actually stop there to discharge and board passengers. There’s a well-hidden bus schedule at the east portal of the tunnel, but it inexplicably only lists the eastbound schedule; the passenger is supposed to guess when the next bus will head into the tunnel.

Unsurprisingly, the buses aren’t very well-patronized. The combined frequency of the six lines is 12 buses per hour at the peak and 8.5 in the midday off-peak – reasonable for a single frequent line in a large city, albeit in this case the buses are not spaced evenly – but the buses do not look very crowded to me.

If Providence forwent the specially branded fake trolleys and instead adopted the emerging practice of a frequent network map, including letting people know that there’s a segment of busway that is grade-separated, it could see ridership on the bus tunnel increase dramatically. Thayer Street is a busy commercial street, with ample foot traffic until 10 or 11; while downtown is urban renewal hell, it still has retail at the mall that isn’t found anywhere else in the city, while making it easier to connect from the rest of the city to College Hill would let people commute uphill more conveniently.

Pedestrian Observations from Providence in Summer

I’d only visited Providence once, for two hours in the dead of winter, and found the downtown/mall area dreary. I just visited twice again to look at apartments, and saw much better. Providence’s downtown is still dominated by single-use office buildings and was dead on Sunday, but the East Side neighborhoods I saw near Brown are walkable.

To see what I’m talking about, look at photos like this, this, this, this, and this. The streets are about the same width you’d expect of suburban side streets: the roadways are 6-7 meters on the narrowest streets, and 9-10 meters on slightly wider residential streets. The buildings are detached and look similar to those in the older postwar suburbs, though in fact many are historic and date back to the 1800s or even the late 1700s.

The difference with the suburbs is that there are no setbacks, which means the buildings provide an adequate street wall. The building to building distance is about 12 meters at the narrowest and 18 at the widest. Many streets are planted, so the trees provide shade and make it pleasant to walk in the summer heat. The streets are reasonably car-friendly and most apartments I’ve seen come with parking, but they don’t let the parking interfere with a pleasant pedestrian experience.

It’s at the periphery of the neighborhood that you can see signs of the general auto-oriented nature of the area. South and west of campus, the two commercial streets are Wickenden and (South) Main. There are a few grocery stores and eating places on other streets, but those two have more commercial activity. Each alone is walkable, with reasonable traffic speeds, and a street wall. However, their intersection, located too close to the freeways that surround and divide the city, is not. Its signal timing is pedestrian-hostile, and instead of more intense corner commercial development, it has a parking lot, a gas station, and open space.

And downtown Providence is a completely different world from the East Side. The streets are in principle walkable, but many buildings are urban renewal projects, and the area is single-use office space apart from some condos right next to the train station. The commercial development has for the most part been collected into the Providence Place Mall or the historic streets close to Brown, such as Main. By the standards of the larger cities of the Northeast, or even New Haven, there’s very little there.