← Back to the full scorecard

Call-prep brief · checked 2026-11-09

CATABUS

Grade F · 29.3 / 100 · partial: freshness not measured

The scoring methodology changed since the prior check; the trend restarts here without an improvement or regression claim.

Scored from a Mobility Database mirror copy downloaded on 2026-10-02, because the feed URL on file could not be downloaded. Service dates in that copy run 2021-05-03 to 2021-08-21. It may not match the feed the agency publishes today.

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

The scoring methodology changed since the prior check. Category deltas restart with this scorecard.

Top three things to fix

  1. Check that https://transitfeeds.com/p/catabus/536/latest/download still serves your current feed. If the feed moved, publish the new address.

    The feed URL on file, https://transitfeeds.com/p/catabus/536/latest/download, could not be downloaded: the server answered with an error instead of the file. Trip planners download the feed from that address too. The grade here was measured on an older Mobility Database copy whose service ended 2021-08-21, so freshness is not graded until the current feed can be downloaded.

    This one is about the feed as a whole, so there is no share of it to count.

    Effort: Usually a server or hosting setting, not a change to the feed itself.

  2. Re-generate shape distances in your export; flag to your vendor if it persists.

    Some trips have stop times whose distances along the route go backwards. Apps can show buses jumping backwards or mis-order stops.

    This is a validator notice, and the validator decides what each instance covers, so no share of the network can be read from it here.

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

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

    Invalid phone number (flagged by the MobilityData validator). See the linked rule for what this affects.

    This is a validator notice, and the validator decides what each instance covers, so no share of the network can be read from it here.

    Effort: Varies.

Riders and need behind these fixes

  • This feed carries no National Transit Database ID, so annual rider-trips are not known for it.
  • Pennsylvania as a whole measures lower on transit need. That is a statewide reading, not one for this feed's service area. Source: US Census ACS 5-year 2022, statewide overlay, as of 2026-11-02.

These describe this feed only. They do not rank agencies, and they do not change the grade or the order of the fixes.

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 feed URL on file, https://transitfeeds.com/p/catabus/536/latest/download, could not be downloaded: the server answered with an error instead of the file.
Next action
Check that https://transitfeeds.com/p/catabus/536/latest/download still serves your current feed. If the feed moved, publish the new address.
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: Not ready

Resolve this before you certify on the D-10. 2 validator errors to resolve. No service end date could be read, so currency is unknown.

Published Ready
Published at a public URL.
Valid Needs attention
2 validator errors to resolve.
Current Not ready
No service end date could be read, so currency is unknown.
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.

Key facts

Feed URL
https://transitfeeds.com/p/catabus/536/latest/download
Last checked
2026-11-09
Service window
Expiry date not stated in the feed.
Location
Pennsylvania

Part of the Pennsylvania 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.4, validator 8.0.1.