Taco909 wrote:bgodette wrote:This is something that may be possible in the near future. There's supposedly in testing a (national?) system for querying gate status for rail crossings. If that system has a public query api or private access can by negotiated by Google/Waze, it's certainly feasible to implement.
That would be great, but what kind of time buffer would we be looking at? With Waze client alert update times taking up to 5 minutes to distribute, and in my city, a typical commuter train gate activation only lasts 45-90 seconds, it seems that it would only be helpful when a crossing is closed for an unusually extended time period such as for switching operations.
I think this would be more useful for freight train crossings. I commute across this ungated CSX crossing every day. It's not common, but about once or twice a month I get stopped for 10-15 minutes near here as a freight train crosses. "We're detecting a slowdown. Are you in traffic?" "No." The problem with taking an alternate route in this case is that pretty much all of them cross the same CSX track, so you'd likely be delayed the same amount of time at another crossing.
I've also lived in more populated areas with commuter trains that put the gates down and take no more than your average wait at a red light to pass through the railroad crossing. A reroute would be of limited utility in this case. It is more for freight train crossings, I think.