Prep for a call: printable one-page brief · For your board packet: printable one-pager · Compare with another agency · Watch this feed: get an email before it expires
Feed status · checked 2026-07-09
Redding Area Bus Authority (RABA)
Based on the feed this agency publishes
unchanged since 2026-07-08
Ahead of 4% of all tracked agencies and 4% of mid-size agencies. Operates 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.1, validator 8.0.1.
Checked for changes 8 hours ago; last changed 8 days ago.
Top things to fix
Re-export the feed with a calendar that reaches further out, and set feed_info feed_end_date past your next service change.Likely your export tool
Service data ended 1012 day(s) ago. When the calendar runs out, trip planners stop showing this agency even though the buses are still running. Riders are told the service does not exist.
⏱ Usually one export setting; export on a schedule so it never lapses again.worth about +100 points
Agencies here usually clear this within about 1 week (based on 18 observed fixes).
Review the rule documentation for 'foreign_key_violation' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.
Foreign key violation (flagged by the MobilityData validator). See the linked rule for what this affects.
⏱ Varies.worth about +24 points
Review the rule documentation for 'invalid_currency_amount' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.
Invalid currency amount (flagged by the MobilityData validator). See the linked rule for what this affects.
⏱ Varies.worth about +18 points
Trillium produces and hosts this feed as a service. These changes are made on their side: send the fix list to your Trillium contact and they apply it and republish.
Close the loop on each fix. Read the guide, make the change in your tool, and let the next run verify it — the scorecard shows the fix; the agency publishes it.
Re-export the feed with a calendar that reaches further out, and set feed_info feed_end_date past your next service change. · Read the fix guide
Make the change. Trillium produces and hosts this feed as a service. These changes are made on their side: send the fix list to your Trillium contact and they apply it and republish.
Prove it cleared. The next scorecard run re-checks this automatically and, once it is gone, mints a dated receipt. Self-check a feed before you publish.
Review the rule documentation for 'foreign_key_violation' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.
Make the change. Trillium produces and hosts this feed as a service. These changes are made on their side: send the fix list to your Trillium contact and they apply it and republish.
Prove it cleared. The next scorecard run re-checks this automatically and, once it is gone, mints a dated receipt. Self-check a feed before you publish.
Review the rule documentation for 'invalid_currency_amount' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. · Read the fix guide
Make the change. Trillium produces and hosts this feed as a service. These changes are made on their side: send the fix list to your Trillium contact and they apply it and republish.
Prove it cleared. The next scorecard run re-checks this automatically and, once it is gone, mints a dated receipt. Self-check a feed before you publish.
Send Trillium a fix request
This feed is produced and hosted by Trillium. Copy this and send it to your Trillium contact; they make the change and republish the feed. Each fix names the validator notice and a guide link.
Send the agency a note
Supporting this agency? Copy this and email it to them. It names what lapsed, why it matters to riders, and the one setting to change.
Score by category
The MobilityData validator flagged 10 kinds of issue across 654 instances (557 error, 12 warning, 85 informational).
Service data ended 1012 day(s) ago. Trip planners have likely already dropped this feed.
1% of stops state wheelchair accessibility (1% marked accessible, 0% marked not accessible). This measures what the feed publishes, not whether a stop is physically usable. Fare data is published.
1% of stops state accessibility (1% marked accessible). Reflects what the feed states, 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.
Skip to route and stop dataBasemap: OpenFreeMap, © OpenStreetMap contributors. Routes and stops: this agency's GTFS feed.
- 1 (teal)
- 3 (teal)
- 4 (white)
- 5 (white)
- 7 (teal)
- 11 (gray)
- 14 (purple)
- BE (teal)
- SE (yellow)
- 2W (orange)
- 2E (white)
- 6N (white)
- 6S (brown)
- BB (blue)
- 9 (red)
- AC (black)
- CTE (green)
| Route | Type | Line color |
|---|---|---|
| 1 Route 1 | Bus | teal |
| 3 Route 3 | Bus | teal |
| 4 Route 4 | Bus | white |
| 5 Route 5 | Bus | white |
| 7 Route 7 | Bus | teal |
| 11 Route 11 | Bus | gray |
| 14 Route 14 | Bus | purple |
| BE Burney Express | Bus | teal |
| SE School Express | Bus | yellow |
| 2W Route 2 West | Bus | orange |
| 2E Route 2 East | Bus | white |
| 6N Route 6 North | Bus | white |
| 6S Route 6 South | Bus | brown |
| BB Beach Bus | Bus | blue |
| 9 Route 9 | Bus | red |
| AC Anderson Commuter | Bus | black |
| CTE Crosstown Express | Bus | green |
This feed has 350 stops.
List every stop
- Masonic Transfer Center
- 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
- Lake Blvd at St. Marks St
- Lake Blvd at Keswick Dam Rd
- Lake Blvd at Oasis Rd
- Lake Blvd at Hiatt Dr
- Lake Blvd n/o Aarly Ln
- Lake Blvd n/o Dean Rd
- Lake Blvd at Pine Cone Dr
- Lake Blvd at Newton Rd
- Lake Blvd at Pine Grove Ave
- Hill Blvd at Ranchera Rd
- Hill Blvd at Pine Ave
- Shasta Dam Blvd at Lake Blvd
- Shasta Dam Blvd at Sacramento St
- Shasta Dam Blvd at Shasta Park Dr
- Shasta Dam Blvd at Givan St
- Shasta Dam Blvd at Montana Ave
- 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
- 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
- East St at Lincoln St
- East St at Placer St
- Downtown Transit Center
- Lincoln St at S. Market St
- S. Market St at California St
- S. Market St at Grange St
- Ellis St at Polk St
- S. Market St at Ellis St
- Parkview Ave at Akard Ave
- Parkview Ave at Freebridge St
- Park Marina Dr at Locust St
- Park Marina Dr at Olympus Ave
- Park Marina Dr at Sundial Bridge Dr
- Continental St at Butte St
- Trinity St at Liberty St
- Trinity St at California St
- Court St at Butte St
- Court St at Gold St
- Court St at Sonoma St
- Rosaline Ave at West St
- Airpark Dr at Rosaline Ave
- 2525 Airpark Dr
- Airpark Dr at Sonoma St
- Airpark Dr at Gold St
- Placer St at Mesa St
- Placer St at San Francisco St
- Buenaventura Blvd at Placer St
- Buenaventura Blvd at N. Cal Ore Dr
- Buenaventura Blvd at Eureka Way
- Eureka Way at Whiskeytown Ct
- Eureka Way at Walnut Ave
- Orange Ave at Eureka Way
- Orange Ave at Shasta St
- Magnolia Ave at Tehama St
- 11th St at Eureka Way
- Court St at 11th St
- Court St at Shasta St
- Court St at Shasta St
- Court St at 11th St
- 11th St at Eureka Way
- Eureka Way at Magnolia Ave
- Eureka Way at Pioneer Dr
- Eureka Way at Overhill Dr
- Eureka Way at Sunset Dr
- Buenaventura Blvd at Eureka Way
- Buenaventura Blvd at Lakeside Dr
- Buenaventura Blvd at Rosita Dr
- Placer St at San Francisco St
- Placer St at Mesa St
- Airpark Dr at Gold St
- Airpark Dr at Sonoma St
- 2510 Airpark Dr
- Airpark Dr at Rosaline Ave
- Rosaline Ave at West St
- Court St at Sonoma St
- Court St at Gold St
- SR 273 (frontage rd) at Happy Valley Rd
- 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
- Railroad Ave at Buenaventura Blvd
- Railroad Ave at Grandview Ave
- West St at Linden Ave
- Sheridan St at Court St
- Railroad Ave at Sheridan St
- Railroad Ave at Logan St
- Railroad Ave at Laurel Ave
- Railroad Ave at Grandview Ave
- Canyon Creek Rd at Buenaventura Blvd
- Westside Rd at El Reno Ln
- Westside Rd at Kenyon Dr
- Breslauer Way at Eastside Rd
- Breslauer Way at Veterans Ln
- Radio Ln at Cerro Ln
- E. Bonnyview Rd at N. Bonnyview Rd
- 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
- 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
- Maraglia St e/o Hilltop Dr
- 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
- Loma Vista Dr at Traverse St
- Bechelli Ln at Layton Rd
- Bechelli Ln at 3rd St
- Bechelli Ln at Wilshire Dr
- Bechelli Ln at Hartnell Ave
- Bechelli Ln at Beagle Ln
- Bechelli Ln at Cypress Ave
- Bechelli Ln at Knollcrest Dr
- Bechelli Ln at Leila Ave
- Bechelli Ln at Beagle Ln
- Bechelli Ln at 3rd St
- Bechelli Ln at Layton Rd
- Loma Vista Dr at Traverse St
- 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
- East St at Butte St
- Trinity St at Liberty St
- Placer St at Continental St
- Sequoia St at Sacramento St
- South St at Athens Ave
- Athens Ave at Cypress Ave
- Hartnell Ave at Parkview Ave
- Hartnell Ave at Shotwick Trail
- Hartnell Ave at Bechelli Ln
- Hartnell Ave at Northwoods Way
- Hartnell Ave at Arcade Way
- Hartnell Ave at Reservoir Ln
- Hartnell Ave at Middleton Ln
- Hartnell Ave at Victor Ave
- Hartnell Ave at Churn Ct
- Hartnell Ave at Shasta View Dr
- Shasta View Dr at Leonard St
- Venus Way at Scorpius Way
- Galaxy Way at Meteor St
- Victor Ave at Galaxy Way
- Victor Ave at Marlene Ave
- Victor Ave at Bramble Pl
- Hartnell Ave at Robert Ct
- Hartnell Ave at Middletown Ln
- Hartnell Ave at Irwin Rd
- Hartnell Ave at Arcade Way
- Hartnell Ave at Northwoods Way
- Hartnell Ave at Bechelli Ln
- Hartnell Ave at Shotwick Trail
- Hartnell Ave at Parkview Ave
- Athens Ave at Cypress Ave
- South St at Athens Ave
- and 100 more (see the full list on the map or in the GeoJSON)
Over time
Overall score across the last 9 checks — unchanged since 2026-07-08.
Show the numbers
| Check | Score | Change |
|---|---|---|
| 2026-06-30 | 26.4 | first check |
| 2026-07-01 | 26.4 | no change |
| 2026-07-02 | 26.4 | no change |
| 2026-07-04 | 26.4 | no change |
| 2026-07-05 | 26.4 | no change |
| 2026-07-06 | 26.4 | no change |
| 2026-07-07 | 26.4 | no change |
| 2026-07-08 | 26.4 | no change |
| 2026-07-09 | 26.4 | 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-08.
Same feed file as 2026-07-08; 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
- Error524 instances
Foreign key violation (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'foreign_key_violation' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Validator rule: foreign_key_violation · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Error31 instances
Invalid currency amount (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'invalid_currency_amount' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Validator rule: invalid_currency_amount · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Error1 instance
Duplicate key (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'duplicate_key' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Validator rule: duplicate_key · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Error1 instance
Missing required column (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'missing_required_column' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Validator rule: missing_required_column · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Error1 instance
Service data ended 1012 day(s) ago.
When the calendar runs out, trip planners stop showing this agency even though the buses are still running. Riders are told the service does not exist.
Fix: Re-export the feed with a calendar that reaches further out, and set feed_info feed_end_date past your next service change. (Usually one export setting; export on a schedule so it never lapses again.)
Agencies here usually clear this within about 1 week (based on 18 observed fixes).
Validator rule: scorecard_feed_expired · Read the fix guide · See GTFS Best Practices (opens GTFS Best Practices on an external site)
- Warning451 instances
451 of 451 trips don't say whether the vehicle is wheelchair accessible.
Even with accessible stops, riders need to know the bus itself can take them.
Fix: Set wheelchair_accessible on every trip (most small-agency fleets are 100% accessible, so this is often a single default). (Often one default setting in your export.)
Agencies here usually clear this within about 1 week (based on 5 observed fixes).
Validator rule: scorecard_wheelchair_accessible_unknown · Read the fix guide · See GTFS Schedule reference (opens the GTFS Schedule reference on an external site)
- Warning348 instances
348 of 350 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.
Fix: Set wheelchair_boarding to 1 (accessible) or 2 (not accessible) for every stop. A field survey can start with the busiest stops. (A column in stops.txt; your scheduling software likely has it.)
Validator rule: scorecard_wheelchair_boarding_unknown · Read the fix guide · See GTFS Schedule reference (opens the GTFS Schedule reference on an external site)
- Warning10 instances
Some service calendars in the feed have already expired.
Expired calendars are dead weight and can hide real schedule problems from your staff and vendors.
Fix: Remove past service periods the next time you export the feed. (One setting in most export tools.)
Agencies here usually clear this within about 1 week (based on 61 observed fixes).
Validator rule: expired_calendar · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning5 instances
5 of 451 trips have no headsign.
Riders at the stop can't tell which direction a bus is going.
Fix: Populate trip_headsign to match what the bus displays. (Usually a bulk edit in your scheduling software.)
Validator rule: scorecard_missing_headsigns · Read the fix guide · See GTFS Best Practices (opens GTFS Best Practices on an external site)
- Warning1 instance
This feed's service calendar runs out within the next 7 days.
When the calendar ends, Google Maps and other trip planners drop your agency entirely. Riders see no service at all.
Fix: Export and publish an updated GTFS feed that covers at least the next 30 days of service. (Usually a re-export from your scheduling software.)
Agencies here usually clear this within about 1 week (based on 16 observed fixes).
Validator rule: feed_expiration_date7_days · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning1 instance
Many of the feed's trips don't run at all in the next 7 days.
It usually means old service periods are still in the export, making the feed bigger and harder to check.
Fix: Trim past service periods the next time you export. (One setting in most export tools.)
Agencies here usually clear this within about 1 week (based on 31 observed fixes).
Validator rule: trip_coverage_not_active_for_next7_days · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning1 instance
This feed describes flexible (demand-responsive) service but has no booking_rules.txt.
Riders can see the service area but not how or when to reserve a trip, so they can't actually use the service.
Fix: Add booking_rules.txt saying how far ahead and how to book (phone, app, or web). (A small file; one rule often covers the whole service.)
Validator rule: scorecard_flex_no_booking_rules · Read the fix guide · See GTFS Schedule reference (opens the GTFS Schedule reference on an external site)
- Info70 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.)
Validator rule: unknown_column · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Info9 instances
Unknown file (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'unknown_file' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Agencies here usually clear this within about 1 week (based on 6 observed fixes).
Validator rule: unknown_file · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Info6 instances
Service window outside feed period (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'service_window_outside_feed_period' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Agencies here usually clear this within about 1 week (based on 17 observed fixes).
Validator rule: service_window_outside_feed_period · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
Beyond the grade
Opportunities that do not change your grade today: fare detail, on-demand service, and deeper accessibility data.
The feed publishes fare products but no fare_media.txt declaring how riders can pay.
Consider: Add fare_media.txt listing your accepted payment methods, including contactless EMV if riders can tap to pay.
Flex zones are published but no booking_rules.txt is present.
Consider: Add booking_rules.txt with how far ahead and how to reserve (phone, app, or web).
5 route badge(s) pair a color and text color below the WCAG 4.5:1 contrast bar (BE, CTE, 3, 4, 7).
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.
342 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set ("Northpoint Dr at Lake Blvd", "Northpoint Dr at Redwood Blvd", "Redwood Blvd at Marijean Way", and more).
Consider: Add tts_stop_name with the spoken form, e.g. 'Main Street and Second Avenue', for the affected stops.
NTD certification readiness Not ready
Resolve this before you certify on the D-10. 4 validator errors to resolve. Service data expired 1012 days ago, so FTA would find the link out of date.
- Published Ready
- Published at a public URL.
- Valid Needs attention
- 4 validator errors to resolve.
- Current Not ready
- Service data expired 1012 days ago, so FTA would find the link out of date.
- agency_id matches your NTD ID Not checked yet
- Setting your GTFS agency_id to your five-digit NTD ID is an optional way to line a feed up with its National Transit Database record. FTA links the two on your P-50 form, so it is not a required feed change. We don't have your NTD ID on file, so this is not checked yet.
In plain words: if you report to the federal transit database, you have to publish a working, up-to-date feed and confirm it once a year. This box is a heads-up on whether yours looks ready; it is not the official sign-off.
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). Aligning agency_id with your NTD ID lets the feed line up with your NTD record; the July 2025 final rule links the two on the P-50 form rather than requiring that feed change, and 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 Not yet
This feed is close to the conformance mark. 4 validator errors to resolve. Service data expired 1012 days ago. States wheelchair access on 1% of stops and 0% of trips; the mark needs 90% of each.
- Valid Not yet
- 4 validator errors to resolve.
- Current Not yet
- Service data expired 1012 days ago.
- Accessible Not yet
- States wheelchair access on 1% of stops and 0% of trips; the mark needs 90% of each.
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.
Below the Google and Apple Maps four-week coverage bar. This feed's last day of service has passed, so Google and Apple Maps will stop showing your agency. Re-export with a calendar that covers at least the next four weeks. The feed also carries 557 validator errors, the other thing Maps checks at onboarding; the findings below name each fix.
How this agency maps to the standards
A data-quality lens, not a compliance determination. Each category shows this feed's score and the standards it relates to: the FTA National Transit Database GTFS requirement, the MobilityData grading scheme, and the Google Transit gate. 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 (3 of 5 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.
- Gap Produce no critical errors in the MobilityData GTFS Validator
4 validator errors to resolve.
- 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.
- Gap wheelchair_boarding stated on stops and trips
States wheelchair access on 1% of stops and 0% of trips.
- Not measured here shapes.txt with a shape for every trip
Shape coverage has not been measured for this feed.
- Meets Fare data published, or the service marked fare-free
Fare data is published.
- Correctness 18 / 100
- GTFS Schedule best practices, checked by the MobilityData validator. MobilityData grading: stop locations, route names and colors. Google Transit: a feed must pass validation to stay in Maps.
- Freshness 0 / 100
- The FTA National Transit Database expectation of a valid, current feed. Google Transit: an expired calendar drops the agency from Maps.
- Rider experience 60 / 100
- GTFS Best Practices for rider-facing fields. MobilityData grading: 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 live badge on your agency site or feed README. It updates daily 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-raba-114/2026-07-09.json and never overwritten, pinning the grade, category scores, rubric version, validator version, and the scored feed's sha256 as they stood on 2026-07-09. Use it in a board packet, an NTD narrative, 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.