Via Mobility

What changed since the last check

• Correctness down 4.0
• Freshness down 1.7
• Rider experience no change
• Realtime quality down 23.1

No longer reported since the last check (1 finding):

• Some live predictions disagree with the schedule by more than 30 minutes. (scorecard_rt_predictions_implausible)

This compares feed state. It does not identify who made a change or why.

Top three things to fix

1. Re-export with a validity window that reaches at least 60 days out.

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

   Effort: One export setting.

2. Review the rule documentation for 'empty_file' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.

   Empty file (flagged by the MobilityData validator). See the linked rule for what this affects.

   Effort: Varies.

3. Set wheelchair_boarding to 1 (accessible) or 2 (not accessible) for every stop. A field survey can start with the busiest stops.

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

   Effort: A column in stops.txt; your scheduling software likely has it.

Ready to send to the agency

Hi Via Mobility team, Service data runs out in 29 day(s). When the calendar runs out, trip planners stop showing this agency. Fixing it now is calmer than after riders notice. The fix is usually one export setting: Re-export with a validity window that reaches at least 60 days out. Your feed is produced by Passio, so the quickest path is usually forwarding this to your Passio contact. This came from your GTFS data quality scorecard, which checks the feed you publish and lists the fixes in plain language: https://gtfsscorecard.org/agency/via-mobility-2395/

Copy this note from the full scorecard.

NTD GTFS readiness: Needs attention

This feed is close to NTD-ready. 1 validator error to resolve. Service data runs out in 29 days; renew before you certify.

Published Ready

Published at a public URL.

Valid Needs attention

1 validator error to resolve.

Current Needs attention

Service data runs out in 29 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 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.

The bar this score answers to

A local transit-data support resource is CDOT Digital Transit Mobility. Colorado's program coordinating GTFS data across transit providers.

Key facts

Feed URL

https://passio3.com/viaboulder/passioTransit/gtfs/google_transit.zip

Last checked

2026-08-24

Service window

29 days of service data remain. Last service date 2027-12-31.

Feed version

20250228

Location

Colorado