Washington Park Shuttle

What changed since the last check

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

Top three things to fix

1. Re-export with a validity window that reaches at least 60 days out.

   Service data runs out in 29 day(s). When the calendar runs out, trip planners stop showing this agency. Fixing it now is calmer than after riders notice.

   Effort: One export setting.

   Agencies here usually clear this within about 1 week (based on 61 observed fixes).

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

   Agencies here usually clear this within about 1 week (based on 11 observed fixes).

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

   Agencies here usually clear this within about 1 week (based on 9 observed fixes).

Ready to send to the agency

Hi Washington Park Shuttle team, Service data runs out in 29 day(s). When the calendar runs out, trip planners stop showing this agency. Fixing it now is calmer than after riders notice. The fix is usually one export setting: Re-export with a validity window that reaches at least 60 days out. Your feed is produced by Trillium, so the quickest path is usually forwarding this to your Trillium contact. 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/washington-park-shuttle/

Copy this note from the full scorecard.

NTD certification readiness: Ready

Published at a public URL, valid, and current: the three things the NTD GTFS requirement asks of a feed all hold here. Only your own D-10 certification makes 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 34 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.

The bar this score answers to

The state transit-data program is Oregon ODOT Public Transportation. ODOT's Public Transportation Division, which supports statewide GTFS.

Key facts

Feed URL

https://oregon-gtfs.trilliumtransit.com/gtfs_data/washingtonparkshuttle-or-us/washingtonparkshuttle-or-us.zip

Last checked

2026-07-09

Service window

29 days of service data remain. Last service date 2026-08-07.

Feed version

UTC: 03-Jul-2026 16:15

State

Oregon