San Francisco Bay Area Water Emergency Transportation Authority (WETA)

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 with a validity window that reaches at least 60 days out.

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

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

   Estimated effort: One export setting.

2. Review the rule documentation for 'foreign_key_violation' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.

   Foreign key violation (flagged by the MobilityData validator). See the linked rule for what this affects.

   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: Varies.

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

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

   Fixing this covers all 548 trips in the feed.

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

Trillium produces and hosts this feed as a service. These changes are made on their side: send the fix list to your Trillium contact and they apply it and republish.