Sun, 12 Jun 2005

The Greater Baltimore Bus Initiative

The MTA recently announced a Greater Baltimore Bus Initiative. They are planning to restructure most of the bus routes in the Baltimore system, in what I believe is that first major overhaul the system has ever undergone.

On looking at the proposal for the first time, the initial impression I got was one of reduction. Four lines will be added (the 9, 28, 40, and 41) while 18 will be discontinued (the 2, 7, 10, 27, 31, 36, 61, 65, 86, 91, 98 (Hampden Neighborhood Shuttle), 102, 103, 104, 105, 150, 160, M6, and M12). (In most cases, each of the areas served by the discontinued lines will be served by a different line after the reorganization.) The reduction has both good and bad aspects. On the good side, it will simplify the routes significantly. As I've written before, the current routes are somewhat baroque, with lots of branches and optional sections. The new plan looks like it eliminates most of those, leading to simpler and more understandable routes, at the cost of convenience--many places will be farther from the buses than they are now, though the limit seems to be between four and eight city blocks.

On the other hand, there are several places where the MTA is simply cutting service completely, largely to the north and northeast of the city. The 83 corridor will remain accessible, but that service will stop at Hunt Valley Mall. Along the rest of the north and northeast portion of the current service area, service will stop at or barely outside the Beltway. The 8 will no longer go to Stella Maris; the 15 will stop short of the Beltway, no longer going to Rutherford Business Park, Windsor Hills, Ingleside Avenue, and Forest Park Avenue; the 19 will no longer go to Cub Hill or Joppa Heights; the 23 will not go to Hawthorne and Wilson Point; the M10's entire route north of Smith Road, which currently goes up to Greenspring Station, will be removed; and the M12's service will be dropped completely, eliminating access outside the Beltway along Stevenson Road, Park Heights Avenue, and Greenspring Valley Road, the latter of which renders Villa Julie College inaccessible. I know people who use some of those removed routes, and I have occasionally made use of some of them myself. Losing them makes Baltimore's public transit system much worse.

I'd say that the changes proposed are more bad than good. The "good" parts are mostly that the bus routes have been simplified and bus frequency increased in heavily-used areas. The simplification is not without its downside, though, since it leaves many people walking much farther to get to a bus. The bad part is that large sections of service are simply being removed, causing serious problems for anyone who uses those sections.

The MTA is holding community meetings this week and public hearings next week to solicit feedback on the proposal. (I have no idea what the difference between a "community meeting" and "public hearing" is.) The public hearings all start at 4pm on weekdays, with the exception of the one that starts at noon on a weekday. Needless to say, they're not terribly convenient for people who work. The community meetings, at least, all start at 6pm.

The Baltimore Sun has an article about the proposed changes.

Mon, 07 Mar 2005

Two Days in a Row

Okay, I guess the snow gives them an excuse, but the same two buses failed to show again today. From 9:25 through 10:10, there was nothing. Oh, sorry. There was nothing except for the bus that drove by without stopping at 9:40 with a sign saying "Finished Service".

The fact that the Light Rail was 10 minutes late seems to pale in comparison.

Trainsched Schedules

In order to use trainsched with the MTA's schedules, I had to write my own programs to parse the MTA's HTML schedule pages. The results of that work are now on this website. Share and Enjoy.

Missing, late buses.

The MTA had been behaving itself for a couple of months (inasmuch as it ever behaves--the 8, on the occasions I've had to use it, has been as bad as ever), so I suppose it was due for something.

The 31 scheduled for 6:58 at Liberty and Baltimore never arrived. I waited until roughly 7:20 before a 31 came by. (The next scheduled arrival was 7:24.) The bus then sat at the Arena stop for roughly 15 minutes as the driver waited for a replacement. None was forthcoming, so he eventually drove on, despite the fact that he was supposed to have been relieved. I got home a bit over an hour later than I ought to have.

Zero for Two

Following in Friday's footsteps, the MTA gave me troubles getting to work this morning.

The bus I caught going into the city (bus #8877) was stuck on a hill for some time, because the transmission wouldn't shift into forward. (I'm not sure how long we were there, since I didn't think to check my watch, but I missed two Light Rail trains, so it was at least half an hour.) The driver tried a number of variations on "roll backwards and then gun the engine" but nothing seemed to work. Eventually, something caught and the bus crept up the hill as people held their breath.

The driver said that she had called for a replacement bus several hours previously (apparently, this had happened earlier today, too), but nothing had been forthcoming.

No Buses on Route 31?

It's been a while since a bus failed to show up at all0; the MTA appears to have attempted to balance this by today skipping two buses in a row. Neither the scheduled 9:28 or the scheduled 9:47 bus came through Arbutus today; I had to wait nearly an hour for the 10:11 bus.


0 Showing up late is another story, but they've been showing up eventually, at least.

More messed up MTA with no communication.

I haven't had problems with mass transit in a week or two. So I was about due, right? Right.

Went to catch the Light Rail on my way home from work. Based on the timing, I figured I'd catch the 6:24 scheduled train from Timonium Fairgrounds. From a distance, I watched a train go through at 6:19. Based on the track signals and the fact that trains are almost never that early, I figured it was just really late and that another would be through shortly.

This turned out to be true; another one ran by a 6:34, presumably the 6:24 scheduled one. I was assisting a couple of out-of-town women with directions and they hadn't finished buying their tickets, so I said, "Oh, there should be another one in ten to twenty minutes." (Reasoning that the next scheduled train (6:44) probably wouldn't be more then ten minutes late itself. More the fool I.)

Over the next twenty minutes, three trains went by heading north. At 6:57, another one same by going south. It drove right through the station without stopping while sporting a sign that said "not in service". Another train went by heading north at 7:12. Finally, at 7:18, almost an hour since I'd gotten there and running 45 minutes behind the last train, another train finally came by to pick us up.

At no point was there any use made of the loudspeakers at the stop, nor does there appear to have been any announcement made via the MTA's website or mailing lists. The transit police officer at the station didn't know what was going on. (Though the delays didn't stop her from doing a fare check once the train was underway.)

Phil! Gold