GTFS Scorecard
← All agencies

Feed status · checked 2026-08-01

Siskiyou County

Based on the feed this agency publishes

Service mode Bus

81.8 / 100

unchanged since 2026-07-31

Catalogued in California.

Covers 1454 daysAccessibility gapsFlexible serviceRealtime 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.3, validator 8.0.1.

Checked for changes 1 hours ago; last changed 29 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

Fix 01

Set wheelchair_accessible on every trip. If every vehicle is accessible, this may be one default; otherwise use the value for each trip.Likely your export tool

31 of 31 trips don't say whether the vehicle is wheelchair accessible. Even with accessible stops, riders need to know the bus itself can take them.

⏱ A default or per-trip field in your export.worth about +15 points in its category

Fix 02

Remove retired stops from the export, or add them back to the trips that should serve them.Likely your export tool

Some stops exist in the feed but no trip ever stops at them. Riders may walk to a stop where no bus is scheduled to arrive.

⏱ A review pass in your scheduling software.worth about +6 points in its category

Fix 03

Check the flagged stop times for transposed minutes.

Some scheduled trips move faster between stops than a bus can. Usually a typo'd stop time; riders get arrival times no bus can meet.

⏱ A few minutes per flagged trip.worth about +6 points in its category

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.

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
31 of 31 trips don't say whether the vehicle is wheelchair accessible.
Next action
Set wheelchair_accessible on every trip. If every vehicle is accessible, this may be one default; otherwise use the value for each trip.
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. Set wheelchair_accessible on every trip. If every vehicle is accessible, this may be one default; otherwise use the value for each trip. · 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.

    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. Remove retired stops from the export, or add them back to the trips that should serve them. · 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.

    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. Check the flagged stop times for transposed minutes. · 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.

    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 1454 days.
Published accessibility data
Accessibility information is stated for 86.8% of stops and 0% 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 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.

Score by category

Correctness71.5 / 100

The MobilityData validator flagged 9 kinds of issue across 115 instances (0 error, 69 warning, 46 informational).

Freshness100.0 / 100

Service data covers the next 1454 days.

Rider experience81.6 / 100

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

Accessibility54.3 / 100

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

