← All agencies

Feed status · checked 2026-08-01

VIA Metropolitan Transit (VIA)

Based on the feed this agency publishes

Service mode Bus

39.8 / 100

down 0.4 since 2026-07-31

Catalogued in Texas.

Expires in 22 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.

Checked for changes 3 hours ago; last changed 2 days ago.

Measured 3 of 4 score categories from the agency's own feed.

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

Fix 01

Re-export with a validity window that reaches at least 60 days out.Likely your export tool

Service data runs out in 22 day(s). When the calendar runs out, trip planners stop showing this agency. Fixing it now is calmer than after riders notice.

⏱ One export setting.worth about +58 points in its category

Fix 02

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

6097 of 6097 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 03

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

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

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
Service data runs out in 22 day(s).
Next action
Re-export with a validity window that reaches at least 60 days out.
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. Re-export with a validity window that reaches at least 60 days out. · 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.

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

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

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

Send the agency a note

Supporting this agency? Copy this and email it to them. It names what lapsed, why it matters to riders, and the one setting to change.

Score by category

Correctness53.0 / 100

The MobilityData validator flagged 9 kinds of issue across 5844 instances (0 error, 5769 warning, 75 informational).

Freshness36.7 / 100

Service data runs out in 22 day(s). Publish an updated feed soon or riders will lose trip planning.

Rider experience23.8 / 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.

