All,
Earlier this year we changed commuter rail predictions from arrival-time to departure-time, then rolled that change back and promised a variation of it in the future with separate arrival and departure times. That variation is now ready; you can access a test feed that includes it now and we will deploy it to production next week.
This change does not affect the v2 API (it will be in future API updates), only GTFS-realtime TripUpdates, and within that, only commuter rail StopTimeUpdates. Commuter rail StopTimeUpdates will no longer necessarily have identical "arrival" and "departure" StopTimeEvents. Sometimes the arrival time will be earlier than the departure time. This reflects cases when the train is predicted to arrive early at the station, but the train is scheduled to hold once it gets there rather than leave early. This is the normal commuter rail procedure, so this applies to all commuter rail stops except those for which GTFS "timepoint" is false (those noted with an "L-note" on the schedule, or the last stop of the trip.)
You can preview the change here:
http://23.21.118.89/Portal/Content/GTFS-realtime/TripUpdates.pbPlease disregard any differences you notice in the data for other modes.
Please provide any feedback you have, and we'll update this thread with the scheduled launch time. Thanks!
Sincerely,
developer@mbta