GTFS Scorecard

← Back to the full scorecard

Call-prep brief · checked 2026-07-17

City of Wasco

Grade F · 30.9 / 100

First check for this agency, so there is no trend yet.

For this call: lead with the grade and the three fixes below, then confirm the feed is current and the NTD details line up. Each fix is framed as a next step, not a failure.

What changed since the last check

No category changes since the last check.

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 1294 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. Review the rule documentation for 'missing_required_file' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.

    Missing required file (flagged by the MobilityData validator). See the linked rule for what this affects.

    Effort: Varies.

  3. Review the rule documentation for 'invalid_input_files_in_subfolder' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.

    Invalid input files in subfolder (flagged by the MobilityData validator). See the linked rule for what this affects.

    Effort: Varies.

Ready to send to the agency

Hi City of Wasco team, Service data ended 1294 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-wasco/

Copy this note from the full scorecard.

NTD GTFS readiness: Not ready

Resolve this before you certify on the D-10. 3 validator errors to resolve. Service data expired 1294 days ago, so FTA would find the link out of date.

Published Ready
Published at a public URL.
Valid Needs attention
3 validator errors to resolve.
Current Not ready
Service data expired 1294 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

The published guideline in California is California Transit Data Guidelines. Caltrans' published quality guidelines and compliance checklist; this rubric is anchored to them.

Key facts

Feed URL
https://gtfs.dds.dot.ca.gov/gtfs_files/WascoDialaRideFlex.zip
Last checked
2026-07-17
Service window
Feed has expired. Last service date 2022-12-31.
Feed version
1
Location
California

Part of the California portfolio: see where this agency sits among the state's feeds before the call.

A data-quality and completeness read to support an agency conversation. Not an official compliance determination. Rubric v1.2, validator 8.0.1.