Call-prep brief · checked 2026-10-07

Golden Gate Transit

Grade D · 67.5 / 100

Unchanged since 2026-10-06.

For this call: lead with the grade and the three fixes below, then confirm the feed is current and the NTD details line up. Each fix is framed as a next step, not a failure.

What changed since the last check

Correctness no change
Freshness no change
Rider experience no change

Top three things to fix

Set wheelchair_boarding to 1 (accessible) or 2 (not accessible) for every stop. A field survey can start with the busiest stops.
349 of 349 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 349 stops in the feed.
Effort: A column in stops.txt; your scheduling software likely has it.
Set wheelchair_accessible on every trip. If every vehicle is accessible, this may be one default; otherwise use the value for each trip.
686 of 686 trips don't say whether the vehicle is wheelchair accessible. Even with accessible stops, riders need to know the transit vehicle itself can take them.
Fixing this covers all 686 trips in the feed.
Effort: A default or per-trip field in your export.
Add feed_info.txt with feed_start_date and feed_end_date to your export.
feed_info.txt is missing its start/end dates (the file itself is absent) Apps and this scorecard can't warn anyone before the feed goes stale without stated validity dates.
This one is about the feed as a whole, so there is no share of it to count.
Effort: Two fields, set once in export settings.

Riders and need behind these fixes

No ridership snapshot was on hand when this was built, so annual rider-trips are not known.
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.

Feed evidence: 349 of 349 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

Agency: Golden Gate Transit
Finding: scorecard_wheelchair_boarding_unknown
Feed evidence: 349 of 349 stops don't say whether a wheelchair user can board there.
Why it matters: Riders who use wheelchairs can't plan a trip when accessibility is marked 'unknown'; apps show no information at all.
Requested change: 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.
Evidence: https://gtfsscorecard.org/agency/golden-gate-transit/?finding=scorecard_wheelchair_boarding_unknown#finding-handoff

NTD GTFS readiness: Ready

Published at a public URL, valid, current, and identified with agency_id: the four feed checks for RY2026 all hold here. Only your own D-10 and P-50 filings make that official; this is a heads-up, not a determination.

Published Ready: Published at a public URL.
Valid Ready: Passes validation with no errors.
Current Ready: Service data covers the next 66 days.
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): Equal. This feed's agency_id also equals its NTD ID (90016). Equality is allowed but not required; keep the value stable and retain the P-50 crosswalk.

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: https://realtime.goldengate.org/gtfsstatic/GTFSTransitData.zip
Last checked: 2026-10-07
Service window: 66 days of service data remain. Last service date 2026-12-12.
Location: California

Part of the California portfolio: see where this agency sits among the other feeds in that group before the call.

A data-quality and completeness read to support an agency conversation. Not an official compliance determination. Rubric v1.4, validator 8.0.1.