Feed status · checked 2026-08-01
Redding Area Bus Authority
Based on the feed this agency publishes
Service mode Bus
unchanged since 2026-07-31
Catalogued in California.
A data-quality and completeness lens to help an agency improve its GTFS feed. Not an official compliance determination from any transit program. New to this? How to read your scorecard. Interactive view of this scorecard. Rubric v1.3, validator 8.0.1.
Checked for changes 16 hours ago; last changed 36 days ago.
Measured 3 of 4 score categories from the agency's own feed.
How we measured this
Confidence in this measurement: medium.
- Realtime quality was not measured this run. It does not count against the grade.
- The feed was downloaded from the agency's own URL.
Confidence describes how much the pipeline could measure this run, not the feed itself. It never changes the grade.
Top things to fix
Re-generate shape_dist_traveled on export so stop and shape distances use the same units.Likely your export tool
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.
⏱ Usually an export-tool fix, not hand editing.worth about +8 points in its category
Turn on shape cleanup in your export tool, or drop the repeated points from shapes.txt.Likely your export tool
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.
⏱ Usually one export setting.worth about +4 points in its category
Check the flagged stops' shape_dist_traveled against the route shape, and re-generate it on export if they disagree.Likely your export tool
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 streets or point riders to the wrong corner.
⏱ Usually an export-tool fix, not hand editing.worth about +4 points in its category
This feed is exported from Remix. The change happens in your Remix workspace; once your planners update the data there, the published export picks it up.
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
- On some trips the stop distances run a little past the end of the route line.
- Next action
- Re-generate shape_dist_traveled on export so stop and shape distances use the same units.
- 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
- Feed evidence
- Some route lines list the same point twice in a row.
- Next action
- Turn on shape cleanup in your export tool, or drop the repeated points from shapes.txt.
- 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
- Feed evidence
- Some stops sit far from the route line, going by the feed's own distance values.
- Next action
- Check the flagged stops' shape_dist_traveled against the route shape, and re-generate it on export if they disagree.
- 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
How to make and check these changes
Check the result on the published feed. Read the guide, make the change in your tool, and use the next comparable run to see whether the finding is still reported. Only an action or ticket record can attribute who made the change.
Re-generate shape_dist_traveled on export so stop and shape distances use the same units. · Read the fix guide
Make the change. This feed is exported from Remix. The change happens in your Remix workspace; once your planners update the data there, the published export picks it up.
Check the result. The next scorecard run checks this finding again. If a comparable check no longer reports it, the feed's clearance log records that result. This confirms feed state, not who made the change. Self-check a feed before you publish.
Turn on shape cleanup in your export tool, or drop the repeated points from shapes.txt. · Read the fix guide
Make the change. This feed is exported from Remix. The change happens in your Remix workspace; once your planners update the data there, the published export picks it up.
Check the result. The next scorecard run checks this finding again. If a comparable check no longer reports it, the feed's clearance log records that result. This confirms feed state, not who made the change. Self-check a feed before you publish.
Check the flagged stops' shape_dist_traveled against the route shape, and re-generate it on export if they disagree. · Read the fix guide
Make the change. This feed is exported from Remix. The change happens in your Remix workspace; once your planners update the data there, the published export picks it up.
Check the result. The next scorecard run checks this finding again. If a comparable check no longer reports it, the feed's clearance log records that result. This confirms feed state, not who made the change. Self-check a feed before you publish.
Rider view: what this feed publishes
A quick read of rider-facing information in this feed.
- Schedule visibility
- The feed's last published service date is in 152 days.
- Published accessibility data
- Accessibility information is stated for 100% of stops and 100% of trips. This measures published data, not whether stops or vehicles are physically usable.
- Fare information
- Fare information is published using GTFS Fares v1.
- Realtime information
- Realtime-feed availability and live-arrival coverage are not known from this scorecard.
Important: This does not rate service reliability. Riders should confirm current service alerts, fares, and accessibility accommodations with the transit operator before traveling.
Send your vendor a fix request
This feed is exported from Remix. If your planners work in Remix, the change happens in your own workspace; otherwise forward this to whoever maintains your Remix data. Each fix names the validator notice and a guide link.
Score by category
The MobilityData validator flagged 7 kinds of issue across 933 instances (0 error, 121 warning, 812 informational).
Service data covers the next 152 days.
100% of stops state wheelchair accessibility (100% marked accessible, 0% marked not accessible). This measures what the feed publishes, not whether a stop is physically usable. Fare data is published.
100% of stops state accessibility (100% marked accessible). Reflects what the feed states, not verified physical usability.
3 accessibility depth signals
7 route badge(s) pair a color and text color below the WCAG 4.5:1 contrast bar (4, 7, 299X, 9, 11, and more).
Consider: Adjust route_color or route_text_color so each pair clears 4.5:1. Often switching the text between black and white is enough.
297 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set ("Shasta Dam Blvd at Kennett St (NS)", "Twin View Blvd at Midway Dr", "Hilltop Dr at Presidio St", and more).
Consider: Add tts_stop_name with the spoken form, e.g. 'Main Street and Second Avenue', for the affected stops.
This feed models stations or entrances but has no pathways.txt and levels.txt.
Consider: Add pathways.txt connecting entrances, platforms, and elevators, and levels.txt for each floor, so the step-free route is described.
Opportunities to strengthen the data, not deductions from the sub-score above. States what the second accessibility lens can check from the feed, not verified physical usability.
Fares are applied to trips.
Not scored yet. Nothing here counts against the grade.
Routes and stops
Each route is drawn once, using the longest shape its trips follow; stops are the dots.
This feed has 320 stops.
The route and stop data is ready below. Load the map only when you want the geographic view. It uses additional data.
Basemap: OpenFreeMap, © OpenStreetMap contributors. Routes and stops: this agency's GTFS feed.
- 15 (red)
- 1 (teal)
- 3 (teal)
- 4 (gray)
- 7 (teal)
- 11 (green)
- 14 (purple)
- 299X (teal)
- 99X (brown)
- 19 (blue)
- 44X (pink)
- 9 (red)
| Route | Type | Line color |
|---|---|---|
| 15 Route 15 | Bus | red |
| 1 Route 1 | Bus | teal |
| 3 Route 3 | Bus | teal |
| 4 Route 4 | Bus | gray |
| 7 Route 7 | Bus | teal |
| 11 Route 11 | Bus | green |
| 14 Route 14 | Bus | purple |
| 299X Route 299X | Bus | teal |
| 99X Route 99X / Amtrak Thruway | Bus | brown |
| 19 Route 19 | Bus | blue |
| 44X Route 44x | Bus | pink |
| 9 Route 9 | Bus | red |
List every stop
- Northpoint Dr at Lake Blvd
- Northpoint Dr at Redwood Blvd
- Redwood Blvd at Marijean Way
- Redwood Blvd at Butternut Trail
- Redwood Blvd at Caterpillar Rd
- Caterpillar Rd at Redwood Blvd
- Caterpillar Rd at Prestige Way
- Caterpillar Rd at Grand Ave
- Twin View Blvd at Caterpillar Rd
- Twin View Blvd at Midway Dr
- Twin View Blvd at Valleyridge Dr
- Northpoint Dr at Redwood Blvd
- Northpoint Dr at Lake Blvd
- Lake Blvd at Clay St
- Shasta Dam Blvd at Hardenbrook Ave
- Shasta Dam Blvd at Median Ave
- Shasta Dam Blvd at Grand Coulee Blvd
- Cascade Blvd at Shasta Dam Blvd
- Cascade Blvd at Morningstar Way
- Cascade Blvd at Cottage Ave
- Cascade Blvd at Mulberry St
- Cascade Blvd at Autumn Harvest Way
- Cascade Blvd at Riddle Rd
- Cascade Blvd at Oasis Rd
- Oasis Rd at Randolph Rd
- Oasis Rd at Beltline Rd
- 3711 Oasis Rd
- Lake Blvd at Keswick Dam Rd
- Lake Blvd at Tamarack Dr
- Lake Blvd at Panorama Dr
- Lake Blvd at St. Marks St
- Lake Blvd at Clay St
- Lake Blvd at Santa Rosa Way
- Lake Blvd at St. Nicholas Ave
- Lake Blvd at Northpoint Dr (FS)
- Oasis Rd at Lake Blvd (FS)
- Oasis Rd at Redding STEM (FS)
- Oasis Rd at Beltline Rd (NS)
- Oasis Rd at Randolph Rd (FS)
- Shasta Dam Blvd at Kennett St (NS)
- Shasta Dam Blvd at 5001 Oregon
- Shasta Dam Blvd and Grand River Ave (NS)
- Shasta Dam Blvd at Farmers Marketplace (MB)
- Oasis Rd at Cascade Blvd (NS)
- Browning St at Mission De Oro Dr
- Hilltop Dr at Palisades Ave
- Hilltop Dr at Sandpointe Dr
- Hilltop Dr at St. Thomas Pkwy
- Hilltop Dr at Mercedes Ln
- 95 Hilltop Dr
- Hilltop Dr at Lake Blvd
- Quartz Hill Rd at Delta St
- Quartz Hill Rd at Benton Dr
- Benton Dr at Quartz Hill Rd
- Cypress Ave at Civic Center Dr
- Cypress Ave at Beverly Dr
- Hilltop Dr at Commerce St
- Hilltop Dr at Mistletoe Ln
- Hilltop Dr at Presidio St
- Hilltop Dr at Rockaway Dr
- Browning St at Mission De Oro Dr
- Benton Dr at Quartz Hill Rd
- Benton Dr w/o Delta St
- Benton Dr at Delta St
- Benton Dr at Loma St
- 100 Hilltop Dr
- Hilltop Dr at Mercedes Ln
- Hilltop Dr at Sandpointe Dr
- Hilltop Dr at Palisades Ave
- Hilltop Dr at Browning St
- Hilltop Dr at Rockaway Dr
- Hilltop Dr at E. Palisades Ave
- Hilltop Dr at Presidio St
- Hilltop Dr at Mistletoe Ln
- Hilltop Dr at Industrial St
- Hilltop Dr at Commerce St
- Cypress Ave at Rosemary Ave
- Cypress Ave at Athens Ave
- Cypress Ave at Civic Center Dr
- Cypress Ave at Pine St
- Canby @ Browning (SB)
- Canby @ The Home Depot (NB)
- VA Clinic at Knighton Rd
- EB Knighton Rd at Pacheco Rd
- Redding Regional Airport
- Fast Track at Churn Creek Rd
- Shasta View Dr at Atrium Wy
- Shasta View Dr at Atrium Wy
- Shasta View Dr at Old Alturas Rd
- Shasta View Dr at Old Alturas Rd
- Shasta View Dr at Voltaire Wy
- Shasta View Dr at Viking Wy
- Shasta View Dr at Palacio Dr
- Shasta View Dr at Palacio Dr
- Turtle Bay Exploration Park (Sheraton)
- Oak Bottom Beach
- Lincoln St at S. Market St
- S. Market St at California St
- S. Market St at Grange St
- S. Market St at Ellis St
- W Placer St at San Francisco St (across from Holiday Market)
- Buenaventura Blvd at Eureka Way
- Court St at 11th St
- Court St at Shasta St
- Court St at Shasta St
- Court St at 11th St
- Buenaventura Blvd at Eureka Way
- E Placer St at San Francisco St (across from Holiday Market)
- SR 299/Elm
- SR 299/CAL Fire Diddy Wells Station #74
- SR 299 @ Hill Country Health and Wellness Center
- SR 89 @ SR 299 Park and Ride Lot
- Downtown Passenger Terminal
- Downtown Passenger Terminal Gate 1
- Downtown Passenger Terminal Gate 2
- Downtown Passenger Terminal Gate 3
- Downtown Passenger Terminal Gate 4
- Downtown Passenger Terminal Gate 5
- Downtown Passenger Terminal Gate 6
- Downtown Passenger Terminal Gate 9
- Downtown Passenger Terminal Gate 11
- Downtown Passenger Terminal Gate 12
- Downtown Passenger Terminal Gate 44x
- Downtown Passenger Terminal Gate 299x
- Silver St at Briggs St (Fairgrounds)
- Lake Blvd at St. Marks St
- Lake Blvd at Keswick Dam Rd
- Shasta View Dr at Simpson Blvd
- Shasta Dam Blvd at Locust Ave
- Westside Rd at El Reno Ln
- Westside Rd at Kenyon Dr
- Westside Rd at Branstetter Ln
- Westside Rd at Concord Ln
- Westside Rd at Happy Valley Rd (NS)
- SR 273 at Canyon Rd
- Westside Rd at Clear Creek Rd
- SR 273 at Westwood Ave
- Cedars Rd at Concord Ln
- Cedars Rd at Branstetter Ln
- Cedars Rd at Kenyon Dr
- Cedars Rd at Riviera Dr
- El Reno Ln at Westside Rd
- Westside Rd at Canyon Creek Rd
- Breslauer Way at Eastside Rd
- Breslauer Way at Veterans Ln
- Radio Ln at Cerro Ln
- E. Bonnyview Rd at N. Bonnyview Rd (Bonnyview Market)
- E. Bonnyview Rd at Nicolet Ln
- E. Bonnyview Rd at Willowbrae Ave
- S. Bonnyview Rd at E. Bonnyview Rd
- Eastside Rd at S. Bonnyview Rd
- Eastside Rd at North Dr
- Eastside Rd at Star Dr
- Eastside Rd at Waverly Ave
- Eastside Rd at Girvan Rd
- SR 273 at Canyon Rd
- Eastside Rd at Wyndham Ln (FS)
- S. Bonnyview Rd at Eastside Rd (FS)
- E. Bonnyview Rd at S. Bonnyview Rd (FS)
- E. Bonnyview Rd at Willowbrae Ave (FS)
- E. Bonnyview Rd at Nicolet Ln
- E. Bonnyview Rd at N. Bonnyview Rd (NS)
- Radio Ln at Cerro Ln (NS)
- Breslauer Way at Eastside Rd (NS)
- Eastside Rd at Wyndham Ln (NS)
- Chico Transit Center (Salem St at 2nd St)
- Canby Transfer Center
- Old Alturas Rd at Bradford Way
- Dana Dr at Bradford Way
- Dana Dr at Friendly Rd
- Churn Creek Rd at Presidio St
- Churn Creek Rd at Mistletoe Ln
- Churn Creek Rd at Wall St
- Churn Creek Rd at Cypress Ave
- Churn Creek Rd at Maraglia St
- Churn Creek Rd at Parsons Dr
- Churn Creek Rd at Hartnell Ave
- Churn Creek Rd at Shirley Ln
- Churn Creek Rd at Echo Rd
- Churn Creek Rd at Loma Vista Dr
- Bechelli Ln at Layton Rd
- Bechelli Ln at 3rd St
- Bechelli Ln at Wilshire Dr
- Bechelli Ln at 3rd St
- Bechelli Ln at Layton Rd
- Churn Creek Rd at Loma Vista Dr
- Churn Creek Rd at Echo Rd
- Churn Creek Rd at Shirley Ln
- Churn Creek Rd at Hartnell Ave
- Churn Creek Rd at Parsons Dr
- Churn Creek Rd at Cypress Ave
- Churn Creek Rd at Industrial St
- Churn Creek Rd at Mistletoe Ln
- Churn Creek Rd at Presidio St
- Dana Dr at Churn Creek Rd
- Dana Dr at Bradford Way
- Victor Ave at Dana Dr
- Old Alturas Rd at Bradford Way
- Old Alturas Rd at Friendly Rd
- Bechelli Ln at Joaquin Ave (FS)
- Bechelli Ln at across Costco Wholesale (FS)
- Bonnyview Rd at Bechelli Ln (FS)
- Churn Creek Rd at Hillmonte Dr (FS)
- Churn Creek Rd at Denton Wy (FS)
- Old Alturas Rd @ Churn Creek Rd (FS)
- Victor Ave at Dana Dr (NS)
- Churn Creek Rd at Hillmonte Dr (FS)
- Bechelli Ln at Costco Wholesale (FS)
- Bechelli Ln at Loma Vista Dr (FS)
- Deschutes Rd @ SR 44 Park and Ride Lot/Across from Holiday Market
- SR 44 @ Black Butte Park and Ride Lot
- Shingletown Park and Ride Lot
- SR 44 @ Black Butte Market
- Old 44 Dr @ Across Millville US Post Office
- Hartnell Ave at Cypress Ave
- Hartnell Ave at Shotwick Trail
- Hartnell Ave at Bechelli Ln
- Hartnell Ave at Bechelli Ln
- Hartnell Ave at Shotwick Trail
- Hartnell Ave at Parkview Ave
- Churn Creek Rd at Old Alturas Rd
- Churn Creek Rd at Browning St
- Churn Creek Rd at Whistling Dr
- Churn Creek Rd at Palacio Dr
- Churn Creek Rd at Golden Gate Trail
- Churn Creek Rd at Rose Ln
- College View Dr at Churn Creek Rd
- College View Dr at Tidmore Ln
- College View Dr at Shasta View Dr
- College View Dr at Mercy Oaks Dr
- College View Dr at Old Oregon Trail
- Shasta College
- Collyer Dr at Twin Tower Dr
- 1720 Collyer Dr
- 1520 Collyer Dr
- Collyer Dr at Ridgewood Rd
- Collyer Dr at Hawley Rd
- Churn Creek Rd at Golden Gate Trail
- Churn Creek Rd at Palacio Dr
- Canby Rd at Churn Creek Rd
- Canby Rd at Pilgrim House
- Trinity St at California St
- N. Market St at Quartz Hill Rd
- N. Market St at Benton Dr
- Lake Blvd at N. Market St
- Lake Blvd at Hilltop Dr
- Lake Blvd at Black Marble Way
- Lake Blvd at N. Boulder Dr
- N. Market St at Benton Dr
- N. Market St at Quartz Hill Rd
- and 70 more (see the full list on the map or in the GeoJSON)
Over time
Overall score across the last 4 checks — unchanged since 2026-07-31.
Show the numbers
| Check | Score | Change |
|---|---|---|
| 2026-07-25 | 91.9 | first check |
| 2026-07-30 | 91.9 | no change |
| 2026-07-31 | 91.9 | no change |
| 2026-08-01 | 91.9 | no change |
What changed since your last check
- Correctness no change
- Freshness no change
- Rider experience no change
What changed in this feed
Overall grade and score held steady since 2026-07-31.
Same feed file as 2026-07-31; the published zip did not change.
Subscribe to this feed’s changes (Atom) to hear about grade drops in a reader, with no sign-up.
Everything we checked
8 findings, ordered by severity.
Show every finding
- Warning118 instances
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.
Fix: Re-generate shape_dist_traveled on export so stop and shape distances use the same units. (Usually an export-tool fix, not hand editing.)
Finding code: trip_distance_exceeds_shape_distance_below_threshold · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning2 instances
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.
Fix: Turn on shape cleanup in your export tool, or drop the repeated points from shapes.txt. (Usually one export setting.)
Finding code: equal_shape_distance_same_coordinates · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning1 instance
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 streets or point riders to the wrong corner.
Fix: Check the flagged stops' shape_dist_traveled against the route shape, and re-generate it on export if they disagree. (Usually an export-tool fix, not hand editing.)
Finding code: stop_too_far_from_shape_using_user_distance · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning1 instance
This feed models stations or entrances but has no pathways.txt.
Trip planners can't guide riders through the station, and there is no step-free route information for wheelchair users.
Fix: Add pathways.txt connecting entrances, platforms, and any elevators, with a level for each. (Worth it for multi-level or large stations; flat stops don't need it.)
Finding code: scorecard_station_no_pathways · Read the fix guide · See GTFS Schedule reference (opens the GTFS Schedule reference on an external site)
- Info803 instances
Unsorted stop times (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'unsorted_stop_times' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Finding code: unsorted_stop_times · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Info5 instances
The feed has a stretch of two weeks or more with no service running.
A long gap can mean dates were left out of the calendar. Apps then show no trips on those days.
Fix: Check whether the gap is real, like a seasonal break; if not, add the missing dates to the calendar. (A review of your calendar dates.)
Finding code: big_gap_in_service · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Info2 instances
Some service dates fall outside the date window set in feed_info.txt.
feed_info.txt should span every day your service runs, so apps know when the data applies.
Fix: Widen feed_start_date and feed_end_date to cover all service dates, or fix the dates that fall outside. (Two fields in feed_info.txt, or one export setting.)
Finding code: service_window_outside_feed_period · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Info2 instances
Some files contain columns that are not part of the GTFS spec.
Harmless to riders, but apps ignore these columns and they can hide typos in real column names.
Fix: Check the flagged column names for misspellings of standard GTFS fields; remove them if they are vendor extras. (A quick look at the flagged files.)
Finding code: unknown_column · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
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 152 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 your 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.
- shapes.txt covers your trips Ready
- All 803 trips have a shape in shapes.txt.
In plain words: if you report to the federal transit database, you have to publish a working, up-to-date feed, provide a stable agency_id for each represented reporter, and confirm the feed and P-50 crosswalk each year. This box is a heads-up; your filings are the official check.
A readiness signal mapping this feed to the FTA National Transit Database GTFS requirement (Report Year 2023 onward: a public, valid, current feed, certified annually on the D-10). For RY2026, each represented reporter needs a stable agency_id, unique within the feed and crosswalked to its five-digit NTD ID on P-50; the values do not need to be equal. FTA also requires shapes.txt in the published GTFS: Full Reporters from Report Year 2025, and Reduced, Rural, and Tribal Reporters from Report Year 2026. Not an official determination; your certification is the official check.
Conformance mark Awarded
This feed earns the conformance mark: valid, current, and stating wheelchair access on nearly every stop and trip.
- Valid Met
- Passes validation with no errors.
- Current Met
- Service data covers the next 152 days.
- Accessible Met
- States wheelchair access on 100% of stops and 100% of trips.
In plain words: earn this mark when your feed passes validation, has not expired, and says whether nearly every stop and trip is wheelchair accessible.
A pass credential for a feed that is valid, current, and states wheelchair access on nearly every stop and trip. Accessibility here measures what the feed publishes, not whether a stop is physically usable. How the conformance mark works.
Clears the Google and Apple Maps four-week coverage bar. This feed has 152 days of service ahead, clearing the four-week (28-day) window Maps asks for. No validator errors either, so riders keep seeing this agency in their trip planners; warnings lower the grade here but do not remove a feed from Maps.
How this agency maps to the standards
The scorecard is a data-quality lens, not a compliance determination. Its universal references describe good GTFS and useful rider information. Useful references here are GTFS Schedule Best Practices, GTFS-Realtime Best Practices, MobilityData grading scheme, Google Transit publication guidance, FTA National Transit Database GTFS requirement. Read the full standards crosswalk.
In California, the published guideline is California Transit Data Guidelines. Caltrans' published quality guidelines and compliance checklist; this rubric is anchored to them.
California Minimum GTFS Guidelines checklist (6 of 6 measured items met)
The state's own Data Process Checklist, matched item by item to what this scorecard already measures. An item marked "not measured here" is real ground the checklist covers that this tool does not check; see the official checklist for the full picture.
- Meets Publish GTFS Schedule at a stable, automatically-fetchable URL
The published feed URL downloaded at the last check.
- Not measured here Implement required fields: Fares v2, text-to-speech stop names, shapes.txt, wheelchair_boarding, and Pathways where applicable
This scorecard measures wheelchair_boarding, shapes.txt coverage, fare data, and station pathways separately, below; it does not check the Fares v2 format specifically or text-to-speech stop names.
- Not measured here Achieve a passing score in every category of the MobilityData GTFS Grading Scheme v1
This scorecard automates a proxy for the Grading Scheme's rider-facing fields (see the standards crosswalk) rather than running the scheme itself, which grades by comparison to the real world by hand.
- Not measured here Publish changes to the base schedule at least one week ahead of every service change
This scorecard does not track a feed's publish history, so advance notice cannot be checked.
- Meets Produce no critical errors in the MobilityData GTFS Validator
Passes validation with no errors.
- Not measured here Publish Trip Updates, Vehicle Positions, and Alerts feeds
This scorecard checks realtime reachability and freshness overall; it does not check for all three feed types individually.
- Not measured here Update Trip Updates and Vehicle Positions at least every 20 seconds
This scorecard samples realtime freshness; it does not check this specific 20-second cadence.
- Not measured here Publish information for at least 99% of vehicles in service
This scorecard measures the share of scheduled trips represented in TripUpdates, a related but different figure than vehicle coverage.
- Not measured here Keep 100% of trip_ids consistent between Schedule and Realtime
This scorecard does not currently check trip_id consistency between the Schedule and Realtime feeds.
- Not measured here Produce no critical errors in the Center for Urban Transportation Research realtime validator
This scorecard does not run the CUTR realtime validator.
- Not measured here Publish accessible feed links on the agency or regional partner website
This scorecard does not check the agency's own website.
- Not measured here Register GTFS and GTFS-Realtime feeds with transit.land and the Mobility Database
This scorecard does not currently check aggregator registration for this section.
- Meets Designate a technical contact in feed_info.txt's feed_contact_email
feed_info.txt states a technical contact.
- Meets wheelchair_boarding stated on stops and trips
States wheelchair access on 100% of stops and 100% of trips.
- Meets shapes.txt with a shape for every trip
All 803 trips have a shape in shapes.txt.
- Meets Fare data published, or the service marked fare-free
Fare data is published.
- Correctness 82 / 100
- GTFS Schedule best practices, checked by the MobilityData validator. MobilityData grading covers stop locations, route names, and colors. Google Transit requires a feed to pass validation for publication. FTA NTD readiness also checks that the published feed is valid.
- Freshness 100 / 100
- GTFS Schedule best practices call for a dataset that stays current. An expired calendar can remove service from Google Transit and other rider trip planners. FTA NTD readiness also checks that the published feed is current.
- Rider experience 100 / 100
- GTFS Best Practices for rider-facing fields. MobilityData grading covers stop names and headsigns.
- Realtime quality Not yet published
- GTFS-Realtime best practices: a stable URL, high uptime, and frequent updates.
Show your grade
Put a badge on your agency site or feed README. It updates after each completed scoring check and links back to this scorecard.
Prefer a shields.io style? Point a dynamic endpoint badge at the published badge.json.
Cite this record
This page updates on every check. The record below does not: it is the dated file this grade came from, published at https://gtfsscorecard.org/data/artifacts/redding-area-bus-authority-3031/2026-08-01.json and never overwritten, pinning the grade, category scores, rubric version, validator version, reader archive profile, and the scored feed's sha256 as they stood on 2026-08-01. Use it in a board packet, a regulatory filing, or a research citation instead of linking the live page, whose content will differ on your next visit.
Citing the tool itself rather than one agency's record? Use the repo's CITATION.cff.