Feed status · checked 2026-08-01
Mass Transportation Authority Flint
Based on the feed this agency publishes
Service mode Bus
unchanged since 2026-07-31
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 19 hours ago; last changed 4 days 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 2405 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
Review the rule documentation for 'invalid_date' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.
Invalid date (flagged by the MobilityData validator). See the linked rule for what this affects.
⏱ Varies.worth about +18 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
1174 of 1174 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
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 2405 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
- Invalid date (flagged by the MobilityData validator).
- Next action
- Review the rule documentation for 'invalid_date' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.
- 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
- 1174 of 1174 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
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.
Review the rule documentation for 'invalid_date' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.
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.
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 2405 days ago.
- Published accessibility data
- Accessibility information is stated for 0% of stops and 100% 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.
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 6 kinds of issue across 67 instances (6 error, 61 warning, 0 informational).
Service data ended 2405 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
8 route badge(s) pair a color and text color below the WCAG 4.5:1 contrast bar (2, 4, 5, 6, 10, 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.
52 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set ("Church at 3rd", "SBD Saginaw at 1st", "EBD Court at Dort SW", 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 1174 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.
- 1 (yellow)
- 10 (orange)
- 11 (teal)
- 12 (orange)
- 13 (pink)
- 15 (gray)
- 2 (red)
- 3 (purple)
- 4 (teal)
- 5 (green)
- 6 (gray)
- 7 (brown)
- 8 (green)
- 9 (pink)
| Route | Type | Line color |
|---|---|---|
| 1 North Saginaw | Bus | yellow |
| 10 Richfield | Bus | orange |
| 11 Fenton Road | Bus | teal |
| 12 Beecher-Corunna | Bus | orange |
| 13 Crosstown North | Bus | pink |
| 15 Shopper Route | Bus | gray |
| 2 M.L.K | Bus | red |
| 3 Miller-Linden | Bus | purple |
| 4 Civic Park | Bus | teal |
| 5 Dupont | Bus | green |
| 6 Lewis-Selby | Bus | gray |
| 7 Franklin | Bus | brown |
| 8 South Saginaw | Bus | green |
| 9 Lapeer Road | Bus | pink |
List every stop
- MTA Transit Center
- WBD Carpenter at Dort
- WBD Carpenter at Horton
- WBD Pierson at Saginaw
- WBD Pierson at M.L.K
- WBD Pierson at Dupont
- WBD Pierson at Clio
- WBD Pierson at Jennings
- EBD Pierson at Jennings
- EBD Pierson at Clio
- EBD Pierson at Dupont
- EBD Pierson at M.L.K
- EBD Pierson at Saginaw
- EBD Pierson at Selby
- EBD Pierson at Horton
- NBD Dort at Webster
- Webster at Carpenter
- WBD 4655 W Pierson
- EBD 4378 W Pierson
- WBD Pierson at Dolan
- EBD Pierson at Dolan
- WBD 4057 W Pierson
- EBD 4075 W Pierson
- WBD Pierson at Hunter
- WBD Pierson at Minerva
- EBD Pierson at Doran
- WBD Pierson at Doran
- EBD Pierson at Orgould
- WBD Pierson at Orgould
- WBD Pierson at Kelley
- WBD Pierson at Susan
- EBD Pierson at Susan
- WBD Pierson at Glenn
- EBD Pierson at Baldwin
- WBD Pierson at Woodbine
- EBD Pierson at Willis
- WBD Pierson at Willis
- EBD Pierson at Aubrey
- WBD Pierson at Harvard
- WBD Pierson at Summit
- EBD Pierson at Fulton
- WBD Pierson at Fulton
- EBD Pierson at North
- WBD Pierson at North
- EBD Pierson at Industrial
- WBD Pierson at Industrial
- Webster at Hathaway
- Webster at Hillcroft
- EBD Carpenter at Roseanna
- EBD Carpenter at Pemberton
- Harry at Kurtz
- Harry at Humphrey
- Harry at Harvard
- Harry at Princeton
- Harry at Cornell
- Harry at Downey
- Harry at Charles
- Harry at Carpenter
- Selby South of Lorado
- Selby at Rosedale
- Harrison at Kearsley
- NBD Saginaw at 5th
- NBD Saginaw at Father Dukette
- NBD Saginaw at Williams
- NBD Saginaw at Wood
- NBD Saginaw at Mary
- NBD Saginaw at Harriet
- NBD Saginaw at Hamilton
- NBD Saginaw at Warren
- NBD Saginaw at Baker
- NBD Saginaw at Taylor
- NBD Saginaw at Leith
- NBD Saginaw at Jamieson
- NBD Saginaw at Dewey
- NBD Saginaw at Pasadena
- NBD Saginaw at Addison
- NBD Saginaw at Edmund
- NBD Saginaw at Black
- NBD Saginaw at Wager
- NBD Saginaw at Philadelphia
- NBD Saginaw at Pierson
- NBD Saginaw at Parkway
- NBD Saginaw at Mott
- NBD Saginaw at Sherman
- NBD Saginaw at Home
- NBD Saginaw at Russell
- NBD Saginaw at Ruth
- NBD Saginaw at Foss
- NBD Saginaw at Alma
- NBD Saginaw at York
- NBD Saginaw at Carpenter
- NBD Saginaw at Charles
- NBD Saginaw at Downey
- NBD Saginaw at Cass
- NBD Saginaw at Cornell
- NBD Saginaw at Princeton
- NBD Saginaw at Humphrey
- NBD Saginaw south of Clovis
- NBD Saginaw at Terry
- NBD Saginaw at Klein
- NBD Saginaw at Stanley
- NBD Saginaw at Dorothy
- NBD Saginawat Maple
- NBD Saginaw at Mount Morris
- SBD Saginaw at Mount Morris
- SBD Saginaw at Maple
- SBD Saginaw at Nutana
- SBD Saginaw at Stanley
- SBD Saginaw at Klein
- SBD Saginaw at Diane
- SBD Saginaw at Terry
- SBD Saginaw at Coldwater
- SBD Saginaw at Humphrey
- SBD Saginaw at Princeton
- SBD Saginaw at Cass
- SBD Saginaw at Downey
- SBD Saginaw at Knickerbocker
- SBD Saginaw at Carpenter
- SBD Saginaw at York
- SBD Saginaw at Holbrook
- SBD Saginaw at Lorado
- SBD Saginaw at Russell
- SBD Saginaw at Piper
- SBD Saginaw at Hobson
- SBD Saginaw at Mott
- SBD Saginaw at Parkway
- SBD Saginaw at Pierson
- SBD Saginaw at Marengo
- SBD Saginaw at Baltimore
- SBD Saginaw at Flint Park
- SBD Saginaw at Stewart
- SBD Saginaw at Edmund
- SBD Saginaw at Carton
- SBD Saginaw at Pasadena
- SBD Saginaw at Dewey
- SBD Saginaw at Leith
- SBD Saginaw at Dartmouth
- SBD Saginaw at Baker
- SBD Saginaw at Warren
- SBD Saginaw at Hamilton
- SBD Saginaw at Harriet
- SBD Saginaw at Mary
- SBD Saginaw at Wood
- SBD Saginaw at William
- SBD Saginaw at Father Dukette
- SBD Saginaw at 5th
- Church at 3rd
- SBD Saginaw at 1st
- Beach at Kearsley
- 2nd at Saginaw
- NBD Saginaw at 4th
- NBD Saginaw at Patternson
- NBD Saginaw at Damon
- NBD Saginaw at Damon
- NBD Saginaw at Stewart
- NBD Saginaw at Coldwater
- NBD Saginaw at Morris Hills
- Save a Lot
- EBD Court at Avon
- EBD Court at Greenfield
- EBD Court at Dort SW
- EBD Court at Dort SE
- EBD Court West of Railroad
- NBD Center at Klein
- WBD Court at Burlington
- Courtland Center
- EBD Court E of Center
- Center at RT Longway
- NBD Center at Palmer
- NBD Center at Starlite
- NBD Center at Risedorph
- NBD Center at Delaware
- NBD Center at Maryland
- Leith at Center
- Leith at Dexter
- Leith at Averill
- Averill at Montana
- Averill at Wyoming
- Averill at Richfield
- EBD Richfield after Term
- EBD Richfield at Drexel
- EBD Richfield at Mince Manor
- EBD Richfield at Center
- EBD Richfield at Layman
- EBD Richfield at Lanning
- Covert at Richfield
- Covert at Potter
- Covert at Weston
- Covert at Leith
- Covert at Lila
- Covert at Beechwood
- Covert at Risedorph
- Covert at Farm Crest
- Covert at Davison
- WBD Davison at Brians
- SBD Center at Marmion
- SBD Center at Pitkin
- SBD Center at Palmer
- SBD Center at RT Longway
- SBD Center at Gorey
- WBD Court at Commerce
- WBD Court at Halo Burger
- WBD Court at Burlington
- WBD Court at Averill
- WBD Court at Consumers
- WBD Court at Kelso
- WBD Court at Meade
- WBD Court at Greenfield
- WBD Court at Vernon
- WBD Court at Franklin
- WBD Court at Avon
- WBD Court at Stevens
- WBD Court at Harrison
- 2nd at Stevens
- WBD Court at Horrigan
- WBD Court at College
- EBD Court at Beard
- WBD Court at Franklin
- EBD Court at Vernon
- EBD Court at Kelso
- EBD Court at Consumers
- EBD Court at Averill
- MTA Administration Building
- MTA Multimodal station
- EBD Court at Center
- EBD Court at Commerce
- NBD Center at Gorey
- NBD Center at Ivanhoe
- NBD Center at Davison
- 4218 Davison Rd
- WBD Davison at Delaney
- 3rd at Church
- Grand Traverse at Court
- Ann Arbor at 5th
- Ann Arbor at Carrill
- Ann Arbor at 6th
- SBD Fenton at 12th
- SBD Fenten at Barlow
- SBD Fenton at Paddington
- SBD Fenton at Ossington
- SBD Fenton at Barrie
- SBD Fenton at Victoria
- SBD Fenton at Neubert
- SBD Fenton at Lincoln
- WBD Atherton at Tuxedo
- WBD Atherton at Phillis
- 1518 Atherton Rd
- WBD Atherton at Hammerberg
- WBD Atherton at Greenbrook
- SBD Van Slyke at Fisher Hall
- and 924 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 | 45.6 | first check |
| 2026-07-30 | 45.6 | no change |
| 2026-07-31 | 45.6 | no change |
| 2026-08-01 | 45.6 | no change |
What changed since your last check
- Correctness no change
- Freshness no change
- Rider experience no change
Everything we checked
9 findings, ordered by severity.
Show every finding
- Error6 instances
Invalid date (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'invalid_date' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Finding code: invalid_date · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Error1 instance
Service data ended 2405 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)
- Warning1174 instances
1174 of 1174 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)
- Warning51 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)
- Warning6 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)
- 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)
- 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)
- 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. 1 validator error to resolve. Service data expired 2405 days ago, so FTA would find the link out of date.
- Published Ready
- Published at a public URL.
- Valid Needs attention
- 1 validator error to resolve.
- Current Not ready
- Service data expired 2405 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 1452 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. 1 validator error to resolve. Service data expired 2405 days ago. States wheelchair access on 0% of stops and 100% of trips; the mark needs 90% of each.
- Valid Not yet
- 1 validator error to resolve.
- Current Not yet
- Service data expired 2405 days ago.
- Accessible Not yet
- States wheelchair access on 0% of stops and 100% 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. The feed also carries 6 validator errors, the other thing Maps checks at onboarding; the findings below name each fix.
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 56 / 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 68 / 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/mass-transportation-authority-flint/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.