Prep for a call: printable one-page brief · For your board packet: printable one-pager · Compare with another agency · Watch this feed: get an email before it expires
Feed status · checked 2026-07-09
Metro SubwayLink
Based on the feed this agency publishes
unchanged since 2026-07-08
Ahead of 69% of all tracked agencies and 68% of mid-size agencies. Operates in Maryland.
A data-quality and completeness lens to help an agency improve its GTFS feed. Not an official compliance determination from any transit program. New to this? How to read your scorecard. Interactive view of this scorecard. Rubric v1.1, validator 8.0.1.
Checked for changes 14 minutes ago; last changed 17 days ago.
Top things to fix
Add feed_info.txt with feed_start_date and feed_end_date to your export.Likely your export tool
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.
⏱ Two fields, set once in export settings.worth about +15 points
Agencies here usually clear this within about 1 week (based on 16 observed fixes).
Set wheelchair_boarding to 1 (accessible) or 2 (not accessible) for every stop. A field survey can start with the busiest stops.Likely your team
142 of 239 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.
⏱ A column in stops.txt; your scheduling software likely has it.worth about +15 points
Use mixed case for stop names and headsigns (e.g. 'Main St & 2nd Ave', not 'MAIN ST & 2ND AVE').Likely your export tool
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.
⏱ Often a bulk fix in your scheduling software.worth about +8 points
Close the loop on each fix. Read the guide, make the change in your tool, and let the next run verify it — the scorecard shows the fix; the agency publishes it.
Add feed_info.txt with feed_start_date and feed_end_date to your export. · Read the fix guide
Make the change. Make this change in whatever tool produces your feed, then re-export.
Prove it cleared. The next scorecard run re-checks this automatically and, once it is gone, mints a dated receipt. Self-check a feed before you publish.
Set wheelchair_boarding to 1 (accessible) or 2 (not accessible) for every stop. A field survey can start with the busiest stops. · Read the fix guide
Make the change. Make this change in whatever tool produces your feed, then re-export.
Prove it cleared. The next scorecard run re-checks this automatically and, once it is gone, mints a dated receipt. Self-check a feed before you publish.
Use mixed case for stop names and headsigns (e.g. 'Main St & 2nd Ave', not 'MAIN ST & 2ND AVE'). · Read the fix guide
Make the change. Make this change in whatever tool produces your feed, then re-export.
Prove it cleared. The next scorecard run re-checks this automatically and, once it is gone, mints a dated receipt. Self-check a feed before you publish.
Send your vendor a fix request
You may not control the GTFS export yourself. Copy this and send it to whoever runs your scheduling software export. It names each fix with the validator notice and a guide link.
Score by category
The MobilityData validator flagged 7 kinds of issue across 687 instances (0 error, 683 warning, 4 informational).
Service data covers the next 175 days.
41% of stops state wheelchair accessibility (41% marked accessible, 0% marked not accessible). This measures what the feed publishes, not whether a stop is physically usable. Fare data is published.
41% of stops state accessibility (41% marked accessible). Reflects what the feed states, not verified physical usability.
Fares are applied to trips.
This agency publishes realtime, but the feed needs an access key we don't have yet. Nothing here counts against the grade.
Over time
Overall score across the last 20 checks — unchanged since 2026-07-08.
Show the numbers
| Check | Score | Change |
|---|---|---|
| 2026-06-19 | 75.3 | first check |
| 2026-06-20 | 75.3 | no change |
| 2026-06-21 | 75.3 | no change |
| 2026-06-22 | 75.3 | no change |
| 2026-06-23 | 75.3 | no change |
| 2026-06-24 | 75.3 | no change |
| 2026-06-25 | 75.3 | no change |
| 2026-06-26 | 75.3 | no change |
| 2026-06-27 | 75.3 | no change |
| 2026-06-28 | 75.3 | no change |
| 2026-06-29 | 75.3 | no change |
| 2026-06-30 | 75.3 | no change |
| 2026-07-01 | 75.3 | no change |
| 2026-07-02 | 75.3 | no change |
| 2026-07-04 | 75.3 | no change |
| 2026-07-05 | 75.3 | no change |
| 2026-07-06 | 75.3 | no change |
| 2026-07-07 | 75.3 | no change |
| 2026-07-08 | 75.3 | no change |
| 2026-07-09 | 75.3 | no change |
What changed since your last check
- Correctness no change
- Freshness no change
- Rider experience no change
What changed in this feed
Overall grade and score held steady since 2026-07-08.
Same feed file as 2026-07-08; the published zip did not change.
Subscribe to this feed’s changes (Atom) to hear about grade drops in a reader, with no sign-up.
Everything we checked
- Warning573 instances
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.
Fix: Use mixed case for stop names and headsigns (e.g. 'Main St & 2nd Ave', not 'MAIN ST & 2ND AVE'). (Often a bulk fix in your scheduling software.)
Validator rule: mixed_case_recommended_field · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning142 instances
142 of 239 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.
Fix: Set wheelchair_boarding to 1 (accessible) or 2 (not accessible) for every stop. A field survey can start with the busiest stops. (A column in stops.txt; your scheduling software likely has it.)
Validator rule: scorecard_wheelchair_boarding_unknown · Read the fix guide · See GTFS Schedule reference (opens the GTFS Schedule reference on an external site)
- Warning73 instances
Equal shape distance same coordinates (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'equal_shape_distance_same_coordinates' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Validator rule: equal_shape_distance_same_coordinates · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning35 instances
Stop too far from shape using user distance (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'stop_too_far_from_shape_using_user_distance' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Agencies here usually clear this within about 1 week (based on 6 observed fixes).
Validator rule: stop_too_far_from_shape_using_user_distance · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning1 instance
A recommended GTFS file (usually feed_info.txt) is missing.
feed_info.txt tells apps who publishes the feed and when it expires; without it nobody is warned before data goes stale.
Fix: Add feed_info.txt with publisher name, URL, language, and feed_start_date/feed_end_date. (One small file, set once in export settings.)
Agencies here usually clear this within about 1 week (based on 13 observed fixes).
Validator rule: missing_recommended_file · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning1 instance
Route short name too long (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'route_short_name_too_long' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Validator rule: route_short_name_too_long · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning1 instance
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.
Fix: Add feed_info.txt with feed_start_date and feed_end_date to your export. (Two fields, set once in export settings.)
Agencies here usually clear this within about 1 week (based on 16 observed fixes).
Validator rule: scorecard_missing_feed_info_dates · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Info319 instances
This feed describes station pathways, including step-free (elevator) routes.
Riders can be routed through the station, and wheelchair users can see whether a step-free route exists.
Fix: No action needed. (None.)
Validator rule: scorecard_station_pathways
- Info18 instances
About 18 stop names are written in ALL CAPS.
Mixed-case names are easier to read in apps and are read more naturally by screen readers.
Fix: Rename stops to mixed case (e.g. 'Main St & 2nd Ave'). (Often a bulk fix in your scheduling software.)
Validator rule: scorecard_stop_names_all_caps · Read the fix guide · See GTFS Best Practices (opens GTFS Best Practices on an external site)
- Info2 instances
Some files contain columns that are not part of the GTFS spec.
Harmless to riders, but apps ignore these columns and they can hide typos in real column names.
Fix: Check the flagged column names for misspellings of standard GTFS fields; remove them if they are vendor extras. (A quick look at the flagged files.)
Validator rule: unknown_column · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Info2 instances
Unknown file (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'unknown_file' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Agencies here usually clear this within about 1 week (based on 6 observed fixes).
Validator rule: unknown_file · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Info1 instance
feed_info.txt has no technical contact (feed_contact_email or feed_contact_url).
App makers and state data programs have nobody to email when they spot a problem with your feed, so problems linger.
Fix: Add feed_contact_email to feed_info.txt. (One field.)
Agencies here usually clear this within about 1 week (based on 10 observed fixes).
Validator rule: scorecard_no_feed_contact · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
Beyond the grade
Opportunities that do not change your grade today: fare detail, on-demand service, and deeper accessibility data.
The feed publishes fare products but no fare_media.txt declaring how riders can pay.
Consider: Add fare_media.txt listing your accepted payment methods, including contactless EMV if riders can tap to pay.
15 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set ("ROGERS AVE STATION (METRO) nb", "ROGERS AVE STATION (METRO) sb", "ROGERS AVE METRO", and more).
Consider: Add tts_stop_name with the spoken form, e.g. 'Main Street and Second Avenue', for the affected stops.
Some fixes we can make for you
These are the safe mechanical fixes, applied to a copy of your feed. They change only what is certain and leave everything else untouched. Review the diff before you publish.
Trimmed surrounding whitespace 1 change
For example: 'stop_lon': ' -76.594166' -> '-76.594166'
Recased shouting stop names 18 changes
For example: OWINGS MILLS STATION (METRO) -> Owings Mills Station (metro)
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 matches your 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.
In plain words: if you report to the federal transit database, you have to publish a working, up-to-date feed and confirm it once a year. This box is a heads-up on whether yours looks ready; it is not the official sign-off.
A readiness signal mapping this feed to the FTA National Transit Database GTFS requirement (Report Year 2023 onward: a public, valid, current feed, certified annually on the D-10). Aligning agency_id with your NTD ID lets the feed line up with your NTD record; the July 2025 final rule links the two on the P-50 form rather than requiring that feed change, and requires shapes.txt in the published GTFS: Full Reporters from Report Year 2025, and Reduced, Rural, and Tribal Reporters from Report Year 2026. Not an official determination; your certification is the official check.
Conformance mark Not yet
This feed is close to the conformance mark. States wheelchair access on 41% of stops and 100% of trips; the mark needs 90% of each.
- Valid Met
- Passes validation with no errors.
- Current Met
- Service data covers the next 175 days.
- Accessible Not yet
- States wheelchair access on 41% of stops and 100% of trips; the mark needs 90% of each.
In plain words: earn this mark when your feed passes validation, has not expired, and says whether nearly every stop and trip is wheelchair accessible.
A pass credential for a feed that is valid, current, and states wheelchair access on nearly every stop and trip. Accessibility here measures what the feed publishes, not whether a stop is physically usable. How the conformance mark works.
Clears the Google and Apple Maps four-week coverage bar. This feed has 175 days of service ahead, clearing the four-week (28-day) window Maps asks for. No validator errors either, so riders keep seeing this agency in their trip planners; warnings lower the grade here but do not remove a feed from Maps.
How this agency maps to the standards
A data-quality lens, not a compliance determination. Each category shows this feed's score and the standards it relates to: the FTA National Transit Database GTFS requirement, the MobilityData grading scheme, and the Google Transit gate. Read the full standards crosswalk.
- Correctness 69 / 100
- GTFS Schedule best practices, checked by the MobilityData validator. MobilityData grading: stop locations, route names and colors. Google Transit: a feed must pass validation to stay in Maps.
- Freshness 85 / 100
- The FTA National Transit Database expectation of a valid, current feed. Google Transit: an expired calendar drops the agency from Maps.
- Rider experience 76 / 100
- GTFS Best Practices for rider-facing fields. MobilityData grading: stop names and headsigns.
- Realtime quality Not yet published
- GTFS-Realtime best practices: a stable URL, high uptime, and frequent updates.
Show your grade
Put a live badge on your agency site or feed README. It updates daily and links back to this scorecard.
Prefer a shields.io style? Point a dynamic endpoint badge at the published badge.json.
Cite this record
This page updates on every check. The record below does not: it is the dated file this grade came from, published at https://gtfsscorecard.org/data/artifacts/maryland-transit-administration-metro-subway/2026-07-09.json and never overwritten, pinning the grade, category scores, rubric version, validator version, and the scored feed's sha256 as they stood on 2026-07-09. Use it in a board packet, an NTD narrative, or a research citation instead of linking the live page, whose content will differ on your next visit.
Citing the tool itself rather than one agency's record? Use the repo's CITATION.cff.