← All agencies

Feed status · checked 2026-08-01

Simi Valley Transit

Based on the feed this agency publishes

Service mode Bus

56.6 / 100

unchanged since 2026-07-31

Catalogued in California.

Feed expiredAccessibility gapsFlexible serviceRealtime not yet published

A data-quality and completeness lens to help an agency improve its GTFS feed. Not an official compliance determination from any transit program. New to this? How to read your scorecard. Interactive view of this scorecard. Rubric v1.3, validator 8.0.1.

Checked for changes 4 hours ago; last changed 41 days ago.

Measured 3 of 4 score categories from the agency's own feed.

How we measured this

Confidence in this measurement: medium.

  • Realtime quality was not measured this run. It does not count against the grade.
  • The feed was downloaded from the agency's own URL.

Confidence describes how much the pipeline could measure this run, not the feed itself. It never changes the grade.

Top things to fix

Fix 01

Re-export the feed with a calendar that reaches further out, and set feed_info feed_end_date past your next service change.Likely your export tool

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

⏱ Usually one export setting; export on a schedule so it never lapses again.worth about +100 points in its category

Fix 02

Add the required column named in the finding to the flagged file.Likely your export tool

A file is missing a column that GTFS requires. Apps may reject the whole file, so riders could lose the affected routes or stops.

⏱ Often an export setting; ask your vendor if it recurs.worth about +12 points in its category

Fix 03

Set wheelchair_accessible on every trip. If every vehicle is accessible, this may be one default; otherwise use the value for each trip.Likely your export tool

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.

⏱ A default or per-trip field in your export.worth about +15 points in its category

Trillium produces and hosts this feed as a service. These changes are made on their side: send the fix list to your Trillium contact and they apply it and republish.

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
Service data ended 1157 day(s) ago.
Next action
Re-export the feed with a calendar that reaches further out, and set feed_info feed_end_date past your next service change.
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
How to make and check these changes

Check the result on the published feed. Read the guide, make the change in your tool, and use the next comparable run to see whether the finding is still reported. Only an action or ticket record can attribute who made the change.

  1. Re-export the feed with a calendar that reaches further out, and set feed_info feed_end_date past your next service change. · Read the fix guide

    Make the change. Trillium produces and hosts this feed as a service. These changes are made on their side: send the fix list to your Trillium contact and they apply it and republish.

    Check the result. The next scorecard run checks this finding again. If a comparable check no longer reports it, the feed's clearance log records that result. This confirms feed state, not who made the change. Self-check a feed before you publish.

  2. Add the required column named in the finding to the flagged file. · Read the fix guide

    Make the change. Trillium produces and hosts this feed as a service. These changes are made on their side: send the fix list to your Trillium contact and they apply it and republish.

    Check the result. The next scorecard run checks this finding again. If a comparable check no longer reports it, the feed's clearance log records that result. This confirms feed state, not who made the change. Self-check a feed before you publish.

  3. Set wheelchair_accessible on every trip. If every vehicle is accessible, this may be one default; otherwise use the value for each trip. · Read the fix guide

    Make the change. Trillium produces and hosts this feed as a service. These changes are made on their side: send the fix list to your Trillium contact and they apply it and republish.

    Check the result. The next scorecard run checks this finding again. If a comparable check no longer reports it, the feed's clearance log records that result. This confirms feed state, not who made the change. Self-check a feed before you publish.

Rider view: what this feed publishes

A quick read of rider-facing information in this feed.

Schedule visibility
The feed's last published service date was 1157 days ago.
Published accessibility data
Accessibility information is stated for 95.1% of stops and 0% of trips. This measures published data, not whether stops or vehicles are physically usable.
Fare information
Fare information is published using GTFS Fares v2.
Realtime information
Realtime-feed availability and live-arrival coverage are not known from this scorecard.

Important: This does not rate service reliability. Riders should confirm current service alerts, fares, and accessibility accommodations with the transit operator before traveling.

Send Trillium a fix request

