Feed status · checked 2026-09-13
University of Michigan Transit Services
Based on the feed source on file; publisher ownership is not verified
Service mode Bus
unchanged since 2026-09-12
Catalogued in Michigan.
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 13 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
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
119 of 120 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
8432 of 8432 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
Turn on 'remove unused shapes' (or the like) in your export tool.Likely your export tool
The feed contains route shapes no trip uses. Harmless to riders, but it bloats the feed and suggests stale export data.
⏱ One setting.worth about +6 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
- 119 of 120 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
- 8432 of 8432 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
- Feed evidence
- The feed contains route shapes no trip uses.
- Next action
- Turn on 'remove unused shapes' (or the like) in your export tool.
- 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.
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 for scorecard_wheelchair_boarding_unknown
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.
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 for scorecard_wheelchair_accessible_unknown
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.
Turn on 'remove unused shapes' (or the like) in your export tool. · Read the fix guide for unused_shape
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 111 days.
- Published accessibility data
- Accessibility information is stated for 0.8% 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
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 7 kinds of issue across 26 instances (0 error, 22 warning, 4 informational).
Service data covers the next 111 days.
1% of stops state wheelchair accessibility (0% marked accessible, 1% marked not accessible). This measures what the feed publishes, not whether a stop is physically usable. Fare data is published.
1% of stops state accessibility (0% marked accessible). Reflects what the feed states, not verified physical usability.
2 accessibility depth signals
2 route badge(s) pair a color and text color below the WCAG 4.5:1 contrast bar (CN, MX).
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.
24 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set ("Green Rd Park & Ride Inbound", "Green Rd Park & Ride Outbound", "East Ann Arbor Health & Geriatrics Center", 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 120 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.
- BB (gray)
- CN (purple)
- CS (teal)
- CSX (gray)
- DD (yellow)
- MX (red)
- NES (gray)
- NW (orange)
- NX (red)
- OS (gray)
- WS (white)
- WX (white)
| Route | Type | Line color |
|---|---|---|
| 99995 Commencement Charters | Bus | white (no shape in feed) |
| 99997 Training route | Bus | white (no shape in feed) |
| 99998 Charter Route | Bus | white (no shape in feed) |
| 99999 Test Route | Bus | white (no shape in feed) |
| BB Bursley Baits | Bus | gray |
| CN Commuter North | Bus | purple |
| CS Commuter South | Bus | teal |
| CSX Crisler Express | Bus | gray |
| DD Diag-to-Diag Express | Bus | yellow |
| MX Med Express | Bus | red |
| NES North-East Shuttle | Bus | gray |
| NW Northwood | Bus | orange |
| NX Northwood Express | Bus | red |
| OS Oxford Shuttle | Bus | gray |
| WS Wall Street-NIB | Bus | white |
| WX Wall Street Express | Bus | white |
List every stop
- TEST STOP 1
- TEST STOP 2
- Huron Parkway and Baxter Northbound
- Baxter at Dean Eastbound
- Dean Road Garage
- Dean and Hubbard Southbound
- Hubbard and Huron Parkway Westbound
- Michigan Union S. State
- Michigan Union S. Univ
- Shapiro Library
- East Quad Willard
- East Quad Church
- Henderson House
- Oxford Housing
- Angell Elementary School
- School of Kinesiology Building
- Power Center
- Rackham Bldg
- Central Campus Transit Center: Chemistry
- Central Campus Transit Center: Ruthven Museum
- Green Rd Park & Ride Inbound
- Green Rd Park & Ride Outbound
- Michigan House
- 2101 Commonwealth
- Rachel Upjohn Building
- East Ann Arbor Health & Geriatrics Center
- Arbor Lakes
- Domino's Farms Lobby A
- Domino's Farms Lobby C
- Domino's Farms Lobby M
- Domino's Farms Lobby H
- Plymouth Park-and-Ride
- Stockwell Hall Outbound
- Stockwell Hall Inbound
- Cardiovascular Center
- Lloyd/Observatory
- Couzens Hall
- Biomedical Science Research Bldg
- Glen/Catherine Outbound
- Glen/Catherine Inbound
- North Ingalls Bldg
- Medical Science Research Bldg II
- Markley Hall
- Mott Hospital
- Taubman Outbound
- Taubman Inbound
- Cancer Center Inbound
- Cancer Center Outbound
- Maiden Lane
- W Medical Ctr Dr at Catherine
- Wall St Structure
- VA Hospital Circle Drive
- Fuller Rd at Mitchell Field Lot M-75
- VA Hospital Fuller Rd
- Biomedical Engineering Bldg
- Ford Presidential Library
- Cooley Lab Inbound
- Cooley Lab Outbound
- FXB Inbound
- FXB Outbound
- Bursley Hall Inbound
- Bursley Hall Outbound
- Baits II Inbound
- Baits II Outbound
- Baits I
- Murfin/Northwood III
- Northwood III Inbound
- Northwood III Outbound
- Northwood I Inbound
- Northwood I Outbound
- Cram Circle Inbound
- Cram Circle Outbound
- Northwood II Inbound
- Northwood II Outbound
- Fire Station Inbound
- Fire Station Outbound
- Plymouth Rd Crosswalk
- Northwood IV
- Northwood Community Center
- Hayward/Hubbard Hubbard Inbound
- Hayward/Hubbard Hubbard Outbound
- Huron/Hubbard Hubbard Inbound
- Hayward/Hubbard Hayward Outbound
- NCAC Hubbard Inbound
- Huron/Hubbard Huron Outbound
- Northwood V (1)
- Northwood V (2)
- Northwood V (3)
- NCAC%% Hubbard Outbound
- NCRC SB Huron Pkwy
- NCRC NB Huron Pkwy
- NCAC Inbound
- NCAC Outbound
- North Campus Facilities Services Bldg Outbound
- North Campus Facilities Services Bldg Inbound
- NCRC
- NCRC South
- Fuller Rd at Lot NC-78 Mitchell Field (1)
- Fuller Rd at Lot NC-78 Mitchell Field (2)
- Fuller Rd at Lot NC-78 Mitchell Field (3)
- Glazier Way Lot NC-51 West
- Glazier Way Lot NC-51 North
- North Campus Facilities Services Bldg Outbound
- Glazier Way Lot NC-51 East
- Pierpont Commons Murfin Outbound
- Pierpont Commons Murfin Inbound
- Art & Architecture
- Pierpont Commons Bonisteel Inbound
- Crisler Center/Lot SC-7
- Crisler Center Lot SC-5
- Transportation Gate
- Facilities Services Building
- Institute for Continuing Legal Education
- Intramural Building Outbound
- Intramural Building Inbound
- Law Quad
- South Quad
- Zina Pitcher
- Wolverine Village Eastbound
- Wolverine Village Westbound
Over time
Overall score across the last 6 checks — unchanged since 2026-09-12.
Show the numbers
| Check | Score | Change |
|---|---|---|
| 2026-08-06 | 58.9 | first check |
| 2026-08-07 | 58.4 | down 0.5 |
| 2026-08-10 | 58.9 | up 0.5 |
| 2026-09-01 | 53.9 | down 5.0 |
| 2026-09-12 | 72.6 | up 18.7 |
| 2026-09-13 | 72.6 | 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 F. On 2026-09-12 the grade moved from F to C. On 2026-09-01 feed expired. On 2026-09-13 the check no longer reported: some service calendars in the feed have already ended; this feed's service calendar runs out within the next 30 days; service data runs out in 15 day(s); some stops sit far from the route line, going by the feed's own distance values. As of 2026-09-13 it holds grade C.
A plain-language history of this feed, newest first.
- 2026-09-12 Grade went F to C, freshness rose 100 points.
- 2026-09-01 Feed expired.
Everything we checked
10 findings, ordered by severity.
Show every finding
- Warning8432 instances
8432 of 8432 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 for scorecard_wheelchair_accessible_unknown · See GTFS Schedule reference (opens the GTFS Schedule reference on an external site)
- Warning119 instances
119 of 120 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)
- Warning9 instances
The feed contains route shapes no trip uses.
Harmless to riders, but it bloats the feed and suggests stale export data.
Fix: Turn on 'remove unused shapes' (or the like) in your export tool. (One setting.)
Finding code: unused_shape · Read the fix guide for unused_shape · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning8 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 for stop_without_stop_time · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning2 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
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 for missing_recommended_field · 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 for route_color_contrast · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Info4 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 for big_gap_in_service · 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 111 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 8432 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
One requirement remains for this feed to earn the conformance mark. States wheelchair access on 1% of stops and 0% of trips; the mark needs 90% of each.
- Valid Met
- Passes validation with no errors.
- Current Met
- Service data covers the next 111 days.
- Accessible Not yet
- States wheelchair access on 1% 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.
- 8 of 120 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.
Clears the Google and Apple Maps four-week coverage bar. This feed has 109 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 72 / 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 52 / 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.
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/university-of-michigan-transit-services-2072/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.