Reasonable Transit Pitches

Providence station to Wareham station via Fall River and New Bedford is 42 miles as the crow files, versus 47 miles by the existing rail alignment via Taunton. The existing alignment has a lot of tangent track; 2 of the 3 worst curves are at stations (Attleboro and Middleborough) anyway. I don't think you can cobble together a new alignment that substantially beats the existing one, nor do I think you'll garner enough FR/NB - Cape Cod ridership to justify the expense.

Here's an article from when the New Haven was considering it in 1910:
Note that a shorter freight route from FR and NB to points west was the primary motivation, with passenger traffic secondary.

I could maybe see Providence-FR-NB light rail or hybrid rail being workable someday, if 195 congestion got to the point that express buses were too slow. But that's much easier engineering, you can have on-street segments, and you don't have to deal with anything east of NB.
Thanks for the historical articles, and I agree with your points. It would be hard to justify building a new crossing of the Acushnet River and a new track from there to Wareham when the Cape Codder’s old alignment still exists and could get people from Providence to the Cape just as well. If you could rustle up the funding and political support to get a track across the Taunton River and through Downtown Fall River, you’re basically just restoring an existing track the rest of the way to New Bedford.

I like the concept of a Providence-Fall River-New Bedford line, but I’m not sure why it would get built. It would probably be a much higher priority for Rhode Island than Massachusetts, yet the vast majority of the line would be in Massachusetts. RI doesn’t have a ton of money to be spending on rail for itself, let alone out-of-state, and MA has bigger in-state priorities for its own money. Hard to see how the stars would align to make this happen in practice. I mainly wanted to say that from an engineering feasibility standpoint, I think it could be a reasonable build.
 
Average Commuter Rail Speeds

I don't know where to stick this, but I think this is maybe interesting for people looking at expanded commuter rail services, or add some around Providence like discussed above. This is just the average speeds of existing commuter rail services. I also Included projected times from all the various TransitMatters reports and their proposed improvements. Those improvements would be pretty aggressive, but in line with international best practices. The biggest speedup would come from electrification (faster acceleration and deceleration), then high level platforms (shorter dwell times). The rest of the speed ups would come from other improvements like increased line speed, double tracking, better switches, and many more minor changes.

For the travel times, routes can take different times through the day, so I was just kind of eyeballing an average. This is meant to be a rough-but-useful estimation. TM didn't make projections for South Coast Rail, and proposed changing the Needham Line to an Orange Line extension, so those aren't included. I added back in Middleborough for comparison. And TM proposes ditching Kingston Station in favor of Plymouth, the distances are about the same, so close enough.

Let me know if any numbers look egregiously wrong.


LineDistance
(miles)
Time
(minutes)
Average Speed
(mph)
TM Projected
(minutes)
TM Projected Average Speed
(mph)
Providence (Wickford Junction)​
62.9​
105​
35.9​
73​
51.7​
New Bedford​
60​
105​
34.3​
Fitchburg (Wachusett)​
54​
96​
33.8​
63​
51.4​
Kingston​
35.1​
63​
33.4​
45​
46.8​
Middleborough​
34.9​
63​
33.2​
42​
49.9​
Fall River​
56.6​
103​
33.0​
Lowell​
25.4​
49​
31.1​
31​
49.2​
Newburyport​
36.2​
70​
31.0​
46​
47.2​
Stoughton​
18.9​
40​
28.4​
26​
43.6​
Worcester​
44.3​
96​
27.7​
43​
61.8​
Greenbush​
27.6​
60​
27.6​
36​
46.0​
Rockport​
35.3​
80​
26.5​
49​
43.2​
Haverhill​
33​
75​
26.4​
40​
49.5​
Franklin (Forge Park/495)​
27.4​
75​
21.9​
44​
37.4​
Needham​
13.7​
43​
19.1​
Fairmount​
9.2​
30​
18.4​
20​
27.6​

I just though this might be useful for anyone thinking about reviving any abandoned rail line, or whatever. 30mph is not a bad estimate for guessing travel times. Lots of curves and stops will be slower. Straight track and wide stops will be faster. And in a world with electrification and other improvements, 45mph average speed is a pretty reasonable minimum for most lines.
 
Average Commuter Rail Speeds

I don't know where to stick this, but I think this is maybe interesting for people looking at expanded commuter rail services, or add some around Providence like discussed above. This is just the average speeds of existing commuter rail services. I also Included projected times from all the various TransitMatters reports and their proposed improvements. Those improvements would be pretty aggressive, but in line with international best practices. The biggest speedup would come from electrification (faster acceleration and deceleration), then high level platforms (shorter dwell times). The rest of the speed ups would come from other improvements like increased line speed, double tracking, better switches, and many more minor changes.

For the travel times, routes can take different times through the day, so I was just kind of eyeballing an average. This is meant to be a rough-but-useful estimation. TM didn't make projections for South Coast Rail, and proposed changing the Needham Line to an Orange Line extension, so those aren't included. I added back in Middleborough for comparison. And TM proposes ditching Kingston Station in favor of Plymouth, the distances are about the same, so close enough.