This feed is produced and hosted by Trillium. Copy this and send it to your Trillium contact; they make the change and republish the feed. Each fix names the validator notice and a guide link.

Send the agency a note

Supporting this agency? Copy this and email it to them. It names what lapsed, why it matters to riders, and the one setting to change.

Score by category

Correctness69.5 / 100

The MobilityData validator flagged 8 kinds of issue across 118 instances (1 error, 63 warning, 54 informational).

Freshness0.0 / 100

Service data ended 1157 day(s) ago. Trip planners have likely already dropped this feed.

Rider experience83.8 / 100

95% of stops state wheelchair accessibility (94% marked accessible, 1% marked not accessible). This measures what the feed publishes, not whether a stop is physically usable. Fare data is published.

Accessibility59.4 / 100

95% of stops state accessibility (94% marked accessible). Reflects what the feed states, not verified physical usability.

1 accessibility depth signal

  • 2 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set ("Topanga Cyn Blvd and Devonshire Street", "Temporary Stop - Simi Town Center Way & Jefferson Way").

    Consider: Add tts_stop_name with the spoken form, e.g. 'Main Street and Second Avenue', for the affected stops.

Opportunities to strengthen the data, not deductions from the sub-score above. States what the second accessibility lens can check from the feed, not verified physical usability.

FaresFares v2

Fares are applied to trips.

Realtime qualityNot yet measured

Not scored yet. Nothing here counts against the grade.

Routes and stops

Each route is drawn once, using the longest shape its trips follow; stops are the dots.

This feed has 204 stops.

Skip to route and stop data

The route and stop data is ready below. Load the map only when you want the geographic view. It uses additional data.

Basemap: OpenFreeMap, © OpenStreetMap contributors. Routes and stops: this agency's GTFS feed.

  • 10 (teal)
  • 30 (red)
  • 20 (purple)
