Puget Sound Consolidated GTFS

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. Review the rule documentation for 'block_trips_with_overlapping_stop_times' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.

   Block trips with overlapping stop times (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.

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

   Missing required agency id (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. Set timepoint=1 on stops that are real time checks and 0 on the rest. If every published time is a scheduled one, mark them all 1.

   Some rows in stop_times.txt leave the timepoint column blank. That column says whether a time is a real checkpoint or an estimate. Blank leaves apps guessing, and they may show your estimates as promises.

   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: Usually one export setting.