2 accessibility depth signals

  • 3 route badge(s) pair a color and text color below the WCAG 4.5:1 contrast bar (2, 4, 6).

    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.

  • 30 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set ("Dunsmuir Inn & Suites", "Corner of Wells & N. Dunsmuir Ave", "Dr. Centeno, DDS.", 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 152 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.

  • 2 (purple)
  • 5 (teal)
  • 3 (yellow)
  • 4 (red)
  • 1 (green)
  • 6 (black)
Routes in Siskiyou County's feed
RouteTypeLine color
2 2 - Dunsmuir/McCloud/YrekaBuspurple
5 5 - Yreka/Montague LocalBusteal
3 3 - McCloud/Dunsmuir/YrekaBusyellow
4 4 - Scott Valley/HornbrookBusred
1 1 - Cascade Flyer (Express)Busgreen
6 6 - Happy CampBusblack
List every stop
  • Dunsmuir Inn & Suites
  • Corner of Wells & N. Dunsmuir Ave
  • Mt. Shasta Fitness Club
  • Alpine Lodge
  • Dignity Health
  • Mt. Shasta Veterinarian Clinic
  • Siskiyou Gardens (Siskiyou Way)
  • Easy Street I5 Off-Ramp
  • Across from Easy Street Mart
  • Mt. Shasta Title
  • Yreka Motel
  • Carquest across from Budget Inn
  • Yreka Child Support
  • Dr. Centeno, DDS.
  • Big Red Barn
  • Scarlet Way/N. Dunsmuir Ave.
  • City Park near Rail Car
  • All Aboard Espresso
  • Across from Park @ Top of the Hill
  • Juvenile Hall
  • Etna Motel
  • Castella Post office
  • Soda Creek
  • Big Springs Church
  • Golden Eagle Charter School
  • Angel Valley - Coupa's Grocery
  • Grenada I5 Off-Ramp
  • Behavioral Health
  • Veteran's Services
  • Fairlane Road Southbound
  • Fairlane Road Northbound
  • Weed Community Center
  • Montague Community Center
  • Etna City Yard/Howell/Church St.
  • Across from Montague City Hall
  • Easy Street Mart
  • Westside Road
  • Edgewood I5 Off-Ramp
  • Edgewood I5 Off-Ramp
  • S. Dunsmuir Ave/Branstetter
  • Park @ the Top of the Hill
  • Acorn Inn
  • Mt. Shasta Shopping Center
  • Mercy Hospital
  • College of the Siskiyous
  • Boles Creek Apartments
  • Weed Ray's Market
  • Grenada - Corner of Shasta & Siskiyou
  • Raley's Shopping Center
  • Black Bear Diner
  • C.O.S. Yreka/Across from Behavioral Health
  • Social Security
  • Main Street/Across from Human Services
  • Pfeiffer Vacuum
  • Chevron/Across From Blackbear Diner
  • Across from Weed Ray's Market
  • Weed Dollar General
  • Greyhound & Comfort Inn
  • Cedar Lodge
  • Parking Lot Before City Hall
  • S. Dunsmuir Ave./Branstetter
  • Weed City Hall
  • Carrick - Corner of 1st & Center
  • Hoy Park - Corner of Pinehill & Lakeside
  • Lake Shastina Golf Course
  • Weed Elemenatary
  • Manfredi's
  • N. Main/Across from Dollar General
  • Fairchild Medical
  • Campbell Tracts
  • Courthouse - Corner of 4th & South St.
  • Yreka Dollar General
  • Montague City Hall
  • Across from Montague Post Office
  • Corner of 7th & Webb
  • Hornbrook - Across from Post Office
  • Across from Ft. Jones Post Office
  • Ft. Jones Post Office
  • Greenview Post Office
  • Greenview Post Office
  • Across from Etna Ray's Market
  • Westside Road
  • Cove Mobile Home Park
  • Gazelle Post Office
  • Truck Village
  • Truck Village
  • Abrams Lake
  • Abrams Lake
  • Valley Pacific
  • Alma West of RR tracks near USFS
  • Alma St./Rockfellow Dr.
  • Berryvale
  • Petals Flower Shop
  • Gold Room
  • Crag View Dr.
  • Corner of Shasta & Colombero
  • Across from McCloud Post Office
  • McCloud Community Services Office
  • US Forest Service Complex
  • Fisher Mobile Home Park (Klamath River)
  • Quigley Country Store
  • Horse Creek
  • Hamburg Country Store
  • Seiad Valley Country Store
  • Double J, Happy Camp
  • Indian Meadows
  • Karuk Head Start
  • Seiad Valley Country Store
  • Hamburg Country Store
  • Horse Creek Community Church
  • Quigley Country Store
  • Fisher Mobile Home Park (Klamath River)
  • Dunsmuir Dollar General
  • Rain Rock Casino
  • Corner of Easy Street & Walter's Lane
  • Ager
  • Campbell Tracts
  • Mount Shasta High School
  • Dunsmuir Dollar General
  • Mt. Shasta Shopping Center
  • Weed Dollar General
  • Raley's Shopping Center
  • Weed City Hall
  • College of the Siskiyous
  • Siskiyou Gardens (Siskiyou Way)
  • Greyhound & Comfort Inn
  • Mercy Hospital
  • Weed Elemenatary
  • Golden Eagle Charter School
  • Manfredi's
  • Gazelle Post Office
  • Courthouse - Corner of 4th & South St.
  • Karuk Museum
  • Partners Deli
  • Six Stones
  • Corner of Main St. and Meamber Street
  • Orleans Tribal Housing
  • Y.M.C.A.
  • Orleans Post Office
  • Karuk Administration Office, Happy Camp
  • Happy Camp High School
  • Happy Camp Ray's Market
  • Natural Resource Center
  • Salmon River Outpost
  • Reginato's
  • Burger Barn
  • Evergreen Lodge
  • Human Services
  • Cold Creek Inn
  • Rockfellow/Everett Memorial
  • Ivy St./Community Bldg.
  • Transit Center

Over time

Overall score across the last 4 checks — unchanged since 2026-07-31.

2026-07-25: 81.82026-07-30: 81.82026-07-31: 81.82026-08-01: 81.8
Show the numbers
CheckScoreChange
2026-07-2581.8 first check
2026-07-3081.8 no change
2026-07-3181.8 no change
2026-08-0181.8 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

12 findings, ordered by severity.

Show every finding
  • Warning40 instances

    Some stops exist in the feed but no trip ever stops at them.

    Riders may walk to a stop where no bus is scheduled to arrive.

    Fix: Remove retired stops from the export, or add them back to the trips that should serve them. (A review pass in your scheduling software.)

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

  • Warning31 instances

    31 of 31 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. If every vehicle is accessible, this may be one default; otherwise use the value for each trip. (A default or per-trip field in your export.)

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

  • Warning20 instances

    20 of 152 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 · See GTFS Schedule reference

  • Warning17 instances

    Some scheduled trips move faster between stops than a bus can.

    Usually a typo'd stop time; riders get arrival times no bus can meet.

    Fix: Check the flagged stop times for transposed minutes. (A few minutes per flagged trip.)

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

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

  • Warning3 instances

    Fast travel between far stops (flagged by the MobilityData validator).

    See the linked rule for what this affects.

    Fix: Review the rule documentation for 'fast_travel_between_far_stops' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)

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

  • Warning3 instances

    Some route colors don't contrast with their text color.

    Route badges get hard to read, most of all for riders with low vision.

    Fix: Pick a darker/lighter route_text_color for the flagged routes. (One field per route.)

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

  • 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.)

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

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

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

  • Info2 instances

    Service extends far in the future (flagged by the MobilityData validator).

    See the linked rule for what this affects.

    Fix: Review the rule documentation for 'service_extends_far_in_the_future' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)

    Finding code: service_extends_far_in_the_future · See MobilityData GTFS Validator rules

  • 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

Beyond the grade

Opportunities that do not change your grade today: fare detail, on-demand service, and deeper accessibility data.

  • 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).

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 1454 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 31 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

This feed is close to the conformance mark. States wheelchair access on 87% of stops and 0% of trips; the mark needs 90% of each.

Valid Met
Passes validation with no errors.
Current Met
Service data covers the next 1454 days.
Accessible Not yet
States wheelchair access on 87% 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.

Can riders use it?

Checks beyond structural validation: places where the feed is valid but a rider still could not travel.

  • 40 of 152 boardable stops are never served by any trip. Riders see these stops in apps and on the map but can never catch anything there, which erodes trust in the data. Remove stops no route serves, or add the trips that should call at them.

These do not change the grade. They catch trips with no rideable leg and stops no trip serves, the kind of gap a trip planner trips over.

Clears the Google and Apple Maps four-week coverage bar. This feed has 1516 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 87% of stops and 0% of trips.

  • Meets shapes.txt with a shape for every trip

    All 31 trips have a shape in shapes.txt.

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

    Fare data is published.

Correctness 72 / 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 82 / 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.

Siskiyou County GTFS data quality grade: B

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/siskiyou-county/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.