Mismatch between Service Alert Feed and Static Feeds

52 views
Skip to first unread message

Meira Zimble

unread,
Jul 9, 2025, 9:20:56 AMJul 9
to mtadeveloperresources
Hi, 
We are seeing a mismatch in agency_key between static feeds and Service alert feeds for MTA services. For example for MTA subway, in the Static feed the agency_key is MTA NYCT but in the service alert feed the alerts for MTA subway are published under the agency_key MTASBWY. 
What is the reason for formatting this way and what are the best practices for consuming your data with this formatting?
Please note -  We are pulling the combined service alerts feed. 
Thank you!

Shen-Cruz, Dillon

unread,
Jul 9, 2025, 4:39:27 PMJul 9
to mtadevelop...@googlegroups.com
Hi Meira,

Thanks for flagging this! You're correct that there is a mismatch. I believe this mismatch should only affect NYCT subways and buses, who have different GTFS-RT service alert agency_ids ("MTASBWY" and "MTA NYCT", respectively) but the same static GTFS agency_id ("MTA NYCT"). Other agency_ids ("MTABC", "LI", and "MNR") should not be affected.

Unfortunately, this is a legacy issue we cannot solve quickly. If you are running into specific issues with consuming these feeds, please feel free to follow-up in this thread.

Thanks,
Dillon

Dillon Shen-Cruz (he/him
Metropolitan Transportation Authority 
Product Manager, Data and APIs

From: 'Meira Zimble' via mtadeveloperresources <mtadevelop...@googlegroups.com>
Sent: Wednesday, July 9, 2025 09:20
To: mtadeveloperresources <mtadevelop...@googlegroups.com>
Subject: [MTAdev] Mismatch between Service Alert Feed and Static Feeds
 
--
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/4b3f2360-0465-4d60-9d45-f79e47903ed8n%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.

Meira Zimble

unread,
Jul 10, 2025, 7:33:06 AMJul 10
to mtadeveloperresources

Thanks Dillon! 

If the mismatch is stable and won't be changed in the near future - we will map on our end. 

Thank you!
Reply all
Reply to author
Forward
0 new messages