Hi Marco,
Thanks for reaching out. Unfortunately, it is not always possible to directly match Subway and SIR trips between static and realtime data. We do provide a TripReplacementPeriod entity which defines the time range currently covered by the realtime feed.
Generally, GTFS-RT consumers can attempt to match realtime and static trips on a best-effort basis, but should be prepared for the possibility of unmatched realtime trips. This occurs due to the nature of our transit operations and the software we use
to operate the subway. On any given day, the schedule may be modified—to support planned work or other operational needs, or to respond to incidents and other realtime conditions—and these will all result in trips appearing in realtime data which cannot be
matched to the static schedule.
Thanks,
Dillon
Dillon Shen-Cruz (he/him)
Metropolitan Transportation Authority
Product Manager, Data and APIs
Hi,
This is Marco from Transit's realtime data team.
However, at the moment we aren't getting any matches. For example, the tripUpdates entity below (tripId 099300_SI.S03R) doesn't have any matching counterpart in the static data:
{
"id": "000005SI",
"tripUpdate": {
"trip": {
"tripId": "099300_SI.S03R",
"routeId": "SI",
"startTime": "16:36:00",
"startDate": "20250724"
},
Would it be possible to have someone have a look at this issue?
Thank you for your help!
--
You received this message because you are subscribed to the Google Groups "mtadeveloperresources" group.
To unsubscribe from this group and stop receiving emails from it, send an email to
mtadeveloperreso...@googlegroups.com.
To view this discussion visit
https://groups.google.com/d/msgid/mtadeveloperresources/b685d196-e0a0-4792-9cc5-f84f4614e551n%40googlegroups.com.
Confidentiality Note: This e-mail, and any attachment to it, may contain privileged and confidential information and is intended for the use of the individual(s) or entity named on the e-mail. Unauthorized disclosure of this message is prohibited. If you have
received this message in error, please notify the sender immediately by return e-mail and destroy this message and all copies thereof, including all attachments.