Golden Empire Transit District (GET)

What this grade measures

The quality of the schedule data this agency publishes 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.

Progress this period

No newly cleared items this period. The score and trend above reflect where the feed stands today.

What needs attention next

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

1. Use mixed case for stop names and headsigns (e.g. 'Main St & 2nd Ave', not 'MAIN ST & 2ND AVE').

   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.

   Estimated effort: Often a bulk fix in your scheduling software.

2. Remove retired stops from the export, or add them back to the trips that should serve them.

   Some stops exist in the feed but no trip ever stops at them. Riders may walk to a stop where no bus is scheduled to arrive.

   Estimated effort: A review pass in your scheduling software.

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

3. Review the rule documentation for 'leading_or_trailing_whitespaces' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.

   Leading or trailing whitespaces (flagged by the MobilityData validator). See the linked rule for what this affects.

   Estimated effort: Varies.

Where this agency stands

Ahead of 96% of all tracked agencies, and ahead of 99% of large agencies nationwide.