Call-prep brief · checked 2026-07-09
Tompkins Consolidated Area Transit Inc
Grade C · 73.3 / 100
Down 0.3 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
Set wheelchair_boarding to 1 (accessible) or 2 (not accessible) for every stop. A field survey can start with the busiest stops.
637 of 637 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.
Effort: A column in stops.txt; your scheduling software likely has it.
Set wheelchair_accessible on every trip (most small-agency fleets are 100% accessible, so this is often a single default).
1375 of 1375 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).
Review the rule documentation for 'route_long_name_contains_short_name' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.
Route long name contains short name (flagged by the MobilityData validator). See the linked rule for what this affects.
Effort: Varies.
NTD certification readiness: Ready
This feed looks ready for your NTD certification: published at a public URL, valid, and current. The official check is still your D-10 certification.
- Published Ready
- Published at a public URL.
- Valid Ready
- Passes validation with no errors.
- Current Ready
- Service data covers the next 49 days.
agency_id and NTD ID: Not aligned. Your feed's agency_id is 0; your National Transit Database ID is 20145. 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 20145 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://s3.amazonaws.com/tcat-gtfs/tcat-ny-us.zip
- Last checked
- 2026-07-09
- Service window
- 37 days of service data remain. Last service date 2026-08-15.
- Feed version
- 20260625
- State
- New York
Part of the New York 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.