Call-prep brief · checked 2026-08-01

Santa Ynez Valley Transit

Grade A · 96.5 / 100

Unchanged since 2026-07-31.

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 no change
Rider experience no change

Top three things to fix

Turn on shape cleanup in your export tool, or drop the repeated points from shapes.txt.
Some route lines list the same point twice in a row. Repeated points don't hurt riders, but they can skew distance math and hint at a shaky export.
Effort: Usually one export setting.
Set trip_headsign to the trip's last stop or its overall destination.
Some trip headsigns name a stop along the way, not the final destination. The sign should tell riders where the bus ends up, so a midpoint name can send them the wrong way.
Effort: Usually a bulk edit in your scheduling software.
Check the flagged column names for misspellings of standard GTFS fields; remove them if they are vendor extras.
Some files contain columns that are not part of the GTFS spec. Harmless to riders, but apps ignore these columns and they can hide typos in real column names.
Effort: A quick look at the flagged files.

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: Some route lines list the same point twice in a row.
Next action: Turn on shape cleanup in your export tool, or drop the repeated points from shapes.txt.
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: Santa Ynez Valley Transit
Finding: equal_shape_distance_same_coordinates
Feed evidence: Some route lines list the same point twice in a row.
Why it matters: Repeated points don't hurt riders, but they can skew distance math and hint at a shaky export.
Requested change: Turn on shape cleanup in your export tool, or drop the repeated points from shapes.txt.
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/santa-ynez-valley-transit/?finding=equal_shape_distance_same_coordinates#finding-handoff

NTD GTFS readiness: Ready

Published at a public URL, valid, current, and identified with agency_id: the four feed checks for RY2026 all hold here. Only your own D-10 and P-50 filings make that official; this is a heads-up, not a determination.

Published Ready: Published at a public URL.
Valid Ready: Passes validation with no errors.
Current Ready: Service data covers the next 182 days.
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://mjcaction.com/MJC_GTFS_Public/syvt_google_transit.zip
Last checked: 2026-08-01
Service window: 182 days of service data remain. Last service date 2027-01-30.
Feed version: 2026-06-17T04:03:53Z
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.