GTFS Scorecard
← All agencies

Feed status · checked 2026-10-07

Trinity Transit

Based on the feed source on file; publisher ownership is not verified

Service mode Bus

85.5 / 100

down 0.2 since 2026-10-06

Cataloged in California.

Covers 85 daysAccessibility gapsRealtime not yet published

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.4, validator 8.0.1.

Checked for changes 3 hours ago; last changed 3 hours ago.

Measured 3 of 4 score categories from the feed URL on file (publisher not verified).

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 configured feed URL. Publisher ownership of that URL is not verified.

Confidence describes how much the pipeline could measure this run, not the feed itself. It never changes the grade.

About this feed

Trinity Transit’s published feed lists 4 bus routes, 74 scheduled trips and 73 stops. Its service dates run from 2026-02-02 through 2026-12-31. The published file last changed on 2026-10-07.

Top things to fix

Fix 01

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

70 of 73 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.

Fixing this covers 70 of 73 stops, about 96% of them.

⏱ A column in stops.txt; your scheduling software likely has it.worth about +24 points in its category

Fix 02

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.

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.

⏱ Usually an export-tool fix, not hand editing.worth about +6 points in its category

Fix 03

Drop the short name from route_long_name and keep the long name descriptive, like 'Downtown via 5th Ave'.

Some route long names repeat the route's short name inside them. Apps show both names together, so riders see the number twice, like '5 5 Downtown'.

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.

⏱ One field per flagged route.worth about +4 points in its category

Riders and need behind these fixes

  • This feed carries no National Transit Database ID, so annual rider-trips are not known for it.
  • California 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-10-05.

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

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.

Finding
Fix 01 in Top things to fix: its feed evidence and the requested change.
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.

  1. Fix 01 · Read the fix guide for scorecard_wheelchair_boarding_unknown

    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.

  2. Fix 02 · Read the fix guide for trip_distance_exceeds_shape_distance_below_threshold

    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.

  3. Fix 03

    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 85 days.
Published accessibility data
Accessibility information is stated for 4.1% 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

Correctness84.0 / 100

The MobilityData validator flagged 6 kinds of issue across 98 instances (0 error, 20 warning, 78 informational).

Freshness100.0 / 100

Service data covers the next 85 days.

Rider experience76.0 / 100

4% of stops state wheelchair accessibility (4% marked accessible, 0% marked not accessible). This measures what the feed publishes, not whether a stop is physically usable. Fare data is published.

Accessibility40.1 / 100

4% of stops state accessibility (4% marked accessible). Reflects what the feed states, not verified physical usability.

1 accessibility depth signal

  • 33 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set ("East Fork Rd.", "Big Flat @ Trinity Rafting", "B Bar K Rd", and more).

    Consider: Add tts_stop_name with the spoken form, e.g. 'Main Street and Second Avenue', for the affected stops.

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.

FaresLegacy fares

Fares are applied to trips.

Realtime qualityNot yet measured

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 73 stops.

Skip to route and stop data

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.

  • Hayfork (purple)
  • Lewiston (orange)
  • Willow Creek (blue)
  • Redding (red)
Routes in Trinity Transit's feed
RouteTypeLine color
Hayfork Hayfork LineBuspurple
Lewiston Lewiston LineBusorange
Willow Creek Willow Creek LineBusblue
Redding Redding LineBusred
List every stop
  • RABA Downtown Passenger Terminal
  • Old Shasta
  • Old Shasta @ Buell Alley
  • Trinity Dam Blvd.
  • Trinity Dam Blvd.
  • French Gulch
  • French Gulch
  • Canby Rd. (Mt. Shasta Mall)
  • Big Foot Campground
  • Big Foot Campground
  • Buddy's Towing
  • Weaverville Library
  • Junction City Cafe
  • Power House Road
  • Trinity Canyon Lodge
  • East Fork Rd.
  • Pigeon Point
  • Big Flat @ Trinity Rafting
  • Big Bar Ranger Station
  • Big Bar @ Old Market
  • Del Loma RV Park
  • Burnt Ranch Post Office
  • Burnt Ranch Store
  • Hawkins Bar @ Denny Rd.
  • Salyer Store
  • Early Bird
  • Panther Rd.
  • Willow Creek @ SR 299 & 96
  • Panther Rd.
  • Early Bird
  • Salyer Store
  • Hawkins Bar @ Denny Rd.
  • Burnt Ranch Store
  • Burnt Ranch Post Office
  • Del Loma RV Park
  • Big Bar @ Old Market
  • Corral Bottom Rd.
  • Big Flat @ TAP Store
  • Pigeon Point
  • East Fork Rd.
  • Trinity Canyon Lodge
  • Power House Road
  • Junction City Store
  • SR 3 Mini Mart
  • Lewiston Rd. & Browns Mtn. Rd.
  • Indian Creek Lodge
  • SR 299 & Martin Rd. (Burger King)
  • Mountain View St.
  • Mill St.
  • Whispering Pines
  • Center St. & SR 3
  • Health & Human Services
  • Indian Creek Park
  • Lewiston Rd. & Browns Mtn. Rd.
  • First St. & Fremont St.
  • Community Center
  • Lewiston Mini Mart
  • Maxwell's Market
  • Douglas City Park & Ride
  • B Bar K Rd
  • Barker Creek Rd
  • Wildwood Rd.
  • Big Creek Rd.
  • Frontier Village
  • Frontier Fuel
  • Hayfork Library
  • Hayfork Post Office
  • Frontier Fuel
  • Big Creek Rd.
  • Wildwood Rd.
  • Summit Creek Rd
  • B Bar K Rd
  • Shasta College