Routes in Simi Valley Transit's feed
RouteTypeLine color
10Busteal
30Busred
20Buspurple
List every stop
  • Madera Road and Strathern Place
  • Los Angeles Avenue and Madera Road
  • Los Angeles Avenue and Simi Village Drive
  • Los Angeles Avenue and Sinaloa Road
  • Fourth Street on Los Angeles Avenue
  • Los Angeles Avenue and First Street
  • Los Angeles Avenue and Hubbard Street
  • Galt Street on Los Angeles Avenue
  • Erringer Road and Larch Street
  • Erringer Road and Cochran Street
  • Town Center Mall on Jefferson Way
  • Lowe's on Jefferson Way
  • Cochran Street and First Street
  • Cochran Street and Caldwell Avenue
  • Cochran Street and Callahan Avenue
  • Cochran Street and Erringer Road
  • Cochran Street and Justin Avenue
  • Cochran Street and Elmdale Avenue
  • Cochran Street and Sycamore Drive
  • Cochran Street and Galena Avenue
  • YMCA on Cochran Street
  • Cochran Street and Sequoia Avenue
  • Cochran Street and Tracy Avenue
  • Tapo Canyon Road and 118 Freeway
  • Credit Union Plaza on Tapo Canyon Road
  • Tapo Canyon Road and Alamo Street
  • Tapo Canyon Road and Avenida Simi
  • Tapo Canyon Road and Township Avenue
  • Township Avenue and Tapo Street
  • Tapo Street and Fort Worth Drive
  • Tapo Street and Alamo Street
  • Tapo Street and Alamo Street
  • Tapo Street and Eve Road
  • Cochran Street and Tapo Street
  • Cochran Street and Ralston Avenue
  • Pinecrest School on Cochran Street
  • Cochran Street and Summerwood Avenue
  • Cochran Street and Stearns Street
  • Cochran Street and Stow Street
  • Cochran Street and Yosemite Avenue
  • Los Angeles Avenue and Yosemite Avenue
  • Los Angeles Avenue and Stow Street
  • Los Angeles Avenue and Emory Avenue
  • Metrolink Simi Valley
  • Los Angeles Avenue and Ralston Avenue
  • Los Angeles Avenue and Tapo Street
  • Los Angeles Avenue and Bishop Lane
  • Los Angeles Avenue and Surveyor Avenue
  • Los Angeles Avenue and Sequoia Avenue
  • Los Angeles Avenue and Church Street
  • Sycamore Drive and Los Angeles Avenue
  • Sycamore Drive and Heywood Street
  • Sycamore Drive and Elizondo Street
  • Sycamore Drive and Royal Avenue
  • Royal Avenue and Whitcomb Avenue
  • Royal Avenue and Haven Avenue
  • Royal Avenue and Erringer Road
  • Royal Avenue and Crocker Street
  • Royal Avenue and Buckskin Avenue
  • Royal Avenue and First Street
  • El Monte Drive on Royal Avenue
  • Royal Avenue and Sinaloa Road
  • Royal Avenue and Vaquero Drive
  • Madera Road and Bonita Drive
  • Madera Road and Los Angeles Avenue
  • Madera Road and Bonita Drive
  • Madera Road and Royal Avenue
  • Royal Avenue and Naples Court
  • Royal Avenue and Sinaloa Road
  • Royal Avenue and El Monte Drive
  • Royal Avenue and First Street
  • Royal Avenue and Buckskin Avenue
  • Royal Avenue and Crocker Street
  • Royal Avenue and Erringer Road
  • Royal Avenue and Haven Avenue
  • Royal Avenue and Brandon Avenue
  • Sycamore Drive and Royal Avenue
  • Sycamore Drive and Elizondo Avenue
  • Sycamore Drive at Lawson Avenue
  • Sycamore Drive and Los Angeles Avenue
  • Los Angeles Avenue and Sycamore Drive
  • Los Angeles Avenue and Blackstock Avenue
  • Los Angeles Avenue and Sequoia Avenue
  • Los Angeles Avenue and Darrah Avenue
  • Los Angeles Avenue and Tapo Canyon Road
  • Los Angeles Avenue and Bishop Lane
  • Los Angeles Avenue and Tapo Street
  • Los Angeles Avenue and Angus Avenue
  • Metrolink Simi Valley
  • Los Angeles Avenue and Stearns Street
  • Conval. Center on Los Angeles Avenue
  • Los Angeles Avenue and Emory Avenue
  • Los Angeles Avenue and Stow Street
  • Los Angeles Avenue and Yosemite Avenue
  • Yosemite Avenue and Los Angeles Avenue
  • Cochran Street and Yosemite Avenue
  • Cochran Street and Stow Street
  • Cochran Street and Stearns Street
  • Cochran Street and Dover Avenue
  • Cochran Street and Kadota Street
  • Cochran Street and Fig Street
  • Cochran Street and Tapo Street
  • Tapo Street and Barnard Street
  • Tapo Street and Alamo Street
  • Tapo Street and Fort Worth Drive
  • Township Avenue and Tapo Street
  • Township Avenue and Divernon Avenue
  • Tapo Canyon Road and Township Avenue
  • Civic Center at City Hall
  • Regal Cinemas on Tapo Canyon Road
  • Cochran Street and Tapo Canyon Road
  • Cochran Street and Tracy Avenue
  • Cochran Street and Sequoia Avenue
  • Cochran Street and Galena Avenue
  • Cochran Street and Sycamore Drive
  • Cochran Street and Jay Street
  • Cochran Street and Justin Avenue
  • Cochran Street and First Street
  • Cochran Street and First Street
  • Cochran Street and Liberty Way
  • Simi Valley Auto Wrecking at 900 W. Los Angeles Avenue
  • Easy Street on W. Los Angeles Avenue
  • Easy Street and Madera Road
  • Madera Road and Los Angeles Avenue
  • Alamo Street and Tapo Canyon Road
  • Tapo Street and Cochran Street
  • Tapo Street and Eileen Street
  • Tapo Street and Industrial Street
  • Los Angeles Avenue and Yosemite Avenue
  • Los Angeles Avenue and Rory Lane
  • Los Angeles Avenue and Alscot Avenue
  • Kuehner Drive and Menlo Street
  • Topanga Cyn Blvd and Devonshire Street
  • Devonshire Street and Owensmouth Avenue
  • Metrolink Chatsworth
  • Lassen Street and Owensmouth Avenue
  • Kuehner Drive and Menlo Street
  • Los Angeles Avenue and Alscot Avenue
  • Los Angeles Avenue and Anastasia Avenue
  • Los Angeles Avenue and Suede Avenue
  • Tapo Canyon Road and Becky Street
  • Madera Road and Country Club Drive East
  • Madera Road and Sunset Garden Lane
  • Madera Road and Wood Ranch Parkway
  • Country Club Drive and Fresh Meadows
  • Country Club Drive and Red Lakes Place
  • Woodranch Parkway and Country Club Drive
  • Woodranch Parkway and Lake Park Drive North
  • Woodranch Parkway and Lake Park Drive South
  • Woodranch Parkway and N. Martha Morrison
  • Woodranch Parkway and High Meadow Road
  • Woodranch Parkway and S. Martha Morrison
  • Woodranch Parkway and Circle Knoll Drive
  • Long Canyon Road and Twisted Oak
  • Long Canyon Road and Rustic Hills
  • Long Canyon Road and Vineyard Drive
  • First Street and Nonchalant Drive
  • First Street and Mellow Lane
  • First Street and Bennett Street
  • First Street and Fitzgerald Road
  • Royal Avenue and First Street
  • Erringer Road and Royal Avenue
  • Erringer Road and Heywood Street
  • Alamo Street and Broadmoor Avenue
  • Atherwood Avenue at Alamo Street
  • Alamo Street and Wanda Avenue
  • Alamo Street and Sycamore Drive
  • Alamo Street and Reservoir Drive
  • Alamo Street and Galena Avenue
  • Alamo Street and Sequoia Avenue
  • Lemon Drive and Alamo Street
  • Senior Center on Avenida Simi
  • Alamo Street and Santa Lucia Street
  • Alamo Street and Sequoia Avenue
  • Alamo Street and Galena Avenue
  • Alamo Street and Reservoir Drive
  • Simi Hospital on Sycamore Drive
  • Alamo Street and Sycamore Drive
  • Alamo Street and Royal Hills Court
  • Alamo Street at Atherwood Avenue
  • Alamo Street and Broadmoor Avenue
  • Erringer Road and Cochran Street
  • Erringer Road and Larch Street
  • Erringer Road and Heywood Street
  • Ronald Reagan Library on Presidential Drive
  • Flower Glen Street at First Street
  • Tapo Canyon Road Alamo Street
  • Mobile Home Park on Topanga Canyon Road
  • Topanga Canyon Road and Dupont Street
  • Simi Town Center Way and Jefferson Way
  • Islands on Simi Town Center Way
  • 2900 Madera Road
  • Rancho Simi Community Park
  • Erringer Road and Cochran Street
  • Temporary Stop - Simi Town Center Way & Jefferson Way
  • Moorpark College
  • First Street and Cochran Street
  • Cochran Street and Stow Street
  • Town Center Mall on Jefferson Way
  • Los Angeles Avenue and Executive Way
  • Los Angeles Avenue and First Street
  • Los Angeles Avenue and Socrates Avenue
  • Tapo Street and Eileen
  • First Street and Ashland Avenue

