Local Bus

What changed since the last check

• Correctness no change
• Freshness down 1.7
• Rider experience no change

Top three things to fix

1. Set wheelchair_boarding to 1 (accessible) or 2 (not accessible) for every stop. A field survey can start with the busiest stops.

   4095 of 4095 stops don't say whether a wheelchair user can board there. Riders who use wheelchairs can't plan a trip when accessibility is marked 'unknown'; apps show no information at all.

   Effort: A column in stops.txt; your scheduling software likely has it.

2. 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.

3. Check the flagged stop times for transposed minutes.

   Some scheduled trips travel implausibly fast between stops. Usually a typo'd stop time; riders get impossible arrival estimates.

   Effort: A few minutes per flagged trip.

NTD GTFS readiness: Ready

This feed looks ready for your NTD certification: published at a public URL, valid, and current. The official check is still your D-10 certification.

Published Ready

Published at a public URL.

Valid Ready

Passes validation with no errors.

Current Ready

Service data covers the next 53 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://mdotmta-gtfs.s3.amazonaws.com/mdotmta_gtfs_localbus.zip

Last checked

2026-07-11

Service window

42 days of service data remain. Last service date 2026-08-22.

Feed version

20260617-merged-222-223-v2