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
Mountain Line Transit Authority
Based on the feed this agency publishes
unchanged since 2026-07-08
Ahead of 94% of all tracked agencies and 95% of mid-size agencies. Operates in West Virginia.
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 4 hours ago; last fetch returned HTTP 403.
Measured 3 of 4 score categories from the Mobility Database's mirror copy of the feed.
How we measured this
Confidence in this measurement: provisional.
- Realtime quality was not measured this run. It does not count against the grade.
- The agency's own feed URL was unreachable, so the Mobility Database's hosted mirror copy was scored instead.
Confidence describes how much the pipeline could measure this run, not the feed itself. It never changes the grade.
Top things to fix
Review the flagged fields and fill in the ones your riders would use.
Some files leave out fields that GTFS asks for but does not require. Recommended fields like agency_phone or stop descriptions make the feed more useful to riders and trip planners.
⏱ A field at a time; not urgent.worth about +6 points
Agencies here usually clear this within about 2 weeks (based on 8 observed fixes).
Review the rule documentation for 'leading_or_trailing_whitespaces' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.
Leading or trailing whitespaces (flagged by the MobilityData validator). See the linked rule for what this affects.
⏱ Varies.worth about +4 points
Review the rule documentation for 'stops_match_shape_out_of_order' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.
Stops match shape out of order (flagged by the MobilityData validator). See the linked rule for what this affects.
⏱ Varies.worth about +4 points
Agencies here usually clear this within about 1 week (based on 6 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.
Review the flagged fields and fill in the ones your riders would use. · 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.
Review the rule documentation for 'leading_or_trailing_whitespaces' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.
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.
Review the rule documentation for 'stops_match_shape_out_of_order' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.
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 8 kinds of issue across 45 instances (0 error, 42 warning, 3 informational).
Service data covers the next 175 days.
98% of stops state wheelchair accessibility (98% marked accessible, 0% marked not accessible). This measures what the feed publishes, not whether a stop is physically usable. Fare data is published.
98% of stops state accessibility (98% marked accessible). Reflects what the feed states, not verified physical usability.
Fares are applied to trips.
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.
- RT 3 (green)
- RT 1 (green)
- RT 2 (green)
- RT 4 (orange)
- RT 6 (yellow)
- RT 7 (red)
- RT 8 (green)
- RT 9 (purple)
- RT 11 (green)
- RT 12 (teal)
- RT 13 (green)
- RT 14 (green)
- RT 15 (green)
- RT 16 (pink)
- RT 29 (gray)
- RT 30 (green)
- RT 38 (black)
- RT 39 (yellow)
- RT 44 (green)
- RT 46 (green)
- RT 47 (green)
- RT 50 (green)
- RT 51 (green)
- RT 52 (green)
| Route | Type | Line color |
|---|---|---|
| RT 3 Green Line | Bus | green |
| RT 1 Campus PM | Bus | green |
| RT 2 Downtown Mall PM | Bus | green |
| RT 4 Orange Line | Bus | orange |
| RT 6 Gold Line | Bus | yellow |
| RT 7 Red Line | Bus | red |
| RT 8 Brookhaven | Bus | green |
| RT 9 Purple Line | Bus | purple |
| RT 11 Cassville | Bus | green |
| RT 12 Blue Line | Bus | teal |
| RT 13 Crown | Bus | green |
| RT 14 Mt. Heights | Bus | green |
| RT 15 Grafton Rd | Bus | green |
| RT 16 Pink Line | Bus | pink |
| RT 29 Grey Line | Bus | gray |
| RT 30 West Run | Bus | green |
| RT 38 Blue & Gold Express | Bus | black |
| RT 39 Beechurst Express | Bus | yellow |
| RT 44 Valley View | Bus | green |
| RT 46 Eastern Circulator | Bus | green |
| RT 47 Northern Circulator | Bus | green |
| RT 50 Don Knotts | Bus | green |
| RT 51 Westridge Mylan | Bus | green |
| RT 52 Wadestown | Bus | green |
This feed has 191 stops.
List every stop
- Westover Terminal
- Towers
- Mountaineer Field/Ruby
- Willowdale & Valley View
- Chestnut Ridge & Stewart St.
- Stewart & University
- E. Moore Hall
- Court House
- Spruce/Public Safety Building
- MountainLair
- Spruce and Wiley
- Willowdale (Stadium End)
- Unity Manor
- Warner Theater
- Westover Triangle
- Westover Park & Ride
- The Commons (Gabe's)
- Morgantown Mall Theater
- Westover BP
- Burger King
- Morgantown Mall Main Entrance A
- McDonald's Westover
- Westover Goodwill
- Waterfront
- Pleasant & Spruce
- Cobun & Pleasant
- Cobun & Walnut
- Wilson & Overdale
- Morgantown High School (MHS)
- South High & Dorsey
- Dorsey Lane
- Senior Monongalians
- Madigan & Barrickman
- White Park
- Mountaineer Mall
- University & Pleasant
- Colasante's Shelter
- Walmart - UTC
- UTC Theater
- Star City CVS
- Mountaineer Station
- Olive Garden/ Red Lobster
- Mon County Ballpark
- Law School Drive
- Evansdale McDonald's
- University & 8th Street
- Met Theatre
- Marilla Park
- DMV
- Sabraton Goodwill
- Brookhaven Rd.
- Brookhaven Fire Department
- Rt. 7 & Greenbag Road
- Shorty Anderson's
- Suncrest Town Centre
- Maple Drive
- University Park Apartments
- Teletech
- Chestnut Hill Apt.
- Kingston & Stewart
- Stewart & Hoffman
- Granville VFD
- Granville Park & Ride
- Bertha Hill
- Shack Nbrh. House
- Cassville
- New Hill
- Giant Eagle/Dick's Entrance
- Old Navy (UTC)
- Hometown Hot Dogs
- Holland & River Road
- Spruce & Willey
- Richwood & Charles
- Woodland Terrace
- Airport
- Richwood & Putnam
- Laurel Point
- Arnettsville Community Center
- Crown Turn-Around
- Everettsville
- Opekisika Dam
- Lawless Road
- Booth
- River Road VFD
- Westwood Middle School
- Westover Town Hall
- Sabraton Plaza
- Sabraton Kroger
- Listravia
- Summer School Road
- Kingwood Pike
- MUB
- South University Plaza
- Greenbag Road
- Giant Eagle/Get Go/Morg. Motel
- Ashton Estates
- Goshen Road Exit
- Halleck Road
- Toms Run
- Brown's Chapel
- Healthy Heights
- Circle K Grafton Road
- Clinton VFD
- Hornbeck Walmart
- Dorsey's Knob
- Pleasant & High St.
- Mileground Honda
- Pierpont Centre/Lowe's
- Ruby
- Fort Pierpont
- City Garden Apartments
- College Park Apartments
- Fairmont/Gateway Shelter
- Clarksburg/White Oaks Shelter
- Saltwell
- Waynesburg, PA
- Washington PA
- Pittsburgh Airport PIT
- Pittsburgh Greyhound
- Mylan
- West Run Complex
- Copper Beech
- Stewartstown & West Run Rd
- Glenmark
- Bon Vista
- Cedarwood Drive
- STC Drive
- Chestnut Ridge & Stewartstown
- Stewart Place/ Lewis St.
- Stewart & Protzman
- University & Falling Run
- Stewart & Willowdale
- Grant & 6th
- Life Sciences
- Beechurst & 8th
- Evansdale Crossing
- CAC
- Beechurst & 6th
- Beechurst & 3rd
- University & Houston
- North Street
- Loop Area Univ. Ave
- Willowdale & Junction
- Richard
- Dellslow
- Tyrone Road
- Snake Hill
- Rolling Hills
- Canyon Circle K
- University High School
- Canyon MHP
- Skyview
- Mon-Fayette Industrial Park
- Rock Forge Comm. House
- University & VanVoorhis
- Unity House
- Congress & Fairfield
- Riverside Commons
- Congress & University
- University & Junior
- Western
- Lawnview
- FETC
- Aspen & Anderson
- Campus Evolution Villages
- Baker's Ridge Road
- Independence Hills MHP
- West Run & Van Voorhis
- The Villages at West Run
- Riddle & West Run Road
- North Hills
- Mon General
- Morgantown Motel
- Valley Health
- Caritas House
- Comfort Inn
- Gateway Entrance
- Mylan Park
- PACE
- Mylan Community Center
- Jere
- Core
- Mason Dixon Park
- Pentress
- Blacksville
- Clay Battelle High School
- Bula
- Wana
- Wadestown
- Grant & 1st
- Valley View
Over time
Overall score across the last 20 checks — unchanged since 2026-07-08.
Show the numbers
| Check | Score | Change |
|---|---|---|
| 2026-06-19 | 85.6 | first check |
| 2026-06-20 | 85.6 | no change |
| 2026-06-21 | 85.6 | no change |
| 2026-06-22 | 85.6 | no change |
| 2026-06-23 | 85.6 | no change |
| 2026-06-24 | 85.6 | no change |
| 2026-06-25 | 85.6 | no change |
| 2026-06-26 | 85.6 | no change |
| 2026-06-27 | 85.6 | no change |
| 2026-06-28 | 85.6 | no change |
| 2026-06-29 | 85.6 | no change |
| 2026-06-30 | 85.6 | no change |
| 2026-07-01 | 85.6 | no change |
| 2026-07-02 | 85.6 | no change |
| 2026-07-04 | 85.6 | no change |
| 2026-07-05 | 85.6 | no change |
| 2026-07-06 | 85.6 | no change |
| 2026-07-07 | 85.6 | no change |
| 2026-07-08 | 85.6 | no change |
| 2026-07-09 | 85.6 | 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
- Warning35 instances
Some files leave out fields that GTFS asks for but does not require.
Recommended fields like agency_phone or stop descriptions make the feed more useful to riders and trip planners.
Fix: Review the flagged fields and fill in the ones your riders would use. (A field at a time; not urgent.)
Agencies here usually clear this within about 2 weeks (based on 8 observed fixes).
Validator rule: missing_recommended_field · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning4 instances
4 of 191 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)
- Warning2 instances
Leading or trailing whitespaces (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'leading_or_trailing_whitespaces' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Validator rule: leading_or_trailing_whitespaces · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning2 instances
Stops match shape out of order (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'stops_match_shape_out_of_order' 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: stops_match_shape_out_of_order · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning1 instance
Some service calendars in the feed have already ended.
Expired calendars are dead weight and can hide real schedule problems from your staff and vendors.
Fix: Remove past service periods the next time you export the feed. (One setting in most export tools.)
Agencies here usually clear this within about 1 week (based on 61 observed fixes).
Validator rule: expired_calendar · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning1 instance
Missing feed contact email and url (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'missing_feed_contact_email_and_url' 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: missing_feed_contact_email_and_url · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning1 instance
Some stops sit far from the route line they belong to.
Trip planners may draw the bus route through the wrong streets or point riders to the wrong corner.
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.)
Agencies here usually clear this within about 2 weeks (based on 6 observed fixes).
Validator rule: stop_too_far_from_shape · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules 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)
- Info1 instance
Feed valid beyond total service window (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'feed_valid_beyond_total_service_window' 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 5 observed fixes).
Validator rule: feed_valid_beyond_total_service_window · 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.
16 route badge(s) pair a color and text color below the WCAG 4.5:1 contrast bar (RT 1, RT 2, RT 8, RT 11, RT 13, and more).
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.
51 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set ("Mountaineer Field/Ruby", "Willowdale & Valley View", "Chestnut Ridge & Stewart St.", 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 11 changes
For example: 'stop_desc': 'Warner Theater: Routes ' -> 'Warner Theater: Routes'
Recased shouting stop names 2 changes
For example: FETC -> Fetc
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.
- shapes.txt covers your trips Ready
- All 131 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 Awarded
This feed earns the conformance mark: valid, current, and stating wheelchair access on nearly every stop and trip.
- Valid Met
- Passes validation with no errors.
- Current Met
- Service data covers the next 175 days.
- Accessible Met
- States wheelchair access on 98% of stops and 100% of trips.
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 73 / 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 100 / 100
- The FTA National Transit Database expectation of a valid, current feed. Google Transit: an expired calendar drops the agency from Maps.
- Rider experience 92 / 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/mountain-line-transit-authority/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.