SORTA recently wrapped up planning for service changes that will take effect in August and December this year. The changes they’ve proposed represent a fairly substantial(though certainly not huge) change to the shape of the network. As they work to finalize their plans, they’ve asked for feedback from the public; as a member of that group I intend to give them some, even though it’s now a little later than I might have liked.
I’ll write first about the changes themselves before going on to comment on the planning process more generally.
Basically there are a four major things changing.
There are also a number of smaller changes, but their effect is more local so I won’t go into it. You can see the complete list here.
The thing SORTA has been touting the most is the the thing I was most wary about before I attended the public meeting on the plan last week: The ‘Metro Plus‘ service, or as I’ll call it, the m+1, is to be their tentative step toward what might be called ‘bus rapid transit‘.
For months it was unclear what kind of service this might provide or how fast it could be expected to go, but the rough details are now out in the open and almost all of my initial hesitation about the service has been wiped away. It will2 run from 6am to 10pm on weekdays with no weekend service, and have the surprisingly high frequency of every 15 minutes between 6am and 6pm before dropping to every half-hour for the rest of the day. That’s roughly the same level of service as the #4, #17, or #33 but for the lack of weekend and late night service.
As I understand it, it will be pretty much like every other local-running line in the system except with fewer and better-marked stops. I assume fares will be the same and will depend on the zone you’re travelling to or from.
The line will not, at least for now, have any designated rights-of-way or signal prioritization(though that one may be coming a bit later) and relies on the simple fact that it will be stopping less for any speed improvements. At the first public meeting in November, SORTA said the m+ would be about 15% faster than a comparable route with many more stops.
One thing about this service is still little unclear to me, though there may be a good justification for it: Why, if we recognize that lines in our most important transit corridors(like Mongomery Road, also served by the #4, or the others where ‘pre-BRT’ is proposed) are slowed down by too many stops, don’t we just strategically remove some of the stops thereby speeding up all service on that road? It seems like we’ve recognized a problem(too many stops in places) and rather than trying to fix it for the #4, or #17 or wherever else ‘BRT’ is planned, SORTA is overlaying those corridors with a substantially different kind of service that avoids the problem altogether. As such, we’ll eventually be getting two very distinct services on our most important corridors rather than one service that could be some sort of a mean between lots of stops and slow speed and what’s being proposed for limited-stop, faster BRT. One main line per corridor would be much easier for customers to understand. Two lines isn’t necessarily a bad strategy, but it’s not one that leaps out to me as obvious either and I’d like to hear SORTA’s reasons for it. TANK is working on strategically eliminating stops on many of their lines right now. Why isn’t SORTA doing the same even though they seem to acknowledge the same problem? What accounts for the difference in approach?
On to the next item, there’s effectively a shift in uptown service toward Vine St. This is a little hard to picture right now without a new frequency map(which will eventually be made), so I’ll do my best to explain it. In a nutshell, there are three main ways transit gets up the northern hill of the basin to the dense neighborhoods around UC: West Clifton Avenue, Vine Street, and Liberty Hill/Highland/Auburn.
The proposal is for the #19 to depart from West Clifton and replace the route of what’s now the #24(brick-red line above) up Liberty/Highland/Auburn before rejoining the #17 at Ludlow. The #24 and #39(brown line) would no longer go to Downtown at all, so the #19 effectively takes over for both in that neighborhood. The #51 also won’t come as far down as the Clifton Heights business district leaving Clifton Heights with just the #17 and #31. Meanwhile the m+ will be added to Vine Street with stops at the top, middle and bottom of the hill. When the m+ is combined with the #78 and #46 already going up Vine street, there will effectively be a very very high frequency of service between Corryville(East side of campus) and Downtown. Whereas now service to either side of campus is pretty evenly split, it looks like in the future it will be pretty heavily weighted to the Corryville side. This is a little inexplicable because the Clifton Heights business district at the corner of West Clifton and McMillan is currently the busiest cluster of transit stops outside of Downtown. Corryville is also a major hub for transit(fourth largest after Walnut Hills and Northside), but the cluster of activity around their business district is only about 65% of the size of Clifton Heights.
Corryville is also less densely populated than CUF which can probably explain most of the difference in ridership, but it’s also less well connected to places that are themselves popular transit destinations like Clifton and Northside. That factor at least will change somewhat with the changes to the #19 and certainly the addition of the m+.
I think as a result we’ll see a decline in transit use in Clifton Heights that will be nearly but not quite matched by a rise in transit use in Corryville. That in and of itself might be fine, but because of the difference in population density between the neighborhoods I suspect the distribution of service after the changes will be slightly less ‘fair’ with fewer people receiving higher-frequency service.
One of the planners at the meeting suggested the 17 could see slight frequency improvements in the future(not officially part of the plan), but I worry about the effective service cut to Clifton Heights because the #17/#19 (which I ride frequently) is already often standing-room-only.
The next big change is the merging of and additions to a few east-west running lines that do not/will not stop in Downtown. We’ll take these one at a time since there are only a few:
Th first two generally seem like a pretty good idea. If people can rely on transfers to high-frequency lines running between the ends of these lines and Downtown, then there’s no need for the lines themselves to make their own foray into Downtown. That cut service will be applied to other parts of the system where it can be more useful.
Next on the list is the simplification of the routes of quite a few lines. This sort of falls into two categories. First is the elimination of what I call ‘only-sometimes’ route segments. These are portions of a route that are only used for a small minority of trips. For example the #31 currently makes 104 trips each weekday. Most of those trips are along the dark portion of the route shown in the map below,
but 25 of them, scattered pretty randomly(though I’m sure with intention) throughout the day, are one of four variations on that route. Effectively, this means that even if you know the basic route of the #31, you still probably can’t know exactly where you’re going unless you have a schedule on you or the ability to view the online PDF map. Such deviations are usually done for some purpose such as to serve a factory that only needs service at the end of the day, but it does make things more difficult for the general public. I’ve always found this sort of route-capriciousness extremely frustrating both as a cartographer and as a transit user. It’s exactly this sort of thing that makes people so crazy for the perception of permanence that things like streetcar tracks are supposed to provide.
But anyway, the fantastic news is that most of the only-sometimes segments are getting cut from lines for one reason or another, to be either eliminated completely or replaced by another and more consistently running line. This will of course upset some people’s daily routines but it will also make the system as a whole much easier to comprehend. Losing their only-sometimes segments are the #33, #19 and #31.
Subject to more basic simplifications are the #1, #24, #46 and #38X. Most exciting are the changes to the #1 which is now so convoluted and hard to follow that I very nearly printed t-shirts implying that the line was drunk. It will still be a little tipsy perhaps, though most certainly rideable.
These changes are great. Let’s never go back to complex routing if a simpler route can do the same job. It’s much easier to walk an extra block than to understand where the #1 goes right now.
On to the more general comments!
There are a few things left out of these proposals that I think might well have been considered during a comprehensive review of the system.
I’d like to end by commenting on the method of feedback and community engagement itself. While I’m glad that SORTA is making a point of reaching out for feedback through public meetings, online surveys and by email and I know that they’re doing it in good faith, the information they’re providing and particularly the questions they’re asking (online at least) seem significantly less useful and informative than they might have been, both for interested citizens and transit users and for SORTA’s planners.
Similar to the way SORTA seems to think about their system generally, so in presenting route and schedule changes we’re not given a coherent picture of how these changes fit together as a network but rather a list of separate individual routes and the mostly unexplained changes each will have. I’m an urban planner and a huge transit nerd, and it’s taken even me hours of scrutiny and re-mapping work to really understand the effect of the proposed service changes. Without providing people with a bigger picture to make sense of the changes, I’m not sure how they could be expected to understand what’s going on here or to provide comments that would actually be valuable to SORTA’s planners.
The questions they’re asking feel to me kind of like a vote for your favourite route:
“Does this route meet your needs?” is totally the wrong question to ask, unless you can ask it of the entire population or a representative sample. Online surveys like this have an obvious self-selection bias; you can easily imagine one person asking everyone on their block to use this form to “vote against” any particular change that they don’t like. The people reviewing the feedback, if they’re smart, will recognize that type of comment for what it is and throw most of them out so they don’t skew the results. Even if someone does manage to weed through the details available and form some valuable opinion on the changes generally, the form isn’t really set up for that kind of comment. That’s why I haven’t filled out the feedback form at all, in favour of talking with people one-on-one and writing here.
I think a great opportunity for public education about how the transit system works was really missed here with both the feedback methods and the way the changes were presented individually. The Hamilton County Budget Office for example does a great job of this. Every year they put out a public survey on budget priorities, but it’s so thick with completely necessary details that you can’t read it without coming away knowing the difference between capital and operating funds. The way that survey is set up, there’s literally no way to respond with something inane like “Don’t raise my taxes!” and “No service cuts anywhere!” just as that’s no way to balance a budget.
After a lot of research and conversation with the planners, these changes make good sense for the most part. Indeed, I’m quite happy with them and think they represent a sensible and reasonable improvement to the way the transit system will work. But I think it would have been much more valuable for everyone if the reasons behind the changes had been made clear from the beginning and this process had been a bit more open to the public. Not only would that have put these changes in context but it would have started to establish some basic standards that people would be likely to follow when talking about more publicly contentious projects or changes.
Do these changes meet your needs? By and large they should, but again that’s not quite the right question to ask.