GTFS Scorecard
← All agencies

Feed status · checked 2026-08-01

Spirit Bus

Based on the feed this agency publishes

Service mode Bus

66.7 / 100

up 8.0 since 2026-07-31 · F → D

Catalogued in California.

Covers 30 daysAccessibility gaps

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 69 minutes ago; last changed 69 minutes ago.

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

How we measured this

Confidence in this measurement: high.

  • All four score categories were measured this run.
  • Realtime was sampled in one bounded window of 9 snapshots.
  • 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

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

214 of 214 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.

⏱ A column in stops.txt; your scheduling software likely has it.worth about +25 points in its category

Fix 02

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

72 of 72 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

Fix 03

Add the destination, direction, or 'via' label riders actually see to trip_headsign. Do not copy the route name. If the label changes during the trip, use stop_headsign.

72 of 72 trips lack rider-facing destination or direction text. When a route has multiple directions or patterns, the route name alone may not tell riders which service is coming.

⏱ Usually one value per route pattern in your scheduling source.worth about +15 points in its category

This feed is generated by your Passio system from the route and stop data they maintain. Send the fix list to your Passio contact.

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
214 of 214 stops don't say whether a wheelchair user can board there.
Next action
Set wheelchair_boarding to 1 (accessible) or 2 (not accessible) for every stop. A field survey can start with the busiest stops.
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. Set wheelchair_boarding to 1 (accessible) or 2 (not accessible) for every stop. A field survey can start with the busiest stops. · Read the fix guide

    Make the change. This feed is generated by your Passio system from the route and stop data they maintain. Send the fix list to your Passio contact.

    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. See this feed's finding-clearance log.

  2. 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. This feed is generated by your Passio system from the route and stop data they maintain. Send the fix list to your Passio contact.

    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. See this feed's finding-clearance log.

  3. Add the destination, direction, or 'via' label riders actually see to trip_headsign. Do not copy the route name. If the label changes during the trip, use stop_headsign. · Read the fix guide

    Make the change. This feed is generated by your Passio system from the route and stop data they maintain. Send the fix list to your Passio contact.

    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. See this feed's finding-clearance log.

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 is in 30 days.
Published accessibility data
Accessibility information is stated for 0% of stops and 0% of trips. This measures published data, not whether stops or vehicles are physically usable.
Fare information
No fare information is published in the feed.
Realtime information
One or more realtime feeds were reachable; live-arrival coverage is not known.

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

Send Passio a fix request

This feed is generated by your Passio system. Copy this and send it to your Passio contact; the fixes apply to the route and stop data behind your AVL setup. Each fix names the validator notice and a guide link.

Score by category

Correctness83.5 / 100

The MobilityData validator flagged 4 kinds of issue across 129 instances (0 error, 128 warning, 1 informational).

Freshness50.0 / 100

Service data covers the next 30 days.

Rider experience30.0 / 100

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

Accessibility0 / 100

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

2 accessibility depth signals

  • 4 route badge(s) pair a color and text color below the WCAG 4.5:1 contrast bar (Route 1, Route 2, Route 3, Route 4).

    Consider: Adjust route_color or route_text_color so each pair clears 4.5:1. Often switching the text between black and white is enough.

  • 81 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set ("1st /Schoolside", "Alhambra Ave", "Arriba/Copa", and more).

    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.

Realtime quality100.0 / 100

Sampled 9 times outside service hours: 3 of 3 configured feeds healthy; vehicle position plausibility was not measurable.

Routes and stops

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

This feed has 214 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.

  • Route 1 (pink)
  • Route 2 (orange)
  • Route 3 (gray)
  • Route 5 (yellow)
