GTFS Scorecard

← Back to the full scorecard

Call-prep brief · checked 2026-09-13

Capital Metro

Grade C · 79.2 / 100

Up 0.2 points since 2026-09-12 (C to C).

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 0.5

Top three things to fix

  1. Check the service alerts endpoint with your AVL vendor; it should return a fresh GTFS-Realtime protobuf on every request.

    The service alerts realtime feed failed during sampling. When this feed is down, riders see scheduled times presented as if they were live.

    Effort: Usually a vendor support ticket.

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

    2348 of 2348 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. Check the flagged stops' shape_dist_traveled against the route shape, and re-generate it on export if they disagree.

    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 path or point riders to the wrong boarding location.

    Effort: Usually an export-tool fix, not hand editing.

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
The service alerts realtime feed failed during sampling.
Next action
Check the service alerts endpoint with your AVL vendor; it should return a fresh GTFS-Realtime protobuf on every request.
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: 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 118 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 NTD ID (optional): Different (allowed). Your feed's agency_id is CM; your National Transit Database ID is 60048. A feed that serves several agencies (a shared regional feed) can legitimately carry more than one agency_id. The values do not need to equal the five-digit NTD ID, so this difference is allowed and carries no score. Confirm that P-50 crosswalks agency_id CM to NTD ID 60048, and keep the feed value stable. Do not change it solely to make the two values equal.

Key facts

Feed URL
https://data.texas.gov/download/r4v4-vz24/application/zip
Last checked
2026-09-13
Service window
118 days of service data remain. Last service date 2027-01-09.
Feed version
260826_0956
Location
Texas

Part of the Texas portfolio: see where this agency sits among the other feeds in that group 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.