GTFS Scorecard

← Back to the full scorecard

Call-prep brief · checked 2026-08-01

Kitsap Transit

Grade D · 66.2 / 100

Up 0.4 points since 2026-07-31 (D to D).

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

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

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

  • Some service calendars in the feed have already ended. (expired_calendar)

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

Top three things to fix

  1. Check the trip updates endpoint with your AVL vendor; it should return a fresh GTFS-Realtime protobuf on every request.

    The trip updates realtime feed failed during sampling. When this feed is down, riders see scheduled times presented as if they were live.

    Effort: Usually a vendor support ticket.

  2. Check the vehicle positions endpoint with your AVL vendor; it should return a fresh GTFS-Realtime protobuf on every request.

    The vehicle positions realtime feed failed during sampling. When this feed is down, riders see scheduled times presented as if they were live.

    Effort: Usually a vendor support ticket.

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

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

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
The trip updates realtime feed failed during sampling.
Next action
Check the trip updates endpoint with your AVL vendor; it should return a fresh GTFS-Realtime protobuf on every request.
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

NTD GTFS readiness: Ready

Published at a public URL, valid, current, and identified with agency_id: the four feed checks for RY2026 all hold here. Only your own D-10 and P-50 filings make that official; this is a heads-up, not a determination.

Published Ready
Published at a public URL.
Valid Ready
Passes validation with no errors.
Current Ready
Service data covers the next 42 days.
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
http://pride.kitsaptransit.com/gtfs/google_transit.zip
Last checked
2026-08-01
Service window
42 days of service data remain. Last service date 2026-09-12.
Feed version
S1000067
Location
Washington

Part of the Washington 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.3, validator 8.0.1.