Froggy Transportation

What changed since the last check

• Correctness no change
• Freshness no change
• Rider experience no change

Top three things to fix

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.

   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.

   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.

   Effort: Varies.

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 187 days.

agency_id and 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.

Key facts

Feed URL

https://rapid.nationalrtap.org/GTFSFileManagement/UserUploadFiles/11830/T.zip

Last checked

2026-07-09

Service window

175 days of service data remain. Last service date 2026-12-31.

State

Ohio