Community Transit (CT)

What changed since the last check

• Correctness no change
• Freshness down 1.7
• Rider experience no change
• Realtime quality up 0.2

No longer reported since the last check (1 finding):

• 1 of 113 trips scheduled during the sampling window had no live predictions. (scorecard_rt_trip_coverage)

This compares feed state. It does not identify who made a change or why.

Top three things to fix

1. Re-export with a validity window that reaches at least 60 days out.

   Service data runs out in 27 day(s). When the calendar runs out, trip planners stop showing this agency. Fixing it now is calmer than after riders notice.

   Effort: One export setting.

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

   1752 of 1752 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.

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

3. 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.

   The feed contains no fare information. Riders see 'fare unknown' in trip planners and can't budget their trip; visitors are most affected.

   Effort: A small file for most flat-fare systems.

Ready to send to the agency

Hi Community Transit (CT) team, Service data runs out in 27 day(s). When the calendar runs out, trip planners stop showing this agency. Fixing it now is calmer than after riders notice. The fix is usually one export setting: Re-export with a validity window that reaches at least 60 days out. This came from your GTFS data quality scorecard, which checks the feed you publish and lists the fixes in plain language: https://gtfsscorecard.org/agency/community-transit-ct/

Copy this note from the full scorecard.

NTD GTFS readiness: Needs attention

This feed is close to NTD-ready. Service data runs out in 27 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 27 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 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.

The bar this score answers to

A local transit-data support resource is WSDOT Transportation Data. WSDOT builds and publishes GTFS for Washington transit agencies.

Key facts

Feed URL

https://www.communitytransit.org/docs/default-source/open-data/gtfs/current.zip

Last checked

2026-08-01

Service window

27 days of service data remain. Last service date 2026-08-28.

Feed version

20260709-20260828v2

Location

Washington