Middletown Area Transit (MAT)

What changed since the last check

• Correctness no change
• Freshness no change
• Rider experience no change

Top three things to fix

1. Correct feed_end_date in feed_info.txt. Set it to 2027-05-27, the last day in your calendar, or to the last day your schedule is reliable.

   feed_info.txt says this feed ends on 2026-10-01. Your service calendar runs to 2027-05-27. The GTFS standard tells apps to trust a feed only up to its end date. So apps may stop showing your service on the earlier date, even though the calendar goes on.

   This one is about the feed as a whole, so there is no share of it to count.

   Effort: One field in feed_info.txt, often an export setting.

2. Set wheelchair_boarding to 1 (accessible) or 2 (not accessible) for every stop. A field survey can start with the busiest stops.

   777 of 795 stops don't say whether a wheelchair user can board there. Riders who use wheelchairs can't plan a trip when accessibility is marked 'unknown'; apps show no information at all.

   Fixing this covers 777 of 795 stops, about 98% of them.

   Effort: A column in stops.txt; your scheduling software likely has it.

3. Set wheelchair_accessible on every trip. If every vehicle is accessible, this may be one default; otherwise use the value for each trip.

   514 of 514 trips don't say whether the vehicle is wheelchair accessible. Even with accessible stops, riders need to know the bus itself can take them.

   Fixing this covers all 514 trips in the feed.

   Effort: A default or per-trip field in your export.

Ready to send to the agency

Hi Middletown Area Transit (MAT) team, feed_info.txt says this feed ends on 2026-10-01. Your service calendar runs to 2027-05-27. The GTFS standard tells apps to trust a feed only up to its end date. So apps may stop showing your service on the earlier date, even though the calendar goes on. The fix is usually one export setting: Correct feed_end_date in feed_info.txt. Set it to 2027-05-27, the last day in your calendar, or to the last day your schedule is reliable. Your feed is produced by Trillium, so the quickest path is usually forwarding this to your Trillium contact. 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/middletown-area-transit-mat/

Copy this note from the full scorecard.

NTD GTFS readiness: Not ready

Resolve this before you certify on the D-10. Service data expired 6 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 6 days ago, so FTA would find the link out of date.

agency_id provided Ready

agency.txt provides agency_id. For RY2026, keep one stable value for each NTD reporter represented in the feed and crosswalk each value on the P-50 form.

agency_id equals NTD ID (optional): Not checked yet. This feed provides agency_id. For RY2026, keep one stable value for each NTD reporter represented in the feed and crosswalk it on the P-50 form. The value does not need to equal the five-digit NTD ID; we do not have that ID on file, so the optional equality comparison is not checked yet.

Key facts

Feed URL

https://data.trilliumtransit.com/gtfs/ninetown-connecticut-us/ninetown-connecticut-us.zip

Last checked

2026-10-07

Service window

Feed has expired. Last service date 2027-05-27.

Feed version

UTC: 17-Sep-2026 17:05

Location

Connecticut