Call-prep brief · checked 2026-08-01
Santa Clara Valley Transportation Authority (VTA)
Grade F · 51.9 / 100
Down 0.4 points since 2026-07-31 (F 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.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 8 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.
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.
Effort: Often a bulk fix in your scheduling software.
Re-generate shape_dist_traveled on export so stop and shape distances use the same units.
On some trips the stop distances run a little past the end of the route line. The stop and shape distance values don't quite line up, so any math that uses them can drift.
Effort: Usually an export-tool fix, not hand editing.
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 8 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
- Feed evidence
- Some rider-facing names are in ALL CAPS or all lowercase.
- Next action
- Use mixed case for stop names and headsigns (e.g. 'Main St & 2nd Ave', not 'MAIN ST & 2ND AVE').
- 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
- Feed evidence
- On some trips the stop distances run a little past the end of the route line.
- Next action
- Re-generate shape_dist_traveled on export so stop and shape distances use the same units.
- 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
Ready to send to the agency
Hi Santa Clara Valley Transportation Authority (VTA) team, Service data runs out in 8 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/santa-clara-valley-transportation-authority-vta/
NTD GTFS readiness: Needs attention
This feed is close to NTD-ready. Service data runs out in 8 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 8 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): Different (allowed). Your feed's agency_id is VTA; your National Transit Database ID is 90013. A feed that serves several agencies (a shared regional feed) can legitimately carry more than one agency_id. The values do not need to equal the five-digit NTD ID, so this difference is allowed and carries no score. Confirm that P-50 crosswalks agency_id VTA to NTD ID 90013, and keep the feed value stable. Do not change it solely to make the two values equal.
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://gtfs.vta.org/gtfs_vta.zip
- Last checked
- 2026-08-01
- Service window
- 8 days of service data remain. Last service date 2026-08-09.
- Feed version
- 2026-07-14_12:57
- Location
- 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.3, validator 8.0.1.