Feed status · checked 2026-08-01
Placer County
Based on the feed this agency publishes
Service mode Bus
down 0.4 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 1 hours ago; last changed 41 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
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
235 of 235 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.
⏱ A column in stops.txt; your scheduling software likely has it.worth about +25 points in its category
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
255 of 255 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
Add fare_attributes.txt (or Fares v2 files) with your fare structure. If your service is fare-free, ask to have it marked fare-free instead.
The feed contains no fare information. Riders see 'fare unknown' in trip planners and can't budget their trip; visitors are most affected.
⏱ A small file for most flat-fare systems.worth about +15 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
- 235 of 235 stops don't say whether a wheelchair user can board there.
- Next action
- Set wheelchair_boarding to 1 (accessible) or 2 (not accessible) for every stop. A field survey can start with the busiest stops.
- 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
- 255 of 255 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
- Feed evidence
- The feed contains no fare information.
- Next action
- Add fare_attributes.txt (or Fares v2 files) with your fare structure. If your service is fare-free, ask to have it marked fare-free instead.
- 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.
Set wheelchair_boarding to 1 (accessible) or 2 (not accessible) for every stop. A field survey can start with the busiest stops. · 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.
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.
Add fare_attributes.txt (or Fares v2 files) with your fare structure. If your service is fare-free, ask to have it marked fare-free instead. · 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 37 days.
- Published accessibility data
- Accessibility information is stated for 0% of stops and 0% of trips. This measures published data, not whether stops or vehicles are physically usable.
- Fare information
- No fare information is published in the feed.
- 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
The MobilityData validator flagged 6 kinds of issue across 160 instances (0 error, 117 warning, 43 informational).
Service data covers the next 37 days.
0% of stops state wheelchair accessibility (0% marked accessible, 0% marked not accessible). This measures what the feed publishes, not whether a stop is physically usable. Fare data is not published.
0% of stops state accessibility (0% marked accessible). Reflects what the feed states, not verified physical usability.
2 accessibility depth signals
1 route badge(s) pair a color and text color below the WCAG 4.5:1 contrast bar (NS267).
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.
200 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set ("Airport Dr and Business Park Dr", "Hwy 89 at McClintock Bldg", "Hwy 89 at Granlibakken", 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.
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 235 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.
- Hwy267 (red)
- Hwy89 (yellow)
- ML (teal)
- NS267 (pink)
- NS89 (orange)
- TLR (gray)
| Route | Type | Line color |
|---|---|---|
| Hwy267 Highway 267 | Bus | red |
| Hwy89 Highway 89 | Bus | yellow |
| ML Mainline AM/PM | Bus | teal |
| NS267 Hwy 267 Night Service | Bus | pink |
| NS89 Hwy 89 Night Service | Bus | orange |
| TLR Truckee Local | Bus | gray |
List every stop
- Airport Dr and Business Park Dr
- Tahoe City Transit Center - Depart
- Hwy 89 at McClintock Bldg
- Hwy 89 at Granlibakken
- Hwy 89 at Cathedral Dr
- Hwy 89 at Sequoia Ave
- Hwy 89 at Pine Ave
- Hwy 89 at Fountain Ave
- Hwy 89 at Pineland Dr
- Hwy 89 at Ward Ave
- Hwy 89 at Timberland Ln
- Hwy 89 at Elizabeth Dr
- Hwy 89 at Grand Ave
- Hwy 89 at South St (Homewood Sign)
- Hwy 89 at Homewood Ski Area
- Hwy 89 at West Shore Sports
- Hwy 89 Tahoe Ski Bowl Way
- Hwy 89 at Ellis Rd
- Hwy 89 at Lodge Dr
- Hwy 89 at McKinney Rubicon Springs Rd
- Hwy 89 at Elm St
- Hwy 89 Across from Tahoma Market and Deli
- Hwy 89 at Pine St (Tahoma Post Office)
- Sugar Pine Point State Park
- Hwy 89 at Pine St (Northbound)
- Hwy 89 at PDQ Market
- Hwy 89 Powderhorn Ln Lakeside
- Hwy 89 at Moana Cir
- Hwy 89 at Chambers Landing
- Hwy 89 at Homewood Obexer's Market
- Hwy 89 at West Shore Cafe
- Hwy 89 at Homewood Sign
- Hwy 89 Across from Grimsell Pass
- Hwy 89 at Grand Ave
- Hwy 89 at Skyland Beach
- Hwy 89 at at Mankato Lakeside
- Hwy 89 Timberland Dr Lakeside
- Hwy 89 at Sunnyside Ln
- Hwy 89 at Sunnyside Market
- Tahoe Park Ln (Lakeside)
- Sequoia Ave (North on Lakeside)
- Hwy 89 at Olympic Dr
- Hwy 89 at Granlibakken Tahoe Tavern Entrance
- Hwy 89 at Chase
- Granlibakken Resort
- Hwy 89 at Mankato Pl
- Tahoe City Transit Center - Arrive
- Hwy 28 at Crystal Bay Club (Shelter) - Arrive
- Lakeshore Dr at Country Club Dr (Hyatt) - Arrive
- Hwy 28 at Stateline Rd (Shelter) - Arrive
- Hwy 28 at Mackinaw (Bus Shelter)
- Hwy 28 at Tahoe City Marina
- Hwy 28 at Lighthouse Center (Shelter)
- Hwy 28 Across from Rocky Ridge Rd
- Hwy 28 at Star Harbor Ct
- Hwy 28 at Lake Forest Rd (West End)
- Hwy 28 at Lake Forest Rd (East End)
- Sugar Pine Point State Park
- Hwy 28 at Dollar Hill 7-11 Store (Shelter)
- Hwy 28 at Chinquapin Condos
- Hwy 28 Lardin Way Lakeside
- Hwy 28 Ridgewood Lakeside
- Hwy 28 at Gar Woods East Parking Lot
- Hwy 28 at Sierra Boat Co
- Hwy 28 Across from Placer Welfare
- Hwy 28 at Agate Sun Club Pier
- Hwy 28 at Stag Dr - Lakeside
- Hwy 28 at The Sands
- Hwy 28 at Anderson St Lakeside
- Hwy 28 at National Ave Lakeside (Shelter)
- Hwy 28 at Pino Grande Ave (Lakeside)
- Truckee Depot - Arrive
- Hwy 28 Across from KB Safeway Store
- Hwy 28 at Secline St
- Hwy 28 at Deer St KB State Beach
- Hwy 28 at Raccoon St (Lakeside)
- Hwy 28 at Fox St (Lakeside)
- Hwy 28 at Chipmunk St Lakeside
- Hwy 28 at Chipmunk St
- Hwy 28 at Fox St
- Hwy 28 at Raccoon St The Grid
- Hwy 28 after Bear St (Chevron Station)
- Hwy 28 at Deer St WB
- Hwy 28 at Secline St
- Hwy 28 at KB Safeway Store
- Hwy 28 at Pino Grande Ave (Shelter)
- Hwy 28 at National Ave (Shelter)
- Hwy 28 at Anderson Rd
- Hwy 28 at Estates Dr
- Hwy 28 at Stag Dr
- Hwy 28 at Agate Rd
- Hwy 28 at Sahara Dr
- Hwy 28 at Old P.O. Coffee Shop
- Hwy 28 at Carnelian Woods (Shelter)
- Hwy 28 at Center St
- Hwy 28 at Ridgewood Rd
- Hwy 28 at Lardin Way
- Hwy 28 at Old County Rd
- Hwy 28 at Dollar Dr
- Hwy 28 at Dollar Hill II
- Hwy 28 at Old Mill Rd
- Hwy 28 at Burton Creek
- Hwy 28 at Tamarack Lodge
- Hwy 28 at Rocky Ridge Rd
- Hwy 28 at Basecamp
- Hwy 28 at Grove St (Fat Cat Bar and Grill)
- Hwy 28 at Tahoe City WYE
- Hwy 28 Kings Beach at Crown Motel
- Soda Springs Ski Resort
- Donner Pass Rd Soda Springs General Store
- Donner Pass Rd at Soda Springs Rd
- Donner Pass Rd at Tri Lodges
- Donner Pass Rd at Ski Inn
- Donner Pass Rd Sugar Bowl Rd
- Sugar Bowl Main Lodge
- Boreal Ridge Ski Resort - Arrive
- Donner Pass Rd Ski Inn
- Donner Pass Rd Tri Lodges
- Donner Pass Rd at Soda Springs Rd
- Donner Pass Rd at Soda Springs General Store
- Donner Pass Rd at Donner Summit Lodge
- Donner Ski Ranch at Ski Ranch Ln
- HWY 28 Crystal Bay Club (Shelter) - Depart
- Sugar Bowl Gondola - Depart
- Hwy 28 at Gonowabie Rd
- Donner Pass Rd at Donner Summit Lodge
- Donner Pass Rd at Gateway Center (Safeway)
- Sugar Bowl Gondola - Arrive
- Hwy 28 at Crystal Bay Cove Condos
- Hwy 28 at Lakeshore Dr Lakeside
- Hwy 28 at Ponderosa (Guardrail) Lakeside
- Deerfield Dr at Crossroads Center (Post Office)
- Edwin Rd at Henness Rd (Bus Shelter)
- Tunnel Creek Bonanza (Arrive)
- Hwy 28 Winding Way Lakeside
- Hwy 28 at Toepa
- Hwy 28 at Village Blvd
- Hwy 28 at US Bank
- Southwood Skate Park at Hwy 28
- Southwood at Bowl Incline
- Village Blvd at Juanita Rd
- Lakeshore Dr at Incline Beach
- Lakeshore Dr at Country Club Dr (Hyatt) - Depart
- Tunnel Creek Bonanza (Depart)
- Country Club Dr at Incline Way
- Country Club Dr at Mill Creek
- Hwy 28 at Country Club By Fairway
- Hwy 28 at Northwood Blvd Mountain Side
- Hwy 28 at Raley's Shopping Center
- Hwy 28 at Christmas Tree Village
- Hwy 28 at Northwoods 76 Gas Station
- Hwy 28 at WInding Way
- Hwy 28 at Ponderosa Ave Mountain Side
- Hwy 28 at Pinion Dr
- Hwy 28 at Red Cedar Ln
- Hwy 28 at Amagosa Rd
- Hwy 28 at Stateline Rd (Shelter) - Depart
- Alpine Transport Center
- Hwy 89 at Alpine Meadows Rd (River Ranch)
- Olympic Valley Rd at 7-11 Driveway (Shelter)
- Olympic Valley Rd and Squaw Creek Rd
- Olympic Valley Rd at Post Office
- Olympic Valley Clock Tower
- Village at Palisades Tahoe - East
- Olympic Valley Rd at Resort Creek Rd (Shelter) EB
- Olympic Valley Rd at New Park (Near Entrance)
- Hwy 89 West River Mousehole
- Hwy 89 at College Trail
- Hwy 89 at Bank of America (old CHP office)
- Highway 89 South Between DMV and Freeway
- Hwy 89 at Deerfield Dr (Crossroad Driveway)
- Hwy 89 Across from West River St (Trailer Park)
- Hwy 89 at Alpine Meadows Rd (River Ranch)
- Olympic Valley Rd at Village East Rd
- Park and Ride (KidsZone)
- Donner Pass Rd and Truckee Way
- Donner Pass Rd and Truckee Way East
- Hwy 267 and Speckled St
- Hwy 267 and Cambridge Dr
- Hwy 267 and Stewart Way
- Sawmill Heights
- Northstar Village Gate # 8
- Airport Rd and Truckee Town Hall
- Airport
- Martis Valley Lodge
- Hwy 267 and Stewart Way
- Hwy 267 and Lincoln Green
- Hwy 267 and Speckled St
- Raley's Southbound
- Raleys Northbound
- Meadow View Place
- Schaffer's Mill and Heartwood Dr
- Schaffer Mill Rd and Hopkins Village Dr
- Truckee Depot - Depart
- Donner Pass Rd at Donner Lake Village Resort
- Donner Pass Rd at West End Boat Launch
- Donner Pass Rd at Moraine Rd (Sticks Market)
- Donner Pass Rd at Summit Dr
- Donner Pass Rd at Donner Memorial State Park
- Donner Pass Rd Cold Stream Rd
- Donner Pass Rd at Tri-Counties Bank Plaza
- Donner Pass Rd at Truckee High School EB
- Donner Pass Rd at Donner Trail Rd
- Donner Pass Rd at Donner Plaza
- Donner Pass Rd at Grocery Outlet/Vista Ave
- Donner Pass Rd at Tahoe Forest Cancer Center
- Donner Pass Rd at Recreation Center
- Edwin Rd at Henness Rd (Bus Shelter)
- Brockway Rd at Martis Valley Rd (The Rock Fifty-Fifty)
- Brockway Rd and Reynold Way
- Estates Dr at Senior Apartments
- Brockway Rd at Regional Park (Bus Shelter)
- Donner Pass Rd at Tahoe Forest Medical Offices
- Donner Pass Rd at Gateway Center (Safeway Bus Shelter)
- Donner Pass Rd at ACE Mountain Hardware
- Donner Pass Rd at Donner Trail Rd
- Donner Pass Rd at Northwoods Blvd
- Donner Pass Rd and Donner Trail Professional Center
- Donner Pass Rd at Donner Memorial State Park
- Donner Pass Rd at East End Donner Lake
- Donner Pass Rd at Summit Dr
- Donner Pass Rd at Moraine Rd (Sticks Market)
- Donner Pass Rd at West End Boat Launch
- Donner Pass Rd at Donner Lake Village Resort
- Donner Pass Rd at South Shore Dr (Bus Shelter)
- Brockway Rd and Palisades Dr
- Gravity Haus
- Brockway Rd Martis Valley Rd (Across from Best Western)
- Truckee Way at Rue Ivy
- Truckee Way at Coburn Crossing Apts
- Roundhouse Way at Artist Loft Apts
- Brockway Rd at Village Green MHP
- Truckee Way and Stockrest Springs Rd (Coburn Crossing Apts)
- Railyard Mobility Hub
- Donner Pass Rd/Cabona's (across from Depot)
Over time
Overall score across the last 4 checks — down 0.4 since 2026-07-31.
Show the numbers
| Check | Score | Change |
|---|---|---|
| 2026-07-25 | 67.4 | first check |
| 2026-07-30 | 65.3 | down 2.1 |
| 2026-07-31 | 64.9 | down 0.4 |
| 2026-08-01 | 64.5 | down 0.4 |
What changed since your last check
- Correctness no change
- Freshness down 1.6
- Rider experience no change
What changed in this feed
Overall score fell 0.4 points 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
10 findings, ordered by severity.
Show every finding
- Warning255 instances
255 of 255 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 (opens the GTFS Schedule reference on an external site)
- Warning235 instances
235 of 235 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 (opens the GTFS Schedule reference on an external site)
- Warning78 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 (opens the validator rules on an external site)
- Warning38 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 (opens the validator rules on an external site)
- Warning1 instance
Some service calendars in the feed have already ended.
Expired calendars are dead weight and can hide real schedule problems from your staff and vendors.
Fix: Remove past service periods the next time you export the feed. (One setting in most export tools.)
Finding code: expired_calendar · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning1 instance
The feed contains no fare information.
Riders see 'fare unknown' in trip planners and can't budget their trip; visitors are most affected.
Fix: Add fare_attributes.txt (or Fares v2 files) with your fare structure. If your service is fare-free, ask to have it marked fare-free instead. (A small file for most flat-fare systems.)
Finding code: scorecard_no_fare_data · Read the fix guide · See GTFS Best Practices (opens GTFS Best Practices 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.)
Finding code: scorecard_flex_no_booking_rules · Read the fix guide · See GTFS Schedule reference (opens the GTFS Schedule reference on an external site)
- 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 (opens the validator rules on an external site)
- 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 (opens the validator rules on an external site)
- Info1 instance
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)
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 37 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 255 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 0% 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 37 days.
- Accessible Not yet
- States wheelchair access on 0% 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.
- 38 of 235 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 37 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 (4 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 0% of stops and 0% of trips.
- Meets shapes.txt with a shape for every trip
All 255 trips have a shape in shapes.txt.
- Gap Fare data published, or the service marked fare-free
No fare data is published.
- Correctness 80 / 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 62 / 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 45 / 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/tahoe-area-regional-transit-tart-north-lake-tahoe-express/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.