Call-prep brief · checked 2026-10-07

GTrans

Grade C · 71.0 / 100

Down 0.3 points since 2026-10-06 (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.7
Rider experience no change
Realtime quality 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 3 day(s). When the calendar runs out, trip planners stop showing this agency. Fixing it now is calmer than after riders notice.
This one is about the feed as a whole, so there is no share of it to count.
Effort: One export setting.
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.
This one is about the feed as a whole, so there is no share of it to count.
Effort: A small file for most flat-fare systems.
Use mixed case for stop names and headsigns (e.g. 'Main St & 2nd Ave', not 'MAIN ST & 2ND AVE').
Some rider-facing names are in ALL CAPS or all lowercase. ALL-CAPS stop and headsign names are harder to read in apps and are read awkwardly by screen readers.
This is a validator notice, and the validator decides what each instance covers, so no share of the network can be read from it here.
Effort: Often a bulk fix in your scheduling software.

Riders and need behind these fixes

This feed carries no National Transit Database ID, so annual rider-trips are not known for it.
California as a whole measures lower on transit need. That is a statewide reading, not one for this feed's service area. Source: US Census ACS 5-year 2022, statewide overlay, as of 2026-10-05.

These describe this feed only. They do not rank agencies, and they do not change the grade or the order of the fixes.

Finding handoff

Move one finding to a recheck

Select one finding. Copy the request, make the change in the feed-producing tool, then compare the next complete run.

Feed evidence: Service data runs out in 3 day(s).
Next action: Re-export with a validity window that reaches at least 60 days out.
Recheck: Publish the changed feed at the same URL. On the next complete, comparable scorecard run, confirm that this finding is no longer reported.

Copy handoff text

Agency: GTrans
Finding: scorecard_feed_expiring_soon
Feed evidence: Service data runs out in 3 day(s).
Why it matters: When the calendar runs out, trip planners stop showing this agency. Fixing it now is calmer than after riders notice.
Requested change: Re-export with a validity window that reaches at least 60 days out.
Recheck: Publish the changed feed at the same URL. On the next complete, comparable scorecard run, confirm that this finding is no longer reported.
Evidence: https://gtfsscorecard.org/agency/gtrans-2270/?finding=scorecard_feed_expiring_soon#finding-handoff

Ready to send to the agency

Hi GTrans team, Service data runs out in 3 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/

Copy this note from the full scorecard.

NTD GTFS readiness: Needs attention

This feed is close to NTD-ready. Service data runs out in 3 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 3 days; renew before you certify.
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.

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-10-07
Service window: 3 days of service data remain. Last service date 2026-10-10.
Feed version: S1000133
Location: California

Part of the California portfolio: see where this agency sits among the other feeds in that group before the call.

A data-quality and completeness read to support an agency conversation. Not an official compliance determination. Rubric v1.4, validator 8.0.1.