Kitsap Transit

What changed since the last check

• Correctness no change
• Freshness no change
• Rider experience no change
• Realtime quality no change

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. Check with your AVL vendor that every vehicle assignment flows into TripUpdates, including school-day and tripper runs.

   17 of 17 trips scheduled during the sampling window had no live predictions. Riders on those trips get schedule data dressed up as realtime. Caltrans expects every operating trip in TripUpdates.

   Effort: A vendor data-mapping question.

NTD GTFS readiness: Ready

This feed looks ready for your NTD certification: published at a public URL, valid, and current. The official check is still your D-10 certification.

Published Ready

Published at a public URL.

Valid Ready

Passes validation with no errors.

Current Ready

Service data covers the next 74 days.

agency_id and NTD ID: Not checked yet. Setting your GTFS agency_id to your five-digit NTD ID is an optional way to line a feed up with its National Transit Database record. FTA links the two on your P-50 form, so it is not a required feed change. We don't have your NTD ID on file, so this is not checked yet.

Key facts

Feed URL

http://pride.kitsaptransit.com/gtfs/google_transit.zip

Last checked

2026-07-11

Service window

63 days of service data remain. Last service date 2026-09-12.

Feed version

S1000066