Call-prep brief · checked 2026-10-31
Marin Transit
Grade A · 97.2 / 100
Unchanged since 2026-10-30.
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_accessible on every trip. If every vehicle is accessible, this may be one default; otherwise use the value for each trip.
535 of 1613 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 535 of 1,613 trips, about 33% of them.
Effort: A default or per-trip field in your export.
Check the flagged file name for a typo of a standard GTFS file. Remove it if it is a vendor extra.
The feed includes a file that is not part of the GTFS spec. Apps ignore files they don't know, and a stray file can hide a misspelled standard file name.
This is a validator notice, and the validator decides what each instance covers, so no share of the network can be read from it here.
Effort: A quick look at the flagged file.
Check whether the gap is real, like a seasonal break; if not, add the missing dates to the calendar.
The feed has a stretch of two weeks or more with no service running. A long gap can mean dates were left out of the calendar. Apps then show no trips on those days.
This is a validator notice, and the validator decides what each instance covers, so no share of the network can be read from it here.
Effort: A review of your calendar dates.
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-26.
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
- 535 of 1613 trips don't say whether the vehicle is wheelchair accessible.
- Next action
- Set wheelchair_accessible on every trip. If every vehicle is accessible, this may be one default; otherwise use the value for each trip.
- 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 includes a file that is not part of the GTFS spec.
- Next action
- Check the flagged file name for a typo of a standard GTFS file. Remove it if it is a vendor extra.
- 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 has a stretch of two weeks or more with no service running.
- Next action
- Check whether the gap is real, like a seasonal break; if not, add the missing dates to the calendar.
- 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
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 70 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): Different (allowed). Your feed's agency_id is 33; your National Transit Database ID is 90234. 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 33 to NTD ID 90234, 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
- https://marintransit.gov/data/google_transit.zip
- Last checked
- 2026-10-31
- Service window
- 70 days of service data remain. Last service date 2027-01-10.
- Feed version
- UTC: 04-Feb-2026 00:08
- 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.