Over time

Overall score across the last 4 checks — unchanged since 2026-07-31.

2026-07-25: 56.62026-07-30: 56.62026-07-31: 56.62026-08-01: 56.6
Show the numbers
Overall score by check, with the change from the previous check
CheckScoreChange
2026-07-2556.6 first check
2026-07-3056.6 no change
2026-07-3156.6 no change
2026-08-0156.6 no change

What changed since your last check

  • Correctness no change
  • Freshness no change
  • Rider experience no change

What changed in this feed

Overall grade and score held steady since 2026-07-31.

Same feed file as 2026-07-31; the published zip did not change.

Subscribe to this feed’s changes (Atom) to hear about grade drops in a reader, with no sign-up.

Everything we checked

12 findings, ordered by severity.

Show every finding
  • Error1 instance

    A file is missing a column that GTFS requires.

    Apps may reject the whole file, so riders could lose the affected routes or stops.

    Fix: Add the required column named in the finding to the flagged file. (Often an export setting; ask your vendor if it recurs.)

    Finding code: missing_required_column · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)

  • Error1 instance

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

    Fix: Re-export the feed with a calendar that reaches further out, and set feed_info feed_end_date past your next service change. (Usually one export setting; export on a schedule so it never lapses again.)

    Finding code: scorecard_feed_expired · Read the fix guide · See GTFS Best Practices (opens GTFS Best Practices on an external site)

  • Warning129 instances

    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.

    Fix: Set wheelchair_accessible on every trip. If every vehicle is accessible, this may be one default; otherwise use the value for each trip. (A default or per-trip field in your export.)

    Finding code: scorecard_wheelchair_accessible_unknown · Read the fix guide · See GTFS Schedule reference (opens the GTFS Schedule reference on an external site)

  • Warning61 instances

    Some stops exist in the feed but no trip ever stops at them.

    Riders may walk to a stop where no bus is scheduled to arrive.

    Fix: Remove retired stops from the export, or add them back to the trips that should serve them. (A review pass in your scheduling software.)

    Finding code: stop_without_stop_time · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)

  • Warning10 instances

    10 of 204 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.

    Fix: Set wheelchair_boarding to 1 (accessible) or 2 (not accessible) for every stop. A field survey can start with the busiest stops. (A column in stops.txt; your scheduling software likely has it.)

    Finding code: scorecard_wheelchair_boarding_unknown · Read the fix guide · See GTFS Schedule reference (opens the GTFS Schedule reference on an external site)

  • Warning1 instance

    This feed's service calendar runs out within the next 7 days.

    When the calendar ends, Google Maps and other trip planners drop your agency entirely. Riders see no service at all.

    Fix: Export and publish an updated GTFS feed that covers at least the next 30 days of service. (Usually a re-export from your scheduling software.)

    Finding code: feed_expiration_date7_days · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)

  • Warning1 instance

    Some stops sit far from the route line, going by the feed's own distance values.

    Trip planners may draw the route down the wrong streets or point riders to the wrong corner.

    Fix: Check the flagged stops' shape_dist_traveled against the route shape, and re-generate it on export if they disagree. (Usually an export-tool fix, not hand editing.)

    Finding code: stop_too_far_from_shape_using_user_distance · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)

  • Warning1 instance

    This feed describes flexible (demand-responsive) service but has no booking_rules.txt.

    Riders can see the service area but not how or when to reserve a trip, so they can't actually use the service.

    Fix: Add booking_rules.txt saying how far ahead and how to book (phone, app, or web). (A small file; one rule often covers the whole service.)

    Finding code: scorecard_flex_no_booking_rules · Read the fix guide · See GTFS Schedule reference (opens the GTFS Schedule reference on an external site)

  • Info38 instances

    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.

    Fix: Check the flagged column names for misspellings of standard GTFS fields; remove them if they are vendor extras. (A quick look at the flagged files.)

    Finding code: unknown_column · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)

  • Info10 instances

    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.

    Fix: Check the flagged file name for a typo of a standard GTFS file. Remove it if it is a vendor extra. (A quick look at the flagged file.)

    Finding code: unknown_file · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)

  • Info3 instances

    Service extends far in the future (flagged by the MobilityData validator).

    See the linked rule for what this affects.

    Fix: Review the rule documentation for 'service_extends_far_in_the_future' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)

    Finding code: service_extends_far_in_the_future · See MobilityData GTFS Validator rules (opens the validator rules on an external site)

  • Info3 instances

    Some service dates fall outside the date window set in feed_info.txt.

    feed_info.txt should span every day your service runs, so apps know when the data applies.

    Fix: Widen feed_start_date and feed_end_date to cover all service dates, or fix the dates that fall outside. (Two fields in feed_info.txt, or one export setting.)

    Finding code: service_window_outside_feed_period · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)

