← Back to the full scorecard

Call-prep brief · checked 2026-07-09

Simi Valley Transit

Grade F · 56.6 / 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. Re-export the feed with a calendar that reaches further out, and set feed_info feed_end_date past your next service change.

    Service data ended 1134 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.

    Effort: Usually one export setting; export on a schedule so it never lapses again.

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

  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).

    129 of 129 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).

Ready to send to the agency

Hi Simi Valley Transit team, Service data ended 1134 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. The fix is usually one export setting: Re-export the feed with a calendar that reaches further out, and set feed_info feed_end_date past your next service change. Your feed is produced by Trillium, so the quickest path is usually forwarding this to your Trillium contact. This came from your GTFS data quality scorecard, which checks the feed you publish and lists the fixes in plain language: https://gtfsscorecard.org/agency/simi-valley-transit/

Copy this note from the full scorecard.

NTD certification readiness: Not ready

Resolve this before you certify on the D-10. 1 validator error to resolve. Service data expired 1122 days ago, so FTA would find the link out of date.

Published Ready
Published at a public URL.
Valid Needs attention
1 validator error to resolve.
Current Not ready
Service data expired 1122 days ago, so FTA would find the link out of date.

agency_id and NTD ID: Not aligned. Your feed's agency_id is 729; your National Transit Database ID is 90050. 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 90050 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/simivalley-ca-us/simivalley-ca-us.zip
Last checked
2026-07-09
Service window
Feed has expired. Last service date 2030-12-31.
Feed version
UTC: 02-Nov-2022 23:01

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