GTFS Scorecard

← Back to the full scorecard

Call-prep brief · checked 2026-07-09

Sonoma-Marin Area Rail Transit (SMART)

Grade A · 98.9 / 100

Unchanged since 2026-07-08.

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

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

    1 of 42 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.

  2. Check the flagged column names for misspellings of standard GTFS fields; remove them if they are vendor extras.

    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.

    Effort: A quick look at the flagged files.

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

    Unknown file (flagged by the MobilityData validator). See the linked rule for what this affects.

    Effort: Varies.

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

NTD certification readiness: Ready

This feed looks ready for your NTD certification: published at a public URL, valid, and current. The official check is still your D-10 certification.

Published Ready
Published at a public URL.
Valid Ready
Passes validation with no errors.
Current Ready
Service data covers the next 197 days.

agency_id and NTD ID: Not aligned. Your feed's agency_id is 1535; your National Transit Database ID is 90299. 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 90299 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
https://data.trilliumtransit.com/gtfs/smart-ca-us/smart-ca-us.zip
Last checked
2026-07-09
Service window
185 days of service data remain. Last service date 2027-01-10.
Feed version
UTC: 14-Apr-2026 15:07

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