Santa Ynez Valley Transit

What changed since the last check

• Correctness no change
• Freshness no change
• Rider experience no change
• Realtime quality no change

Top three things to fix

1. Check the vehicle positions endpoint with your AVL vendor; it should return a fresh GTFS-Realtime protobuf on every request.

   The vehicle positions realtime feed failed during sampling. When this feed is down, riders see scheduled times presented as if they were live.

   This was measured over a realtime sampling window, so it has no feed-wide share.

   Effort: Usually a vendor support ticket.

2. 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.

   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: Usually one export setting.

3. 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.

   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: Usually a bulk edit in your scheduling software.

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 91 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-10-31

Service window

91 days of service data remain. Last service date 2027-01-30.

Feed version

2026-06-17T04:03:53Z

Location

California