City of Ellensburg Public Transit (Central Transit)

What changed since the last check

• Correctness no change
• Freshness no change
• Rider experience no change

Top three things to fix

1. Re-export the feed with a calendar that reaches further out, and set feed_info feed_end_date past your next service change.

   Service data ended 488 day(s) ago. When the calendar runs out, trip planners stop showing this agency even though the buses are still running. Riders are told the service does not exist.

   Effort: Usually one export setting; export on a schedule so it never lapses again.

2. Remove past service periods the next time you export the feed.

   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.

   Effort: One setting in most export tools.

3. Export and publish an updated GTFS feed that covers at least the next 30 days of service.

   This feed's service calendar runs out within the next 7 days. When the calendar ends, Google Maps and other trip planners drop your agency entirely. Riders see no service at all.

   Effort: Usually a re-export from your scheduling software.

Ready to send to the agency

Hi City of Ellensburg Public Transit (Central Transit) team, Service data ended 488 day(s) ago. When the calendar runs out, trip planners stop showing this agency even though the buses are still running. Riders are told the service does not exist. The fix is usually one export setting: Re-export the feed with a calendar that reaches further out, and set feed_info feed_end_date past your next service change. 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/city-of-ellensburg-public-transit-central-transit/

Copy this note from the full scorecard.

NTD GTFS readiness: Not ready

Resolve this before you certify on the D-10. Service data expired 488 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 488 days ago, so FTA would find the link out of date.

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://mjcaction.com/MJC_GTFS_Public/centraltransit_google_transit.zip

Last checked

2026-08-01

Service window

Feed has expired. Last service date 2025-03-31.

Feed version

20241023

Location

Washington