Light Rail

What changed since the last check

• Correctness up 4.5
• Freshness down 15.0
• Rider experience down 7.5

Fixed since the last check (3 findings):

• Stops match shape out of order (flagged by the MobilityData validator). (stops_match_shape_out_of_order)
• Some service calendars have no days of the week switched on. (service_has_no_active_day_of_the_week)
• Feed valid beyond total service window (flagged by the MobilityData validator). (feed_valid_beyond_total_service_window)

Top three things to fix

1. Add feed_info.txt with feed_start_date and feed_end_date to your export.

   feed_info.txt is missing its start/end dates (the file itself is absent) Apps and this scorecard can't warn anyone before the feed goes stale without stated validity dates.

   Effort: Two fields, set once in export settings.

   Agencies here usually clear this within about 1 week (based on 16 observed fixes).

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

   67 of 161 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.

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: Ready

Published at a public URL, valid, and current: the three things the NTD GTFS requirement asks of a feed all hold here. Only your own D-10 certification makes that official; this is a heads-up, not a determination.

Published Ready

Published at a public URL.

Valid Ready

Passes validation with no errors.

Current Ready

Service data covers the next 175 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_lightrail.zip

Last checked

2026-07-09

Service window

175 days of service data remain. Last service date 2026-12-31.

State

Maryland