Over time

Overall score across the last 2 checks — down 0.2 since 2026-10-06.

2026-10-06: 85.72026-10-07: 85.5
Show the numbers
CheckScoreChange
2026-10-0685.7 first check
2026-10-0785.5 down 0.2

What changed since your last check

  • Correctness down 0.5
  • Freshness no change
  • Rider experience no change

Feed history

Every check on record for this feed, grouped by the published file, newest first. A new file means the published zip changed. Grades from earlier rubric versions are shown with their rubric and are not comparable with today’s grade or the trend above.

CheckedPublished fileService dates throughGrade at the time
2026-10-0713e10dc37fab2026-12-31Current rubric: see the trend above
2026-10-06b259266c94862026-12-31Current rubric: see the trend above
2026-08-06 to 2026-08-07 (2 checks)676bb3acf1f02026-12-31B, 87.5 under rubric 1.3, an earlier scoring contract; not comparable with today’s grade
2026-06-19 to 2026-07-10 (22 checks)6872a99179062026-12-31B, 87.6 under rubric 1.1, an earlier scoring contract; not comparable with today’s grade

What changed in this feed

Overall score fell 0.2 points since 2026-10-06.

The feed file was re-published since 2026-10-06.

New since 2026-10-06 (1 finding)

Subscribe to this feed’s changes (Atom) to hear about grade drops and export changes in a reader, with no sign-up.

Everything we checked

7 findings, ordered by severity.

Show every finding
  • Warning70 instances

    70 of 73 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.)

    Finding code: scorecard_wheelchair_boarding_unknown · Read the fix guide for scorecard_wheelchair_boarding_unknown · See GTFS Schedule reference

  • Warning15 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 for trip_distance_exceeds_shape_distance_below_threshold · See MobilityData GTFS Validator rules

  • Warning4 instances

    Some route long names repeat the route's short name inside them.

    Apps show both names together, so riders see the number twice, like '5 5 Downtown'.

    Fix: Drop the short name from route_long_name and keep the long name descriptive, like 'Downtown via 5th Ave'. (One field per flagged route.)

    Finding code: route_long_name_contains_short_name · See MobilityData GTFS Validator rules

  • 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 for stop_too_far_from_shape_using_user_distance · See MobilityData GTFS Validator rules

  • Info74 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

  • 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 for unknown_column · See MobilityData GTFS Validator rules

  • Info2 instances

    The feed includes a file that is not part of the GTFS spec.

    Apps ignore files they don't know, and a stray file can hide a misspelled standard file name.

    Fix: Check the flagged file name for a typo of a standard GTFS file. Remove it if it is a vendor extra. (A quick look at the flagged file.)

    Finding code: unknown_file · Read the fix guide for unknown_file · See MobilityData GTFS Validator rules

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 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 74 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 Not yet

One requirement remains for this feed to earn the conformance mark. States wheelchair access on 4% of stops and 100% of trips; the mark needs 90% of each.

Valid Met
Passes validation with no errors.
Current Met
Service data covers the next 85 days.
Accessible Not yet
States wheelchair access on 4% of stops and 100% 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.

Clears the Google and Apple Maps four-week coverage bar. This feed has 85 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 (5 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.

  • Gap wheelchair_boarding stated on stops and trips

    States wheelchair access on 4% of stops and 100% of trips.

  • Meets shapes.txt with a shape for every trip

    All 74 trips have a shape in shapes.txt.

  • Meets Fare data published, or the service marked fare-free

    Fare data is published.

Correctness 84 / 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 76 / 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.

Part of the California portfolio: the same scorecards for every feed we track in that group, on one free page.

For programs that support several agencies

This scorecard and the board one-pager for Trinity Transit are free, and they stay free. If you support several agencies, as a state program, a technical-assistance center, a feed vendor, or a consultancy, you can buy the program report bundle. It puts this agency's board report in one archive with the reports for the other agencies you support, and each cover carries your program's name, logo, and accent color.

The report for Trinity Transit uses the same numbers as this page: grade B (85.5 out of 100) as of the check on 2026-10-07, its category scores, its top fixes, and its score at each check.

One bundle, up to 25 agencies: $149, paid once, delivered within 2 business days or refunded. Other plans, including a monthly refresh, are on the bundle page.

See the program report bundle

See a sample bundle report: a real agency's current grade, with placeholder branding.

A purchase buys no influence over grades, methodology, or which agencies are listed. The grade on this page comes from the check on 2026-10-07, scored with rubric v1.4 and MobilityData gtfs-validator 8.0.1. Based on the feed source on file; publisher ownership is not verified. Read how the grade is calculated.

Similar feeds in California

Other scorecards in California, starting with the same kind of service at a similar size. Listed for comparison, not ranked.

Show your grade

Put this badge on your agency site or feed README. It updates after each completed scoring check, shows the date of that check, and links back to this scorecard. When there is no current score it says so instead of showing an old one.

Trinity Transit: GTFS feed quality grade B, 85.5 of 100, checked 2026-10-07. GTFS 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/trinity-transit-2709/2026-10-07.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-10-07. 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.