Emerald Bay Shuttle

What changed since the last check

• Correctness no change
• Freshness no change
• Rider experience no change

Top three things to fix

1. Re-export the feed with a calendar that reaches further out, and set feed_info feed_end_date past your next service change.

   Service data ended 267 day(s) ago. When the calendar runs out, trip planners stop showing this agency even though the buses are still running. Riders are told the service does not exist.

   Effort: Usually one export setting; export on a schedule so it never lapses again.

   Agencies here usually clear this within about 1 week (based on 18 observed fixes).

2. Set wheelchair_accessible on every trip (most small-agency fleets are 100% accessible, so this is often a single default).

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

   Effort: Often one default setting in your export.

   Agencies here usually clear this within about 1 week (based on 5 observed fixes).

3. Remove past service periods the next time you export the feed.

   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.

   Effort: One setting in most export tools.

   Agencies here usually clear this within about 1 week (based on 61 observed fixes).

Ready to send to the agency

Hi Emerald Bay Shuttle team, Service data ended 267 day(s) ago. When the calendar runs out, trip planners stop showing this agency even though the buses are still running. Riders are told the service does not exist. The fix is usually one export setting: Re-export the feed with a calendar that reaches further out, and set feed_info feed_end_date past your next service change. This came from your GTFS data quality scorecard, which checks the feed you publish and lists the fixes in plain language: https://gtfsscorecard.org/agency/keep-tahoe-blue/

Copy this note from the full scorecard.

NTD certification readiness: Not ready

Resolve this before you certify on the D-10. Service data expired 266 days ago, so FTA would find the link out of date.

Published Ready

Published at a public URL.

Valid Ready

Passes validation with no errors.

Current Not ready

Service data expired 266 days ago, so FTA would find the link out of date.

agency_id and NTD ID: Not checked yet. Setting your GTFS agency_id to your five-digit NTD ID is an optional way to line a feed up with its National Transit Database record. FTA links the two on your P-50 form, so it is not a required feed change. We don't have your NTD ID on file, so this is not checked yet.

The bar this score answers to

The published guideline in California is California Transit Data Guidelines. Caltrans' published quality guidelines and compliance checklist; this rubric is anchored to them.

Key facts

Feed URL

https://keeptahoeblue.sharepoint.com/sites/LeaguetoSaveLakeTahoe-CommunityEngagement/_layouts/15/guestaccess.aspx?share=EdcHnLwMfdJLscvyGDDa8FwB_bLXkpj9XIuG5GFiKdlKJw&e=1yNB6c&download=1

Last checked

2026-07-09

Service window

Feed has expired. Last service date 2025-10-15.

Feed version

3

State

California