GTFS Scorecard
← All agencies

Feed status · checked 2026-09-18

Metro McAllen

Based on the official feed source on file

Service mode Bus

78.4 / 100

First scorecard for this agency

Catalogued in Texas.

Covers 104 daysAccessibility gapsRealtime not yet published

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.

Measured 3 of 4 score categories from the official feed URL on file.

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 official feed URL on file.

Confidence describes how much the pipeline could measure this run, not the feed itself. It never changes the grade.

Top things to fix

Fix 01

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

372 of 372 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

Fix 02

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 in its category

Fix 03

Set timepoint=1 on stops that are real time checks and 0 on the rest. If every published time is a scheduled one, mark them all 1.Likely your export tool

Some rows in stop_times.txt leave the timepoint column blank. That column says whether a time is a real checkpoint or an estimate. Blank leaves apps guessing, and they may show your estimates as promises.

⏱ Usually one export setting.worth about +8 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
372 of 372 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
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.

  1. 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 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.

  2. 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 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.

  3. Set timepoint=1 on stops that are real time checks and 0 on the rest. If every published time is a scheduled one, mark them all 1. · Read the fix guide for missing_timepoint_value

    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 104 days.
Published accessibility data
Accessibility information is stated for 0% of stops and 64% 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

Correctness83.0 / 100

The MobilityData validator flagged 5 kinds of issue across 181 instances (0 error, 173 warning, 8 informational).

Freshness100.0 / 100

Service data covers the next 104 days.

Rider experience54.6 / 100

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.

Accessibility24 / 100

0% of stops state accessibility (0% marked accessible). Reflects what the feed states, not verified physical usability.

