Feed status · checked 2026-08-23
VIA Metropolitan Transit (VIA)
Based on the feed source on file; publisher ownership is not verified
Service mode Bus
unchanged since 2026-08-22
Catalogued in Texas.
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 15 hours ago; last changed 15 hours 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.
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
6100 of 6100 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
29254 of 29254 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 (the file itself is absent) Apps and this scorecard can't warn anyone before the feed goes stale without stated validity dates.
⏱ Two fields, set once in export settings.worth about +15 points 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
- 6100 of 6100 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
- 29254 of 29254 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 (the file itself is absent)
- 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's last published service date is in 140 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
- Fare information is published using GTFS Fares v1.
- 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 12 kinds of issue across 1420409 instances (0 error, 1420131 warning, 278 informational).
Service data covers the next 140 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 published.
0% of stops state accessibility (0% marked accessible). Reflects what the feed states, not verified physical usability.
2 accessibility depth signals
32 route badge(s) pair a color and text color below the WCAG 4.5:1 contrast bar (214, 225, 289, 288, 282, 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.
4928 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set ("S.W. 35TH & OLGA", "Blanco & Mt Capote", "WIND BURN TR. BET. WELLS FARGO & TRAPPERS RDG", 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.
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.
This feed has 6100 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.
- 10 (red)
- 100 (red)
- 102 (red)
- 103 (red)
- 14 (red)
- 17 (teal)
- 2 (red)
- 20 (red)
- 204 (gray)
- 21 (red)
- 214 (gray)
- 22 (teal)
- 222 (gray)
- 225 (gray)
- 230 (gray)
- 232 (gray)
- 24 (red)
- 242 (gray)
- 25 (red)
- 251 (gray)
- 26 (teal)
- 268 (gray)
- 275 (gray)
- 276 (gray)
- 28 (red)
- 282 (gray)
- 288 (gray)
- 289 (gray)
- 3 (red)
- 30 (teal)
- 32 (gray)
- 34 (red)
- 36 (gray)
- 4 (red)
- 42 (gray)
- 43 (teal)
- 44 (teal)
- 46 (teal)
- 5 (teal)
- 501 (gray)
- 502 (teal)
- 503 (gray)
- 505 (teal)
- 509 (gray)
- 51 (teal)
- 515 (teal)
- 522 (gray)
- 524 (red)
- 534 (red)
- 552 (red)
- 602 (teal)
- 603 (teal)
- 604 (gray)
- 607 (gray)
- 609 (teal)
- 610 (gray)
- 611 (teal)
- 612 (teal)
- 615 (teal)
- 616 (teal)
- 618 (teal)
- 619 (teal)
- 620 (teal)
- 62 (gray)
- 62 (teal)
- 632 (teal)
- 64 (teal)
- 647 (gray)
- 648 (gray)
- 649 (teal)
- 651 (gray)
- 66 (gray)
- 67 (gray)
- 68 (red)
- 7 (teal)
- 75 (red)
- 76 (red)
- 77 (red)
- 79 (teal)
- 8 (teal)
- 82 (red)
- 88 (red)
- 89 (gray)
- 89 (teal)
- 9 (teal)
- 90 (teal)
- 92 (gray)
- 93 (red)
- 95 (red)
- 96 (red)
- 97 (teal)
| Route | Type | Line color |
|---|---|---|
| 10 Naco / Broadway Skip | Bus | red |
| 100 Primo Fredericksburg Road | Bus | red |
| 102 Primo Military | Bus | red |
| 103 Primo Zarzamora | Bus | red |
| 14 Perrin Beitel Skip | Bus | red |
| 17 IH-35 Express | Bus | teal |
| 2 Blanco Frequent | Bus | red |
| 20 New Braunfels Frequent | Bus | red |
| 204 San Pedro / McCullough 4-5 Lineup | Bus | gray |
| 21 Kirby / Ventura Frequent | Bus | red |
| 214 Austin Hwy / Randolph 14-17 Lineup | Bus | gray |
| 22 Hays | Bus | teal |
| 222 Hays / E Houston 22-24 Lineup | Bus | gray |
| 225 E Commerce / MLK 25-26 Lineup | Bus | gray |
| 230 Rigsby / Porter 30-28 Lineup | Bus | gray |
| 232 Steves / S St Marys 32-34 Lineup | Bus | gray |
| 24 East Houston Frequent | Bus | red |
| 242 Roosevelt / S Presa 42-36 Lineup | Bus | gray |
| 25 East Commerce Frequent | Bus | red |
| 251 Nogalitos / Kirk 51-62 Lineup | Bus | gray |
| 26 Martin Luther King | Bus | teal |
| 268 Guadalupe / Ceralvo 68-66 Lineup | Bus | gray |
| 275 Commerce / Laredo 75-67 Lineup | Bus | gray |
| 276 Commerce / Kel-Lac TC 76-64 Lineup | Bus | gray |
| 28 Porter Frequent | Bus | red |
| 282 Culebra 82 Lineup | Bus | gray |
| 288 Bandera / Evers 88 Lineup | Bus | gray |
| 289 Poplar / Woodlawn 89-90 Lineup | Bus | gray |
| 3 San Pedro Skip | Bus | red |
| 30 Rigsby | Bus | teal |
| 32 Steves | Bus | gray |
| 34 South St Marys Frequent | Bus | red |
| 36 South Presa | Bus | gray |
| 4 San Pedro Frequent | Bus | red |
| 42 Roosevelt | Bus | gray |
| 43 South Flores | Bus | teal |
| 44 Pleasanton | Bus | teal |
| 46 Commercial | Bus | teal |
| 5 McCullough | Bus | teal |
| 501 UTSA / Leon Valley | Bus | gray |
| 502 Thousand Oaks / Converse | Bus | teal |
| 503 Huebner Crosstown | Bus | gray |
| 505 Basse | Bus | teal |
| 509 Hildebrand | Bus | gray |
| 51 Nogalitos | Bus | teal |
| 515 Southcross | Bus | teal |
| 522 Babcock | Bus | gray |
| 524 General McMullen Frequent | Bus | red |
| 534 Wurzbach Frequent | Bus | red |
| 552 Loop 410 / W. W. White Skip | Bus | red |
| 602 Medical Center / Blossom | Bus | teal |
| 603 Medical Center / UTSA | Bus | teal |
| 604 Medical Center / University Heights | Bus | gray |
| 607 Medical Center / Ingram | Bus | gray |
| 609 Medical Center / Ingram / Kel-Lac | Bus | teal |
| 610 Ingram / Northwest Crossing | Bus | gray |
| 611 Kel-Lac / Valley-Hi / Hidden Cove | Bus | teal |
| 612 Kel-Lac / Westlakes / Ingram | Bus | teal |
| 615 Kel-Lac / Heritage Park | Bus | teal |
| 616 Sky Harbor / Kel-Lac | Bus | teal |
| 618 Ingram / Westover Hills / Kel-Lac | Bus | teal |
| 619 Kel-Lac / Port SA | Bus | teal |
| 620 Northwest Vista College / Ingram | Bus | teal |
| 62 Kirk | Bus | gray |
| 62 Kirk | Bus | teal |
| 632 Randolph / Ventura | Bus | teal |
| 64 US 90 Alamo Ranch Express | Bus | teal |
| 647 North Star / Harry Wurzbach | Bus | gray |
| 648 North Star / Stone Oak | Bus | gray |
| 649 North Star / N Blanco / Stone Oak | Bus | teal |
| 651 Deco District / Castle Hills | Bus | gray |
| 66 Ceralvo | Bus | gray |
| 67 Laredo | Bus | gray |
| 68 Guadalupe Frequent | Bus | red |
| 7 US 281 Stone Oak Express | Bus | teal |
| 75 West Commerce Frequent | Bus | red |
| 76 West Commerce Skip | Bus | red |
| 77 Martin / Las Palmas Frequent | Bus | red |
| 79 Ruiz / Culebra Park | Bus | teal |
| 8 North St Marys | Bus | teal |
| 82 Culebra Frequent | Bus | red |
| 88 Bandera Frequent | Bus | red |
| 89 Poplar | Bus | gray |
| 89 Poplar | Bus | teal |
| 9 Broadway | Bus | teal |
| 90 Woodlawn | Bus | teal |
| 92 Brooks / Medical Center Express | Bus | gray |
| 93 Roadrunner Express | Bus | red |
| 95 Fredericksburg Road Frequent | Bus | red |
| 96 Vance Jackson Frequent | Bus | red |
| 97 West Avenue | Bus | teal |
List every stop
- NORTH STAR TRANSIT CENTER
- NORTH STAR TRANSIT CENTER
- NORTH STAR TRANSIT CENTER
- NORTH STAR TRANSIT CENTER
- NORTH STAR TRANSIT CENTER
- NORTH STAR TRANSIT CENTER
- NORTH STAR TRANSIT CENTER
- NORTH STAR TRANSIT CENTER
- North Star Transit Center
- NORTH STAR TRANSIT CENTER
- HUISACHE STATION
- HUISACHE STATION
- MARY LOUISE STATION
- MARY LOUISE STATION
- BABCOCK STATION
- BABCOCK STATION
- DE CHANTLE STATION
- DE CHANTLE STATION
- CROSSROADS STATION
- CROSSROADS STATION
- CALLAGHAN STATION
- CALLAGHAN STATION
- EWING HALSELL STATION
- EWING HALSELL STATION
- UNIVERSITY HOSPITAL STATION
- UNIVERSITY HOSPITAL STATION
- VANCE JACKSON OPPOSITE 16333
- Vance Jackson in front of 16333
- EASTBOUND LOOP 1604 & TRADESMAN
- WESTBOUND LOOP 1604 OPPOSITE TRADES
- VANCE JACKSON ACROSS FROM 16631
- MADLA TRANSIT CENTER
- WURZBACH & IRONSIDE
- WURZBACH & IRONSIDE
- GUADALUPE & SABINAS
- EVERS & BANDERA
- EVERS & BANDERA
- GUADALUPE & SABINAS
- EVERS & WILDFLOWER
- EVERS OPPOSITE WILDFLOWER
- North Loop 1604 W in front of 4553
- EASTBOUND LOOP 1604 @ VIA SHAVANO
- WESTBOUND LOOP 1604 & LOCKHILL-SELM
- HUEBNER & EVERS
- S. ST. MARY'S & CESAR CHAVEZ BLVD
- EVERS OPPOSITE E. ROLLING RIDGE
- CESAR CHAVEZ BLVD & S. ST. MARY'S
- CESAR CHAVEZ BLVD & S. PRESA
- EVERS & E. ROLLING RIDGE
- EVERS OPPOSITE FAIRFORD
- WESTBOUND LOOP 1604 & MILITARY HWY.
- HUEBNER & EVERS
- EVERS & DAUGHTRY
- E. SOUTHCROSS & GEVERS
- TORINO & VEGA
- TORINO OPPOSITE VEGA
- EVERS & HUEBNER
- QUINTANA & GRIFFIN
- QUINTANA OPPOSITE GRIFFIN
- E. SOUTHCROSS & GEVERS
- CESAR CHAVEZ BLVD & S. ALAMO
- CESAR CHAVEZ & S. ALAMO
- THOUSAND OAKS & TURKEY POINT
- CLIFFBRIER & BROAD FOREST
- GALLERY RIDGE & BROAD FOREST
- THOUSAND OAKS & TURKEY POINT
- E. SOUTHCROSS & HILLJE
- ESCALON & BAETZ
- E. SOUTHCROSS OPPOSITE HILLJE
- EVERS & FAIRFORD
- FREDERICKSBURG RD. & FULTON
- EVERS OPPOSITE DAUGHTRY
- MADLA TRANSIT CENTER
- EVERS & GLEN RIDGE
- MADLA TRANSIT CENTER
- MADLA TRANSIT CENTER
- S ALAMO OPPOSITE REFUGIO & LAVACA
- HUEBNER & BALKY
- HUEBNER & REDBIRD LN
- WURZBACH & BABCOCK
- BABCOCK & WURZBACH
- MADLA TRANSIT CENTER
- Laureate Dr at Turn Around
- MARBACH IN FRONT OF HEB PLUS
- FLANDERS OPPOSITE OREY
- OREY & FLANDERS
- LAS PALMAS SHOPPING CENTER
- Las Palmas Shopping Center
- Wurzbach at 7230 Wurzbach
- Wurzbach at 7171 Wurzbach
- MARBACH & LOOP 410 S ACCESS RD.
- ACME RD & ARDMORE
- LA CANTERA & LOOP 1604 W ACCESS R
- Las Palmas Exit & Castroville
- BARRERA & S. ALAMO
- VANCE JACKSON IN FRNT OF 16631
- EVERS BETWEEN GRASS VALLEY & TEAL
- ESCALON OPPOSITE FAULK
- EVERS BETWEEN TEALEAF & GRASS VAL
- JOHN PEACE & LOOP 1604 E ACCESS R
- FREDERICKSBURG RD. & CALAVERAS
- S. PRESA & CAMARGO (S. ALAMO)
- LA CANTERA ENTRAN. SHOPS LA CANTERA
- LA CANTERA OPP. ENTR/SHOPS LA CANT.
- FREDERICKSBURG RD. & SUMMIT
- S ST. MARY'S & ALAMO
- S. ST. MARY'S & ALAMO
- FREDERICKSBURG RD. & AGARITA
- CLIFFBRIER & TREE VILLAGE
- CLIFFBRIER & TREE VILLAGE
- Wurzbach at 7110 Wurzbach
- S. ALAMO & BARRERA
- SW LOOP 410 S ACCESS RD AT 1749
- SW LOOP 410 N ACCESS RD & LATIGO
- UTSA LOOP 1604 CAMPUS (1st Stop)
- UTSA LOOP 1604 CAMPUS (2nd Stop)
- LAUREATE DR. & PRUE RD.
- LAUREATE DR. & PRUE RD.
- S. PRESA & CALLAGHAN AVE.
- S. PRESA OPPOSITE SAN ARTURO (701)
- FREDERICKSBURG RD. OPP. MULBERRY
- CESAR CHAVEZ BLV OPP J.H. WOOD BLDG
- WURZBACH & MELROSE- HOLMGREEN
- WURZBACH OPPOSITE MELROSE HOLMGREEN
- CESAR CHAVEZ FRNT OF J.H. WOOD BLDG
- JUNIPER OPPOSITE BARKMEYER
- PATRICIA IN FRONT OF 1300
- PATRICIA IN FRONT OF 1401
- FIVE PALMS IN FRONT OF 5706
- FIVE PALMS IN FRONT OF 5715
- GUADALUPE & TRINITY
- RAY BON BET. GALAHAD & PRINCE
- RAY BON BET. PRINCE VALIANT AN
- GUADALUPE & TRINITY
- RAY ELLISON & OLD VALLEY HI DR
- Old Sky Harbor opposite Ocean Port
- E. SOUTHCROSS & LYRIC
- E. SOUTHCROSS & LYRIC
- GUADALUPE & SAN JACINTO
- COMMERCIAL & GILLETTE
- GUADALUPE & SAN JACINTO
- COMMERCIAL & BAETZ
- COMMERCIAL & BAETZ
- E. SOUTHCROSS OPP. PECAN GROVE
- E. SOUTHCROSS & PECAN GROVE
- CASTROVILLE OPPOSITE INCA
- Castroville between SW 26th & Inca
- ST. CLOUD & SEELING
- MARBACH IN FRONT OF 8103 (PEP BOYS)
- MARBACH & HARNESS
- MERTON-MINTER OPP MELROSE-HOLMGREEN
- MERTON-MINTER & MELROSE-HOLMGREEN
- MARBACH OPPOSITE MEADOW WAY
- MEADOW WAY & MARBACH
- MEADOW WAY & MARBACH
- MARBACH & MEADOW WAY
- BABCOCK BTWN WURZBACH & BEVERLY
- CESAR CHAVEZ BLVD & INDIANOLA
- ST. CLOUD & BEVERLY
- CESAR CHAVEZ OPPOSITE INDIANOLA
- THOUSAND OAKS IN FRONT OF 2250
- THOUSAND OAKS OPPOSITE 2250
- GILLETTE IN FRONT OF 625
- GILLETTE BTWN ESCALON AVE. & ROCKWELL BLVD.
- HENDERSON PASS IN FRONT OF 16081
- GILLETTE & ZARZAMORA
- COMMERCIAL & GILLETTE
- RAY BON BETWEEN MERLIN & LAN
- RAY BON BETWEEN LANCELOT & M
- FREDERICKSBURG RD. & CLARKE RD.
- FREDERICKSBURG RD. & CLUB (PRIVATE RD)
- AUSTIN HWY. IN FRONT OF 1955
- LEBANON & GOLIAD RD.
- AUSTIN HWY. FRONT N.E. PROF.BLDG.
- RAY ELLISON BETWEEN MAPLE VALLEY AN
- FIVE PALMS OPPOSITE CENTURY
- HENDERSON PASS BETWEEN THOUSAND OAKS & ROUGH OAKS
- BARRERA & INDIANOLA
- BARRERA & INDIANOLA
- St. Cloud opposite Summit
- St. Cloud & Mulberry
- FIVE PALMS OPPOSITE SEASHELL
- US Hwy 281 S Access & Encino Rio
- US Hwy 281 S Access btwn Stone Oak & Evans
- BULVERDE & NACO PERRIN
- US Hwy 281 N btwn Encino Rio & Evans
- US Hwy 281 N & Encino Commons
- FREDERICKSBURG RD. & PRUE RD.
- HARNESS & REMUDA
- HARNESS OPPOSITE REMUDA
- COMMUNITY LIBRARY
- HWY 281 S ACCESS RD FRONT OF BEST WESTERN MOTEL
- COMMUNITY LIBRARY
- RAY ELLISON OPPOSITE MAPLE VALLEY
- HENDERSON PASS OPPOSITE CANYON LEDG
- S.W. 26TH & CASTROVILLE
- S.W. 26TH & CASTROVILLE
- HENDERSON PASS & CANYON LEDGE
- FREEMAN IN FRONT OF 732
- FREEMAN OPPOSITE 732
- GOLIAD & CLARK
- GOLIAD & BILL MILLER LANE (OFFER)
- SOUTHCROSS IN FRONT OF 3875
- JONES-MALTSBERGER & OBLATE
- GUADALUPE & BRAZOS
- BRAZOS & GUADALUPE
- BRAZOS & GUADALUPE
- GUADALUPE & BRAZOS
- W Military & Buckhorn
- CASTROVILLE & 26TH
- CASTROVILLE IN FRONT OF 426
- CASTROVILLE OPPOSITE 416
- Castroville between Inca & Cupples
- Southcross Ranch Rd. & Firestar Trl.
- CASTROVILLE IN FRONT OF LAS PALMAS
- FIRESTAR TRL. & SOUTHCROSS RANCH RD.
- AUSTIN HWY. FRONT N.HILL SH.CTR.
- AUSTIN HWY. OPP. N HILL SHP. CTR.
- OLD SKY HARBOR & CLIPPER
- CASTROVILLE & CUPPLES (SW 26TH)
- ROOSEVELT OPPOSITE TRAVELERS WORLD
- ROOSEVELT IN FRONT OF 2617
- E. SOUTHCROSS & CLUB VIEW
- E. SOUTHCROSS & CLUB VIEW
- HUEBNER & HUEBNER OAKS
- Old Sky Harbor opposite Harbor View
- HENDERSON PASS AT ENT TO COSTA DEL SOL APTS.
- HENDERSON PASS OPP. COSTA DEL SOL A
- MARBACH & WRANGLER
- MARBACH OPPOSITE WRANGLER
- S.W. MILITARY DR. & ROYALGATE
- SW MLTRY BTWN RYLGATE & MERRY OAKS
- PATRICIA OPPOSITE PARLIAMENT
- WURZBACH & WHISPER SOUND
- WURZBACH OPPOSITE WHISPER SOUND
- PATRICIA & PARLIAMENT
- S.W. MILITARY DR. & RUSTLEAF
- BRAZOS & VERA CRUZ
- BRAZOS & VERA CRUZ
- ROOSEVELT & E. SOUTHCROSS
- ROOSEVELT & E. SOUTHCROSS
- PATRICIA AT SIDE ENTR OF JIFFY LUBE
- HUEBNER & IH-10 W
- IH-10 Frontage Rd in front of 12055
- PATRICIA IN FRONT OF 1030
- NACOGDOCHES & NACO-PERRIN
- Cesar Chavez Between Labor & IH-37
- IH-37 & CESAR CHAVEZ
- STADIUM DR IN FRONT OF SAWS
- WILSON & KINGS HWY.
- and 5850 more (see the full list on the map or in the GeoJSON)
Over time
Overall score across the last 4 checks — unchanged since 2026-08-22.
Show the numbers
| Check | Score | Change |
|---|---|---|
| 2026-08-06 | 35.9 | first check |
| 2026-08-07 | 35.5 | down 0.4 |
| 2026-08-22 | 48.7 | up 13.2 |
| 2026-08-23 | 48.7 | 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-08-22.
Same feed file as 2026-08-22; the published zip did not change.
Subscribe to this feed’s changes (Atom) to hear about grade drops and export changes in a reader, with no sign-up.
What changed over time
On 2026-08-06 this feed started at grade F. On 2026-08-22 feed renewed to a current calendar. On 2026-08-22 the check no longer reported: this feed's service calendar runs out within the next 30 days; feed_info.txt lists no contact email and no contact URL; service data runs out in 16 day(s); the feed contains no fare information; some trips serve fewer than two stops. As of 2026-08-23 it holds grade F.
A plain-language history of this feed, newest first.
- 2026-08-22 Feed renewed to a current calendar.
Everything we checked
17 findings, ordered by severity.
Show every finding
- Warning1414299 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 · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning29254 instances
29254 of 29254 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)
- Warning6100 instances
6100 of 6100 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)
- Warning5593 instances
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 · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning132 instances
Some scheduled trips move faster between stops than a bus can.
Usually a typo'd stop time; riders get arrival times no bus can meet.
Fix: Check the flagged stop times for transposed minutes. (A few minutes per flagged trip.)
Finding code: fast_travel_between_consecutive_stops · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning53 instances
Some stops exist in the feed but no trip ever stops at them.
Riders may walk to a stop where no bus is scheduled to arrive.
Fix: Remove retired stops from the export, or add them back to the trips that should serve them. (A review pass in your scheduling software.)
Finding code: stop_without_stop_time · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning36 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)
- Warning7 instances
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.)
Finding code: stop_too_far_from_shape · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning4 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.)
Finding code: missing_recommended_field · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning3 instances
Same name and description for stop (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'same_name_and_description_for_stop' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Finding code: same_name_and_description_for_stop · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning2 instances
Two or more routes share the same name.
Riders can't tell the routes apart in apps.
Fix: Give each route a distinct short or long name. (One field per route.)
Finding code: duplicate_route_name · 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.)
Finding code: expired_calendar · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning1 instance
A file GTFS asks for (usually feed_info.txt) is missing.
feed_info.txt tells apps who publishes the feed and when it expires; without it nobody is warned before data goes stale.
Fix: Add feed_info.txt with publisher name, URL, language, and feed_start_date/feed_end_date. (One small file, set once in export settings.)
Finding code: missing_recommended_file · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning1 instance
feed_info.txt is missing its start/end dates (the file itself is absent)
Apps and this scorecard can't warn anyone before the feed goes stale without stated validity dates.
Fix: Add feed_info.txt with feed_start_date and feed_end_date to your export. (Two fields, set once in export settings.)
Finding code: scorecard_missing_feed_info_dates · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Info5587 instances
About 5587 stop names are written in ALL CAPS.
Mixed-case names are easier to read in apps and are read more naturally by screen readers.
Fix: Rename stops to mixed case where the language has letter case (for example, 'Central Station'). (Often a bulk fix in your scheduling software.)
Finding code: scorecard_stop_names_all_caps · Read the fix guide · See GTFS Best Practices (opens GTFS Best Practices on an external site)
- Info278 instances
Some trip headsigns name a stop along the way, not the final destination.
The sign should tell riders where the bus ends up, so a midpoint name can send them the wrong way.
Fix: Set trip_headsign to the trip's last stop or its overall destination. (Usually a bulk edit in your scheduling software.)
Finding code: trip_headsign_matches_intermediate_stop · 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).
Trip-planning apps and regional data coordinators 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.)
Finding code: scorecard_no_feed_contact · 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
- Service data covers the next 140 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) Equal
- This feed's agency_id also equals its NTD ID (60011). Equality is allowed but not required; keep the value stable and retain the P-50 crosswalk.
- shapes.txt covers your trips Ready
- All 29254 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 140 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.
Can riders use it?
Checks beyond structural validation: places where the feed is valid but a rider still could not travel.
- 53 of 6100 boardable stops are never served by any trip. Riders see these stops in apps and on the map but can never catch anything there, which erodes trust in the data. Remove stops no route serves, or add the trips that should call at them.
These do not change the grade. They catch trips with no rideable leg and stops no trip serves, the kind of gap a trip planner trips over.
Clears the Google and Apple Maps four-week coverage bar. This feed has 140 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 35 / 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 39 / 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.
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/via-metropolitan-transit-via-2348/2026-08-23.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-23. 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.