Routes in Spirit Bus's feed
RouteTypeLine color
Route 1Buspink
Route 2Busorange
Route 3Busgray
Route 4Busgray (no shape in feed)
Route 5Busyellow
List every stop
  • Fulton Avenue and Ackley
  • Ackley Street and Harrison Road
  • S Orange Avenue and Ackley Street
  • Emerson and Alhambra
  • N Alhambra Avenue and E Garvey Avenue
  • Arriba/Copa
  • S Atlantic Boulevard and Brightwood Street NE
  • S Atlantic Boulevard and Brightwood Street SW
  • S Atlantic Boulevard and Cadiz Street NW
  • S Atlantic Boulevard and Cadiz Street SE
  • S Atlantic Boulevard and Avenida Cesar Chavez
  • S Atlantic Boulevard and El Portal Place
  • Atlantic Blvd and El Portal
  • S Atlantic Boulevard and W El Repetto Drive
  • N Atlantic Boulevard and W Emerson Avenue SE
  • N Atlantic Boulevard and W Emerson Avenue SW
  • Floral and Atlantic
  • S Atlantic Boulevard and W Floral Drive
  • Atlantic/Garvey NE
  • Atlantic/Garvey SW
  • S Atlantic Boulevard and Harding Avenue SE
  • S Atlantic Boulevard and Harding Avenue NW
  • S Atlantic Boulevard and W Newmark Avenue
  • S Atlantic Boulevard and Sevilla Street NE
  • S Atlantic Boulevard and Sevilla Street SW
  • Atlas Avenue and Saturn Street
  • Brier Cliff Way and Crest Vista Drive
  • Brightwood Street and Lunar Drive
  • Brightwood/Sunnyslope
  • Casuda Canyon Drive and Copa Way
  • Casuda Canyon Drive and Verde Vista Drive
  • Corporate Center Drive (900) E
  • Corporate Center Drive (900) W
  • Corporate Center Drive and Casuda Canyon Drive SE
  • Corporate Center Drive and Casuda Canyon Drive SW
  • Corporate Center Drive and Corporate Place E
  • Corporate Center Drive and Corporate Place NW
  • Corporate Center Drive and Davidson Drive NE
  • Corporate Center Drive and Davidson Drive W
  • Crest Vista Drive and College View Drive N
  • Crest Vista Drive and Rolling Hill Drive
  • Elizabeth Avenue and E Garvey Avenue
  • Garfield Avenue and Elmgate
  • E Emerson Avenue and N Alhambra Avenue
  • E Emerson Avenue and Florence Avenue
  • E Emerson Avenue and N Garfield Avenue
  • W Emerson Avenue and N Mc Pherrin Avenue
  • Emerson and McPherrin
  • W Emerson Avenue and N Moore Avenue SW
  • Emerson and Rural
  • E Emerson Avenue and N Rural Drive
  • Floral Drive and Corporate Center Drive S
  • W Floral Drive and Crest Vista Drive
  • W Floral Drive and Hillside Street NE
  • W Floral Drive and Hillside Street SW
  • Fulton Avenue and Keller Street
  • Fulton Avenue and Kempton Avenue (835)
  • Fulton Avenue and Wilcox Avenue
  • Garfield Avenue S and Coral View Street SE
  • Garfield Avenue S and Coral View Street W
  • Garfield Avenue and Elmgate NE
  • Garfield Avenue and Elmgate SE
  • N Garfield Avenue and E Emerson Avenue
  • Garfield Avenue and Emerson
  • N Garfield Avenue and E Garvey Avenue
  • Garfield Avenue S and E Graves Avenue SE
  • Garfield Avenue S and E Graves Avenue SW
  • E Hellman Avenue and N Garfield Avenue
  • Garfield Avenue and Keller
  • Garfield Avenue S and Maronde Way W
  • Garfield Avenue and Med Ctr (600)
  • W Riggin Street and Garfield Avenue S
  • Garvey and Atlantic
  • Garvey Avenue and S Atlantic Avenue
  • Garvey and Casuda Canyon
  • Casuda Canyon Drive and Garvey Avenue
  • Garvey Avenue and S Chandler Avenue NE
  • Garvey Avenue and S Chandler Avenue SE
  • E Garvey Avenue and S Garfield Avenue
  • Garvey Avenue and Hitchcock Drive
  • E Garvey Avenue and S Orange Avenue
  • Garvey Avenue at Orthodox Church
  • Garvey Avenue and S Ramona Avenue
  • Garvey Avenue and Ynez
  • Graves and Alhambra
  • Orange and Graves
  • E Hellman Avenue and N Alhambra Avenue
  • E Hellman Avenue and N Garfield Avenue
  • Fulton Avenue and Kempton Avenue (835)
  • N Mc Pherrin Avenue and W Emerson Avenue
  • Monterey Pass (1st)
  • Monterey Pass (3rd)
  • Monterey Pass Road and Davidson Drive
  • Monterey Pass and Vagabond
  • Orange (409 S)
  • Orange (410 S)
  • S Orange Avenue and E Garvey Avenue
  • Orange and Garvey
  • S Orange Avenue and E Graves Avenue
  • S Orange Avenue and Metro Drive
  • Orange and Newmark SE
  • Orange and Newmark SW
  • S Orange Avenue and Pepper Street
  • Potrero Grande/Greenwood
  • W Ramona Boulevard and Center Plaza Drive N
  • W Ramona Boulevard and Center Plaza Drive SW
  • Ramona and Garvey SE
  • Ramona and Garvey SW
  • City Hall
  • Ramona and Newmark
  • Ridgecrest Street and Brier Cliff Way
  • Ridgecrest Street and Hillside Street
  • Ridgecrest Street and Vagabond Drive
  • Atlantic/Riggin
  • W Riggin Street and S Bradshawe Avenue NE
  • W Riggin Street and S Bradshawe Avenue SW
  • Riggin and Ferdinand
  • W Riggin Street and Findlay Avenue NW
  • W Riggin Street and Findlay Avenue SW
  • E Riggin Street and Fulton Avenue
  • Riggin and Fulton
  • W Riggin Street and Garfield Ave
  • W Riggin Street and Garfield Avenue S SW
  • W Riggin Street and Gerhart Avenue SE
  • E Riggin Street and Wilcox Avenue NW
  • E Riggin Street and Wilcox Avenue SE
  • Saturn Street (1980)
  • Saturn and Potrero Grande
  • 1st /Schoolside
  • Wilcox Avenue and E Arlight Street
  • S Atlantic Boulevard and W El Repetto Drive
  • S Atlantic Boulevard and Harding Avenue
  • S Atlantic Boulevard and W Newmark Avenue
  • Schoolside Avenue and Avenida Cesar Chavez
  • Elizabeth Avenue and E Garvey Avenue 2
  • E Emerson Avenue and Florence Avenue
  • N Garfield Avenue and W Emerson Avenue
  • Floral and Valley Vista
  • Garfield Avenue S and El Repetto Drive
  • Garfield Avenue S and W El Repetto Drive
  • Garfield Avenue S and Maronde Way E
  • W Riggin Street and Garfield Avenue S
  • Schoolside Avenue and Avenida Cesar Chavez
  • Floral Drive and Corporate Center Drive N
  • Floral Drive and Monterey Pass Road NE
  • Floral Drive and Monterey Pass Road SE
  • Garvey Avenue and Abajo Drive
  • Garvey Avenue and S Ramona Avenue
  • Potrero Grande/Markland
  • Wilcox/Arlight
  • Riggin and Gerhert Ave
  • Emerson and Nicholson Ave
  • Collegian Ave at Avenida Cesar Chavez
  • Riggin St and Atlantic Blvd
  • Garfield Avenue and El Repetto
  • Graves and Russel Ave
  • Lincoln Ave and Kempton Ave
  • Atlantic Blvd and Emerson
  • Casuda Canyon Drive and Ladera st
  • Garvey Avenue and Atlantic Blvd
  • Floral Drive and Mednik Ave
  • Elac Transit Center
  • S Garfield Ave and
  • Circle Drive
  • W Riggin St. and Atlantic SE
  • Emerson Park
  • Crest Vista Drive and College View Drive S
  • CSULA (Cal State) Station
  • Garvey Ave and Ynez
  • Atlantic Blvd and Garvey
  • Atlantic Blvd and Harding
  • Atlantic Blvd and Sevilla st
  • Atlantic Blvd and El Reppeto
  • Atlantic Blvd and Brightwood
  • Emerson and Garfield
  • Garfield Avenue and Newmark Ave
  • Garfield Avenue and Graves
  • Garfield Avenue and El Reppeto
  • Emerson and Florence
  • Elizabeth and Garvey
  • Orange and Newmark
  • Russel and Newmark
  • Alhambra and Peach
  • Avenida Cesar Chavez and Collegian
  • Garfield Avenue and Coralview
  • Atlantic Blvd and Cadiz St
  • Atlantic Blvd and Avenida Cesar Chavez
  • First Street and School Side
  • School Ave. and Avenida Cesar Chavez
  • Atlantic Blvd and Cesar Chavez
  • Atlantic Blvd and Newmark
  • Hellman Ave and Garfield
  • Hellman Ave and Alahambra
  • Newmark and Ramona
  • Ynez and Garvey
  • Garfield Ave and Bank of America
  • Riggin and Findlay
  • Riggin and Garfield
  • Riggin and Bradshaw
  • Avenidad Cesar Chavez and Atlantic
  • Corporate Center and 710 Freeway
  • Corporate Center and Monterey Hill
  • Orange and Orange 415
  • Orange and Orange 408-402
  • Garfield Avenue and Elmgate 1
  • Riggin & Garfield 1
  • Floral and Valley Vista 2
  • Mark Keppel High School
  • El Repetto Elementary School
  • Alhambra Ave
  • Lincoln Hotel
  • Riggin and Garfield
  • Langley Senior Citizen Center
  • Ynez Elementary School

