GTrans

Top things to fix

Score by category

Over time

Overall score across the last 20 checks — down 0.4 since 2026-07-08.

What changed since your last check

• Correctness— no change
• Freshness▼ down 1.7
• Rider experience— no change

What changed in this feed

Overall score fell 0.4 points 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.

What changed over time

On 2026-06-19 this feed started at grade C. On 2026-06-24 the grade moved from C to D. On 2026-06-29 the grade moved from D to C. On 2026-07-01 the grade moved from C to D. As of 2026-07-09 it holds grade D.

A plain-language history of this feed, newest first.

• 2026-07-08 Score rose 4 points, correctness rose 11 points.
• 2026-07-02 Score fell 5 points, correctness fell 11 points.
• 2026-07-01 Grade went C to D.
• 2026-06-29 Grade went D to C, correctness rose 6 points.
• 2026-06-24 Grade went C to D.

Everything we checked

• Warning1 instance

  This feed's service calendar runs out within the next 30 days.

  If a new feed isn't published before it ends, trip planners will drop your agency and riders will see no service.

  Fix: Schedule a feed re-export now so the new calendar is live well before the current one ends. (Usually a re-export from your scheduling software.)

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

  Validator rule: feed_expiration_date30_days · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)

• Warning1 instance

  Missing feed contact email and url (flagged by the MobilityData validator).

  See the linked rule for what this affects.

  Fix: Review the rule documentation for 'missing_feed_contact_email_and_url' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)

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

  Validator rule: missing_feed_contact_email_and_url · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)

• Warning1 instance

  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)

• Warning1 instance

  Service data runs out in 9 day(s).

  When the calendar runs out, trip planners stop showing this agency. Fixing it now is calmer than after riders notice.

  Fix: Re-export with a validity window that reaches at least 60 days out. (One export setting.)

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

  Validator rule: scorecard_feed_expiring_soon · Read the fix guide · See GTFS Best Practices (opens GTFS Best Practices 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.

• 2 route badge(s) pair a color and text color below the WCAG 4.5:1 contrast bar (2, 5).

  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.

• 376 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set ("Compton Bl & Matthisen Ave", "Western Ave & Redondo Beach Bl", "Western Ave & 154th St", 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.

• Recased shouting stop names 1 change

  For example: PRAIRIE AND ARBOR VITAE -> Prairie And Arbor Vitae

Run it yourself on your own copy of the feed: scorecard autofix <feed.zip> --out corrected.zip