Let me know if any numbers look egregiously wrong.


LineDistance
(miles)
Time
(minutes)
Average Speed
(mph)
TM Projected
(minutes)
TM Projected Average Speed
(mph)
Providence (Wickford Junction)​
62.9​
105​
35.9​
73​
51.7​
New Bedford​
60​
105​
34.3​
Fitchburg (Wachusett)​
54​
96​
33.8​
63​
51.4​
Kingston​
35.1​
63​
33.4​
45​
46.8​
Middleborough​
34.9​
63​
33.2​
42​
49.9​
Fall River​
56.6​
103​
33.0​
Lowell​
25.4​
49​
31.1​
31​
49.2​
Newburyport​
36.2​
70​
31.0​
46​
47.2​
Stoughton​
18.9​
40​
28.4​
26​
43.6​
Worcester​
44.3​
96​
27.7​
43​
61.8​
Greenbush​
27.6​
60​
27.6​
36​
46.0​
Rockport​
35.3​
80​
26.5​
49​
43.2​
Haverhill​
33​
75​
26.4​
40​
49.5​
Franklin (Forge Park/495)​
27.4​
75​
21.9​
44​
37.4​
Needham​
13.7​
43​
19.1​
Fairmount​
9.2​
30​
18.4​
20​
27.6​

I just though this might be useful for anyone thinking about reviving any abandoned rail line, or whatever. 30mph is not a bad estimate for guessing travel times. Lots of curves and stops will be slower. Straight track and wide stops will be faster. And in a world with electrification and other improvements, 45mph average speed is a pretty reasonable minimum for most lines.
Crazy how Lowell and Franklin are both ~25 miles yet Lowell is 26min faster. Difference being twice as many stops. Hot take but they should ditch Norfolk, Windsor Gardens, Norwood Depot, Islington, and Endicott, I bet you’d get more total ridership focusing on much faster travel times at the bigger stations
 
Average Commuter Rail Speeds

I don't know where to stick this, but I think this is maybe interesting for people looking at expanded commuter rail services, or add some around Providence like discussed above. This is just the average speeds of existing commuter rail services. I also Included projected times from all the various TransitMatters reports and their proposed improvements. Those improvements would be pretty aggressive, but in line with international best practices. The biggest speedup would come from electrification (faster acceleration and deceleration), then high level platforms (shorter dwell times). The rest of the speed ups would come from other improvements like increased line speed, double tracking, better switches, and many more minor changes.

For the travel times, routes can take different times through the day, so I was just kind of eyeballing an average. This is meant to be a rough-but-useful estimation. TM didn't make projections for South Coast Rail, and proposed changing the Needham Line to an Orange Line extension, so those aren't included. I added back in Middleborough for comparison. And TM proposes ditching Kingston Station in favor of Plymouth, the distances are about the same, so close enough.

Let me know if any numbers look egregiously wrong.


LineDistance
(miles)
Time
(minutes)
Average Speed
(mph)
TM Projected
(minutes)
TM Projected Average Speed
(mph)
Providence (Wickford Junction)​
62.9​
105​
35.9​
73​
51.7​
New Bedford​
60​
105​
34.3​
Fitchburg (Wachusett)​
54​
96​
33.8​
63​
51.4​
Kingston​
35.1​
63​
33.4​
45​
46.8​
Middleborough​
34.9​
63​
33.2​
42​
49.9​
Fall River​
56.6​
103​
33.0​
Lowell​
25.4​
49​
31.1​
31​
49.2​
Newburyport​
36.2​
70​
31.0​
46​
47.2​
Stoughton​
18.9​
40​
28.4​
26​
43.6​
Worcester​
44.3​
96​
27.7​
43​
61.8​
Greenbush​
27.6​
60​
27.6​
36​
46.0​
Rockport​
35.3​
80​
26.5​
49​
43.2​
Haverhill​
33​
75​
26.4​
40​
49.5​
Franklin (Forge Park/495)​
27.4​
75​
21.9​
44​
37.4​
Needham​
13.7​
43​
19.1​
Fairmount​
9.2​
30​
18.4​
20​
27.6​

I just though this might be useful for anyone thinking about reviving any abandoned rail line, or whatever. 30mph is not a bad estimate for guessing travel times. Lots of curves and stops will be slower. Straight track and wide stops will be faster. And in a world with electrification and other improvements, 45mph average speed is a pretty reasonable minimum for most lines.
The TM travel times are all complete garbage. They spec Class 6 track on all lines for 100 MPH topline speeds, which you can't do at anywhere close to the price they quote because they severely underestimate the cost in track work and completely ignore the billions in required grade crossing treatments (all existing FRA quiet zone designations get nullified by the sheer size of the speed + track class increase, and a large number of crossings would be unsafe to run at all sans punitive individual speed restrictions unless they got expensively upgraded or eliminated). And they spec buying intercity-class EMU's in commuter service to get the desired hyper-aggressive acceleration and deceleration profiles, which you can't do while having standees onboard (plus other vehicle-side cost issues). The speed modeling was bar none the most suspect methodology used in their reports, and does not line with international best practices because hardly anybody outside of *maybe* Japan runs intercity-class trains on purely commuter routes for purely commuter fares.

