GTFS Scorecard

← Back to the full scorecard

Call-prep brief · checked 2026-09-13

Puget Sound Consolidated GTFS

Grade F · 52.2 / 100

Unchanged since 2026-09-12.

For this call: lead with the grade and the three fixes below, then confirm the feed is current and the NTD details line up. Each fix is framed as a next step, not a failure.

What changed since the last check

  • Correctness no change
  • Freshness no change
  • Rider experience no change

Top three things to fix

  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.

    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.

    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.

    Effort: Usually one export setting.

Finding handoff

Move one finding to a recheck

Select one finding. Copy the request, make the change in the feed-producing tool, then compare the next complete run.

Feed evidence
Block trips with overlapping stop times (flagged by the MobilityData validator).
Next action
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.
Recheck
Publish the changed feed at the same URL. On the next complete, comparable scorecard run, confirm that this finding is no longer reported.
Copy handoff text

NTD GTFS readiness: Needs attention

This feed is close to NTD-ready. 2 validator errors to resolve.

Published Ready
Published at a public URL.
Valid Needs attention
2 validator errors to resolve.
Current Ready
Service data covers the next 194 days.
agency_id provided Ready
agency.txt provides agency_id. For RY2026, keep one stable value for each NTD reporter represented in the feed and crosswalk each value on the P-50 form.

agency_id equals NTD ID (optional): Not checked yet. This feed provides agency_id. For RY2026, keep one stable value for each NTD reporter represented in the feed and crosswalk it on the P-50 form. The value does not need to equal the five-digit NTD ID; we do not have that ID on file, so the optional equality comparison is not checked yet.

The bar this score answers to

A local transit-data support resource is WSDOT Transportation Data. WSDOT builds and publishes GTFS for Washington transit agencies.

Key facts

Feed URL
https://gtfs.sound.obaweb.org/prod/gtfs_puget_sound_consolidated.zip
Last checked
2026-09-13
Service window
194 days of service data remain. Last service date 2027-12-31.
Feed version
FAL26-161.0
Location
Washington

Part of the Washington portfolio: see where this agency sits among the other feeds in that group before the call.

A data-quality and completeness read to support an agency conversation. Not an official compliance determination. Rubric v1.3, validator 8.0.1.