Feed status · checked 2026-09-13
Ann Arbor Area Transportation Authority (TheRide)
Based on the feed source on file; publisher ownership is not verified
Service mode Bus
unchanged since 2026-09-12
Catalogued in Michigan.
Heads-up: The score rose 20 points in one step, from 64 on 2026-08-10 to 84 on 2026-09-01. A jump this size usually means the export changed rather than the service. Worth checking the run on this date. (checked 2026-09-01). This can be a brief vendor export glitch; watch the next update before acting.
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 30 hours ago; last changed 3 days ago.
Measured 3 of 4 score categories from the feed URL on file (publisher not verified).
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 configured feed URL. Publisher ownership of that URL is not verified.
Confidence describes how much the pipeline could measure this run, not the feed itself. It never changes the grade.
Top things to 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.
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
Trim leading and trailing spaces on export. The scorecard's auto-fixed copy already does this.Likely your export tool
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.
⏱ Usually one export setting.worth about +8 points in its category
Use mixed case for stop names and headsigns (e.g. 'Main St & 2nd Ave', not 'MAIN ST & 2ND AVE').Likely your export tool
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.
⏱ Often a bulk fix in your scheduling software.worth about +4 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 feed contains no fare information.
- Next action
- 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.
- 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
- Some values have extra spaces at the start or end.
- Next action
- Trim leading and trailing spaces on export. The scorecard's auto-fixed copy already does this.
- 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
- Some rider-facing names are in ALL CAPS or all lowercase.
- Next action
- Use mixed case for stop names and headsigns (e.g. 'Main St & 2nd Ave', not 'MAIN ST & 2ND AVE').
- 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.
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 for scorecard_no_fare_data
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.
Trim leading and trailing spaces on export. The scorecard's auto-fixed copy already does this.
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.
Use mixed case for stop names and headsigns (e.g. 'Main St & 2nd Ave', not 'MAIN ST & 2ND AVE'). · Read the fix guide for mixed_case_recommended_field
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 139 days.
- Published accessibility data
- Accessibility information is stated for 99.6% 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
The MobilityData validator flagged 5 kinds of issue across 4362 instances (0 error, 4361 warning, 1 informational).
Service data covers the next 139 days.
100% of stops state wheelchair accessibility (57% marked accessible, 43% marked not accessible). This measures what the feed publishes, not whether a stop is physically usable. Fare data is not published.
100% of stops state accessibility (57% marked accessible). Reflects what the feed states, not verified physical usability.
2 accessibility depth signals
11 route badge(s) pair a color and text color below the WCAG 4.5:1 contrast bar (104, 22, 28, 32, 33, 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.
987 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set ("Michigan + Huron", "Michigan + River", "Emerick + Service Dr", 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.
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 1060 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.
- 104 (teal)
- 22 (blue)
- 23 (purple)
- 25 (brown)
- 26 (purple)
- 27 (brown)
- 28 (blue)
- 3 (brown)
- 30 (purple)
- 31 (green)
- 32 (orange)
- 33 (teal)
- 34 (green)
- 4 (purple)
- 42 (orange)
- 43 (brown)
- 44 (green)
- 45 (blue)
- 46 (green)
- 47 (brown)
- 5 (blue)
- 6 (pink)
- 61 (purple)
- 62 (orange)
- 63 (orange)
- 64 (green)
- 65 (green)
- 66 (brown)
- 67 (brown)
- 68 (green)
| Route | Type | Line color |
|---|---|---|
| 104 Washtenaw Express | Bus | teal |
| 22 Pontiac - Dhu Varren | Bus | blue |
| 23 Plymouth | Bus | purple |
| 25 Ann Arbor - Saline Rd | Bus | brown |
| 26 Scio Church | Bus | purple |
| 27 W Stadium - Oak Valley | Bus | brown |
| 28 Pauline | Bus | blue |
| 3 Huron River | Bus | brown |
| 30 Jackson Rd | Bus | purple |
| 31 Dexter Ave | Bus | green |
| 32 Miller - Maple | Bus | orange |
| 33 Newport | Bus | teal |
| 34 Maple - Dexter | Bus | green |
| 4 Washtenaw | Bus | purple |
| 42 Forest - MacArthur | Bus | orange |
| 43 E Michigan Ave | Bus | brown |
| 44 Ecorse - Tyler | Bus | green |
| 45 Grove | Bus | blue |
| 46 Paint Creek | Bus | green |
| 47 Harriet - W Michigan | Bus | brown |
| 5 Packard | Bus | blue |
| 6 ELLSWORTH - STATE | Bus | pink |
| 61 U-M Miller | Bus | purple |
| 62 U-M - State | Bus | orange |
| 63 U-M - Pontiac | Bus | orange |
| 64 Geddes - E Stadium | Bus | green |
| 65 U-M - PLYMOUTH - GREENHILLS | Bus | green |
| 66 Carpenter - Huron Pkwy | Bus | brown |
| 67 Eisenhower- Golfside | Bus | brown |
| 68 Harris - Ford | Bus | green |
List every stop
- Service Dr. + Gault
- Dexter + Maple
- Stadium + Greenview
- Franklin + Stadium
- Franklin St. + Seventh
- Seventh + Pauline
- Seventh + Davis
- Seventh + Princeton
- Madison + Sixth
- Madison + Fourth
- Madison + First
- Dexter Rd + Wildwood
- YTC - Stop 1
- Dexter Rd + Grandview
- Dexter Rd + Doty
- Dexter Rd w. of Lyn Anne Ct.
- Miller + Maple
- S- Dexter Rd. east of Maple
- S - Dexter west of Lyn Anne
- S- Dexter Rd. btw Worden and Allen
- Dexter + Grandview
- S - Dexter east of Wildwood
- E - First north of Frederick
- Bonisteel + Beal
- N - Michigan west of First
- Michigan + Wallace
- Michigan + Wilson
- Ellsworth + Michigan
- Ellsworth + Hewitt
- Ellsworth + Fairhills
- Ellsworth + Clubview
- Ellsworth + Golfside
- Ellsworth + Cloverlawn
- Ellsworth + Cloverlawn
- YTC - Stop 5
- S - Ellsworth east of Golfside
- Ellsworth + Roundtree Blv
- S - Ellsworth at Wal-Mart
- Michigan + Mansfield
- Michigan + Brown Chapel
- Cross + Huron
- Cross + River
- Cross + Park
- Prospect + Maple
- Forest + Vought
- Forest + Campbell
- Forest + Hollis
- Forest + Browning
- Forest + Harris
- Ford + Forest
- Ford + Holmes
- Golfside + Bynan
- Clark + Ford Elementary
- Clark + Ridge
- Ridge + Holmes
- Holmes + Wildwood
- Cross + Prospect
- Cross + River
- Cross + Huron
- Golfside + Twin Lakes
- Golfside + Washtenaw
- YTC - Stop 4
- Huron River + Cornell
- Service Dr. + Share
- Huron River Dr + Leforge
- South U + State
- Wolverine Tower Entrance #C
- Church + South U
- State St Commuter Lot
- SU + Tappan
- Huron River + Oakwood
- State + UM Commuter Lot
- State + UM Tenni & Gymnastics
- Miller + Maple
- Miller + Kuehnle
- Huron + State
- Maple + Miller
- E- State north of Eisenhower
- State + Hoffman
- State + Hoffman
- State + Parkcrest
- State St + 2285
- State + Hidden Valley
- State + Oakbrook
- State + State Park and Ride
- State + Parkcrest
- Prospect + Oak
- Holmes + East Cir
- Huron River + Oakwood
- YTC - Stop 6
- Nixon + Plymouth
- Adams + Forest
- Michigan + Grove
- Grove + Spring
- Grove + Dorothy
- Grove + Mollie
- Harris + Wingate
- Michigan + Prospect
- Towner + Ecorse
- Ecorse + Maplewood
- First + Michigan
- Ecorse + Maus
- Ecorse + Redwood
- Ecorse + Glenwood
- Jackson + Wagner
- Meijer Jackson Rd
- Jackson + Parkland
- Jackson + Aprill
- Jackson + Nancy
- Jackson + Myrtle
- Foley + Harris
- McAuley + Huron River
- Clark + Ypsilanti Township Community Center
- Ford + Holmes
- Michigan + Harris
- Harris + Foley
- Harriet + Parkridge Community Center
- First + Michigan
- Harris + Ecorse
- Oak Valley + Scio Church
- Towner + Prospect
- Oak Valley + Scio Church
- Leforge + Green
- Stadium + Franlin
- Stadium + Greenview
- Stadium + Kay Parkway
- Stadium + Suffolk
- Ellsworth Rd. + Stone Sch
- Maple + Keystone
- Maple + Country Village
- Oak Valley + Pittsfield Branch Library
- Oak Vally + Arbor Hospice
- Oak Valley + Silver Springs
- Oak Valley + Boulder Ridge
- OakValley + Ann Arbor-Saline
- Oak Valley + Boulder Ridge
- Oak Valley + Silver Spring
- Oak Valley + Pittsfield Branch Library
- Oak Valley + Pittsfield Branch Library
- Scio Ridge + Chase
- Scio Ridge + Liberty
- Liberty + Summerfield Glen
- Jackson + Nancy
- Jackson + April
- Jackson + Trinity Health
- Jackson + Myrtle
- Jackson + Burton
- Jackson + Zeeb
- Jackson + Luella
- Jackson + Burton
- Dexter + Wagner
- Dexter + Landings
- Dexter + Barber
- Dexter + Glenwood
- Dexter + Center
- Dexter + Valley
- Holmes + Spencer
- Holmes + Jerome
- Forest + Ford
- Forest + Harris
- Forest + Browning
- Forest + Hollis
- Main + HarborWay
- Forest + Campell
- Prospect + Forest
- Prospect + Oak
- Michigan + Crimson
- Michigan + Burbank
- Michigan + Utah
- Michigan + Burbank
- Michigan + Oak Grove
- Michigan + Ecorse
- Eisenhower + Signature
- First + Frederick
- Harriet + Perry
- Harriet + Hamilton
- Service Dr + Share
- Service Dr + Hull
- Service Dr + Georgina
- Chidister + Spring
- Grove + Georgina
- Grove + Laural Bay
- Harris + Hawthorne
- Harris + Russel
- Ford + Russell
- Ford + Forest
- Harris + Ecorse
- Leforge + Huron River Dr
- Foley + Gattegno
- Summit + Daniel
- Leforge + Woburn
- Leforge + Clark
- Clark + Bedford
- River + Holmes
- Forest + Norris
- Forest + Huron
- Forest + Norris
- River + Holmes
- Holyoke + 2752 Holyoke
- Leforge + Clark
- Leforge + Huron River Dr
- Clark East Towers
- Midway + Holmes
- Michigan + Spencer
- Spencer + Holmes
- Brooks + Summit
- Holmes + Ridge
- Michigan + Wiard
- Upland + Snowberry Ridge
- Scio Ridge + Sudburry
- Zeeb + Jackson
- Jackson + Dexter
- Miller + Newport Pl.
- Jackson + Grandview
- Jackson + Worden
- Jackson + Burwood
- Jackson + Maple
- Jackson + Lakeview
- YTC - Stop 2
- Green + Whisperwood
- W- Hewitt south of Ellsworth
- N - Jefferson east of Brooks
- MacArthur + Stamford
- Plymouth + Green
- Foley + Harry
- Congress + Ballard
- Carpenter + Washtenaw
- Carpenter + Central
- Carpenter + Packard
- Carpenter + Packard
- Carpenter + Central
- Michigan + Hamilton
- Wiard + Woodruff
- Jackson + Classic Cup Cafe
- Michigan + Johnson
- Scio Church + Oak Valley
- Scio Church + Oak Valley
- Oak Valley + Tudor Time
- Maple + Foss
- Hitchingham + Merritt
- Huron River + Textile
- Huron River + Scooner Cove
- Harry + Heatherridge
- Civic Center Dr + Whittaker
- Maple + Bens
- Textile + Tuttle Hill
- Huron River + Ford Lake Park
- Huron River + Lakecrest
- Huron River + Briarbrook
- Ypsilanti Township Civic Center
- and 810 more (see the full list on the map or in the GeoJSON)
Over time
Overall score across the last 6 checks — unchanged since 2026-09-12.
Show the numbers
| Check | Score | Change |
|---|---|---|
| 2026-08-06 | 65.9 | first check |
| 2026-08-07 | 65.5 | down 0.4 |
| 2026-08-10 | 64.2 | down 1.3 |
| 2026-09-01 | 84.2 | up 20.0 |
| 2026-09-12 | 84.0 | down 0.2 |
| 2026-09-13 | 84.0 | no change |
What changed since your last check
- Correctness no change
- Freshness no change
- Rider experience no change
What changed over time
On 2026-08-06 this feed started at grade D. On 2026-09-01 the grade moved from D to B. On 2026-09-13 the check no longer reported: this feed's service calendar runs out within the next 30 days; service data runs out in 15 day(s). As of 2026-09-13 it holds grade B.
A plain-language history of this feed, newest first.
- 2026-09-01 Grade went D to B, freshness rose 80 points.
Everything we checked
8 findings, ordered by severity.
Show every finding
- Warning4356 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)
- Warning4 instances
4 of 1060 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 for scorecard_wheelchair_boarding_unknown · See GTFS Schedule reference (opens the GTFS Schedule reference on an external site)
- Warning3 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 for mixed_case_recommended_field · 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 for missing_feed_contact_email_and_url · 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 for trip_coverage_not_active_for_next7_days · 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 for scorecard_no_fare_data · See GTFS Best Practices (opens GTFS Best Practices on an external site)
- Info1 instance
Feed valid beyond total service window (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'feed_valid_beyond_total_service_window' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Finding code: feed_valid_beyond_total_service_window · 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).
App makers and state data programs have nobody to email when they spot a problem. Small errors then sit in the feed for months.
Fix: Add feed_contact_email to feed_info.txt. (One field.)
Finding code: scorecard_no_feed_contact · Read the fix guide for scorecard_no_feed_contact · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
NTD GTFS readiness Ready
Published at a public URL, valid, current, and identified with agency_id: the four feed checks for RY2026 all hold here. Only your own D-10 and P-50 filings make that official; this is a heads-up, not a determination.
- Published Ready
- Published at a public URL.
- Valid Ready
- Passes validation with no errors.
- Current Ready
- Service data covers the next 139 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 4235 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 Awarded
This feed earns the conformance mark: valid, current, and stating wheelchair access on nearly every stop and trip.
- Valid Met
- Passes validation with no errors.
- Current Met
- Service data covers the next 139 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 137 days of service ahead, clearing the four-week (28-day) window Maps asks for. No validator errors either, so riders keep seeing this agency in their trip planners; warnings lower the grade here but do not remove a feed from Maps.
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.
A local transit-data support resource is Michigan Public Transit Open Data Program. MDOT's program helping agencies produce and maintain GTFS and GTFS-Flex. This resource supports agencies; it is not a scoring authority.
- Correctness 80 / 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 77 / 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.
Part of the Michigan portfolio: the same scorecards for every feed we track in that group, on one free page.
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/ann-arbor-area-transportation-authority-theride/2026-09-13.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-09-13. 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.