Unitrans — GTFS feed status board

Score by category

01 Correctness 84.8 Validator flagged 4 kinds of issues; no errors, mostly warnings.

02 Freshness 100 Service data covers the next 98 days. No expiry risk.

03 Rider experience 60 0% of stops state wheelchair accessibility. Fares are published.

04 Realtime quality — not measured — NOT YET PUBLISHED Unitrans runs live tracking, but the feed needs an access key. Nothing here counts against the grade.

Top things to fix — most rider-affecting first

Fix 01

Set wheelchair_boarding on every stop

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

⏱ A column in stops.txt; your scheduling software likely has it.

Fix 02

Set wheelchair_accessible on every trip

Even with accessible stops, riders need to know the vehicle can carry them. Most small-agency fleets are 100% accessible, so this is often a single default.

⏱ Often one default setting in your export.

Fix 03

Remove unused route shapes

Shapes no trip uses are dead weight from the export and usually a sign of stale data the next reviewer has to wade through.

⏱ One setting.

About this data

Feed: unitrans.ucdavis.edu/media/gtfs/Unitrans_GTFS.zip
Checked: June 16, 2026 (re-checked daily)
Validator: MobilityData gtfs-validator 8.0.1
Rubric: version 1.1

A data-quality and completeness lens to help the agency improve its feed. Not an official compliance determination from any transit program.

Score history