Stanford Marguerite Shuttle (SMS)

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. Remove retired stops from the export, or add them back to the trips that should serve them.

   Some stops exist in the feed but no trip ever stops at them. Riders may walk to a stop where no bus is scheduled to arrive.

   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 pass in your scheduling software.

2. Check the flagged column names for misspellings of standard GTFS fields; remove them if they are vendor extras.

   Some files contain columns that are not part of the GTFS spec. Harmless to riders, but apps ignore these columns and they can hide typos in real column names.

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

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.