Feed status · checked 2026-08-01
Memphis Area Transit Authority
Based on the feed this agency publishes
Service mode Bus
unchanged since 2026-07-31
Catalogued in Tennessee.
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 73 minutes ago.
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 509 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
7494 of 7494 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
1496 of 1496 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
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 509 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
- 7494 of 7494 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
- 1496 of 1496 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. 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.
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. 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.
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. 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 was 509 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
- 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.
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 7 kinds of issue across 9123 instances (0 error, 9122 warning, 1 informational).
Service data ended 509 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 not published.
0% of stops state accessibility (0% marked accessible). Reflects what the feed states, not verified physical usability.
3 accessibility depth signals
18 route badge(s) pair a color and text color below the WCAG 4.5:1 contrast bar (34, 16, 53, 39, 37, 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.
643 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set ("NORTH HOLLYWOOD ST at ELDRIDGE AVENUE", "NORTH HOLLYWOOD ST at GOLDENORTH AVENUE", "CENTRAL AVENUE at EARLY MAXWELL BLVD", 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.
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 7494 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.
- 01 (blue)
- 02 (red)
- 04 (blue)
- 07 (red)
- 08 (blue)
- 11 (red)
- 12 (blue)
- 16 (teal)
- 19 (red)
- 28 (teal)
- 30 (blue)
- 32 (red)
- 34 (blue)
- 36 (red)
- 37 (blue)
- 39 (red)
- 40 (blue)
- 42 (blue)
- 50 (blue)
- 52 (blue)
- 53 (red)
- 57 (red)
- 69 (red)
| Route | Type | Line color |
|---|---|---|
| 01 UNION | Bus | blue |
| 02 MADISON | Bus | red |
| 04 WALKER | Bus | blue |
| 07 SHELBY & HOLMES | Bus | red |
| 08 CHELSEA & HIGHLAND | Bus | blue |
| 11 FRAYSER | Bus | red |
| 12 MALLORY | Bus | blue |
| 16 SOUTHEAST CIRCULATOR | Bus | teal |
| 19 VOLLINTINE | Bus | red |
| 28 AIRPORT | Bus | teal |
| 30 BROOKS | Bus | blue |
| 32 HOLLYWOOD & HAWKINS MILL | Bus | red |
| 34 CENTRAL & WALNUT GROVE | Bus | blue |
| 36 LAMAR | Bus | red |
| 37 PERKINS | Bus | blue |
| 39 SOUTH THIRD | Bus | red |
| 40 STAGE & LAUDERDALE | Bus | blue |
| 42 CROSSTOWN | Bus | blue |
| 50 POPLAR | Bus | blue |
| 52 JACKSON | Bus | blue |
| 53 SUMMER | Bus | red |
| 57 PARK | Bus | red |
| 69 WINCHESTER | Bus | red |
List every stop
- WATKINS STREET at LEVEE ROAD
- RIVERDALE BEND at WINCHESTER ROAD
- WILLIAM HUDSON TRANSIT CENTER
- AMERICAN WAY TRANSIT CENTER
- AIRWAYS TRANSIT CENTER
- WALNUT GROVE ROAD at PERKINS EXT
- FRAYSER PLAZA
- YALE ROAD at AUSTIN PEAY HWY
- BROOKS RD at 3RD ST
- EXETER ROAD at POPLAR AVENUE
- CENTRAL AVENUE at U-M CROSSWALK
- PRIMACY PARKWAY at RIDGEWAY ROAD
- SECOND at EXCHANGE
- CAROLINE AVE at RIVERSIDE DR
- CENTENNIAL DRIVE at HACKS CROSS ROAD
- HOLMES ROAD at HUDGINS ROAD
- WOLFCHASE GALLERIA MALL
- ADAMS AVENUE at DANNY THOMAS BOULEVARD
- ADAMS AVENUE at DUNLAP STREET
- ADAMS AVENUE at DUNLAP STREET
- ADAMS AVENUE at DUNLAP STREET
- ADAMS AVENUE at 4TH STREET
- ADAMS AVENUE at HIGH STREET
- ADAMS AVENUE at HIGH STREET
- ADAMS AVENUE at JEFFERSON AVENUE
- ADAMS AVENUE at JEFFERSON AVENUE
- ADAMS AVENUE at MANASSAS STREET
- ADAMS AVENUE at MANASSAS STREET
- ADAMS AVENUE at NEELY STREET
- ADAMS AVENUE at NEELY STREET
- ADAMS AVENUE at ORLEANS STREET
- ADAMS AVENUE at ORLEANS STREET
- ADAMS AVENUE at 3RD STREET
- AIR PARK STREET at REGAL BOULEVARD
- AIR PARK STREET at WINCHESTER ROAD
- AIR PARK STREET at AIR PARK STREET
- AIR PARK STREET at AIR PARK STREET
- AIRWAYS BOULEVARD at ARLINGTON AVENUE
- AIRWAYS BOULEVARD at ARLINGTON AVENUE
- AIRWAYS BOULEVARD at BALL ROAD
- AIRWAYS BOULEVARD at BOYLE AVENUE
- AIRWAYS BOULEVARD at BOYLE AVENUE
- AIRWAYS BOULEVARD at BROOKS ROAD
- AIRWAYS BOULEVARD at BROOKLYN AVENUE
- AIRWAYS BOULEVARD at BROOKS ROAD
- AIRWAYS BOULEVARD at BROOKS ROAD
- AIRWAYS BOULEVARD at CARNES AVENUE
- AIRWAYS BOULEVARD at DEADRICK AVENUE
- AIRWAYS BOULEVARD at DEMOCRAT ROAD
- AIRWAYS BOULEVARD at DEMOCRAT ROAD
- AIRWAYS BOULEVARD at DEMOCRAT ROAD
- AIRWAYS BOULEVARD at DIRECTORS ROW
- AIRWAYS BOULEVARD at DIRECTORS ROW
- AIRWAYS BOULEVARD at DIRECTORS ROW
- AIRWAYS BOULEVARD at DUNN AVENUE
- AIRWAYS BOULEVARD at DUNN AVENUE
- AIRWAYS BOULEVARD at DUNN AVENUE
- AIRWAYS BOULEVARD at DUNN AVENUE
- AIRWAYS BOULEVARD at DUNN AVENUE
- AIRWAYS BOULEVARD at DWIGHT ROAD
- AIRWAYS BOULEVARD at DWIGHT ROAD
- AIRWAYS BOULEVARD at HOLMES ROAD
- AIRWAYS BLVD at HOLMES RD
- AIRWAYS BLVD at JAMIE DR
- AIRWAYS BOULEVARD at JAMIE DRIVE
- AIRWAYS BOULEVARD at JOY LANE
- AIRWAYS BOULEVARD at KETCHUM ROAD
- AIRWAYS BOULEVARD at KETCHUM ROAD
- AIRWAYS BOULEVARD at LARMA AVENUE
- AIRWAYS BOULEVARD at LAMAR AVENUE
- AIRWAYS BOULEVARD at LAROSE AVENUE
- AIRWAYS BOULEVARD at LOWELL AVENUE
- AIRWAYS BOULEVARD at MALONE AVENUE
- AIRWAYS BOULEVARD at MALONE AVENUE
- AIRWAYS BLVD at MCKELLAR WOODS
- AIRWAYS BOULEVARD at MCKELLAR WOODS
- AIRWAYS BOULEVARD at MEMPHIS DEPOT PKWY
- AIRWAYS BOULEVARD at MEMPHIS DEPOT PKWY
- AIRWAYS BOULEVARD at PARK AVENUE
- AIRWAYS BOULEVARD at PARK AVENUE
- AIRWAYS BOULEVARD at PECAN CIRCLE
- AIR PARK STREET at PREMIER AVENUE
- AIR PARK STREET at PREMIER AVENUE
- AIR PARK STREET at PREMIER AVENUE
- AIR PARK STREET at PREMIER AVENUE
- AIRWAYS BOULEVARD at PROFESSIONAL
- AIRWAYS BOULEVARD at PROGRESS AVENUE
- AIRWAYS BOULEVARD at PROGRESS AVENUE
- AIR PARK STREET at RAINES ROAD
- AIR PARK STREET at RAINES ROAD
- AIR PARK STREET at REGAL BOULEVARD
- AIRWAYS BOULEVARD at RILEY AVENUE
- AIRWAYS BOULEVARD at SARATOGA AVENUE
- AIRWAYS BOULEVARD at SHELBY DRIVE
- AIRWAYS BOULEVARD at SPOTTSWOOD AVENUE
- AIRWAYS BOULEVARD at WILSON ROAD
- AIRWAYS BOULEVARD at WINCHESTER ROAD
- AIRWAYS BOULEVARD at WINCHESTER ROAD
- ALCY ROAD at HILLVIEW DRIVE
- ALCY ROAD at JOHANNA DRIVE
- ALCY ROAD at JOHANNA DRIVE
- ALCY ROAD at JUDSON STREET
- ALCY ROAD at KETCHUM ROAD
- ALCY ROAD at KETCHUM ROAD
- ALCY ROAD at KEEN ROAD
- ALCY ROAD at LAPALOMA STREET
- ALCY ROAD at MANCHESTER ROAD
- ALCY ROAD at MANCHESTER ROAD
- ALCY ROAD at PERRY ROAD
- ALCY ROAD at PERRY ROAD
- ALCY ROAD at ROZELLE STREET
- ALCY ROAD at SAMUELS STREET
- ALCY ROAD at SHERRIE STREET
- ALCY ROAD at SPARKS STREET
- ALCY ROAD at THAMES ROAD
- ALCY ROAD at VERDUN STREET
- ALICIA DRIVE at ASHLAWN ROAD
- ALICE AVENUE at BENTON STREET
- ALICE AVENUE at LAUREN ROBERTS
- ALICIA DRIVE at MADISON AVENUE
- ALICIA DRIVE at MADISON AVENUE
- ALICIA DRIVE at MADISON AVENUE
- ALICE AVE at PINE HILL
- ALICIA DRIVE at POPLAR AVENUE
- ALICIA DRIVE at POPLAR AVENUE
- ALICIA DRIVE at UNION AVENUE
- ALICIA DRIVE at UNION AVENUE
- ALICIA DRIVE at UNION AVENUE
- AMERICAN WAY at AMERICAN WAY DRIVE
- AMERICAN WAY at CHERRY ROAD
- AMERICAN WAY at CHERRY ROAD
- AMERICAN WAY at CHERRY ROAD
- AMERICAN WAY at CHERRY ROAD
- AMERICAN WAY at CLAUDETTE ROAD
- AMERICAN WAY at CLAUDETTE ROAD
- AMERICAN WAY at COLONY PARK DRIVE
- AMERICAN WAY at COLONY PARK DRIVE
- AMERICAN WAY at GETWELL ROAD
- AMERICAN WAY at GETWELL ROAD
- AMERICAN WAY at GETWELL ROAD
- AMERICAN WAY at LARMA AVENUE
- AMERICAN WAY at LAMAR AVENUE
- AMERICAN WAY at MALL ROAD
- AMERICAN WAY at S PERKINS ROAD
- AMERICAN WAY at S PERKINS ROAD
- AMERICAN WAY at TRANSIT CENTER
- AMERICAN WAY at TRANSIT CENTER
- AMERICAN WAY at CONNECTING ROAD
- AMERICAN WAY at MALL ROAD
- APPLING ROAD at DEXTER ROAD
- APPLING ROAD at MAY APPLE DRIVE
- ARNOLD ROAD at OLD QUARRY ROAD
- ARNOLD ROAD at PRESCOTT ROAD
- ARNOLD ROAD at PRESCOTT ROAD
- ARNOLD ROAD at SHELBY DRIVE
- ARNOLD ROAD at SUMNERS WELLS ROAD
- AUCTION AVENUE at DANNY THOMAS BOULEVARD
- AUCTION AVENUE at DANNY THOMAS BOULEVARD
- AUCTION AVENUE at DANNY THOMAS BOULEVARD
- AUCTION AVENUE at 5TH STREET
- AUCTION AVENUE at 5TH STREET
- AUCTION AVENUE at 7TH STREET
- AW WILLIS AVENUE at 3RD STREET
- AUCTION AVENUE at 3RD STREET
- AUSTIN PEAY HWY at COLEMAN ROAD
- AUSTIN PEAY HWY at COLEMAN ROAD
- AUSTIN PEAY HWY at COLEMAN ROAD
- AUSTIN PEAY HWY at COLEMAN ROAD
- AUSTIN PEAY HWY at JONES ROAD
- AUSTIN PEAY HWY at JONES ROAD
- AUSTIN PEAY HWY at JOSLYN STREET
- AUSTIN PEAY HWY at LAKEHURST DRIVE
- AUSTIN PEAY HWY at LAKEHURST DRIVE
- AUSTIN PEAY HWY at OVERBROOK DRIVE
- AUSTIN PEAY HWY at RALEIGH COMMON DRIVE
- AUSTIN PEAY HWY at RALEIGH COMMON DRIVE
- AUSTIN PEAY HWY at RALEIGH SPRINGS MKTPL
- AUSTIN PEAY HWY at STAGE ROAD
- AUSTIN PEAY HWY at STAGE ROAD
- AUSTIN PEAY HWY at YALE ROAD
- AUSTIN PEAY HWY at YALE ROAD
- AUSTIN PEAY HWY at YALE ROAD
- AUSTIN PEAY HWY at YALE ROAD
- AUSTIN PEAY HWY at YALE ROAD
- BALL ROAD at SILVER STREET
- BALL ROAD at SILVER STREET
- BASS PRO SHOPS
- BEALE ST at MAIN ST
- BEALE STREET at MAIN STREET
- BEALE STREET at MAIN STREET
- BELLEVUE BOULEVARD at AGNES PLACE
- BELLEVUE BOULEVARD at AUTUMN AVENUE
- BELLEVUE BOULEVARD at AUTUMN AVENUE
- BELLEVUE BOULEVARD at BEECHWOOD AVENUE
- BELLEVUE BOULEVARD at BEECHWOOD AVENUE
- BELLEVUE BOULEVARD at CARR AVENUE
- BELLEVUE BOULEVARD at CARR AVENUE
- BELLEVUE BOULEVARD at CARR AVENUE
- BELLEVUE BOULEVARD at CENTRAL AVENUE
- BELLEVUE BOULEVARD at CENTRAL AVENUE
- BELLEVUE BOULEVARD at COURT AVENUE
- BELZ BOULEVARD at FLORIDA STREET
- BELZ BOULEVARD at FLORIDA STREET
- BELLEVUE BOULEVARD at FORREST AVENUE
- BELLEVUE BOULEVARD at FORREST AVENUE
- BELLEVUE BOULEVARD at HEISTAN PLACE
- BELZ BOULEVARD at KANSAS STREET
- BELZ BOULEVARD at KANSAS STREET
- BELLEVUE BOULEVARD at LAMAR AVENUE
- BELLEVUE BOULEVARD at LAMAR AVENUE
- BELLEVUE BOULEVARD at MADISON AVENUE
- BELLEVUE BOULEVARD at MCLEMORE AVENUE
- BELLEVUE BOULEVARD at MCLEMORE AVENUE
- BELLEVUE BOULEVARD at MCLEMORE AVENUE
- BELLEVUE BOULEVARD at MCLEMORE AVENUE
- BELLEVUE BOULEVARD at ORGILL AVENUE
- BELLEVUE BOULEVARD at OVERTON PARK AVE
- BELLEVUE BOULEVARD at PEABODY AVENUE
- BELLEVUE BOULEVARD at SAXON AVENUE
- BELLEVUE BOULEVARD at SAXON AVENUE
- BELLEVUE BOULEVARD at SEVERSON AVENUE
- BELLEVUE BOULEVARD at SLEDGE STREET
- BELLEVUE BOULEVARD at SOUTH PARKWAY EAST
- BELLEVUE BOULEVARD at TRIGG AVENUE
- BELLEVUE BOULEVARD at TRIGG AVENUE
- BELLEVUE BOULEVARD at WALKER AVENUE
- BELLEVUE BOULEVARD at WILLIAMS AVENUE
- BELLEVUE BOULEVARD at WILLIAMS AVENUE
- BERRYHILL ROAD at MORNING PARK DRIVE
- BERRYHILL ROAD at STAGE ROAD
- BOXTOWN ROAD at EAST BOXTOWN ROAD
- BOXTOWN ROAD at EAST BOXTOWN ROAD
- BOXTOWN ROAD at EAST BOXTOWN ROAD
- FIELDS ROAD at BOXTOWN ROAD
- BOXTOWN ROAD at SEWANEE ROAD
- BOXTOWN ROAD at SEWANEE ROAD
- BRANTLY ROAD at HORN LAKE ROAD
- BREEDLOVE STREET at COWETA PLACE
- BREEDLOVE STREET at COWETA PLACE
- BREEDLOVE STREET at JACKSON AVENUE
- BREEDLOVE STREET at JEHL PL
- BREEDLOVE STREET at JOSEPH PLACE
- BREEDLOVE STREET at JOSEPH PLACE
- BREEDLOVE STREET at LAGRANGE AVENUE
- BREEDLOVE STREET at PALMETTO AVENUE
- BREEDLOVE STREET at PALMETTO AVENUE
- BREEDLOVE STREET at VOLLINTINE AVENUE
- BREEDLOVE STREET at VOLLINTINE AVENUE
- BROOKS ROAD at AIRWAYS BOULEVARD
- BROOKS ROAD at AIRWAYS BOULEVARD
- and 7244 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 | 40.3 | first check |
| 2026-07-30 | 40.3 | no change |
| 2026-07-31 | 40.3 | no change |
| 2026-08-01 | 40.3 | no change |
What changed since your last check
- Correctness no change
- Freshness no change
- Rider experience 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.
Everything we checked
14 findings, ordered by severity.
Show every finding
- Error1 instance
Service data ended 509 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)
- Warning8917 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)
- Warning7494 instances
7494 of 7494 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)
- Warning1496 instances
1496 of 1496 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)
- Warning160 instances
Some stops exist in the feed but no trip ever stops at them.
Riders may walk to a stop where no bus is scheduled to arrive.
Fix: Remove retired stops from the export, or add them back to the trips that should serve them. (A review pass in your scheduling software.)
Finding code: stop_without_stop_time · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning40 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)
- 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
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
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)
- Info1 instance
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
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 509 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 509 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 1496 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 509 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 509 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.
Can riders use it?
Checks beyond structural validation: places where the feed is valid but a rider still could not travel.
- 160 of 3799 boardable stops are never served by any trip. Riders see these stops in apps and on the map but can never catch anything there, which erodes trust in the data. Remove stops no route serves, or add the trips that should call at them.
These do not change the grade. They catch trips with no rideable leg and stops no trip serves, the kind of gap a trip planner trips over.
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 66 / 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 37 / 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/memphis-area-transit-authority-2352/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.