← All agencies

Feed status · checked 2026-08-02

Chicago Transit Authority (CTA)

Based on the feed this agency publishes

Service mode Metro + Bus

51.7 / 100

down 0.5 since 2026-08-01

Catalogued in Illinois.

Covers 59 daysRealtime not yet published

A data-quality and completeness lens to help an agency improve its GTFS feed. Not an official compliance determination from any transit program. New to this? How to read your scorecard. Interactive view of this scorecard. Rubric v1.3, validator 8.0.1.

Checked for changes 3 hours ago; last changed 23 days ago.

Measured 3 of 4 score categories from the agency's own feed.

How we measured this

Confidence in this measurement: medium.

  • Realtime quality was not measured this run. It does not count against the grade.
  • The feed was downloaded from the agency's own URL.

Confidence describes how much the pipeline could measure this run, not the feed itself. It never changes the grade.

Top things to fix

Fix 01

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.

⏱ Varies.worth about +24 points in its category

Fix 02

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.

⏱ Usually one value per route pattern in your scheduling source.worth about +15 points in its category

Fix 03

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.

⏱ A small file for most flat-fare systems.worth about +15 points in its category

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
How to make and check these changes

Check the result on the published feed. Read the guide, make the change in your tool, and use the next comparable run to see whether the finding is still reported. Only an action or ticket record can attribute who made the change.

  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.

    Make the change. Make this change in whatever tool produces your feed, then re-export.

    Check the result. The next scorecard run checks this finding again. If a comparable check no longer reports it, the feed's clearance log records that result. This confirms feed state, not who made the change. Self-check a feed before you publish.

  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. · Read the fix guide

    Make the change. Make this change in whatever tool produces your feed, then re-export.

    Check the result. The next scorecard run checks this finding again. If a comparable check no longer reports it, the feed's clearance log records that result. This confirms feed state, not who made the change. Self-check a feed before you publish.

  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. · Read the fix guide

    Make the change. Make this change in whatever tool produces your feed, then re-export.

    Check the result. The next scorecard run checks this finding again. If a comparable check no longer reports it, the feed's clearance log records that result. This confirms feed state, not who made the change. Self-check a feed before you publish.

Rider view: what this feed publishes

A quick read of rider-facing information in this feed.

Schedule visibility
The feed's last published service date is in 59 days.
Published accessibility data
Accessibility information is stated for 100% of stops and 100% of trips. This measures published data, not whether stops or vehicles are physically usable.
Fare information
No fare information is published in the feed.
Realtime information
Realtime-feed availability and live-arrival coverage are not known from this scorecard.

Important: This does not rate service reliability. Riders should confirm current service alerts, fares, and accessibility accommodations with the transit operator before traveling.

Send your vendor a fix request

You may not control the GTFS export yourself. Copy this and send it to whoever runs your scheduling software export. It names each fix with the validator notice and a guide link.

Score by category

Correctness26.0 / 100

The MobilityData validator flagged 12 kinds of issue across 188812 instances (96894 error, 1475 warning, 90443 informational).

Freshness83.3 / 100

Service data covers the next 59 days.

Rider experience62.5 / 100

100% of stops state wheelchair accessibility (99% marked accessible, 1% marked not accessible). This measures what the feed publishes, not whether a stop is physically usable. Fare data is not published.

Accessibility100 / 100

100% of stops state accessibility (99% marked accessible). Reflects what the feed states, not verified physical usability.

3 accessibility depth signals

  • 91 route badge(s) pair a color and text color below the WCAG 4.5:1 contrast bar (1, 3, N5, 7, 8, and more).

    Consider: Adjust route_color or route_text_color so each pair clears 4.5:1. Often switching the text between black and white is enough.

  • 10243 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set ("Jackson & Austin Terminal", "Jackson & Lotus", "Jackson & Lockwood", and more).

    Consider: Add tts_stop_name with the spoken form, e.g. 'Main Street and Second Avenue', for the affected stops.

  • This feed models stations or entrances but has no pathways.txt and levels.txt.

    Consider: Add pathways.txt connecting entrances, platforms, and elevators, and levels.txt for each floor, so the step-free route is described.

