Call-prep brief · checked 2026-11-09
Washington Metropolitan Area Transit Authority (WMATA) Rail
Grade F · 47.1 / 100 · partial: freshness not measured
The scoring methodology changed since the prior check; the trend restarts here without an improvement or regression claim.
Scored from a Mobility Database mirror copy downloaded on 2026-10-19, because the feed URL on file could not be downloaded. Service dates in that copy run 2026-10-15 to 2026-10-23. It may not match the feed the agency publishes today.
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
The scoring methodology changed since the prior check. Category deltas restart with this scorecard.
Top three things to fix
Check that https://api.wmata.com/gtfs/rail-gtfs-static.zip still serves your current feed. If the feed moved, publish the new address.
The feed URL on file, https://api.wmata.com/gtfs/rail-gtfs-static.zip, could not be downloaded: the server answered with an error instead of the file. Trip planners download the feed from that address too. The grade here was measured on an older Mobility Database copy whose service ended 2026-10-23, so freshness is not graded until the current feed can be downloaded.
This one is about the feed as a whole, so there is no share of it to count.
Effort: Usually a server or hosting setting, not a change to the feed itself.
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.
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.
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.
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-11-02.
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
- The feed URL on file, https://api.wmata.com/gtfs/rail-gtfs-static.zip, could not be downloaded: the server answered with an error instead of the file.
- Next action
- Check that https://api.wmata.com/gtfs/rail-gtfs-static.zip still serves your current feed. If the feed moved, publish the new address.
- 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
- Feed evidence
- Number out of range (flagged by the MobilityData validator).
- Next action
- 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.
- 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
- Feed evidence
- Bidirectional exit gate (flagged by the MobilityData validator).
- Next action
- Review the rule documentation for 'bidirectional_exit_gate' 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: Not ready
Resolve this before you certify on the D-10. 2 validator errors to resolve. No service end date could be read, so currency is unknown.
- Published Ready
- Published at a public URL.
- Valid Needs attention
- 2 validator errors to resolve.
- Current Not ready
- No service end date could be read, so currency is unknown.
- 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-11-09
- Service window
- Expiry date not stated in the feed.
- Location
- District of Columbia
Part of the District of Columbia 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.4, validator 8.0.1.