Redding Area Bus Authority

What changed since the last check

• Correctness no change
• Freshness no change
• Rider experience no change

Top three things to fix

1. Re-generate shape_dist_traveled on export so stop and shape distances use the same units.

   On some trips the stop distances run a little past the end of the route line. The stop and shape distance values don't quite line up, so any math that uses them can drift.

   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.

2. Remove past service periods the next time you export the feed.

   Some service calendars in the feed have already ended. Expired calendars are dead weight and can hide real schedule problems from your staff and vendors.

   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: One setting in most export tools.

3. Turn on shape cleanup in your export tool, or drop the repeated points from shapes.txt.

   Some route lines list the same point twice in a row. Repeated points don't hurt riders, but they can skew distance math and hint at a shaky export.

   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 one export setting.

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 85 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): 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

The published guideline in California is California Transit Data Guidelines. Caltrans' published quality guidelines and compliance checklist; this rubric is anchored to them.

Key facts

Feed URL

https://gtfs.remix.com/redding_area_bus_authority.zip

Last checked

2026-10-07

Service window

85 days of service data remain. Last service date 2026-12-31.

Feed version

Updated: Oct 5, 2026, 3:44 AM

Location

California