Opportunities to strengthen the data, not deductions from the sub-score above. States what the second accessibility lens can check from the feed, not verified physical usability.

Realtime qualityNot yet measured

Not scored yet. Nothing here counts against the grade.

Routes and stops

Each route is drawn once, using the longest shape its trips follow; stops are the dots.

This feed has 11125 stops.

Skip to route and stop data

The route and stop data is ready below. Load the map only when you want the geographic view. It uses additional data.

Basemap: OpenFreeMap, © OpenStreetMap contributors. Routes and stops: this agency's GTFS feed.

  • 1 (gray)
  • 10 (red)
  • 100 (red)
  • 103 (gray)
  • 106 (gray)
  • 108 (gray)
  • 11 (gray)
  • 111 (gray)
  • 111A (gray)
  • 112 (gray)
  • 115 (gray)
  • 119 (gray)
  • 12 (green)
  • 120 (red)
  • 121 (red)
  • 124 (gray)
  • 125 (red)
  • 126 (gray)
  • 130 (gray)
  • 134 (red)
  • 135 (red)
  • 136 (red)
  • 143 (red)
  • 146 (red)
  • 147 (red)
  • 148 (red)
  • 15 (gray)
  • 151 (gray)
  • 152 (gray)
  • 155 (gray)
  • 156 (gray)
  • 157 (gray)
  • 165 (gray)
  • 169 (gray)
  • 171 (gray)
  • 172 (gray)
  • 18 (gray)
  • 192 (gray)
  • 2 (red)
  • 20 (green)
  • 201 (gray)
  • 206 (gray)
  • 21 (gray)
  • 22 (gray)
  • 24 (gray)
  • 26 (red)
  • 28 (gray)
  • 29 (gray)
  • 3 (gray)
  • 30 (gray)
  • 31 (gray)
  • 34 (green)
  • 35 (gray)
  • 36 (gray)
  • 37 (gray)
  • 39 (gray)
  • 4 (green)
  • 43 (gray)
  • 44 (gray)
  • 47 (green)
  • 48 (gray)
  • 49 (green)
  • 49B (gray)
  • 50 (gray)
  • 51 (gray)
  • 52 (gray)
  • 52A (gray)
  • 53 (green)
  • 53A (gray)
  • 54 (green)
  • 54A (gray)
  • 54B (gray)
  • 55 (green)
  • 55A (gray)
  • 55N (gray)
  • 56 (gray)
  • 57 (gray)
  • 59 (gray)
  • 6 (red)
  • 60 (green)
  • 62 (gray)
  • 62H (gray)
  • 63 (green)
  • 63W (gray)
  • 65 (gray)
  • 66 (green)
  • 67 (gray)
  • 68 (gray)
  • 7 (gray)
  • 70 (gray)
  • 71 (gray)
  • 72 (green)
  • 73 (gray)
  • 74 (gray)
  • 75 (gray)
  • 76 (gray)
  • 77 (green)
  • 78 (gray)
  • 79 (green)
  • 8 (gray)
  • 80 (gray)
  • 81 (green)
  • 81W (gray)
  • 82 (green)
  • 84 (gray)
  • 85 (gray)
  • 85A (gray)
  • 86 (gray)
  • 87 (gray)
  • 88 (gray)
  • 8A (gray)
  • 9 (green)
  • 90 (gray)
  • 91 (gray)
  • 92 (gray)
  • 93 (gray)
  • 94 (gray)
  • 95 (green)
  • 96 (gray)
  • 97 (gray)
  • Blue Line (teal)
  • Brown Line (brown)
  • Green Line (green)
  • J14 (teal)
  • N5 (gray)
  • Orange Line (red)
  • Purple Line (purple)
  • Pink Line (pink)
  • Red Line (red)
  • X4 (red)
  • X49 (red)
  • X9 (red)
  • Yellow Line (yellow)
