Feed status · checked 2026-08-01
Nevada County Connects (Gold Country Stage)
Based on the feed this agency publishes
Service mode Bus
unchanged 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 72 minutes 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
Re-export the feed with a calendar that reaches further out, and set feed_info feed_end_date past your next service change.Likely your export tool
Service data ended 182 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.
⏱ Usually one export setting; export on a schedule so it never lapses again.worth about +100 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
200 of 200 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
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
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
- Service data ended 182 day(s) ago.
- Next action
- Re-export the feed with a calendar that reaches further out, and set feed_info feed_end_date past your next service 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
- Feed evidence
- 200 of 200 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
- Some stops exist in the feed but no trip ever stops at them.
- Next action
- Remove retired stops from the export, or add them back to the trips that should serve them.
- 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.
Re-export the feed with a calendar that reaches further out, and set feed_info feed_end_date past your next service change. · 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.
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.
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 was 182 days ago.
- Published accessibility data
- Accessibility information is stated for 92% 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.
Send the agency a note
Supporting this agency? Copy this and email it to them. It names what lapsed, why it matters to riders, and the one setting to change.
Score by category
The MobilityData validator flagged 6 kinds of issue across 35 instances (0 error, 32 warning, 3 informational).
Service data ended 182 day(s) ago. Trip planners have likely already dropped this feed.
92% of stops state wheelchair accessibility (92% marked accessible, 0% marked not accessible). This measures what the feed publishes, not whether a stop is physically usable. Fare data is published.
92% of stops state accessibility (92% 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 (1).
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.
208 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set ("Zion St across from Rankins Trailer Park", "Zion St across from Forest Charter School", "Zion St at SPD Market and Seven Hills Ctr", 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.
Fares are applied to trips.
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 251 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.
- AS (orange)
- 6 (purple)
- 5 (orange)
- 4 (brown)
- 3 (teal)
- 2 (teal)
- 1 (red)
- 7 (yellow)
| Route | Type | Line color |
|---|---|---|
| AS Grass Valley - Alta Sierra | Bus | orange |
| 6 Grass Valley - Penn Valley | Bus | purple |
| 5 Grass Valley - Auburn | Bus | orange |
| 4 Grass Valley Downtown - Brunswick Basin | Bus | brown |
| 3 Grass Valley | Bus | teal |
| 2 Grass Valley Downtown - Ridge Road | Bus | teal |
| 1 Nevada City - Grass Valley | Bus | red |
| 7 North San Juan | Bus | yellow |
List every stop
- Zion St across from Rankins Trailer Park
- Zion St across from Forest Charter School
- Zion St at SPD Market and Seven Hills Ctr
- Zion St at Rankins Trailer Park
- Zion St at Providence Mine Rd
- Zion St at Forest Charter School
- Zion St at SPD Market
- W McKnight Way at Papa Murphys
- GV Shopping Center, Kmart
- W Main St at Townsend
- W Main St at The Pines Motel
- W Main St at Sierra Mountain Inn across from Lyman Gilmore School
- W Main St across from Sierra Mountain Inn at Lyman Gilmore School
- W Main St at Charis Youth Center
- W Main St at Cemetery
- Whiting St at Crown Point Apts
- Whiting St at Church of Christ
- Whispering Pines Ln across from Miners Family Health Ctr
- Whispering Pines Ln across from 900 building
- Whispering Pines Ln across from 1415 building at Brunswick Rd
- Whispering Pines Ln at Unity Center
- Whispering Pines Ln at Clydesdale Ct
- Whispering Pines Ln at Miners Family Health Ctr
- Whispering Pines Ln at 900 building
- Whispering Pines Ln at 1415 building at Brunswick Rd
- Gold Country Vlg
- Tinloy St at Bank St
- Sutton Way at Plaza Dr and Sutton Cinemas
- Sutton Way at Olympia Garden Apts
- Sutton Way at Laura Wilcox Bldg and Oak Ridge Apts
- Hospitality House
- Gold Country Shopping Center Safeway
- Sutton Way at Glenbrook Ctr
- Sutton Way at Glenbrook Apts
- Squirrel Creek Rd across from Margaret G. Scotten School
- Squirrel Creek Rd at Old Dairy Pl
- Squirrel Creek Rd at Oak St Market
- Squirrel Creek Rd at Margaret G. Scotten School
- Squirrel Creek Rd at Crestwood St
- Hwy 49 at Welsh Ln (mailboxes)
- Hwy 49 at Dry Creek Rd at Tuff Shed
- Hwy 49 at Travertine Ct
- Hwy 49 at Streeter Rd
- Hwy 49 at Running M Dr
- Hwy 49 at Rock Creek Mobile Home Park
- Hwy 49 at Quartz Dr
- Hwy 49 at Pekolee Dr
- Hwy 49 at Oakhurst Dr
- Hwy 49 at N Bloomfield-Graniteville Rd
- Manzanita Ave at Mt Air Mobile Park
- Hwy 49 at Macy Pl
- Hwy 49 at Lorenson Rd
- Hwy 49 at Lone Star Rd
- Hwy 49 at Linnet Ln
- Hwy 49 at Gautier Dr
- Forest Springs Dr at Forest Springs Mobilehome Community
- Hwy 49 at Florence Ln
- Hwy 49 at Featherlite Trailers
- Hwy 49 at Dry Creek Rd at Arco
- Hwy 49 at Dana Ct
- Hwy 49 at Coyote St
- Hwy 49 at Clivus Dr
- Hwy 49 at Bethel Church
- Hwy 49 at Cherry Creek Rd
- Hughes Rd at Sierra Cinemas
- Rockwood Dr at Hughes Rd
- Hughes Rd at Lidster Ave
- High St at Neal St
- Higgins Rd at Higgins Village
- Helling Way at Madelyn Helling Library
- SNM Building #1 Hospital
- SNM Building #4 Hospital
- Peer Resource
- Pine Creek Shopping Ctr, Raleys
- Freeman Ln at Wolf Creek Trail
- Freeman Ln at Grass Valley Municipal Facilities
- E Main St across from Humpty Dumpty Kitchen
- E Main St at Professional Bldg
- E Main St at W Berryhill Dr
- E Main St at The Fairway Bldg
- E Main St at Main St Professional Ctr
- E Main St at Idaho-Maryland Rd
- E Main St at Humpty Dumpty Kitchen
- City Hall
- E Main St at Eureka St
- E Main St at E Berryhill Dr
- Squirrel Creek Rd at Cedar Ave
- Sierra College Dr across from 400 Medical Building
- Sierra College Dr at Litton Trail
- Sierra College Dr across from 380 Medical Building
- 400 Sierra College Dr
- Sierra College Dr at Rotary Fields
- Sierra College Dr at Fire Dept Sta 2
- Granite Wellness
- Sierra College Dr at Chapa De Clinic
- Sierra College Dr at BriarPatch Co-op
- 380 Sierra College Dr
- S Auburn St at Stacey Ln
- S Auburn St at Race St
- S Auburn St at Mainhart Dr
- S Auburn St at Adams Ln
- Sacramento St at Zion St
- Sacramento St across from S Pine St at Tour of Nevada City Bicycle Shop
- Sacramento St across from Railroad Ave
- Sacramento St at Adams St
- Rough and Ready Hwy across from West Dr
- Rough and Ready Hwy across from Randolph Ln
- Rough and Ready Hwy across from Ironclad Rd
- Rough and Ready Hwy across from East Dr
- Rough and Ready Hwy across from Bitney Springs Rd
- Rough and Ready Hwy at West Dr
- Rough and Ready Hwy at Valley Rd
- Rough and Ready Hwy at Twin Cities Church
- Rough and Ready Hwy at S Ponderosa Way
- Rough and Ready Hwy at Rough and Ready Rd
- Rough and Ready Hwy at Ridge Rd
- Rough and Ready Hwy at Randolph Ln
- Rough and Ready Hwy at N Ponderosa Way
- Rough and Ready Hwy at Ironclad Rd
- Rough and Ready Hwy at Grubstake Trl
- Rough and Ready Hwy at Fire Station
- Rough and Ready Hwy at East Dr
- Rough and Ready Hwy at Post Office
- Rough and Ready Hwy at Bitney Springs Rd
- Rough and Ready Hwy at Animal Clinic
- Rough and Ready Hwy at Adam Ave
- Sierra College
- Ridge Rd across from Slate Creek Rd
- Ridge Rd across from Ridge Feed
- Ridge Rd across from Hughes Rd
- Ridge Rd at Ventana Sierra Dr across from Nevada Union High School
- Ridge Rd at Slate Creek Rd
- Ridge Rd at Ridge Feed
- Ridge Rd at Morgan Ranch Dr
- Ridge Rd at Hughes Rd
- Railroad Ave at Idaho Maryland Rd
- Professional Dr at Fortune Ct
- Pleasant St across from Dalton St
- Pleasant St at Walsh St
- Wildwood Ctr
- Pleasant Valley Rd at Hwy 20 at Park and Ride
- Pleasant Valley Rd at Donovan Rd
- Commercial St across from Gas Station
- Pleasant Valley Rd at Branding Iron Rd
- Pleasant Valley Rd at Black Forest Rd
- Pleasant Valley Rd at Biladeau Ln
- Penn Valley Dr across from Broken Oak Ct
- Penn Valley Dr at Willowbrook Rd
- Penn Valley Dr at Western Gateway Park
- Penn Valley Dr at Valley Oak Ct
- Penn Valley Dr at Tack Room
- Penn Valley Dr at Spenceville Rd
- Penn Valley Dr at Spenceville Rd (Northridge Pizza)
- Penn Valley Dr at Hwy 20 at Quincy Ln
- Penn Valley Dr at Horton St
- Penn Valley Dr at Easy St
- Penn Valley Dr at Clover Rd
- Penn Valley Dr at Broken Oak Ct
- Old Tunnel Rd at Nevada City Senior Apts
- Western Sierra Medical Center
- Old Tunnel Rd at Bank of the West
- New Mohawk Rd across from Gold Flat Ct
- Nevada City Hwy across from Hubbard Rd
- Nevada City Hwy across from Fowler Ctr
- Nevada St at Willow Valley Rd
- Nevada Way at Social Security Administration
- Nevada City Hwy at Skewes Ln
- Nevada City Hwy at Narrow Gauge Ln
- Nevada City Hwy at Hubbard Rd
- Nevada City Hwy at Gold Flat Rd
- Nevada City Hwy at Glenwood Dr
- Nevada City HWY at Fowler Ctr
- Nevada St at Enterprise Dr at US Post Office
- Nevada City Hwy at Banner Lava Cap Rd
- Nevada St at Amtrak Station
- McCourtney Rd across from Auburn Rd at Fairgrounds Gate 3
- McCourtney Rd at Allison Ranch Rd
- Maidu Ave at Eric Rood Government Center
- Loma Rica Drive across from Pride Industries
- Loma Rica Dr at Transportation Yard
- Loma Rica Drive at Pride Industries
- Loma Rica Dr at Nevada City Ave
- Little Valley Rd at Grass Valley Mobilehome Village
- Litton Dr at Litton Building
- Little Valley Rd at Forever Flowering
- Litton Dr
- John Bauer Ave at Gold Country Stage Transit
- Joerschke Dr across from Maltman Dr
- Joerschke Dr at Valley Commons
- Hwy 49 across from Edgewood Rd across from Social Security Administration
- Drive-In Way at Atwood Rd at Umpqua Bank across from park and ride
- Dorsey Dr across from Springhill Gardens Apts
- Dorsey Dr across from Senior Apts
- Dorsey Dr across from Grass Valley Terrace Apts
- Dorsey Dr across from Crystal Ridge Care Ctr
- Dorsey Dr at Springhill Gardens Apts
- Dorsey Dr at Senior Apts
- Dorsey Dr at Segsworth Way
- Dorsey Dr at Grass Valley Terrace Apts
- Dorsey Dr at Sutton Way
- Dorsey Dr At Catherine
- Crown Point Cir across from 333 building
- Crown Point Cir at Nevada County Behavioral Health
- Crown Point Cir at Crown Point Ct
- Crown Point Cir at driveway of Behavioral Health
- Crown Point Cir at Maeir Manufacturing
- Coyote St at Washington St
- Combie Rd at Lake Ctr
- Colfax Ave Hwy 174 at Grass Valley Glass
- Colfax Ave Hwy 174 Prosperity Lanes
- Colfax Ave at Ophir St, Bottle Shop
- Church St at Neal St
- Butler St at Penstock Dr
- Broad St at Union St and Hwy 20-49 Bridge
- Broad St at Chief Kelly Dr
- Broad St at Bennett St
- Brighton St at Packard Dr
- Brighton St at Minnie Park
- Brighton St at Fawcett St
- Brighton St at Fairgrounds Gate 8
- Bennett St at Ophir St
- Alta St at Express Mart
- Alta St across from Devere Mautino Park
- Alta St at Ridge Rd
- Alta Sierra Dr at Little Valley Road
- Alta St at Linden Ave
- Alta Sierra at Johnson Pl
- Alta St at Ivy St
- Alta St at Salvation Army
- Alta St at Devere Mautino Park
- Alta St at Country Preschool
- Glenbrook Shopping Ctr (Westbound)
- Nevada Union High School
- Highway 49 at Tyler Foote Road
- North San Juan Post Office
- Oak Tree Rd at Tyler Foote Rd
- Sierra Family Medical Clinic
- North Columbia Cultural Center
- Ananda Village
- South Yuba River
- Resource Center at Library
- North San Juan Community Center
- Oak Tree Rd at Tyler Foote Rd
- North San Juan Post Office
- Highway 49 at Tyler Foote Road
- South Yuba River
- Broad Street @ City Hall
- Glenbrook Shopping Ctr
- 12350 La Barr Meadows Rd
- SNM Building #3 Hospital
- and 1 more (see the full list on the map or in the GeoJSON)
Over time
Overall score across the last 4 checks — unchanged since 2026-07-31.
Show the numbers
| Check | Score | Change |
|---|---|---|
| 2026-07-25 | 61.4 | first check |
| 2026-07-30 | 61.4 | no change |
| 2026-07-31 | 61.4 | no change |
| 2026-08-01 | 61.4 | 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
9 findings, ordered by severity.
Show every finding
- Error1 instance
Service data ended 182 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.
Fix: Re-export the feed with a calendar that reaches further out, and set feed_info feed_end_date past your next service change. (Usually one export setting; export on a schedule so it never lapses again.)
Finding code: scorecard_feed_expired · Read the fix guide · See GTFS Best Practices (opens GTFS Best Practices on an external site)
- Warning200 instances
200 of 200 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)
- Warning28 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)
- Warning20 instances
20 of 251 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)
- Warning2 instances
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
This feed's service calendar runs out within the next 7 days.
When the calendar ends, Google Maps and other trip planners drop your agency entirely. Riders see no service at all.
Fix: Export and publish an updated GTFS feed that covers at least the next 30 days of service. (Usually a re-export from your scheduling software.)
Finding code: feed_expiration_date7_days · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning1 instance
Many of the feed's trips don't run at all in the next 7 days.
It usually means old service periods are still in the export, making the feed bigger and harder to check.
Fix: Trim past service periods the next time you export. (One setting in most export tools.)
Finding code: trip_coverage_not_active_for_next7_days · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- 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 · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Info1 instance
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)
NTD GTFS readiness Not ready
Resolve this before you certify on the D-10. Service data expired 182 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 182 days ago, so FTA would find the link out of date.
- 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 200 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. Service data expired 182 days ago. States wheelchair access on 92% of stops and 0% of trips; the mark needs 90% of each.
- Valid Met
- Passes validation with no errors.
- Current Not yet
- Service data expired 182 days ago.
- Accessible Not yet
- States wheelchair access on 92% 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.
- 28 of 251 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.
Below the Google and Apple Maps four-week coverage bar. This feed's last day of service has passed, so Google and Apple Maps will stop showing your agency. Re-export with a calendar that covers at least the next four weeks.
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 92% of stops and 0% of trips.
- Meets shapes.txt with a shape for every trip
All 200 trips have a shape in shapes.txt.
- Meets Fare data published, or the service marked fare-free
Fare data is published.
- Correctness 81 / 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 0 / 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 83 / 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.
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/nevada-county-connects-gold-country-stage/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.