Beyond the grade

Opportunities that do not change your grade today: fare detail, on-demand service, and deeper accessibility data.

  • Flex zones are published but no booking_rules.txt is present.

    Consider: Add booking_rules.txt with how far ahead and how to reserve (phone, app, or web).

NTD GTFS readiness Not ready

Resolve this before you certify on the D-10. 1 validator error to resolve. Service data expired 1157 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 1157 days ago, so FTA would find the link out of date.
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 your NTD ID (optional) Different (allowed)
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. 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 729 to NTD ID 90050, and keep the feed value stable. Do not change it solely to make the two values equal.
shapes.txt covers your trips Ready
All 129 trips have a shape in shapes.txt.

In plain words: if you report to the federal transit database, you have to publish a working, up-to-date feed, provide a stable agency_id for each represented reporter, and confirm the feed and P-50 crosswalk each year. This box is a heads-up; your filings are the official check.

A readiness signal mapping this feed to the FTA National Transit Database GTFS requirement (Report Year 2023 onward: a public, valid, current feed, certified annually on the D-10). For RY2026, each represented reporter needs a stable agency_id, unique within the feed and crosswalked to its five-digit NTD ID on P-50; the values do not need to be equal. FTA also requires shapes.txt in the published GTFS: Full Reporters from Report Year 2025, and Reduced, Rural, and Tribal Reporters from Report Year 2026. Not an official determination; your certification is the official check.

