Bay Area Rapid Transit (BART)

What changed since the last check

• Correctness no change
• Freshness down 1.7
• Rider experience no change
• Realtime quality no change

Top three things to fix

1. Re-export with a validity window that reaches at least 60 days out.

   Service data runs out in 29 day(s). When the calendar runs out, trip planners stop showing this agency. Fixing it now is calmer than after riders notice.

   Effort: One export setting.

2. Add the required column named in the finding to the flagged file.

   A file is missing a column that GTFS requires. Apps may reject the whole file, so riders could lose the affected routes or stops.

   Effort: Often an export setting; ask your vendor if it recurs.

3. Set wheelchair_boarding to 1 (accessible) or 2 (not accessible) for every stop. A field survey can start with the busiest stops.

   287 of 287 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.

   Effort: A column in stops.txt; your scheduling software likely has it.

Ready to send to the agency

Hi Bay Area Rapid Transit (BART) team, Service data runs out in 29 day(s). When the calendar runs out, trip planners stop showing this agency. Fixing it now is calmer than after riders notice. The fix is usually one export setting: Re-export with a validity window that reaches at least 60 days out. 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/bay-area-rapid-transit-bart/

Copy this note from the full scorecard.

NTD GTFS readiness: Needs attention

This feed is close to NTD-ready. 1 validator error to resolve. Service data runs out in 29 days; renew before you certify.

Published Ready

Published at a public URL.

Valid Needs attention

1 validator error to resolve.

Current Needs attention

Service data runs out in 29 days; renew before you certify.

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 NTD ID (optional): Different (allowed). Your feed's agency_id is BART; your National Transit Database ID is 90003. 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 BART to NTD ID 90003, and keep the feed value stable. Do not change it solely to make the two values equal.

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://www.bart.gov/dev/schedules/google_transit.zip

Last checked

2026-08-01

Service window

29 days of service data remain. Last service date 2027-01-10.

Feed version

72

Location

California