Marin Transit

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. Set wheelchair_accessible on every trip. If every vehicle is accessible, this may be one default; otherwise use the value for each trip.

   535 of 1613 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 535 of 1,613 trips, about 33% of them.

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

2. Check the flagged file name for a typo of a standard GTFS file. Remove it if it is a vendor extra.

   The feed includes a file that is not part of the GTFS spec. Apps ignore files they don't know, and a stray file can hide a misspelled standard file name.

   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: A quick look at the flagged file.

3. Check whether the gap is real, like a seasonal break; if not, add the missing dates to the calendar.

   The feed has a stretch of two weeks or more with no service running. A long gap can mean dates were left out of the calendar. Apps then show no trips on those days.

   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: A review of your calendar dates.