GTFS Scorecard

← Back to the full scorecard

Call-prep brief · checked 2026-07-09

Flex v2 included

Grade F · 44.4 / 100

Unchanged since 2026-07-08.

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 no change
  • Rider experience no change

Top three things to fix

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

    Stop time with only arrival or departure time (flagged by the MobilityData validator). See the linked rule for what this affects.

    Effort: Varies.

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

    Missing trip edge (flagged by the MobilityData validator). See the linked rule for what this affects.

    Effort: Varies.

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

    Block trips with overlapping stop times (flagged by the MobilityData validator). See the linked rule for what this affects.

    Effort: Varies.

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

NTD certification readiness: Needs attention

This feed is close to NTD-ready. 4 validator errors to resolve.

Published Ready
Published at a public URL.
Valid Needs attention
4 validator errors to resolve.
Current Ready
Service data covers the next 80 days.

agency_id and NTD ID: Not aligned. Your feed's agency_id is RTD; your National Transit Database ID is 80006. 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 80006 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.

The bar this score answers to

The state transit-data program is CDOT Digital Transit Mobility. Colorado's program coordinating GTFS data across transit providers.

Key facts

Feed URL
https://www.rtd-denver.com/files/gtfs/google_transit_flex.zip
Last checked
2026-07-09
Service window
79 days of service data remain. Last service date 2026-09-26.
Feed version
Jun26-36807-13-20-20260708-034151
State
Colorado

Part of the Colorado 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.