Feed status · checked 2026-08-01
Stark Area Regional Transit Authority (SARTA)
Based on the feed this agency publishes
Service mode 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 11 hours ago; last fetch returned HTTP 404.
Measured 3 of 4 score categories from the Mobility Database's mirror copy of the feed.
How we measured this
Confidence in this measurement: provisional.
- Realtime quality was not measured this run. It does not count against the grade.
- The agency's own feed URL was unreachable, so the Mobility Database's hosted mirror copy was scored instead.
Confidence describes how much the pipeline could measure this run, not the feed itself. It never changes the grade.
Top things to fix
Re-export the feed with a calendar that reaches further out, and set feed_info feed_end_date past your next service change.Likely your export tool
Service data ended 994 day(s) ago. When the calendar runs out, trip planners stop showing this agency even though the buses are still running. Riders are told the service does not exist.
⏱ Usually one export setting; export on a schedule so it never lapses again.worth about +100 points in its category
Set wheelchair_boarding to 1 (accessible) or 2 (not accessible) for every stop. A field survey can start with the busiest stops.Likely your team
1422 of 1422 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.
⏱ A column in stops.txt; your scheduling software likely has it.worth about +25 points in its category
Set wheelchair_accessible on every trip. If every vehicle is accessible, this may be one default; otherwise use the value for each trip.Likely your export tool
1644 of 1644 trips don't say whether the vehicle is wheelchair accessible. Even with accessible stops, riders need to know the bus itself can take them.
⏱ A default or per-trip field in your export.worth about +15 points in its category
This feed is published from a code repository, so whoever maintains that repository regenerates the zip — often planning staff or a consultant. The fix happens in the source data, then a fresh export is committed.
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
- Service data ended 994 day(s) ago.
- Next action
- Re-export the feed with a calendar that reaches further out, and set feed_info feed_end_date past your next service change.
- 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
- 1422 of 1422 stops don't say whether a wheelchair user can board there.
- Next action
- Set wheelchair_boarding to 1 (accessible) or 2 (not accessible) for every stop. A field survey can start with the busiest stops.
- 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
- 1644 of 1644 trips don't say whether the vehicle is wheelchair accessible.
- Next action
- Set wheelchair_accessible on every trip. If every vehicle is accessible, this may be one default; otherwise use the value for each trip.
- 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.
Re-export the feed with a calendar that reaches further out, and set feed_info feed_end_date past your next service change. · Read the fix guide
Make the change. This feed is published from a code repository, so whoever maintains that repository regenerates the zip — often planning staff or a consultant. The fix happens in the source data, then a fresh export is committed.
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.
Set wheelchair_boarding to 1 (accessible) or 2 (not accessible) for every stop. A field survey can start with the busiest stops. · Read the fix guide
Make the change. This feed is published from a code repository, so whoever maintains that repository regenerates the zip — often planning staff or a consultant. The fix happens in the source data, then a fresh export is committed.
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.
Set wheelchair_accessible on every trip. If every vehicle is accessible, this may be one default; otherwise use the value for each trip. · Read the fix guide
Make the change. This feed is published from a code repository, so whoever maintains that repository regenerates the zip — often planning staff or a consultant. The fix happens in the source data, then a fresh export is committed.
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 was 994 days ago.
- 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 v1.
- 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
This feed is published from a code repository. Forward this to whoever maintains that repository; the fix happens in the source data, then a fresh export is committed. Each fix names the validator notice and a guide link.
Send the agency a note
Supporting this agency? Copy this and email it to them. It names what lapsed, why it matters to riders, and the one setting to change.
Score by category
The MobilityData validator flagged 11 kinds of issue across 3810 instances (0 error, 3810 warning, 0 informational).
Service data ended 994 day(s) ago. Trip planners have likely already dropped this feed.
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
15 route badge(s) pair a color and text color below the WCAG 4.5:1 contrast bar (045, 101, 102, 105, 108, 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.
1333 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set ("BELDEN VILLAGE AVE AT WESTFIELD MALL", "HOLIDAY AND HIGBEE AVE NW", "WHIPPLE AVE AND 50TH ST NW", and more).
Consider: Add tts_stop_name with the spoken form, e.g. 'Main Street and Second Avenue', for the affected stops.
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.
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 1422 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.
- 004 (brown)
- 045 (pink)
- 081 (pink)
- 101 (orange)
- 102 (orange)
- 103 (blue)
- 105 (purple)
- 106 (white)
- 107 (blue)
- 108 (gray)
- 110 (pink)
- 111 (green)
- 113 (gray)
- 114 (blue)
- 117 (brown)
- 118 (brown)
- 119 (purple)
- 121 (purple)
- 122 (yellow)
- 124 (gray)
- 125 (white)
- 126 (white)
- 128 (pink)
- 130 (white)
- 131 (gray)
- 132 (pink)
- 133 (white)
- 139 (white)
- 151 (brown)
- 152 (blue)
- 153 (brown)
- 157 (pink)
- 158 (green)
| Route | Type | Line color |
|---|---|---|
| 004 DOWNTOWN CANTON-CLEVELAND OH WADE P | Bus | brown |
| 045 BELDEN VILLAGE/STARK STATE | Bus | pink |
| 081 DOWNTOWN CANTON/AKRON EXPRESS | Bus | pink |
| 101 HARMONT WALMART - DOWNTOWN CANTON | Bus | orange |
| 102 DOWNTOWN CANTON - DOWNTOWN MASSILLO | Bus | orange |
| 103 PLAIN TWP - DOWNTOWN CANTON | Bus | blue |
| 105 BELDEN VILLAGE - DOWNTOWN CANTON | Bus | purple |
| 106 DOWNTOWN CANTON - BELDEN VILLAGE | Bus | white |
| 107 DOWNTOWN CANTON - EAST CANTON | Bus | blue |
| 108 DOWNTOWN CANTON-WASHINGTON SQUARE | Bus | gray |
| 110 SHERRICK WARNER-DOWNTOWN CANTON | Bus | pink |
| 111 DOWNTOWN CANTON-HARMONT WALMART | Bus | green |
| 113 DOWNTOWN CANTON - SOUTHWAY IND | Bus | gray |
| 114 SOUTHGATE-DOWNTOWN CANTON | Bus | blue |
| 117 DOWNTOWN CANTON - FAIRGROUNDS | Bus | brown |
| 118 DOWNTOWN CANTON - PERRY HILLS | Bus | brown |
| 119 DOWNTOWN CANTON - FRAZER | Bus | purple |
| 121 BELDEN VILLAGE - N CANTON IND PARK | Bus | purple |
| 122 DOWNTOWN MASSILLON - FINEFROCK | Bus | yellow |
| 124 DOWNTOWN MASSILLON - WALNUT HILLS | Bus | gray |
| 125 DOWNTOWN MASSILLON - BELDEN VILLAGE | Bus | white |
| 126 DOWNTOWN MASSILLON - ROLLING HILLS | Bus | white |
| 128 DOWNTOWN MASSILLON - MENARDS | Bus | pink |
| 130 DOWNTOWN ALLIANCE - GASKILL | Bus | white |
| 131 DOWNTOWN ALLIANCE - WALMART | Bus | gray |
| 132 DOWNTOWN ALLIANCE - COLLEGE PLAZA | Bus | pink |
| 133 DOWNTOWN ALLIANCE / WEST STATE & FR | Bus | white |
| 139 DOWNTOWN CANTON - LOUISVILLE ALLIAN | Bus | white |
| 151 NORTH LATE NIGHT LOOP | Bus | brown |
| 152 WEST LATE NIGHT LOOP | Bus | blue |
| 153 EAST LATE NIGHT LOOP | Bus | brown |
| 157 MASSILLON/NAVARRE INDUSTRIAL | Bus | pink |
| 158 COMMUNITY CIRCULATOR | Bus | green |
List every stop
- CORNERSTONE TRANSIT CENTER
- MASSILLON TRANSIT CENTER
- BELDEN VILLAGE TRANSIT CENTER
- ALLIANCE TRANSIT CENTER
- BELDEN VILLAGE AVE AT WESTFIELD MALL
- HOLIDAY AND HIGBEE AVE NW
- WHIPPLE AVE AND 50TH ST NW
- WHIPPLE AVE AND CONVENIENCE CIRCLE NW
- AKRON / CANTON AIRPORT
- STAPLES-ARLINGTON ROAD AKRON OHIO
- METRO TRANSIT CENTER AKRON OHIO
- WHIPPLE AVE AND 50TH ST NW
- HARMONT AND 35TH ST NE - WALMART
- 34TH ST AND HARMONT AVE NE
- DALEFORD AVE AND 33RD ST NE
- 30TH ST NE - 3600 BLOCK
- 30TH ST NE - 3400 BLOCK
- HARMONT AVE AND KALAHARI ST NE
- HARMONT AVE AND FAIRMONT BLVD NE
- HARMONT AVE AND 25TH ST NE
- 25TH ST AND WILLOWROW AVE NE
- 25TH ST AND MIDWAY AVE NE
- MIDWAY AVE AND 22ND ST NE
- MIDWAY AVE AND 19TH ST NE
- 19TH ST AND MORRIS AVE NE
- MORRIS AVE AND 22ND ST NE
- MORRIS AVE AND 25TH ST NE
- NORTHEAST COMMUNITY CENTER ON 25TH ST NE
- ROYAL AVE AND 22ND ST NE
- 19TH ST AND ROYAL AVE NE
- 19TH ST AND EDWARDS AVE NE
- HARRISBURG RD AND 19TH ST NE
- HARRISBURG RD AND INDIANA WAY NE
- HARRISBURG RD AND 15TH ST NE
- HARRISBURG RD AND MAHONING RD NE
- COOK LAGOON STARK PARK
- THE OJAYS PARKWAY AND 10TH ST NE
- THE OJAYS PARKWAY AND 9TH ST NE
- THE OJAYS PARKWAY AND SENECA PL NE
- THE OJAYS PARKWAY AND 6TH ST NE
- 6TH ST AND DILL CT NE
- 6TH ST AND CHERRY AVE NE
- WALNUT AVE AND 4TH ST NE
- W TUSCARAWAS ST AND MARKET AVE
- W TUSCARAWAS ST AND CLEVELAND AVE
- W TUSCARAWAS ST AND MCKINLEY AVE
- W TUSCARAWAS ST AND FULTON RD
- W TUSCARAWAS ST AND NEWTON AVE
- W TUSCARAWAS ST AND KENNET CT
- W TUSCARAWAS ST AND HARRISON AVE
- W TUSCARAWAS ST AND BEDFORD AVE
- W TUSCARAWAS ST AND DARTMOUTH AVE
- W TUSCARAWAS ST AND WERTZ AVE
- W TUSCARAWAS ST AND MARYLAND AVE
- W TUSCARAWAS ST AND BELLFLOWER AVE
- W TUSCARAWAS ST AND RAFF RD
- W TUSCARAWAS ST AND POPLAR AVE
- W TUSCARAWAS ST AND VALLYVIEW AVE
- W TUSCARAWAS ST AT FISHER FOODS
- W TUSCARAWAS ST AND MANOR AVE
- W TUSCARAWAS ST AND WOODLAWN AVE
- W TUSCARAWAS ST AND ANNA AVE
- LINCOLN WAY E AND PERRY DR
- LINCOLN WAY E AND EDGEWATER AVE
- LINCOLN WAY E AND HARDING AVE
- LINCOLN WAY E AND HIGHLAND AVE
- LINCOLN WAY E AND GEONA RD
- LINCOLN WAY E AND LENNOX AVE
- BAILY AND LENNOX AVE NW
- BAILY AND AUSTIN AVE NW
- AUSTIN AND LINCOLN WAY E
- LINCOLN WAY E AND KOLPWOOD AVE
- LINCOLN WAY E AND 27TH ST
- LINCOLN WAY E AND 24TH ST
- LINCOLN WAY E AND 22ND ST
- LINCOLN WAY E AND MEADOWS PLAZA
- LINCOLN WAY E AND 17TH ST
- LINCOLN WAY E AND HESS BLVD
- LINCOLN WAY E AND WALES RD
- LINCOLN WAY E AND 9TH ST
- LINCOLN WAY E AND 7TH ST
- LINCOLN WAY E AND 5TH ST
- 3RD ST AND LINCOLNWAY E
- 3RD ST AND WELLMAN AVE
- LINCOLN WAY E AND 5TH ST
- LINCOLN WAY E AND 7TH ST
- LINCOLN WAY E AND 9TH ST
- LINCOLN WAY E AND WALES RD
- LINCOLN WAY E AND HESS BLVD
- LINCOLN WAY E AND 17TH ST
- LINCOLN WAY E AND TREMONT AVE
- LINCOLN WAY E AND 22ND ST
- LINCOLN WAY E AND 24TH ST
- LINCOLN WAY E AND 27TH ST
- LINCOLN WAY E AND GNAU ST
- LINCOLN WAY E AND AUSTIN AVE
- LINCOLN WAY E AND HINDERER AVE
- LINCOLN WAY E AND GENOA AVE
- LINCOLN WAY E AND HIGHLAND AVE
- LINCOLN WAY E AND HARDING AVE
- LINCOLN WAY E AND LEONARD AVE
- LINCOLN WAY E AND PERRY DR
- W TUSCARAWAS ST AND ANNA AVE
- W TUSCARAWAS ST AND WOODLAWN AVE
- W TUSCARAWAS ST AND MILES AVE
- W TUSCARAWAS ST AND W MANOR AVE
- W TUSCARAWAS ST AND WHIPPLE AVE
- CANTON CENTRE
- W TUSCARAWAS ST AND AULTMAN AVE
- W TUSCARAWAS ST AND RAFF RD
- W TUSCARAWAS ST AND MARYLAND AVE
- W TUSCARAWAS ST AND WERTZ AVE
- W TUSCARAWAS ST AND CLARENDON
- W TUSCARAWAS ST AND ARLINGTON AVE
- W TUSCARAWAS ST AND HARRISON AVE
- W TUSCARAWAS ST AND KENNET CT
- W TUSCARAWAS ST AND SCHROYER AVE
- W TUSCARAWAS ST AND BROWN AVE
- W TUSCARAWAS ST AND FULTON RD
- W TUSCARAWAS ST 400 BLOCK
- W TUSCARAWAS ST AND CLEVELAND AVE
- E TUSCARAWAS ST AND PEIDMONT CT
- CHERRY AVE AND 4TH ST NE
- CHERRY AVE AND 6TH ST NE
- CHERRY AVE AND 8TH ST NE
- CHERRY AVE AND LAWRENCE RD NE
- CHERRY AVE AND 11TH ST NE
- CHERRY AVE AND12TH ST AVE NE
- 12TH ST AND SPRING AVE NE
- GIBBS AVE AND 12TH ST NE
- GIBBS AVE AND 14TH ST NE
- GIBBS AVE AND 15TH ST NE
- GIBBS AVE AND 17TH ST NE
- GIBBS AVE AND 19TH ST NE
- GIBBS AVE AND 21ST ST NE
- GIBBS AVE AND 24TH ST NE
- GIBBS AVE AND HAVANA PL NE
- COLONIAL BLVD AND ROWLAND AVE NE
- ROWLAND AVE AND 28TH ST NE
- ROWLAND AVE AND SPANGLER RD NE
- SPANGLER RD AND ST ELMO AVE NE
- SPANGLER RD AND MAPLE AVE NE
- SPANGLER RD AND HARRISBURG RD
- HARRISBURG RD AND 30TH ST NE
- MIDDLEBRANCH RD AND 32ND ST NE
- MIDDLEBRANCH RD 3400 BLOCK
- MIDDLEBRANCH RD AND CATHY DR NE
- MIDDLEBRANCH RD AND 40TH ST NE
- MIDDLEBRANCH RD AND MARTINDALE RD NE
- MIDDLEBRANCH RD AND 45TH ST NE
- MIDDLEBRANCH RD AND 48TH ST NE
- MIDDLEBRANCH RD AND GLADIOLA ST NE
- MIDDLEBRANCH RD AND TULIP ST NE
- 55TH ST AND MIDDLEBRANCH RD NE
- 55TH ST AND GLENHILL AVE NE
- 55TH ST AND LINFORD AVE NE
- FIRESTONE AND SCHNEIDER RD NE
- GLENOAK HIGH SCHOOL
- SCHNEIDER RD AND MIDDLEBRANCH RD NE
- MIDDLEBRANCH RD AND MCDOWELL ST NE
- MIDDLEBRANCH AND EASTON
- EDELWEISS MIDDLEBRANCH
- MIDDLEBRANCH RD AND HOLLYVIEW ST NE
- MIDDLEBRANCH RD AND SCHNEIDER RD NE
- MIDDLEBRANCH RD AND 58TH ST NE
- MIDDLEBRANCH RD AND 55TH ST NE
- MIDDLEBRANCH RD AND TULIP ST NE
- MIDDLEBRANCH RD AND GLADIOLA ST NE
- MIDDLEBRANCH RD AND 48TH ST NE
- MIDDLEBRANCH RD AND 45TH ST NE
- MIDDLEBRANCH RD AND MARTINDALE RD NE
- MIDDLEBRANCH RD AND 41ST ST NE
- MIDDLEBRANCH RD AND CATHY DR NE
- MIDDLEBRANCH RD AND 34TH ST NE
- MIDDLEBRANCH RD AND ROUTE 62
- HARRISBURG RD NE AT ROUTE 62
- SPANGLER RD AND HARRISBURG RD NE
- SPANGLER RD AND MAPLE AVE NE
- SPANGLER RD AND ST ELMO AVE NE
- SPANGLER RD AND ROWLAND AVE NE
- ROWLAND AND COLONIAL BLVD NE
- COLONIAL BLVD AND GIBBS AVE NE
- GIBBS AVE AND 25TH ST NE
- GIBBS AVE AND 21ST ST NE
- GIBBS AVE AND 19TH ST NE
- GIBBS AVE AND 17TH ST NE
- GIBBS AVE AND 15TH ST NE
- GIBBS AVE AND 14TH ST NE
- GIBBS AVE AND 12TH ST NE
- 12TH ST AND PLAIN AVE NE
- 12TH ST AND SPRING AVE NE
- WALNUT AVE AND 12TH ST NE
- WALNUT AVE AND 9TH ST NE
- WALNUT AVE NE 700 BLOCK
- WALNUT AVE AND 6TH ST NE
- 2ND ST AND MARKET AVE SE
- 2ND ST AND CLEVELAND AVE SW
- CLEVELAND AVE AND 2ND ST NW
- CLEVELAND AVE AND 4TH ST NW
- CLEVELAND AVE AND 6TH ST NW
- CLEVELAND AVE AND 8TH ST NW
- CLEVELAND AVE AND 10TH ST NW
- CLEVELAND AVE AND 12TH ST NW
- CLEVELAND AVE AND 14TH ST NW
- CLEVELAND AVE AND 15TH ST NW
- CLEVELAND AVE AND 17TH ST NW
- CLEVELAND AVE AND 18TH ST NW
- CLEVELAND AVE AND 20TH ST NW
- CLEVELAND AVE AND 22ND ST NW
- CLEVELAND AVE AND 25TH ST NW
- CLEVELAND AVE AND 26TH ST NW
- CLEVELAND AVE AT MAIN POST OFFICE
- CLEVELAND AVE AND 28TH ST NW
- CLEVELAND AVE AND 30TH ST NW
- CLEVELAND AVE AND RACHEL ST NW
- CLEVELAND AVE AND 34TH ST NW
- CLEVELAND AVE AND 36TH ST NW
- CLEVELAND AVE AND 38TH ST NW
- CLEVELAND AVE AND 42ND ST NW
- CLEVELAND AVE AND 44TH ST NW
- CLEVELAND AVE AND 47TH ST NW
- CLEVELAND AVE AND 49TH ST NW
- S MAIN ST AND GREENWAY RD NW
- S MAIN ST AND KNOLL ST NW
- EVERHARD RD AND S MAIN ST NW
- EVERHARD RD AND CASTLEWOOD AVE SW
- EVERHARD RD AND JONATHON AVE SW
- EVERHARD RD AND ELBERTA AVE SW
- EVERHARD RD AND SALWAY AVE SW
- EVERHARD RD SW 3800 BLOCK
- EVERHARD RD AND STRATMOR DR SW
- EVERHARD RD AND WHIPPLE AVE SW
- EVERHARD RD AND WHIPPLE AVE SW
- EVERHARD RD AND STRATMOR DR SW
- EVERHARD RD SW 3700 BLOCK
- EVERHARD RD AND SALWAY ST SW
- EVERHARD RD AND ELBERTA AVE SW
- EVERHARD RD AND JONATHON AVE SW
- EVERHARD RD AND WESTFIELD AVE SW
- EVERHARD RD AND S MAIN ST
- S MAIN ST AND GREENWAY RD SW
- CLEVELAND AVE AND 49TH ST NW
- CLEVELAND AVE AND 47TH ST NW
- CLEVELAND AVE AND 44TH ST NW
- CLEVELAND AVE AND 42TH ST NW
- CLEVELAND AVE AND 40TH ST NW
- CLEVELAND AVE AND 38TH ST NW
- CLEVELAND AVE AND 36TH ST NW
- CLEVELAND AVE AND 34TH ST NW
- CLEVELAND AVE AND 32ND ST NW
- and 1172 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 | 29.2 | first check |
| 2026-07-30 | 29.2 | no change |
| 2026-07-31 | 29.2 | no change |
| 2026-08-01 | 29.2 | no change |
What changed since your last check
- Correctness no change
- Freshness no change
- Rider experience no change
Everything we checked
16 findings, ordered by severity.
Show every finding
- Error1 instance
Service data ended 994 day(s) ago.
When the calendar runs out, trip planners stop showing this agency even though the buses are still running. Riders are told the service does not exist.
Fix: Re-export the feed with a calendar that reaches further out, and set feed_info feed_end_date past your next service change. (Usually one export setting; export on a schedule so it never lapses again.)
Finding code: scorecard_feed_expired · Read the fix guide · See GTFS Best Practices (opens GTFS Best Practices on an external site)
- Warning3088 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)
- Warning1644 instances
1644 of 1644 trips don't say whether the vehicle is wheelchair accessible.
Even with accessible stops, riders need to know the bus 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)
- Warning1422 instances
1422 of 1422 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)
- Warning463 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 streets or point riders to the wrong corner.
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)
- Warning194 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)
- Warning54 instances
Some scheduled trips move faster between stops than a bus can.
Usually a typo'd stop time; riders get arrival times no bus can meet.
Fix: Check the flagged stop times for transposed minutes. (A few minutes per flagged trip.)
Finding code: fast_travel_between_consecutive_stops · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning3 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)
- Warning2 instances
Some files leave out fields that GTFS asks for but does not require.
Recommended fields like agency_phone or stop descriptions make the feed more useful to riders and trip planners.
Fix: Review the flagged fields and fill in the ones your riders would use. (A field at a time; not urgent.)
Finding code: missing_recommended_field · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning2 instances
Some stops sit far from the route line they belong to.
Trip planners may draw the bus route through the wrong streets or point riders to the wrong corner.
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)
- Warning1 instance
This feed's service calendar runs out within the next 7 days.
When the calendar ends, Google Maps and other trip planners drop your agency entirely. Riders see no service at all.
Fix: Export and publish an updated GTFS feed that covers at least the next 30 days of service. (Usually a re-export from your scheduling software.)
Finding code: feed_expiration_date7_days · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning1 instance
feed_info.txt lists no contact email and no contact URL.
Without a contact, apps like Google Maps can't reach you when they find a problem in the feed.
Fix: Add feed_contact_email or feed_contact_url to feed_info.txt. (One field, set once in export settings.)
Finding code: missing_feed_contact_email_and_url · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning1 instance
Some route colors don't contrast with their text color.
Route badges get hard to read, most of all for riders with low vision.
Fix: Pick a darker/lighter route_text_color for the flagged routes. (One field per route.)
Finding code: route_color_contrast · Read the fix guide · 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)
- Info1415 instances
About 1415 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)
- 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 Not ready
Resolve this before you certify on the D-10. Service data expired 994 days ago, so FTA would find the link out of date.
- Published Ready
- Published at a public URL.
- Valid Ready
- Passes validation with no errors.
- Current Not ready
- Service data expired 994 days ago, so FTA would find the link out of date.
- 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 1644 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. Service data expired 994 days ago. States wheelchair access on 0% of stops and 0% of trips; the mark needs 90% of each.
- Valid Met
- Passes validation with no errors.
- Current Not yet
- Service data expired 994 days ago.
- 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.
Below the Google and Apple Maps four-week coverage bar. This feed's last day of service has passed, so Google and Apple Maps will stop showing your agency. Re-export with a calendar that covers at least the next four weeks.
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 40 / 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 0 / 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 38 / 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.
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/stark-area-regional-transit-authority-sarta/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.