Over time

Overall score across the last 2 checks — up 8.0 since 2026-07-31.

2026-07-31: 58.72026-08-01: 66.7
Show the numbers
CheckScoreChange
2026-07-3158.7 first check
2026-08-0166.7 up 8.0

What changed since your last check

  • Correctness no change
  • Freshness no change
  • Rider experience no change
  • Realtime quality up 40.0

What changed in this feed

Grade improved from F to D since 2026-07-31.

The feed file was re-published since 2026-07-31.

No longer reported since 2026-07-31 (2 findings)

  • 4 of 9 sampled vehicle positions were far from their assigned route (worst: 2994 m). (scorecard_rt_vehicles_off_route)
  • 1 of 1 trips scheduled during the sampling window had no live predictions. (scorecard_rt_trip_coverage)

This records the later feed state. It does not establish who made a change or why.

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

What changed over time

On 2026-07-31 this feed started at grade F. On 2026-08-01 the grade moved from F to D. On 2026-08-01 the check no longer reported: 1 of 1 trips scheduled during the sampling window had no live predictions; 4 of 9 sampled vehicle positions were far from their assigned route (worst: 2994 m). As of 2026-08-01 it holds grade D.

A plain-language history of this feed, newest first.

  • 2026-08-01 Grade went F to D, realtime rose 40 points.