Conformance mark Not yet

This feed is close to the conformance mark. 1 validator error to resolve. Service data expired 1157 days ago. States wheelchair access on 95% of stops and 0% of trips; the mark needs 90% of each.

Valid Not yet
1 validator error to resolve.
Current Not yet
Service data expired 1157 days ago.
Accessible Not yet
States wheelchair access on 95% of stops and 0% of trips; the mark needs 90% of each.

In plain words: earn this mark when your feed passes validation, has not expired, and says whether nearly every stop and trip is wheelchair accessible.

A pass credential for a feed that is valid, current, and states wheelchair access on nearly every stop and trip. Accessibility here measures what the feed publishes, not whether a stop is physically usable. How the conformance mark works.

Can riders use it?

Checks beyond structural validation: places where the feed is valid but a rider still could not travel.

  • 61 of 204 boardable stops are never served by any trip. Riders see these stops in apps and on the map but can never catch anything there, which erodes trust in the data. Remove stops no route serves, or add the trips that should call at them.

These do not change the grade. They catch trips with no rideable leg and stops no trip serves, the kind of gap a trip planner trips over.

Clears the Google and Apple Maps four-week coverage bar. This feed has 1613 days of service ahead, clearing the four-week (28-day) window Maps asks for. The feed also carries 1 validator error, the other thing Maps checks at onboarding; the findings below name each fix.

How this agency maps to the standards

The scorecard is a data-quality lens, not a compliance determination. Its universal references describe good GTFS and useful rider information. Useful references here are GTFS Schedule Best Practices, GTFS-Realtime Best Practices, MobilityData grading scheme, Google Transit publication guidance, FTA National Transit Database GTFS requirement. Read the full standards crosswalk.

In California, the published guideline is California Transit Data Guidelines. Caltrans' published quality guidelines and compliance checklist; this rubric is anchored to them.

California Minimum GTFS Guidelines checklist (4 of 6 measured items met)

