GTFS Scorecard

← Back to the full scorecard

Call-prep brief · checked 2026-08-02

Chicago Transit Authority (CTA)

Grade F · 51.7 / 100

Down 0.5 points since 2026-08-01 (F to F).

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. Review the rule documentation for 'equal_shape_distance_diff_coordinates' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.

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

    Effort: Varies.

  2. Add the destination, direction, or 'via' label riders actually see to trip_headsign. Do not copy the route name. If the label changes during the trip, use stop_headsign.

    94667 of 94667 trips lack rider-facing destination or direction text. When a route has multiple directions or patterns, the route name alone may not tell riders which service is coming.

    Effort: Usually one value per route pattern in your scheduling source.

  3. Add fare_attributes.txt (or Fares v2 files) with your fare structure. If your service is fare-free, ask to have it marked fare-free instead.

    The feed contains no fare information. Riders see 'fare unknown' in trip planners and can't budget their trip; visitors are most affected.

    Effort: A small file for most flat-fare systems.

Finding handoff

Move one finding to a recheck

Select one finding. Copy the request, make the change in the feed-producing tool, then compare the next complete run.

Feed evidence
Equal shape distance diff coordinates (flagged by the MobilityData validator).
Next action
Review the rule documentation for 'equal_shape_distance_diff_coordinates' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.
Recheck
Publish the changed feed at the same URL. On the next complete, comparable scorecard run, confirm that this finding is no longer reported.
Copy handoff text

NTD GTFS readiness: Needs attention

This feed is close to NTD-ready. 1 validator error to resolve.

Published Ready
Published at a public URL.
Valid Needs attention
1 validator error to resolve.
Current Ready
Service data covers the next 59 days.
agency_id provided Ready
agency.txt provides agency_id. For RY2026, keep one stable value for each NTD reporter represented in the feed and crosswalk each value on the P-50 form.

agency_id equals NTD ID (optional): Not checked yet. This feed provides agency_id. For RY2026, keep one stable value for each NTD reporter represented in the feed and crosswalk it on the P-50 form. The value does not need to equal the five-digit NTD ID; we do not have that ID on file, so the optional equality comparison is not checked yet.

Key facts

Feed URL
http://www.transitchicago.com/downloads/sch_data/google_transit.zip
Last checked
2026-08-02
Service window
59 days of service data remain. Last service date 2026-09-30.
Location
Illinois

Part of the Illinois 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.3, validator 8.0.1.