The T's and Amtrak's own modeling for Providence Line with standard commuter class EMU's had an 18% schedule reduction on Providence locals and a 16% reduction on Wickford locals. Caltrain got a full-on 25% reduction on its local schedules with a standard commuter-class EMU make, but they have up to 22 stops on their local runs so the savings get amplified by the sheer number of accelerations from a dead stop. So generally speaking you're looking at 15% bare minimum and 25% practical maximum reduction over today's diesel Purple Line schedules, with likely an 18-20% average. I don't know how precisely to factor the lower dwells from level boarding into all of that, but in practice that's mainly going to take a bite out of the schedule padding allotted to each line since the dwells would conform more tightly to the averages with high platforms instead of blowing out the average at particularly busy low-platform stops.
 
Crazy how Lowell and Franklin are both ~25 miles yet Lowell is 26min faster. Difference being twice as many stops. Hot take but they should ditch Norfolk, Windsor Gardens, Norwood Depot, Islington, and Endicott, I bet you’d get more total ridership focusing on much faster travel times at the bigger stations
1760128208037.png


So, eliminating 1/3 of stops with 1/3 of ridership?

If you actually want to optimize the line, besides electrification (which, as F-Line explains, will get you a nice performance benefit but not what TM claims) and the obvious things (high platforms, double tracking, etc):
  • TOD the hell out of parking lots, especially in the town center stops
  • Relocate Walpole so it's served by Foxboro trains
  • New entrances and sidewalks:
    • East entrance to Windsor Gardens
    • Southeast sidewalk at Norwood Central
    • North entrance at Norwood Depot
  • Get rid of the Forest Hills stops now that the Orange Line is functional again
  • Either get rid of Hyde Park with Fairmount nearby, or rebuild it with high platforms and provide full service
  • Equalize fares so that riders don't have an incentive to wait the long 34E rather than the faster train
 
View attachment 67634

So, eliminating 1/3 of stops with 1/3 of ridership?

If you actually want to optimize the line, besides electrification (which, as F-Line explains, will get you a nice performance benefit but not what TM claims) and the obvious things (high platforms, double tracking, etc):
  • TOD the hell out of parking lots, especially in the town center stops
  • Relocate Walpole so it's served by Foxboro trains
  • New entrances and sidewalks:
    • East entrance to Windsor Gardens
    • Southeast sidewalk at Norwood Central
    • North entrance at Norwood Depot
  • Get rid of the Forest Hills stops now that the Orange Line is functional again
  • Either get rid of Hyde Park with Fairmount nearby, or rebuild it with high platforms and provide full service
  • Equalize fares so that riders don't have an incentive to wait the long 34E rather than the faster train
I like the idea of putting Walpole on Foxboro, but I prefer even more to revert Foxboro to event only or give it a shuttle on the Framingham Secondary. Obviously strong agree with the TOD.

i disagree w/ your premise re: lost ridership from those stations. For example 99% of Norwood Depot riders and 90% of WG would just go to Norwood Central. Norfolk needs to build significant housing to justify its stop, but most of those would drive elsewhere anyway. I think HP needs to stay open because Fairmount doesnt go to Ruggles/Back Bay.
 
I like the idea of putting Walpole on Foxboro, but I prefer even more to revert Foxboro to event only or give it a shuttle on the Framingham Secondary. Obviously strong agree with the TOD.

i disagree w/ your premise re: lost ridership from those stations. For example 99% of Norwood Depot riders and 90% of WG would just go to Norwood Central. Norfolk needs to build significant housing to justify its stop, but most of those would drive elsewhere anyway. I think HP needs to stay open because Fairmount doesnt go to Ruggles/Back Bay.
The counts EGE cited disagree with you strongly. Norfolk already outslugs Franklin, which you want to speed up travel times to, in ridership. Norwood Depot does 72% of Norwood Central's ridership; you have a lot of heavy-lifting to do to prove that "99%" of the riders would migrate to Central instead of a significant share of those disappearing altogether with the service cut. And Hyde Park is doing very poor ridership for that supposed ace-in-the-hole of Ruggles/BBY one-seats. It's not featured on many Forge Park runs to begin with, so that cuts against your premise that it's a critical schedule feature.

And finally, the Franklin mainline has PLENTY of capacity for Foxboro runs. Indeed, it doubles up service out to Walpole if Phase III double-tracking is finished and the F'boro schedules get expanded to full-tilt, uncorking a ridership bonanza at the very mainline stops you think are most worthy of ridership. And you want to service-cut it???
 
Crazy how Lowell and Franklin are both ~25 miles yet Lowell is 26min faster. Difference being twice as many stops. Hot take but they should ditch Norfolk, Windsor Gardens, Norwood Depot, Islington, and Endicott, I bet you’d get more total ridership focusing on much faster travel times at the bigger stations
I like the idea of putting Walpole on Foxboro, but I prefer even more to revert Foxboro to event only or give it a shuttle on the Framingham Secondary.
The loss of those stops would cut off transit access for so many Franklin/Foxboro Line riders.

