GTFS Scorecard

← Back to the full scorecard

Call-prep brief · checked 2026-07-09

County Connection (CCCTA)

Grade D · 62.5 / 100

Down 0.4 points since 2026-07-08 (D to D).

For this call: lead with the grade and the three fixes below, then confirm the feed is current and the NTD details line up. Each fix is framed as a next step, not a failure.

What changed since the last check

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

Top three things to fix

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

    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.

    Effort: Two fields, set once in export settings.

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

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

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

    Effort: Varies.

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

agency_id and NTD ID: Not aligned. Your feed's agency_id is 2; your National Transit Database ID is 90078. A feed that serves several agencies (a shared regional feed) can legitimately carry more than one agency_id, so a difference here is a heads-up, not an error. Optionally set the agency_id for your service to 90078 in agency.txt (and the matching agency_id in routes.txt) so the feed lines up with your NTD record. It is a convenience, not a required feed change: FTA also links agency_id to your NTD ID on your P-50 form.

Key facts

Feed URL
https://countyconnection.com/GTFS/google_transit.zip
Last checked
2026-07-09
Service window
30 days of service data remain. Last service date 2026-08-08.
State
Tennessee

Part of the Tennessee portfolio: see where this agency sits among the state's feeds before the call.

A data-quality and completeness read to support an agency conversation. Not an official compliance determination. Rubric v1.1, validator 8.0.1.