Routes in Chicago Transit Authority (CTA)'s feed
RouteTypeLine color
1 Bronzeville/Union StationBusgray
10 Obama Presidential Center/Museum of Science & Industry ExpressBusred
100 Jeffery Manor ExpressBusred
103 West 103rdBusgray
106 East 103rdBusgray
108 Halsted/95thBusgray
11 LincolnBusgray
111 111th/King DriveBusgray
111A Pullman ShuttleBusgray
112 Vincennes/111thBusgray
115 Pullman/115thBusgray
119 Michigan/119thBusgray
12 RooseveltBusgreen
120 Ogilvie/Streeterville ExpressBusred
121 Union/Streeterville ExpressBusred
124 Navy PierBusgray
125 Water Tower ExpressBusred
126 JacksonBusgray
130 Museum CampusBusgray
134 Stockton/LaSalle ExpressBusred
135 Clarendon/LaSalle ExpressBusred
136 Sheridan/LaSalle ExpressBusred
143 Stockton/Michigan ExpressBusred
146 Inner Lake Shore/Michigan ExpressBusred
147 Outer DuSable Lake Shore ExpressBusred
148 Clarendon/Michigan ExpressBusred
15 Jeffery LocalBusgray
151 SheridanBusgray
152 AddisonBusgray
155 DevonBusgray
156 LaSalleBusgray
157 Streeterville/TaylorBusgray
165 West 65thBusgray
169 69th/UPS ExpressBusgray
171 U. of Chicago/Hyde ParkBusgray
172 U. of Chicago/KenwoodBusgray
18 16th/18thBusgray
192 University of Chicago Hospitals ExpressBusgray
2 Hyde Park ExpressBusred
20 MadisonBusgreen
201 Central/RidgeBusgray
206 Evanston CirculatorBusgray
21 CermakBusgray
22 ClarkBusgray
24 WentworthBusgray
26 South Shore ExpressBusred
28 Stony IslandBusgray
29 StateBusgray
3 King DriveBusgray
30 South ChicagoBusgray
31 31stBusgray
34 South MichiganBusgreen
35 31st/35thBusgray
36 BroadwayBusgray
37 SedgwickBusgray
39 PershingBusgray
4 Cottage GroveBusgreen
43 43rdBusgray
44 Wallace/RacineBusgray
47 47thBusgreen
48 South DamenBusgray
49 WesternBusgreen
49B North WesternBusgray
50 DamenBusgray
51 51stBusgray
52 KedzieBusgray
52A South KedzieBusgray
53 PulaskiBusgreen
53A South PulaskiBusgray
54 CiceroBusgreen
54A North Cicero/Skokie Blvd.Busgray
54B South CiceroBusgray
55 GarfieldBusgreen
55A 55th/AustinBusgray
55N 55th/NarragansettBusgray
56 MilwaukeeBusgray
57 LaramieBusgray
59 59th/61stBusgray
6 Jackson Park ExpressBusred
60 Blue Island/26thBusgreen
62 ArcherBusgray
62H Archer/HarlemBusgray
63 63rdBusgreen
63W West 63rdBusgray
65 GrandBusgray
66 ChicagoBusgreen
67 67th/69th/71stBusgray
68 Northwest HighwayBusgray
7 HarrisonBusgray
70 DivisionBusgray
71 71st/South ShoreBusgray
72 NorthBusgreen
73 ArmitageBusgray
74 FullertonBusgray
75 74th/75thBusgray
76 DiverseyBusgray
77 BelmontBusgreen
78 MontroseBusgray
79 79thBusgreen
8 HalstedBusgray
80 Irving ParkBusgray
81 LawrenceBusgreen
81W West LawrenceBusgray
82 Kimball/HomanBusgreen
84 PetersonBusgray
85 CentralBusgray
85A North CentralBusgray
86 Narragansett/RidgelandBusgray
87 87thBusgray
88 HigginsBusgray
8A South HalstedBusgray
9 AshlandBusgreen
90 HarlemBusgray
91 AustinBusgray
92 FosterBusgray
93 California/DodgeBusgray
94 CaliforniaBusgray
95 95thBusgreen
96 LuntBusgray
97 SkokieBusgray
Blue LineSubway / metroteal
Brown LineSubway / metrobrown
Green LineSubway / metrogreen
J14 Jeffery JumpBusteal
N5 South Shore Night BusBusgray
Orange LineSubway / metrored
Purple LineSubway / metropurple
Pink LineSubway / metropink
Red LineSubway / metrored
X4 Cottage Grove ExpressBusred
X49 Western ExpressBusred
X9 Ashland ExpressBusred
Yellow LineSubway / metroyellow
List every stop
  • Jackson & Austin Terminal
  • Jackson & Leamington
  • 1900 W Van Buren
  • North Ave & Nordica
  • Kedzie & 77th Street
  • Kedzie & 72nd Street
  • Kedzie & Marquette Rd
  • Kedzie & 66th Street
  • Kedzie & 65th Street
  • Kedzie & 64th Street
  • North Ave & Neva
  • Kedzie & 64th Street
  • Kedzie & 65th Street
  • Kedzie & 66th Street
  • Kedzie & Marquette Rd
  • Kedzie & 71st Street
  • Kedzie & 72nd Street
  • Kedzie & 73rd Street
  • Harlem & North Ave
  • Kedzie & 77th Street
  • Kedzie & 78th Street
  • Kedzie & 79th Street
  • Kedzie & 80th Street
  • Kedzie & 81st Street
  • Kedzie & 82nd Street
  • Kedzie & 83rd Street
  • Kedzie & 84th Street
  • Kedzie & 85th Street
  • 8600 S Kedzie
  • Kedzie & 87th Street
  • Kedzie & 88th Street
  • Kedzie & 89th Street
  • Kedzie & 90th Street
  • Kedzie & 91st Street
  • Kedzie & 92nd Street
  • Kedzie & 93rd Street
  • Kedzie & 94th Street
  • Kedzie & 95th Street
  • Kedzie & 96th Street
  • Harlem & Wabansia
  • Kedzie & 97th Street
  • Kedzie & 98th Street
  • Kedzie & 99th Street
  • Kedzie & 100th Street
  • Kedzie & 101st Street
  • Kedzie & 102nd Street
  • Kedzie & 103rd Street
  • Kedzie & 104th Street
  • Kedzie & 105th Street
  • Kedzie & 106th Street
  • Wabansia & Neva
  • Kedzie & 108th Street
  • Kedzie & 109th Street
  • Kedzie & 110th Street
  • Kedzie & 111th Street
  • Kedzie & 112th Street
  • Kedzie & 113th Street
  • Kedzie & 114th Street
  • Kedzie & 115th Street
  • 115th Street & Spaulding
  • 115th Street & Homan
  • 115th Street & St. Louis
  • 115th Street & Central Park
  • 115th Street & Lawndale
  • 115th Street & Hamlin
  • 115th Street & Springfield Terminal
  • 67th Street & Oglesby Terminal
  • 67th Street & Stony Island
  • 67th Street & Blackstone
  • 67th Street & Dorchester
  • 67th Street & Kenwood
  • 67th Street & Kimbark
  • 67th Street & Woodlawn
  • 67th Street & Minerva
  • 67th Street & University
  • 67th Street & Greenwood
  • 67th Street & Ellis
  • 67th Street & Ingleside
  • 67th Street & Drexel
  • 67th Street & Cottage Grove
  • 67th Street & Langley
  • 67th Street & St. Lawrence
  • Rhodes & 67th Street
  • Rhodes & 68th Street
  • Keefe & South Chicago
  • 69th Street & Perry
  • 69th Street & Wentworth
  • 69th Street & Princeton
  • 69th Street & Harvard
  • 69th Street & Stewart
  • 69th Street & Normal
  • 69th Street & Lowe
  • 69th Street & Union
  • 69th Street & Halsted
  • 69th Street & Peoria
  • 69th Street & Morgan
  • Van Buren & Damen
  • 69th Street & Aberdeen
  • 69th Street & Racine
  • 69th Street & Throop
  • 69th Street & Loomis
  • 69th Street & Laflin
  • 69th Street & Ashland
  • 69th Street & Paulina
  • Howard & Sheridan
  • 69th Street & Wood
  • 69th Street & Wolcott
  • 69th Street & Damen
  • 69th Street & Hoyne
  • 69th Street & Bell
  • 69th Street & Oakley
  • Western & 69th Street
  • 71st Street & Campbell
  • 71st Street & Rockwell
  • Sheridan & Birchwood
  • 71st Street & California
  • 71st Street & Spaulding
  • 71st Street & Homan
  • 71st Street & St. Louis
  • 71st Street & Central Park
  • 71st Street & Hamlin
  • 71st Street & Springfield
  • 71st Street & Pulaski
  • 71st Street & Springfield
  • 71st Street & Hamlin
  • 71st Street & Lawndale
  • 3600 W 71st Street
  • 71st Street & St. Louis
  • 71st Street & Homan
  • 71st Street & Spaulding
  • Sheridan & Jarvis
  • 71st Street & Kedzie
  • 71st Street & Albany
  • 71st Street & Washtenaw
  • 71st Street & Rockwell
  • 71st Street & Campbell
  • Western & 71st Street
  • 69th Street & Oakley
  • 69th Street & Bell
  • Sheridan & Sherwin
  • 69th Street & Hoyne
  • 69th Street & Damen
  • 69th Street & Wolcott
  • 69th Street & Wood
  • 69th Street & Paulina
  • 69th Street & Laflin
  • Sheridan & Chase
  • 69th Street & Loomis
  • 69th Street & Throop
  • 69th Street & Racine
  • 69th Street & Aberdeen
  • 69th Street & Morgan
  • 69th Street & Peoria
  • 69th Street & Halsted
  • 69th Street & Union
  • Sheridan & Touhy
  • 69th Street & Lowe
  • 69th Street & Normal
  • 69th Street & Stewart
  • 69th Street & Harvard
  • 69th Street & Princeton
  • 69th Street & Wentworth
  • 69th Street & Perry
  • 69th Red Line Station
  • 69th Street & State
  • Sheridan & Estes
  • Rhodes & 68th Street
  • Rhodes & 67th Street
  • 67th Street & St. Lawrence
  • 67th Street & Langley
  • 67th Street & Cottage Grove
  • 67th Street & Drexel
  • 67th Street & Ingleside
  • 67th Street & Ellis
  • 67th Street & Greenwood
  • 67th Street & University
  • 67th Street & Minerva
  • 67th Street & Woodlawn
  • 67th Street & Kimbark
  • 67th Street & Kenwood
  • 67th Street & Dorchester
  • 67th Street & Blackstone
  • 67th Street & Stony Island
  • La Rabida Hospital
  • Cicero & Pensacola Terminal
  • Sheridan & Lunt
  • Cicero & Cullom
  • Cicero & Belle Plaine
  • Cicero & Irving Park/Milwaukee
  • Cicero & Byron
  • Cicero & Grace
  • Cicero & Waveland
  • Cicero & Addison
  • Cicero & Cornelia
  • Sheridan & Morse
  • Cicero & Roscoe
  • Cicero & School
  • Cicero & George
  • Cicero & Diversey
  • Cicero & Wrightwood
  • Cicero & Dickens
  • Cicero & Armitage
  • Cicero & Cortland
  • Cicero & Grand
  • Cicero & Wabansia
  • Cicero & North Ave
  • Cicero & Le Moyne
  • Sheridan & Pratt
  • Cicero & Hirsch
  • Cicero & Potomac
  • Cicero & Thomas
  • Cicero & Iowa
  • Cicero & Huron
  • Cicero & Hubbard
  • Cicero & Lake (Green Line)
  • Cicero & Adams
  • Cicero & Jackson
  • Cicero & Van Buren
  • Sheridan & North Shore
  • Cicero & Congress
  • Cicero & Harrison
  • Cicero Blue Line Station
  • Cicero & Polk
  • Cicero & Fifth Avenue
  • Cicero & Roosevelt
  • Cicero & 13th Street
  • Cicero & 14th Street
  • Cicero & 15th Street
  • Cicero & 18th Street
  • Cicero & 21st Place (Pink Line)
  • Cicero & Cermak
  • Cicero & 24th Place Terminal
  • Sheridan & Loyola (Red Line)
  • Cicero & Cermak (Pink Line)
  • Cicero & 21st Street
  • Cicero & 18th Street
  • Cicero & 16th Street
  • Cicero & 15th Street
  • Cicero & 14th Street
  • Sheridan & Arthur
  • Cicero & 13th Street
  • Cicero & Fifth Avenue
  • Cicero & Polk
  • Cicero & Lexington (Blue Line)
  • Cicero & Harrison
  • Cicero & Congress Parkway
  • Cicero & Van Buren
  • Sheridan & Broadway/Devon
  • Cicero & Madison
  • Cicero & Maypole
  • and 10875 more (see the full list on the map or in the GeoJSON)

