Feed status · checked 2026-08-01
Bay Area Transportation Authority
Based on the feed this agency publishes
Service mode Bus
unchanged since 2026-07-31
Catalogued in Michigan.
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 81 minutes ago; last changed 41 days ago.
Measured 3 of 4 score categories from the agency's own feed.
How we measured this
Confidence in this measurement: medium.
- Realtime quality was not measured this run. It does not count against the grade.
- The feed was downloaded from the agency's own URL.
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 1666 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
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.
The feed contains no fare information. Riders see 'fare unknown' in trip planners and can't budget their trip; visitors are most affected.
⏱ A small file for most flat-fare systems.worth about +15 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
80 of 229 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 +9 points in its category
This feed is built with National RTAP's GTFS Builder. Your staff can usually make these changes in the GTFS Builder spreadsheets and republish, and National RTAP's help desk supports that at no cost.
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 1666 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
- The feed contains no fare information.
- Next action
- 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.
- 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
- 80 of 229 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
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. This feed is built with National RTAP's GTFS Builder. Your staff can usually make these changes in the GTFS Builder spreadsheets and republish, and National RTAP's help desk supports that at no cost.
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.
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. · Read the fix guide
Make the change. This feed is built with National RTAP's GTFS Builder. Your staff can usually make these changes in the GTFS Builder spreadsheets and republish, and National RTAP's help desk supports that at no cost.
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. This feed is built with National RTAP's GTFS Builder. Your staff can usually make these changes in the GTFS Builder spreadsheets and republish, and National RTAP's help desk supports that at no cost.
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 1666 days ago.
- Published accessibility data
- Accessibility information is stated for 65.1% of stops and 100% 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
This feed comes from National RTAP's GTFS Builder, so your own staff can usually make these changes in the GTFS Builder spreadsheets and republish. If a consultant maintains it for you, forward this to them. Each fix names 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 12 kinds of issue across 44 instances (0 error, 37 warning, 7 informational).
Service data ended 1666 day(s) ago. Trip planners have likely already dropped this feed.
65% of stops state wheelchair accessibility (65% marked accessible, 0% marked not accessible). This measures what the feed publishes, not whether a stop is physically usable. Fare data is not published.
65% of stops state accessibility (65% marked accessible). Reflects what the feed states, not verified physical usability.
2 accessibility depth signals
4 route badge(s) pair a color and text color below the WCAG 4.5:1 contrast bar (17, 31, Bayline, 4).
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.
128 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set ("Crossing Circle Dr @ The Tower (Route 1)", "Albany St @ Fire Barn", "Veterans Dr @ Vista Park (inbound)", 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 229 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 (green)
- 10 (gray)
- 12 (gray)
- 13 (gray)
- 14 (gray)
- 16 (gray)
- 2 (black)
- 31 (pink)
- 4 (red)
- 5 (yellow)
- Bayline (teal)
- 17 (green)
| Route | Type | Line color |
|---|---|---|
| 1 Downtown to GT Mall via Veterans | Bus | green |
| 10 Traverse City to Suttons Bay / Northport | Bus | gray |
| 11 Traverse City to Glen Arbor / Empire | Bus | gray (no shape in feed) |
| 12 Traverse City to Interlochen | Bus | gray |
| 13 Traverse City to Kingsley / Fife Lake | Bus | gray |
| 14 Traverse City to Acme / Williamsburg | Bus | gray |
| 16 Old Mission : Traverse City to Bowers Harbor Park | Bus | gray |
| 2 Downtown to Goodwill Inn | Bus | black |
| 31 East Traverse Flex | Bus | pink |
| 4 Downtown to Meijer | Bus | red |
| 5 Garfield / LaFranier / GT Mall | Bus | yellow |
| Bayline | Bus | teal |
| 17 Leelanau Loop | Bus | green |
List every stop
- Downtown Hall St Transfer Station
- Children's Museum / Discovery Center (outbound to Suttons Bay)
- Children's Museum / Discovery Center (Inbound to TC)
- Cherry Bend Rd @ Leelanau Studios
- M-22 @ Shady Lane Market
- M-22 @ Fort Road (Outbound)
- Hop Lot Brewing Company (Inbound)
- Hop Lot Brewing Company (outbound)
- Leelanau Montessori
- State St west of Union
- Front St @ Suttons Bay Library
- Lake Leelanau at NJ Grocery (LL)
- Ki-Dah-Keh Mi-Kun
- Leelanau Sands Casino
- Omena Post Office
- W Nagonaba @ Northport Village Offices (LL)
- Union St @ 7th St (outbound)
- Union St @ 10th St (outbound)
- Union St @ 12th St (outbound)
- Union at 13th St (outbound)
- 14th St at Veterans Dr (outbound)
- Division Street @ Tenth St (Outbound)
- Division Street @ Tenth St
- US-31 S @ Menards
- Blair Township Hall
- Veterans Dr @ Bayhill (Outbound)
- M-137 @ Blue Vase Books (Park-n-Ride)
- Interlochen Center for the Arts
- Veterans Dr @ Vista Park (outbound)
- Cass St @ Lake Avenue (Outbound 205)
- Cass St @ Tenth Street
- Cass St @ Sixteenth Street (Inbound)
- Liv Arbors
- Three Mile @ Oleson's
- Garfield Road @ Mayfield Post Office
- M-113 E @ Northland Foods (Park-n-Ride)
- Downtown Fife Lake (Merritt & Lakecrest)
- Albany St @ Fire Barn
- Crossing Circle Dr @ The Tower (Route 1)
- E Front at Fair St Civic Center (Eastbound)
- TC State Park @ Footbridge (Outbound)
- US-31 at Economy Inn (Outbound)
- 8th and Rose (Inbound)
- 8th and Rose (outbound)
- US-31 at Four Mile Road
- US-31 Woodland Furniture (Park-n-Ride)
- Cherry Capital Airport
- S Airport at Woodcreek (Inbound)
- S Airport Road @ Woodcreek BLVD (Outbound)
- Grand Traverse Resort
- Meijer Acme
- Turtle Creek Casino (Main Ent)
- Turtle Creek Casino (Park/Ride)
- Turtle Creek Casino (Emp Ent)
- Acme Park-n-Ride
- US-31 Economy Inn
- US-31 at Four Mile Road (Inbound)
- TC State Park at Footbridge (Inbound)
- Veterans Dr @ Vista Park (inbound)
- Veterans Dr @ Bayhill (inbound)
- First Congregational Church
- Peninsula Twp. Fire Station
- Archie Park (Gray & Center Roads)
- Old Mission Peninsula School
- Bowers Harbor Park
- 14th St at Veterans Dr (inbound)
- Union at 13th St (St. Francis)
- Union St @ 12th St (inbound)
- Lake Leelanau at NJ Grocery
- Leland Library (LL)
- Union St @ 10th St (inbound)
- W Nagonaba @ Northport Village Offices
- Omena Post Office (LL)
- Union St @ 7th St (Inbound)
- Leelanau Sands Casino
- Front St @ Suttons Bay Library
- W Front St @ Record Eagle (Route 1)
- W Front St @ Pine St (JS - Route 1)
- Bay Hill Office
- North Royal Drive (Kids Creek Clinic)
- Bay Hill Terrace @ Garden
- Hillview Apts (Front End)
- Cass Rd Transfer Station
- State St East of Union
- Cass St @ Lake Avenue (Outbound)
- Comfort Inn (Bayline)
- 8th @ Lake Ave
- 8th at Wellington (outbound)
- Traverse Area District Library (outbound)
- Barlow & Hannah (inbound)
- Barlow at Center (inbound)
- Barlow at Carver (inbound)
- Carver St @ Garfield Ave (Southbound)
- Barlow St @ Salvation Army (outbound)
- M-22 & Fort Route (inbound)
- Barlow St @ Glenview Ln (Outbound)
- Barlow St @ Gladewood Ln (outbound)
- Barlow St @ Secretary of State/USPS (outbound)
- Kings Court at Ray Blvd
- Fitzhugh Drive @ US-31
- Fitzhugh Dr. @ US-31
- US-31 & Sugar Beach
- Airport Access & Indian Trail Blvd
- East Front & Davis Street
- East Front & Davis Street
- US-31 & Pirates Cove
- East Front & Rose Street
- East Front & Rose Street
- LaFrainer Rd at Ridge 45 Apartments (Route 2 Outbound)
- Keystone @ Goodwill Inn Entrance
- LaFrainer Rd @ GT County Health Dept. (Route 2/5 Inbound)
- LaFrainer Rd @ Village Glen Apts
- LaFrainer Rd at Ridge 45 Apartments (Route 2 Inbound)
- Traverse Health Clinic (1408)
- LaFrainer Rd @ Maylane (GT County Health Dept).
- US-31 at Lowe's Dr.
- North Hall (NMC)
- Barlow St @ Secretary of State / USPS (inbound)
- Franke Rd. (WB)
- Franke Rd. (EB)
- Barlow St @ Gladewood Ln (Inbound)
- Front & Boardman
- Barlow St @ Glenview Ln (inbound)
- Barlow St @ salvation army (inbound)
- Carver St @ Garfield Ave (northbound)
- Grand Traverse Mall (1,5,12,Bayline)
- Barlow at Carver (outbound)
- Barlow at Center (outbound)
- Barlow & Hannah (Outbound)
- Traverse Area District Library (inbound)
- 8th at Wellington (inbound)
- 8th @ Lake Ave
- Cass St @ Lake Ave (Inbound)
- Front St @ Cass (inbound)
- W Front St @ Record Eagle (inbound)
- W Front St @ Pine St (JS)
- Cass St @ Sixteenth Street (OB)
- GT County Civic Center
- Grand Traverse Academy
- Oleson's @ Three Mile
- Woodland School
- Timber Ridge
- 8th and Rose (outbound) 1419
- Tom's East Bay (Route 5)
- 8th and Rose (inbound)
- Cass St @ Tenth Street (outbound)
- W Front at Maple
- W Front at Maple
- W Front at Cedar (Inbound)
- W Front at Cedar
- 6th st at Madison (inbound)
- 6th st at Madison (outbound)
- LOT Q / Munson Family
- Munson Family Practice
- Oleson's Food Store West
- West Royal Drive (Munson Dialysis)
- Meijer (Bayline / Route 4)
- GT YMCA
- Brookside Commons
- Oryana West
- S Airport Rd @ Goodwill Store
- S Airport Rd @ Logans Landing (Northbound)
- Kings Court at Ray Blvd
- LaFrainer Rd @ Village Glen Apts
- Oak Terrace Apts
- Oak Terrace @ Garfield Rd
- Aspen Hill Apts
- Traverse Health Clinic
- Hastings @ Father Fred (northbound)
- Garfield and Boon (Northbound)
- Hastings St @ Father Fred (southbound)
- Garfield and Boyd (Southbound)
- Garfield Ave @ Titus St (Southbound)
- S Airport Rd @ Logans Landing (Southbound)
- Garfield @ State St (Southbound)
- Dennos Museum Center
- LaFrainer Rd at Ridge 45 Apartments (Northbound)
- Garfield Ave @ State St (Northbound)
- LaFrainer Rd at Ridge 45 Apartments (Southbound)
- Garfield Ave @ Titus St (Northbound)
- Garfield and Boyd (Northbound)
- Garfield and Boon (Southbound)
- Sugar Plum Apts
- Meijer Park n Ride
- Silver Drive - Historic Barns
- Silver Drive - Historic Barns
- GT Commons Power Plant
- Silver Drive The Commons at Stella
- Silver Drive The Commons at Stella
- Elmwood at 11th - WRC
- Elmwood @ State of Mich Bldg
- Elmwood at 7th
- Elmwood @ Seventh Street
- Elmwood at 6th
- Elmwood at 6th
- W. Front at Cedar St. (Ace Hardware)
- W. Front at Cedar St.
- W. Front at Maple (Westbound)
- W. Front at Maple (eastbound)
- Hall Street at Lot X
- Pine and State
- State St East of Union
- State St @ Cass St
- State St @ Park St
- Front St @ Wellington
- Front St @ Wellington
- Front St @ Park St
- Front St @ Cass
- E. Front at Barlow (eastbound)
- E. Front at Barlow (Hagerty Center)
- E. Front at Garfield
- E. Front at Garfield
- E. Front at Milliken (NMC : Westbound)
- Munson Ave and 8th St (MCHC)
- Munson Ave and 8th St (Westbound)
- Tom's East Bay (Bayline)
- Airport Access (MCHC)
- Parsons Rd. & CTC
- Parsons Rd. & Aero Park Campus
- Aero Park @ Parsons Stuelen
- N Aero Park Ct
- US-31 at 3 Mile Rd
- US-31 at 3 Mile Rd
- TC State Park at Footbridge (Westbound)
- US-31 Grand Beach (Inbound)
- US-31 at Four Mile Road
- US-31 at Four Mile Road
- Gens Park
- US-31 Woodland Furniture
Over time
Overall score across the last 4 checks — unchanged since 2026-07-31.
Show the numbers
| Check | Score | Change |
|---|---|---|
| 2026-07-25 | 44.5 | first check |
| 2026-07-30 | 44.6 | up 0.1 |
| 2026-07-31 | 44.6 | no change |
| 2026-08-01 | 44.6 | 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
16 findings, ordered by severity.
Show every finding
- Error1 instance
Service data ended 1666 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)
- Warning80 instances
80 of 229 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)
- Warning13 instances
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)
- Warning10 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 · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning6 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
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)
- 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 route long names repeat the route's short name inside them.
Apps show both names together, so riders see the number twice, like '5 5 Downtown'.
Fix: Drop the short name from route_long_name and keep the long name descriptive, like 'Downtown via 5th Ave'. (One field per flagged route.)
Finding code: route_long_name_contains_short_name · 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 · 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)
- Info6 instances
Some service dates fall outside the date window set in feed_info.txt.
feed_info.txt should span every day your service runs, so apps know when the data applies.
Fix: Widen feed_start_date and feed_end_date to cover all service dates, or fix the dates that fall outside. (Two fields in feed_info.txt, or one export setting.)
Finding code: service_window_outside_feed_period · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Info1 instance
Some files contain columns that are not part of the GTFS spec.
Harmless to riders, but apps ignore these columns and they can hide typos in real column names.
Fix: Check the flagged column names for misspellings of standard GTFS fields; remove them if they are vendor extras. (A quick look at the flagged files.)
Finding code: unknown_column · Read the fix guide · 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 1666 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 1666 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 60 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 1666 days ago. States wheelchair access on 65% of stops and 100% of trips; the mark needs 90% of each.
- Valid Met
- Passes validation with no errors.
- Current Not yet
- Service data expired 1666 days ago.
- Accessible Not yet
- States wheelchair access on 65% of stops and 100% 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.
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.
A local transit-data support resource is Michigan Public Transit Open Data Program. MDOT's program helping agencies produce and maintain GTFS and GTFS-Flex. This resource supports agencies; it is not a scoring authority.
- Correctness 53 / 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 69 / 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/bay-area-transportation-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.