Livermore Amador Valley Transit Authority

What changed since the last check

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

Top three things to fix

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

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

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

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

2. Review the rule documentation for 'stop_too_far_from_shape_using_user_distance' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.

   Stop too far from shape using user distance (flagged by the MobilityData validator). See the linked rule for what this affects.

   Effort: Varies.

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

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

   Some service calendars in the feed have already ended. Expired calendars are dead weight and can hide real schedule problems from your staff and vendors.

   Effort: One setting in most export tools.

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

Ready to send to the agency

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

Copy this note from the full scorecard.

NTD certification readiness: Not ready

Resolve this before you certify on the D-10. Service data expired 69 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 69 days ago, so FTA would find the link out of date.

agency_id and NTD ID: Not aligned. 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, so a difference here is a heads-up, not an error. Optionally set the agency_id for your service to 90144 in agency.txt (and the matching agency_id in routes.txt) so the feed lines up with your NTD record. It is a convenience, not a required feed change: FTA also links agency_id to your NTD ID on your P-50 form.

The bar this score answers to

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

Key facts

Feed URL

http://webwatch.lavta.org/TMGTFSRealTimeWebService/GTFS-Static/google_transit.zip

Last checked

2026-07-09

Service window

Feed has expired. Last service date 2026-04-30.

Feed version

January_26_01_20260327

State

California