Feed status · checked 2026-08-01
Livermore Amador Valley Transit Authority
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 74 minutes ago; last fetch returned HTTP 404.
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 93 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
Check the flagged stops' shape_dist_traveled against the route shape, and re-generate it on export if they disagree.Likely your export tool
Some stops sit far from the route line, going by the feed's own distance values. Trip planners may draw the route down the wrong streets or point riders to the wrong corner.
⏱ Usually an export-tool fix, not hand editing.worth about +6 points in its category
Remove past service periods the next time you export the feed.Likely your export tool
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.
⏱ One setting in most export tools.worth about +6 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 93 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
- Some stops sit far from the route line, going by the feed's own distance values.
- Next action
- Check the flagged stops' shape_dist_traveled against the route shape, and re-generate it on export if they disagree.
- 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 service calendars in the feed have already ended.
- Next action
- Remove past service periods the next time you export the feed.
- 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.
Check the flagged stops' shape_dist_traveled against the route shape, and re-generate it on export if they disagree. · 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.
Remove past service periods the next time you export the feed. · 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 93 days ago.
- Published accessibility data
- Accessibility information is stated for 100% of stops and 100% 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 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 8 kinds of issue across 70 instances (0 error, 57 warning, 13 informational).
Service data ended 93 day(s) ago. Trip planners have likely already dropped this feed.
100% of stops state wheelchair accessibility (1% marked accessible, 99% marked not accessible). This measures what the feed publishes, not whether a stop is physically usable. Fare data is published.
100% of stops state accessibility (1% marked accessible). Reflects what the feed states, not verified physical usability.
2 accessibility depth signals
23 route badge(s) pair a color and text color below the WCAG 4.5:1 contrast bar (10R, 18, 2, 201, 20X, 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.
655 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set ("Springtown Blvd & Bluebell Dr", "Dalton Ave & N Vasco Rd", "Junction Ave & Chestnut St WB", 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.
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 665 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.
- 1 (purple)
- 10R (red)
- 11 (black)
- 14 (purple)
- 15 (teal)
- 18 (orange)
- 2 (green)
- 201 (red)
- 20X (pink)
- 3 (teal)
- 30R (green)
- 4 (green)
- 501 (red)
- 502 (red)
- 503 (red)
- 504 (red)
- 53 (blue)
- 54 (brown)
- 580X (blue)
- 601 (red)
- 602 (red)
- 603 (red)
- 604 (red)
- 605 (red)
- 606 (red)
- 607 (red)
- 608 (red)
- 609 (red)
- 610 (red)
- 611 (red)
- 70X (green)
- 8 (red)
| Route | Type | Line color |
|---|---|---|
| 1 Gleason/Hacienda | Bus | purple |
| 10R Pleasanton - Livermore via Stanley | Bus | red |
| 11 Greenville | Bus | black |
| 14 Pleasanton - Livermore via Outlets | Bus | purple |
| 15 Springtown | Bus | teal |
| 18 Granada | Bus | orange |
| 2 East Dublin | Bus | green |
| 201 Emerald High | Bus | red |
| 20X Vasco | Bus | pink |
| 3 Stoneridge | Bus | teal |
| 30R Dublin - Livermore via College | Bus | green |
| 4 Central Dublin | Bus | green |
| 501 Positano Hill | Bus | red |
| 502 Emerald Glen | Bus | red |
| 503 Shannon Park | Bus | red |
| 504 Dublin Ranch | Bus | red |
| 53 Stoneridge | Bus | blue |
| 54 Hacienda | Bus | brown |
| 580X Airway | Bus | blue |
| 601 Ruby Hill | Bus | red |
| 602 Del Prado Park | Bus | red |
| 603 Muirwood Park | Bus | red |
| 604 Fairlands | Bus | red |
| 605 Fairlands | Bus | red |
| 606 Vintage Hills | Bus | red |
| 607 Laguna Oaks | Bus | red |
| 608 Amaral Park | Bus | red |
| 609 Del Prado Park | Bus | red |
| 610 Fairlands | Bus | red |
| 611 Ruby Hill | Bus | red |
| 70X Pleasant Hill | Bus | green |
| 8 Hopyard | Bus | red |
List every stop
- Airway Park & Ride
- Murrieta Blvd & Olivina Ave NB
- Murrieta Blvd & Pine St NB
- Murrieta Blvd & Huron Rd
- Murrieta Blvd & Portola Ave NB
- E Airway Blvd & Portola Ave
- Rutan Dr & Rickenbacker Pl SB
- Portola Ave & Campus Hill Dr
- N Canyons Pkwy & Constitution Dr EB
- N Canyons Pkwy & Independence Dr EB
- N Canyons Pkwy & Triad Dr
- Las Positas College
- N Canyons Pkwy & Triad Pl
- N Canyons Pkwy & Independence Dr WB
- N Canyons Pkwy & Constitution Dr WB
- Portola Ave & Tranquility Cir
- Rutan Dr & Rickenbacker Pl NB
- E Airway Blvd & Sutter St
- E Airway Blvd & Via Montalvo
- Murrieta Blvd & Portola Ave SB
- Murrieta Blvd & Del Norte Dr
- Murrieta Blvd & Pine St SB
- Murrieta Blvd & Olivina Ave SB
- Olivina Ave & Adelle St WB
- Olivina Ave & Rincon Ave
- Olivina Ave & Murrieta Blvd WB
- Rutan Dr & Sonic Ave
- Rutan Dr & E Airway Blvd
- W Jack London Blvd & Outlets WB
- W Jack London Blvd & Outlets EB
- W Jack London Blvd & Discovery Dr
- E Jack London Blvd & Hagemann Dr WB
- W Jack London Blvd & Voyager St
- W Jack London Blvd & Wolf House Dr WB
- W Jack London Blvd & Wolf House Dr EB
- E Jack London Blvd & Arlington Rd EB
- E Jack London Blvd & Turino St
- E Jack London Blvd & Troy St
- E Jack London Blvd & Murrieta Blvd
- E Jack London Blvd & Arlington Rd WB
- Olivina Ave & Murrieta Blvd EB
- Olivina Ave & Albatross Ave
- Olivina Ave & Adelle St EB
- E Jack London Blvd & Hagemann Dr EB
- Las Positas Rd & S Vasco Rd WB
- S Vasco Rd & Las Positas Rd NB
- S Vasco Rd & Las Positas Rd SB
- S Vasco Rd & Brisa St SB
- First St & Larch Ln EB
- First St & Portola Ave
- First St & Trevarno Rd
- First St & N Mines Rd EB
- Springtown Blvd & Bluebell Dr
- Springtown Blvd & Poppy Wy
- Springtown Blvd & Oleander St
- Springtown Blvd & Rhododendron Dr
- Galloway St & Bluebell Dr
- Bluebell Dr & Marlin A. Pound Park
- Bluebell Dr & Capriconus Ave
- Scenic Ave & Aquarius St
- Scenic Ave & Heather Ln
- Broadmoor St & Greenwich Ave
- Broadmoor St & Bridgeport Cir
- Broadmoor St & Haggin Oaks Ave
- Dalton Ave & N Vasco Rd
- Scenic Ave & N Vasco Rd
- Scenic Ave & Croce Elementary School
- Scenic Ave & Broadmoor St
- Heather Ln & Iris Wy
- Bluebell Dr & Heather Ln
- Bluebell Dr & Sunflower Ct
- Bluebell Dr & Las Flores Rd
- First St & Las Positas Rd
- First St & N Mines Rd WB
- First St & Larch Ln WB
- Maple St & Livermore High School
- Junction Ave & Chestnut St WB
- N Livermore Ave & Cromwell Wy NB
- N Livermore Ave & Las Positas Rd
- Las Positas Rd & First St EB
- Las Positas Rd & First St WB
- Las Positas Rd & Plaza 580
- Las Positas Rd & Arroyo Plaza WB
- N Livermore Ave & Las Positas Ct
- N Livermore Ave & Cromwell Wy SB
- Junction Ave & Chestnut St EB
- Garaventa Ranch Rd & Periwinkle Cmn
- Garaventa Ranch Rd & Altamont Creek Elementary School
- Garaventa Ranch Rd & Scenic Ave
- Scenic Ave & Ridgestone Rd
- Junction Ave & Walnut St
- Las Positas Rd & N Mines Rd EB
- Las Positas Rd & N Mines Rd WB
- First St & Inman St EB
- Las Positas Rd & Mountain Vista Pkwy WB
- Las Positas Rd & Arroyo Plaza EB
- Las Positas Rd & Lawrence Dr WB
- Las Positas Rd & Preston Ave WB
- Las Positas Rd & S Vasco Rd EB
- Las Positas Rd & Pullman St EB
- Las Positas Rd & Preston Ave EB
- Las Positas Rd & Lawrence Dr EB
- Las Positas Rd & Mountain Vista Pkwy EB
- Las Positas Rd & Arroyo Vista EB
- Las Positas Rd & Contractors St
- Las Positas Rd & Bennett Dr EB
- Las Positas Rd & Capitol St EB
- Las Positas Rd & Pullman St WB
- Las Positas Rd & Capitol St WB
- Las Positas Rd & Arroyo Vista WB
- Las Positas Rd & Bennett Dr WB
- First St & Southfront Rd
- Junction Ave & N Livermore Ave
- First St & Inman St WB
- Vasco Road ACE
- National Dr & Exchange Ct WB
- National Dr & Exchange Ct EB
- National Dr & Greenville Rd EB
- National Dr & Greenville Rd WB
- National Dr & Longfellow Ct
- Brisa St & National Dr
- E Stanley Blvd & Murdell Ln EB
- E Stanley Blvd & El Caminito
- E Stanley Blvd & Murrieta Blvd EB
- E Stanley Blvd & ValleyCare Medical Center EB
- Railroad Ave & South P St
- Railroad Ave & N St
- Railroad Ave & North L St
- Railroad Ave & North P St
- E Stanley Blvd & ValleyCare Medical Center WB
- E Stanley Blvd & Wall St
- E Stanley Blvd & Murdell Ln WB
- Railroad Ave & South L St
- Fourth St & South M St WB
- Fourth St & South P St WB
- Holmes St & Murrieta Blvd SB
- Holmes St & Mocho St
- Holmes St & Elaine Ave
- Holmes St & El Caminito
- Holmes St & Concannon Blvd SB
- Concannon Blvd & Barcelona St WB
- Concannon Blvd & Niagara Dr
- Concannon Blvd & Pulsar Ave WB
- El Padro Dr & Mendenhall Middle School NB
- El Padro Dr & Orange Wy
- El Caminito & Andalucia St
- Wall St & Caliente Ave
- Fourth St & South P St EB
- Fourth St & South M St EB
- Wall St & Granada High School NB
- Wall St & Granada High School SB
- Wall St & El Caminito
- El Caminito & Encino Dr
- El Caminito & El Padro Dr
- El Padro Dr & Ontario Dr
- El Padro Dr & Mendenhall Middle School SB
- Concannon Blvd & Pulsar Ave EB
- Concannon Blvd & Vega Rd
- Concannon Blvd & Barcelona St EB
- Holmes St & Concannon Blvd NB
- Holmes St & Vancouver Wy
- Holmes St & Anza Wy
- Holmes St & Murrieta Blvd NB
- South P St & Railroad Ave
- South P St & First St
- E Stanley Blvd & Murrieta Blvd WB
- Maple St & Second St
- East Ave & Maple St
- East Ave & Dolores St
- East Ave & East Avenue Middle School
- East Ave & Buena Vista Ave EB
- East Ave & N Mines Rd EB
- East Ave & Charlotte Wy EB
- East Ave & Research Dr EB
- East Ave & Livermore Community Center EB
- Downtown Livermore / Transit Center WB
- Downtown Livermore / Transit Center EB
- East Ave & Research Dr WB
- East Ave & Charlotte Wy WB
- East Ave & N Mines Rd WB
- East Ave & Buena Vista Ave WB
- East Ave & Livermore Community Center WB
- East Ave & Hayes Ave
- East Ave & Estates St
- East Ave & Jensen St
- Pacific Ave & Dolores St WB
- Fourth St & South J St
- Fourth St & South K St
- S Vasco Rd & East Ave
- S Vasco Rd & Mesquite Wy
- S Vasco Rd & Westgate Dr
- S Vasco Rd & Patterson Pass Rd NB
- S Vasco Rd & Brisa St NB
- S Vasco Rd & Industrial Wy
- Maple St & Fourth St
- Dolores St & Arbor Ave
- Pacific Ave & Dolores St EB
- Dolores St & Pacific Ave
- Dolores St & Carrigan Cmn
- S Vasco Rd & Patterson Pass Rd SB
- S Vasco Rd & Daphne Dr
- S Vasco Rd & Emily Wy
- N Mines Rd & East Ave NB
- N Mines Rd & Dana Cir NB
- N Mines Rd & Patterson Pass Rd NB
- N Mines Rd & First St
- N Mines Rd & Patterson Pass Rd SB
- N Mines Rd & Dana Cir SB
- N Mines Rd & East Ave SB
- N Mines Rd & Charlotte Wy
- East Ave & S Vasco Rd
- Regional St & Dublin Blvd NB
- Amador Valley Blvd & Regional St EB
- Amador Valley Blvd & Donohue Dr EB
- Village Pkwy & Amador Valley Blvd
- Village Pkwy & Tamarack Dr NB
- Village Pkwy & Dublin High School
- DHS - Village Pkwy & Davona Dr
- Davona Dr & Briarwood Ln
- Davona Dr & Lucania St WB
- Davona Dr & Wicklow Ln WB
- Davona Dr & Bluebell Wy
- Alcosta Blvd & Fircrest Ln EB
- Alcosta Blvd & Stagecoach Rd
- Stagecoach Rd & N Lake Dr SB
- Stagecoach Rd & Jade Cir SB
- Dougherty Rd & Camp Parks Blvd
- Stagecoach Rd & Turquoise St
- Amador Valley Blvd & Dublin Meadows St
- Dougherty Rd & Mariposa Cir
- Dougherty Rd & Park Sierra
- Dougherty Rd & Sierra Ln SB
- Dougherty Rd & Sierra Ln NB
- Dougherty Rd & Houston Pl
- Amador Valley Blvd & Wildwood Rd
- Amador Valley Blvd & Stagecoach Rd
- Stagecoach Rd & Topaz Cir
- Stagecoach Rd & Jade Cir NB
- Stagecoach Rd & N Lake Dr NB
- Stagecoach Rd & Alcosta Blvd
- Alcosta Blvd & Fircrest Ln WB
- Davona Dr & Gate Wy
- Davona Dr & Wicklow Ln EB
- Davona Dr & Lucania St EB
- Village Pkwy & Davona Dr
- Village Pkwy & Brighton Dr
- Village Pkwy & Tamarack Dr SB
- Amador Valley Blvd & Village Pkwy
- Amador Valley Blvd & Donohue Dr WB
- Amador Valley Blvd & Regional St WB
- and 415 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 | 58.3 | first check |
| 2026-07-30 | 58.3 | no change |
| 2026-07-31 | 58.3 | no change |
| 2026-08-01 | 58.3 | 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
10 findings, ordered by severity.
Show every finding
- Error1 instance
Service data ended 93 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)
- Warning42 instances
Some stops sit far from the route line, going by the feed's own distance values.
Trip planners may draw the route down the wrong streets or point riders to the wrong corner.
Fix: Check the flagged stops' shape_dist_traveled against the route shape, and re-generate it on export if they disagree. (Usually an export-tool fix, not hand editing.)
Finding code: stop_too_far_from_shape_using_user_distance · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning7 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)
- Warning4 instances
Same name and description for stop (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'same_name_and_description_for_stop' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Finding code: same_name_and_description_for_stop · 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
feed_info.txt lists no contact email and no contact URL.
Without a contact, apps like Google Maps can't reach you when they find a problem in the feed.
Fix: Add feed_contact_email or feed_contact_url to feed_info.txt. (One field, set once in export settings.)
Finding code: missing_feed_contact_email_and_url · Read the fix guide · 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
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)
- Info13 instances
Some trip headsigns name a stop along the way, not the final destination.
The sign should tell riders where the bus ends up, so a midpoint name can send them the wrong way.
Fix: Set trip_headsign to the trip's last stop or its overall destination. (Usually a bulk edit in your scheduling software.)
Finding code: trip_headsign_matches_intermediate_stop · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Info1 instance
feed_info.txt has no technical contact (feed_contact_email or feed_contact_url).
Trip-planning apps and regional data coordinators have nobody to email when they spot a problem with your feed, so problems linger.
Fix: Add feed_contact_email to feed_info.txt. (One field.)
Finding code: scorecard_no_feed_contact · 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 93 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 93 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) Different (allowed)
- Your feed's agency_id is lavta-ca-us; your National Transit Database ID is 90144. A feed that serves several agencies (a shared regional feed) can legitimately carry more than one agency_id. The values do not need to equal the five-digit NTD ID, so this difference is allowed and carries no score. Confirm that P-50 crosswalks agency_id lavta-ca-us to NTD ID 90144, and keep the feed value stable. Do not change it solely to make the two values equal.
- shapes.txt covers your trips Ready
- All 3009 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 93 days ago.
- Valid Met
- Passes validation with no errors.
- Current Not yet
- Service data expired 93 days ago.
- Accessible Met
- States wheelchair access on 100% of stops and 100% of trips.
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.
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.
- Gap Designate a technical contact in feed_info.txt's feed_contact_email
feed_info.txt has no feed_contact_email or feed_contact_url.
- Meets wheelchair_boarding stated on stops and trips
States wheelchair access on 100% of stops and 100% of trips.
- Meets shapes.txt with a shape for every trip
All 3009 trips have a shape in shapes.txt.
- Meets Fare data published, or the service marked fare-free
Fare data is published.
- Correctness 67 / 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 92 / 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/livermore-amador-valley-transit-authority/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.