Over time

Overall score across the last 4 checks — down 0.5 since 2026-08-01.

2026-07-25: 52.22026-07-30: 52.22026-08-01: 52.22026-08-02: 51.7
Show the numbers
Overall score by check, with the change from the previous check
CheckScoreChange
2026-07-2552.2 first check
2026-07-3052.2 no change
2026-08-0152.2 no change
2026-08-0251.7 down 0.5

What changed since your last check

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

What changed in this feed

Overall score fell 0.5 points since 2026-08-01.

Same feed file as 2026-08-01; the published zip did not change.

Subscribe to this feed’s changes (Atom) to hear about grade drops in a reader, with no sign-up.

Everything we checked

17 findings, ordered by severity.

Show every finding
  • Error96894 instances

    Equal shape distance diff coordinates (flagged by the MobilityData validator).

    See the linked rule for what this affects.

    Fix: 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. (Varies.)

    Finding code: equal_shape_distance_diff_coordinates · See MobilityData GTFS Validator rules (opens the validator rules on an external site)

  • Warning94667 instances

    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.

    Fix: 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. (Usually one value per route pattern in your scheduling source.)

    Finding code: scorecard_missing_headsigns · Read the fix guide · See GTFS Best Practices (opens GTFS Best Practices on an external site)

  • Warning1033 instances

    Equal shape distance diff coordinates distance below threshold (flagged by the MobilityData validator).

    See the linked rule for what this affects.

    Fix: 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. (Varies.)

    Finding code: equal_shape_distance_diff_coordinates_distance_below_threshold · See MobilityData GTFS Validator rules (opens the validator rules on an external site)

  • Warning348 instances

    Some route lines list the same point twice in a row.

    Repeated points don't hurt riders, but they can skew distance math and hint at a shaky export.

    Fix: Turn on shape cleanup in your export tool, or drop the repeated points from shapes.txt. (Usually one export setting.)

    Finding code: equal_shape_distance_same_coordinates · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)

  • Warning37 instances

    Some service calendars in the feed have already ended.

    Expired calendars are dead weight and can hide real schedule problems from your staff and vendors.

    Fix: Remove past service periods the next time you export the feed. (One setting in most export tools.)

    Finding code: expired_calendar · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)

  • Warning36 instances

    Some rider-facing names are in ALL CAPS or all lowercase.

    ALL-CAPS stop and headsign names are harder to read in apps and are read awkwardly by screen readers.

    Fix: Use mixed case for stop names and headsigns (e.g. 'Main St & 2nd Ave', not 'MAIN ST & 2ND AVE'). (Often a bulk fix in your scheduling software.)

    Finding code: mixed_case_recommended_field · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)

  • Warning11 instances

    Some stops sit far from the route line, going by the feed's own distance values.

    Trip planners may draw the route down the wrong path or point riders to the wrong boarding location.

    Fix: Check the flagged stops' shape_dist_traveled against the route shape, and re-generate it on export if they disagree. (Usually an export-tool fix, not hand editing.)

    Finding code: stop_too_far_from_shape_using_user_distance · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)

  • Warning6 instances

    Some stops sit far from the route line they belong to.

    Trip planners may draw the transit vehicle route through the wrong path or point riders to the wrong boarding location.

    Fix: Check the flagged stops' coordinates and the route shape in your scheduling software; re-snap whichever is misplaced. (A few minutes per flagged stop.)

    Finding code: stop_too_far_from_shape · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)

  • Warning3 instances

    Some values have extra spaces at the start or end.

    A stray space can break a match, so a stop or route may fail to link across files.

    Fix: Trim leading and trailing spaces on export. The scorecard's auto-fixed copy already does this. (Usually one export setting.)

    Finding code: leading_or_trailing_whitespaces · See MobilityData GTFS Validator rules (opens the validator rules on an external site)

  • Warning1 instance

    A file GTFS asks for (usually feed_info.txt) is missing.

    feed_info.txt tells apps who publishes the feed and when it expires; without it nobody is warned before data goes stale.

    Fix: Add feed_info.txt with publisher name, URL, language, and feed_start_date/feed_end_date. (One small file, set once in export settings.)

    Finding code: missing_recommended_file · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)

  • Warning1 instance

    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.

    Fix: Add feed_info.txt with feed_start_date and feed_end_date to your export. (Two fields, set once in export settings.)

    Finding code: scorecard_missing_feed_info_dates · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)

  • Warning1 instance

    The feed contains no fare information.

    Riders see 'fare unknown' in trip planners and can't budget their trip; visitors are most affected.

    Fix: 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. (A small file for most flat-fare systems.)

    Finding code: scorecard_no_fare_data · Read the fix guide · See GTFS Best Practices (opens GTFS Best Practices on an external site)

  • Warning1 instance

    This feed models stations or entrances but has no pathways.txt.

    Trip planners can't guide riders through the station, and there is no step-free route information for wheelchair users.

    Fix: Add pathways.txt connecting entrances, platforms, and any elevators, with a level for each. (Worth it for multi-level or large stations; flat stops don't need it.)

    Finding code: scorecard_station_no_pathways · Read the fix guide · See GTFS Schedule reference (opens the GTFS Schedule reference on an external site)

  • Info90440 instances

    Unsorted stop times (flagged by the MobilityData validator).

    See the linked rule for what this affects.

    Fix: Review the rule documentation for 'unsorted_stop_times' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)

    Finding code: unsorted_stop_times · See MobilityData GTFS Validator rules (opens the validator rules on an external site)

  • Info2 instances

    Some files contain columns that are not part of the GTFS spec.

    Harmless to riders, but apps ignore these columns and they can hide typos in real column names.

    Fix: Check the flagged column names for misspellings of standard GTFS fields; remove them if they are vendor extras. (A quick look at the flagged files.)

    Finding code: unknown_column · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)

  • Info1 instance

    The feed includes a file that is not part of the GTFS spec.

    Apps ignore files they don't know, and a stray file can hide a misspelled standard file name.

    Fix: Check the flagged file name for a typo of a standard GTFS file. Remove it if it is a vendor extra. (A quick look at the flagged file.)

    Finding code: unknown_file · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)

  • Info1 instance

    feed_info.txt has no technical contact (feed_contact_email or feed_contact_url).

    Trip-planning apps and regional data coordinators have nobody to email when they spot a problem with your feed, so problems linger.

    Fix: Add feed_contact_email to feed_info.txt. (One field.)

    Finding code: scorecard_no_feed_contact · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)

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 your 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.
shapes.txt covers your trips Ready
All 94667 trips have a shape in shapes.txt.

