Moderating two definitions of access

This post was written in the winter of 2014, but for some reason I got distracted and never posted it. Now I’m cleaning house, and here it is! In case you were wondering why it’s about winter weather…

————-

About twice a week, I find myself waiting for the #17 at 13th and Main, heading up to UC for the day. The #17 works well for me since the geography department is on the west side of campus anyway, though in the winter more often than not I find myself wishing for a bus, any bus, for the love of god, when is the bus coming? My hands are freezing! I find myself here almost every day, but about twice a week, like I say, I find myself in a particular situation: passed up by a bus that’s going the same place I’m going, its clean, brightly lit, warm interior mocking me through it’s big windows. I don’t care it’s it’s going to the other side of campus. I just want on.

The M+ has just passed by. My inclination is to run for it’s next stop, but my position on 13th street denies me the option.

Too far.

Once I see the M+ coming up Main, it’s too late to run south to the courthouse stop, too far and still too late to run up to it’s next stop at Findlay market. This is why the M+ is marginally faster than the other buses. It doesn’t stop for people like me, people of course, not at it’s limited and clearly signed set of stops.

The 13th Street stop is the one closest to my house and it’s always my starting place when catching transit up to campus. I always look south when I get there, and if I don’t see anything coming, sometimes I’ll sneak toward the courthouse, stop by stop, never getting too far away in case a bus pops out of nowhere. (Sometimes I creep north, constantly looking back…do I have time to grab a baguette?!? I pay for it, already half-way out the door.) The courthouse stop, see, has better frequency toward campus since it works for both the #17 and the M+, two high-frequency lines going where I want to go. Since they don’t usually arrive at exactly the same time, their headways compound and we get some constructive interference.

But it’s more complicated than this. Because the schedules for the #17 and M+ don’t work together, aren’t coordinated, reliably interrelated, I never know which to catch, which will actually get me to Braunstein Hall first. Both are frequent enough that I wouldn’t bother looking at a schedule if I wanted either, and both are so often just a little late or early that it wouldn’t do me much good if I did. In the absence of real-time-location information…you know what? Let’s let this derailment happen. Why not?

Where the h*ll is that real-time data, SORTA? What’s the deal here? This is getting really frustrating, now that the real-time info is posted at half a dozen stops. You’ve missed at least three of your own deadlines for releasing it. Stop making excuses and get your shit together!!!! RAAAGHAHG!!!1

*Phew* OK. Back on track. Without that real-time data, I’m essentially looking to ascertain the quantum state of the buses. Buses here are both a wave and a particle. Clearly working in a regular pattern, they still come in discrete chunks which can be discovered only by measurement and then never exactly predicted.

What’s a boy to do?

Stop fussing and wait an extra minute perhaps. That would be too simple though.

A big part of my problem here is that the schedules aren’t coordinated, meaning that they overlap and interact with each other in unpredictable ways. If they were coordinated, I could decide now which stop is usually the better one and stick to that decision.

In this particular situation, there’s not a good case to be made that these ones should be coordinated since they split off from each other once they get to the hill, but my dilemma illustrates a broader problem with the way SORTA has conceived of BRT: as a fast express line mostly redundant to a slow local service. Schedule coordination is impossible where lines are running at different speeds.

And this same problem becomes more dramatic when I consider other destinations. Lets say I want to get to Norwood, or once there, even further out to Kenwood. In the first case, I would have to take a bigger risk in walking toward the courthouse stop.  The #4 turns east around the corner from the courthouse stop, meaning that I can’t even see it coming.

The best choice would necessarily be based on expected waiting times and expected travel times. A better-than-probabilistic decision can’t realistically be made during higher-frequency hours since the normal(in the non-statistical sense at least) delays, disrupt shorter and more-frequent trips more, relatively speaking. In the later case, I would most likely be presented with the same optimizing tactic that finds me sneaking south on Main Street. That is: walk to the nearest stop on Montgomery Road and once there, inch toward the closest higher-frequency stop, taking in any case whichever bus comes first. Once I know the position of one bus, the one having just arrived, I won’t typically wait around for the next since it’s position is unknown and possibly very distant. Assuming both came at once, and were both stopping, the choice would be easy: the faster one.

The problem here is one of lost potential. It’s not a bad situation by any stretch(I have two reasonably frequent-transit options! Yay!) but it could be better. Rather than having two transit lines in the same corridor running at ten-minute headways, one dramatically faster than other, we could have one line, significantly faster than what we have now, running more consistently, more frequently, and importantly: more simply.

Express lines, as SORTA have conceived them, split the baby.

Show 1 footnote

  1. real-time data DOES exist now!
Comments: Leave one?
Posted in: Access | Analysis | Simplicity
Tags: | | | | | | |

Metro Plush service a hit with riders

KINDA, the Kentucky, Indiana and Norwood-area Dispersal Agency, announced ridership figures today for several new routes that were rolled out recently in a package of service changes. One service in particular, the ‘Metro Plush‘, revealed particularly strong ridership since it’s initiation just weeks ago in mid-August.

Cincinnati Metro Plus

