Quote:
Originally Posted by TransitZilla
Any examples?
I have some connection to the folks to work on this. The system has improved but certainly there are some known issues that are being worked on.
Are you using Transit app to get the data or another source?
|
OC Transpo's own website.
Constantly getting incorrect information:
- that a bus is about to come (that isn't)
- that a bus is about to come (that is already long gone)
- that there is no bus imminent at all (and then it shows up)
- that the wait time will be N minutes, when it ends up being much earlier than that.
I'm not talking about being a minute or even two off, or about inevitable schedule slippage as a bus encounters delays en route. But the data service fully lies to customers, and causes us to make incorrect decisions about when to head to the stop or which route, or which trip, to take. IT. LIES.
Most of my busing is on downtown routes: 6, 7, 9, 11, 12, 15, 19, 20. (5 and 14, too, but not enough to know whether they are also as bad.)
I used to see these kinds of time-wasting and frustrating problems at least daily. Now I am seeing them on probably 80% of my trips, and more annoyingly, attempted trips. Maybe even higher than that.
I am told that the data feed that apps get is the same as what OC Transpo feeds to itself. I can cut the frustration somewhat by supplementing with Transee, which at least seems to be able to spot a lot of out-of-service-but-about-to-go-into-service vehicles that OC Transpo's website can't spot for some reason.
HOWEVER, in the course of a busy day, with quick choices to make at the bus stop, you don't have time to juggle between sources. (And don't get me started on how OC Transpo's website, and OC Transpo's digital displays, are so often at odds with one another.)
Why does OC Transpo's website just lie? I don't understand it. The paper timetables of the 1990s were more reliable than this steaming sack of incompetent dogshit.
The difference with STO real-time service is also stark.