The state's own Data Process Checklist, matched item by item to what this scorecard already measures. An item marked "not measured here" is real ground the checklist covers that this tool does not check; see the official checklist for the full picture.

  • Meets Publish GTFS Schedule at a stable, automatically-fetchable URL

    The published feed URL downloaded at the last check.

  • Not measured here Implement required fields: Fares v2, text-to-speech stop names, shapes.txt, wheelchair_boarding, and Pathways where applicable

    This scorecard measures wheelchair_boarding, shapes.txt coverage, fare data, and station pathways separately, below; it does not check the Fares v2 format specifically or text-to-speech stop names.

  • Not measured here Achieve a passing score in every category of the MobilityData GTFS Grading Scheme v1

    This scorecard automates a proxy for the Grading Scheme's rider-facing fields (see the standards crosswalk) rather than running the scheme itself, which grades by comparison to the real world by hand.

  • Not measured here Publish changes to the base schedule at least one week ahead of every service change

    This scorecard does not track a feed's publish history, so advance notice cannot be checked.

  • Gap Produce no critical errors in the MobilityData GTFS Validator

    1 validator error to resolve.

  • Not measured here Publish Trip Updates, Vehicle Positions, and Alerts feeds

    This scorecard checks realtime reachability and freshness overall; it does not check for all three feed types individually.

  • Not measured here Update Trip Updates and Vehicle Positions at least every 20 seconds

    This scorecard samples realtime freshness; it does not check this specific 20-second cadence.

  • Not measured here Publish information for at least 99% of vehicles in service

    This scorecard measures the share of scheduled trips represented in TripUpdates, a related but different figure than vehicle coverage.

  • Not measured here Keep 100% of trip_ids consistent between Schedule and Realtime

    This scorecard does not currently check trip_id consistency between the Schedule and Realtime feeds.

  • Not measured here Produce no critical errors in the Center for Urban Transportation Research realtime validator

    This scorecard does not run the CUTR realtime validator.

  • Not measured here Publish accessible feed links on the agency or regional partner website

    This scorecard does not check the agency's own website.

  • Not measured here Register GTFS and GTFS-Realtime feeds with transit.land and the Mobility Database

    This scorecard does not currently check aggregator registration for this section.

  • Meets Designate a technical contact in feed_info.txt's feed_contact_email

    feed_info.txt states a technical contact.

  • Gap wheelchair_boarding stated on stops and trips

    States wheelchair access on 95% of stops and 0% of trips.

  • Meets shapes.txt with a shape for every trip

    All 129 trips have a shape in shapes.txt.

  • Meets Fare data published, or the service marked fare-free

    Fare data is published.

Correctness 70 / 100
GTFS Schedule best practices, checked by the MobilityData validator. MobilityData grading covers stop locations, route names, and colors. Google Transit requires a feed to pass validation for publication. FTA NTD readiness also checks that the published feed is valid.
Freshness 0 / 100
GTFS Schedule best practices call for a dataset that stays current. An expired calendar can remove service from Google Transit and other rider trip planners. FTA NTD readiness also checks that the published feed is current.
Rider experience 84 / 100
GTFS Best Practices for rider-facing fields. MobilityData grading covers stop names and headsigns.
Realtime quality Not yet published
GTFS-Realtime best practices: a stable URL, high uptime, and frequent updates.

Show your grade

Put a badge on your agency site or feed README. It updates after each completed scoring check and links back to this scorecard.

Simi Valley Transit GTFS data quality grade: F

Prefer a shields.io style? Point a dynamic endpoint badge at the published badge.json.

Cite this record

This page updates on every check. The record below does not: it is the dated file this grade came from, published at https://gtfsscorecard.org/data/artifacts/simi-valley-transit/2026-08-01.json and never overwritten, pinning the grade, category scores, rubric version, validator version, reader archive profile, and the scored feed's sha256 as they stood on 2026-08-01. Use it in a board packet, a regulatory filing, or a research citation instead of linking the live page, whose content will differ on your next visit.

Citing the tool itself rather than one agency's record? Use the repo's CITATION.cff.