Call-prep brief · checked 2026-08-01

Washington Metropolitan Area Transit Authority (WMATA) Rail

Grade F · 26.7 / 100

Unchanged since 2026-07-31.

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

Re-export the feed with a calendar that reaches further out, and set feed_info feed_end_date past your next service change.
Service data ended 659 day(s) ago. When the calendar runs out, trip planners stop showing this agency even though the transit vehicles are still running. Riders are told the service does not exist.
Effort: Usually one export setting; export on a schedule so it never lapses again.
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.
Effort: Varies.
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.
Effort: Varies.

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: Service data ended 659 day(s) ago.
Next action: Re-export the feed with a calendar that reaches further out, and set feed_info feed_end_date past your next service change.
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

Agency: Washington Metropolitan Area Transit Authority (WMATA) Rail
Finding: scorecard_feed_expired
Feed evidence: Service data ended 659 day(s) ago.
Why it matters: When the calendar runs out, trip planners stop showing this agency even though the transit vehicles are still running. Riders are told the service does not exist.
Requested change: Re-export the feed with a calendar that reaches further out, and set feed_info feed_end_date past your next service change.
Recheck: Publish the changed feed at the same URL. On the next complete, comparable scorecard run, confirm that this finding is no longer reported.
Evidence: https://gtfsscorecard.org/agency/washington-metropolitan-area-transit-authority-wmata-1847/?finding=scorecard_feed_expired#finding-handoff

Ready to send to the agency

Hi Washington Metropolitan Area Transit Authority (WMATA) Rail team, Service data ended 659 day(s) ago. When the calendar runs out, trip planners stop showing this agency even though the transit vehicles are still running. Riders are told the service does not exist. The fix is usually one export setting: Re-export the feed with a calendar that reaches further out, and set feed_info feed_end_date past your next service change. This came from your GTFS data quality scorecard, which checks the feed you publish and lists the fixes in plain language: https://gtfsscorecard.org/agency/washington-metropolitan-area-transit-authority-wmata-1847/

Copy this note from the full scorecard.

NTD GTFS readiness: Not ready

Resolve this before you certify on the D-10. 2 validator errors to resolve. Service data expired 659 days ago, so FTA would find the link out of date.

Published Ready: Published at a public URL.
Valid Needs attention: 2 validator errors to resolve.
Current Not ready: Service data expired 659 days ago, so FTA would find the link out of date.
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): Different (allowed). Your feed's agency_id is 1; your National Transit Database ID is 30030. A feed that serves several agencies (a shared regional feed) can legitimately carry more than one agency_id. The values do not need to equal the five-digit NTD ID, so this difference is allowed and carries no score. Confirm that P-50 crosswalks agency_id 1 to NTD ID 30030, and keep the feed value stable. Do not change it solely to make the two values equal.

Key facts

Feed URL: https://api.wmata.com/gtfs/rail-gtfs-static.zip
Last checked: 2026-08-01
Service window: Feed has expired. Last service date 2024-12-14.
Location: District of Columbia

Part of the District of Columbia portfolio: see where this agency sits among the state's feeds 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.