Unitrans (ASUCD / City of Davis)

Grade C · 76.7 out of 100

Unchanged since 2026-10-01.

What this grade measures

The quality of the schedule data in the feed scored here for trip-planning apps: whether riders using Google Maps, Apple Maps, or Transit see current, correct, and complete information. It measures the data feed, not service quality or operations.

Category scores

The four rubric categories, each scored 0 to 100. A category the pipeline has not measured yet shows no number and never counts against the grade.
Category	Score	Where this feed stands
Correctness	75.2	The MobilityData validator flagged 5 kinds of issue across 119 instances (0 error, 96 warning, 23 informational).
Freshness	100.0	Service data covers the next 72 days.
Rider experience	60.0	0% of stops state wheelchair accessibility (0% marked accessible, 0% marked not accessible). This measures what the feed publishes, not whether a stop is physically usable. Fare data is published.
Realtime quality	Not yet published	Unitrans runs live tracking through Swiftly, but no public GTFS-Realtime endpoint is documented. Realtime remains unmeasured and does not count against the grade.

Top three things to fix

Three improvements, in priority order, each sized so a board can see what it is approving:

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.
Estimated effort: A column in stops.txt; your scheduling software likely has it.
Set wheelchair_accessible on every trip. If every vehicle is accessible, this may be one default; otherwise use the value for each trip.
6210 of 6210 trips don't say whether the vehicle is wheelchair accessible. Even with accessible stops, riders need to know the bus itself can take them.
Estimated effort: A default or per-trip field in your export.
Turn on 'remove unused shapes' (or the like) 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.
Estimated effort: One setting.

NTD GTFS readiness Ready

Published at a public URL, valid, current, and identified with agency_id: the four feed checks for RY2026 all hold here. Only your own D-10 and P-50 filings make that official; this is a heads-up, not a determination.

Published Ready: Published at a public URL.
Valid Ready: Passes validation with no errors.
Current Ready: Service data covers the next 72 days.
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.
shapes.txt covers your trips Ready: All 6210 trips have a shape in shapes.txt.

In plain words: agencies that report to the federal National Transit Database certify once a year, on form D-10, that they publish a working, up-to-date feed. For RY2026, each represented reporter also needs a stable agency_id crosswalked to its NTD ID on P-50; the two values need not be equal. This section is a heads-up on whether the feed looks ready; the filings are the official check. FTA also requires shapes.txt in the published GTFS: Full Reporters from Report Year 2025, and Reduced, Rural, and Tribal Reporters from Report Year 2026.

Over time

Unchanged since 2026-10-01. The table lists each daily check.

Showing the 12 most recent of 32 checks.

Overall score by check, with the change from the previous check stated in words.
Check	Score	Grade	Change
2026-07-03	80.8	B	not compared
2026-07-04	80.8	B	not compared
2026-07-05	80.8	B	not compared
2026-07-06	80.8	B	not compared
2026-07-07	80.8	B	not compared
2026-07-08	80.8	B	not compared
2026-07-09	80.8	B	not compared
2026-07-10	80.8	B	not compared
2026-08-06	75.6	C	not compared
2026-08-07	72.6	C	down 3.0
2026-10-01	76.7	C	up 4.1
2026-10-02	76.7	C	no change