1 accessibility depth signal

  • 364 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set ("Bicentennial & Austin SB", "Bicentennial & Fresno", "Jackson & 21st 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.

Realtime qualityNot yet measured

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 372 stops.

Skip to route and stop data

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.

  • 1 (green)
  • 10 (green)
  • 11 (green)
  • 12 (green)
  • BR (blue)
  • 2 (green)
  • 3 (green)
  • 4 (green)
  • 5 (green)
  • 6 (green)
  • 7 (green)
  • 8 (green)
  • 9 (green)
  • DT (brown)
Routes in Metro McAllen's feed
RouteTypeLine color
1 Route 1Busgreen
10 Route 10Busgreen
11 Route 11Busgreen
12 Route 12Busgreen
BR Bridge RouteBusblue
2 Route 2Busgreen
3 Route 3Busgreen
4 Route 4Busgreen
5 Route 5Busgreen
6 Route 6Busgreen
7 Route 7Busgreen
8 Route 8Busgreen
9 Route 9Busgreen
DT Downtown CirculatorBusbrown
List every stop
  • 16th St & Cedar Ave
  • Hidalgo Bridge
  • Trenton & 17th
  • Central Station
  • Jackson & 21st WB
  • 23rd & Military
  • Ware & Sarah
  • Ware & Olga
  • Idela & Ware
  • Jordan & 29th
  • Jordan & 23rd
  • 23rd & Mobile
  • Colbath & 36th
  • Colbath & 29th
  • Colbath & 26th
  • Jordan & 31st
  • Ursula & Ware
  • Sarah & 30th
  • 23rd & Elmira
  • Military-STC
  • Idela & 33rd
  • Jackson & 22nd WB
  • McColl & Pecan
  • Jackson & 21st EB
  • Savannah Ave & 16th
  • Military & 27th
  • 42nd & Military
  • 23rd & Balboa
  • 23rd & Balboa
  • 23rd & Jordan
  • Ware & Military
  • 23rd & Colbath
  • Idela & 24th
  • Nolana & 29th
  • Ware & Sonora
  • 23rd & Idela
  • 23rd & Lindberg
  • Jackson & 22nd EB
  • 23rd & Uvalde
  • Ware & Jordan
  • Sarah & 27th
  • 23rd & Sarah
  • Idela & 29th
  • Vine & 35th
  • Jordan & 34th
  • Bicentennial & Austin SB
  • Bicentennial & Fresno
  • Bicentennial & Austin Park and Ride
  • Bicentennial & Erie
  • 23rd & Orchid
  • Business 83 & 22nd
  • Business 83 & 20 1/2
  • Business 83 & 22nd
  • Business 83 & 23rd
  • Bicentennial & Pecan
  • Bicentennial & Kerria
  • Bicentennial & Beech
  • Bicentennial & Date Palm
  • Bicentennial & Hackberry
  • Bicentennial & Kendelwood
  • Bicentennial & Harvey
  • Dove & Bicentennial
  • Dove & 23rd N
  • Dove & 21st
  • Bicentennial & Fern
  • Bicentenniel & Camelia
  • Bicentennial & Tamarack
  • Bicentennial & Maple
  • Bicentennial & Ivy
  • Bicentennial & Ebony
  • 29th & Pecan
  • Bus 83 & 25th
  • Nolana & 25th
  • 29th & Daffodil
  • 29th & Iris
  • Nolana & 29th
  • 29th & La Vista
  • 29th & Harvey
  • Bus 83 & 26th
  • Bus 83 & 27th
  • Nolana & 23rd
  • 29th & Tamarack
  • 29th & Ebony
  • 29th & Pecan
  • Bus 83 & 23rd
  • 29th & Quince
  • 29th & Tamarack
  • 29th & Iris
  • 29th & Daffodil
  • 29th & Harvey
  • 29th & Quince
  • 29th & Gumwood
  • Wichita & Bicentennial
  • Bicentennial & Wichita
  • Uvalde & Main
  • 15th St & Gumwood Ave
  • 10th & Bales
  • 10th & Bluebird
  • 10th & Wisteria
  • 10th & Datepalm
  • 10th & Beech
  • 10th & Gumwood
  • 10th & Quince
  • 10th & Shasta
  • 10th & Wisconsin
  • 10th & Fern
  • 10th & Martin
  • 10th & Nolana
  • 10th & Trenton
  • 10th & Dove
  • 10th & Zinnia
  • 10th & Shasta
  • 10th & Frontera
  • 10th & Trenton
  • 10th & Jasmine
  • 10th & Robin
  • 10th & Trenton N
  • 10th & Nolana
  • 10th & Hibiscus
  • 10th & S. of Zinnia
  • 10th & Nyssa
  • 10th & La Vista
  • 10th & Jonquil
  • 10th & Harvey
  • 10th & Tamarack
  • 10th & Kerria
  • 10th & Esperanza
  • 10th & Harvey
  • 10th & La Vista
  • 10th & Upas
  • 10th & Redwood
  • 10th & Nyssa
  • 10th & Jasmine
  • 10th & Fir
  • 10th & Datepalm
  • Col Rowe & Wisconsin
  • Wisconsin & 4th
  • 10th & Valencia Market Place
  • 10th & Jay
  • 10th & Robin
  • 23rd & Hackberry
  • Frontera & 8th St
  • Frontera & 4th St
  • 23rd & Quince
  • 29th & Thunderbird
  • 23rd & Pecan
  • 23rd & Ebony
  • 23rd & Maple
  • 29th & Xenops
  • 23rd & Pecan
  • 23rd & Upas
  • 23rd & Fern
  • Lark & 25th
  • 23rd & La Vista
  • 23rd & Harvey
  • 23rd & Ivy
  • 23rd & Vine
  • 23rd & Harvey
  • Lark & 24th
  • 23rd & La Vista
  • 23rd & Maple
  • 23rd & Tamarack
  • 23rd & Daffodil
  • 23rd & Jonquil
  • 23rd & Jonquil
  • 23rd & Ebony
  • 29th & Pelican
  • 23rd & Ivy
  • Savannah & 1st
  • Houston & Main
  • K St & Ridge
  • South J St
  • Cynthia & Ridge Rd
  • E Frontage Rd & Cynthia
  • Houston & 16th1/2
  • K St & Vermont
  • Houston & 15 1/2 St
  • K St & Savannah
  • Houston & Broaday
  • Houston & Broadway
  • 10th & Houston
  • 10th & Houston
  • Ridge Rd & D St
  • Houston & 12th St
  • Ridge Rd & 2nd
  • 2nd & West Frontage Rd
  • E Frontage Rd & 6th
  • Allan Miller & 5th
  • 10th & Lindberg
  • 10th & Lindberg
  • Vermont & McColl
  • 23rd & Warbler
  • Bensten & W Frontage
  • Buddy Owens & 34th
  • Bus 83 & 40th
  • Ware & Pecan
  • Ware & Pecan N
  • Buddy Owens & 33rd
  • Ithaca at Palms Crossing
  • Ware & Camelia
  • Bus. 83 & Bensten
  • Ware & Pecan
  • Ware & Quince
  • Ware & Harvey
  • Ware & Hibiscus
  • 29th & Erie
  • Ware & Ivy
  • Ware & Gumwood
  • 29th & Bus. 83
  • Nolana & 34th
  • Ware & Gumwood
  • Ware & Jonquil
  • Ware & Daffodil
  • Bus 83 & 31st
  • McColl & Upas
  • McColl & La Vista
  • McColl & Whitewing
  • Pecan & McColl
  • Pecan & McColl
  • McColl & Esperanza
  • McColl & Jonquil
  • Nolana & 23rd
  • Nolana & 16th
  • Nolana & 12th
  • Nolana & 8th
  • Nolana & 5th
  • Nolana & Cynthia
  • Nolana & Bicentennial
  • Pecan & 10th
  • Nolana & McColl
  • McColl & Jonquil
  • McColl & Fern
  • McColl & Whitewing
  • McColl & Vine
  • Pecan & 1st
  • Pecan & 6th
  • Pecan & 9th
  • Pecan & 11th
  • Main & Maple
  • Main & Jasmine
  • Main & Fir
  • 15th & Cedar
  • Datepalm & 15th
  • Main & Ebony
  • Main & Gumwood
  • Main & Jasmine
  • Main & Orange
  • Pecan & 13 1/2
  • Pecan & 6th
  • Pecan & 3rd
  • and 122 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
  • Warning372 instances

    372 of 372 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

  • Warning171 instances

    Some rows in stop_times.txt leave the timepoint column blank.

    That column says whether a time is a real checkpoint or an estimate. Blank leaves apps guessing, and they may show your estimates as promises.

    Fix: Set timepoint=1 on stops that are real time checks and 0 on the rest. If every published time is a scheduled one, mark them all 1. (Usually one export setting.)

    Finding code: missing_timepoint_value · Read the fix guide for missing_timepoint_value · See MobilityData GTFS Validator rules

  • Warning136 instances

    136 of 378 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

  • 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.)

    Finding code: expired_calendar · Read the fix guide for expired_calendar · See MobilityData GTFS Validator rules

  • Warning1 instance

    Some rider-facing names are in ALL CAPS or all lowercase.

    ALL-CAPS stop and headsign names are harder to read in apps and are read awkwardly by screen readers.

    Fix: Use mixed case for stop names and headsigns (e.g. 'Main St & 2nd Ave', not 'MAIN ST & 2ND AVE'). (Often a bulk fix in your scheduling software.)

    Finding code: mixed_case_recommended_field · Read the fix guide for mixed_case_recommended_field · See MobilityData GTFS Validator rules

  • 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

  • Info5 instances

    The feed has a stretch of two weeks or more with no service running.

    A long gap can mean dates were left out of the calendar. Apps then show no trips on those days.

    Fix: Check whether the gap is real, like a seasonal break; if not, add the missing dates to the calendar. (A review of your calendar dates.)

    Finding code: big_gap_in_service · Read the fix guide for big_gap_in_service · See MobilityData GTFS Validator rules

  • 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.)

    Finding code: unknown_column · Read the fix guide for unknown_column · See MobilityData GTFS Validator rules

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 104 days.
agency_id provided Ready
agency.txt provides agency_id. For RY2026, keep one stable value for each NTD reporter represented in the feed and crosswalk each value on the P-50 form.
agency_id equals your NTD ID (optional) Not checked yet
This feed provides agency_id. For RY2026, keep one stable value for each NTD reporter represented in the feed and crosswalk it on the P-50 form. The value does not need to equal the five-digit NTD ID; we do not have that ID on file, so the optional equality comparison is not checked yet.
shapes.txt covers your trips Ready
All 378 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 64% of trips; the mark needs 90% of each.

Valid Met
Passes validation with no errors.
Current Met
Service data covers the next 104 days.
Accessible Not yet
States wheelchair access on 0% of stops and 64% 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 104 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 83 / 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 55 / 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.

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.

Metro McAllen GTFS data quality grade: C

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/metro-mcallen/2026-09-18.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-09-18. 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.