Everett Transit

What changed since the last check

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

Top three things to fix

1. Set wheelchair_accessible on every trip. If every vehicle is accessible, this may be one default; otherwise use the value for each trip.

   1098 of 1098 trips don't say whether the vehicle is wheelchair accessible. Even with accessible stops, riders need to know the bus itself can take them.

   Fixing this covers all 1,098 trips in the feed.

   Effort: A default or per-trip field in your export.

2. Add the destination, direction, or 'via' label riders actually see to trip_headsign. Do not copy the route name. If the label changes during the trip, use stop_headsign.

   1098 of 1098 trips have no headsign, the text that tells riders where the bus is going. A trip counts when it has trip_headsign or a stop_headsign at every stop. When a route has multiple directions or patterns, the route name alone may not tell riders which service is coming.

   Fixing this covers all 1,098 trips in the feed.

   Effort: Usually one value per route pattern in your scheduling source.

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

   Effort: A small file for most flat-fare systems.

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 67 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

https://everett.prod.mapstrat.com/current/google_transit.zip

Last checked

2026-10-07

Service window

67 days of service data remain. Last service date 2026-12-13.

Feed version

f3eb566c-18ab-42f6-a5e2-e58b848458a2

Location

Washington