Montgomery County Department of Transportation (Ride On)

What changed since the last check

• Correctness no change
• Freshness down 1.6
• 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. Add fare_attributes.txt (or Fares v2 files) with your fare structure. If your service is fare-free, ask to have it marked fare-free instead.

   The feed contains no fare information. Riders see 'fare unknown' in trip planners and can't budget their trip; visitors are most affected.

   Effort: A small file for most flat-fare systems.

3. Use mixed case for stop names and headsigns (e.g. 'Main St & 2nd Ave', not 'MAIN ST & 2ND AVE').

   Some rider-facing names are in ALL CAPS or all lowercase. ALL-CAPS stop and headsign names are harder to read in apps and are read awkwardly by screen readers.

   Effort: Often a bulk fix in your scheduling software.

NTD certification readiness: Needs attention

This feed is close to NTD-ready. 1 validator error to resolve.

Published Ready

Published at a public URL.

Valid Needs attention

1 validator error to resolve.

Current Ready

Service data covers the next 70 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://www.montgomerycountymd.gov/DOT-Transit/Resources/Files/GTFS/RideOnGTFS.zip

Last checked

2026-07-09

Service window

58 days of service data remain. Last service date 2026-09-05.

Feed version

13-May 3, 2026_20260423

State

Maryland