GTFS Scorecard

← Back to the full scorecard

Board packet · transit data quality · checked 2026-10-07

Washington Metropolitan Area Transit Authority (WMATA) Rail

Grade F · 42.5 / 100

Up 2.5 points since 2026-10-06 (F to F).

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

Since the previous compatible check, 1 finding was no longer reported:

  • This feed's service calendar runs out within the next 7 days.

This records feed state, not who made a change or why.

What needs attention next

Three improvements, in priority order, each sized so the board can see what it is approving:

  1. Correct feed_end_date in feed_info.txt. Set it to 2027-01-02, the last day in your calendar, or to the last day your schedule is reliable.

    feed_info.txt says this feed ends on 2026-10-16. Your service calendar runs to 2027-01-02. The GTFS standard tells apps to trust a feed only up to its end date. So apps may stop showing your service on the earlier date, even though the calendar goes on.

    This one is about the feed as a whole, so there is no share of it to count.

    Estimated effort: One field in feed_info.txt, often an export setting.

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

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

    Bidirectional exit gate (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.

Riders and need behind these fixes

  • More than one feed record claims this National Transit Database reporter, so its rider-trips are held back rather than counted against any single feed.
  • District of Columbia as a whole measures moderate on transit need. That is a statewide reading, not one for this feed's service area. Source: US Census ACS 5-year 2022, statewide overlay, as of 2026-10-05.

These describe this feed only. They do not rank agencies, and they do not change the grade or the order of the fixes.

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
feed_info.txt says this feed ends on 2026-10-16. Your service calendar runs to 2027-01-02.
Next action
Correct feed_end_date in feed_info.txt. Set it to 2027-01-02, the last day in your calendar, or to the last day your schedule is reliable.
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

Produced by the GTFS Scorecard, an open-source data quality tool. A data-quality read to support the board conversation, not an official compliance determination. Live scorecard: https://gtfsscorecard.org/agency/washington-metropolitan-area-transit-authority-wmata-1847/. Rubric v1.4, validator 8.0.1.