Froggy Transportation

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. Populate trip_headsign to match what the bus displays.

   7 of 7 trips have no headsign. Riders at the stop can't tell which direction a bus is going.

   Estimated effort: Usually a bulk edit in your scheduling software.

2. Add feed_info.txt with feed_start_date and feed_end_date to your export.

   feed_info.txt is missing its start/end dates Apps and this scorecard can't warn anyone before the feed goes stale without stated validity dates.

   Estimated effort: Two fields, set once in export settings.

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

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

   Equal shape distance diff coordinates distance below threshold (flagged by the MobilityData validator). See the linked rule for what this affects.

   Estimated effort: Varies.

This feed is built with National RTAP's GTFS Builder. Your staff can usually make these changes in the GTFS Builder spreadsheets and republish, and National RTAP's help desk supports that at no cost.

Where this agency stands

Ahead of 88% of all tracked agencies, and ahead of 84% of small agencies nationwide.