Call-prep brief · checked 2026-07-09
Springfield Mass Transit District (SMTD)
Grade F · 55.7 / 100
Up 0.1 points since 2026-07-08 (F to F).
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 no change
- Rider experience no change
- Realtime quality no change
Top three things to fix
Re-export the feed with a calendar that reaches further out, and set feed_info feed_end_date past your next service change.
Service data ended 33 day(s) ago. When the calendar runs out, trip planners stop showing this agency even though the buses are still running. Riders are told the service does not exist.
Effort: Usually one export setting; export on a schedule so it never lapses again.
Agencies here usually clear this within about 1 week (based on 18 observed fixes).
Set wheelchair_accessible on every trip (most small-agency fleets are 100% accessible, so this is often a single default).
3505 of 3505 trips don't say whether the vehicle is wheelchair accessible. Even with accessible stops, riders need to know the bus itself can take them.
Effort: Often one default setting in your export.
Agencies here usually clear this within about 1 week (based on 5 observed fixes).
Ask your AVL vendor to check vehicle-to-trip assignments for the flagged trips.
51 of 57 sampled vehicle positions were far from their assigned route (worst: 9060 m). A bus shown off its route usually means a wrong trip assignment; riders watch their bus drive the wrong streets.
Effort: A vendor support ticket with the trip ids attached.
Agencies here usually clear this within about 1 week (based on 31 observed fixes).
Ready to send to the agency
Hi Springfield Mass Transit District (SMTD) team, Service data ended 33 day(s) ago. When the calendar runs out, trip planners stop showing this agency even though the buses are still running. Riders are told the service does not exist. The fix is usually one export setting: Re-export the feed with a calendar that reaches further out, and set feed_info feed_end_date past your next service change. This came from your GTFS data quality scorecard, which checks the feed you publish and lists the fixes in plain language: https://gtfsscorecard.org/agency/springfield-mass-transit-district-smtd/
NTD certification readiness: Not ready
Resolve this before you certify on the D-10. Service data expired 32 days ago, so FTA would find the link out of date.
- Published Ready
- Published at a public URL.
- Valid Ready
- Passes validation with no errors.
- Current Not ready
- Service data expired 32 days ago, so FTA would find the link out of date.
agency_id and NTD ID: Not checked yet. Setting your GTFS agency_id to your five-digit NTD ID is an optional way to line a feed up with its National Transit Database record. FTA links the two on your P-50 form, so it is not a required feed change. We don't have your NTD ID on file, so this is not checked yet.
Key facts
- Feed URL
- http://data.smtd.org/gtfs/smtd_gtfs_feed.zip
- Last checked
- 2026-07-09
- Service window
- Feed has expired. Last service date 2026-06-06.
- Feed version
- S1000197
- State
- Illinois
Part of the Illinois 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.