Call-prep brief · checked 2026-07-09
Sacramento Regional Transit (SacRT)
Grade F · 59.6 / 100
Down 0.4 points since 2026-07-08 (D 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 down 1.6
- Rider experience 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.
2534 of 2534 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).
4953 of 4953 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).
Add fare_attributes.txt (or Fares v2 files) with your fare structure. If your service is fare-free, ask to have it marked fare-free instead.
The feed contains no fare information. Riders see 'fare unknown' in trip planners and can't budget their trip; visitors are most affected.
Effort: A small file for most flat-fare systems.
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 SRTD; your National Transit Database ID is 90019. 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 90019 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.
The bar this score answers to
The published guideline in California is California Transit Data Guidelines. Caltrans' published quality guidelines and compliance checklist; this rubric is anchored to them.
Key facts
- Feed URL
- https://iportal.sacrt.com/GTFS/SRTD/google_transit.zip
- Last checked
- 2026-07-09
- Service window
- 37 days of service data remain. Last service date 2026-08-15.
- Feed version
- June_2026
- State
- California
Part of the California 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.