Valley Metro

What changed since the last check

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

Top three things to fix

1. Re-generate shape distances in your export; flag to your vendor if it persists.

   Some trips have stop times whose distances along the route go backwards. Apps can show buses jumping backwards or mis-order stops.

   Effort: Usually an export-tool fix, not hand editing.

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

   Duplicate key (flagged by the MobilityData validator). See the linked rule for what this affects.

   Effort: Varies.

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

   Stop time with arrival before previous departure time (flagged by the MobilityData validator). See the linked rule for what this affects.

   Effort: Varies.

NTD certification readiness: Needs attention

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

Published Ready

Published at a public URL.

Valid Needs attention

5 validator errors to resolve.

Current Ready

Service data covers the next 26838 days.

agency_id and NTD ID: Not checked yet. Setting your GTFS agency_id to your five-digit NTD ID is an optional way to line a feed up with its National Transit Database record. FTA links the two on your P-50 form, so it is not a required feed change. We don't have your NTD ID on file, so this is not checked yet.

Key facts

Feed URL

https://vmgoapp.com/gtfs

Last checked

2026-07-09

Service window

26838 days of service data remain. Last service date 2099-12-31.

Feed version

04/06/26

State

Virginia