Feed status · checked 2026-08-01
Mountain Line Transit
Based on the feed this agency publishes
Service mode Bus
unchanged since 2026-07-31
Catalogued in Arizona.
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.3, validator 8.0.1.
Checked for changes 3 hours ago; last changed 16 hours ago.
Measured 4 of 4 score categories from the agency's own feed.
How we measured this
Confidence in this measurement: high.
- All four score categories were measured this run.
- Realtime was sampled in one bounded window of 9 snapshots.
- 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
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
181 of 181 stops don't say whether a wheelchair user can board there. Riders who use wheelchairs can't plan a trip when accessibility is marked 'unknown'; apps show no information at all.
⏱ A column in stops.txt; your scheduling software likely has it.worth about +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
2753 of 2753 trips don't say whether the vehicle is wheelchair accessible. Even with accessible stops, riders need to know the bus itself can take them.
⏱ A default or per-trip field in your export.worth about +15 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 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 in its category
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.
- Feed evidence
- 181 of 181 stops don't say whether a wheelchair user can board there.
- Next action
- Set wheelchair_boarding to 1 (accessible) or 2 (not accessible) for every stop. A field survey can start with the busiest stops.
- 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
- Feed evidence
- 2753 of 2753 trips don't say whether the vehicle is wheelchair accessible.
- Next action
- Set wheelchair_accessible on every trip. If every vehicle is accessible, this may be one default; otherwise use the value for each trip.
- 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
- Feed evidence
- feed_info.txt is missing its start/end dates
- Next action
- Add feed_info.txt with feed_start_date and feed_end_date to your export.
- 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.
Set wheelchair_boarding to 1 (accessible) or 2 (not accessible) for every stop. A field survey can start with the busiest stops. · Read the fix guide
Make the change. Make this change in whatever tool produces your feed, then re-export.
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.
Set wheelchair_accessible on every trip. If every vehicle is accessible, this may be one default; otherwise use the value for each trip. · Read the fix guide
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.
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.
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 states that service is published through 2099-12-31. This may be intentional or a placeholder; confirm current service with the transit operator.
- 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
- Live-arrival data covered 80% of scheduled trips in the sampled window.
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 9 kinds of issue across 434 instances (0 error, 427 warning, 7 informational).
Service is published through 2099-12-31. It may be intentional, but confirm the end date before treating the feed as maintained.
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 (4, 5, 66).
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.
130 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set ("Route 66 / Thompson St (Mavrik) WB", "Route 66 / Railroad Springs Blvd WB", "Route 66 / Northwestern St (Hidden Hollow) WB", 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.
Sampled 9 times: 3 of 3 configured feeds healthy; 80.0% of scheduled trips had live predictions; 95.7% of vehicles on their route; predictions ran a median of 106s ahead of schedule.
Routes and stops
Each route is drawn once, using the longest shape its trips follow; stops are the dots.
This feed has 181 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.
- 2 (blue)
- 3 (green)
- 4 (orange)
- 5 (orange)
- R14 (brown)
- 7 (purple)
- R10 (red)
- 66 (red)
- 8 (teal)
| Route | Type | Line color |
|---|---|---|
| 2 Route 02 - Blue | Bus | blue |
| 3 Route 03 - Green | Bus | green |
| 4 Route 04 - Gold | Bus | orange |
| 5 Route 05 - Orange | Bus | orange |
| R14 Route 14 - Brown | Bus | brown |
| 7 Route 07 - Purple | Bus | purple |
| R10 Route 10 - Maroon | Bus | red |
| 66 Route 66 - Red | Bus | red |
| 8 Route 8 to Woody Mountain Road | Bus | teal |
List every stop
- Route 66 / Thompson St (Mavrik) WB
- Route 66 / Railroad Springs Blvd WB
- Route 66 / Northwestern St (Hidden Hollow) WB
- Woody Mountain Rd. / Patio del Presidio
- Rt. 66 / Northwestern St. (Wildwood Hills)
- Beulah Blvd. / University
- Beulah Blvd./ University Av. (Roundabout) NB
- Route 66 / Railroad Springs Blvd. (Heartwood RV Park)
- McAllister Ranch Rd./ Alvan Clark Blvd. (Atlas Timber Sky)
- Pine Cliff Dr (Lofts on the Mesa)
- Gemini Rd. (Arizona State Veteran Home)
- McAllister Ranch Rd./ Charon Way
- Alvan Clark Blvd. / Rt. 66 (Sierra on 66)
- Rt. 66 / Woody Mountain Rd. (Liv Timber Sky)
- N. 89 (Sacred Peaks Access)
- Kaspar (NAIPTA) WB
- Lockett / Fanning WB
- Lockett / Manor
- Lockett / Alta Vista WB
- Lockett / King WB
- Cedar Plaza WB
- Cedar / West WB
- Cedar / Gemini SB
- Forest / Turquoise WB
- Beaver (FMC) SB
- Beaver / Hunt
- Beaver / Birch
- Downtown Connection Center
- San Francisco / Birch
- San Francisco / Elm
- Beaver St/Desilva Av
- Beaver (FMC) NB
- Forest / Turquoise EB
- Cedar / Gemini NB
- Cedar / West EB
- Cedar / Aris EB
- Lockett / King EB
- Lockett / Alta Vista EB
- Lockett / Fanning EB
- Kaspar (NAIPTA) EB
- Lynch (FUTS Trail)
- Flagstaff Mall Connection Ctr
- Cummings / Lynch
- Soliere / Country Club
- Soliere (Timberline) WB
- Soliere (Butterfield) WB
- Soliere / Elk Run WB
- Soliere / Foxlair (East) WB
- Soliere / Foxlair (West) WB
- Foxglenn / Butler SB
- Butler (Black Barts)
- Butler / Lucky WB
- Butler (Golden Eagle) WB
- Butler WB (L&W Supply)
- Butler / Sawmill WB
- Butler / Elden WB
- Butler / San Francisco WB
- Kendrick / Benton
- Butler / San Francisco EB
- Butler / Elden EB
- Butler / Cambridge EB
- Butler EB (Marathon)
- Butler (Napa)
- Butler (Filiberto's)
- Butler (Little America)
- Foxglenn / Butler NB
- Soliere / Foxlair (West) EB
- Soliere / Foxlair (East ) EB
- Soliere / Elk Run EB
- Soliere (Butterfield) EB
- Soliere (Timberline) EB
- Country Club (B of A)
- Route 66 / Country Club
- Milton (Taco Bell)
- Milton Rd. / Fresquez Av. (Wendy's)
- Beulah (Wal-Mart)
- Lake Mary / I-17 underpass
- Lake Mary / High Country Trail
- Lake Mary / Mohawk
- Walapai/Lake Mary
- Walapai / Yaqui (Forest Ridge Apts North)
- Zuni / Kofa
- Lone Tree (CCC)
- Lone Tree / Pine Knoll
- Lone Tree / Brannen
- Lone Tree / Franklin
- Fort Valley / Winding Brook
- Fort Valley / Valley Crest
- Peak View / Mountain
- Peak View / Cooper
- Peak View / Fremont
- Fremont / Lynette
- Fremont (Cheshire Park)
- Fremont (FALA)
- Fort Valley (Museum of N. AZ)
- Fort Valley / Stevanna
- Fort Valley / Meade SB
- Fort Valley / Whipple
- Thorpe / Bonito WB
- Thorpe (Clark Homes) WB
- Thorpe (Ball Fields) SB
- Thorpe (Adult Center) SB
- Santa Fe / Park EB
- Aspen (City Hall) EB
- Beaver / Phoenix
- Lone Tree / Franklin
- Lone Tree / Brannen
- Lone Tree / Pine Knoll
- Lone Tree (CCC)
- Zuni / Kofa
- Walapai / South Yaqui
- Walapai / Lake Mary
- Lake Mary / Mohawk
- Lake Mary / High Country Trail
- Lake Mary / Beulah
- Beulah / McConnell
- Milton / University (Target)
- Milton / Plaza Way
- Milton Rd. / Butler Av. (NAU)
- Aspen (City Hall) WB
- Santa Fe / Park WB
- Thorpe (Adult Center) NB
- Thorpe (Ball Fields) NB
- Thorpe (Clark Homes) EB
- Thorpe / Bonito EB
- Fort Valley / Forest
- Fort Valley / Meade NB
- Fort Valley (Pioneer Museum)
- Sixth / Third WB
- Sixth / First WB
- Sixth / West WB
- West / Felice NB
- Fourth / Felice SB
- Fourth at Route 66 SB
- Fourth / Huntington SB
- Huntington (Walmart) WB
- Route 66 / Riordan Rd. (The Standard)
- Route 66 / Pinnacle
- Thompson St
- University Av. / Forest Meadows St. (True North Dentistry)
- Woodlands Village Blvd. / University Av.
- Route 66 / Woodlands Village Blvd. (Doubletree)
- Route 66 / Metz Walk
- Huntington Dr. / Grant St. EB
- Huntington (Walmart) EB
- Fourth / Huntington NB
- Fourth NB (Walgreens)
- Huntington Dr. / Grant St. WB
- Beaver / Franklin SB
- Beaver (Gillenwater)
- University (Wilson)
- Knoles (Campus Heights) SB
- McConnell (SBS) WB
- Forest Meadows (Shell)
- Forest Meadows (Apts.)
- Woodlands Village
- McConnell (SBS) EB
- Knoles (Campus Heights) NB
- University (Reilly)
- Beaver (NAU Bookstore)
- Beaver / Franklin NB
- Route 66 / Fanning WB
- Route 66 / Steves WB
- Route 66 / Fourth WB
- Route 66 / Arrowhead WB
- Route 66 / Ponderosa WB
- Route 66 / Switzer WB
- Route 66 / San Francisco
- Route 66 / Switzer EB
- Route 66 / Ponderosa EB
- Route 66 / Arrowhead EB
- Route 66 / Fourth EB
- Route 66 / Steves EB
- Route 66 / Fanning EB
- Highway 89 / Smokerise
- Christmas Tree / Snowflake
- Winter / Christmas Tree
- Gemini Rd. (BASIS/FJA)
- Fourth / Sparrow (NPA) SB
- Fourth / Sparrow (NPA) NB
- Fourth / Cedar SB
Over time
Overall score across the last 4 checks — unchanged since 2026-07-31.
Show the numbers
| Check | Score | Change |
|---|---|---|
| 2026-07-25 | 70.8 | first check |
| 2026-07-30 | 67.8 | down 3.0 |
| 2026-07-31 | 67.8 | no change |
| 2026-08-01 | 67.8 | no change |
What changed since your last check
- Correctness no change
- Freshness no change
- Rider experience down 0.4
- Realtime quality up 0.5
What changed over time
On 2026-07-25 this feed started at grade C. On 2026-07-30 the grade moved from C to D. As of 2026-08-01 it holds grade D.
A plain-language history of this feed, newest first.
- 2026-07-30 Grade went C to D, realtime fell 8 points.
Everything we checked
15 findings, ordered by severity.
Show every finding
- Warning2753 instances
2753 of 2753 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 · See GTFS Schedule reference (opens the GTFS Schedule reference on an external site)
- Warning710 instances
710 of 2753 trips lack rider-facing destination or direction text.
When a route has multiple directions or patterns, the route name alone may not tell riders which service is coming.
Fix: Add the destination, direction, or 'via' label riders actually see to trip_headsign. Do not copy the route name. If the label changes during the trip, use stop_headsign. (Usually one value per route pattern in your scheduling source.)
Finding code: scorecard_missing_headsigns · Read the fix guide · See GTFS Best Practices (opens GTFS Best Practices on an external site)
- Warning398 instances
On some trips the stop distances run a little past the end of the route line.
The stop and shape distance values don't quite line up, so any math that uses them can drift.
Fix: Re-generate shape_dist_traveled on export so stop and shape distances use the same units. (Usually an export-tool fix, not hand editing.)
Finding code: trip_distance_exceeds_shape_distance_below_threshold · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning181 instances
181 of 181 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 · See GTFS Schedule reference (opens the GTFS Schedule reference on an external site)
- Warning12 instances
Some route lines list the same point twice in a row.
Repeated points don't hurt riders, but they can skew distance math and hint at a shaky export.
Fix: Turn on shape cleanup in your export tool, or drop the repeated points from shapes.txt. (Usually one export setting.)
Finding code: equal_shape_distance_same_coordinates · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning7 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 · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning5 instances
Some values have extra spaces at the start or end.
A stray space can break a match, so a stop or route may fail to link across files.
Fix: Trim leading and trailing spaces on export. The scorecard's auto-fixed copy already does this. (Usually one export setting.)
Finding code: leading_or_trailing_whitespaces · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning3 instances
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.)
Finding code: expired_calendar · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning2 instances
2 of 10 trips scheduled during the sampling window had no live predictions.
Riders on those trips get schedule data dressed up as realtime. Caltrans expects every operating trip in TripUpdates.
Fix: Check with your AVL vendor that every vehicle assignment flows into TripUpdates, including school-day and tripper runs. (A vendor data-mapping question.)
Finding code: scorecard_rt_trip_coverage · Read the fix guide · See GTFS-Realtime reference (opens the GTFS-Realtime reference on an external site)
- Warning1 instance
feed_info.txt does not state when this feed starts and ends.
Without stated dates, apps can't warn anyone before your data goes stale; it just disappears one day.
Fix: Fill in feed_start_date and feed_end_date in feed_info.txt. (Two fields, likely set once in your export settings.)
Finding code: missing_feed_info_date · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning1 instance
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.)
Finding code: missing_recommended_field · 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
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 · 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 · See GTFS Best Practices (opens GTFS Best Practices on an external site)
- Info4 instances
Service extends far in the future (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'service_extends_far_in_the_future' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Finding code: service_extends_far_in_the_future · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Info3 instances
The feed includes a file that is not part of the GTFS spec.
Apps ignore files they don't know, and a stray file can hide a misspelled standard file name.
Fix: Check the flagged file name for a typo of a standard GTFS file. Remove it if it is a vendor extra. (A quick look at the flagged file.)
Finding code: unknown_file · Read the fix guide · 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
- The published window is current, but its service end date is unusually distant; confirm that date is intentional.
- 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 2753 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
This feed is close to 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
- The published window is current, but its service end date is unusually distant; confirm that date is intentional.
- 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.
Realtime reliability
The realtime feed responded on 100.0% of 200 checks over the last 34 days, with 0s median lag.
Sampled on a schedule between full scores, so this tracks uptime and freshness over time rather than at a single moment.
Live predictions vs schedule
Arrival predictions ran a median 106s early versus the schedule, and stayed within 305s nine times in ten. They were on time (about a minute early to five late) 37.3% of the time. 95.7% of reported vehicle positions sat on or near the published route shape.
From the last full realtime sample: how far live arrival predictions sat from the schedule, and whether vehicle positions fell on the route. These feed the realtime score; they change no other category.
Clears the Google and Apple Maps four-week coverage bar. This feed clears the four-week coverage window, but its service end date is unusually distant. Confirm that date is intentional before treating it as evidence of ongoing maintenance. 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 63 / 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 41 / 100
- GTFS Best Practices for rider-facing fields. MobilityData grading covers stop names and headsigns.
- Realtime quality 92 / 100
- GTFS-Realtime best practices: a stable URL, high uptime, and frequent updates.
Show your grade
Put a badge on your agency site or feed README. It updates after each completed scoring check 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/2026-08-01.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-08-01. 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.