Feed status · checked 2026-10-20
Mid Mon Valley Transit Authority
Based on the feed source on file; publisher ownership is not verified
Service mode Bus
First scorecard for this agency
Cataloged in Pennsylvania.
Source feed: https://mmvta.rideralerts.com/InfoPoint/gtfs-zip.ashx
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.4, validator 8.0.1.
Checked for changes 34 minutes ago; last changed 34 minutes 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.
About this feed
Mid Mon Valley Transit Authority’s published feed lists 10 bus routes, 777 scheduled trips and 286 stops. Its service dates run from 2026-10-07 through 2027-07-31.
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
286 of 286 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 286 stops in the feed.
⏱ A column in stops.txt; your scheduling software likely has it.worth about +25 points in its category
Set wheelchair_accessible on every trip. If every vehicle is accessible, this may be one default; otherwise use the value for each trip.Likely your export tool
777 of 777 trips don't say whether the vehicle is wheelchair accessible. Even with accessible stops, riders need to know the bus itself can take them.
Fixing this covers all 777 trips in the feed.
⏱ A default or per-trip field in your export.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
- No ridership snapshot was on hand when this was built, so annual rider-trips are not known.
- Pennsylvania 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-10-19.
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. Self-check a feed before you publish.
Fix 02 · Read the fix guide for scorecard_wheelchair_accessible_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. Self-check a feed before you publish.
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. Self-check a feed before you publish.
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 284 days.
- Published accessibility data
- Accessibility information is stated for 0% of stops and 0% 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.
Score by category
The MobilityData validator flagged 4 kinds of issue across 15 instances (0 error, 15 warning, 0 informational).
Service data covers the next 284 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 (Local 2, Local 3, Cal U Vulcan Fl).
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.
244 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set ("Liberty Ave @ 21st St FS", "California: 3rd St + Wood St", "California: 3rd St opp Mechanic St", and more).
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 286 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.
- Commuter A (red)
- Local 5 (brown)
- Cal U Vulcan Fl (red)
- Cal Commuter (black)
- Commuter Exp 1 (red)
- Commuter Exp 2 (purple)
- Local 1 (purple)
- Local 2 (gray)
- Local 3 (teal)
- Local 4 (black)
| Route | Type | Line color |
|---|---|---|
| Commuter A | Bus | red |
| Local 5 | Bus | brown |
| Cal U Vulcan Fl Cal U Vulcan Flyer Shuttle | Bus | red |
| Cal Commuter | Bus | black |
| Commuter Exp 1 | Bus | red |
| Commuter Exp 2 | Bus | purple |
| Local 1 | Bus | purple |
| Local 2 | Bus | gray |
| Local 3 | Bus | teal |
| Local 4 | Bus | black |
List every stop
- Castle Shannon - Rte. 88 at Killarney D
- Rotary Park
- Rostraver Apartments
- Liberty Ave @ 21st St FS
- California: 3rd St + Wood St
- California: 3rd St opp Mechanic St
- California University: Vulcan Village U
- Liberty @ 25th
- Liberty Ave @ 21st St
- Liberty Ave @ 17th St
- Liberty Ave @ 14th St
- Liberty @ 12th
- Liberty after 11th (Amtrak)
- Liberty Ave @ 14th St
- Liberty Ave @ 17th St
- Liberty at 26th St.
- Allenport: Credit Union
- Liberty Towers
- Dunlevy: Route 88 + Mannina Ave
- Allenport: Route 88 + Horseshoe St
- Allenport: Route 88 + Washington St
- Allenport: Route 88 + Wheeling Steel Pla
- Stockdale: Route 88 opp Locust St
- Stockdale: Route 88 + Elm St
- Roscoe: Route 88 + Ruth St
- Roscoe: Route 88 + Mt Tabor Rd
- Roscoe: Route 88 + Rebecca St
- Elco: Route 88 + Jobes St
- Elco: Route 88 + Vesta St
- Elco: Route 88 + Hollow Rd
- California: 3rd St + Union St
- California University: Hickory St + 3rd
- California University: 3rd St + Universi
- California University: Vulcan Village L
- California University: Park & Ride
- Allenport: Credit Union
- Roadman Park
- California University: Bldg B + Parking
- California: 3rd St + Mechanic St
- Elco: Route 88 opp Hollow Rd
- Elco: Route 88 + Vesta St
- Elco: Route 88 + Jobes St
- Roscoe: Route 88 + Howard St
- Roscoe: Route 88 +Mt Tabor Rd
- Roscoe: Route 88 + Ruth St
- Stockdale: Route 88 + Elm St
- Stockdale: Route 88 + Locust St
- Allenport: Route 88 + Community Bldg
- Allenport: Route 88 + Washington St
- Allenport: Route 88 opp Horseshoe St
- Allenport: Route 88 + Allen St
- Dunlevy: Dunlevy Gardens
- Dunlevy: Route 88 + Frick St
- West Brownsville: Walmart
- Route 88 + 4th St BBQ North
- Route 88 + Taylor Run Rd (YMCA)
- Upper Speers
- Fisher Hts-Giant Eagle
- Route 88 + County Club Rd
- Country Club Rd + Giant Eagle S
- Route 88 + Coyle Curtain Rd
- Route 88 + Quality CoPack North
- Route 88 opp Hospital Dr
- Mon Valley Hospital
- Route 88 + Coyle Curtain Rd
- Route 88 + Taylor Run Rd
- Country Club Rd + Route 837
- Route 88 + Hospital Dr
- Route 88 + Maple Dr
- North Charleroi: Transit Center
- Charleroi: Fallowfield Ave + 7th St
- Charleroi: Fallowfield Ave + 9th St
- Charleroi: Fallowfield Ave + 5th St
- Charleroi: Fallowfield Ave + 3rd St
- Charleroi: 1st St + Sunoco
- Route 88 + Grandview Way
- Charleroi: McKean Ave + 1st St
- Charleroi: McKean Ave + 3rd St
- Charleroi: McKean Ave + 7th St
- Charleroi: Crest Apartments
- Charleroi: McKean Ave + 9th St
- North Charleroi: Transit Center
- Route 88 + Dairy Queen
- North Charleroi: Lincoln Ave + Lock St
- North Charleroi: Lincoln Ave + 7th St
- Route 88 + Grandview Way
- North Charleroi: Nathan Goff Apts
- North Charleroi: Lincoln Ave + 7th St
- Smithfield St + Forbes Ave
- Smithfield St + Third Ave
- North Charleroi: Lincoln Ave + Bridge
- Route 88 + Dairy Queen
- N Belle Vernon: Broad St + Grant St
- N Belle Vernon: Broad St + Vine St
- N Belle Vernon: Broad St + Fayette St
- Broad and Don St
- Rostraver Twp: Walmart
- Rostraver Square: Aldi
- Lower Belle Vernon: opp Municipal Buildi
- Lower Belle Vernon: Municipal Building
- Rostraver Twp: Giant Eagle
- Broad and Johnson
- N Belle Vernon: Broad St + St. Sebastian
- N Belle Vernon: Broad St + Vine St
- N Belle Vernon: Broad St + Arch St
- Belle Vernon Highrise
- N Belle Vernon: Broad St + Grant St
- East Busway Bus Stop D
- N Belle Vernon: Broad St + Short St
- N Belle Vernon: Broad St + Short St
- Monessen: Route 906 + Tyrol Blvd
- New Eagle: Lignelli Manor
- N Belle Vernon: Broad St + Arch St
- Monessen: Donner Ave + Parente Blvd
- Monessen: Donner Ave + 2nd St
- Monessen: Route 906 after Tyrol Blvd
- Smithfield St Bridge + Station Square
- Monessen: Schoonmaker + 10th St
- Monessen: Schoonmaker at 6th
- Monessen: Schoonmaker + 4th
- Monessen: Schoonmaker + 2nd
- Monessen: Schoonmaker + Oneida
- Monessen: Exxon Bus Shelter
- Monessen: Route 906 + Keystone Bakery
- Monessen: Donner Ave + 4th St
- Monessen: Donner Ave + 5th St
- Monessen: Donner Ave + 6th St
- Monessen: Donner Ave + Civic Center
- Monessen: Donner Ave + 10th St
- Monessen: Donner + Riverfront Ind Park
- Route 906 + Riverfront Indust Park
- Route 906 + Riverfront Indust Park
- Monessen: Schoonmaker Ave + 3rd St
- Monessen: 3rd St opp Valley Manor
- Monessen: 3rd St + Valley Manor
- Donora: 6th St + McKean Ave
- Grand Blvd + George & Hallworth House
- Grand Blvd + St. Vincent de Paul/Park Ce
- Grand Blvd + Watkins Rd (Grand Plaza)
- Grand Blvd + Monessen Elementary
- Grand Blvd + Monessen Senior Center
- Grand Blvd opp St. Vincent de Paul
- Grand by Jehovah Witnesses
- Park Manor
- 9th @ Knox at Park
- Monessen House Apartments
- McMahon @ 9th St.
- MMVTA Garage Departing
- Allenport: Route 88 + Allen St
- Donora: 6th St + Thompson Ave
- Smithfield St + Sixth Ave
- Donora: Modisette Ave + Chestnut St
- Donora: Meldon Ave + 9th St
- Donora: Castner Ave + 4th
- Donora: McKean Ave + 9th St
- Donora: opp War Memorial
- Donora: McKean Ave + Market St
- Donora: McKean Ave + 1st St
- Donora: 3rd St + McKean Ave
- Donora: McKean Ave + 5th St
- Donora: McKean Ave + 6th St
- Donora: McKean Ave + 7th St
- Donora: 11th St + Meldon Ave
- Donora: Meldon Ave + 13th St
- Donora: Meldon Ave + 15th St
- Donora: 6th St + Castner Ave
- Donora: Castner Ave + 4th St
- Highland Terrace
- Donora: McKean St + 11th St
- Donora: Meldon Ave + 15th St
- Donora: Meldon Ave + 13th St
- Donora: Meldon Ave + 11th St
- Donora: Meldon Ave + 7th St
- Donora: Meldon Ave + 6th St
- Donora: Meldon Ave + 5th St
- Donora: 3rd St + McKean Ave
- Donora: McKean Ave + 1st St
- Donora: McKean Ave + Market St
- Donora: War Memorial
- Monongahela: W Main St + Foodland
- New Eagle: Route 88 after Dry Run Rd
- New Eagle: W Main St + Maple St
- Route 88 + Trailer Park Ent
- Route 88 + Trailer Park Ent
- Monongahela: W Main St + Charleroi Feder
- Monongahela: W Main St + 11th St
- New Eagle W Main + Dry Run Rd
- New Eagle: Route 88 after Maderia St.
- Route 88 + Marion
- New Eagle: Route 88 + Memorial Dr
- New Eagle: Main St + Hemlock St
- New Eagle: Main St + Maple St
- Monongahela: W Main St + 5th St
- Monongahela: E Main St + 1st St
- Route 88 + Carrol St
- Route 88 + Maderia St
- Monongahela: Route 837 + Walnut St
- Black Diamond: Route 837 + Nelson St
- Monongahela: Route 837 + Ridge Ave
- Monongahela: Route 837 + Factory St
- Monongahela: W Main St + 3rd St
- Monongahela: W Main St + 4th St
- Monongahela: W Main St + 7th St
- Monongahela: W Main St + 9th St
- New Eagle: W Main St + Hemlock St
- New Eagle: Route 88 + Memorial Dr
- Monongahela: W Main St + 9th St
- Monongahela: W Main St + 7th St
- Monongahela: W Main St + 4th St
- Monongahela: W Main St + 3rd St
- W Main at 1st S
- Monongahela: Route 837 + Walnut St
- Monongahela: Route 837 + Ridge Ave
- Black Diamond: Route 837 + Nelson St
- Route 837 + Walnut St
- Monongahela: W Main St + 5th St
- Finleyville: Route 88 + Boyer St
- Large Park & Ride
- Route 88 + Castle Shannon Blvd
- Route 88 + Castle Shannon Blvd
- Crookham: Opposite Park & Ride Rt 88
- Route 88 + Boyka Dr
- Route 88 + Stondebridge/Giant Eagle
- Smithfield St + Blvd of the Allies
- Smithfield St + Forbes Ave
- Smithfield St + Sixth Ave
- Smithfield St + Seventh Ave
- Route 88 + Walter Long
- Route 88 + Morgan Ln
- Route 88 + Union Valley Apts
- Route 88 + Jason Dr
- Finleyville: Finley Middle School
- Route 88 + Finleyville VFD
- Route 88 + Stonebridge Dr
- Route 88 + Boyka Dr
- Crookham: Park & Ride Route 88 + Ginger
- Route 88 + Brownsville Rd
- Route 88 + St. Joan of Arc
- Library: Route 88 after Brownsville Dr
- Route 88 + St. Joan of Arc
- Route 88 + Royal Dr
- Route 88 and Clifton Rd
- Route 88 + Library T Crossing
- Route 88 + Keystone Ct
- Route 88 + Phillippi Ave
- Route 88 + Colonial Ln
- Route 88 + Kings School Rd
- Route 88 + Logan Rd
- Route 88 + Sarah St
- Route 88 + Brightwood/Nazarene
- and 36 more (see the full list on the map or in the GeoJSON)
Over time
This is the first scorecard for this agency. A trend and a "what changed" summary appear here once it has been checked more than once.
Everything we checked
8 findings, ordered by severity.
Show every finding
- Warning777 instances
777 of 777 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. If every vehicle is accessible, this may be one default; otherwise use the value for each trip. (A default or per-trip field in your export.)
Finding code: scorecard_wheelchair_accessible_unknown · Read the fix guide for scorecard_wheelchair_accessible_unknown · See GTFS Schedule reference (opens the GTFS Schedule reference on an external site)
- Warning286 instances
286 of 286 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)
- Warning9 instances
Some route long names repeat the route's short name inside them.
Apps show both names together, so riders see the number twice, like '5 5 Downtown'.
Fix: Drop the short name from route_long_name and keep the long name descriptive, like 'Downtown via 5th Ave'. (One field per flagged route.)
Finding code: route_long_name_contains_short_name · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning3 instances
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.)
Finding code: route_short_name_too_long · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning2 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 streets or point riders to the wrong corner.
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)
- Warning1 instance
feed_info.txt lists no contact email and no contact URL.
Without a contact, apps like Google Maps can't reach you when they find a problem in the feed.
Fix: Add feed_contact_email or feed_contact_url to feed_info.txt. (One field, set once in export settings.)
Finding code: missing_feed_contact_email_and_url · Read the fix guide for missing_feed_contact_email_and_url · 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)
- 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)
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 284 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) Different (allowed)
- Your feed's agency_id is 0; your National Transit Database ID is 30061. A feed that serves several agencies (a shared regional feed) can legitimately carry more than one agency_id. The values do not need to equal the five-digit NTD ID, so this difference is allowed and carries no score. Confirm that P-50 crosswalks agency_id 0 to NTD ID 30061, and keep the feed value stable. Do not change it solely to make the two values equal.
- shapes.txt covers your trips Ready
- All 777 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 0% of trips; the mark needs 90% of each.
- Valid Met
- Passes validation with no errors.
- Current Met
- Service data covers the next 284 days.
- Accessible Not yet
- States wheelchair access on 0% of stops and 0% 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 284 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 82 / 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 100 / 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 38 / 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 Pennsylvania portfolio: the same scorecards for every feed we track in that group, on one free page.
Similar feeds in Pennsylvania
Other scorecards in Pennsylvania, starting with the same kind of service at a similar size. Listed for comparison, not ranked.
Show your grade
Put this badge on your agency site or feed README. It updates after each completed scoring check, shows the date of that check, and links back to this scorecard. When there is no current score it says so instead of showing an old one.
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/mid-mon-valley-transit-authority/2026-10-20.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-10-20. 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.