The Franklin Line needs a semi-express service pattern that skips Windsor Gardens, Norwood Depot, Islington, and Endicott to save time. Trains to/from Foxboro would make all stops to retain service at these stations. The implementation of express trains would also enable an extension to Milford, since any extension past Forge Park is unlikely without a reduction in travel time between Franklin and Boston.
 
So I would like to circle back on all the interest in increasing train frequency to Gillette, particularly given World Cup events on the horizon. I think we can stop worrying about the World Cup crowds wanting train service -- not given the seat pricing that is emerging (this is going to be a black car crowd, not a commuter rail crowd).


The much touted $60 affordable seats for the World Cup matches are going to amount to perhaps a few hundred seats per game -- less than 1% of capacity. Given the resale fees, dynamic pricing and crypto ploys being deployed, pricing for upper tier seats is already looking like $2,000 to $4,500 per seat. And these prices are only going up as we approach the games. That is NOT a commuter rail riding crowd.
 
The counts EGE cited disagree with you strongly. Norfolk already outslugs Franklin, which you want to speed up travel times to, in ridership. Norwood Depot does 72% of Norwood Central's ridership; you have a lot of heavy-lifting to do to prove that "99%" of the riders would migrate to Central instead of a significant share of those disappearing altogether with the service cut. And Hyde Park is doing very poor ridership for that supposed ace-in-the-hole of Ruggles/BBY one-seats. It's not featured on many Forge Park runs to begin with, so that cuts against your premise that it's a critical schedule feature.

