Prep for a call: printable one-page brief · For your board packet: printable one-pager · Compare with another agency · Watch this feed: get an email before it expires
Feed status · checked 2026-07-09
Yolo County Transportation District (Yolobus)
Based on the feed this agency publishes
unchanged since 2026-07-08
Ahead of 44% of all tracked agencies and 41% of mid-size agencies. Operates in California.
A data-quality and completeness lens to help an agency improve its GTFS feed. Not an official compliance determination from any transit program. New to this? How to read your scorecard. Interactive view of this scorecard. Rubric v1.1, validator 8.0.1.
Checked for changes 11 minutes ago; last fetch returned HTTP 404.
Measured 3 of 4 score categories from the Mobility Database's mirror copy of the feed.
How we measured this
Confidence in this measurement: provisional.
- Realtime quality was not measured this run. It does not count against the grade.
- The agency's own feed URL was unreachable, so the Mobility Database's hosted mirror copy was scored instead.
Confidence describes how much the pipeline could measure this run, not the feed itself. It never changes the grade.
Top things to fix
Re-export the feed with a calendar that reaches further out, and set feed_info feed_end_date past your next service change.Likely your export tool
Service data ended 158 day(s) ago. When the calendar runs out, trip planners stop showing this agency even though the buses are still running. Riders are told the service does not exist.
⏱ Usually one export setting; export on a schedule so it never lapses again.worth about +100 points
Agencies here usually clear this within about 1 week (based on 18 observed fixes).
Set wheelchair_accessible on every trip (most small-agency fleets are 100% accessible, so this is often a single default).Likely your export tool
743 of 743 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.worth about +15 points
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.
⏱ A small file for most flat-fare systems.worth about +15 points
Close the loop on each fix. Read the guide, make the change in your tool, and let the next run verify it — the scorecard shows the fix; the agency publishes it.
Re-export the feed with a calendar that reaches further out, and set feed_info feed_end_date past your next service change. · Read the fix guide
Make the change. Make this change in whatever tool produces your feed, then re-export.
Prove it cleared. The next scorecard run re-checks this automatically and, once it is gone, mints a dated receipt. Self-check a feed before you publish.
Set wheelchair_accessible on every trip (most small-agency fleets are 100% accessible, so this is often a single default). · Read the fix guide
Make the change. Make this change in whatever tool produces your feed, then re-export.
Prove it cleared. The next scorecard run re-checks this automatically and, once it is gone, mints a dated receipt. Self-check a feed before you publish.
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. · Read the fix guide
Make the change. Make this change in whatever tool produces your feed, then re-export.
Prove it cleared. The next scorecard run re-checks this automatically and, once it is gone, mints a dated receipt. Self-check a feed before you publish.
Send your vendor a fix request
You may not control the GTFS export yourself. Copy this and send it to whoever runs your scheduling software export. It names each fix with the validator notice and a guide link.
Send the agency a note
Supporting this agency? Copy this and email it to them. It names what lapsed, why it matters to riders, and the one setting to change.
Score by category
The MobilityData validator flagged 4 kinds of issue across 22 instances (0 error, 22 warning, 0 informational).
Service data ended 158 day(s) ago. Trip planners have likely already dropped this feed.
99% of stops state wheelchair accessibility (99% marked accessible, 0% marked not accessible). This measures what the feed publishes, not whether a stop is physically usable. Fare data is not published.
100% of stops state accessibility (100% marked accessible). Reflects what the feed states, not verified physical usability.
Not scored yet. Nothing here counts against the grade.
Routes and stops
Each route is drawn once, using the longest shape its trips follow; stops are the dots.
Skip to route and stop dataBasemap: OpenFreeMap, © OpenStreetMap contributors. Routes and stops: this agency's GTFS feed.
- 138 (pink)
- 211 (teal)
- 212 (orange)
- 215 (orange)
- 230 (teal)
- 240 (purple)
- 37 (teal)
- 40 (purple)
- 41 (purple)
- 42A (teal)
- 42B (green)
- 43 (red)
- 43R (teal)
- 44 (red)
- 45 (red)
| Route | Type | Line color |
|---|---|---|
| 138 Causeway Connection | Bus | pink |
| 211 ROUTE 211 | Bus | teal |
| 212 ROUTE 212 | Bus | orange |
| 215 ROUTE 215 | Bus | orange |
| 230 ROUTE 230 | Bus | teal |
| 240 ROUTE 240 | Bus | purple |
| 37 ROUTE 37 | Bus | teal |
| 40 ROUTE 40 | Bus | purple |
| 41 ROUTE 41 | Bus | purple |
| 42A ROUTE 42A | Bus | teal |
| 42B ROUTE 42B | Bus | green |
| 43 ROUTE 43 | Bus | red |
| 43R ROUTE 43-R | Bus | teal |
| 44 ROUTE 44 | Bus | red |
| 45 ROUTE 45 | Bus | red |
This feed has 374 stops.
List every stop
- Y Street & 45th
- Mondavi Center
- Silo at UC Davis
- Stockton Blvd & Colonial Way (NB)
- 5th St at G St.
- 5th St at I St.
- 5th St & Pelz Bike Path (WB)
- 5th St & Windmere Apts. (EB)
- 5th St & Cantrill/Greystone (WB)
- 5th St & Cantrill/Police Station (EB)
- 5th St & Post Office / Pole Line Rd (WB)
- 5th St & Post Office / Pole Line (EB)
- 5th St & Pole Line Rd/D.M.V (EB)
- 5th St & Pole Line Rd/D.M.V (WB)
- 5th St & Spafford St (EB)
- 5th St & Spafford (WB)
- 5th St. at D St. EB
- Cowell at Sunrise WB
- UC Davis Memorial Union
- UC Davis Health Sciences SB
- Ashley at W. Lincoln SB
- Ashley at W. Lincoln NB
- W. Beamer at Mariposa WB
- W. Beamer at Mariposa EB
- E. Beamer at Matmor WB
- E. Beamer at Matmor EB
- Beamer at 5th WB
- Beamer at 5th EB
- W. Beamer at West WB
- W. Beamer at West EB
- Cottonwood at W Beamer SB
- Cottonwood at W Beamer NB
- Cottonwood at Buckeye SB
- Cottonwood at Buckeye NB
- Cottonwood at Riverside SB
- Cottonwood at Riverside NB
- Cottonwood at W. Cross SB
- Cottonwood at W. Cross NB
- Cottonwood at W. Gibson SB
- Cottonwood at W. Gibson NB
- Cottonwood at W. Lincoln SB
- Cottonwood at W. Lincoln NB
- Cottonwood at W. Main SB
- Cottonwood at W. Main NB
- Cottonwood at W. Southwood SB
- Cottonwood at W. Southwood NB
- Court at 2nd WB
- Court at 2nd EB
- Court at Cleveland WB
- Court at Cleveland EB
- Court at College WB
- Court at College EB
- Court at Walnut WB
- Court at Walnut EB
- Farnham at Maxwell NB
- Farnham at Eaton
- Farnham at Howard NB
- W. Gibson at Amherst WB
- W. Gibson at Amherst EB
- Gibson at College EB
- Gibson at College WB
- Gibson at Coloma
- Gibson at Coloma
- W. Gibson at Midway WB
- W. Gibson at Midway EB
- Gibson at Spruce
- Gibson at Spruce
- E. Gibson at Washington WB
- E. Gibson at Washington EB
- W. Gibson at West WB
- Gibson at West
- E. Gum at East WB
- E. Gum at Matmor WB
- E. Gum at Wallace WB
- Industrial at E Main NB
- Industrial at E. Main SB
- W. Lincoln at Ashley WB
- Main at 5th WB
- Main at 5th EB
- Main at Cleveland WB
- Main at Cleveland EB
- W. Main at Community WB
- W. Main at Community EB
- E. Main at East
- E. Main at Industrial WB
- E. Main at Matmor
- Matmor at Cannery NB
- Matmor at Cannery SB
- Matmor at Crystal Springs
- Matmor at Oak NB
- Matmor at E. Main SB
- Matmor at E. Main NB
- Matmor at E. Gibson NB
- Matmor at E. Gibson SB
- Matmor at Gum SB
- Matmor at Gum NB
- Ogden at Branigan
- Pioneer at E. Gum NB
- West at Clover SB
- West at Clover NB
- West at North NB
- West at North SB
- E. Gibson at Pioneer EB
- 1st St. at D St. WB
- 1st St. at C St. EB
- 5th St. at D St. WB
- Alhambra at 5th St. EB
- Alhambra at Atlantis
- Alhambra at Arroyo
- Alhambra at Carcia
- Alhambra at Mace EB
- Alhambra at Covell
- Alhambra at 5th St. WB
- Alhambra at Loyola SB
- Alhambra at San Miguel
- Anderson at Amherst SB
- Anderson at Amherst NB
- Anderson at Hanover NB
- Anderson at Hanover SB
- Anderson at Russell SB
- Anderson at Russell NB
- Anderson at Sunset SB
- Anderson at Sunset NB
- Anderson at Villanova SB
- Anderson at Villanova NB
- Arlington at Lake WB
- Arlington at Lake EB
- Arlington at Shasta EB
- Arlington at Shasta WB
- Arthur at Alameda SB
- B at 4th NB
- B at 4th SB
- Chiles at Mace
- Chiles at Mace
- E. Covell at J EB
- E. Covell at J WB
- E. Covell at Poleline EB
- W. Covell at Sycamore WB
- W. Covell at Sycamore EB
- W. Covell at Shasta WB
- Cowell at Drummond EB
- Cowell at El Cemonte WB
- Cowell at El Cemonte EB
- Cowell at La Vida WB
- Cowell at La Vida EB
- Drummond at Lillard NB
- Drummond at Lillard SB
- El Cemonte at Glide NB
- Ensenada at Chiles
- F St. at 5th St.
- F St. at 6th St. SB
- F St. at Covell NB
- F St. at Covell SB
- Lake at W. Covell NB
- Lake at W. Covell SB
- Lillard at Cowell EB
- Loyola at Whittier Dr
- Loyola at Regis West
- Mace at 2nd St. SB
- Mace at Chiles
- Monarch at Campbell SB
- Monarch at Covell NB
- Poleline at Covell
- Russell at A St.WB
- Russell at A St. EB
- Tulip at Blackburn SB
- Tulip at Blackburn
- Tulip at Cascade NB
- Alhambra at Loyola NB
- Loyola at Tulip
- Lillard at Farragut WB
- W. Covell at Shasta EB
- 5th St. at C St.
- 6th St. at Andrew SB
- Anna at Bryte WB
- Anna at Bryte EB
- Bryte at Lisbon
- Golden Gate at Tortola
- Harbor at W. Capitol SB
- Harbor at Duluth SB
- Harbor at Duluth NB
- Hobson at Water
- Jefferson at Gateway
- Jefferson at Michigan
- Jefferson at Michigan NB
- Jefferson at Triangle Court SB
- Lisbon at Bryte
- Lisbon at Water
- Park at 17th NB
- Park at Stone NB
- Reed at I-80 WB
- Reed at Ikea EB
- Reed at Stillwater
- Solano at Sacramento NB
- Riverside at Cummins Co.
- Water at Lisbon
- Water at Hobson SB
- W. Capitol at Cedar WB
- W. Capitol at Enterprise WB
- W. Capitol at Enterprise EB
- W. Capitol at Glide WB
- W. Capitol at Glide EB
- W. Capitol at Harbor WB
- W. Capitol at Harbor EB
- W. Capitol at Jefferson WB
- W. Capitol at Jefferson EB
- W. Capitol at Pecan WB
- W. Capitol at Pine WB
- W. Capitol at Pine EB
- W. Capitol at Poplar WB
- W. Capitol at Poplar EB
- W. Capitol at Sycamore EB
- W. Capitol at Walnut EB
- W. Lincoln at Rd 98 EB
- W. Court at Cottonwood EB
- Ashley at W. Court
- 3rd St. at Clover NB
- 3rd St. at Clover SB
- 3rd St. at Beamer SB
- 3rd St. at Beamer NB
- Woodland Community College
- East at Gum
- W. Lincoln at Rd 98 WB
- County Fair Mall
- Pioneer at Spring Lake NB
- E. Main at Wal-Mart
- Jefferson at Lake Washington NB
- Jefferson at Lake Washington SB
- Marshall at Rivermont
- Harbor at W. Capitol NB
- W. Capitol at Interstate EB
- W. Capitol at Interstate Co. WB
- W. Capitol at Roadway EB
- W. Capitol at Roadway WB
- W. Capitol at Northport EB
- W. Capitol at Northport WB
- Solano at Sacramento SB
- Stillwater at Citi Group
- Stillwater at Reed
- Riverside at State Library WB
- Sacramento at Todhunter
- W. Capitol at Westacre EB
- W. Capitol at Westacre WB
- Railroad at Main (Madison)
- Yolo at Grafton (Esparto) NB
- Yolo at Grafton (Esparto) SB
- Jefferson at Higgins SB
- Hwy 16 at Rd 85 (Capay) WB
- Cache Creek Casino Resort
- Russell at California EB
- and 124 more (see the full list on the map or in the GeoJSON)
Over time
Overall score across the last 10 checks — unchanged since 2026-07-08.
Show the numbers
| Check | Score | Change |
|---|---|---|
| 2026-06-30 | 55.4 | first check |
| 2026-07-01 | 55.4 | no change |
| 2026-07-02 | 55.4 | no change |
| 2026-07-03 | 55.4 | no change |
| 2026-07-04 | 55.4 | no change |
| 2026-07-05 | 55.4 | no change |
| 2026-07-06 | 55.4 | no change |
| 2026-07-07 | 55.4 | no change |
| 2026-07-08 | 55.4 | no change |
| 2026-07-09 | 55.4 | no change |
What changed since your last check
- Correctness no change
- Freshness no change
- Rider experience no change
What changed in this feed
Overall grade and score held steady since 2026-07-08.
Same feed file as 2026-07-08; the published zip did not change.
Subscribe to this feed’s changes (Atom) to hear about grade drops in a reader, with no sign-up.
Everything we checked
- Error1 instance
Service data ended 158 day(s) ago.
When the calendar runs out, trip planners stop showing this agency even though the buses are still running. Riders are told the service does not exist.
Fix: Re-export the feed with a calendar that reaches further out, and set feed_info feed_end_date past your next service change. (Usually one export setting; export on a schedule so it never lapses again.)
Agencies here usually clear this within about 1 week (based on 18 observed fixes).
Validator rule: scorecard_feed_expired · Read the fix guide · See GTFS Best Practices (opens GTFS Best Practices on an external site)
- Warning743 instances
743 of 743 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.)
Agencies here usually clear this within about 1 week (based on 5 observed fixes).
Validator rule: scorecard_wheelchair_accessible_unknown · Read the fix guide · See GTFS Schedule reference (opens the GTFS Schedule reference on an external site)
- Warning15 instances
Some rider-facing names are in ALL CAPS or all lowercase.
ALL-CAPS stop and headsign names are harder to read in apps and are read awkwardly by screen readers.
Fix: Use mixed case for stop names and headsigns (e.g. 'Main St & 2nd Ave', not 'MAIN ST & 2ND AVE'). (Often a bulk fix in your scheduling software.)
Validator rule: mixed_case_recommended_field · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning5 instances
Some service calendars in the feed have already ended.
Expired calendars are dead weight and can hide real schedule problems from your staff and vendors.
Fix: Remove past service periods the next time you export the feed. (One setting in most export tools.)
Agencies here usually clear this within about 1 week (based on 61 observed fixes).
Validator rule: expired_calendar · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning2 instances
2 of 374 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 · See GTFS Schedule reference (opens the GTFS Schedule reference on an external site)
- Warning1 instance
A file GTFS asks for (usually feed_info.txt) is missing.
feed_info.txt tells apps who publishes the feed and when it expires; without it nobody is warned before data goes stale.
Fix: Add feed_info.txt with publisher name, URL, language, and feed_start_date/feed_end_date. (One small file, set once in export settings.)
Agencies here usually clear this within about 1 week (based on 13 observed fixes).
Validator rule: missing_recommended_file · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning1 instance
Many of the feed's trips don't run at all in the next 7 days.
It usually means old service periods are still in the export, making the feed bigger and harder to check.
Fix: Trim past service periods the next time you export. (One setting in most export tools.)
Agencies here usually clear this within about 1 week (based on 31 observed fixes).
Validator rule: trip_coverage_not_active_for_next7_days · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning1 instance
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.
Fix: Add feed_info.txt with feed_start_date and feed_end_date to your export. (Two fields, set once in export settings.)
Agencies here usually clear this within about 1 week (based on 16 observed fixes).
Validator rule: scorecard_missing_feed_info_dates · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning1 instance
The feed contains no fare information.
Riders see 'fare unknown' in trip planners and can't budget their trip; visitors are most affected.
Fix: 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. (A small file for most flat-fare systems.)
Validator rule: scorecard_no_fare_data · Read the fix guide · See GTFS Best Practices (opens GTFS Best Practices on an external site)
- Info1 instance
feed_info.txt has no technical contact (feed_contact_email or feed_contact_url).
App makers and state data programs have nobody to email when they spot a problem with your feed, so problems linger.
Fix: Add feed_contact_email to feed_info.txt. (One field.)
Agencies here usually clear this within about 1 week (based on 10 observed fixes).
Validator rule: scorecard_no_feed_contact · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
Beyond the grade
Opportunities that do not change your grade today: fare detail, on-demand service, and deeper accessibility data.
4 route badge(s) pair a color and text color below the WCAG 4.5:1 contrast bar (40, 41, 240, 211).
Consider: Adjust route_color or route_text_color so each pair clears 4.5:1. Often switching the text between black and white is enough.
83 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set ("3rd St. at Beamer SB", "3rd St. at Clover SB", "Woodland Community & Senior Center NB", and more).
Consider: Add tts_stop_name with the spoken form, e.g. 'Main Street and Second Avenue', for the affected stops.
Some fixes we can make for you
These are the safe mechanical fixes, applied to a copy of your feed. They change only what is certain and leave everything else untouched. Review the diff before you publish.
Trimmed surrounding whitespace 2 changes
For example: 'stop_name': '5th St at I St. ' -> '5th St at I St.'
Recased shouting route names 14 changes
For example: ROUTE 40 -> Route 40
NTD certification readiness Not ready
Resolve this before you certify on the D-10. Service data expired 158 days ago, so FTA would find the link out of date.
- Published Ready
- Published at a public URL.
- Valid Ready
- Passes validation with no errors.
- Current Not ready
- Service data expired 158 days ago, so FTA would find the link out of date.
- agency_id matches your NTD ID Not checked yet
- Setting your GTFS agency_id to your five-digit NTD ID is an optional way to line a feed up with its National Transit Database record. FTA links the two on your P-50 form, so it is not a required feed change. We don't have your NTD ID on file, so this is not checked yet.
- shapes.txt covers your trips Ready
- All 743 trips have a shape in shapes.txt.
In plain words: if you report to the federal transit database, you have to publish a working, up-to-date feed and confirm it once a year. This box is a heads-up on whether yours looks ready; it is not the official sign-off.
A readiness signal mapping this feed to the FTA National Transit Database GTFS requirement (Report Year 2023 onward: a public, valid, current feed, certified annually on the D-10). Aligning agency_id with your NTD ID lets the feed line up with your NTD record; the July 2025 final rule links the two on the P-50 form rather than requiring that feed change, and requires shapes.txt in the published GTFS: Full Reporters from Report Year 2025, and Reduced, Rural, and Tribal Reporters from Report Year 2026. Not an official determination; your certification is the official check.
Conformance mark Not yet
This feed is close to the conformance mark. Service data expired 158 days ago. States wheelchair access on 100% of stops and 0% of trips; the mark needs 90% of each.
- Valid Met
- Passes validation with no errors.
- Current Not yet
- Service data expired 158 days ago.
- Accessible Not yet
- States wheelchair access on 100% of stops and 0% of trips; the mark needs 90% of each.
In plain words: earn this mark when your feed passes validation, has not expired, and says whether nearly every stop and trip is wheelchair accessible.
A pass credential for a feed that is valid, current, and states wheelchair access on nearly every stop and trip. Accessibility here measures what the feed publishes, not whether a stop is physically usable. How the conformance mark works.
Below the Google and Apple Maps four-week coverage bar. This feed's last day of service has passed, so Google and Apple Maps will stop showing your agency. Re-export with a calendar that covers at least the next four weeks.
How this agency maps to the standards
A data-quality lens, not a compliance determination. Each category shows this feed's score and the standards it relates to: the FTA National Transit Database GTFS requirement, the MobilityData grading scheme, and the Google Transit gate. Read the full standards crosswalk.
In California, the published guideline is California Transit Data Guidelines. Caltrans' published quality guidelines and compliance checklist; this rubric is anchored to them.
California Minimum GTFS Guidelines checklist (3 of 6 measured items met)
The state's own Data Process Checklist, matched item by item to what this scorecard already measures. An item marked "not measured here" is real ground the checklist covers that this tool does not check; see the official checklist for the full picture.
- Meets Publish GTFS Schedule at a stable, automatically-fetchable URL
The published feed URL downloaded at the last check.
- Not measured here Implement required fields: Fares v2, text-to-speech stop names, shapes.txt, wheelchair_boarding, and Pathways where applicable
This scorecard measures wheelchair_boarding, shapes.txt coverage, fare data, and station pathways separately, below; it does not check the Fares v2 format specifically or text-to-speech stop names.
- Not measured here Achieve a passing score in every category of the MobilityData GTFS Grading Scheme v1
This scorecard automates a proxy for the Grading Scheme's rider-facing fields (see the standards crosswalk) rather than running the scheme itself, which grades by comparison to the real world by hand.
- Not measured here Publish changes to the base schedule at least one week ahead of every service change
This scorecard does not track a feed's publish history, so advance notice cannot be checked.
- Meets Produce no critical errors in the MobilityData GTFS Validator
Passes validation with no errors.
- Not measured here Publish Trip Updates, Vehicle Positions, and Alerts feeds
This scorecard checks realtime reachability and freshness overall; it does not check for all three feed types individually.
- Not measured here Update Trip Updates and Vehicle Positions at least every 20 seconds
This scorecard samples realtime freshness; it does not check this specific 20-second cadence.
- Not measured here Publish information for at least 99% of vehicles in service
This scorecard measures the share of scheduled trips represented in TripUpdates, a related but different figure than vehicle coverage.
- Not measured here Keep 100% of trip_ids consistent between Schedule and Realtime
This scorecard does not currently check trip_id consistency between the Schedule and Realtime feeds.
- Not measured here Produce no critical errors in the Center for Urban Transportation Research realtime validator
This scorecard does not run the CUTR realtime validator.
- Not measured here Publish accessible feed links on the agency or regional partner website
This scorecard does not check the agency's own website.
- Not measured here Register GTFS and GTFS-Realtime feeds with transit.land and the Mobility Database
This scorecard does not currently check aggregator registration for this section.
- Gap Designate a technical contact in feed_info.txt's feed_contact_email
feed_info.txt has no feed_contact_email or feed_contact_url.
- Gap wheelchair_boarding stated on stops and trips
States wheelchair access on 100% of stops and 0% of trips.
- Meets shapes.txt with a shape for every trip
All 743 trips have a shape in shapes.txt.
- Gap Fare data published, or the service marked fare-free
No fare data is published.
- Correctness 82 / 100
- GTFS Schedule best practices, checked by the MobilityData validator. MobilityData grading: stop locations, route names and colors. Google Transit: a feed must pass validation to stay in Maps.
- Freshness 0 / 100
- The FTA National Transit Database expectation of a valid, current feed. Google Transit: an expired calendar drops the agency from Maps.
- Rider experience 62 / 100
- GTFS Best Practices for rider-facing fields. MobilityData grading: stop names and headsigns.
- Realtime quality Not yet published
- GTFS-Realtime best practices: a stable URL, high uptime, and frequent updates.
Show your grade
Put a live badge on your agency site or feed README. It updates daily and links back to this scorecard.
Prefer a shields.io style? Point a dynamic endpoint badge at the published badge.json.
Cite this record
This page updates on every check. The record below does not: it is the dated file this grade came from, published at https://gtfsscorecard.org/data/artifacts/yolo-county-transportation-district-yolobus/2026-07-09.json and never overwritten, pinning the grade, category scores, rubric version, validator version, and the scored feed's sha256 as they stood on 2026-07-09. Use it in a board packet, an NTD narrative, or a research citation instead of linking the live page, whose content will differ on your next visit.
Citing the tool itself rather than one agency's record? Use the repo's CITATION.cff.