The Metro Plush offers direct, limited stop service between the bureau, lamp and washstand every fifteen minutes Monday through Friday. In the past, many routes required a transfer at the washstand for passengers coming from the bureau and traveling to the lamp, a sore point for many busy commuters. “We’ve heard from many of our customers since the changes took effect,” said KINDA communications director Sally Hiller, “and many of them have been quite pleased to be able to make a faster, more direct trip to and from the bedroom’s most popular light source.”

The basic demographic statistics released in the report reveal that most of the new Metro Plush riders are commuters and Lego people.

transit idership chart

There has also been a significant contingent of the smaller teddy bears from around the bedroom-bathroom area.

“We’re very pleased with the new service” said Mr. Teddy as he headed toward the bureau, “It’s just very convenient.”

Comments: 1
Posted in: Silly Bullshit
Tags: | | | |

SORTA’s new transit plan: The Map

I’ve put together a map of SORTA’s proposed routing changes that beats the pants off any maps I’ve yet seen, at least as far as legibility is concerned. It’s here for your digestion. I’ll have a more detailed play-by-play analysis coming soon, probably tomorrow.

Map of SORTA's proposed changes

PROPOSED changes. Click for full size.

current Cincinnati ransit frequency map for comparison

Transit AS IT IS. Click for full size.

Thoughts? Criticisms? Missed opportunities, or ones well taken? Post them in the comments! I’ll use them as fodder when I write the next post.

Comments: 1
Posted in: Maps | Priorities
Tags: | | | | | |

‘BRT’ – What is it?

I’ve heard a lot of talk about Bus Rapid Transit(BRT) lately, and I’m feeling the need to start unpacking some of it. Just what is BRT? I suspect many people have a fairly vague idea, but fortunately, I found this great slideshow on SORTA’s page about the topic that actually explains everything quite clearly. From the second slide:

“[BRT is] A flexible, high performance rapid transit mode that combines a variety of physical, operating, and system elements into a permanently integrated system with a quality image and unique identity.”

Sounds good so far, no?

On the next slide we learn that “BRT is tailored to each unique corridor” and “can be implemented incrementally“. There are a variety of “alternate BRT packages”. Awesome!

The fourth slide gives us a show of how many cities are supposedly planning BRT.

BRT popularity map

Sweeping the nation like a new boy band!

Then on the next two slides we go back to how flexible BRT is.

The infinite specturm of BRT

BRT will be your everything.

Now this is actually the second time this next slide appears in the document. They really don’t want us to miss the fact that BRT is plug and play.

parts of a so called BRT

Buy the expansion pack!

Let’s pause for a moment to get real: I’m sure Parsons Brinkerhoff does some decent work every once in a while, but this slideshow looks like it was put together by a first year planning student assigned to learn about BRT.

Carrying on again: From here on out, the document spends a few slides at a time highlighting certain features of BRT one at a time. Let’s pick them apart one by one.

“Stylish Vehicles”

BRT is stylish apparently

“Environmentally compatible”: You don’t have to install any proprietary codecs?

Let’s look closer at that one in the top right.

Damn, BRT. You fine.

Damn, BRT. You fine.

That’s pretty awesome. I’m not sure I’ve ever felt as excited about transportation as the emotions this picture conveys, but I have come close.

The big difference, as the next slide explains, between a BRT bus and a “regular”(?) bus is that the BRT is more “rail-like”. They even suggest retrofitting existing buses from the fleet with “front cones” and “wheel covers“.

But then of course if you don’t want any of that, BRT will be anything you want it to be. I mean, look at LA!

BRT will be anything for you

BRT is available in sizes XS -5XL

“Running Ways”

“BRT can operate in a wide variety of physical environments:
-On Street
-Bus Lane
-Bus Way…
-Guided or Non-guided
-Exclusive Lane or Mixed Traffic”

This is pretty neat. You mean to tell me it can go anywhere if we want it to? It could even have it’s own lanes?

buses frolicking in a feild

Buses frolicking in grass. Curiously, there is no sidewalk.

a variety of BRT lane types

 

Well, this is all well and good, but it amounts to little more than saying something like “Nate: with his two feet, he can go anywhere, climb stairs, even run! He’s found in the great outdoors, in bed, in coffee shops and many other physical environments. He could even fit in a hot-tub if you bought him one.” *wink, wink*

It’s simply a list of possibilities rather than requirements or standards. And it’s not unique to things called “BRT”. Trains could operate with essentially the same infrastructure. So could cars or bicycles or people or anything else that moves.

“BRT Stations”

We’re told that BRT “stations” can include such amenities as “artwork”, “customer information”, and “lighting”. That they can be “attractive and safe”, “permanent, substantial, and protected from weather”. It gives us a range of design possibilities, most of which look like nice bus shelters already do.

BRT station design

What’s this bus doing here? I thought this was the train station!

Most importantly, it tells us that a typical spacing between “stations” is 1/4 to 1 mile. This is the real meat of the difference between BRT and “local service”, and it’s taken us 3/4 of the presentation to get to it.

“Branding”

Basically, yes, you can still write all over the stations and vehicles. BRT is not made of Teflon so your logos will stick just like they always have.

