Prep for a call: printable one-page brief · For your board packet: printable one-pager · Fix log: every issue this feed has cleared · Compare with another agency · Watch this feed: get an email before it expires
Feed status · checked 2026-07-09
Capital Area Transit System (CATS)
Based on the feed this agency publishes
unchanged since 2026-07-08
Ahead of 24% of all tracked agencies and 37% of large agencies. Operates in Louisiana.
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.1, validator 8.0.1.
Checked for changes 16 minutes ago; last fetch returned HTTP 404.
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
Confirm your next service period is published: export its calendar and set feed_info feed_end_date past it.Likely your export tool
The published calendar ended 140 day(s) ago at a boundary between the feed's own scheduled service periods. The calendar encodes distinct service periods (like academic terms), so this looks like a planned transition rather than a lapse — but trip planners still show nothing until the next period is published.
⏱ One export when the next period's schedule is set.worth about +50 points
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
1596 of 1596 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
Set wheelchair_accessible on every trip (most small-agency fleets are 100% accessible, so this is often a single default).Likely your export tool
2372 of 2372 trips don't say whether the vehicle is wheelchair accessible. Even with accessible stops, riders need to know the bus itself can take them.
⏱ Often one default setting in your export.worth about +15 points
Agencies here usually clear this within about 1 week (based on 5 observed fixes).
This feed is published from a code repository, so whoever maintains that repository regenerates the zip — often planning staff or a consultant. The fix happens in the source data, then a fresh export is committed.
Close the loop on each fix. Read the guide, make the change in your tool, and let the next run verify it — the scorecard shows the fix; the agency publishes it.
Confirm your next service period is published: export its calendar and set feed_info feed_end_date past it.
Make the change. This feed is published from a code repository, so whoever maintains that repository regenerates the zip — often planning staff or a consultant. The fix happens in the source data, then a fresh export is committed.
Prove it cleared. The next scorecard run re-checks this automatically and, once it is gone, mints a dated receipt. See this feed's dated fix 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. This feed is published from a code repository, so whoever maintains that repository regenerates the zip — often planning staff or a consultant. The fix happens in the source data, then a fresh export is committed.
Prove it cleared. The next scorecard run re-checks this automatically and, once it is gone, mints a dated receipt. See this feed's dated fix log.
Set wheelchair_accessible on every trip (most small-agency fleets are 100% accessible, so this is often a single default). · Read the fix guide
Make the change. This feed is published from a code repository, so whoever maintains that repository regenerates the zip — often planning staff or a consultant. The fix happens in the source data, then a fresh export is committed.
Prove it cleared. The next scorecard run re-checks this automatically and, once it is gone, mints a dated receipt. See this feed's dated fix log.
Send your vendor a fix request
This feed is published from a code repository. Forward this to whoever maintains that repository; the fix happens in the source data, then a fresh export is committed. Each fix names the validator notice and a guide link.
Score by category
The MobilityData validator flagged 11 kinds of issue across 58 instances (0 error, 49 warning, 9 informational).
This feed's calendar reached a scheduled service boundary 140 day(s) ago. Confirm your next service period is published so riders can keep planning trips.
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.
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.
Skip to route and stop dataBasemap: OpenFreeMap, © OpenStreetMap contributors. Routes and stops: this agency's GTFS feed.
- 008 (green)
- 021 (green)
- 022 (green)
- 023 (green)
- 041 (green)
- 044 (green)
- 046 (green)
- 047 (green)
- 054 (green)
- 010 (green)
- 057 (green)
- 058 (green)
- 059 (green)
- 060 (green)
- 070 (green)
- 011 (green)
- 015 (green)
- 012 (green)
- 014 (green)
- 017 (green)
- 018 (green)
- 020 (green)
| Route | Type | Line color |
|---|---|---|
| 008 Gus Young / BRCC | Bus | green |
| 021 Fairfields Ave. - Cortana Mall | Bus | green |
| 022 Winbourne Ave. - Cortana Mall | Bus | green |
| 023 Foster Dr. | Bus | green |
| 041 Plank Rd. | Bus | green |
| 044 Florida Blvd. - Cortana Mall | Bus | green |
| 046 Cortana/Gardere/L'Auberge | Bus | green |
| 047 Highland Rd. | Bus | green |
| 054 Airline Hwy. North / Southern Univ. | Bus | green |
| 010 Scenic Hwy. / Southern Univ. | Bus | green |
| 057 Sherwood Forest Blvd. | Bus | green |
| 058 Coursey Blvd. / O'Neal Ln. | Bus | green |
| 059 East Florida Blvd. / O'Neal Ln. | Bus | green |
| 060 Medical Circulator | Bus | green |
| 070 Baker /Southern Univ. / CATS Terminal | Bus | green |
| 011 Northside Circulator | Bus | green |
| 015 Blount Rd | Bus | green |
| 012 Government St. / Jefferson Hwy. | Bus | green |
| 014 Thomas Delpit Dr. | Bus | green |
| 017 Perkins Rd. - Mall of Louisiana | Bus | green |
| 018 LSU - Cortana Mall | Bus | green |
| 020 North Acadian Throughway | Bus | green |
This feed has 1596 stops.
List every stop
- CATS Terminal
- Cortana Pl Walmart Transfer Center - W
- Earl K. Long Transfer Center - N
- Mall of Louisiana
- North St @ 23rd St - E
- North St @ 25th St - E
- North St @ Eugene - E
- North St @ Gebelin - E
- North St @ Connell - E
- North St @ N Acadian - E
- North St @ Saguaro - E
- 39th @ North St - N
- 39th @ Jonah - N
- 39th @ Zion - N
- 39th @ Billops - N
- Gus Young @ 40th St - E
- Gus Young @ Capitol Elementary - E
- Gus Young @ 44th St - E
- Gus Young @ Columbus Dunn - S
- Columbus Dunn @ Odell - S
- Columbus Dunn @ Jonah - S
- Columbus Dunn @ 44th - S
- North St @ Turner Plaza - E
- North St @ 49th St - E
- Foster Dr @ Laurel - S
- Foster Dr @ Laurel - N
- North St @ N 48th - W
- North St @ Columbus Dunn - W
- Columbus Dunn @ Jonah - N
- Columbus Dunn @ Odell - N
- Columbus Dunn @ Gus Young - N
- Gus Young @ 43rd St - W
- Gus Young @ Capitol Elementary - W
- Gus Young @ 40th St - W
- 39th @ Cain - S
- 39th @ Odell - S
- 39th @ Zion - S
- 39th @ Jonah - S
- 39th @ North St - S
- North St @ 36th - W
- North St @ N Acadian - W
- North St @ 32nd St - W
- North St @ 30th St - W
- North St @ 27th St - W
- North St @ 25th St - W
- North St @ 23rd St - W
- Scenic @ Spanish Town - N
- Scenic @ Fuqua - N
- Scenic @ Plank - N
- Scenic @ Bellvale - N
- Scenic @ Birch - N
- Scenic @ Shawnee - N
- Scenic @ Pawnee - N
- Scenic @ Adams - N
- Scenic @ Monroe - N
- Scenic @ Iroquois - N
- Scenic @ Chippewa - N
- Scenic @ Ontario - N
- Scenic @ Winbourne - N
- Scenic @ Calumet - N
- Scenic @ Wyandotte - N
- Scenic @ Mohican - N
- Scenic @ Weller - N
- Scenic @ Dayton - N
- Scenic @ Cable - N
- Scenic @ Evangeline/Galvez - N
- Scenic @ Lorraine - N
- Scenic @ Hollywood - N
- Scenic @ Shada - N
- Scenic @ Mason - N
- Scenic @ Kaufman - N
- Scenic @ 69th - N
- Scenic @ 72nd - N
- Scenic @ 74th - N
- Scenic @ 77th - N
- Scenic @ 78th - N
- Scenic @ 79th - N
- Harding Blvd @ Mini Dome - W
- Swan @ Mini Dome - E
- Scenic @ Fairchild - S
- Scenic @ Curtis St - S
- Scenic @ Palisades - S
- Scenic @ 78th - S
- Scenic @ 76th - S
- Scenic @ Scotlandville Library - S
- Scenic @ 72nd - S
- Scenic @ 70th - S
- Scenic @ 68th - S
- Scenic @ Kaufman - S
- Scenic @ Mason - S
- Scenic @ Hollywood - S
- Scenic @ Iberia - S
- Scenic @ Dayton - S
- Scenic @ Mohican - S
- Scenic @ Ontario - S
- Scenic @ Chippewa - S
- Scenic @ Seneca - S
- Scenic @ Choctaw - S
- Scenic @ Monroe - S
- Scenic @ Adams - S
- Scenic @ Hemlock - S
- Scenic @ Chestnut - S
- Scenic @ Birch - S
- Scenic @ Ellerslie - S
- Scenic @ Foss - S
- Scenic @ Fuqua - S
- Scenic @ Spanish Town - S
- 4th @ north of Florida Blvd - S
- Airline @ New Life Ministries - N
- McClelland @ Maplewood - N
- McClelland @ Glen Oaks - N
- Glen Oaks @ Ash - E
- Glen Oaks @ Bluegrass - E
- Bluegrass @ Sumrall - E
- Bluegrass @ W Upland - N
- Bluegrass @ W Monarch - N
- Bluegrass @ Cadillac - N
- Cadillac @ Apperson - W
- Cadillac @ Simplex - W
- Cadillac @ Stutz - W
- Cadillac @ Kissel - W
- Cadillac @ Moon - W
- Cadillac @ Plank - W
- 72nd @ Winnfield Funeral Home - S
- 72nd @ Memorial Park - W
- 72nd @ Howell - W
- 72nd @ YMCA - W
- 72nd @ Yorkshire - W
- 72nd @ Nottingham - W
- 72nd @ Middlesex - W
- 72nd @ Pembroke - W
- 72nd @ Goode - W
- 72nd @ Somerset - W
- 72nd @ Scenic - W
- Scenic Hwy @ Harding Blvd - N
- Scenic Hwy @ Curtis St - N
- Scenic Hwy @ Fairchild - N
- Scotland @ Swan - N
- Hwy 19 @ Robin St - N
- Hwy 19 @ Stilt - N
- Hwy 19 @ Oriole - N
- Hwy 19 @ Fraternity - N
- Hwy 19 @ Rosenwald Rd - N
- Scotland @ Scotlandville High School - N
- Blount @ Scotland - W
- Blount @ Tallow - W
- Blount @ Scenic/Canada - W
- Blount @ Kingfisher - W
- Blount @ Ave D - W
- Blount @ Ave F - W
- Blount @ Ave G - W
- Mills @ Scenic Hwy - S
- Scenic Hwy @ Bittern - S
- Scenic Hwy @ W.K. Gordon - S
- Scenic Hwy @ Baranco - S
- Scenic Hwy @ Goose St - S
- Scenic Hwy @ Grebe St - S
- Scenic Hwy @ Sparrow St - S
- Scenic Hwy @ Swan Ave - S
- Swan @ Leon Netterville - W
- Leon Netterville @ Comptroller Office - S
- Harding Blvd @ Elton C Harrison - E
- Harding Blvd @ Teacher's Parents CU - E
- Harding @ Mini Dome - E
- 72nd @ Scenic - E
- 72nd @ Somerset - E
- 72nd @ Goode - E
- 72nd @ Pembroke - E
- 72nd @ Middlesex - E
- 72nd @ Nottingham - E
- 72nd @ Yorkshire - E
- 72nd @ Howell - E
- 72nd @ Howell Place Apartments - E
- 72nd @ Plank - E
- Cadillac @ Moon - E
- Cadillac @ Kissel - E
- Cadillac @ Stutz - E
- Cadillac @ Apperson - E
- Cadillac @ White - E
- Bluegrass @ Cadillac - S
- Bluegrass @ W Monarch - S
- Bluegrass @ W Perimeter - S
- Bluegrass @ Sumrall - S
- Bluegrass @ Glen Oaks - S
- Greenwell @ Urban Restoration Apts - W
- Greenwell @ Quida Mae - W
- Greenwell St @ Airline Hwy - N
- Elm Grove @ Central Rd - S
- Central Rd @ Jewel Newman Center - W
- Central Rd @ Elm Grove - E
- Swan @ Kingfisher - W
- Swan @ Isabel Herson - W
- St Ferdinand @ Louisiana - S
- Government @ Eddie Robinson - E
- 22nd @ Louisiana - N
- 22nd @ North Blvd - N
- 22nd @ Government - W
- Government @ Eugene - E
- Government @ Hearthstone - E
- Government @ Acadian Thwy - E
- Government @ Mouton - E
- Government @ Foster - E
- Government @ Franklin - E
- Government @ Ardenwood - E
- Government @ Apartment Ct Dr - E
- Jefferson @ After Corporate - E
- Jefferson @ Mc Carroll - E
- Jefferson @ Argosy - E
- Jefferson @ Brandon - E
- Jefferson @ Owen - E
- Jefferson @ Wrenwood - E
- Jefferson @ Brentwood - E
- Jefferson @ Drusilla Shopping Center - E
- Jefferson @ Drusilla - E
- Jefferson @ Jefferson Heights Apts - E
- Jefferson @ Jefferson Baptist Church - E
- Jefferson @ Bluebonnet Rd - E
- Bluebonnet @ Jefferson - S
- Bluebonnet @ Oliphant - S
- Bluebonnet @ Cal - S
- Bluebonnet @ Blue Cross Pkwy - N
- Bluebonnet @ Blue Cross Pkwy - S
- Bluebonnet @ Gail - N
- Bluebonnet @ Cal - N
- Bluebonnet @ Oliphant - N
- Bluebonnet @ Jefferson - N
- Jefferson @ Bluebonnet Rd - W
- Jefferson @ Jefferson Baptist Church - W
- Jefferson @ Jefferson Heights Apts - W
- Jefferson @ Drusilla Shopping Center - W
- Jefferson @ Fairway - W
- Jefferson @ Essen - W
- Jefferson @ Brentwood - W
- Jefferson @ Mcllhenny - W
- Jefferson @ Wrenwood - W
- Jefferson @ Jefferson Pl Blvd - W
- Jefferson @ Owen - W
- Jefferson @ Brandon - W
- Jefferson @ After Argosy - W
- Jefferson @ Mc Carroll - W
- Jefferson @ Corporate - W
- Lobdell @ Lasalle - N
- Lobdell @ Sevenoaks - N
- Government @ Croydon - W
- Government @ Apartment Ct - W
- Government @ Ardenwood - W
- Government @ Community College Dr - W
- Government @ Foster - W
- Government @ Edison - W
- Government @ Acadian - W
- and 1346 more (see the full list on the map or in the GeoJSON)
Over time
Overall score across the last 20 checks — unchanged since 2026-07-08.
Show the numbers
| Check | Score | Change |
|---|---|---|
| 2026-06-19 | 37.4 | first check |
| 2026-06-20 | 37.4 | no change |
| 2026-06-21 | 37.4 | no change |
| 2026-06-22 | 37.4 | no change |
| 2026-06-23 | 37.4 | no change |
| 2026-06-24 | 37.4 | no change |
| 2026-06-25 | 37.4 | no change |
| 2026-06-26 | 37.4 | no change |
| 2026-06-27 | 37.4 | no change |
| 2026-06-28 | 37.4 | no change |
| 2026-06-29 | 37.4 | no change |
| 2026-06-30 | 37.4 | no change |
| 2026-07-01 | 37.4 | no change |
| 2026-07-02 | 37.4 | no change |
| 2026-07-04 | 46.2 | up 8.8 |
| 2026-07-05 | 46.2 | no change |
| 2026-07-06 | 46.2 | no change |
| 2026-07-07 | 46.2 | no change |
| 2026-07-08 | 46.2 | no change |
| 2026-07-09 | 46.2 | 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-08.
Same feed file as 2026-07-08; 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.
What changed over time
On 2026-06-19 this feed started at grade F. On 2026-07-04 it cleared scorecard_feed_expired. As of 2026-07-09 it holds grade F.
A plain-language history of this feed, newest first.
- 2026-07-04 Score rose 9 points, freshness rose 35 points.
Everything we checked
- Warning2372 instances
2372 of 2372 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 (most small-agency fleets are 100% accessible, so this is often a single default). (Often one default setting in your export.)
Agencies here usually clear this within about 1 week (based on 5 observed fixes).
Validator rule: scorecard_wheelchair_accessible_unknown · Read the fix guide · See GTFS Schedule reference (opens the GTFS Schedule reference on an external site)
- Warning1596 instances
1596 of 1596 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.)
Validator rule: scorecard_wheelchair_boarding_unknown · Read the fix guide · See GTFS Schedule reference (opens the GTFS Schedule reference on an external site)
- Warning23 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.)
Agencies here usually clear this within about 2 weeks (based on 8 observed fixes).
Validator rule: missing_recommended_field · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning12 instances
Equal shape distance same coordinates (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'equal_shape_distance_same_coordinates' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Validator rule: equal_shape_distance_same_coordinates · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning3 instances
Some service calendars in the feed have already ended.
Expired calendars are dead weight and can hide real schedule problems from your staff and vendors.
Fix: Remove past service periods the next time you export the feed. (One setting in most export tools.)
Agencies here usually clear this within about 1 week (based on 61 observed fixes).
Validator rule: expired_calendar · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning3 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.)
Agencies here usually clear this within about 2 weeks (based on 6 observed fixes).
Validator rule: stop_too_far_from_shape · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning3 instances
Stop too far from shape using user distance (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'stop_too_far_from_shape_using_user_distance' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Agencies here usually clear this within about 1 week (based on 6 observed fixes).
Validator rule: 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
Stops match shape out of order (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'stops_match_shape_out_of_order' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Agencies here usually clear this within about 1 week (based on 6 observed fixes).
Validator rule: stops_match_shape_out_of_order · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning1 instance
A file GTFS asks for (usually feed_info.txt) is missing.
feed_info.txt tells apps who publishes the feed and when it expires; without it nobody is warned before data goes stale.
Fix: Add feed_info.txt with publisher name, URL, language, and feed_start_date/feed_end_date. (One small file, set once in export settings.)
Agencies here usually clear this within about 1 week (based on 13 observed fixes).
Validator rule: missing_recommended_file · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning1 instance
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.)
Validator rule: mixed_case_recommended_field · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning1 instance
Many of the feed's trips don't run at all in the next 7 days.
It usually means old service periods are still in the export, making the feed bigger and harder to check.
Fix: Trim past service periods the next time you export. (One setting in most export tools.)
Agencies here usually clear this within about 1 week (based on 31 observed fixes).
Validator rule: 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 published calendar ended 140 day(s) ago at a boundary between the feed's own scheduled service periods.
The calendar encodes distinct service periods (like academic terms), so this looks like a planned transition rather than a lapse — but trip planners still show nothing until the next period is published.
Fix: Confirm your next service period is published: export its calendar and set feed_info feed_end_date past it. (One export when the next period's schedule is set.)
Validator rule: scorecard_planned_service_boundary
- Warning1 instance
feed_info.txt is missing its start/end dates (the file itself is absent)
Apps and this scorecard can't warn anyone before the feed goes stale without stated validity dates.
Fix: Add feed_info.txt with feed_start_date and feed_end_date to your export. (Two fields, set once in export settings.)
Agencies here usually clear this within about 1 week (based on 16 observed fixes).
Validator rule: scorecard_missing_feed_info_dates · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning1 instance
The feed contains no fare information.
Riders see 'fare unknown' in trip planners and can't budget their trip; visitors are most affected.
Fix: Add fare_attributes.txt (or Fares v2 files) with your fare structure. If your service is fare-free, ask to have it marked fare-free instead. (A small file for most flat-fare systems.)
Validator rule: scorecard_no_fare_data · Read the fix guide · See GTFS Best Practices (opens GTFS Best Practices on an external site)
- Info7 instances
Big gap in service (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'big_gap_in_service' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Agencies here usually clear this within about 1 week (based on 13 observed fixes).
Validator rule: big_gap_in_service · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Info2 instances
Unknown file (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'unknown_file' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Agencies here usually clear this within about 1 week (based on 6 observed fixes).
Validator rule: unknown_file · 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).
App makers and state data programs 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.)
Agencies here usually clear this within about 1 week (based on 10 observed fixes).
Validator rule: scorecard_no_feed_contact · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
Beyond the grade
Opportunities that do not change your grade today: fare detail, on-demand service, and deeper accessibility data.
1582 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set ("North St @ 23rd St - E", "North St @ 25th St - E", "North St @ Eugene - E", and more).
Consider: Add tts_stop_name with the spoken form, e.g. 'Main Street and Second Avenue', for the affected stops.
NTD certification readiness Not ready
Resolve this before you certify on the D-10. Service data expired 140 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 140 days ago, so FTA would find the link out of date.
- agency_id matches your NTD ID Not checked yet
- Setting your GTFS agency_id to your five-digit NTD ID is an optional way to line a feed up with its National Transit Database record. FTA links the two on your P-50 form, so it is not a required feed change. We don't have your NTD ID on file, so this is not checked yet.
- shapes.txt covers your trips Ready
- All 2372 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 and confirm it once a year. This box is a heads-up on whether yours looks ready; it is not the official sign-off.
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). Aligning agency_id with your NTD ID lets the feed line up with your NTD record; the July 2025 final rule links the two on the P-50 form rather than requiring that feed change, and 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 140 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 140 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
A data-quality lens, not a compliance determination. Each category shows this feed's score and the standards it relates to: the FTA National Transit Database GTFS requirement, the MobilityData grading scheme, and the Google Transit gate. Read the full standards crosswalk.
- Correctness 59 / 100
- GTFS Schedule best practices, checked by the MobilityData validator. MobilityData grading: stop locations, route names and colors. Google Transit: a feed must pass validation to stay in Maps.
- Freshness 35 / 100
- The FTA National Transit Database expectation of a valid, current feed. Google Transit: an expired calendar drops the agency from Maps.
- Rider experience 38 / 100
- GTFS Best Practices for rider-facing fields. MobilityData grading: 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 live badge on your agency site or feed README. It updates daily 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-transit-system-cats/2026-07-09.json and never overwritten, pinning the grade, category scores, rubric version, validator version, and the scored feed's sha256 as they stood on 2026-07-09. Use it in a board packet, an NTD narrative, 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.