Feed status · checked 2026-08-01
Tahoe Transportation District
Based on the feed this agency publishes
Service mode Bus
unchanged since 2026-07-31
Catalogued in Nevada.
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 9 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
127 of 127 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
132 of 132 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
- 127 of 127 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
- 132 of 132 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 states that service is published through 2099-12-31. This may be intentional or a placeholder; confirm current service with the transit operator.
- 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 7 kinds of issue across 26 instances (0 error, 22 warning, 4 informational).
Service is published through 2099-12-31. It may be intentional, but confirm the end date before treating the feed as maintained.
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 (55).
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.
118 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set ("South Ave/3rd St (Barton Hospital)", "3rd St (Tahoe Senior Plaza)", "US 50/3rd St (Orchids)", 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.
This agency publishes realtime, but the feed needs an access key we don't have 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 127 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.
- 50 (brown)
- 55 (red)
- 19X (yellow)
- 22 (teal)
- 28 (teal)
| Route | Type | Line color |
|---|---|---|
| 50 South Shore Daily | Bus | brown |
| 55 Neighborhood Connection | Bus | red |
| 19X Valley Express Daily | Bus | yellow |
| 22 South Shore Service and Lake Express Daily | Bus | teal |
| 28 East Shore Express | Bus | teal |
List every stop
- South Y Transit Center
- Lake Tahoe Community College Mobility Hub
- Stateline Transit Center
- Kingsbury Transit Center
- South Ave/3rd St (Barton Hospital)
- 3rd St (Tahoe Senior Plaza)
- US 50/3rd St (Orchids)
- US 50/Tahoe Keys Blvd (Winter's Electric)
- US 50/Truckee Dr (Grocery Outlet)
- US 50/Stockton Ave
- US 50/Reno Ave
- US 50/ Carson Ave (Town and Country Center)
- US 50/Al Tahoe Blvd (US Bank)
- Al Tahoe Blvd/US 50 (Tahoe Center/Rite Aid)
- College Ave/US Forest Service
- Al Tahoe/Johnson Blvd (El Dorado County Offices)
- Al Tahoe/US 50 (LTUSD Offices)
- US 50/Lyons Ave (Middle School)
- US 50/Tallac Ave (Visitor/Senior Center)
- US 50/Rufus Allen Blvd (County Library)
- US 50/Takela Dr (Bank of America)
- US 50/Johnson Blvd (Safeway)
- US 50/Fairway Ave
- US 50/Ski Run Blvd
- US 50/Wildwood Ave
- US HW 50/ Midway Rd (Hampton Inn)
- US 50/Pioneer Trail (Subway)
- US 50/Park Ave (Village Center - Raley's)
- US 50/Pioneer Trail (Holiday Inn Express)
- US 50/Wildwood Ave
- US 50/ Ski Run Blvd
- US 50/ Fairway Ave (Heidi's)
- US 50/Takela Dr (Beach Retreat)
- US 50/Fremont St (Across from DMV)
- US 50/San Jose Ave (Lakeview Commons)
- US 50/Modesto Ave
- US 50/Bigler Ave
- US 50 (Presbyterian Church)
- US 50/ Brockway Ave (Jack in the Box)
- US 50/Sierra Blvd
- US 50/Lodi Ave
- US 50/Truckee Dr (Motel 6)
- US 50/Tahoe Keys Blvd (O'Reilly Auto Parts)
- US 50/3rd St
- Johnson Blvd/Fairway Dr
- Johnson Blvd/Marlettr Circle (Cemetery)
- Johnson Blvd/Marlette Circle
- Pioneer Trail/Shepherds Rd
- Pioneer Trail/Glen Dr
- Pioneer Trail/Moss Rd
- US 50/ Lake Parkway (Bally's/Tahoe Blue Event Center)
- Herbert Ave/Red Lake Rd (Kelly Ridge)
- Spruce Ave/Herbert Ave
- Spruce Ave/Blackwood Rd
- Ski Run Blvd/Spruce Ave (Terry)
- Pioneer Trail/Spruce Ave
- Johnson Blvd/Al Tahoe Blvd (El Dorado County Sheriff/CSLT Police Dept)
- Glenwood Way/Blackwood Rd
- US 50/Lake Parkway (Golden Nugget)
- US 50/Stateline Ave (Harvey's)
- Pioneer Trail/Moss Rd (7-11)
- Pioneer Trail/Shepherds Rd (Americana)
- Pioneer Trail/Aspenwald Rd
- Pioneer Trail/Wildwood Ave
- Pioneer Trail/Sonora Ave
- Ski Run Blvd/Willow Ave
- Glenwood Way/Blackwood Rd (4181)
- Glenwood Way/Fawn (4191)
- Glenwood Way/Fawn
- Spruce Ave/Herbert Ave (Bijou Woods Apartments)
- Johnson Blvd/Fairway Dr (Safeway)
- Johnson Blvd/Marlette Circle (5019)
- Johnson Blvd/Marlette Circle (5020)
- Johnson Blvd/Al Tahoe Blvd (El Dorado County Sheriff/CSLT Police Dept)5121
- Tamarack Ave/Bowers Ave (4169)
- Tamarack Ave/Bowers Ave
- D St/Tata Ln
- Julie Ln/B St
- Julie Ln/Lake Tahoe Blvd
- Douglas County Community/Senior Center (Herbig Park)
- Washington/Plaza (near Federal Building and Bureau of Indian Affairs)
- SR 207/Market St
- Tramway Drive/Tina Court (in front of house)
- Tramway Dr/Bonnie Dr (Summit Village)
- Tramway Dr/Jack Dr
- Tramway Dr/Olympic Court (Ridge View)
- Tramway Dr/Milky Way Court
- Tramway Dr/Wells Fargo Ln (Worldmark)
- Tramway Dr/North Bowl Ln
- Tramway Dr/Jack Dr (Fox & Hound)
- Tramway Drive/Bonnie Dr (WorldMark-202 Tramway)
- Quaking Aspen Ln/Ridge Club Dr
- Quaking Aspen Ln/Galaxy Ln
- Quaking Aspen Ln (Tahoe Vacation Condos-261 Quaking Aspen)
- Quaking Aspen Ln/Tramway Dr
- Tramway Dr/SR 207
- SR 207/Foothill Rd. (Foothill Park and Ride)- EB
- Kimmerlang Rd/TIllman Ln (Tillman Center)
- Tillman Ln/Manahattan Way
- Tillman Ln/Topaz Ln
- SR 207/Foothill Rd (Foothill Park and Ride) -WB
- SR 207/Shady Lane
- SR 207/Kahle Dr
- Hwy 395/Eddy St (Cheshire Antiques)
- US 395 Northbound (Carson Valley Inn)
- Hwy 395/Ironwood Dr. Northbound
- Topsy Lane & Vista Grande Blvd. (near Walmart)
- Old Clear Creek Rd./Fuji Park (Costco)
- Cochise St./Overland Dr. (Liberty Dialysis)
- South Curry Street (Galaxy Theatres/Fandango Casino)
- Stewart St. (NDOT/DMV)
- Stewart St. between 2nd and 3rd St- NB
- Stewart St between 2nd and 3rd St-SB
- Stewart St (behind JoAnn Fabrics)
- Hwy 395/Ironwood Dr.-Southbound
- US 395 Southbound (Carson Valley Inn)
- Hwy 395/Gilman Ave. (Sharkey's)
- Sand Harbor Visitors Center
- Hwy 28 at Hidden Beach NB
- Hwy 28 at Tunnel Creek
- Hwy 28 at Raley's Shopping Center
- Incline Village (Old Elementary)
- Hwy 28 at US Bank
- Hwy 28 at Lakeshore Blvd.
- Hwy 28 at Hidden Beach SB
- Tahoe Blvd 76 Gas Station
- Tahoe Blvd Across From Wells Fargo
Over time
Overall score across the last 4 checks — unchanged since 2026-07-31.
Show the numbers
| Check | Score | Change |
|---|---|---|
| 2026-07-25 | 69.0 | first check |
| 2026-07-30 | 69.0 | no change |
| 2026-07-31 | 69.0 | no change |
| 2026-08-01 | 69.0 | 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
11 findings, ordered by severity.
Show every finding
- Warning132 instances
132 of 132 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)
- Warning127 instances
127 of 127 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)
- Warning12 instances
Some route lines list the same point twice in a row.
Repeated points don't hurt riders, but they can skew distance math and hint at a shaky export.
Fix: Turn on shape cleanup in your export tool, or drop the repeated points from shapes.txt. (Usually one export setting.)
Finding code: equal_shape_distance_same_coordinates · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning4 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)
- Warning4 instances
On some trips the stop distances run a little past the end of the route line.
The stop and shape distance values don't quite line up, so any math that uses them can drift.
Fix: Re-generate shape_dist_traveled on export so stop and shape distances use the same units. (Usually an export-tool fix, not hand editing.)
Finding code: trip_distance_exceeds_shape_distance_below_threshold · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning1 instance
feed_info.txt does not state when this feed starts and ends.
Without stated dates, apps can't warn anyone before your data goes stale; it just disappears one day.
Fix: Fill in feed_start_date and feed_end_date in feed_info.txt. (Two fields, likely set once in your export settings.)
Finding code: missing_feed_info_date · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning1 instance
Some files leave out fields that GTFS asks for but does not require.
Recommended fields like agency_phone or stop descriptions make the feed more useful to riders and trip planners.
Fix: Review the flagged fields and fill in the ones your riders would use. (A field at a time; not urgent.)
Finding code: missing_recommended_field · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning1 instance
feed_info.txt is missing its start/end dates
Apps and this scorecard can't warn anyone before the feed goes stale without stated validity dates.
Fix: Add feed_info.txt with feed_start_date and feed_end_date to your export. (Two fields, set once in export settings.)
Finding code: scorecard_missing_feed_info_dates · 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)
- Info3 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
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 (opens the validator rules on an external site)
NTD GTFS readiness Ready
Published at a public URL, valid, current, and identified with agency_id: the four feed checks for RY2026 all hold here. Only your own D-10 and P-50 filings make that official; this is a heads-up, not a determination.
- Published Ready
- Published at a public URL.
- Valid Ready
- Passes validation with no errors.
- Current Ready
- The published window is current, but its service end date is unusually distant; confirm that date is intentional.
- 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 132 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
- The published window is current, but its service end date is unusually distant; confirm that date is intentional.
- 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.
- 4 of 127 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 clears the four-week coverage window, but its service end date is unusually distant. Confirm that date is intentional before treating it as evidence of ongoing maintenance. 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.
- Correctness 77 / 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 85 / 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 Access needed to measure
- 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-transportation-district/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.