Washington Metropolitan Area Transit Authority (WMATA) Rail

What changed since the last check

• Correctness no change
• Freshness up 10.0
• Rider experience no change

No longer reported since the last check (1 finding):

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

This compares feed state. It does not identify who made a change or why.

Top three things to fix

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.

   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.

   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.

   Effort: Varies.

Ready to send to the agency

Hi Washington Metropolitan Area Transit Authority (WMATA) Rail team, 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. The fix is usually one export setting: 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. 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: Needs attention

This feed is close to NTD-ready. 2 validator errors to resolve. Service data runs out in 9 days; renew before you certify.

Published Ready

Published at a public URL.

Valid Needs attention

2 validator errors to resolve.

Current Needs attention

Service data runs out in 9 days; renew before you certify.

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-10-07

Service window

9 days of service data remain. Last service date 2027-01-02.

Location

District of Columbia