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

The MTA Sucks

Public transportation is a good idea, it really is. Maryland just happens to have implemented it in a rather sucky manner. And I get to deal with it.

I was actually up earlier today, so I figured I'd stop at Baltimore Coffee and Tea for chai and a bagel to server as my breakfast/lunch. I missed the bus I was aiming at, which was my fault because I was a little late and it was on time. I caught the next one, which was three minutes late.

Got on the Light Rail in Baltimore and off next to Baltimore Coffee and Tea, ten minutes later than scheduled. Well, I still had ten minutes before the next train, and it was probably going to be late, so I went and got my food. Came back ten minutes later to see the back of the train receeding along the tracks.

Now I made my big mistake. "Oh," says I, "I can just go catch the 8, rather than waiting twenty minutes for the next train." I walked for six minutes to the bus stop, then waited for another twenty-five. In that time, two buses were supposed to have gone by. None did. From past experience, I really should have known better than to trust the 8 when I needed to have anything resembling a schedule.

I ended up walking back to the Light Rail stop and taking the next train, which was only seven minutes later than scheduled.

All told, if I'd left right after missing the first train, I could literally have walked to work and gotten there sooner than I ultimately did.

Bah.

MTA Proposes Route Changes

I recently discovered that the MTA is considering shortening several of its bus routes, including that of the 31, the one I use most often. Unfortunately, I didn't hear about it via the MTA's email announcement system, nor is it listed anywhere on their web site that I can find. I read about it in an article in the Baltimore Sun.

For the 31, they're planning to eliminate the portion of the route that runs between the Inner Harbor and Penn Station. I have an issue with this because I use that portion. I do things at night along Charles Street (which is one of the city's more active regions). Having a single bus to catch only a block away from my location is something I consider a good thing. Without the 31 running through there, I would have to catch a different bus down to the Inner Harbor (and have to worry about inter-bus timing late at night) or walk several blocks (through Baltimore late at night) to the Light Rail (and then worry about train-to-bus timing).

I will admit that, at that time of night, the bus isn't heavily used, but I'm never the only person that gets on in that segment of its route, either. There are also generally a good number of people on the bus in the mornings when it passes the Convention Center and starts heading north. That portion of the route is used, and cutting it out will only cause additional hassle for the many people that use it.

I have sent a message to the MTA regarding this. I'll have to see what sort of response I get.

MTA Needs More Coordination

The Light Rail was fun this morning. Got on at the Convention Center stop as normal, then drowsed until reaching North Avenue. At that stop, we were informed by the driver that we would have to get off and take buses further north. There were two buses waiting and an MTA supervisor directing people onto them. I said I was going to Timonium and he pointed me at the first bus of the pair.

I was a little annoyed at this point because the service update board they'd put up were blank--this was not an announced outage. Upon reading the Light Rail service status page the MTA provides, I learned that this was unplanned. Still, they could have been more prepared, especially since they're planning to do this sort of thing regularly in the future.

It turned out that the bus I was on went directly to the Timonium area, skipping the more southerly Light Rail stops. This makes sense, since buses are slower than the trains. The driver, however, was unfamiliar with the area and had not been given driving directions. I had to direct her from the Lutherville stop to the Timonium Business Park and Timonium Fairgrounds stops. I only realized after going past it that she'd been told to only stop at the Lutherville, Timonium Fairgrounds, and Hunt Valley stops, so the Timonium Business Park one was a waste of time. I then gave her directions from the Timonium Fairgrounds stop to the Hunt Valley stop.

Neither she nor the supervisor communicated adequately to the riders what exactly was going on. It wouldn't have taken too long to say, "This bus is going to the Lutherville, Timonium, and Hunt Valley Light Rail stops," and that would have made things go a little more smoothley, I think. Several people (including me, though I was less affected) were confused by the stops the bus skipped.

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.

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.

Appropriate Error Messages

I spent some quality time with several MTA ticket vending machines today, much to my sorrow. You see, I wanted to buy a $64 monthly ticket. I pushed the appropriate button, fed in each of my four $20 bills, watched the amount remaining as displayed on the machine decrease by 20 for each bill, then, after I fed it the last bill, watched it display "Money Returned" and spit all the bills back out. Useful error message, no? I eventually determined that it didn't want to give me change form $80. Fortunately, a local bar had a bartender who was willing to give me change for a $20. Upon being given exact change, the machine happily supplied me with a ticket.

Then I proceeded to wait an hour for the bus. In that span of time, three different buses from the 19 route were scheduled to go by. Not one did. Thanks again, MTA.


Phil! Gold