Open
Description
Originally reported by @devinbraun at OneBusAway/onebusaway-gtfs-realtime-api#6:
When viewing the GTFS-realtime feed alerts output at the link above, the active_period start and end time are incorrect. They are off by a multiple of 1000.
When viewing the alerts in the OBA console, the start and end times are correct. It appears that it might be only an issue in the output of the API endpoint?
I'm assuming this is a time conversion bug in the GTFS-rt output API. GTFS-rt times are seconds past epoch vs. milliseconds past epoch.