GTFS Scorecard

← Back to the full scorecard

Call-prep brief · checked 2026-08-02

Via Mobility

Grade D · 66.7 / 100

Up 0.3 points since 2026-08-01 (D to D).

For this call: lead with the grade and the three fixes below, then confirm the feed is current and the NTD details line up. Each fix is framed as a next step, not a failure.

What changed since the last check

  • Correctness no change
  • Freshness no change
  • Rider experience no change
  • Realtime quality up 1.7

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

  • 5 of 35 sampled vehicle positions were far from their assigned route (worst: 3377 m). (scorecard_rt_vehicles_off_route)

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

Top three things to fix

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

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

  3. Set wheelchair_accessible on every trip. If every vehicle is accessible, this may be one default; otherwise use the value for each trip.

    397 of 397 trips don't say whether the vehicle is wheelchair accessible. Even with accessible stops, riders need to know the bus itself can take them.

    Effort: A default or per-trip field in your export.

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
Empty file (flagged by the MobilityData validator).
Next action
Review the rule documentation for 'empty_file' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.
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

NTD GTFS readiness: Needs attention

This feed is close to NTD-ready. 1 validator error to resolve. Service data runs out in 30 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 30 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-02
Service window
30 days of service data remain. Last service date 2027-12-31.
Feed version
20250228
Location
Colorado

Part of the Colorado portfolio: see where this agency sits among the state's feeds before the call.

A data-quality and completeness read to support an agency conversation. Not an official compliance determination. Rubric v1.3, validator 8.0.1.