Feed status · checked 2026-08-01
Santa Maria Area Transit
Based on the feed this agency publishes
Service mode Bus
unchanged since 2026-07-31
Catalogued in California.
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 12 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
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 1735 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
Review the rule documentation for 'missing_required_field' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.
Missing required field (flagged by the MobilityData validator). See the linked rule for what this affects.
⏱ Varies.worth about +18 points in its category
Review the rule documentation for 'invalid_currency_amount' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.
Invalid currency amount (flagged by the MobilityData validator). See the linked rule for what this affects.
⏱ Varies.worth about +18 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 1735 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
- Feed evidence
- Missing required field (flagged by the MobilityData validator).
- Next action
- Review the rule documentation for 'missing_required_field' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.
- 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
- Feed evidence
- Invalid currency amount (flagged by the MobilityData validator).
- Next action
- Review the rule documentation for 'invalid_currency_amount' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.
- 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.
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.
Review the rule documentation for 'missing_required_field' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.
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.
Review the rule documentation for 'invalid_currency_amount' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. · 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 1735 days ago.
- Published accessibility data
- Accessibility information is stated for 1.2% 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
The MobilityData validator flagged 10 kinds of issue across 127 instances (28 error, 8 warning, 91 informational).
Service data ended 1735 day(s) ago. Trip planners have likely already dropped this feed.
1% of stops state wheelchair accessibility (1% marked accessible, 0% marked not accessible). This measures what the feed publishes, not whether a stop is physically usable. Fare data is published.
1% of stops state accessibility (1% marked accessible). Reflects what the feed states, not verified physical usability.
3 accessibility depth signals
5 route badge(s) pair a color and text color below the WCAG 4.5:1 contrast bar (2, 3, 4, 6, 8).
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.
42 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set ("Orcutt Rd at Lakeview (Evergreen Shopping Ctr)", "Buellton 2nd/Ave of the Flags", "Buellton 2nd/Ave of the Flags", and more).
Consider: Add tts_stop_name with the spoken form, e.g. 'Main Street and Second Avenue', for the affected stops.
This feed models stations or entrances but has no pathways.txt and levels.txt.
Consider: Add pathways.txt connecting entrances, platforms, and elevators, and levels.txt for each floor, so the step-free route is described.
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.
Fares are applied to trips.
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 249 stops.
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.
- 1 (red)
- 2 (teal)
- 3 (green)
- 4 (yellow)
- 5 (green)
- 6 (red)
- 7 (purple)
- 8 (pink)
- 100 (teal)
- 200 (teal)
| Route | Type | Line color |
|---|---|---|
| 1 Hidden Pines/Broadway/Transit Center | Bus | red |
| 2 Transit Center/Taylor/Mussel Senior Center/McCoy | Bus | teal |
| 3 Transit Center/Marian Hospital/Merril Gardens/Allan Hancock College | Bus | green |
| 4 Transit Center/Miller/Edwards Community Center/Town Center Mall/VTC/Airport | Bus | yellow |
| 5 Downtown/Blosser/Old Orcutt/Rice Ranch/Oak Knoll | Bus | green |
| 6 Oak Knoll/Rice Ranch/Old Orcutt/Blosser/Downtown | Bus | red |
| 7 Transit Center/Allan Hancock College/Crossroads/McCoy/Lakeview Road | Bus | purple |
| 8 McCoy/Tanglewood | Bus | pink |
| 100 Breeze | Bus | teal |
| 200 Breeze | Bus | teal |
List every stop
- Stillwell at Rhinestone (Greenbelt)
- Orcutt Rd at Lakeview (Evergreen Shopping Ctr)
- McCoy at Sandpiper
- Buellton 2nd/Ave of the Flags
- Buellton 2nd/Ave of the Flags
- Foster at California
- College at Park (Allan Hancock College)
- Lompoc Transit Center
- SM Transit Center 1
- SM Transit Center 2N
- SM Transit Center 3N
- SM Transit Center 4N
- SM Transit Center 6
- SM Transit Center 5
- SM Transit Center 4S
- SM Transit Center 2S
- SM Transit Center 200
- SM Transit Center 100
- SM Transit Center 7
- SM Transit Center 3S
- SM Transit Center
- Broadway at Mill
- Broadway at Tunnell
- Broadway at Alvin
- Broadway at Orchard
- Broadway at Williams
- Broadway at Taylor
- Taylor at Broadway
- Taylor at Casa Grande
- Railroad Ave at Taylor St
- Railroad Ave at Hidden Pines Way
- Hidden Pines Way at Preisker Park
- Preisker Ln at Cedar
- Broadway at Taylor
- Broadway at Williams
- Broadway at Orchard
- Broadway at Agnes
- Broadway at McElhany
- Broadway at Hermosa
- Broadway at Fesler
- Miller at Orange (Cook)
- Cook at Pine
- Cook at Western
- Western at Main
- Western at Alvin
- Western at Harding
- Western at Creston
- Taylor at Western
- Railroad at Taylor
- Railroad at Creston
- Railroad at Donovan
- Railroad at Alvin
- Depot at Mill
- College at Boone
- Park at Elizabeth (Mussell Senior Center)
- Miller at Stowell
- Miller at Enos
- Miller at Battles
- Miller at Inger
- Miller at Daniel And Betteravia
- Betteravia at Target
- McCoy at FoodMaxx
- Miller at Betteravia (County Government Center)
- Miller at E Inger
- Miller at E Battles
- Miller at E Enos
- Miller at Morrison
- Park at Oakwood
- College at Park (Allan Hancock College)
- Main at College
- Cypress at S Nicholson
- Church at S Palisade (Marian Regional Medical Center)
- Main at Palisades
- Suey at Fesler
- Suey at Alvin
- Donovan at Merrill Gardens
- Suey Rd Crossing at Seapark Dr
- Suey at Alvin
- Suey at Main
- Church at N Palisades
- Cypress at N Nicholson
- Jones at College (Allan Hancock College)
- Bradley at Jones (Allan Hancock College)
- Bradley at Sierra Madre
- College at Mariposa
- College at Allan Hancock Field (Back Entrance)
- Miller at Bunny
- Miller at Orchard
- Donovan at Magellan
- Donovan at Canyon
- Panther at Centennial
- Panther at Domingues (Pioneer Valley High School)
- Donovan at Charlie
- Donovan at Canyon
- Donovan at College
- Miller at Donovan
- Miller at McElhany
- Miller at Fesler
- Pine at Cook
- Pine at Jones
- Pine at Morrison
- Morrison at Thornburg (CET)
- Morrison at Oakley
- Morrison at Western
- Western at Stowell
- Enos at Depot (Minami Center)
- Enos at Thornburg
- Thornburg at Newlove
- Thornburg at Sonya
- Thornburg at Carmen
- Thornburg at Betteravia
- Betteravia at Blosser
- Carmen Ln at Trinity
- A St at Carpenters Training Union
- A St at Vocational Training Center
- Fairway at Skyway
- Santa Maria Public Airport
- A St at Betteravia
- Carmen Ln at Trinity Dr
- Betteravia at Bakery Outlet
- Thornburg at Dal Porto
- Thornburg at Carmen
- Thornburg at Sonya
- Thornburg at Battles
- Enos at Wallis
- Enos at Depot
- Stowell at Western
- Morrison at Western
- Morrison at Depot
- Morrison at Thornburg (Santa Maria High School)
- Pine at Jones
- Cook at Pine
- Town Center Mall
- Broadway at Jones
- Broadway at Morrison (Santa Maria High School)
- Broadway at Enos
- Broadway at Newlove
- Broadway at Carmen Ln
- Betteravia at Panda Express
- McCoy at Albertsons
- Foster Across Foodbank
- Foster at California
- Airport Mobile Home Park
- Blosser Rd at Foxenwood
- Blosser at Solomon
- Clark Ave at Broadway
- Clark Ave at Dyer
- Orcutt Rd at Clark (Jack N The Box)
- Orcutt Rd at Valley View
- Rice Ranch at Orcutt Rd
- Rice Ranch at Princeton
- Rice Ranch Rd at Bradley
- Clark Ave at Oak Knolls Shopping Center
- Clark at Kenneth
- Clark at Oak Ridge Park
- Stillwell at Cameo
- Oak Knolls at Kenneth
- Oak Knolls at Tilbury
- Bradley at Patterson
- Bradley at Village Dr
- Bradley at Parkland
- Foster at Bradley (Righetti High School)
- Foster at Hillview
- Foster at YOYO Youth Center
- Foster at Dartmouth
- Foster at Jetty
- Broadway at Starbuck's
- Broadway at CVS Pharmacy
- Broadway at Newlove
- Broadway at Battles
- Broadway at Stowell
- Broadway at Morrison (Across Santa Maria High School)
- Broadway at Jones
- Orcutt Rd at Lakeview
- Foster Rd at Michelle
- Foster Rd at Lockford
- Bradley at Foster Rd (Righetti High School)
- Bradley at Country Hill
- Bradley at Basque
- Oak Knolls at Sweetbriar
- Oak Knolls at Harmony Ln
- Stillwell at Cameo (Green Belt)
- Clark at Kenneth
- Clark Ave at Oak Knolls Shopping Center
- Rice Ranch at Princeton
- Rice Ranch Rd at Orcutt Rd
- Orcutt Rd at Valley View
- Orcutt Rd at Clark
- Clark Ave at Pacific
- Blosser Rd at Old Mill
- Foster at Foodbank
- Santa Maria Way at K-Mart Center
- McCoy at Eastbury
- McCoy at Depot
- McCoy at Skyway
- Lakeview at Orcutt Rd (Evergreen Shopping Ctr)
- Lakeview at Hillview
- Santa Maria Way at College
- Santa Maria Way at Del Cielo Mobile Hm Prk
- Santa Maria Way at Drive-In
- Santa Maria Way at Broadway
- Bradley at Costco (Edwards Cinema)
- Bradley at Southside Parkway (Walmart)
- Crossroads at Del Sur
- Orcutt at Winter (Evergreen Shopping Center)
- McCoy at Caballero
- Crossroads at Del Sur
- Bradley at Crossroads (Walmart)
- Southside Pkwy at Volkswagon
- Bradley at Sierra Madre (Olive Garden)
- Jones at Vineyard Apartments
- McCoy at Thompson
- McCoy at Westgate
- Sandalwood at Black Rd
- Tanglewood at Willowood
- Tanglewood at Black Rd
- Betteravia at Blosser (McDonald's)
- Mccoy at Broadway
- Orcutt Rd at Foster
- Vandenberg Air Force Base at Main Gate
- Vandenberg Village
- Mission Plaza
- Mccoy at Broadway (Professional Pkwy)
- County Government Center
- Los Alamos
- Buellton Albertsons
- Solvang
- Main at Broadway (North Town Center Mall)
- Miller at Chapel
- Donovan at 1133 Donovan
- Donovan at Pepperwood
- Blosser at Rick
- Rice Ranch at Domino
- Denmat
- Miller at Cook
- Bradley at Stowell
- Orcutt Rd at Clark
- Broadway at Stowell
- Santa Maria Way at Sunrise
- Mccoy at Skyway
- Santa Maria Way at Del Cielo Mobile Hm Prk
- Buellton Freear/SR 246
- Clark Avenue Park-and-Ride (East)
- Orcutt Rd at Foster
- Hidden Pines at Railroad
- Railroad at El Camino
- Main at Ranch
- Santa Maria Way at Holly Oak
- Lakeview at Lakeview
Over time
Overall score across the last 4 checks — unchanged since 2026-07-31.
Show the numbers
| Check | Score | Change |
|---|---|---|
| 2026-07-25 | 33.6 | first check |
| 2026-07-30 | 33.6 | no change |
| 2026-07-31 | 33.6 | no change |
| 2026-08-01 | 33.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
15 findings, ordered by severity.
Show every finding
- Error18 instances
Missing required field (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'missing_required_field' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Finding code: missing_required_field · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Error9 instances
Invalid currency amount (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'invalid_currency_amount' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Finding code: invalid_currency_amount · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- 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 1735 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)
- Warning710 instances
710 of 710 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)
- Warning246 instances
246 of 249 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)
- Warning3 instances
Some service calendars in the feed have already ended.
Expired calendars are dead weight and can hide real schedule problems from your staff and vendors.
Fix: Remove past service periods the next time you export the feed. (One setting in most export tools.)
Finding code: expired_calendar · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning3 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)
- 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
Many of the feed's trips don't run at all in the next 7 days.
It usually means old service periods are still in the export, making the feed bigger and harder to check.
Fix: Trim past service periods the next time you export. (One setting in most export tools.)
Finding code: trip_coverage_not_active_for_next7_days · 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)
- Warning1 instance
This feed models stations or entrances but has no pathways.txt.
Trip planners can't guide riders through the station, and there is no step-free route information for wheelchair users.
Fix: Add pathways.txt connecting entrances, platforms, and any elevators, with a level for each. (Worth it for multi-level or large stations; flat stops don't need it.)
Finding code: scorecard_station_no_pathways · Read the fix guide · See GTFS Schedule reference (opens the GTFS Schedule reference on an external site)
- Info79 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)
- Info9 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
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.
The feed publishes fare products but no fare_media.txt declaring how riders can pay.
Consider: Add fare_media.txt listing your accepted payment methods, including contactless EMV if riders can tap to pay.
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. 3 validator errors to resolve. Service data expired 1735 days ago, so FTA would find the link out of date.
- Published Ready
- Published at a public URL.
- Valid Needs attention
- 3 validator errors to resolve.
- Current Not ready
- Service data expired 1735 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) 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 710 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. 3 validator errors to resolve. Service data expired 1735 days ago. States wheelchair access on 1% of stops and 0% of trips; the mark needs 90% of each.
- Valid Not yet
- 3 validator errors to resolve.
- Current Not yet
- Service data expired 1735 days ago.
- Accessible Not yet
- States wheelchair access on 1% 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.
- 3 of 248 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.
Below the Google and Apple Maps four-week coverage bar. This feed's last day of service has passed, so Google and Apple Maps will stop showing your agency. Re-export with a calendar that covers at least the next four weeks. The feed also carries 28 validator errors, 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
3 validator errors 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 1% of stops and 0% of trips.
- Meets shapes.txt with a shape for every trip
All 710 trips have a shape in shapes.txt.
- Meets Fare data published, or the service marked fare-free
Fare data is published.
- Correctness 34 / 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 60 / 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.
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/santa-maria-area-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.