Feed status · checked 2026-08-01
Capital Area Transportation Authority (CATA)
Based on the feed this agency publishes
Service mode Bus
down 0.3 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 3 hours ago; last changed 42 days ago.
Measured 4 of 4 score categories from the agency's own feed.
How we measured this
Confidence in this measurement: high.
- All four score categories were measured this run.
- Realtime was sampled in one bounded window of 9 snapshots.
- 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 with a validity window that reaches at least 60 days out.Likely your export tool
Service data runs out in 22 day(s). When the calendar runs out, trip planners stop showing this agency. Fixing it now is calmer than after riders notice.
⏱ One export setting.worth about +58 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
1335 of 1335 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
7620 of 7620 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 runs out in 22 day(s).
- Next action
- Re-export with a validity window that reaches at least 60 days out.
- 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
- 1335 of 1335 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
- 7620 of 7620 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 with a validity window that reaches at least 60 days out. · 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. See this feed's finding-clearance log.
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. 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
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 22 days.
- 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
- Live-arrival data covered 100% of scheduled trips in the sampled window.
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 8154 instances (0 error, 8154 warning, 0 informational).
Service data runs out in 22 day(s). Publish an updated feed soon or riders will lose trip planning.
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
5 route badge(s) pair a color and text color below the WCAG 4.5:1 contrast bar (01, 10, 12, 14, 31).
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.
765 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set ("SBD Collins Rd @ Post Office", "EBD St Joseph before Waverly (store)", "NBD Grand Ave before E Allegan St", 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.
Sampled 9 times: 3 of 3 configured feeds healthy; 100.0% of scheduled trips had live predictions; 83.3% of vehicles on their route; predictions ran a median of 89s behind schedule.
Routes and stops
Each route is drawn once, using the longest shape its trips follow; stops are the dots.
This feed has 1335 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 (gray)
- 03 (pink)
- 05 (yellow)
- 06 (teal)
- 07 (pink)
- 08 (green)
- 09 (pink)
- 10 (green)
- 11 (red)
- 12 (teal)
- 13 (purple)
- 14 (brown)
- 15 (pink)
- 16 (pink)
- 18 (white)
- 20 (yellow)
- 22 (pink)
- 23 (teal)
- 24 (gray)
- 25 (orange)
- 26 (green)
- 32 (pink)
- 46 (yellow)
- 48 (white)
| Route | Type | Line color |
|---|---|---|
| 01 DOWNTOWN LANSING-MERIDIAN MALL | Bus | blue |
| 02 SOUTH WASHINGTON-PLEASANT GROVE | Bus | gray |
| 03 WILLOW-LANSING MALL | Bus | pink |
| 05 SOUTH CEDAR-EDGEWOOD | Bus | yellow |
| 06 CEDAR - JOLLY CONNECTION | Bus | teal |
| 07 AURELIUS-MILLER | Bus | pink |
| 08 PENNSYLVANIA - HOLT | Bus | green |
| 09 SOUTH MLK - MILLER | Bus | pink |
| 10 NORTH LANSING - TURNER | Bus | green |
| 11 WAVERLY - COLONIAL VILLAGE | Bus | red |
| 12 W. MICHIGAN - WAVERLY - LCC WEST | Bus | teal |
| 13 GROESBECK AREA | Bus | purple |
| 14 NORTH GRAND RIVER-OLD TOWN-AIRPORT | Bus | brown |
| 15 KALAMAZOO - FRANDOR | Bus | pink |
| 16 OLD TOWN - W. LK LANSING - EASTWOOD | Bus | pink |
| 18 CAPITAL CITY CROSSTOWN | Bus | white |
| 20 SOUTH HARRISON - JOLLY - DUNCKEL | Bus | yellow |
| 22 MSU - HASLETT - OKEMOS | Bus | pink |
| 23 MSU - OKEMOS - HASLETT | Bus | teal |
| 24 EAST LANSING - E. LAKE LANSING ROAD | Bus | gray |
| 25 NORTH HARRISON | Bus | orange |
| 26 ABBOT - CHANDLER | Bus | green |
| 30 SOUTH & EAST NEIGHBORHOODS | Bus | purple (no shape in feed) |
| 31 BRODY & EAST NEIGHBORHOODS | Bus | brown (no shape in feed) |
| 32 COMM LOT- SNYDER HALL - CLIN CENTER | Bus | pink |
| 33 UNION - S.NEIGHBORHOOD | Bus | gray (no shape in feed) |
| 34 BRODY NEIGHBORHOOD - UNIV. VILLAGE | Bus | orange (no shape in feed) |
| 35 SOUTH NEIGHBORHOOD | Bus | white (no shape in feed) |
| 36 EAST NEIGHBORHOOD | Bus | gray (no shape in feed) |
| 39 UNIVERSITY VILLAGE | Bus | teal (no shape in feed) |
| 46 MASON LTD | Bus | yellow |
| 48 WILLIAMSTON-WEBBERVILLE LTD | Bus | white |
List every stop
- Meridian Mall
- NBD Abbot past Saginaw
- NBD Main before Grand River
- Mason Meijer
- EBD Burneway before Waverly
- CATA Offices
- NBD Grand past Hillsdale
- NBD Grand Ave before E Allegan St
- Community Mental Health
- NBD Grand Ave past E Michigan Ave
- NBD Grand before Shiawassee St
- NBD Grand past Shiawassee St
- NBD Grand past Saginaw St
- SBD Capitol past Saginaw St
- Family Ind. Agency
- SBD Capitol past Genessee St
- SBD Capitol past Kalamazoo St
- SBD Capitol past Hillsdale
- NBD Walnut past Shiawassee St
- SBD Pine past Genessee St
- SBD Pine St past Ottawa
- EBD Shiawassee past Cedar St
- WBD Shiawassee St at Washington Ave
- WBD Shiawassee before Seymour St
- WBD Shiawassee past Walnut
- WBD Kalamazoo past S Cedar St
- WBD Kalamazoo before Townsend St
- EBD Gr. River past Abbot Rd
- EBD Gr. River Ave past Division St
- EBD Gr. River Ave past Farm Lane
- WBD Gr. River past Collingwood
- WBD Gr. River Ave before Division
- WBD Gr. River past MAC AVE
- SBD Farm past E Circle Dr
- SBD Farm Ln before Auditorium Rd
- Meijer Lake Lansing Boarding Center (East Side)
- EBD Michigan past Grand Ave
- EBD Michigan past Cedar St
- EBD Michigan past Larch St
- EBD Michigan after S Hosmer St
- EBD Michigan past Pennsylvania
- EBD Michigan past Jones St
- EBD Michigan past Holmes St
- EBD Michigan past Lathrop St
- SBD Harrison before Michigan
- EBD Michigan past Sheperd St
- EBD Michigan past Clemens Ave
- EBD Michigan before S Magnolia Av
- EBD Michigan past Foster Ave
- EBD Michigan past Mifflin Ave
- EBD Michigan Ave past Friendship Cl
- EBD Michigan past Highland Ave
- NBD Harrison past Michigan
- EBD Michigan past Brody Rd W
- EBD Michigan past Harrison Rd
- EBD Michigan Ave before Delta St
- EBD Gr. River Ave past Bogue St
- EBD Gr. River Ave past River St
- EBD Gr. River Ave before Spartan Av
- EBD Gr. River Ave past S Hagadorn
- EBD Gr. River Ave at Maplewood Dr
- EBD Gr. River past Brookfield
- EBD Grand River before Dawn
- EBD Gr. River Ave before Park Lake
- EBD Gr. River Ave before Small Acre
- EBD Gr. River Ave past Nakoma Dr
- EBD Gr. River Ave after Grand View
- EBD Gr. River Ave past Okemos Rd
- Okemos Meijer
- WBD Gr. River Ave past Marsh Rd
- WBD Gr. River past Okemos Rd
- WBD Gr. River past Grand View
- WBD Gr. River past Montrose Av
- WBD Gr. River past Mohawk Rd
- WBD Gr. River past Park Lake R
- WBD Gr. River past Northwind D
- WBD Gr. River past E Brookfield
- WBD Gr. River past Maplewood D
- WBD Gr. River past N Hagadorn
- WBD Gr. River past Stoddard Av
- WBD Gr. River past Gunson St
- WBD Gr. River past Kedzie St
- WBD Michigan past Delta St
- WBD Michigan Ave past Louis St
- WBD Michigan past Center St
- WBD Michigan past Kensington
- WBD Michigan past Friendship Cir
- SBD Clippert St before Michigan Ave
- WBD Michigan past Howard Ave
- WBD Michigan past Kipling Blvd
- WBD Michigan past Foster Ave
- WBD Michigan before Magnolia Av
- WBD Michigan past Clemens Ave
- WBD Michigan past Marshall Ave
- WBD Michigan past Custer Ave
- WBD Michigan past Holmes St
- WBD Michigan before Pennsylvani
- WBD Michigan past Hosmer St
- WBD Michigan past Larch St
- WBD Michigan at Museum Drive
- SBD Washington past Hazel St
- SBD Washington past South St
- SBD Washington before Baker St
- SBD Washington past Barnes Ave
- SBD Washington past Mt Hope Av
- SBD Washington past Strathmore R
- SBD Washington past Wayburn Rd
- SBD Washington past Greenlawn Av
- SBD Washington before Dunlap St
- SBD Washington past Hodge Ave
- SBD Washington past Berry Ave
- WBD Holmes past Washington Ave
- WBD Holmes past MLK
- WBD Holmes Rd before Simken Dr
- SBD Pleasant Grove past Holmes Rd
- SBD Pleasant Grove before Wadsworth
- SBD Pleasant Grove before Mary
- SBD Pleasant Grove past Risdale St
- WBD Reo before Sidney St
- WBD Reo past Ingham St
- Brody Complex
- WBD Reo Rd at Wainwright Ave
- NBD Stillwell past Jerree St
- WBD Sumpter before Anson
- WBD Sumpter before Waverly
- WBD Sheffield Blvd past Waverly Rd
- WBD Sheffield past Bayview Dr
- WBD Sheffield before Blue River
- WBD Sheffield past Blue River Dr
- Commuter Lot 89-4
- SBD Seaway past Sheffield Blvd
- SBD Seaway past Glenburne Blvd
- EBD Sumpter past Waverly Rd
- EBD Sumpter past Anson St
- EBD Sumpter before Stillwell Ave
- EBD Ronald before Atlanta Pl
- EBD Reo past Wainwright Ave
- EBD Reo past Ingham St
- NBD Pleasant Grove past Reo Rd
- NBD Pleasant Grove at Risdale St
- NBD Pleasant Grove before Mary Ave
- NBD Pleasant Grove past Hillcrest S
- NBD Pleasant Grove before Holmes
- EBD Holmes past Pleasant Grove
- EBD Holmes past Simkin
- EBD Holmes past MLK
- NBD Washington before Berry Ave
- NBD Washington before Loa St
- NBD Washington past Dunlap St
- NBD Washington before Greenlawn
- NBD Washington past Kensington R
- NBD Washington past Rockford R
- NBD Washington before Mt Hope A
- NBD Washington at Bank St
- NBD Washington past Barnes Ave
- NBD Washington past Baker St
- NBD Washington Ave before South St
- NBD Washington past Elm St
- NBD Washington past Hazel St
- NBD Walnut past Saginaw St
- NBD Walnut past Oakland Ave
- NBD Walnut past Maple St
- NBD Walnut before Willow
- WBD Willow past Chestnut St
- WBD Willow before Christopher St
- WBD Willow past Lansing Ave
- WBD Willow before Glenrose Ave
- WBD Willow past Comfort Ave
- WBD Willow past Cleo St
- WBD Willow past Sunset Ave
- WBD Willow before Eastfield Rd
- WBD Willow past Eastfield Rd
- WBD Willow before Boynton Dr
- WBD Willow past Briarwood Dr
- SBD Morris past Willow St
- SBD Morris past Cornelia Dr
- SBD Morris before Sylvan Ave
- SBD Morris before Upton Rd
- WBD Saginaw past Morris Ave
- WBD Saginaw past Edgemont Blvd
- WBD Saginaw past Waverly Rd
- WBD Saginaw past Thomas L Pkwy
- WBD Saginaw past Clark Rd
- WBD Saginaw past Maycroft Rd
- NBD Elmwood past Saginaw St
- WBD Mall Dr W after Elmwood Rd
- WBD Mall Dr Past Vil. Green Access
- EBD Saginaw past Mall Dr
- Meijer W Saginaw by Gas Station
- EBD Saginaw past Elmwood Dr
- EBD Saginaw past Theo Ave
- EBD Saginaw St past Julian Ave
- EBD Saginaw past Harriet Ave
- EBD Saginaw past Renker Rd
- NBD Morris before Upton Rd
- NBD Morris before Sylvan Ave
- NBD Morris past Timber Dr
- NBD Morris before Willow St
- EBD Willow at Gould
- EBD Willow past Westfield Rd
- EBD Willow past Eastfield Rd
- EBD Willow before Sunset Ave
- EBD Willow past Sunset Ave
- EBD Willow past Jenison Ave
- EBD Willow past Linwood St
- EBD Willow past MLK Jr Blvd
- EBD Willow at Christopher St
- SBD Pine St past W Willow St
- SBD Pine St past W Oakland Ave
- EBD Malcolm X past S Grand Ave
- SBD Cedar past E Elm St
- SBD Cedar past Isbell St
- SBD Cedar past E Mt Hope Ave
- SBD Cedar past E Greenlawn Ave
- SBD Cedar past Paris Ave
- SBD Cedar past E Holmes Rd
- SBD Cedar before E Rouse St
- SBD Cedar past E Cavanaugh Rd
- SBD Cedar past E Potter Ave
- SBD Cedar past E Syringa Dd
- SBD Cedar past E Jolly Rd
- SBD Cedar past Armstrong Rd
- SBD Cedar past E Northrup St
- SBD Cedar past Kaynorth Rd
- SBD Eifert past Deer Run Ln
- SBD Eifert past Wilcox
- EBD Windmill past Rotterdam
- NBD Eifert at Valley Brook Rd
- EBD Doncaster past Aurelius Rd
- EBD Mt Hope past Hagadorn
- NBD Cedar past Cedar Ct
- NBD Cedar past E Elm St
- EBD Kalamazoo past Lathrop St
- EBD Forest past Aurelius Rd
- EBD Forest past Aurora Dr
- EBD Jolly past Aurelius Rd
- WBD Forest past Aurora Rd
- WBD Kalamazoo past Shepard
- WBD Kalamazoo past Hosmer
- NBD Pennsylvania past Maplehill
- NBD Pennsylvania at Irvington Ave
- EBD Shiawassee near Dorrance Pl
- Lansing Mall
- NBD N East past Howe
- EBD Thomas past Turner St
- EBD Thomas past Gary Ave
- EBD Thomas at Hall St
- SBD High past Lake Lansing
- SBD Pennsylvania past Porter St
- EBD Shiawassee past MLK
- and 1085 more (see the full list on the map or in the GeoJSON)
Over time
Overall score across the last 4 checks — down 0.3 since 2026-07-31.
Show the numbers
| Check | Score | Change |
|---|---|---|
| 2026-07-25 | 60.1 | first check |
| 2026-07-30 | 58.5 | down 1.6 |
| 2026-07-31 | 58.1 | down 0.4 |
| 2026-08-01 | 57.8 | down 0.3 |
What changed since your last check
- Correctness no change
- Freshness down 1.6
- Rider experience no change
- Realtime quality no change
What changed over time
On 2026-07-25 this feed started at grade D. On 2026-07-30 the grade moved from D to F. As of 2026-08-01 it holds grade F.
A plain-language history of this feed, newest first.
- 2026-07-30 Grade went D to F, freshness fell 8 points.
Everything we checked
14 findings, ordered by severity.
Show every finding
- Warning7620 instances
7620 of 7620 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)
- Warning7448 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)
- Warning1335 instances
1335 of 1335 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)
- Warning683 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)
- Warning204 instances
204 of 7620 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)
- Warning18 instances
Some stops sit far from the route line, going by the feed's own distance values.
Trip planners may draw the route down the wrong streets or point riders to the wrong corner.
Fix: Check the flagged stops' shape_dist_traveled against the route shape, and re-generate it on export if they disagree. (Usually an export-tool fix, not hand editing.)
Finding code: stop_too_far_from_shape_using_user_distance · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning2 instances
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
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
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 · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning1 instance
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
Service data runs out in 22 day(s).
When the calendar runs out, trip planners stop showing this agency. Fixing it now is calmer than after riders notice.
Fix: Re-export with a validity window that reaches at least 60 days out. (One export setting.)
Finding code: scorecard_feed_expiring_soon · Read the fix guide · See GTFS Best Practices (opens GTFS Best Practices 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
1 of 6 sampled vehicle positions were far from their assigned route (worst: 265 m).
A bus shown off its route usually means a wrong trip assignment; riders watch their bus drive the wrong streets.
Fix: Ask your AVL vendor to check vehicle-to-trip assignments for the flagged trips. (A vendor support ticket with the trip ids attached.)
Finding code: scorecard_rt_vehicles_off_route
- 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 Needs attention
This feed is close to NTD-ready. Service data runs out in 22 days; renew before you certify.
- Published Ready
- Published at a public URL.
- Valid Ready
- Passes validation with no errors.
- Current Needs attention
- Service data runs out in 22 days; renew before you certify.
- 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) Equal
- This feed's agency_id also equals its NTD ID (50036). Equality is allowed but not required; keep the value stable and retain the P-50 crosswalk.
- shapes.txt covers your trips Ready
- All 7620 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 runs out in 22 days; renew to qualify. 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 runs out in 22 days; renew to qualify.
- 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.
Realtime reliability
The realtime feed responded on 100.0% of 200 checks over the last 34 days, with 10s median lag.
Sampled on a schedule between full scores, so this tracks uptime and freshness over time rather than at a single moment.
Live predictions vs schedule
Arrival predictions ran a median 89s late versus the schedule, and stayed within 275s nine times in ten. They were on time (about a minute early to five late) 86.8% of the time. 83.3% of reported vehicle positions sat on or near the published route shape.
From the last full realtime sample: how far live arrival predictions sat from the schedule, and whether vehicle positions fell on the route. These feed the realtime score; they change no other category.
At risk for the Google and Apple Maps four-week coverage bar. This feed has 21 days of service left. Maps needs at least four weeks (28 days) of upcoming service, so your agency will fall out of trip planners soon. Re-export with a longer calendar.
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 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 37 / 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 98 / 100
- 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/capital-area-transportation-authority-cata/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.