Capital District Transportation Authority (CDTA)

Top things to fix

Score by category

Over time

Overall score across the last 20 checks — down 0.3 since 2026-07-08.

What changed since your last check

• Correctness— no change
• Freshness▼ down 1.7
• Rider experience— no change
• Realtime quality— no change

What changed in this feed

Overall score fell 0.3 points 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 A. On 2026-06-20 it cleared scorecard_rt_trip_coverage. On 2026-07-01 it cleared scorecard_rt_vehicles_off_route. As of 2026-07-09 it holds grade A.

A plain-language history of this feed, newest first.

• 2026-06-30 Score fell 3 points, realtime fell 17 points.

Everything we checked

• Warning15 instances

  15 of 13940 trips have no headsign.

  Riders at the stop can't tell which direction a bus is going.

  Fix: Populate trip_headsign to match what the bus displays. (Usually a bulk edit in your scheduling software.)

  Validator rule: scorecard_missing_headsigns · Read the fix guide · See GTFS Best Practices (opens GTFS Best Practices on an external site)

• Warning8 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)

• Warning6 instances

  Some stops exist in the feed but no trip ever stops at them.

  Riders may walk to a stop where no bus is scheduled to arrive.

  Fix: Remove retired stops from the export, or add them back to the trips that should serve them. (A review pass in your scheduling software.)

  Agencies here usually clear this within about 1 week (based on 11 observed fixes).

  Validator rule: stop_without_stop_time · 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

  1 of 97 trips scheduled during the sampling window had no live predictions.

  Riders on those trips get schedule data dressed up as realtime. Caltrans expects every operating trip in TripUpdates.

  Fix: Check with your AVL vendor that every vehicle assignment flows into TripUpdates, including school-day and tripper runs. (A vendor data-mapping question.)

  Agencies here usually clear this within about 1 week (based on 84 observed fixes).

  Validator rule: scorecard_rt_trip_coverage · Read the fix guide · See GTFS-Realtime reference (opens the GTFS-Realtime reference on an external site)

• Info1 instance

  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)

• Info1 instance

  Some files contain columns that are not part of the GTFS spec.

  Harmless to riders, but apps ignore these columns and they can hide typos in real column names.

  Fix: Check the flagged column names for misspellings of standard GTFS fields; remove them if they are vendor extras. (A quick look at the flagged files.)

  Validator rule: unknown_column · 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.

• 2686 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set ("Second Ave & S. Bertha St", "Second Ave & Jeanette St", "3rd Ave & 4th St", and more).

  Consider: Add tts_stop_name with the spoken form, e.g. 'Main Street and Second Avenue', for the affected stops.

Some fixes we can make for you

These are the safe mechanical fixes, applied to a copy of your feed. They change only what is certain and leave everything else untouched. Review the diff before you publish.

• Recased shouting stop names 1 change

  For example: ALBANY GARAGE -> Albany Garage

Download corrected feed