Feed status · checked 2026-08-01
Greater Cleveland Regional Transit Authority
Based on the feed this agency publishes
Service mode Tram + Metro + Bus
unchanged since 2026-07-31
Catalogued in Ohio.
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 76 minutes ago; last changed 4 days ago.
Measured 4 of 4 score categories from the agency's own feed.
How we measured this
Confidence in this measurement: high.
- All four score categories were measured this run.
- Realtime was sampled in one bounded window of 9 snapshots.
- 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
Check the trip updates endpoint with your AVL vendor; it should return a fresh GTFS-Realtime protobuf on every request.
The trip updates realtime feed failed during sampling. When this feed is down, riders see scheduled times presented as if they were live.
⏱ Usually a vendor support ticket.worth about +33 points in its category
Check the vehicle positions endpoint with your AVL vendor; it should return a fresh GTFS-Realtime protobuf on every request.
The vehicle positions realtime feed failed during sampling. When this feed is down, riders see scheduled times presented as if they were live.
⏱ Usually a vendor support ticket.worth about +33 points in its category
Check the service alerts endpoint with your AVL vendor; it should return a fresh GTFS-Realtime protobuf on every request.
The service alerts realtime feed failed during sampling. When this feed is down, riders see scheduled times presented as if they were live.
⏱ Usually a vendor support ticket.worth about +33 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
- The trip updates realtime feed failed during sampling.
- Next action
- Check the trip updates endpoint with your AVL vendor; it should return a fresh GTFS-Realtime protobuf on every request.
- 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
- Feed evidence
- The vehicle positions realtime feed failed during sampling.
- Next action
- Check the vehicle positions endpoint with your AVL vendor; it should return a fresh GTFS-Realtime protobuf on every request.
- 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
- Feed evidence
- The service alerts realtime feed failed during sampling.
- Next action
- Check the service alerts endpoint with your AVL vendor; it should return a fresh GTFS-Realtime protobuf on every request.
- 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.
Check the trip updates endpoint with your AVL vendor; it should return a fresh GTFS-Realtime protobuf on every request. · 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. See this feed's finding-clearance log.
Check the vehicle positions endpoint with your AVL vendor; it should return a fresh GTFS-Realtime protobuf on every request. · 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. See this feed's finding-clearance log.
Check the service alerts endpoint with your AVL vendor; it should return a fresh GTFS-Realtime protobuf on every request. · 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. See this feed's finding-clearance log.
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 126 days.
- Published accessibility data
- Accessibility information is stated for 0% of stops and 0% of trips. This measures published data, not whether stops or vehicles are physically usable.
- Fare information
- Fare information is published using GTFS Fares v2.
- Realtime information
- No realtime feed was reachable during sampling.
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
The MobilityData validator flagged 11 kinds of issue across 31558 instances (522 error, 31029 warning, 7 informational).
Service data covers the next 126 days.
0% of stops state wheelchair accessibility (0% marked accessible, 0% marked not accessible). This measures what the feed publishes, not whether a stop is physically usable. Fare data is published.
0% of stops state accessibility (0% marked accessible). Reflects what the feed states, not verified physical usability.
2 accessibility depth signals
5429 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set ("COLUMBUS ST & BROADWAY", "BROOKPARK RD & W COMMERCE PKWY", "BROADWAY & BOOTH AV", 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.
Fares are applied to trips.
Sampled 9 times outside service hours: 0 of 3 configured feeds healthy; vehicle position plausibility was not measurable.
Routes and stops
Each route is drawn once, using the longest shape its trips follow; stops are the dots.
This feed has 5631 stops.
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 (black)
- 10 (black)
- 11 (black)
- 14-14A (black)
- 15 (black)
- 16 (black)
- 18 (black)
- 19-19A-19B (black)
- 2 (black)
- 22 (black)
- 25 (black)
- 251 (black)
- 26-26A (black)
- 28-28A (black)
- 3 (black)
- 31 (black)
- 34 (black)
- 35 (black)
- 37 (black)
- 39 (black)
- 40 (black)
- 41-41F (black)
- 45 (black)
- 48 (black)
- 50 (black)
- 51-51A (black)
- 53-53A (black)
- 54 (black)
- 55-55B-55C (black)
- HL (gray)
- B-Line Trolley (yellow)
- RL (red)
- 66R (red)
- BL (teal)
- 67R (teal)
- GL (gray)
- 68R (gray)
- WL (teal)
- 7-7A (black)
- 71 (black)
- 77 (black)
- 78 (black)
- 8 (black)
- 83 (black)
- 86 (black)
- 9 (black)
- 90 (black)
- 94 (black)
| Route | Type | Line color |
|---|---|---|
| 1 St. Clair | Bus | black |
| 10 East 105–Lakeshore | Bus | black |
| 11 Quincy–Cedar | Bus | black |
| 14-14A Kinsman | Bus | black |
| 15 Union–Harvard | Bus | black |
| 16 East 55 | Bus | black |
| 18 West 98–Garfield | Bus | black |
| 19-19A-19B Broadway | Bus | black |
| 2 East 79 | Bus | black |
| 22 Lorain | Bus | black |
| 25 Madison–Clark | Bus | black |
| 251 Strongsville Park-N-Ride | Bus | black |
| 26-26A Detroit | Bus | black |
| 28-28A Euclid | Bus | black |
| 3 Superior | Bus | black |
| 31 St. Clair–Babbitt | Bus | black |
| 34 East 200–Green | Bus | black |
| 35 Lee Blvd.–East 123 | Bus | black |
| 37 Hayden–East 185 | Bus | black |
| 39 Lakeshore | Bus | black |
| 40 Lakeview–Lee | Bus | black |
| 41-41F Warrensville | Bus | black |
| 45 Ridge–Fulton | Bus | black |
| 48 East 131 | Bus | black |
| 50 East 116 | Bus | black |
| 51-51A MetroHealth Line | Bus | black |
| 53-53A MetroHealth Line–Broadview | Bus | black |
| 54 Brookpark–Rockside | Bus | black |
| 55-55B-55C Clifton | Bus | black |
| HL HealthLine | Bus | gray |
| B-Line Trolley | Bus | yellow |
| RL Red Line | Subway / metro | red |
| 66R Red Line Replacement Bus | Bus | red |
| BL Blue Line | Tram / light rail | teal |
| 67R Blue Line Replacement Bus | Bus | teal |
| GL Green Line | Tram / light rail | gray |
| 68R Green Line Replacement Bus | Bus | gray |
| WL Waterfront Line | Tram / light rail | teal |
| 7-7A Monticello | Bus | black |
| 71 Pearl–Tiedeman | Bus | black |
| 77 Brecksville | Bus | black |
| 78 West 117–Puritas | Bus | black |
| 8 Cedar–Buckeye | Bus | black |
| 83 Warren–West 130 | Bus | black |
| 86 Rocky River Dr.–Bagley | Bus | black |
| 9 Mayfield–Hough | Bus | black |
| 90 Broadway–Libby | Bus | black |
| 94 East 260–Richmond | Bus | black |
List every stop
- COLUMBUS ST & BROADWAY
- BROOKPARK RD & W COMMERCE PKWY
- BROADWAY & BOOTH AV
- EUCLID AV & E 100TH ST
- 10081 W RIDGEWOOD DR
- WASHINGTON AV & W 25TH ST
- CORLETT AV & E 131ST ST
- HARVARD AV & E 150TH ST
- HARVARD AV & ACCESS DR
- 19403 HARVARD AV
- HARVARD AV & E 150TH ST
- BROADWAY & MARBLE AV
- MILES AV & E 135TH ST
- PROSPECT AV & ONTARIO ST
- HARVARD AV & LEE RD
- MILES AV & DANDRIDGE DR
- MILES AV & DANDRIDGE DR
- MILES AV & E 146TH ST
- 1028 PROSPECT AV E
- 1027 SUPERIOR AV E
- MILES AV & E 111TH ST
- W 25TH ST & LORAIN AV
- HARVARD AV & E 71ST ST
- KINSMAN RD & E 104TH ST
- 10335 DETROIT AV
- 10335 DETROIT AV
- SEVILLE RD & JOHNSTON PKWY
- QUINCY AV & WOODHILL RD
- SEVILLE RD & JOHNSTON PKWY
- QUINCY AV & E 85TH ST
- 10603 DETROIT AV
- 10603 DETROIT AV
- BROADVIEW RD & NORTH AV
- BROOKPARK RD & W 33RD LOOP
- BROOKPARK RD & TIEDEMAN RD
- RICHMOND RD & ROBERT BISHOP DR
- ST. CLAIR AV & E 106TH ST
- QUINCY AV & E 85TH ST
- KINSMAN RD & MARTIN LUTHER KING JR DR
- GREAT NORTHERN BLVD & BROOKPARK RD
- MILES AV & E ELMARGE RD
- GREAT NORTHERN BLVD & COUNTRY CLUB BLVD
- GREAT NORTHERN BLVD & COUNTRY CLUB BLVD
- BRUSH RD & METRO DR
- 10705 LORAIN AV
- 1450 E 260TH ST
- BRUSH RD & METRO DR
- BRUSH RD & MULBERRY CIR
- MONTICELLO BLVD & MONTFORD RD
- 1424 SOM CENTER RD
- WILSON MILLS RD & STANWELL DR
- MONTICELLO BLVD & MONTFORD RD
- 3000 QUIGLEY RD
- 3000 QUIGLEY RD
- HARVARD AV & WARRENSVILLE CTR RD
- TIEDEMAN RD & MEMPHIS AV
- LORAIN RD & W 210TH ST
- BRUSH RD & MULBERRY CIR
- BUCKEYE RD & MARTIN LUTHER KING DR
- LAKEVIEW RD & CHESTERFIELD AV
- RICHMOND RD & FARNHURST RD
- ST. CLAIR AV & E 112TH ST
- RICHMOND RD & EASTOVER RD
- RICHMOND RD & EASTOVER RD
- RICHMOND RD & KAREN ISLE DR
- EUCLID AV & HERITAGE DR
- 30400 SOLON RD
- SOLON RD & CAMP INDUSTRIAL PKWY
- 11109 W PLEASANT VALLEY RD
- 31100 SOLON RD
- 30815 SOLON RD
- 33000 SOLON RD
- ORANGE AV & E 30TH ST
- 11216 STOKES BLVD
- PEARL RD & IDLEWOOD TRAIL
- 26900 GEORGE ZEIGER DR (CLEVELAND CLINIC)
- CEDAR RD & GEORGE ZEIGER DR
- FAIRMOUNT BLVD & BRENTWOOD RD
- BROOKPARK RD & CHEVROLET BLVD
- BUCKEYE RD & E 114TH ST
- ORANGE AV & E 14TH ST
- HEPBURN DR & BAGLEY RD
- 18344 BAGLEY RD
- HEPBURN RD & JEFFERSON PARK
- JEFFERSON PARK RD & ENGLE RD
- W PLEASANT VALLEY RD & E BICENTENNIAL DR
- JEFFERSON PARK RD & ENGLE RD
- 18660 BAGLEY RD
- LAKESHORE BLVD & CORNWALL RD
- MONTICELLO BLVD & RICHMOND RD
- DETROIT AV & HIRD AV
- EMERY RD & RENAISSANCE PKWY
- 11800 BROOKPARK RD
- 11801 LAKESHORE BLVD
- 11801 LAKESHORE BLVD
- FLEET AV & E 71ST ST
- 11820 EDGEWATER DR
- 11843 EDGEWATER DR
- CLIFTON BLVD & FRY AV
- MADISON AV & W 112TH ST
- PEARL RD & PROGRESS DR
- MADISON AV & W 112TH ST
- 13936 CEDAR RD
- 12000 FAIRHILL RD
- 12000 FAIRHILL RD
- 13939 CEDAR RD
- WARREN RD & EMILY AV
- S GREEN RD & FERNWOOD DR
- S GREEN RD & E CARROLL BLVD
- S GREEN RD & BIRCHWOLD RD
- S GREEN RD & BIRCHWOLD RD
- S GREEN RD & FERNWOOD DR
- OPPORTUNITY CORRIDOR & E 79TH ST
- OPPORTUNITY CORRIDOR & E 79TH ST
- RIDGE RD & FLOWERDALE AV
- 1240 WARREN RD
- W 140TH ST & TYLER AV
- BUCKEYE RD & E 124TH ST
- SOUTHGATE TRANSIT CENTER STOP #4
- 1245 WARREN RD
- RIDGE RD & WEFEL AV
- RIDGE RD & WEFEL AV
- EDGEWATER DR & COVE DR
- W PLEASANT VALLEY RD & PARMA PARK BLVD
- W PLEASANT VALLEY RD & PARMA PARK BLVD
- 12509 ST. CLAIR AV
- 12518 LAKESHORE BLVD
- 12521 LAKESHORE BLVD
- 12543 LAKE AV
- 12547 LAKE AV
- LAKESIDE AVE & CONVENTION CENTER (W MALL DR)
- 1 SEVERANCE CIR
- HURON RD & PROSPECT AV
- HURON RD E & E 4TH ST
- FULTON RD & PARK DR
- MT SINAI DR & E 105TH ST
- E 116TH ST & CROMWELL AV
- TRANSPORTATION BLVD & WESTBOUND I-480
- 12720 LAKESHORE BLVD
- 8888 BROOKPARK RD
- 6767 BROOKPARK RD
- 8888 BROOKPARK RD
- BROOKPARK RD & W 139TH ST
- NOBLE RD & YELLOWSTONE RD
- BROOKPARK RD & ROCKY RIVER DR
- LORAIN AV & OLD LORAIN RD
- 13200 PEARL RD
- ST. CLAIR AV & E 129TH ST
- 12910 LAKESHORE BLVD
- MT SINAI DR & E 105TH ST
- E 200TH ST & SHAWNEE AV
- GREEN RD & BLANDFORD RD
- GOLD COAST LN LOOP
- GREEN RD & PRASSE RD
- CORLETT AV & CORLETT LOOP
- PEARL RD & ZVERINA LN
- 13003 LAKESHORE BLVD
- E 200TH ST & MONTEREY AV
- 1484 CHARDON RD
- MILES AV & E 135TH ST
- 13211 LAKESHORE BLVD
- 13211 LAKESHORE BLVD
- 13300 BROOKPARK RD
- 1365 CHARDON RD
- 13405 LAKESHORE BLVD
- KINSMAN RD & E 135TH ST
- 13478 LAKESHORE BLVD
- ST. CLAIR AV & WOODWORTH RD
- SLOANE AV & EDANOLA AV
- SLOANE AV & DETROIT RD
- CLIFTON BLVD & BUNTS RD
- 14200 SUPERIOR RD
- TURNEY RD & VALLEY RANCH DR
- 14092 PEARL RD
- 14583 TURNEY RD
- 14600 TURNEY RD (ST. MARTIN'S CHURCH)
- 1470 WARREN RD
- 1476 WARRENSVILLE CTR RD
- 1491 CHARDON RD
- 15299 BAGLEY RD
- 15299 BAGLEY RD
- 15300 HOWE RD
- ST. CLAIR AV & E 153RD ST LOOP STOP 2
- W 25TH ST & FRANKLIN AV
- LORAIN AV & TRISKETT RD
- 15650 PEARL RD
- 15653 PEARL RD
- 15655 BROOKPARK RD
- 15708 BROOKPARK RD
- 15745 EAST BAGLEY RD
- 15802 SEVILLE RD
- PEARL RD & KNOWLTON PKWY
- BROADWAY & MAPLE HEIGHTS BLVD
- 15700 EAST BAGLEY RD
- 1601 WARREN RD
- E 105TH ST & MAGNOLIA DR
- BROOKPARK RD & W 161ST ST
- 16151 LAKESHORE BLVD
- ST. CLAIR AV & HOLMES AV
- ST. CLAIR AV & E. 166TH ST
- 16608 LAKESHORE BLVD
- 16700 ST. CLAIR AV
- CHAGRIN BLVD & WINSLOW CT
- 16807 ST. CLAIR AV
- CHAGRIN BLVD & WINSLOW CT
- 17218 TARKINGTON AV
- 17000 TARKINGTON AV
- MADISON AV & WINTON AV
- 17201 MILES AV
- CLIFTON BLVD & GRANGER AV
- 17439 LORAIN AV
- BAGLEY RD & I-71
- 17515 S MILES RD
- 17570 LAKESHORE BLVD
- LAKESHORE BLVD & WILDWOOD LN
- LAKESHORE BLVD & MARCELLA RD
- 17700 ST. CLAIR AV
- 17712 PURITAS AV
- 17800 ST. CLAIR AV
- HARVARD AV & LEE HEIGHTS BLVD
- MILES AV & LEE HTS BLVD
- ST. CLAIR AV & E. 179TH ST
- 18200 LORAIN AV
- 18013 PURITAS AV
- EUCLID AV & CLIFFVIEW RD
- 18120 PURITAS AV
- SLOANE AV & W CLIFTON BLVD
- 18211 LORAIN AV
- ST. CLAIR AV & MELVILLE RD
- HARVARD AV E & E 183RD ST
- DETROIT AV & MAILE AV
- SLOANE AV & PARK ROW
- SLOANE AV & PARK ROW
- E BAGLEY RD & HEPBURN RD
- SLOANE AV & EDANOLA AV
- 18825 ROYALTON RD
- ROCKY RIVER LOOP
- 19115 ST. CLAIR AV
- 19170 BAGLEY RD
- 19199 ST. CLAIR AV
- 19355 BAGLEY RD
- HILLIARD BLVD & WOOSTER RD
- 19350 PURITAS AV
- MILES RD & EMERY RD
- MILES RD & EMERY RD
- 19516 HARVARD AV
- CENTER RIDGE RD & WOOSTER PARK DR
- BAGLEY DR & PLEASANT ST
- 19700 LAKESHORE BLVD
- HARVARD AV & EASTWOOD LN
- and 5381 more (see the full list on the map or in the GeoJSON)
Over time
Overall score across the last 4 checks — unchanged since 2026-07-31.
Show the numbers
| Check | Score | Change |
|---|---|---|
| 2026-07-25 | 14.2 | first check |
| 2026-07-30 | 33.6 | up 19.4 |
| 2026-07-31 | 33.6 | no change |
| 2026-08-01 | 33.6 | no change |
What changed since your last check
- Correctness no change
- Freshness no change
- Rider experience no change
- Realtime quality no change
What changed in this feed
Overall grade and score held steady since 2026-07-31.
Same feed file as 2026-07-31; 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.
What changed over time
On 2026-07-25 this feed started at grade F. On 2026-07-30 feed renewed to a current calendar. As of 2026-08-01 it holds grade F.
A plain-language history of this feed, newest first.
- 2026-07-30 Feed renewed to a current calendar.
Everything we checked
18 findings, ordered by severity.
Show every finding
- Error449 instances
Trip distance exceeds shape distance (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'trip_distance_exceeds_shape_distance' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Finding code: trip_distance_exceeds_shape_distance · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Error73 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)
- Error1 instance
The trip updates realtime feed failed during sampling.
When this feed is down, riders see scheduled times presented as if they were live.
Fix: Check the trip updates endpoint with your AVL vendor; it should return a fresh GTFS-Realtime protobuf on every request. (Usually a vendor support ticket.)
Finding code: scorecard_rt_trip_updates_unreachable · Read the fix guide · See GTFS-Realtime reference (opens the GTFS-Realtime reference on an external site)
- Error1 instance
The vehicle positions realtime feed failed during sampling.
When this feed is down, riders see scheduled times presented as if they were live.
Fix: Check the vehicle positions endpoint with your AVL vendor; it should return a fresh GTFS-Realtime protobuf on every request. (Usually a vendor support ticket.)
Finding code: scorecard_rt_vehicle_positions_unreachable · Read the fix guide · See GTFS-Realtime reference (opens the GTFS-Realtime reference on an external site)
- Error1 instance
The service alerts realtime feed failed during sampling.
When this feed is down, riders see scheduled times presented as if they were live.
Fix: Check the service alerts endpoint with your AVL vendor; it should return a fresh GTFS-Realtime protobuf on every request. (Usually a vendor support ticket.)
Finding code: scorecard_rt_service_alerts_unreachable · Read the fix guide · See GTFS-Realtime reference (opens the GTFS-Realtime reference on an external site)
- Warning24036 instances
24036 of 24036 trips don't say whether the vehicle is wheelchair accessible.
Even with accessible stops, riders need to know the transit vehicle itself can take them.
Fix: Set wheelchair_accessible on every trip. If every vehicle is accessible, this may be one default; otherwise use the value for each trip. (A default or per-trip field in your export.)
Finding code: scorecard_wheelchair_accessible_unknown · Read the fix guide · See GTFS Schedule reference (opens the GTFS Schedule reference on an external site)
- Warning16981 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)
- Warning7262 instances
On some trips the stop distances run a little past the end of the route line.
The stop and shape distance values don't quite line up, so any math that uses them can drift.
Fix: Re-generate shape_dist_traveled on export so stop and shape distances use the same units. (Usually an export-tool fix, not hand editing.)
Finding code: trip_distance_exceeds_shape_distance_below_threshold · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning5631 instances
5631 of 5631 stops don't say whether a wheelchair user can board there.
Riders who use wheelchairs can't plan a trip when accessibility is marked 'unknown'; apps show no information at all.
Fix: Set wheelchair_boarding to 1 (accessible) or 2 (not accessible) for every stop. A field survey can start with the busiest stops. (A column in stops.txt; your scheduling software likely has it.)
Finding code: scorecard_wheelchair_boarding_unknown · Read the fix guide · See GTFS Schedule reference (opens the GTFS Schedule reference on an external site)
- Warning5596 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)
- Warning793 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)
- Warning396 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)
- Warning1 instance
Many of the feed's trips don't run at all in the next 7 days.
It usually means old service periods are still in the export, making the feed bigger and harder to check.
Fix: Trim past service periods the next time you export. (One setting in most export tools.)
Finding code: trip_coverage_not_active_for_next7_days · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules 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)
- Info5535 instances
About 5535 stop names are written in ALL CAPS.
Mixed-case names are easier to read in apps and are read more naturally by screen readers.
Fix: Rename stops to mixed case where the language has letter case (for example, 'Central Station'). (Often a bulk fix in your scheduling software.)
Finding code: scorecard_stop_names_all_caps · Read the fix guide · See GTFS Best Practices (opens GTFS Best Practices on an external site)
- Info5 instances
The feed has a stretch of two weeks or more with no service running.
A long gap can mean dates were left out of the calendar. Apps then show no trips on those days.
Fix: Check whether the gap is real, like a seasonal break; if not, add the missing dates to the calendar. (A review of your calendar dates.)
Finding code: big_gap_in_service · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Info1 instance
Future calendar (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'future_calendar' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Finding code: future_calendar · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Info1 instance
Future feed (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'future_feed' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Finding code: future_feed · 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. 2 validator errors to resolve.
- Published Ready
- Published at a public URL.
- Valid Needs attention
- 2 validator errors to resolve.
- Current Ready
- Service data covers the next 126 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 24036 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. 2 validator errors to resolve. States wheelchair access on 0% of stops and 0% of trips; the mark needs 90% of each.
- Valid Not yet
- 2 validator errors to resolve.
- Current Met
- Service data covers the next 126 days.
- Accessible Not yet
- States wheelchair access on 0% of stops and 0% of trips; the mark needs 90% of each.
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.
Realtime reliability
The realtime feed responded on 0.0% of 200 checks over the last 34 days, with lag not reported by the feed.
Sampled on a schedule between full scores, so this tracks uptime and freshness over time rather than at a single moment.
Clears the Google and Apple Maps four-week coverage bar. This feed has 126 days of service ahead, clearing the four-week (28-day) window Maps asks for. The feed also carries 522 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 6 / 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 100 / 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 45 / 100
- GTFS Best Practices for rider-facing fields. MobilityData grading covers stop names and headsigns.
- Realtime quality 0 / 100
- 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.
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/greater-cleveland-regional-transit-authority/2026-08-01.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-01. 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.