05-30-2017, 01:42 PM
The realtime GTFS feed is available for consumption here: http://www.regionofwaterloo.ca/en/region...FSdata.asp
You'll need a grounding in protocol buffers and data storage to build up a suitable number of records. From there you can compare the scheduled stop times (present in the static feed zip, also at the above URL) to the ones advertised by the GTFS data.
From there it's a matter of summing seconds of earliness per dimension you want to track (presumably per stop, route, hour... but maybe you're also interested in per-bus timings in case you want to see if there's a driver component?)
Or, you could ask GRT yourself. They undoubtedly track it as a key performance metric.
You'll need a grounding in protocol buffers and data storage to build up a suitable number of records. From there you can compare the scheduled stop times (present in the static feed zip, also at the above URL) to the ones advertised by the GTFS data.
From there it's a matter of summing seconds of earliness per dimension you want to track (presumably per stop, route, hour... but maybe you're also interested in per-bus timings in case you want to see if there's a driver component?)
Or, you could ask GRT yourself. They undoubtedly track it as a key performance metric.