Capital Area Transit System (CATS)

What this grade measures

The quality of the schedule data this agency publishes for trip-planning apps: whether riders using Google Maps, Apple Maps, or Transit see current, correct, and complete information. It measures the data feed, not service quality or operations.

Progress this period

No newly cleared items this period. The score and trend above reflect where the feed stands today.

What needs attention next

Three improvements, in priority order, each sized so the board can see what it is approving:

1. Confirm your next service period is published: export its calendar and set feed_info feed_end_date past it.

   The published calendar ended 163 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.

   Estimated effort: One export when the next period's schedule is set.

2. Set wheelchair_boarding to 1 (accessible) or 2 (not accessible) for every stop. A field survey can start with the busiest stops.

   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.

   Estimated effort: A column in stops.txt; your scheduling software likely has it.

3. Set wheelchair_accessible on every trip. If every vehicle is accessible, this may be one default; otherwise use the value for each trip.

   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.

   Estimated effort: A default or per-trip field in your export.

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.