Marin Transit

What changed since the last check

• Correctness no change
• Freshness down 1.6
• Rider experience no change

Top three things to fix

1. Review the rule documentation for 'trip_distance_exceeds_shape_distance' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.

   Trip distance exceeds shape distance (flagged by the MobilityData validator). See the linked rule for what this affects.

   Effort: Varies.

2. Review the rule documentation for 'missing_required_column' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.

   Missing required column (flagged by the MobilityData validator). See the linked rule for what this affects.

   Effort: Varies.

3. Set wheelchair_accessible on every trip (most small-agency fleets are 100% accessible, so this is often a single default).

   532 of 1612 trips don't say whether the vehicle is wheelchair accessible. Even with accessible stops, riders need to know the bus itself can take them.

   Effort: Often one default setting in your export.

   Agencies here usually clear this within about 1 week (based on 5 observed fixes).

NTD certification readiness: Needs attention

This feed is close to NTD-ready. 2 validator errors to resolve.

Published Ready

Published at a public URL.

Valid Needs attention

2 validator errors to resolve.

Current Ready

Service data covers the next 43 days.

agency_id and NTD ID: Not aligned. 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, so a difference here is a heads-up, not an error. Optionally set the agency_id for your service to 90234 in agency.txt (and the matching agency_id in routes.txt) so the feed lines up with your NTD record. It is a convenience, not a required feed change: FTA also links agency_id to your NTD ID on your P-50 form.

Key facts

Feed URL

http://www.marintransit.org/data/google_transit.zip

Last checked

2026-07-09

Service window

31 days of service data remain. Last service date 2026-08-09.

Feed version

UTC: 04-Feb-2026 00:08