Feed status · checked 2026-10-09
Antelope Valley Transit Authority (AVTA)
Based on the feed source on file; publisher ownership is not verified
Service mode Bus
unchanged since 2026-10-08
Cataloged 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.4, validator 8.0.1.
Checked for changes 45 minutes ago; last changed 110 days ago.
Measured 4 of 4 score categories from the feed URL on file (publisher not verified).
How we measured this
Confidence in this measurement: high.
- All four score categories were measured this run.
- Realtime was sampled in one bounded window of 9 snapshots.
- The feed was downloaded from the configured feed URL. Publisher ownership of that URL is not verified.
Confidence describes how much the pipeline could measure this run, not the feed itself. It never changes the grade.
About this feed
Antelope Valley Transit Authority (AVTA)’s published feed lists 16 bus routes, 588 scheduled trips and 811 stops. Its service dates run from 2021-05-03 through 2021-08-01. It publishes realtime trip updates, vehicle positions and service alerts; when we checked, all of them answered. The published file has not changed since our first check on 2026-06-19.
Top things to fix
Re-export the feed with a calendar that reaches further out. Set feed_end_date in feed_info.txt past your next service change.Likely your export tool
Service data ended 1895 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.
This one is about the feed as a whole, so there is no share of it to count.
⏱ 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
811 of 811 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.
Fixing this covers all 811 stops in the feed.
⏱ 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
588 of 588 trips don't say whether the vehicle is wheelchair accessible. Even with accessible stops, riders need to know the bus itself can take them.
Fixing this covers all 588 trips in the feed.
⏱ A default or per-trip field in your export.worth about +15 points in its category
Riders and need behind these fixes
- This feed carries no National Transit Database ID, so annual rider-trips are not known for it.
- California as a whole measures lower on transit need. That is a statewide reading, not one for this feed's service area. Source: US Census ACS 5-year 2022, statewide overlay, as of 2026-10-05.
These describe this feed only. They do not rank agencies, and they do not change the grade or the order of the fixes.
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.
- Finding
- Fix 01 in Top things to fix: its feed evidence and the requested 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
- Finding
- Fix 02 in Top things to fix: its feed evidence and the requested 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
- Finding
- Fix 03 in Top things to fix: its feed evidence and the requested 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
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.
Fix 01 · Read the fix guide for scorecard_feed_expired
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.
Fix 02 · Read the fix guide for scorecard_wheelchair_boarding_unknown
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.
Fix 03 · Read the fix guide for scorecard_wheelchair_accessible_unknown
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 1895 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
- Fare information is published using GTFS Fares v1.
- Realtime information
- One or more realtime feeds were reachable; live-arrival coverage is not known.
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 9 kinds of issue across 4600 instances (0 error, 4600 warning, 0 informational).
Service data ended 1895 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 published.
0% of stops state accessibility (0% marked accessible). Reflects what the feed states, not verified physical usability.
2 accessibility depth signals
10 route badge(s) pair a color and text color below the WCAG 4.5:1 contrast bar (1, 4, 5, 7, 9, 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.
800 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set ("47th St. E. & Ave. S", "Rancho Vista Blvd. & Sierra Hwy.", "Sierra Hwy & Ave. I", 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.
Sampled 9 times outside service hours: 3 of 3 configured feeds healthy; vehicle position plausibility was not measurable; predictions ran a median of 0s behind schedule.
Routes and stops
Each route is drawn once, using the longest shape its trips follow; stops are the dots.
This feed has 811 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 (red)
- 11 (teal)
- 12 (white)
- 2 (gray)
- 3 (blue)
- 4 (brown)
- 5 (teal)
- 50 (orange)
- 51 (yellow)
- 52 (gray)
- 7 (green)
- 785 (yellow)
- 786 (green)
- 787 (red)
- 8 (black)
- 9 (yellow)
| Route | Type | Line color |
|---|---|---|
| 1 Route 1 | Bus | red |
| 11 Route 11 | Bus | teal |
| 12 Route 12 | Bus | white |
| 2 Route 2 | Bus | gray |
| 3 Route 3 | Bus | blue |
| 4 Route 4 | Bus | brown |
| 5 Route 5 | Bus | teal |
| 50 Route 50 | Bus | orange |
| 51 Route 51 | Bus | yellow |
| 52 Route 52 | Bus | gray |
| 7 Route 7 | Bus | green |
| 785 Route 785 | Bus | yellow |
| 786 Route 786 | Bus | green |
| 787 Route 787 | Bus | red |
| 8 Route 8 | Bus | black |
| 9 Route 9 | Bus | yellow |
List every stop
- 47th St. E. & Ave. S
- Rancho Vista Blvd. & Sierra Hwy.
- Sierra Hwy & Ave. I
- South Vally Transit Center
- Palmdale Transportation Center
- Owen Memorial Park
- Ave. R & Lemsford Ave.
- The Boulevard Transit Center
- Sierra Hwy & Ave. J-7
- Palmdale Blvd. & 5th St. W.
- Ave. Q-8 & 5th St. W.
- Ave. Q-8 & Wakefield Pl.
- 10th St. W. & Date Palm Dr
- Rancho Vista Blvd. & Palmdale Promenade
- Lancaster Blvd. & Valley Central Way
- Lancaster Blvd. & 30th St. W.
- Ave. I & 30th St. W.
- Ave. I & Valley Central Way
- 30th St. W. & Ave. I
- Lancaster Blvd. & 30th St. W.
- 10th St. W. & Jackman St.
- Sierra Hwy & Lancaster Blvd.
- Rancho Vista Blvd & 10th St. West
- Technology Dr. & Trade Center Dr.
- Technology Dr. & Trade Center Dr.
- 10th St. W. & Auto Center Dr.
- 10th St. W. & Auto Center Dr.
- 15th St. W. & Kaiser Clinic
- Ave. R & Debra Ann Pl.
- 10th St. W. & Marketplace dr.
- Ave. Q & Rembler Ave.
- Ave. R & Janus Dr.
- 50th St. W. & Ave. M
- Ave. V-10 & 121st St. E.
- 126th St. E. & Ave. V-10
- Ave. W & 128th St. E.
- Longview Rd. & Pearblossom Hwy.
- Pearblossom Hwy. & 87th St. E.
- Pearblossom Hwy. & 82nd St. E.
- 47th St. E. & Ave. S
- Ave. R & 100th St. E.
- Ave. R & 105th St. E.
- Ave. R & 110th St. E.
- Ave. K & 10th St. W.
- Ave. K & 12th St. W.
- Tierra Subida & Cactus Dr.
- Rancho Vista Blvd. & Town Center Drive
- 47th St. E. & Ave. R
- Ave. S & 20th St. E.
- Avenue S & 20th Street East
- 6th St. E. & Palmdale Blvd.
- 6th St. E. & Palmdale Blvd.
- 10th St. W. & Ave. O-4
- 10th St. W. & Ave. O-4
- 10th St. W. & Palmdale Blvd.
- Rancho Vista Blvd & 3rd St. E.
- Ave. H & 20th St. W.
- Ave. H & 20th St. W.
- 60th St. W. & Ave. K
- 60th St. W. & Ave. K
- Ave. N-8 & 160th St. E.
- 15th St. W. & Ave. J-5
- 15th St. W. & Ave. J-5
- 170th St. E. & Ave. M-8
- Ave. I & 10th St. W.
- Kaiser Permanent at Ave L
- Rancho Vista Blvd. & Armfield Avenue
- Rancho Vista Blvd. & Armfield Ave.
- 10th. W & Palmdale Blvd.
- 10th St. W. & Date Palm Dr.
- Ave. Q-8 & Tierra Subida Ave.
- Ave. Q-8 & Wakefield Pl.
- Ave. Q-8 & Campos Dr.
- 30th St. W. & Ave. I
- 30th St. W. & Ave. I
- Avenue S & Springfield
- Ave. K & 7th St. E.
- Ave. L & Sierra Hwy.
- Business Center Parkway & Ave. L
- Business Center Pkwy. & Ave. L
- Ave. R & 47th St. E.
- Fern Ave. & Jackman St.
- Ave. R & 47th St. E.
- 30th St. W. & Ave. L
- 30th St. W. & Ave. K-8
- 30th St. W. & Ave. K-4
- Sierra Hwy & Ave. J
- 30th St. W. & Ave. K-4
- 30th St. W. & Ave. K-8
- 30th St. W. & Ave. K-12
- 50th St. W. & Ave. L-8
- Sierra Hwy & Ave. J
- Ave. S & Dawson Dr.
- Sierra Hwy. & Ave. K
- Ave. K & Gadsden Ave.
- Ave. K & Gadsden Ave.
- Sierra Hwy. & Ave. K
- Sierra Hwy. & Ave. J
- Challenger Way & Ave. K
- Challenger Way & Ave. J-8
- Challenger Way & Ave. J
- Challenger Way & Ave. J-8
- Business Center Pkwy. & Ave. L
- Ave. S & 30th St. E.
- 40th St. E. & Palmdale Blvd.
- Ave. R & 40th St. E.
- Ave. R & 52th St. E.
- Ave. R & 55th St. E.
- Ave. R & 60th St. E.
- Ave. R & 65th St. E.
- Ave. R & Valberg St.
- Ave. R & 70th St. E.
- Ave. R & 70th St. E.
- Ave. R & Valberg St.
- Ave. S & 27th St. E.
- Ave. R & 65th St. E.
- Ave. R & 60th St. E.
- Ave. R & 55th St. E.
- Ave. R & 52nd St. E.
- Ave. R & 40th St. E.
- 40th St. E. & Palmdale Blvd.
- Ave. S & 25th St. E.
- 87th St. E. & Pearblossom Hwy.
- 87th St. E. & Ave. T
- 90th St. E. & Ave. S
- 90th St. E. & Ave. R-8
- 90th St. E. & Ave. R
- Ave. R & 95th St. E.
- 96th St. E. & Ave U
- Palmdale Blvd. & 5th St. W.
- Ave. R & 90th St. E.
- 90th St. E. & Ave. R-8
- 90th St. E. & Ave S
- 87th St. E. & Ave. T
- 87th St. E. & Ave. U
- Ave. R & 47th St. E.
- Ave. J at 20th St. W.
- 30th St. W. & Ave. K
- Ave. S & Casa Verde Dr.
- Sierra Hwy. & Lancaster Blvd.
- Ave. S & Calle Mazatlan
- 60th St. W. & Ave. K-9
- 60th St. W. & Ave. K-9
- 100th St. E. & Ave. Q-10
- Ave. J & 20th St. E.
- Yucca Blvd. & Jackman St.
- 30th Street West & Coppersquare Apts.
- Palmdale Blvd. & Division
- 10th St. E. & Ave. S
- Palmdale Blvd. & 3rd St. E.
- Avenue S & 40th St East
- Palmdale Blvd. & 6th St. E.
- 10th St. E. & Ave. R
- 10th St. E. & Ave. R
- 10th St. E. & Ave. Q-11
- Technology Dr. & 5th St. W.
- 10th St. W. & Technology Dr.
- 10th St. W. & Rancho Vista Blvd.
- 10th St. W. & Destination O-8
- 10th St. W. & Ave. O
- 10th St. W. & Ave. N
- 10th St. W. & Ave. M-8
- 10th St. W. & Ave. M-4
- 10th St. W. & Ave. M
- Rancho Vista Blvd. & 3rd Street East
- Palmdale Blvd. & 6th St. E.
- Rancho Vista Bvld. & Sierra Hwy.
- Rancho Vista Blvd. & Palmdale Promenade
- Palmdale Blvd. & 3rd St. E.
- Palmdale Blvd. & Division
- Palmdale Blvd. & Del Taco / Arco
- Ave. J & 17th St. E.
- Ave. J & 15th St. E.
- Ave. J & Palm Vista
- 10th St. W. & Ave. L-12
- 10th St. W. & Ave. L-10
- 10th St. W. & Ave. L-8
- 10th St. W. & Ave. L-4
- 10th St. W. & Ave. L
- Ave. J & Challenger Way
- Ave. J & Hanstead
- Ave. J & 5th St. E.
- Ave. J & 3rd St. E.
- Ave. J & Division St.
- Ave. J & Sierra Hwy.
- Ave. J & Fig
- Ave. J & Lowtree
- Ave. J & 15th St. W.
- 50th St. W & Ave. M
- 20th St. W. & Ave. J
- Ave. J & 17th St. W.
- Palmdale Blvd. & 11th St. E.
- Ave. R & Janus Dr.
- Palmdale Blvd. & 95th St. E.
- 10th St. W. & Beechdale
- Palmdale Blvd. & 11th St. E.
- Palmdale Blvd. & 15th St. E.
- Palmdale Blvd. & 17th St. E.
- Ave. J & 10th St. W
- Palmdale Blvd. & 20th St. E.
- Reseda & Devonshire
- Plummer & Tampa
- Plummer & Corbin
- Plummer & Winnetka
- Plummer & Mason
- Desoto & Plummer
- De Soto & Nordhoff
- De Soto & Roscoe
- De Soto & Saticoy
- Palmdale Blvd. & 25th St. E.
- Desoto & Sherman Way
- De Soto & Vanowen
- Victory & Variel
- Canoga & Victory
- Canoga & Trillium
- Canoga & Erwin
- Canoga & Oxnard
- Canoga & Burbank (Warner Center)
- Burbank & Northrop Grumman
- Burbank & Kaiser Permanente Woodland Hil
- Palmdale Blvd. & 22nd St. E.
- Ventura & Kelvin
- Ventura & Winnetka
- Ventura & Tampa
- Reseda & Ventura
- Ventura & Reseda
- Ventura & Tampa
- Ventura & Winnetka
- Ventura & Kelvin
- Burbank & Kaiser Permanente Woodland Hil
- Burbank & Northrop Grumman
- Palmdale Blvd. & 27th St. E.
- Burbank & Canoga (Warner Center)
- Canoga & Oxnard
- Canoga & Erwin
- Canoga & Victory Blvd
- Victory & Variel
- De Soto & Vanowen
- Desoto & Sherman
- De Soto & Saticoy
- De Soto & Roscoe
- De Soto & Nordhoff
- Palmdale Blvd. & 30th St. E.
- Desoto & Plummer
- Plummer & Mason
- Plummer & Winnetka
- Plummer & Corbin
- Plummer & Tampa
- Reseda & Plummer
- Plummer & Reseda
- and 561 more (see the full list on the map or in the GeoJSON)
Over time
Overall score across the last 2 checks — unchanged since 2026-10-08.
Show the numbers
| Check | Score | Change |
|---|---|---|
| 2026-10-08 | 51.3 | first check |
| 2026-10-09 | 51.3 | no change |
What changed since your last check
- Correctness no change
- Freshness no change
- Rider experience no change
- Realtime quality no change
Feed history
Every check on record for this feed, grouped by the published file, newest first. A new file means the published zip changed. Grades from earlier rubric versions are shown with their rubric and are not comparable with today’s grade or the trend above.
| Checked | Published file | Service dates through | Grade at the time |
|---|---|---|---|
| 2026-10-08 to 2026-10-09 (2 checks) | aee75355a03e | 2021-08-01 | Current rubric: see the trend above |
| 2026-08-06 to 2026-08-07 (2 checks) | aee75355a03e | 2021-08-01 | F, 39.2 under rubric 1.3, an earlier scoring contract; not comparable with today’s grade |
| 2026-06-19 to 2026-07-10 (21 checks) | aee75355a03e | 2021-08-01 | F, 39.2 under rubric 1.1, an earlier scoring contract; not comparable with today’s grade |
What changed in this feed
Overall grade and score held steady since 2026-10-08.
Same feed file as 2026-10-08; the published zip did not change.
Subscribe to this feed’s changes (Atom) to hear about grade drops and export changes in a reader, with no sign-up.
Everything we checked
13 findings, ordered by severity.
Show every finding
- Error1 instance
Service data ended 1895 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. Set feed_end_date in feed_info.txt 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 for scorecard_feed_expired · See GTFS Best Practices (opens GTFS Best Practices on an external site)
- Warning2700 instances
Some scheduled trips move faster between stops than a bus can.
Usually a typo'd stop time; riders get arrival times no bus can meet.
Fix: Check the flagged stop times for transposed minutes. (A few minutes per flagged trip.)
Finding code: fast_travel_between_consecutive_stops · Read the fix guide for fast_travel_between_consecutive_stops · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning1676 instances
Some route lines list the same point twice in a row.
Repeated points don't hurt riders, but they can skew distance math and hint at a shaky export.
Fix: Turn on shape cleanup in your export tool, or drop the repeated points from shapes.txt. (Usually one export setting.)
Finding code: equal_shape_distance_same_coordinates · Read the fix guide for equal_shape_distance_same_coordinates · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning811 instances
811 of 811 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 for scorecard_wheelchair_boarding_unknown · See GTFS Schedule reference (opens the GTFS Schedule reference on an external site)
- Warning588 instances
588 of 588 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 for scorecard_wheelchair_accessible_unknown · See GTFS Schedule reference (opens the GTFS Schedule reference on an external site)
- Warning214 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 for stop_too_far_from_shape_using_user_distance · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning4 instances
Some stops sit far from the route line they belong to.
Trip planners may draw the bus route through the wrong streets or point riders to the wrong corner.
Fix: Check the flagged stops' coordinates and the route shape in your scheduling software; re-snap whichever is misplaced. (A few minutes per flagged stop.)
Finding code: stop_too_far_from_shape · Read the fix guide for stop_too_far_from_shape · 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 for expired_calendar · 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 for feed_expiration_date7_days · 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 for missing_feed_contact_email_and_url · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning1 instance
On some trips the stops fall along the route line in a different order than the schedule lists.
Trip planners can draw the bus doubling back or skipping ahead, which confuses riders reading the map.
Fix: Check the stop order and the shape direction in your scheduling software; the shape is often drawn backwards. (A few minutes per flagged trip.)
Finding code: stops_match_shape_out_of_order · 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 for trip_coverage_not_active_for_next7_days · 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).
App makers and state data programs have nobody to email when they spot a problem. Small errors then sit in the feed for months.
Fix: Add feed_contact_email to feed_info.txt. (One field.)
Finding code: scorecard_no_feed_contact · Read the fix guide for scorecard_no_feed_contact · 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 1895 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 1895 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 588 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
Two requirements remain for this feed to earn the conformance mark. Service data expired 1895 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 1895 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.
Realtime reliability
The realtime feed responded on 100.0% of 200 checks in the 25 days to 2026-10-09, with 15s median lag.
Sampled on a schedule between full scores, so this tracks uptime and freshness over time rather than at a single moment. The window ends at the newest observation, which is not always today: if the monitor stops, this window stops with it.
Live predictions vs schedule
Arrival predictions ran right on the schedule, and stayed within 95s nine times in ten. They were on time (about a minute early to five late) 97.1% of the time.
From the last full realtime sample: how far live arrival predictions sat from the schedule, and whether vehicle positions fell on the route. These feed the realtime score; they change no other category.
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.
- 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.
- 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 588 trips have a shape in shapes.txt.
- Meets Fare data published, or the service marked fare-free
Fare data is published.
- Correctness 52 / 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 52 / 100
- GTFS Best Practices for rider-facing fields. MobilityData grading covers stop names and headsigns.
- Realtime quality 100 / 100
- GTFS-Realtime best practices: a stable URL, high uptime, and frequent updates.
Part of the California portfolio: the same scorecards for every feed we track in that group, on one free page.
For programs that support several agencies
This scorecard and the board one-pager for Antelope Valley Transit Authority (AVTA) are free, and they stay free. If you support several agencies, as a state program, a technical-assistance center, a feed vendor, or a consultancy, you can buy the program report bundle. It puts this agency's board report in one archive with the reports for the other agencies you support, and each cover carries your program's name, logo, and accent color.
The report for Antelope Valley Transit Authority (AVTA) uses the same numbers as this page: grade F (51.3 out of 100) as of the check on 2026-10-09, its category scores, its top fixes, and its score at each check.
One bundle, up to 25 agencies: $149, paid once, delivered within 2 business days or refunded. Other plans, including a monthly refresh, are on the bundle page.
See a sample bundle report: a real agency's current grade, with placeholder branding.
A purchase buys no influence over grades, methodology, or which agencies are listed. The grade on this page comes from the check on 2026-10-09, scored with rubric v1.4 and MobilityData gtfs-validator 8.0.1. Based on the feed source on file; publisher ownership is not verified. Read how the grade is calculated.
Similar feeds in California
Other scorecards in California, starting with the same kind of service at a similar size. Listed for comparison, not ranked.
Show your grade
Put this badge on your agency site or feed README. It updates after each completed scoring check, shows the date of that check, and links back to this scorecard. When there is no current score it says so instead of showing an old one.
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/antelope-valley-transit-authority-avta/2026-10-09.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-10-09. 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.