Feed status · checked 2026-06-16
Unitrans (ASUCD / City of Davis)
Based on the feed this agency publishes
up 10.2 since 2026-06-15 · C → B
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_boarding to 1 (accessible) or 2 (not accessible) for every stop. A field survey can start with the busiest stops.
296 of 296 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.
⏱ A column in stops.txt; your scheduling software likely has it.
Set wheelchair_accessible on every trip (most small-agency fleets are 100% accessible, so this is often a single default).
3071 of 3071 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.
Enable 'remove unused shapes' (or similar) in your export tool.
The feed contains route shapes no trip uses. Harmless to riders, but it bloats the feed and suggests stale export data.
⏱ One setting.
Score by category
The MobilityData validator flagged 4 kinds of issues: 0 error, 72 warning, and 24 informational instances in total.
Service data covers the next 98 days.
0% of stops state wheelchair accessibility (0% marked accessible). Fare data is published.
Unitrans runs live bus tracking, but its data feed needs an access key we don't have yet. Nothing here counts against the grade.
Over time
Overall score across the last 6 checks — up 10.2 since 2026-06-15.
What changed since your last check
- Correctness up 12.0
- Freshness up 20.0
- Rider experience no change
Everything we checked
- Warning3071 instances
3071 of 3071 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
- Warning296 instances
296 of 296 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
- Warning54 instances
The feed contains route shapes no trip uses.
Harmless to riders, but it bloats the feed and suggests stale export data.
Fix: Enable 'remove unused shapes' (or similar) in your export tool. (One setting.)
Validator rule: unused_shape · Read the fix guide
- Warning18 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.)
Validator rule: stop_without_stop_time · Read the fix guide
- Info23 instances
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.
Fix: Check the flagged column names for misspellings of standard GTFS fields; remove them if they are vendor extras. (A quick look at the flagged files.)
Validator rule: unknown_column · Read the fix guide
- Info1 instance
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.)
Validator rule: service_window_outside_feed_period · Read the fix guide