Clovis Transit

What changed since the last check

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

No longer reported since the last check (1 finding):

• 17 of 21 sampled vehicle positions were far from their assigned route (worst: 4293 m). (scorecard_rt_vehicles_off_route)

This compares feed state. It does not identify who made a change or why.

Top three things to fix

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

   Foreign key violation (flagged by the MobilityData validator). See the linked rule for what this affects.

   Effort: Varies.

2. Set wheelchair_accessible on every trip. If every vehicle is accessible, this may be one default; otherwise use the value for each trip.

   16 of 16 trips don't say whether the vehicle is wheelchair accessible. Even with accessible stops, riders need to know the bus itself can take them.

   Effort: A default or per-trip field in your export.

3. Add the destination, direction, or 'via' label riders actually see to trip_headsign. Do not copy the route name. If the label changes during the trip, use stop_headsign.

   16 of 16 trips lack rider-facing destination or direction text. When a route has multiple directions or patterns, the route name alone may not tell riders which service is coming.

   Effort: Usually one value per route pattern in your scheduling source.

NTD GTFS readiness: Needs attention

This feed is close to NTD-ready. 1 validator error to resolve. Service data runs out in 30 days; renew before you certify.

Published Ready

Published at a public URL.

Valid Needs attention

1 validator error to resolve.

Current Needs attention

Service data runs out in 30 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://passio3.com/clovis/passioTransit/gtfs/google_transit.zip

Last checked

2026-08-02

Service window

30 days of service data remain. Last service date 2027-12-31.

Feed version

20250228

Location

California