Santa Ynez Valley Transit

What changed since the last check

• Correctness no change
• Freshness no change
• Rider experience no change

Top three things to fix

1. Review the rule documentation for 'equal_shape_distance_same_coordinates' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.

   Equal shape distance same coordinates (flagged by the MobilityData validator). See the linked rule for what this affects.

   Effort: Varies.

2. Review the rule documentation for 'trip_headsign_matches_intermediate_stop' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.

   Trip headsign matches intermediate stop (flagged by the MobilityData validator). See the linked rule for what this affects.

   Effort: Varies.

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

NTD certification readiness: Ready

This feed looks ready for your NTD certification: published at a public URL, valid, and current. The official check is still your D-10 certification.

Published Ready

Published at a public URL.

Valid Ready

Passes validation with no errors.

Current Ready

Service data covers the next 217 days.

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.

Key facts

Feed URL

https://mjcaction.com/MJC_GTFS_Public/syvt_google_transit.zip

Last checked

2026-07-09

Service window

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

Feed version

2026-06-17T04:03:53Z