branding options

BRT will strut for you.

“BRT Service Plans”

This pretty much lists everything transit can be– from omnipresent frequency to peak-only, stops spaced far apart or close together, local service or express.

things transit can do

You can have BRT where and when you want.

Closing Thoughts

BRT as I understand it in theory has one critical difference from most transit lines we have in Cincinnati. Higher average speed brought about by less frequent stops and a designated transit only right-of-way.

Any other differences are imagined or branded. Indeed, this whole slideshow has amounted to very little more than an enumeration of what is possible with any type of transit. I said earlier in the post it looked like it was put together by a student researching BRT. I take that back. It looks like it was put together by a student researching transit generally and presenting to an audience who hasn’t heard of such a thing before.

If clean, safe stops are a good thing to have, why should BRT lines be the only ones to have them? If level, multi-door boarding and off-board payment are good things to have, why shouldn’t any other line have them too? If running in an exclusive right-of-way can make transit faster, why should we limit such a boon to only certain lines?

And further, if the qualities of BRT that we’ve heard make it special, that differentiate it from other lines are so flexible as to be completely optional, to be implemented one at a time as we can afford them, why can’t similar incremental improvements be made to any line as the funds are available?

It seems then like “BRT” is a brand more than anything. It’s a look to be slapped on a transit service, like the Southbank Shuttle’s  self-conscious ‘trolley’.

southbank shuttle

It’s a forced distinction and ultimately an ambiguous, unnecessary and possibly confusing one. It’s already resulting in maps that, like the streetcar’s, completely ignore the rest of the transit system:

BRT stands in glorious isolation.

BRT stands in glorious isolation.

That sort of cartography is indicative of a line that will itself ignore much of what already exists. Indeed, SORTA has put out some specific suggestions for BRT line routing and they seem to almost completely overlap existing ‘local’ lines:

proposed Cincinnati brt alignments

In this case the #33, #17, #78, #43, #4 & #11 but with a very, very different stop spacing:

SORTA transit proposal

This map is uglier than even yo’ mamma, and just as decontextualized as that joke.

What this means is potentially more of the same sort of confusion I’ve written about regarding TANK’s stop locations in Downtown with the shuttle stop disjunction. Where does one go to wait for the next bus in such a case? It’s not totally clear(without checking multiple schedules) whether you’re better off waiting for the #4 or the faster bus that won’t pick you up if you’re at the wrong stop.

Further muddying the waters is the complete silence on possible frequency for the new services SORTA is proposing. Since these new lines would be almost completely redundant to the main high frequency corridors, they would work best in compliment to them. I’m going to go out on a limb and guess that SORTA doesn’t have the money to operate these new lines at anywhere close to the frequency of the lines they duplicate(if they did have extra, they would already be spending it. It’s annual operatin funds.). That would mean they could either make ‘BRT’ by taking buses from the existing heavily used lines to run them with limited stops, decreasing ‘local’ service, or they could operate a very low-frequency high-speed line over the still-high-frequency lower-speed line. In the former case, we would have very significant service changes ahead, and ones that people who don’t live near proposed BRT stops will not be at all happy with. In the later case, one would have to wait a reasonably long time for the higher speed line, making irrelevant much of it’s speed benefit. It’s been well demonstrated that, all else being equal, people would rather get a slow bus with little time waiting at the stop than wait a long time for a fast bus. I’ll call it the at-least-we’re-moving effect. Psychology is crazy.

But the point is that if the frequency of the ‘BRT’ service isn’t high enough(and it can’t be without sacrificing ‘local’ service somewhere) then the best option people will have in many of these transit corridors will still be to go out there and wait for the next bus. It might be a higher-speed limited-stop bus if they are near a stop, or a line like we have now. Whichever comes first will be the one they catch. I do this between Downtown and Northside. There are a number of lines I can take to get out there but the one I choose is always the one that happens to get to Government Square first.

Beyond the stops though, the other substantive difference with the idea of BRT is the designated, transit-only right-of-way that prevents cars and stop lights and squirrels from getting in the way. It’s not at all clear where if anywhere this would be found along these proposed routes. In fact, the City has been extremely reluctant to yield even an occasional parking lane for bikes. I doubt they would be friendlier to transit. It’s also not clear whether the vehicles would get priority at traffic signals. Without the assurance that they could avoid most car traffic between stops the potential for substantively higher speed is significantly diminished.

My suggestion would be to improve the high frequency lines that we have by eliminating some stops, assigning a designated right-of-way where possible, improving technology on most or all lines such as with the signal prioritization, and investing(as operating money is available) in higher frequencies and longer schedules. This would have the added benefit of keeping the maps and schedules simple. If a different line is added over the #4 for example, and I just want to get from Downtown to Norwood, I might now have to check two schedules rather than one. Or worse, a new rider may well not realize there are two lines and only check the schedule for one of them, leading to unnecessary wait.

In conclusion, I’ll point everyone to the last words in that slideshow:

don't oversell BRT

Don’t do it.

Comments: 1
Posted in: Definitions | Maps | modes | Technology Choices
Tags: | | | | |