Feed status · checked 2026-08-01
Muncie Indiana Transit System (MITS)
Based on the feed this agency publishes
Service mode Bus
unchanged since 2026-07-31
Catalogued in Indiana.
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 72 minutes ago; last changed 41 days ago.
Measured 3 of 4 score categories from the agency's own feed.
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 agency's own URL.
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 3514 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
717 of 717 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
2165 of 2165 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 3514 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
- 717 of 717 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
- 2165 of 2165 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 3514 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 822 instances (0 error, 822 warning, 0 informational).
Service data ended 3514 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.
2 accessibility depth signals
2 route badge(s) pair a color and text color below the WCAG 4.5:1 contrast bar (Industry Willard, Ball State University).
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.
699 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set ("JACKSON/WALNUT", "JACKSON/MULBERRY", "MAIN/MULBERRY", 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 717 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.
- East Jackson (pink)
- Ball State University (red)
- Ball State Jackson (pink)
- Northwest Plaza (blue)
- Whitely/Morningside (yellow)
- North Walnut (orange)
- Burlington (yellow)
- Industry Willard (red)
- Heekin Park (orange)
- Southway Centre (blue)
- Ivy Tech (purple)
- Riverside/Rural King (purple)
- Walmart (green)
- Mall (green)
| Route | Type | Line color |
|---|---|---|
| East Jackson | Bus | pink |
| Ball State University | Bus | red |
| Ball State Jackson | Bus | pink |
| Northwest Plaza | Bus | blue |
| Whitely/Morningside | Bus | yellow |
| North Walnut | Bus | orange |
| Burlington | Bus | yellow |
| Industry Willard | Bus | red |
| Heekin Park | Bus | orange |
| Southway Centre | Bus | blue |
| Ivy Tech | Bus | purple |
| Riverside/Rural King | Bus | purple |
| Walmart | Bus | green |
| Mall | Bus | green |
List every stop
- MITS STATION
- UNIVERSITY & RESERVE
- JACKSON & HODSON
- JACKSON & COUNTRY CLUB
- UNIVERSITY & MCKINLEY
- GILBERT & TILLOTSON
- MORRISON & PEACHTREE
- MCKINLEY & JACKSON
- WHITE RIVER PLAZA
- MARSH
- YOC
- CENTENNIAL & WHEELING
- OAKWOOD & WHEELING
- NORTHWEST PLAZA
- MUNCIE MALL
- MUNCIE PLAZA
- LOWELL & MLK
- ELGIN & STREETER
- MCGALLIARD & BELLAIRE
- K-MART
- WALNUT & STREETER
- WALNUT & SKYWAY
- ONTARIO & SUPERIOR
- HACKLEY & KIRBY
- BURLINGTON & MEEKER
- MANHATTAN & 16TH
- MADISON & WILLARD
- MACEDONIA & MEMORIAL
- WALMART SOUTH
- MADISON & 8TH
- MEMORIAL & HACKLEY
- 29TH/EBRIGHT
- WALNUT & 15TH
- SOUTHERN PINES
- 8TH/HOYT
- IVY TECH
- RIVERSIDE & TILLOTSON
- MCGALLIARD & TILLOTSON
- SILVERTREE APARTMENTS
- WALMART NORTH
- MARLEON & BETHEL
- CLARK/12TH
- MADISON & 26TH
- MADISON AND MEMORIAL
- WALNUT & MADISON
- 17TH & HOYT
- ELM & GRANVILLE
- MORRISON RD & BAKER LN
- WASHINGTON/HIGH
- WYSOR/HIGH/FRANKLIN
- NORTH/WHITE RIVER/WHEELING
- UNIVERSITY/WHEELING
- ASHLAND/WHEELING
- RIVERSIDE/WHEELING
- QUEEN/WHEELING
- MINNETRISTA/WHEELING
- NEELY/MINNETRISTA/WHEELING
- MARSH/WHEELING
- REX/WHEELING
- UNDWETH/WHEELING
- *UNIVERSITY/RESERVE
- UNIVERSITY/PAULINE
- UNIVERSITY/LINDEN
- UNIVERSITY/LOCUST
- UNIVERSITY/LIGHT
- UNIVERSITY/GREENWOOD
- UNIVERSITY/DICKS
- UNIVERSITY/DILL
- UNIVERSITY/MARTIN
- UNIVERSITY/CALVERT
- UNIVERSITY/TALLEY
- UNIVERSITY/CAMPUS
- UNIVERSITY/CAMPUS (2)
- UNIVERSITY/MANNING
- GILBERT/MANNING
- MAIN/TILLOTSON
- JACKSON/TILLOTSON
- JACKSON/RILEY
- JACKSON/WESTVIEW
- JACKSON/NORMANDY
- JACKSON/IVYWOOD
- JACKSON/STONEGATE
- JACKSON/BITTERSWEET
- JACKSON/WOODWAY
- WOODWAY/MERRYWOOD
- WOODWAY/STRADLING
- GARVER/STRADLING
- GARVER/TREEVIEW
- GARVER/HAWTHORNE
- GARVER/REDWOOD
- GARVER/BIRCHWOOD
- GARVER/MORRISON
- UNNANMED/MORRISON
- PEACHTREE/RAMBLER
- PEACHTREE/HAWTHORNE
- PEACHTREE/GREENTREE
- PEACHTREE/PASTURE
- PEACHTREE/STRADLING
- JACKSON/STRADLING
- 3RD/MADISON
- KILGORE/TILLOTSON
- TILLOTSON OVERPASS/WHITE RIVER
- WHITE RIVER/TILLOTSON
- ETHEL/UNNAMED
- ETHEL/TILLOTSON
- WHITE RIVER/CELIA
- WHITE RIVER/BRITTAIN
- WHITE RIVER/HUTCHINSON
- CROMER/WALNUT
- GODMAN/NICHOLS
- CHARLES/NICHOLS
- ADAMS/NICHOLS
- JACKSON/NICHOLS
- MAIN/NICHOLS
- WASHINGTON/NICHOLS
- GILBERT/NICHOLS
- GILBERT/TALLEY
- GILBERT/COLLEGE
- GILBERT/MCKINLEY
- WASHINGTON/MCKINLEY
- MAIN/MCKINLEY
- JACKSON/CALVERT
- JACKSON/MARTIN
- JACKSON/DILL
- JACKSON/DICKS
- JACKSON/GRACELAND
- JACKSON/WHITE RIVER
- JACKSON/MAIN (2)
- JACKSON/PROUD
- JACKSON/KILGORE
- ADAMS/KILGORE
- CHARLES/KILGORE
- POWERS/KILGORE
- POWERS/ROSS
- POWERS/WILSON/PIERCE
- POWERS/BIRCH
- POWERS/ELLIOTT
- POWERS/PROUD
- POWERS/MOUND
- POWERS/GHARKEY
- POWERS/COUNCIL
- HOWARD/COUNCIL
- CHARLES/COUNCIL
- ADAMS/COUNCIL
- ADAMS/CHERRY
- ADAMS/LIBERTY
- ADAMS/FRANKLIN
- ADAMS/HIGH
- ETHEL/VARSITY
- MCGALLIARD/ROSEWOOD
- WOODMONT/ROSEWOOD
- HARVARD/WHEELING
- YALE/ROSEWOOD/WHEELING
- PURDUE/WHEELING
- SHEFFIELD/OAKWOOD
- BARCELONA/OAKWOOD
- PURDUE/OAKWOOD (2)
- PURDUE/OAKWOOD
- VERNON/OAKWOOD
- W BRYDEN/OAKWOOD
- NORWOOD/OAKWOOD
- HARVARD/OAKWOOD
- WOODMONT/OAKWOOD
- MCGALLIARD/OAKWOOD
- W ROYALE/OAKWOOD
- W ROYALE/ROSEWOOD
- ROYALE/STIRLING/GLENN ELLYN
- *ROYALE/WHEELING (NORTHWEST PLAZA)
- HAINES/WHEELING
- COWING/WHEELING
- WAID/WHEELING
- CROMER/WHEELING
- WEBER/WHEELING
- BETHEL/WHEELING
- WILLS/WHEELING
- MCGALLIARD/WALNUT
- ANDOVER/WALNUT
- BERKLEY/WALNUT
- CENTENNIAL/WALNUT
- WYSOR/MULBERRY
- WYSOR/JEFFERSON
- MYRTLE/ELM
- DARTMOUTH/WALNUT
- HARVARD/WALNUT
- CHARTER/WALNUT
- BROOKLYN/WALNUT
- AIRPARK/WALNUT
- AIRPARK/ONTARIO
- OLDFIELD/WALNUT
- MCGALLIARD/GRANVILLE
- DUNN/GRANVILLE
- LINDA LAYNE/GRANVILLE
- STREETER/GRANVILLE
- KOHLMETZ/ELM
- BIDWELL/ELM
- HIGHLAND/ELM
- MCCULLOCH/ELM
- COLUMBUS/ELM
- RACE/ELM
- WYSOR/ELM
- NORTH/ELM
- GILBERT/ELM
- WASHINGTON/ELM
- WASHINGTON/JEFFERSON
- WASHINGTON/MULBERRY
- MAIN/MULBERRY
- JACKSON/MULBERRY
- JACKSON/WALNUT
- PRINCETON/MALL PARKING
- UNNAMED/ELM
- HAINES/WALNUT
- CHATEAU/WALNUT
- ROOSEVELT/WALNUT
- WARD/WALNUT
- DAVIDSON/WALNUT
- SAINT JOSEPH/WALNUT
- HIGHLAND/WALNUT
- MCCULLOCH/GRANVILLE/WALNUT
- MAPLE/WALNUT
- MYRTLE/WALNUT
- COLUMBUS/WALNUT
- WYSOR/WALNUT
- NORTH/WALNUT
- GILBERT/WALNUT
- GILBERT/MULBERRY
- JACKSON/BUNCH
- JACKSON/MAIN
- MAIN/MACEDONIA
- MAIN/LINCOLN
- MAIN/BRADY
- MAIN/WOLFE
- KIRBY/BLAINE
- KIRBY/WOLFE
- KIRBY/BRADY
- KIRBY/BURLINGTON/OHIO/MACEDONIA
- BURLINGTON/WINDSOR
- BURLINGTON/SHIPLEY
- BURLINGTON/KOONTZ
- BURLINGTON/BROTHERTON
- BURLINGTON/RIBBLE
- BURLINGTON/WILLARD/LUICK
- 8TH/MEEKER
- 9TH/MEEKER
- MEMORIAL/MEEKER
- MEMORIAL/WALL
- MEMORIAL/ROSEMONT
- MEMORIAL/MAY
- MEMORIAL/MANHATTAN
- CENTENNIAL/ELM
- 14TH/MANHATTAN
- and 467 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 | 29.5 | first check |
| 2026-07-30 | 29.5 | no change |
| 2026-07-31 | 29.5 | no change |
| 2026-08-01 | 29.5 | 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 3514 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)
- Warning2165 instances
2165 of 2165 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)
- Warning2165 instances
2165 of 2165 trips lack rider-facing destination or direction text.
When a route has multiple directions or patterns, the route name alone may not tell riders which service is coming.
Fix: Add the destination, direction, or 'via' label riders actually see to trip_headsign. Do not copy the route name. If the label changes during the trip, use stop_headsign. (Usually one value per route pattern in your scheduling source.)
Finding code: scorecard_missing_headsigns · Read the fix guide · See GTFS Best Practices (opens GTFS Best Practices on an external site)
- Warning717 instances
717 of 717 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)
- Warning712 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)
- Warning84 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)
- Warning22 instances
Some stops sit far from the route line they belong to.
Trip planners may draw the bus route through the wrong streets or point riders to the wrong corner.
Fix: Check the flagged stops' coordinates and the route shape in your scheduling software; re-snap whichever is misplaced. (A few minutes per flagged stop.)
Finding code: stop_too_far_from_shape · 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)
- Warning1 instance
On some trips the stops fall along the route line in a different order than the schedule lists.
Trip planners can draw the bus doubling back or skipping ahead, which confuses riders reading the map.
Fix: Check the stop order and the shape direction in your scheduling software; the shape is often drawn backwards. (A few minutes per flagged trip.)
Finding code: stops_match_shape_out_of_order · 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
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)
- Info716 instances
About 716 stop names are written in ALL CAPS.
Mixed-case names are easier to read in apps and are read more naturally by screen readers.
Fix: Rename stops to mixed case where the language has letter case (for example, 'Central Station'). (Often a bulk fix in your scheduling software.)
Finding code: scorecard_stop_names_all_caps · Read the fix guide · See GTFS Best Practices (opens GTFS Best Practices 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 3514 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 3514 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 2165 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 3514 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 3514 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.
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 62 / 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 8 / 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/muncie-indiana-transit-system-mits/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.