Clovis Transit

Top things to fix

This feed is generated by your Passio system from the route and stop data they maintain. Send the fix list to your Passio contact.

Score by category

Over time

Overall score across the last 20 checks — down 1.7 since 2026-07-08.

What changed since your last check

• Correctness▼ down 4.0
• Freshness▼ down 1.7
• Rider experience— no change
• Realtime quality— no change

What changed in this feed

Overall score fell 1.7 points since 2026-07-08.

The feed file was re-published since 2026-07-08.

New since 2026-07-08 (2 findings)

• Warning1 instance

  This feed's service calendar runs out within the next 30 days.

  Validator rule: feed_expiration_date30_days · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)

• Warning1 instance

  Service data runs out in 29 day(s).

  Validator rule: scorecard_feed_expiring_soon · Read the fix guide · See GTFS Best Practices (opens GTFS Best Practices on an external site)

Subscribe to this feed’s changes (Atom) to hear about grade drops in a reader, with no sign-up.

Everything we checked

• Warning123 instances

  123 of 253 stops don't say whether a wheelchair user can board there.

  Riders who use wheelchairs can't plan a trip when accessibility is marked 'unknown'; apps show no information at all.

  Fix: Set wheelchair_boarding to 1 (accessible) or 2 (not accessible) for every stop. A field survey can start with the busiest stops. (A column in stops.txt; your scheduling software likely has it.)

  Validator rule: scorecard_wheelchair_boarding_unknown · Read the fix guide · See GTFS Schedule reference (opens the GTFS Schedule reference on an external site)

• Warning78 instances

  Some stops exist in the feed but no trip ever stops at them.

  Riders may walk to a stop where no bus is scheduled to arrive.

  Fix: Remove retired stops from the export, or add them back to the trips that should serve them. (A review pass in your scheduling software.)

  Agencies here usually clear this within about 1 week (based on 11 observed fixes).

  Validator rule: stop_without_stop_time · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)

• Warning17 instances

  17 of 17 trips don't say whether the vehicle is wheelchair accessible.

  Even with accessible stops, riders need to know the bus itself can take them.

  Fix: Set wheelchair_accessible on every trip (most small-agency fleets are 100% accessible, so this is often a single default). (Often one default setting in your export.)

  Agencies here usually clear this within about 1 week (based on 5 observed fixes).

  Validator rule: scorecard_wheelchair_accessible_unknown · Read the fix guide · See GTFS Schedule reference (opens the GTFS Schedule reference on an external site)

• Warning17 instances

  17 of 17 trips have no headsign.

  Riders at the stop can't tell which direction a bus is going.

  Fix: Populate trip_headsign to match what the bus displays. (Usually a bulk edit in your scheduling software.)

  Validator rule: scorecard_missing_headsigns · Read the fix guide · See GTFS Best Practices (opens GTFS Best Practices on an external site)

• Warning1 instance

  This feed's service calendar runs out within the next 30 days.

  If a new feed isn't published before it ends, trip planners will drop your agency and riders will see no service.

  Fix: Schedule a feed re-export now so the new calendar is live well before the current one ends. (Usually a re-export from your scheduling software.)

  Agencies here usually clear this within about 1 week (based on 24 observed fixes).

  Validator rule: feed_expiration_date30_days · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)

• Warning1 instance

  Service data runs out in 29 day(s).

  When the calendar runs out, trip planners stop showing this agency. Fixing it now is calmer than after riders notice.

  Fix: Re-export with a validity window that reaches at least 60 days out. (One export setting.)

  Agencies here usually clear this within about 1 week (based on 61 observed fixes).

  Validator rule: scorecard_feed_expiring_soon · Read the fix guide · See GTFS Best Practices (opens GTFS Best Practices on an external site)

• Warning1 instance

  The feed contains no fare information.

  Riders see 'fare unknown' in trip planners and can't budget their trip; visitors are most affected.

  Fix: Add fare_attributes.txt (or Fares v2 files) with your fare structure. If your service is fare-free, ask to have it marked fare-free instead. (A small file for most flat-fare systems.)

  Validator rule: scorecard_no_fare_data · Read the fix guide · See GTFS Best Practices (opens GTFS Best Practices on an external site)

• Info3 instances

  Service window outside feed period (flagged by the MobilityData validator).

  See the linked rule for what this affects.

  Fix: Review the rule documentation for 'service_window_outside_feed_period' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)

  Agencies here usually clear this within about 1 week (based on 17 observed fixes).

  Validator rule: service_window_outside_feed_period · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)