GTFS Scorecard

← Back to the full scorecard

Call-prep brief · checked 2026-07-09

Unitrans (ASUCD / City of Davis)

Grade B · 80.8 / 100

Unchanged since 2026-07-08.

For this call: lead with the grade and the three fixes below, then confirm the feed is current and the NTD details line up. Each fix is framed as a next step, not a failure.

What changed since the last check

  • Correctness no change
  • Freshness no change
  • Rider experience no change

Top three things to fix

  1. 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.

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

  2. 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.

    Effort: Often one default setting in your export.

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

  3. 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.

    Effort: One setting.

NTD certification readiness: Ready

This feed looks ready for your NTD certification: published at a public URL, valid, and current. The official check is still your D-10 certification.

Published Ready
Published at a public URL.
Valid Ready
Passes validation with no errors.
Current Ready
Service data covers the next 87 days.

agency_id and NTD ID: Not aligned. Your feed's agency_id is unitrans; your National Transit Database ID is 90142. A feed that serves several agencies (a shared regional feed) can legitimately carry more than one agency_id, so a difference here is a heads-up, not an error. Optionally set the agency_id for your service to 90142 in agency.txt (and the matching agency_id in routes.txt) so the feed lines up with your NTD record. It is a convenience, not a required feed change: FTA also links agency_id to your NTD ID on your P-50 form.

Key facts

Feed URL
https://unitrans.ucdavis.edu/media/gtfs/Unitrans_GTFS.zip
Last checked
2026-07-09
Service window
75 days of service data remain. Last service date 2026-09-22.
Feed version
SS1-SS2_2026_V1

A data-quality and completeness read to support an agency conversation. Not an official compliance determination. Rubric v1.1, validator 8.0.1.