Marin Transit

What this grade measures

The quality of the schedule data this agency publishes 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. Add the required column named in the finding to the flagged file.

   A file is missing a column that GTFS requires. Apps may reject the whole file, so riders could lose the affected routes or stops.

   Estimated effort: Often an export setting; ask your vendor if it recurs.

2. Check the flagged stops' shape_dist_traveled against the route shape, and re-generate it on export if they disagree.

   Some stops sit far from the route line, going by the feed's own distance values. Trip planners may draw the route down the wrong streets or point riders to the wrong corner.

   Estimated effort: Usually an export-tool fix, not hand editing.

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

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

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