And finally, the Franklin mainline has PLENTY of capacity for Foxboro runs. Indeed, it doubles up service out to Walpole if Phase III double-tracking is finished and the F'boro schedules get expanded to full-tilt, uncorking a ridership bonanza at the very mainline stops you think are most worthy of ridership. And you want to service-cut it???
You can't just look at the raw numbers without diving into the factors that drive them. Franklin is the most populous municipality on the line (and would be the most populous on the Providence Line north of Attleboro as well). Ridership from Forge Park is severely suppressed by horrendous travel times on the CR. Downtown Franklin station parking lot fills up before 7am on weekdays, and many residents taking public transit drive to other facilities because of it (but I'm definitely not advocating for expanding that downtown parking lot - rather keep increasing walkshed residential population). While some go to Forge Park, many more go to Norfolk (towards Boston, whereas Forge Park is away, and has 630 spaces vs downtown Franklin's 173), and I would bet a plurality of Norfolk Station riders live in Franklin (3X the population). Many others go to Norwood Central (730 spaces and a lot more frequency), or to QA for the red line's frequency.

The point of my take is to align travel times on the Franklin line with the significantly better travel times enjoyed on other lines for the same travel distances. If there were 5+ added neighborhood stops on the Lowell or Providence lines, aligning travel times from Lowell or Mansfield with Franklin, I think ridership would drop precipitously.

You are right I was being hyperbolic with 99% on Norwood Depot but I would be curious to know what % of those Norwood Depot riders would prefer a faster travel time (albeit they wouldn't benefit nearly as much as Franklin from the cut stations) to the possible small edge some riders get from station proximity now.

Re: Hyde Park - the take is not necessarily about the Franklin line itself, but about boosting as opposed to reducing HP Station service. The scheduling is terrible right now and that suppresses ridership. But we have to be planning the right conditions, not reacting to the wrong ones. HP is embarking on a housing explosion. It's already sub 10 minute ride from HP to a major employment area in Ruggles and just over 10 to Back Bay.

Re: Foxboro - there's just not a lot of point to the station for anything other than Patriot Place. Almost nobody lives around the station and the Town does not want any new housing. They even rejected a completely undevelopable MBTAc district at town meeting the first time around. If you live in Foxboro and take the train to Boston, you go to Mansfield and cut your commute time nearly in half. In a regional rail world where travel time from Forge Park is ~50min or less, it makes more sense to send all those trains to Franklin where you have a much bigger population center now, far more housing being permitted, and the added ability to draw many more from the City of Woonsocket if you just get the travel time reasonable. Zone for 2500 housing units in the Gillette Parking lots and I'll change my mind.
 
I would bet a plurality of Norfolk Station riders live in Franklin (3X the population).
Norfolk station has been my main station on the Commuter Rail for the past 21 years, and I don't think it's accurate to say that most riders at Norfolk come from Franklin. Most people who ride from Norfolk are coming from Medway, Millis, parts of Wrentham, and Norfolk itself. Eliminating Norfolk Station would be a significant loss for the Franklin Line.
 
You can't just look at the raw numbers without diving into the factors that drive them. Franklin is the most populous municipality on the line (and would be the most populous on the Providence Line north of Attleboro as well). Ridership from Forge Park is severely suppressed by horrendous travel times on the CR. Downtown Franklin station parking lot fills up before 7am on weekdays, and many residents taking public transit drive to other facilities because of it (but I'm definitely not advocating for expanding that downtown parking lot - rather keep increasing walkshed residential population). While some go to Forge Park, many more go to Norfolk (towards Boston, whereas Forge Park is away, and has 630 spaces vs downtown Franklin's 173), and I would bet a plurality of Norfolk Station riders live in Franklin (3X the population). Many others go to Norwood Central (730 spaces and a lot more frequency), or to QA for the red line's frequency.
Generally speaking, 1 hour to 495 and 30 minutes to 128 is the sweet spot where commuter rail becomes driving-competitive in Greater Boston. Forge Park-South Station takes about 72 minutes right now. If you electrified Forge Park at an 18% average time reduction (as outlined in my previous post) it comes down to 59 minutes...right on the money. So don't cut stops and suppress more ridership than you gain...do your due diligence and implement full Regional Rail on Franklin/Foxboro and you get your idealized transit times with no changes to the stop roster.

You're also going to need to show some evidence that Norfolk is overly cannibalized by Franklin overflow. They are not very close at all, being 4.5 miles apart. The road network is not oriented well between the two, as the MA 115 corridor taps Wrentham and Millis much more than meandering Main and Pleasant Streets tap Franklin.

The point of my take is to align travel times on the Franklin line with the significantly better travel times enjoyed on other lines for the same travel distances. If there were 5+ added neighborhood stops on the Lowell or Providence lines, aligning travel times from Lowell or Mansfield with Franklin, I think ridership would drop precipitously.
Again...idealized travel times net less ridership than having enough well-sited neighborhood stops. This is proven time and again in Regional Rail applications worldwide, and the T's own Regional Rail Rail Vision includes copious infills across the system (though not on Franklin, which already taps pretty much all of the population catchment on its route) to take advantage of that within the slack offered by electrification's time savings. I think you're severely overestimating the topline of improved travel times to relatively medium-small towns vs. the bottom line of reduced ridership from cutting service. Again, I have to note that basic electrification brings Forge Park in under the hour target so there's no need to consider draconian station cuts to "improve" service from the end of the line.
You are right I was being hyperbolic with 99% on Norwood Depot but I would be curious to know what % of those Norwood Depot riders would prefer a faster travel time (albeit they wouldn't benefit nearly as much as Franklin from the cut stations) to the possible small edge some riders get from station proximity now.
Norwood Depot and Central are exactly 2 minutes apart on the schedule. On previous midday schedules when Depot was skipped the time savings were minimal. That's not going to move the needle. No trains skip it today because the ridership tapped at Depot was too beneficial to be outweighted by any savings in travel times by skipping it on the off-peak. Norwood's got a big enough downtown to merit two full-time stops. They already have all the data they need to see that's the case.

Re: Hyde Park - the take is not necessarily about the Franklin line itself, but about boosting as opposed to reducing HP Station service. The scheduling is terrible right now and that suppresses ridership. But we have to be planning the right conditions, not reacting to the wrong ones. HP is embarking on a housing explosion. It's already sub 10 minute ride from HP to a major employment area in Ruggles and just over 10 to Back Bay.
Perfectly valid. They should absolutely think about rebuilding it for high platforms and increasing the service levels. But is that worth more ridership gain that cutting up to 5 stops on the Franklin schedules? Absolutely not. Look...you're single-mindedly focused on better end-to-end travel times damn the torpedoes. If that somehow requires draconian service cuts to intermediate stops contributing 1/3 of the line's total ridership, shouldn't you be prioritizing keeping the ones that bring in the most ridership for their service levels? There is no effing way Hyde Park outslugs Norfolk or Norwood Depot, or that the one-seat to Ruggles and Back Bay matters that much. The math simply isn't there.
Re: Foxboro - there's just not a lot of point to the station for anything other than Patriot Place. Almost nobody lives around the station and the Town does not want any new housing. They even rejected a completely undevelopable MBTAc district at town meeting the first time around. If you live in Foxboro and take the train to Boston, you go to Mansfield and cut your commute time nearly in half. In a regional rail world where travel time from Forge Park is ~50min or less, it makes more sense to send all those trains to Franklin where you have a much bigger population center now, far more housing being permitted, and the added ability to draw many more from the City of Woonsocket if you just get the travel time reasonable. Zone for 2500 housing units in the Gillette Parking lots and I'll change my mind.
Foxboro Station isn't the be-all/end-all of having Foxboro service. You seem to be single-mindedly hyper-focused on the endpoints rather than the intermediates. Having Foxboro service is a service boost to all of the intermediates out to Windsor Gardens (and Walpole if the station is relocated several hundred feet to before the junction), and as said before service increases are a far bigger ridership generator...FAR bigger...than travel time cuts. Overall Franklin ridership is up because of the extra slots, if those Foxboro service levels were increased to the all-day level of the 2010 Feasibility Study they'd be higher still, and if full-on Regional Rail were implemented there'd be :15 service out to Walpole cranking it up to the moon. Gillette Stadium itself doesn't have to contribute more than middling numbers to provide a HUUUGE boost to the line's fortunes because most of the ridership increases get driven on the inner half of the mainline. I can't fathom the logic of wanting to cut all that for...reasons?

Secondly, you need Foxboro all-local service if you ever want to do what @themissinglink suggests about running some skip-stop service to Forge Park to decrease travel times and make Milford or Woonsocket more palatable extensions. Foxboro in a Regional Rail universe would provide :30 service by its lonesome to Walpole, which is probably enough for the Endicotts and Islingtons and Windsor Gardens of the world where :15 service would probably be overkill. So...yes!...Forge Park would get to skip some of those stops and beneficially decrease travel times without unduly hurting ridership on the mainline. Do you not see that it would be insanity to kill off Foxboro service before we move to a Regional Rail model? That directly cuts against what you ultimately want.
 
Norwood: Compared to Franklin, and Depot vs. Central

@dennismulder - With all due respect, it sounds like an underlying philosophy of yours is that Franklin/Foxboro Line riders primarily drive to the stations. I'd like to push back on that assumption, especially in the context of Norwood.

Firstly, Norwood is anomalously dense for the region. My population density map (adjusted below for better readability) suggests that Norwood has the highest density in its downtown regions on the entire Franklin Line; the only possible contender would be if a Milford extension happens, since it's about equally dense as Norwood. In fact, Norwood's density stands out across the entire region south of Route 128, with Brockton being the single exception.

1760194946452.png


This also plays out at a municipal level. You cited that "Franklin is the most populous municipality on the line" -- except that even in total population, Franklin (33,255 pax) has no real difference from Norwood (31,611 pax).

However... Franklin's size is almost 3x that of Norwood's. This gives Norwood much higher density (3,037 pax/mi^2) than Franklin (1,235 pax/mi^2). (Also note Milford on the map.)

1760196314646.png


Another dimension is: Norwood has significantly better transit share today than Franklin does.

10%
of Norwood residents use transit (any mode) to work, on par with Braintree despite very different transit access. Almost 7% of Walpole residents do so. That figure drops to 2.7% for Franklin.

1760196344593.png


But I've found that both Franklin and the two Norwood stations have a high proportion (23-27%) of riders walking or biking to take CR, relative to the rest of the line (see Appendix). So why the huge discrepancy in transit usage overall?

Aside from possible differences in employment patterns, another factor could be the 34E bus, which runs parallel to the commuter rail ROW in Norwood (and also serves Walpole station).

Inbound ridership on a typical weekday in Fall 2024:
CR34ENote on 34E
Forge Park/495485
Franklin403
Norfolk427
[Foxboro]145
Walpole32176.1From terminus to East St @ Eastover Rd
East Walpole64.2From 710 East St to 67 Washington St (city line)
Windsor Gardens226
"South Norwood"114.1From Rockhill St to Heaton Ave
Norwood Central
(and its walkshed)
613107.1From Dean St (15-min walk to Norwood Central);
To Day St (7 min to Central, 10 min to Depot)
Norwood Depot415111.8From Cottage St (10 min to Central, 8 min to Depot);
To Hill St (15 min to Depot)
[Intermediate on Washington St]9.1From Neponset St to 20 Washington St
(Not close to any CR station)
Islington15484.5From Marshall St (15 min to Islington) to Dean Ave
Dedham Corp. Center408
Endicott289
Readville
(Franklin Line trips only)
366
(73 offs)
[The rest of 34E until Dedham Square]236.4105.5 of them are from a single stop at Ariadne Rd, the closest to Dedham Corp Ctr
[The rest of 34E north of Dedham Square]581.5
Total3825
(until Readville)
1384.8
Takeaways:
  • The entire Norwood area -- Depot, Central, and south of Central -- is a notable ridership generator on the 34E bus, with 333 bus riders. This compares to 1,028 total CR riders at the two Norwoods, and even higher than the ~240 CR riders walking or biking to the stations. (The last figure applies the 2015-17 walk/bike % to 2024 ridership.)
  • Walksheds of Norwood Central and Norwood Depot attract essentially equal ridership on the 34E (107.1 vs. 111.8). Of these, 44.7 riders would strongly prefer Norwood Depot: walking to Norwood Central would lengthen their travel time by 13 minutes.
    • The single most heavily used inbound bus stop in the area -- and the 2nd most on the entire 34E -- is Washington St @ Cottage St (Norwood Common), which is slightly closer to Depot than Central. However, they will likely find Central a reasonable substitute.
  • There's also notable bus usage in "South Norwood", beyond Norwood Central's walkshed. Its demand (114.1) is roughly equal to those in each of Central's and Depot's walksheds alone.
In summary, Norwood already has above-average transit share for this region, and car-free riders may even be using the 34E more than commuter rail (despite the former being much slower). Norwood Central and Depot stations are just under 3000 ft apart -- the exact stop spacing on the southside Orange Line.

If we want commuter rail to actually serve as the "de-facto rapid transit" for Norwood and to attract more residents here, especially car-free residents, it seems to me that keeping Norwood Depot for better pedestrian coverage is well worth it.

How are riders accessing the Franklin/Foxboro line?

The most recent MBTA passenger survey (2024) unfortunately only reports this at a line level, not station level. A more outdated 2015-17 passenger survey offered station-level data:

StationsWalk or bikeDrive aloneCarpool & Drop-offBus transferWalk/bike %
(among all riders)
Hyde Park
(and Fairmount)
5123531455548.1%
Readville17414810313
(another 13 from CR transfer)
38.6%
Endicott & IslingtonN/AN/AN/A0N/A
Dedham Corp. Center
(and Route 128 on Providence Line)
25313644170
(25 from CR transfer, somehow)
12.3%
(Heavily influenced by PVD Line)
Norwood, Depot and Central3317762962623.2%
Windsor GardensN/AN/AN/A0N/A
Plimptonville and Walpole106490161014.0%
Norfolk6043029107.7%
Franklin176303168027.2%
Forge Park/4956058417107.4%
Besides the Hyde Park, Readville (and Fairmount) stations that are obviously more urban, Franklin has the highest proportion of walking or biking transfers on "Franklin Line Proper" at 27.2%. But the two Norwood stations are just behind them, at 23.2%. This may not be surprising given the urban landscape at both downtown areas in the two municipalities.

However, in terms of absolute numbers, the Norwoods has more walking and biking riders (331) than Franklin (176), and even Franklin and Forge Park combined (226).
 
A more outdated 2015-17 passenger survey offered station-level data:
The bus transfer ridership data at Norfolk is inaccurate, as it shows 0 bus transfers, even though the GATRA Medway shuttle terminates at Norfolk. There's not too much ridership on the shuttle, but there's at least some ridership that wasn't tallied here. Also, there used to be GATRA shuttles between Bellingham and Forge Park, but I'm not sure if they're still in service (I can't find anything about the Bellingham shuttle on the GATRA website).
 
The bus transfer ridership data at Norfolk is inaccurate, as it shows 0 bus transfers, even though the GATRA Medway shuttle terminates at Norfolk. There's not too much ridership on the shuttle, but there's at least some ridership that wasn't tallied here.
I haven't dug into the exact definition there, but I suspect that the bus transfers column only counts MBTA services. Transfers from non-MBTA buses (even including EZRide and LMA shuttles) may have been reported under "drop-off" instead.

(The source data for 2015-17 surveys had separate columns for "drop-off from personal vehicles" and "drop-off from other vehicles", which I combined in my analysis not knowing this caveat that you mentioned.)
 
This map makes me wonder if there's ever going to be a new station in Foxboro Center. It would also be nice if the Foxboro trains eventually get extended to Mansfield for transfers to Providence Line trains, but there might need to be an additional platform on the Framingham Secondary at Mansfield for that to work out.
 
Last edited:
This map makes me wonder if there's ever going to be a new station in Foxboro Center. It would also be nice if the Fxoboro trains eventually get extended to Mansfield for transfers to Providence Line trains, but there might need to be an additional platform on the Framingham Secondary at Mansfield for that to work out.
Related to this: Would SCR Phase II be easier if it went via Mansfield instead? It's a bit of a detour but it's dead straight which should hopefully help with travel times, and it avoids any big wildlife areas like the Hockomock Swamp.

The big downside is that the ROW is heavily encroached upon within Mansfield. East of Main St it's mostly just parking but west of Main St is Old Colony Rd. The block between Cottage St and Church St in particular has several shops that face onto Old Colony Rd, with no alternate entrance.
 
Related to this: Would SCR Phase II be easier if it went via Mansfield instead? It's a bit of a detour but it's dead straight which should hopefully help with travel times, and it avoids any big wildlife areas like the Hockomock Swamp.
The grade crossing cluster in downtown Taunton would be problematic for Commuter Rail service. Also, Norton was extremely opposed to rail service running through town last time it was considered (the 90s), but I'm not sure how people in Norton would feel about it nowadays (probably still opposed, but who knows).
 
The grade crossing cluster in downtown Taunton would be problematic for Commuter Rail service. Also, Norton was extremely opposed to rail service running through town last time it was considered (the 90s), but I'm not sure how people in Norton would feel about it nowadays (probably still opposed, but who knows).
The Norton NIMBY's were rabid and were very active up until the publication of the 2013 FEIS more or less closed the book on the Attleboro Alternative. If anybody even thinks about reviving one or the other alignments through town for commuter service, they'll reassemble with force. And, yeah, the grade crossings--15 of them--are super problematic. Especially around the would-be Downtown Taunton station where multiple crossings would be blocked by any six-car train. I did an analysis of how bad it would be in this post 5 years ago.
Related to this: Would SCR Phase II be easier if it went via Mansfield instead? It's a bit of a detour but it's dead straight which should hopefully help with travel times, and it avoids any big wildlife areas like the Hockomock Swamp.

The big downside is that the ROW is heavily encroached upon within Mansfield. East of Main St it's mostly just parking but west of Main St is Old Colony Rd. The block between Cottage St and Church St in particular has several shops that face onto Old Colony Rd, with no alternate entrance.
In addition to the encroachment downtown, it's all a non-landbanked rail trail down to the Mansfield Airport and 495. The only way you'd be able to hook in anywhere near Mansfield is to spur off the NEC at MA 140, go along that overbuilt road's side median, then go alongside 495 to the airport and the old ROW and get ready for a massive fight in Norton over ownership of said reverted/non-landbanked ROW. It's functionally identical to the rejected Attleboro Alternative via a well-buffered and single-ownership power line ROW to the Middleboro Secondary, with a *slightly* better Norton station location (though it's still off-center from Downtown in a town that doesn't build a lot of sidewalks) and probably equal travel times but a ton more cost and controversy. It's a nonstarter.
 
Again...idealized travel times net less ridership than having enough well-sited neighborhood stops. This is proven time and again in Regional Rail applications worldwide, and the T's own Regional Rail Rail Vision includes copious infills across the system (though not on Franklin, which already taps pretty much all of the population catchment on its route) to take advantage of that within the slack offered by electrification's time savings. I think you're severely overestimating the topline of improved travel times to relatively medium-small towns vs. the bottom line of reduced ridership from cutting service. Again, I have to note that basic electrification brings Forge Park in under the hour target so there's no need to consider draconian station cuts to "improve" service from the end of the line.
This is of course a fair rebuttal, and I'm admittedly coming from a point of frustration that Franklin riders face by far the longest travel time of all the Zone 6 stations, in some cases nearly double, and they are ALSO likely the ones who will be sacrified with a forced transfer at Readville to take the NEC . In an ideal Regional Rail implementation, do you envision other lines adding enough infill stations to reach a similar point to where the Franklin line is today? I ask because - without that electrification - I think that riders in places like Mansfield, South Acton, Lowell, or Hanson would go nuclear if they were told 5+ infill stations are coming, and the travel time will increase by ~30 minutes to be similar to what Franklin faces now.


Secondly, you need Foxboro all-local service if you ever want to do what @themissinglink suggests about running some skip-stop service to Forge Park to decrease travel times and make Milford or Woonsocket more palatable extensions. Foxboro in a Regional Rail universe would provide :30 service by its lonesome to Walpole, which is probably enough for the Endicotts and Islingtons and Windsor Gardens of the world where :15 service would probably be overkill. So...yes!...Forge Park would get to skip some of those stops and beneficially decrease travel times without unduly hurting ridership on the mainline. Do you not see that it would be insanity to kill off Foxboro service before we move to a Regional Rail model? That directly cuts against what you ultimately want.
I think you're describing a major possible benefit that could exist in the future but does not exist today. Today, every train sent to Foxboro instead of Franklin is a wasted train. Right now, there's a lot more potential ridership in adding that frequency to Franklin - using the frequency to help make the awful travel times more palatable - than there is to sending them to Foxboro, where there's hardly any ridership and it's faster to drive to Mansfield. If in a regional rail world the existence of the Foxboro branch could be used to create express-ish service on both branches, while offering far better frequencies than what we have now, then hey I'm sold.

Norwood: Compared to Franklin, and Depot vs. Central

@dennismulder - With all due respect, it sounds like an underlying philosophy of yours is that Franklin/Foxboro Line riders primarily drive to the stations. I'd like to push back on that assumption, especially in the context of Norwood.

Firstly, Norwood is anomalously dense for the region. My population density map (adjusted below for better readability) suggests that Norwood has the highest density in its downtown regions on the entire Franklin Line; the only possible contender would be if a Milford extension happens, since it's about equally dense as Norwood. In fact, Norwood's density stands out across the entire region south of Route 128, with Brockton being the single exception.



This also plays out at a municipal level. You cited that "Franklin is the most populous municipality on the line" -- except that even in total population, Franklin (33,255 pax) has no real difference from Norwood (31,611 pax).

However... Franklin's size is almost 3x that of Norwood's. This gives Norwood much higher density (3,037 pax/mi^2) than Franklin (1,235 pax/mi^2). (Also note Milford on the map.)



Another dimension is: Norwood has significantly better transit share today than Franklin does.

10%
of Norwood residents use transit (any mode) to work, on par with Braintree despite very different transit access. Almost 7% of Walpole residents do so. That figure drops to 2.7% for Franklin.



But I've found that both Franklin and the two Norwood stations have a high proportion (23-27%) of riders walking or biking to take CR, relative to the rest of the line (see Appendix). So why the huge discrepancy in transit usage overall?

Aside from possible differences in employment patterns, another factor could be the 34E bus, which runs parallel to the commuter rail ROW in Norwood (and also serves Walpole station).

Quite familiar with the population characteristics of the towns on the line. Yes, Norwood has a wonderfully dense downtown comparitively because it developed much earlier. Franklin has built more new housing in recent history, but alas, mostly sprawl (albeit that's starting to change). I think you're partially reversing cause and effect with the transit data though. Obviously Norwood's more robust downtown contributes to more transit share. But if Franklin (which I have around 5% per census data) had the travel time and frequency enjoyed by Norwood, its transit share would be better as well. I also think the presence of the bus would mitigate any potential ridership loss expected from consolidating Norwood's downtown stations.

In any event, I think you F-Line make great points, and perhaps take shouldn't have been so station-specific, but I stand by the need to bring Franklin and Forge Park travel times in line with the other zone 6 statations in the shorter term, especially as those stations continue to lose a bunch of trains to Foxboro, and sometimes face forced transfers at Readville.
 

Back
Top