3 ms·
I really want to agree with you, but I don't think that's the case. Most of the US isn't dense enough to avoid the same DC metro area problem. In most places,
by kelnos 7y ago
I really want to agree with you, but I don't think that's the case.
Most of the US isn't dense enough to avoid the same DC metro area problem. In most places, you're transporting people between suburban areas, not between the suburbs and the city, and not between different places in the city. If you have hundreds of suburban areas that are spread out over thousands of square miles, the amount of rail necessary to adequately service that area without stranding people at one end or the other is just massively infeasible.
Even look at the Bay Area. Say you live in SF and work somewhere in the peninsula or south bay. If you don't live near one of the Caltrain stations in SF, you're probably going to spend 30-60 minutes just getting there on Muni. Then you ride for 45-90 minutes on Caltrain. But what if your job isn't along the Caltrain corridor, which is most of the area? Ironically, some of the companies which are within a reasonable distance from Caltrain (walkable, or the company could provide a frequent shuttle bus) provide their own buses to and from SF. Clearly, the preference is just not to have to deal with the mess of Caltrain. And people who don't have shuttle buses still find driving a better use of their time.
Given that the Bay Area is (on either side of the bay, anyway) relatively long and narrow, another one or two parallel trains might solve the problem, though it'd be prohibitively expensive and I doubt the NIMBYs would yield right of way. I think this is an example of the opposite problem: cherry-picking examples that just happen to work out due to favorable land shape and suburb clustering.