Call-prep brief · checked 2026-07-09
Massachusetts Bay Transportation Authority (MBTA)
Grade C · 75.4 / 100
Down 0.4 points since 2026-07-08 (C to C).
For this call: lead with the grade and the three fixes below, then confirm the feed is current and the NTD details line up. Each fix is framed as a next step, not a failure.
What changed since the last check
- Correctness no change
- Freshness down 1.6
- Rider experience no change
- Realtime quality no change
Top three things to fix
Review the rule documentation for 'same_name_and_description_for_stop' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.
Same name and description for stop (flagged by the MobilityData validator). See the linked rule for what this affects.
Effort: Varies.
Review the rule documentation for 'route_short_name_too_long' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.
Route short name too long (flagged by the MobilityData validator). See the linked rule for what this affects.
Effort: Varies.
Remove retired stops from the export, or add them back to the trips that should serve them.
Some stops exist in the feed but no trip ever stops at them. Riders may walk to a stop where no bus is scheduled to arrive.
Effort: A review pass in your scheduling software.
Agencies here usually clear this within about 1 week (based on 11 observed fixes).
NTD certification readiness: Ready
Published at a public URL, valid, and current: the three things the NTD GTFS requirement asks of a feed all hold here. Only your own D-10 certification makes that official; this is a heads-up, not a determination.
- Published Ready
- Published at a public URL.
- Valid Ready
- Passes validation with no errors.
- Current Ready
- Service data covers the next 60 days.
agency_id and NTD ID: Not aligned. Your feed's agency_id is 3, 1; your National Transit Database ID is 10003. A feed that serves several agencies (a shared regional feed) can legitimately carry more than one agency_id, so a difference here is a heads-up, not an error. Optionally set the agency_id for your service to 10003 in agency.txt (and the matching agency_id in routes.txt) so the feed lines up with your NTD record. It is a convenience, not a required feed change: FTA also links agency_id to your NTD ID on your P-50 form.
Key facts
- Feed URL
- https://cdn.mbta.com/MBTA_GTFS.zip
- Last checked
- 2026-07-09
- Service window
- 58 days of service data remain. Last service date 2026-09-05.
- Feed version
- Summer 2026, 2026-07-07T21:07:54+00:00, version D
- State
- Massachusetts
Part of the Massachusetts portfolio: see where this agency sits among the state's feeds before the call.
A data-quality and completeness read to support an agency conversation. Not an official compliance determination. Rubric v1.1, validator 8.0.1.