Ann Arbor Area Transportation Authority (TheRide)

What changed since the last check

• Correctness no change
• Freshness no change
• Rider experience no change

Top three things to fix

1. 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.

   This one is about the feed as a whole, so there is no share of it to count.

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

2. Trim leading and trailing spaces on export. The scorecard's auto-fixed copy already does this.

   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.

   This is a validator notice, and the validator decides what each instance covers, so no share of the network can be read from it here.

   Effort: Usually one export setting.

3. Use mixed case for stop names and headsigns (e.g. 'Main St & 2nd Ave', not 'MAIN ST & 2ND AVE').

   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.

   This is a validator notice, and the validator decides what each instance covers, so no share of the network can be read from it here.

   Effort: Often a bulk fix in your scheduling software.

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 115 days.

agency_id provided Ready

agency.txt provides agency_id. For RY2026, keep one stable value for each NTD reporter represented in the feed and crosswalk each value on the P-50 form.

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

The bar this score answers to

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.

Key facts

Feed URL

https://www.theride.org/sites/default/files/google/google_transit.zip

Last checked

2026-10-07

Service window

115 days of service data remain. Last service date 2027-01-30.

Feed version

S1000302

Location

Michigan