4 ms·
For some reason, Google maps tends to be horrible at getting subway transit right: They frequently list delays when there are none and don't list them when the
by fwilliams 9y ago
For some reason, Google maps tends to be horrible at getting subway transit right:
They frequently list delays when there are none and don't list them when the subway is running very behind. I wonder if it's just hard to get this kind of real-time data from MTA.
- Avery3R 9y agoIt's probably just whatever transit delay system your area is letting Google use. The delays are almost always accurate for me in San Diego
- jdavis703 9y agoThe problem is the subways misuse their delay systems. A few months ago BART was using their delay feed to warn about a shutdown that would occur over a long 3-day weekend. Sure it's a "delay", but it's not an active delay that impacts riders now. Google Maps doesn't seem smart enough to figure that out. But honestly the operators should find better ways to alert riders about upcoming planned delays.
- puzzle 9y agoIt depends on the line. Numbered ones have more accurate data, for example, as they rely on rail sensors to track trains. MTA recently pushed new Bluetooth-based technology to get location estimates on all the other lines. They're just estimates, still. It's really an MTA problem, though. You can tell because they now have screens with arrival times everywhere. Even if the screen says that a E train is coming in 11 minutes, one moment later the same train (another E train?) is just two minutes away, if not approaching the platform. Perhaps they only need to recalibrate the code that comes up with the estimates, since the beacon system is fairly recent.