Feed status · checked 2026-11-21
MARC Train
Based on the feed source on file; publisher ownership is not verified
Service mode Rail
up 9.6 since 2026-11-20 · F → D
Cataloged in Maryland.
The grade is not a count of validator errors. It also weighs freshness and rider information. How the grade works
Feed file
Feed URL: https://mdotmta-gtfs.s3.amazonaws.com/mdotmta_gtfs_marc.zip
Watch this feed for free: we email you before it expires or when its grade drops.
Top things to fix
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
79 of 79 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.
Fixing this covers all 79 stops in the feed.
⏱ A column in stops.txt; your scheduling software likely has it.worth about +25 points in its category
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.
This one is about the feed as a whole, so there is no share of it to count.
⏱ Two fields, set once in export settings.worth about +15 points in its category
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.
This one is about the feed as a whole, so there is no share of it to count.
⏱ A small file for most flat-fare systems.worth about +15 points in its category
Riders and need behind these fixes
- This feed carries no National Transit Database ID, so annual rider-trips are not known for it.
- Maryland as a whole measures lower on transit need. That is a statewide reading, not one for this feed's service area. Source: US Census ACS 5-year 2022, statewide overlay, as of 2026-11-02.
These describe this feed only. They do not rank agencies, and they do not change the grade or the order of the fixes.
Finding handoff
Move one finding to a recheck
Select one finding. Copy the request, make the change in the feed-producing tool, then compare the next complete run.
- Finding
- Fix 01 in Top things to fix: its feed evidence and the requested change.
- Recheck
- Publish the changed feed at the same URL. On the next complete, comparable scorecard run, confirm that this finding is no longer reported.
Copy handoff text
- Finding
- Fix 02 in Top things to fix: its feed evidence and the requested change.
- Recheck
- Publish the changed feed at the same URL. On the next complete, comparable scorecard run, confirm that this finding is no longer reported.
Copy handoff text
- Finding
- Fix 03 in Top things to fix: its feed evidence and the requested change.
- Recheck
- Publish the changed feed at the same URL. On the next complete, comparable scorecard run, confirm that this finding is no longer reported.
Copy handoff text
How to make and check these changes
Check the result on the published feed. Read the guide, make the change in your tool, and use the next comparable run to see whether the finding is still reported. Only an action or ticket record can attribute who made the change.
Fix 01 · Read the fix guide for scorecard_wheelchair_boarding_unknown
Make the change. Make this change in whatever tool produces your feed, then re-export.
Check the result. The next scorecard run checks this finding again. If a comparable check no longer reports it, the feed's clearance log records that result. This confirms feed state, not who made the change. See this feed's finding-clearance log.
Fix 02 · Read the fix guide for scorecard_missing_feed_info_dates
Make the change. Make this change in whatever tool produces your feed, then re-export.
Check the result. The next scorecard run checks this finding again. If a comparable check no longer reports it, the feed's clearance log records that result. This confirms feed state, not who made the change. See this feed's finding-clearance log.
Fix 03 · Read the fix guide for scorecard_no_fare_data
Make the change. Make this change in whatever tool produces your feed, then re-export.
Check the result. The next scorecard run checks this finding again. If a comparable check no longer reports it, the feed's clearance log records that result. This confirms feed state, not who made the change. See this feed's finding-clearance log.
Rider view: what this feed publishes
A quick read of rider-facing information in this feed.
- Schedule visibility
- The feed's last published service date is in 370 days.
- Published accessibility data
- Accessibility information is stated for 0% of stops and 100% of trips. This measures published data, not whether stops or vehicles are physically usable.
- Fare information
- No fare information is published in the feed.
- Realtime information
- Realtime-feed availability and live-arrival coverage are not known from this scorecard.
Important: This does not rate service reliability. Riders should confirm current service alerts, fares, and accessibility accommodations with the transit operator before traveling.
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.
About this feed
Looking for times or routes? This page checks the data file that trip planners use. For schedules, use the agency's own website or a trip planner.
MARC Train’s published feed lists 3 rail routes, 176 scheduled trips and 79 stops. The published file last changed on 2026-11-21.
Score by category
The MobilityData validator flagged 9 kinds of issue across 285 instances (0 error, 268 warning, 17 informational).
Service data covers the next 370 days.
0% of stops state wheelchair accessibility (0% marked accessible, 0% marked not accessible). This measures what the feed publishes, not whether a stop is physically usable. Fare data is not published.
0% of stops state accessibility (0% marked accessible). Reflects what the feed states, not verified physical usability.
2 accessibility depth signals
3 route badge(s) pair a color and text color below the WCAG 4.5:1 contrast bar (MARC, MARC, MARC).
Consider: Adjust route_color or route_text_color so each pair clears 4.5:1. Often switching the text between black and white is enough.
2 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set ("ST DENIS MARC sb", "ST DENIS MARC nb").
Consider: Add tts_stop_name with the spoken form, e.g. 'Main Street and Second Avenue', for the affected stops.
Opportunities to strengthen the data, not deductions from the sub-score above. States what the second accessibility lens can check from the feed, not verified physical usability.
Not scored yet. Nothing here counts against the grade.
Routes and stops
Each route is drawn once, using the longest shape its trips follow; stops are the dots.
This feed has 79 stops.
The route and stop data is ready below. Load the map only when you want the geographic view. It uses additional data.
Basemap: OpenFreeMap, © OpenStreetMap contributors. Routes and stops: this agency's GTFS feed.
- MARC (orange)
- MARC (orange)
- MARC (orange)
| Route | Type | Line color |
|---|---|---|
| MARC BRUNSWICK - WASHINGTON | Rail | orange |
| MARC PENN - WASHINGTON | Rail | orange |
| MARC CAMDEN - WASHINGTON | Rail | orange |
List every stop
- MARTINSBURG W VA MARC
- DUFFIELDS W VA MARC eb
- HARPERS FERRY W VA MARC eb
- BRUNSWICK MD MARC eb
- FREDERICK MARC eb
- MONOCACY MARC eb
- POINT OF ROCKS MARC eb
- DICKERSON MARC eb
- BARNESVILLE MARC eb
- BOYDS MARC eb
- GERMANTOWN MARC eb
- METROPOLITAN GROVE MARC eb
- GAITHERSBURG MARC eb
- WASHINGTON GROVE MARC eb
- ROCKVILLE MARC eb
- GARRETT PARK MARC eb
- KENSINGTON MARC eb
- SILVER SPRING MARC eb
- UNION STATION MARC Washington
- SILVER SPRING MARC wb
- KENSINGTON MARC wb
- GARRETT PARK MARC wb
- ROCKVILLE MARC wb
- WASHINGTON GROVE MARC wb
- GAITHERSBURG MARC wb
- METROPOLITAN GROVE MARC wb
- GERMANTOWN MARC wb
- BOYDS MARC wb
- BARNESVILLE MARC wb
- DICKERSON MARC wb
- POINT OF ROCKS MARC wb
- MONOCACY MARC wb
- FREDERICK MARC wb
- BRUNSWICK MD MARC wb
- HARPERS FERRY W VA MARC wb
- DUFFIELDS W VA MARC wb
- PERRYVILLE MARC
- ABERDEEN MARC sb
- EDGEWOOD MARC sb
- MARTIN AIRPORT MARC sb
- PENN STATION MARC sb
- WEST BALTIMORE MARC sb
- HALETHORPE MARC sb
- BWI RAIL STATION MARC sb
- ODENTON MARC sb
- BOWIE STATE MARC sb
- SEABROOK MARC sb
- NEW CARROLLTON MARC sb
- NEW CARROLLTON MARC nb
- SEABROOK MARC nb
- BOWIE STATE MARC nb
- ODENTON MARC nb
- BWI RAIL STATION MARC nb
- HALETHORPE MARC nb
- WEST BALTIMORE MARC nb
- PENN STATION MARC nb
- MARTIN AIRPORT MARC nb
- EDGEWOOD MARC nb
- ABERDEEN MARC nb
- CAMDEN STATION MARC
- ST DENIS MARC sb
- DORSEY MARC sb
- JESSUP MARC sb
- SAVAGE MARC sb
- LAUREL RACETRACK MARC sb
- LAUREL MARC sb
- MUIRKIRK MARC sb
- GREENBELT MARC sb
- COLLEGE PARK MARC sb
- RIVERDALE MARC sb
- RIVERDALE MARC nb
- COLLEGE PARK MARC nb
- GREENBELT MARC nb
- MUIRKIRK MARC nb
- LAUREL MARC nb
- SAVAGE MARC nb
- JESSUP MARC nb
- DORSEY MARC nb
- ST DENIS MARC nb
Over time
Overall score across the last 13 checks — up 9.6 since 2026-11-20.
Show the numbers
| Check | Score | Change |
|---|---|---|
| 2026-11-09 | 57.4 | first check |
| 2026-11-10 | 57.0 | down 0.4 |
| 2026-11-11 | 56.6 | down 0.4 |
| 2026-11-12 | 56.2 | down 0.4 |
| 2026-11-13 | 55.8 | down 0.4 |
| 2026-11-14 | 55.4 | down 0.4 |
| 2026-11-15 | 54.9 | down 0.5 |
| 2026-11-16 | 54.5 | down 0.4 |
| 2026-11-17 | 54.1 | down 0.4 |
| 2026-11-18 | 53.7 | down 0.4 |
| 2026-11-19 | 53.3 | down 0.4 |
| 2026-11-20 | 52.9 | down 0.4 |
| 2026-11-21 | 62.5 | up 9.6 |
What changed since your last check
- Correctness up 4.0
- Freshness up 31.7
- Rider experience no change
Feed history
Every check on record for this feed, grouped by the published file, newest first. A new file means the published zip changed. Grades from earlier rubric versions are shown with their rubric and are not comparable with today’s grade or the trend above.
| Checked | Published file | Service dates through | Grade at the time |
|---|---|---|---|
| 2026-11-21 | 7313b7f76d82 | 2027-11-26 | Current rubric: see the trend above |
| 2026-11-16 to 2026-11-20 (5 checks) | 8473a38603d2 | 2026-12-31 | Current rubric: see the trend above |
| 2026-11-09 to 2026-11-15 (7 checks) | 28aad239a63e | 2026-12-31 | Current rubric: see the trend above |
| 2026-10-12 to 2026-11-06 (26 checks) | 28aad239a63e | 2026-12-31 | F, 58.7 under rubric 1.4, an earlier scoring contract; not comparable with today’s grade |
| 2026-10-02 to 2026-10-11 (10 checks) | e0d7d7027093 | 2026-12-31 | F, 55.5 under rubric 1.4, an earlier scoring contract; not comparable with today’s grade |
| 2026-09-28 to 2026-10-01 (4 checks) | e0d7d7027093 | 2026-12-31 | F, 55.5 under rubric 1.3, an earlier scoring contract; not comparable with today’s grade |
| 2026-09-11 to 2026-09-27 (13 checks) | 05758f55714e | 2026-12-31 | D, 60.8 under rubric 1.3, an earlier scoring contract; not comparable with today’s grade |
| 2026-09-04 to 2026-09-10 (7 checks) | d99a7a46ccc7 | 2026-12-31 | D, 60.8 under rubric 1.3, an earlier scoring contract; not comparable with today’s grade |
| 2026-07-25 to 2026-09-03 (41 checks) | a5cb03e93204 | 2026-12-31 | D, 60.7 under rubric 1.3, an earlier scoring contract; not comparable with today’s grade |
| 2026-07-14 to 2026-07-24 (8 checks) | a5cb03e93204 | 2026-12-31 | D, 60.7 under rubric 1.2, an earlier scoring contract; not comparable with today’s grade |
| 2026-07-02 to 2026-07-13 (12 checks) | a5cb03e93204 | 2026-12-31 | D, 60.7 under rubric 1.1, an earlier scoring contract; not comparable with today’s grade |
| 2026-06-24 to 2026-07-01 (8 checks) | ab32f69073ba | 2026-12-31 | D, 60.7 under rubric 1.1, an earlier scoring contract; not comparable with today’s grade |
Showing the 12 most recent of 13 periods.
What changed over time
On 2026-11-09 this feed started at grade F. On 2026-11-21 the grade moved from F to D. As of 2026-11-21 it holds grade D.
A plain-language history of this feed, newest first.
- 2026-11-21 Grade went F to D, freshness rose 32 points.
Everything we checked
13 findings, ordered by severity.
Show every finding
- Warning131 instances
Some stops sit far from the route line, going by the feed's own distance values.
Trip planners may draw the route down the wrong path or point riders to the wrong boarding location.
Fix: Check the flagged stops' shape_dist_traveled against the route shape, and re-generate it on export if they disagree. (Usually an export-tool fix, not hand editing.)
Finding code: stop_too_far_from_shape_using_user_distance · Read the fix guide for stop_too_far_from_shape_using_user_distance · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning120 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.)
Finding code: mixed_case_recommended_field · Read the fix guide for mixed_case_recommended_field · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning79 instances
79 of 79 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.)
Finding code: scorecard_wheelchair_boarding_unknown · Read the fix guide for scorecard_wheelchair_boarding_unknown · See GTFS Schedule reference (opens the GTFS Schedule reference on an external site)
- Warning8 instances
Some service calendars have no days of the week switched on.
Trips tied to these calendars never run; they are dead data that can mask real schedule problems.
Fix: Delete the empty calendars or set their service days. (A few minutes in your scheduling software.)
Finding code: service_has_no_active_day_of_the_week · Read the fix guide for service_has_no_active_day_of_the_week · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning3 instances
Some stops sit far from the route line they belong to.
Trip planners may draw the transit vehicle route through the wrong path or point riders to the wrong boarding location.
Fix: Check the flagged stops' coordinates and the route shape in your scheduling software; re-snap whichever is misplaced. (A few minutes per flagged stop.)
Finding code: stop_too_far_from_shape · Read the fix guide for stop_too_far_from_shape · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning3 instances
The feed contains route shapes no trip uses.
Harmless to riders, but it bloats the feed and suggests stale export data.
Fix: Turn on 'remove unused shapes' (or the like) in your export tool. (One setting.)
Finding code: unused_shape · Read the fix guide for unused_shape · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning1 instance
A file GTFS asks for (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.)
Finding code: missing_recommended_file · Read the fix guide for missing_recommended_file · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning1 instance
Some trips serve fewer than two stops.
A trip with one stop can't be ridden; planners ignore it and it may signal an export problem.
Fix: Check the flagged trips in your scheduling software; remove them or restore their missing stops. (Worth a vendor question if it appears often.)
Finding code: unusable_trip · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning1 instance
Unused trip (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'unused_trip' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Finding code: unused_trip · 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.)
Finding code: scorecard_missing_feed_info_dates · Read the fix guide for scorecard_missing_feed_info_dates · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning1 instance
The feed contains no fare information.
Riders see 'fare unknown' in trip planners and can't budget their trip; visitors are most affected.
Fix: 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. (A small file for most flat-fare systems.)
Finding code: scorecard_no_fare_data · Read the fix guide for scorecard_no_fare_data · See GTFS Best Practices (opens GTFS Best Practices on an external site)
- Info17 instances
The feed has a stretch of two weeks or more with no service running.
A long gap can mean dates were left out of the calendar. Apps then show no trips on those days.
Fix: Check whether the gap is real, like a seasonal break; if not, add the missing dates to the calendar. (A review of your calendar dates.)
Finding code: big_gap_in_service · Read the fix guide for big_gap_in_service · 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. Small errors then sit in the feed for months.
Fix: Add feed_contact_email to feed_info.txt. (One field.)
Finding code: scorecard_no_feed_contact · Read the fix guide for scorecard_no_feed_contact · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
How we measured this
Checked for changes 18 hours ago; last changed 18 hours ago.
Measured 3 of 4 score categories from the feed URL on file (publisher not verified).
How we measured this
Confidence in this measurement: medium.
- Realtime quality was not measured this run. It does not count against the grade.
- The feed was downloaded from the configured feed URL. Publisher ownership of that URL is not verified.
Confidence describes how much the pipeline could measure this run, not the feed itself. It never changes the grade.
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.5, validator 8.0.1.
NTD GTFS readiness Ready
Published at a public URL, valid, current, and identified with agency_id: the four feed checks for RY2026 all hold here. Only your own D-10 and P-50 filings make 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 370 days.
- agency_id provided Ready
- agency.txt provides agency_id. For RY2026, keep one stable value for each NTD reporter represented in the feed and crosswalk each value on the P-50 form.
- agency_id equals your NTD ID (optional) Not checked yet
- This feed provides agency_id. For RY2026, keep one stable value for each NTD reporter represented in the feed and crosswalk it on the P-50 form. The value does not need to equal the five-digit NTD ID; we do not have that ID on file, so the optional equality comparison is not checked yet.
- shapes.txt covers your trips Ready
- All 176 trips have a shape in shapes.txt.
In plain words: if you report to the federal transit database, you have to publish a working, up-to-date feed, provide a stable agency_id for each represented reporter, and confirm the feed and P-50 crosswalk each year. This box is a heads-up; your filings are the official check.
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). For RY2026, each represented reporter needs a stable agency_id, unique within the feed and crosswalked to its five-digit NTD ID on P-50; the values do not need to be equal. FTA also 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
One requirement remains for this feed to earn the conformance mark. States wheelchair access on 0% 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 370 days.
- Accessible Not yet
- States wheelchair access on 0% 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.
Can riders use it?
Checks beyond structural validation: places where the feed is valid but a rider still could not travel.
- 1 of 176 trips list fewer than two stops. A trip with one stop has no ride in it. Trip planners can't put a rider on that trip at all. Check your scheduling export: every trip should list each stop it calls at, in order, with times.
These do not change the grade. They catch trips with no rideable leg and stops no trip serves, the kind of gap a trip planner trips over.
Clears the Google and Apple Maps four-week coverage bar. This feed has 369 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
The scorecard is a data-quality lens, not a compliance determination. Its universal references describe good GTFS and useful rider information. Useful references here are GTFS Schedule Best Practices, GTFS-Realtime Best Practices, MobilityData grading scheme, Google Transit publication guidance, FTA National Transit Database GTFS requirement. Read the full standards crosswalk.
- Correctness 57 / 100
- GTFS Schedule best practices, checked by the MobilityData validator. MobilityData grading covers stop locations, route names, and colors. Google Transit requires a feed to pass validation for publication. FTA NTD readiness also checks that the published feed is valid.
- Freshness 85 / 100
- GTFS Schedule best practices call for a dataset that stays current. An expired calendar can remove service from Google Transit and other rider trip planners. FTA NTD readiness also checks that the published feed is current.
- Rider experience 52 / 100
- GTFS Best Practices for rider-facing fields. MobilityData grading covers stop names and headsigns.
- Realtime quality Not yet published
- GTFS-Realtime best practices: a stable URL, high uptime, and frequent updates.
Part of the Maryland portfolio: the same scorecards for every feed we track in that group, on one free page.
Similar feeds in Maryland
Other scorecards in Maryland, starting with the same kind of service at a similar size. Listed for comparison, not ranked.
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-468/2026-11-21.json and never overwritten, pinning the grade, category scores, rubric version, validator version, reader archive profile, and the scored feed's sha256 as they stood on 2026-11-21. Use it in a board packet, a regulatory filing, 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.