Call-prep brief · checked 2026-07-09
Yolobus (Yolo County Transportation District)
Grade B · 82.5 / 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
- Realtime quality no change
Top three 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.
Effort: Often one default setting in your export.
Agencies here usually clear this within about 1 week (based on 5 observed fixes).
Add fare_attributes.txt (or Fares v2 files) with your fare structure. If your service is fare-free, ask to have it marked fare-free instead.
The feed contains no fare information. Riders see 'fare unknown' in trip planners and can't budget their trip; visitors are most affected.
Effort: A small file for most flat-fare systems.
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.
Effort: Two fields, set once in export settings.
Agencies here usually clear this within about 1 week (based on 16 observed fixes).
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 72 days.
agency_id and NTD ID: Not aligned. Your feed's agency_id is d139e461-175c-4156-beb0-e6a23b64d978; your National Transit Database ID is 90090. 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 90090 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://avl.yctd.org/RealTime/google_transit.zip
- Last checked
- 2026-07-09
- Service window
- 60 days of service data remain. Last service date 2026-09-07.
A data-quality and completeness read to support an agency conversation. Not an official compliance determination. Rubric v1.1, validator 8.0.1.