Live data from Hacker News

Show HN: San Francisco MUNI Transit Delays, Visualized

bdon.org

31–33 of 33 posts

Re: Show HN: San Francisco MUNI Transit Delays, Visualized

#31
post #14

Earlier quoted context omitted.

It's pretty remarkable how buses in other cities manage to adhere to the published schedule, but MUNI can't seem to manage. I've ridden buses all over the world, and MUNI is absolutely the worst at scheduling or latency. It's almost like they aren't even trying. And even if you drop the requirement of "stick to the schedule", they still suck: you can have two lines running the same route up a major thoroughfare (e.g.…

I noticed that certain lines on AC Transit in Berkeley would routinely have the three back-to-back buses problem and wrote a post on it a while ago: http://andrewfong.com/blog/2009/11/12/bus-scheduling/ Long story short, having a slew of people trying to board and disembark at the same time creates a lot of delay. It seems like the sort of thing you could address by having trailing bus(es) during peak hours. But if y…

Definitely. Of course, MUNI compounds the problem by running absurdly small buses on popular routes (infrequently!) and stopping them nearly every block.

I don't know what ridiculous decision making resulted in this system, but it's not as if the problems are difficult to diagnose.

Re: Show HN: San Francisco MUNI Transit Delays, Visualized

#33
post #32

Could you swap the vertical axis for N Judah? It's a bit confusing to have King & 4th at the top and Judah at the bottom.

This bothers me as well- I'm trying to figure out a consistent way to determine which direction is "Inbound" and which is Outbound - turns out this is quite difficult!

In the case of the N, the 4th and King terminus is closer to some abstract "downtown" point than the other end at Ocean Beach, however this heuristic doesn't generalize to genuinely "crosstown" routes like the 22.

So this depends on when/if I find a method I'm satisfied with.

Post reply on HN