Feed status · checked 2026-06-16
Yolobus (Yolo County Transportation District)
Based on the feed this agency publishes
down 2.9 since 2026-06-15
A data-quality and completeness lens to help an agency improve its feed. Not the official Caltrans or Cal-ITP compliance determination. New to this? How to read your scorecard. Interactive view. Rubric v1.1, validator 8.0.1.
Top things to fix
Set wheelchair_accessible on every trip (most small-agency fleets are 100% accessible, so this is often a single default).
721 of 721 trips don't say whether the vehicle is wheelchair accessible. Even with accessible stops, riders need to know the bus itself can take them.
⏱ Often one default setting in your export.
Add feed_info.txt with feed_start_date and feed_end_date to your export.
feed_info.txt is missing its start/end dates (the file itself is absent) Apps and this scorecard can't warn anyone before the feed goes stale without stated validity dates.
⏱ Two fields, set once in export settings.
Add fare_attributes.txt (or Fares v2 files) with your fare structure.
The feed contains no fare information. Riders see 'fare unknown' in trip planners and can't budget their trip; visitors are most affected.
⏱ A small file for most flat-fare systems.
Score by category
The MobilityData validator flagged 2 kinds of issues: 0 error, 16 warning, and 0 informational instances in total.
Service data covers the next 83 days.
99% of stops state wheelchair accessibility (99% marked accessible). Fare data is not published.
Not scored yet. Nothing here counts against the grade.
Over time
Overall score across the last 6 checks — down 2.9 since 2026-06-15.
What changed since your last check
- Correctness no change
- Freshness no change
- Rider experience no change
Everything we checked
- Warning721 instances
721 of 721 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.)
Validator rule: scorecard_wheelchair_accessible_unknown · Read the fix guide
- Warning15 instances
Some rider-facing names are in ALL CAPS or all lowercase.
ALL-CAPS stop and headsign names are harder to read in apps and are read awkwardly by screen readers.
Fix: Use mixed case for stop names and headsigns (e.g. 'Main St & 2nd Ave', not 'MAIN ST & 2ND AVE'). (Often a bulk fix in your scheduling software.)
Validator rule: mixed_case_recommended_field · Read the fix guide
- Warning2 instances
2 of 374 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
- Warning1 instance
A recommended GTFS file (usually feed_info.txt) is missing.
feed_info.txt tells apps who publishes the feed and when it expires; without it nobody is warned before data goes stale.
Fix: Add feed_info.txt with publisher name, URL, language, and feed_start_date/feed_end_date. (One small file, set once in export settings.)
Validator rule: missing_recommended_file · Read the fix guide
- Warning1 instance
feed_info.txt is missing its start/end dates (the file itself is absent)
Apps and this scorecard can't warn anyone before the feed goes stale without stated validity dates.
Fix: Add feed_info.txt with feed_start_date and feed_end_date to your export. (Two fields, set once in export settings.)
Validator rule: scorecard_missing_feed_info_dates · Read the fix guide
- 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. (A small file for most flat-fare systems.)
Validator rule: scorecard_no_fare_data · Read the fix guide
- Info1 instance
feed_info.txt has no technical contact (feed_contact_email or feed_contact_url).
App makers and state data programs have nobody to email when they spot a problem with your feed, so problems linger.
Fix: Add feed_contact_email to feed_info.txt. (One field.)
Validator rule: scorecard_no_feed_contact · Read the fix guide