Feed status · checked 2026-08-01
Elk Grove Transit
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.2, validator 8.0.1.
Checked for changes 3 hours ago; last changed 2 days ago.
Measured 3 of 4 score categories from the Mobility Database's mirror copy of the feed.
How we measured this
Confidence in this measurement: provisional.
- Realtime quality was not measured this run. It does not count against the grade.
- The agency's own feed URL was unreachable, so the Mobility Database's hosted mirror copy was scored instead.
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 573 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_boarding to 1 (accessible) or 2 (not accessible) for every stop. A field survey can start with the busiest stops.Likely your team
460 of 460 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
338 of 338 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
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 573 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
- 460 of 460 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
- 338 of 338 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.
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. Make this change in whatever tool produces your feed, then re-export.
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_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. Make this change in whatever tool produces your feed, then re-export.
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. Make this change in whatever tool produces your feed, then re-export.
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 573 days ago.
- 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 your vendor a fix request
You may not control the GTFS export yourself. Copy this and send it to whoever runs your scheduling software export. It names each fix with 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 10 kinds of issue across 105 instances (0 error, 102 warning, 3 informational).
Service data ended 573 day(s) ago. Trip planners have likely already dropped this feed.
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
16 route badge(s) pair a color and text color below the WCAG 4.5:1 contrast bar (110, 111, 112, 114, 115, and more).
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.
456 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set ("Laguna Springs & West Stockton (NB)", "Big Horn & Laguna Blvd. (NB)", "Big Horn & Kaiser Entrance (NB)", 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 460 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.
- 110 (red)
- 111 (teal)
- 112 (green)
- 113 (pink)
- 114 (yellow)
- 115 (white)
- 116 (brown)
- 10 (pink)
- 11 (yellow)
- 12 (gray)
- 13 (teal)
- 14 (white)
- 15 (teal)
- 16 (gray)
- 17 (pink)
- 18 (pink)
- 19 (pink)
| Route | Type | Line color |
|---|---|---|
| 110 Route 110 | Bus | red |
| 111 Route 111 | Bus | teal |
| 112 Route 112 | Bus | green |
| 113 Route 113 | Bus | pink |
| 114 Route 114 | Bus | yellow |
| 115 Route 115 | Bus | white |
| 116 Route 116 | Bus | brown |
| 10 Route 10 | Bus | pink |
| 11 Route 11 | Bus | yellow |
| 12 Route 12 | Bus | gray |
| 13 Route 13 | Bus | teal |
| 14 Route 14 | Bus | white |
| 15 Route 15 | Bus | teal |
| 16 Route 16 | Bus | gray |
| 17 Route 17 | Bus | pink |
| 18 Route 18 | Bus | pink |
| 19 Route 19 | Bus | pink |
List every stop
- Laguna Springs & West Stockton (NB)
- Big Horn & Laguna Blvd. (NB)
- Big Horn & Kaiser Entrance (NB)
- Big Horn & New Country (NB)
- Big Horn & Arborview (NB)
- Big Horn & Laguna Star (NB)
- Laguna Blvd. & Dwight Rd. (NB)
- Laguna Blvd. & Laguna Main St. (NB)
- Laguna Blvd. & Harbour Point Dr. (NB)
- Q St. & 8th St. (NB)
- 8th St. & P St. (NB)
- 8th St. & O St. (NB)
- 8th St. & N St. (NB)
- 8th St. & Capitol Mall (NB)
- 8th St. & K St. (NB)
- Bruceville & Elk Grove Blvd. (NB)
- Bruceville & Soaring Oaks (NB)
- Bruceville & Soaring Oaks (NB)
- Bruceville & Laguna Blvd. (NB)
- Bruceville & Laguna Blvd. (NB)
- Bruceville & Di Lusso (NB)
- Bruceville & Sheldon (NB)
- Bruceville & Damascas (NB)
- Bruceville & Jacinto (NB)
- Bruceville & Calvine (NB)
- Bruceville & College Entrance (SB)
- Bruceville & Calvine (SB)
- Bruceville & Jacinto (SB)
- Bruceville & Damascas (SB)
- Bruceville & Center PKWY (SB)
- Bruceville & Center PKWY (SB)
- Bruceville & Big Horn (SB)
- Bruceville & Di Lusso (SB)
- Bruceville & Laguna Blvd. (SB)
- Bruceville & Seasons (SB)
- Bruceville & Beaver Falls (SB)
- Bruceville & Kilconnell (SB)
- Elk Grove Blvd. & Bruceville (SB)
- Elk Grove Blvd. & Big Horn (SB)
- Elk Grove Blvd. & Laguna Springs (SB)
- Promenade Pkwy at Kaiser (NB)
- Big Horn Blvd at Whitelock Pkwy
- Big Horn Blvd at Lotz Pkwy
- Big Horn Blvd at Civic Center Dr
- Big Horn Blvd at Elk Grove Blvd
- Big Horn & Village Tree (NB)
- Big Horn & Monetta (NB)
- Big Horn Blvd at Laguna Blvd
- Lewis Stein & Big Horn (NB)
- Lewis Stein & West Stockton (NB)
- Sheldon & Lewis Stein (WB)
- Sheldon & West Wing (WB)
- Sheldon Rd at Bruceville Rd
- Cosumnes River LRT
- Lewis Stein & Sheldon (SB)
- Lewis Stein Rd at W. Stockton Blvd
- Big Horn & Ancestor (EB)
- Big Horn Blvd at New Country Ct
- Big Horn Blvd at Generations Dr
- Big Horn & Monetta (SB)
- Big Horn & Village Tree (SB)
- Big Horn Blvd at Red Elk Dr
- Big Horn & Elk Grove Blvd (SB)
- Big Horn & Civic Center (SB)
- Big Horn Blvd at Denali Cir
- Big Horn Blvd at Whitelock Pkwy
- Whitelock at Big Horn Blvd
- Vaux & Laguna Main (WB)
- Laguna Blvd & Apple Computer (WB)
- Harbour Point & Laguna Blvd (SB)
- Harbour Point Dr at Longport Ct
- Harbour Point & Buckminster (SB)
- Harbour Point & Bastona (SB)
- Harbour Point & Galen (SB)
- Harbour Point & Maritime (SB)
- Harbour Point & Maritime (SB)
- Harbour Point Dr. at Elk Grove Blvd
- Elk Grove Blvd at W Taron Dr
- Elk Grove Blvd & Waterfowl (EB)
- Elk Grove Blvd & Stonelake Club Dr (EB)
- Elk Grove Blvd & East Taron (EB)
- Elk Grove Blvd & Shore Lake Dr (EB)
- Elk Grove Blvd & Four Winds Dr (EB)
- Elk Grove Blvd & Franklin (EB)
- Elk Grove Blvd & Orchard Valley (EB)
- Fire Poppy & Vineland (SB)
- Fire Poppy & Iris Meadow (SB)
- Fire Poppy & Fox Trotter (SB)
- Fire Poppy & Blossom Ranch (SB)
- Bellaterra & Fire Poppy (WB)
- Bellaterra & Gold Poppy (WB)
- Whitelock Pkwy & Bellaterra (EB)
- Whitelock Pkwy & Atkins (EB)
- Whitelock Pkwy & Shana (EB)
- Franklin High Rd at Whitelock Pkwy
- Franklin High Rd at Hewitt Wy
- Franklin High Rd at McLean Dr
- Franklin High Rd at Coop Dr
- Stathos Dr at Jillson Wy
- Bruceville & Bilby (NB)
- Whitelock Pkwy & Bruceville (EB)
- Whitelock Pkwy & Ped Crosswalk (EB)
- Whitelock Pkwy & Big Horn (WB)
- Whitelock Pkwy & Ped Crosswalk (WB)
- Bruceville & Whitelock Pkwy (SB)
- Bruceville & Quail Run (SB)
- Bilby Rd at Bruceville Rd
- Stathos Dr at Jillson Wy
- Franklin High Rd & Coop (NB)
- Franklin High Rd & Jefjen (NB)
- Franklin High Rd & Hewitt (NB)
- Franklin High Rd at Whitelock Pkwy (Library)
- Whitelock Pkwy & Franklin High Rd (WB)
- Bellaterra & Whitelock Pkwy (NB)
- Bellaterra Dr at Gold Poppy Wy
- Fire Poppy & Bellaterra (NB)
- Fire Poppy & Blossom Ranch (NB)
- Fire Poppy & Summer Glen (NB)
- Fire Poppy & Spring Flower (NB)
- Fire Poppy Dr at Elk Grove Blvd
- Elk Grove Blvd & Franklin (WB)
- Elk Grove Blvd & Four Winds Dr (WB)
- Elk Grove Blvd & Shore Lake Dr (WB)
- Elk Grove Blvd & East Taron (WB)
- Elk Grove Blvd & Stonelake Club Dr (WB)
- Harbour Point & Elk Grove Blvd (NB)
- Harbour Point & Maritime (NB)
- Harbour Point & Granite Park (NB)
- Harbour Point & Galen (NB)
- Harbour Point & Buckminster (NB)
- Harbour Point & Renwick (NB)
- Laguna Blvd & Harbour Point (EB)
- Laguna Blvd & Laguna Main (EB)
- Big Horn & Red Elk (NB)
- Laguna Blvd & Babson Dr (EB)
- Laguna Blvd & Neosho (EB)
- Franklin Blvd at Laguna Blvd
- Franklin Blvd at Millstone Dr
- Franklin Blvd at Elliot Ranch Rd
- Franklin & Castleview (SB)
- Franklin Blvd at Castleview Dr
- Elk Grove Blvd & Fire Poppy (EB)
- Elk Grove Blvd & Cresleigh (EB)
- Cresleigh Pkwy at Harvest Park Dr
- Cresleigh & Orchard View (SB)
- Cresleigh & Orchard View (SB)
- Cresleigh Pkwy at Harvest Park Dr
- Allessandria & Bellaterra (SB)
- Bellaterra Dr at Rosanna Dr
- Terrazzo Dr at Bellaterra Dr
- Bruceville & Del Webb (NB)
- Bruceville & Barcella (NB)
- Civic Center Dr at Wymark Dr
- Civic Center Dr at Wymark Dr
- Bruceville & Ackley (SB)
- Terrazzo Dr at Bruceville Rd
- Bellaterra Dr at Terrazzo Wy
- Bellaterra Dr at Brinzino Ct
- Allessandria & Bellaterra (NB)
- Cresleigh Pkwy at Harvest Park Dr
- Cresleigh Pkwy at Radmere Dr
- Cresleigh Pwky at Blue Poppy Dr
- Cresleigh & Harvest Park (NB)
- Elk Grove Blvd & Foulks Ranch (WB)
- Elk Grove Blvd & Fire Poppy (WB)
- Franklin Blvd at Elk Grove Blvd
- Franklin & Saint Augustine (NB)
- Franklin & Laguna Woods (NB)
- Franklin & Laguna Blvd (NB)
- Laguna Blvd & Franklin (WB)
- Laguna Blvd & Santorini Dr (WB)
- Laguna Blvd & Dwight Rd (WB)
- Laguna Blvd & Franklin (EB)
- Laguna Blvd & Laguna Oaks (EB)
- Laguna Blvd & Laguna Park (EB)
- Laguna Blvd & Old Creek (EB)
- Laguna Blvd & Laguna Park (EB)
- Laguna Blvd & Bruceville (EB)
- Laguna Blvd & Trenholm (EB)
- Laguna Blvd & Big Horn (EB)
- Laguna Blvd & Elk Grove Creekbridge (EB)
- Laguna Springs & Laguna Blvd (SB)
- Laguna Springs & West Stockton (SB)
- Laguna Palms Wy. at Laguna Springs Dr. (City Hall)
- Bond & East Stockton Blvd (EB)
- Bond & Elk Crest (EB)
- Bond & Emerald Crest (EB)
- Bond Rd at Egret Dr
- Bond & Terra Linda (EB)
- Bond & Terra Linda (EB)
- Bond Rd. at Elk Grove-Florin Rd.
- Bond Rd at Elk Grove-Florin Rd
- Elk Grove-Florin Rd at Laguna Creek Bridge
- Elk Grove Florin & Halverson (SB)
- Elk Grove Florin & Kelsey (SB)
- Elk Grove Florin & 2nd Ave (SB)
- Elk Grove Florin & Kerr Middle School (SB)
- Elk Grove-Florin Rd at Elk Grove Blvd
- Elk Grove-Florin Rd at Across Emerald Park
- Elk Grove Florin & Cadura Circle (SB)
- Elk Grove Florin & Elk Grove High School (SB)
- Elk Grove Florin & Lismore (SB)
- Elk Grove-Florin Rd at Across Park Meadows
- Elk Grove Florin & Across Castle Park (SB)
- Elk Grove Florin & East Stockton Blvd (SB)
- East Stockton Blvd & Hampton Oak (SB)
- Hampton Oak & East Valley Dr (EB)
- Hampton Oak & Belcourt (EB)
- Hampton Oak & Westpark (EB)
- Hampton Oak & Canyon View (EB)
- Iron Rock Way & Hampton Oak (SB)
- Iron Rock Way & Union (SB)
- Elkmont & Iron Rock Way (WB)
- East Stockton Blvd & Elkmont (NB)
- East Stockton Blvd & Hampton Oak (NB)
- Elk Grove-Florin Rd at Carmel Valley Wy
- Elk Grove-Florin at Park Meadow
- Elk Grove-Florin Rd at Park Wy
- Elk Grove Florin & Lismore (NB)
- Elk Grove Florin & Tralee (NB)
- Elk Grove Florin & Plaza Park Dr (NB)
- Elk Grove Florin & Emerald Park (NB)
- Elk Grove Florin & Elk Grove Blvd (NB)
- Elk Grove Florin & 2nd Ave (NB)
- Elk Grove Florin & La Haya (NB)
- Elk Grove Florin & Aizenberg Circle (NB)
- Elk Grove Florin & Vintage Oaks Apartments (NB)
- Bond & Elk Grove Florin (WB)
- Bond & Terra Linda (WB)
- Bond & Mosquito Vector Control (WB)
- Bond & Emerald Crest (WB)
- Bond & Elk Crest (WB)
- Bond Rd at East Stockton Blvd
- Laguna Blvd & West Stockton (WB)
- Laguna Blvd & Laguna Creek Bridge (WB)
- Laguna Blvd & Big Horn (WB)
- Laguna Blvd & Trenholm (WB)
- Laguna Blvd & Bruceville (WB)
- Laguna Blvd & Di Lusso (WB)
- Laguna Blvd & Old Creek (WB)
- Laguna Blvd & Laguna Park (WB)
- Laguna Blvd & Laguna Manor (WB)
- Laguna Blvd & Laguna Crest (WB)
- Franklin Blvd & Laguna Blvd (NB)
- Franklin & Tegan (NB)
- Franklin & Laguna Park (NB)
- Big Horn & Franklin (EB)
- Big Horn Blvd at Amber Creek Dr
- Big Horn Blvd at Meadowspring Dr
- Big Horn Blvd at Meadowspring Dr
- and 210 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 | 39.2 | first check |
| 2026-07-30 | 39.2 | no change |
| 2026-07-31 | 39.2 | no change |
| 2026-08-01 | 39.2 | no change |
What changed since your last check
- Correctness no change
- Freshness no change
- Rider experience no change
Everything we checked
14 findings, ordered by severity.
Show every finding
- Error1 instance
Service data ended 573 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)
- Warning460 instances
460 of 460 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)
- Warning338 instances
338 of 338 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)
- Warning69 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)
- Warning16 instances
Same name and description for route (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'same_name_and_description_for_route' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Finding code: same_name_and_description_for_route · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning5 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)
- Warning3 instances
Some values have extra spaces at the start or end.
A stray space can break a match, so a stop or route may fail to link across files.
Fix: Trim leading and trailing spaces on export. The scorecard's auto-fixed copy already does this. (Usually one export setting.)
Finding code: leading_or_trailing_whitespaces · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- 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 (opens the validator rules 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)
- Warning2 instances
Some rider-facing names are in ALL CAPS or all lowercase.
ALL-CAPS stop and headsign names are harder to read in apps and are read awkwardly by screen readers.
Fix: Use mixed case for stop names and headsigns (e.g. 'Main St & 2nd Ave', not 'MAIN ST & 2ND AVE'). (Often a bulk fix in your scheduling software.)
Finding code: mixed_case_recommended_field · 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)
- 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)
NTD GTFS readiness Not ready
Resolve this before you certify on the D-10. Service data expired 573 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 573 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 338 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 573 days ago. 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 Not yet
- Service data expired 573 days ago.
- 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.
- 5 of 460 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 (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 338 trips have a shape in shapes.txt.
- Gap Fare data published, or the service marked fare-free
No fare data is published.
- Correctness 58 / 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 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/elk-grove-transit/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.