In plain words: if you report to the federal transit database, you have to publish a working, up-to-date feed, provide a stable agency_id for each represented reporter, and confirm the feed and P-50 crosswalk each year. This box is a heads-up; your filings are the official check.

A readiness signal mapping this feed to the FTA National Transit Database GTFS requirement (Report Year 2023 onward: a public, valid, current feed, certified annually on the D-10). For RY2026, each represented reporter needs a stable agency_id, unique within the feed and crosswalked to its five-digit NTD ID on P-50; the values do not need to be equal. FTA also requires shapes.txt in the published GTFS: Full Reporters from Report Year 2025, and Reduced, Rural, and Tribal Reporters from Report Year 2026. Not an official determination; your certification is the official check.

Conformance mark Not yet

This feed is close to the conformance mark. 1 validator error to resolve.

Valid Not yet
1 validator error to resolve.
Current Met
Service data covers the next 59 days.
Accessible Met
States wheelchair access on 100% of stops and 100% of trips.

In plain words: earn this mark when your feed passes validation, has not expired, and says whether nearly every stop and trip is wheelchair accessible.

A pass credential for a feed that is valid, current, and states wheelchair access on nearly every stop and trip. Accessibility here measures what the feed publishes, not whether a stop is physically usable. How the conformance mark works.