Accessibility0 / 100

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 (204, 214, 222, 225, 230, 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.

  • 4925 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set ("BLANCO & DRESDEN", "FRESNO & I-10 W ACCESS RD.", "MARTIN & N. FRIO", 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 6097 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.

  • 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)
  • 62 (gray)
  • 620 (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)
  • 9 (teal)
  • 90 (teal)
  • 92 (gray)
  • 93 (red)
  • 95 (red)
  • 96 (red)
  • 97 (teal)
Routes in VIA Metropolitan Transit (VIA)'s feed
RouteTypeLine color
10 Naco / Broadway SkipBusred
100 Primo Fredericksburg RoadBusred
102 Primo MilitaryBusred
103 Primo ZarzamoraBusred
14 Perrin Beitel SkipBusred
17 IH-35 ExpressBusteal
2 Blanco FrequentBusred
20 New Braunfels FrequentBusred
204 San Pedro / McCullough 4-5 LineupBusgray
21 Kirby / Ventura FrequentBusred
214 Austin Hwy / Randolph 14-17 LineupBusgray
22 HaysBusteal
222 Hays / E Houston 22-24 LineupBusgray
225 E Commerce / MLK 25-26 LineupBusgray
230 Rigsby / Porter 30-28 LineupBusgray
232 Steves / S St Marys 32-34 LineupBusgray
24 East Houston FrequentBusred
242 Roosevelt / S Presa 42-36 LineupBusgray
25 East Commerce FrequentBusred
251 Nogalitos / Kirk 51-62 LineupBusgray
26 Martin Luther KingBusteal
268 Guadalupe / Ceralvo 68-66 LineupBusgray
275 Commerce / Laredo 75-67 LineupBusgray
276 Commerce / Kel-Lac TC 76-64 LineupBusgray
28 Porter FrequentBusred
282 Culebra 82 LineupBusgray
288 Bandera / Evers 88 LineupBusgray
289 Poplar / Woodlawn 89-90 LineupBusgray
3 San Pedro SkipBusred
30 RigsbyBusteal
32 StevesBusgray
34 South St Marys FrequentBusred
36 South PresaBusgray
4 San Pedro FrequentBusred
42 RooseveltBusgray
43 South FloresBusteal
44 PleasantonBusteal
46 CommercialBusteal
5 McCulloughBusteal
501 UTSA / Leon ValleyBusgray
502 Thousand Oaks / ConverseBusteal
503 Huebner CrosstownBusgray
505 BasseBusteal
509 HildebrandBusgray
51 NogalitosBusteal
515 SouthcrossBusteal
522 BabcockBusgray
524 General McMullen FrequentBusred
534 Wurzbach FrequentBusred
552 Loop 410 / W. W. White SkipBusred
602 Medical Center / BlossomBusteal
603 Medical Center / UTSABusteal
604 Medical Center / University HeightsBusgray
607 Medical Center / IngramBusgray
609 Medical Center / Ingram / Kel-LacBusteal
610 Ingram / Northwest CrossingBusgray
611 Kel-Lac / Valley-Hi / Hidden CoveBusteal
612 Kel-Lac / Westlakes / IngramBusteal
615 Kel-Lac / Heritage ParkBusteal
616 Sky Harbor / Kel-LacBusteal
618 Ingram / Westover Hills / Kel-LacBusteal
619 Kel-Lac / Port SABusteal
62 KirkBusgray
620 Northwest Vista College / IngramBusteal
632 Randolph / VenturaBusteal
64 US 90 Alamo Ranch ExpressBusteal
647 North Star / Harry WurzbachBusgray
648 North Star / Stone OakBusgray
649 North Star / N Blanco / Stone OakBusteal
651 Deco District / Castle HillsBusgray
66 CeralvoBusgray
67 LaredoBusgray
68 Guadalupe FrequentBusred
7 US 281 Stone Oak ExpressBusteal
75 West Commerce FrequentBusred
76 West Commerce SkipBusred
77 Martin / Las Palmas FrequentBusred
79 Ruiz / Culebra ParkBusteal
8 North St MarysBusteal
82 Culebra FrequentBusred
88 Bandera FrequentBusred
89 PoplarBusgray
9 BroadwayBusteal
90 WoodlawnBusteal
92 Brooks / Medical Center ExpressBusgray
93 Roadrunner ExpressBusred
95 Fredericksburg Road FrequentBusred
96 Vance Jackson FrequentBusred
97 West AvenueBusteal
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 5847 more (see the full list on the map or in the GeoJSON)

Over time

Overall score across the last 4 checks — down 0.4 since 2026-07-31.

2026-07-25: 39.22026-07-30: 40.62026-07-31: 40.22026-08-01: 39.8
Show the numbers
Overall score by check, with the change from the previous check
CheckScoreChange
2026-07-2539.2 first check
2026-07-3040.6 up 1.4
2026-07-3140.2 down 0.4
2026-08-0139.8 down 0.4

What changed since your last check

  • Correctness no change
  • Freshness down 1.6
  • Rider experience no change

Everything we checked

15 findings, ordered by severity.

Show every finding
  • Warning14589 instances

    14589 of 14589 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)

  • Warning6097 instances

    6097 of 6097 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)

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

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

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

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

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

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

  • Warning1 instance

    This feed's service calendar runs out within the next 30 days.

    If a new feed isn't published before it ends, trip planners will drop your agency and riders will see no service.

    Fix: Schedule a feed re-export now so the new calendar is live well before the current one ends. (Usually a re-export from your scheduling software.)

    Finding code: feed_expiration_date30_days · Read the fix guide · 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 · See MobilityData GTFS Validator rules (opens the validator rules on an external site)

  • Warning1 instance

    Service data runs out in 22 day(s).

    When the calendar runs out, trip planners stop showing this agency. Fixing it now is calmer than after riders notice.

    Fix: Re-export with a validity window that reaches at least 60 days out. (One export setting.)

    Finding code: scorecard_feed_expiring_soon · Read the fix guide · See GTFS Best Practices (opens GTFS Best Practices 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)

  • Info5588 instances

    About 5588 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)

  • Info75 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 Needs attention

This feed is close to NTD-ready. Service data runs out in 22 days; renew before you certify.

Published Ready
Published at a public URL.
Valid Ready
Passes validation with no errors.
Current Needs attention
Service data runs out in 22 days; renew before you certify.
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 14589 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. Service data runs out in 22 days; renew to qualify. 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 Not yet
Service data runs out in 22 days; renew to qualify.
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.

  • 78 of 6097 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.

At risk for the Google and Apple Maps four-week coverage bar. This feed has 21 days of service left. Maps needs at least four weeks (28 days) of upcoming service, so your agency will fall out of trip planners soon. Re-export with a longer calendar.

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 53 / 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 37 / 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 24 / 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.

VIA Metropolitan Transit (VIA) GTFS data quality grade: F

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