Everything we checked

8 findings, ordered by severity.

Show every finding
  • Warning214 instances

    214 of 214 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

  • Warning126 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

  • Warning72 instances

    72 of 72 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

  • Warning72 instances

    72 of 72 trips lack rider-facing destination or direction text.

    When a route has multiple directions or patterns, the route name alone may not tell riders which service is coming.

    Fix: Add the destination, direction, or 'via' label riders actually see to trip_headsign. Do not copy the route name. If the label changes during the trip, use stop_headsign. (Usually one value per route pattern in your scheduling source.)

    Finding code: scorecard_missing_headsigns · Read the fix guide · See GTFS Best Practices

  • Warning1 instance

    Some scheduled trips move faster between stops than a bus can.

    Usually a typo'd stop time; riders get arrival times no bus can meet.

    Fix: Check the flagged stop times for transposed minutes. (A few minutes per flagged trip.)

    Finding code: fast_travel_between_consecutive_stops · Read the fix guide · See MobilityData GTFS Validator rules

  • Warning1 instance

    On some trips the stops fall along the route line in a different order than the schedule lists.

    Trip planners can draw the bus doubling back or skipping ahead, which confuses riders reading the map.

    Fix: Check the stop order and the shape direction in your scheduling software; the shape is often drawn backwards. (A few minutes per flagged trip.)

    Finding code: stops_match_shape_out_of_order · See MobilityData GTFS Validator rules

  • Warning1 instance

    The feed contains no fare information.

    Riders see 'fare unknown' in trip planners and can't budget their trip; visitors are most affected.

    Fix: Add fare_attributes.txt (or Fares v2 files) with your fare structure. If your service is fare-free, ask to have it marked fare-free instead. (A small file for most flat-fare systems.)

    Finding code: scorecard_no_fare_data · Read the fix guide · See GTFS Best Practices

  • Info1 instance

    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

NTD GTFS readiness Needs attention

This feed is close to NTD-ready. Service data runs out in 30 days; renew before you certify.

Published Ready
Published at a public URL.
Valid Ready
Passes validation with no errors.
Current Needs attention
Service data runs out in 30 days; renew before you certify.
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) Not checked yet
This feed provides agency_id. For RY2026, keep one stable value for each NTD reporter represented in the feed and crosswalk it on the P-50 form. The value does not need to equal the five-digit NTD ID; we do not have that ID on file, so the optional equality comparison is not checked yet.
shapes.txt covers your trips Ready
All 72 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. Service data runs out in 30 days; renew to qualify. States wheelchair access on 0% of stops and 0% of trips; the mark needs 90% of each.

Valid Met
Passes validation with no errors.
Current Not yet
Service data runs out in 30 days; renew to qualify.
Accessible Not yet
States wheelchair access on 0% 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.

  • 126 of 214 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.

Realtime reliability

The realtime feed responded on 100.0% of 200 checks over the last 34 days, with 4s median lag.

Sampled on a schedule between full scores, so this tracks uptime and freshness over time rather than at a single moment.

Clears the Google and Apple Maps four-week coverage bar. This feed has 517 days of service ahead, clearing the four-week (28-day) window Maps asks for. No validator errors either, so riders keep seeing this agency in their trip planners; warnings lower the grade here but do not remove a feed from Maps.

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.

  • Meets Produce no critical errors in the MobilityData GTFS Validator

    Passes validation with no errors.

  • 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 0% of stops and 0% of trips.

  • Meets shapes.txt with a shape for every trip

    All 72 trips have a shape in shapes.txt.

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

    No fare data is published.

Correctness 84 / 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 50 / 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 30 / 100
GTFS Best Practices for rider-facing fields. MobilityData grading covers stop names and headsigns.
Realtime quality 100 / 100
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.

Spirit Bus GTFS data quality grade: D

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/spirit-bus-2202/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.