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-North Railroad
Based on the feed this agency publishes
unchanged since 2026-07-08
Ahead of 75% of all tracked agencies and 73% of mid-size agencies. Operates in New York.
Heads-up: Days until the service window ends dropped by 17 between 2026-06-24 and 2026-06-25, but only 1 day(s) passed. The feed's calendar appears to have moved backward, which can happen when an older export is republished. Worth confirming the latest export is the one being served. (checked 2026-06-25). This can be a brief vendor export glitch; watch the next update before acting.
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 10 hours ago; last changed 10 hours ago.
Measured 3 of 4 score categories from the agency's own feed.
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 agency's own URL.
Confidence describes how much the pipeline could measure this run, not the feed itself. It never changes the grade.
Top things to 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.
The feed contains no fare information. Riders see 'fare unknown' in trip planners and can't budget their trip; visitors are most affected.
⏱ A small file for most flat-fare systems.worth about +15 points
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_accessible on every trip (most small-agency fleets are 100% accessible, so this is often a single default).Likely your export tool
32711 of 42393 trips don't say whether the vehicle is wheelchair accessible. Even with accessible stops, riders need to know the bus itself can take them.
⏱ Often one default setting in your export.worth about +12 points
Agencies here usually clear this within about 1 week (based on 5 observed fixes).
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 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. · 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.
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_accessible on every trip (most small-agency fleets are 100% accessible, so this is often a single default). · 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 6 kinds of issue across 26 instances (0 error, 22 warning, 4 informational).
Service data covers the next 170 days.
98% of stops state wheelchair accessibility (82% marked accessible, 16% marked not accessible). This measures what the feed publishes, not whether a stop is physically usable. Fare data is not published.
98% of stops state accessibility (82% marked accessible). Reflects what the feed states, 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.
Skip to route and stop dataBasemap: OpenFreeMap, © OpenStreetMap contributors. Routes and stops: this agency's GTFS feed.
- Hudson (green)
- Harlem (blue)
- New Haven (red)
- New Canaan (red)
- Danbury (red)
- Waterbury (red)
| Route | Type | Line color |
|---|---|---|
| Hudson | Rail | green |
| Harlem | Rail | blue |
| New Haven | Rail | red |
| New Canaan | Rail | red |
| Danbury | Rail | red |
| Waterbury | Rail | red |
This feed has 114 stops.
List every stop
- Grand Central
- University Heights
- Harlem Valley-Wingdale
- Dover Plains
- Mt Vernon East
- Pelham
- New Rochelle
- Marble Hill
- Larchmont
- Mamaroneck
- Harrison
- Rye
- Port Chester
- Greenwich
- Cos Cob
- Riverside
- Old Greenwich
- Stamford
- Noroton Heights
- Darien
- Rowayton
- South Norwalk
- East Norwalk
- Westport
- Green's Farms
- Southport
- Fairfield
- Spuyten Duyvil
- Bridgeport
- Stratford
- Milford
- New Haven
- New Haven-State St
- Glenbrook
- Springdale
- Talmadge Hill
- New Canaan
- Merritt 7
- Riverdale
- Wilton
- Cannondale
- Branchville
- Redding
- Bethel
- Danbury
- Derby-Shelton
- Ansonia
- Seymour
- Ludlow
- Beacon Falls
- Naugatuck
- Waterbury
- Tenmile River
- Wassaic
- Yonkers
- Highbridge Yard
- Fairfield-Black Rock
- Glenwood
- West Haven
- Greystone
- Hastings-on-Hudson
- Dobbs Ferry
- Ardsley-on-Hudson
- Irvington
- Tarrytown
- Philipse Manor
- Scarborough
- Ossining
- Croton-Harmon
- Cortlandt
- Peekskill
- Harlem-125 St
- Manitou
- Garrison
- Cold Spring
- Breakneck Ridge
- Beacon
- New Hamburg
- Poughkeepsie
- Melrose
- Tremont
- Fordham
- Botanical Garden
- Williams Bridge
- Woodlawn
- Wakefield
- Mt Vernon West
- Yankees-E 153 St
- Fleetwood
- Bronxville
- Springdale MW Facility
- Tuckahoe
- Crestwood
- Scarsdale
- Hartsdale
- White Plains
- North White Plains
- Valhalla
- Mt Pleasant
- Hawthorne
- Pleasantville
- Chappaqua
- Mt Kisco
- Bedford Hills
- Katonah
- Goldens Bridge
- Purdy's
- Morris Heights
- Croton Falls
- Brewster
- Southeast
- Patterson
- Pawling
- Appalachian Trail
Over time
Overall score across the last 20 checks — unchanged since 2026-07-08.
Show the numbers
| Check | Score | Change |
|---|---|---|
| 2026-06-19 | 78.3 | first check |
| 2026-06-20 | 78.3 | no change |
| 2026-06-21 | 78.3 | no change |
| 2026-06-22 | 78.3 | no change |
| 2026-06-23 | 78.3 | no change |
| 2026-06-24 | 78.3 | no change |
| 2026-06-25 | 77.1 | down 1.2 |
| 2026-06-26 | 77.1 | no change |
| 2026-06-27 | 77.1 | no change |
| 2026-06-28 | 77.1 | no change |
| 2026-06-29 | 77.1 | no change |
| 2026-06-30 | 77.1 | no change |
| 2026-07-01 | 77.2 | up 0.1 |
| 2026-07-02 | 77.2 | no change |
| 2026-07-04 | 77.2 | no change |
| 2026-07-05 | 77.2 | no change |
| 2026-07-06 | 77.2 | no change |
| 2026-07-07 | 77.2 | no change |
| 2026-07-08 | 77.2 | no change |
| 2026-07-09 | 77.2 | 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
- Warning32711 instances
32711 of 42393 trips don't say whether the vehicle is wheelchair accessible.
Even with accessible stops, riders need to know the bus itself can take them.
Fix: Set wheelchair_accessible on every trip (most small-agency fleets are 100% accessible, so this is often a single default). (Often one default setting in your export.)
Agencies here usually clear this within about 1 week (based on 5 observed fixes).
Validator rule: scorecard_wheelchair_accessible_unknown · Read the fix guide · See GTFS Schedule reference (opens the GTFS Schedule reference on an external site)
- Warning16 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.)
Validator rule: unused_shape · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning4 instances
Single shape point (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'single_shape_point' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Validator rule: single_shape_point · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning2 instances
2 of 114 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)
- 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.)
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
Some stops exist in the feed but no trip ever stops at them.
Riders may walk to a stop where no bus is scheduled to arrive.
Fix: Remove retired stops from the export, or add them back to the trips that should serve them. (A review pass in your scheduling software.)
Agencies here usually clear this within about 1 week (based on 11 observed fixes).
Validator rule: stop_without_stop_time · Read the fix guide · 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)
- 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.)
Validator rule: scorecard_no_fare_data · Read the fix guide · See GTFS Best Practices (opens GTFS Best Practices on an external site)
- Info3 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)
- Info1 instance
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.
5 route badge(s) pair a color and text color below the WCAG 4.5:1 contrast bar (New Haven, New Canaan, Danbury, Waterbury, Hudson).
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.
3 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set ("Harlem-125 St", "Yankees-E 153 St", "New Haven-State St").
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_name': 'Mt Vernon East ' -> 'Mt Vernon East'
Run it yourself on your own copy of the feed: scorecard autofix <feed.zip> --out corrected.zip
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 170 days.
- agency_id matches your NTD ID Not aligned
- Your feed's agency_id is 1; your National Transit Database ID is 20078. A feed that serves several agencies (a shared regional feed) can legitimately carry more than one agency_id, so a difference here is a heads-up, not an error. Optionally set the agency_id for your service to 20078 in agency.txt (and the matching agency_id in routes.txt) so the feed lines up with your NTD record. It is a convenience, not a required feed change: FTA also links agency_id to your NTD ID on your P-50 form.
- shapes.txt covers your trips Ready
- All 42393 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 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 98% of stops and 23% of trips; the mark needs 90% of each.
- Valid Met
- Passes validation with no errors.
- Current Met
- Service data covers the next 170 days.
- Accessible Not yet
- States wheelchair access on 98% of stops and 23% 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 114 boardable stops are never served by any trip. Riders see these stops in apps and on the map but can never catch anything there, which erodes trust in the data. Remove stops no route serves, or add the trips that should call at them.
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 170 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 81 / 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 66 / 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/mta/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.