Clears the Google and Apple Maps four-week coverage bar. This feed has 59 days of service ahead, clearing the four-week (28-day) window Maps asks for. The feed also carries 96894 validator errors, the other thing Maps checks at onboarding; the findings below name each fix.

How this agency maps to the standards

The scorecard is a data-quality lens, not a compliance determination. Its universal references describe good GTFS and useful rider information. Useful references here are GTFS Schedule Best Practices, GTFS-Realtime Best Practices, MobilityData grading scheme, Google Transit publication guidance, FTA National Transit Database GTFS requirement. Read the full standards crosswalk.

Correctness 26 / 100
GTFS Schedule best practices, checked by the MobilityData validator. MobilityData grading covers stop locations, route names, and colors. Google Transit requires a feed to pass validation for publication. FTA NTD readiness also checks that the published feed is valid.
Freshness 83 / 100
GTFS Schedule best practices call for a dataset that stays current. An expired calendar can remove service from Google Transit and other rider trip planners. FTA NTD readiness also checks that the published feed is current.
Rider experience 62 / 100
GTFS Best Practices for rider-facing fields. MobilityData grading covers stop names and headsigns.
Realtime quality Not yet published
GTFS-Realtime best practices: a stable URL, high uptime, and frequent updates.

Show your grade

Put a badge on your agency site or feed README. It updates after each completed scoring check and links back to this scorecard.

Chicago Transit Authority (CTA) GTFS data quality grade: F

Prefer a shields.io style? Point a dynamic endpoint badge at the published badge.json.

Cite this record

This page updates on every check. The record below does not: it is the dated file this grade came from, published at https://gtfsscorecard.org/data/artifacts/chicago-transit-authority-cta/2026-08-02.json and never overwritten, pinning the grade, category scores, rubric version, validator version, reader archive profile, and the scored feed's sha256 as they stood on 2026-08-02. Use it in a board packet, a regulatory filing, or a research citation instead of linking the live page, whose content will differ on your next visit.

Citing the tool itself rather than one agency's record? Use the repo's CITATION.cff.