← Back to the full scorecard

Board packet · transit data quality · checked 2026-10-07

The Victoria Clipper

Grade F · 58.1 / 100

Unchanged since 2026-10-06.

What this grade measures

The quality of the schedule data in the feed scored here 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. Re-export the feed with a calendar that reaches further out. Set feed_end_date in feed_info.txt past your next service change.

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

    This one is about the feed as a whole, so there is no share of it to count.

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

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

    This one is about the feed as a whole, so there is no share of it to count.

    Estimated effort: A small file for most flat-fare systems.

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

    This is a validator notice, and the validator decides what each instance covers, so no share of the network can be read from it here.

    Estimated effort: One setting in most export tools.

Riders and need behind these fixes

  • This feed carries no National Transit Database ID, so annual rider-trips are not known for it.
  • Washington as a whole measures lower on transit need. That is a statewide reading, not one for this feed's service area. Source: US Census ACS 5-year 2022, statewide overlay, as of 2026-10-05.

These describe this feed only. They do not rank agencies, and they do not change the grade or the order of the fixes.

Finding handoff

Move one finding to a recheck

Select one finding. Copy the request, make the change in the feed-producing tool, then compare the next complete run.

Feed evidence
Service data ended 3143 day(s) ago.
Next action
Re-export the feed with a calendar that reaches further out. Set feed_end_date in feed_info.txt past your next service change.
Recheck
Publish the changed feed at the same URL. On the next complete, comparable scorecard run, confirm that this finding is no longer reported.
Copy handoff text

Produced by the GTFS Scorecard, an open-source data quality tool. A data-quality read to support the board conversation, not an official compliance determination. Live scorecard: https://gtfsscorecard.org/agency/the-victoria-clipper/. Rubric v1.4, validator 8.0.1.