Call-prep brief · checked 2026-07-09
GTrans
Grade D · 66.5 / 100
Down 0.4 points since 2026-07-08 (D to D).
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.7
- Rider experience no change
Top three things to fix
Re-export with a validity window that reaches at least 60 days out.
Service data runs out in 9 day(s). When the calendar runs out, trip planners stop showing this agency. Fixing it now is calmer than after riders notice.
Effort: One export setting.
Agencies here usually clear this within about 1 week (based on 61 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.
Schedule a feed re-export now so the new calendar is live well before the current one ends.
This feed's service calendar runs out within the next 30 days. If a new feed isn't published before it ends, trip planners will drop your agency and riders will see no service.
Effort: Usually a re-export from your scheduling software.
Agencies here usually clear this within about 1 week (based on 24 observed fixes).
Ready to send to the agency
Hi GTrans team, Service data runs out in 9 day(s). When the calendar runs out, trip planners stop showing this agency. Fixing it now is calmer than after riders notice. The fix is usually one export setting: Re-export with a validity window that reaches at least 60 days out. 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/gtrans-2270/
NTD certification readiness: Needs attention
This feed is close to NTD-ready. Service data runs out in 10 days; renew before you certify.
- Published Ready
- Published at a public URL.
- Valid Ready
- Passes validation with no errors.
- Current Needs attention
- Service data runs out in 10 days; renew before you certify.
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.
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://ridegtrans.com/gtfs.zip
- Last checked
- 2026-07-09
- Service window
- 9 days of service data remain. Last service date 2026-07-18.
- Feed version
- S1000131
- 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.