Feed status · checked 2026-09-13
City of San Luis Obispo Transit
Based on a Mobility Database mirror copy of the feed source on file; publisher ownership is not verified
Service mode Bus
unchanged since 2026-09-12
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 30 hours ago; last changed 85 days ago; last fetch returned HTTP 404.
Measured 4 of 4 score categories from the Mobility Database's mirror copy of the feed.
How we measured this
Confidence in this measurement: medium.
- All four score categories were measured this run.
- Realtime was sampled in one bounded window of 9 snapshots.
- The configured feed URL was unreachable, so the Mobility Database's hosted mirror copy was scored instead. Publisher ownership of the configured URL is not verified.
Confidence describes how much the pipeline could measure this run, not the feed itself. It never changes the grade.
Top things to fix
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
157 of 165 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 +24 points in its category
Turn on shape cleanup in your export tool, or drop the repeated points from shapes.txt.Likely your export tool
Some route lines list the same point twice in a row. Repeated points don't hurt riders, but they can skew distance math and hint at a shaky export.
⏱ Usually one export setting.worth about +8 points in its category
Remove past service periods the next time you export the feed.Likely your export tool
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.
⏱ One setting in most export tools.worth about +4 points in its category
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
- 157 of 165 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
- Feed evidence
- Some route lines list the same point twice in a row.
- Next action
- Turn on shape cleanup in your export tool, or drop the repeated points from shapes.txt.
- 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
- Some service calendars in the feed have already ended.
- Next action
- Remove past service periods the next time you export the 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.
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 for scorecard_wheelchair_boarding_unknown
Make the change. Make this change in whatever tool produces your feed, then re-export.
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.
Turn on shape cleanup in your export tool, or drop the repeated points from shapes.txt. · Read the fix guide for equal_shape_distance_same_coordinates
Make the change. Make this change in whatever tool produces your feed, then re-export.
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.
Remove past service periods the next time you export the feed. · Read the fix guide for expired_calendar
Make the change. Make this change in whatever tool produces your feed, then re-export.
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 110 days.
- Published accessibility data
- Accessibility information is stated for 4.8% of stops and 100% of trips. This measures published data, not whether stops or vehicles are physically usable.
- Fare information
- Fare information is published using GTFS Fares v1.
- 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 your vendor a fix request
You may not control the GTFS export yourself. Copy this and send it to whoever runs your scheduling software export. It names each fix with the validator notice and a guide link.
Score by category
The MobilityData validator flagged 5 kinds of issue across 253 instances (0 error, 228 warning, 25 informational).
Service data covers the next 110 days.
5% of stops state wheelchair accessibility (5% marked accessible, 0% marked not accessible). This measures what the feed publishes, not whether a stop is physically usable. Fare data is published.
5% of stops state accessibility (5% 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 (2B, 3A, 4B, Old SLO Trolley).
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.
2 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set ("Madonna Rd at Madonna Plaza (W)", "Madonna Rd at Madonna Plaza").
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.
Fares are applied to trips.
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 165 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.
- 1B (purple)
- 3B (yellow)
- 2B (teal)
- 1A (black)
- 2A (blue)
- 3A (red)
- 4A (green)
- 4B (green)
- LT (yellow)
- 6X (red)
- Old SLO Trolley (teal)
| Route | Type | Line color |
|---|---|---|
| 1B Broad/Airport/Johnson | Bus | purple |
| 3B Cal Poly/LOVR/Amtrak | Bus | yellow |
| 2B Madonna/LOVR/Higuera | Bus | teal |
| 1A Johnson/Tank Farm/Airport | Bus | black |
| 2A Higuera/LOVR/Madonna | Bus | blue |
| 3A Promenade/LOVR/Cal Poly | Bus | red |
| 4A Monterey/Foothill/Cal Poly | Bus | green |
| 4B Cal Poly/Ramona/Monterey | Bus | green |
| LT Laguna Tripper | Bus | yellow |
| 6X 6 Express | Bus | red |
| Old SLO Trolley | Bus | teal |
List every stop
- Monterey at La Cuesta Inn
- Wayfarer Inn
- Monterey at Osos
- Higuera at Broad
- Monterey at Grand
- Monterey at The Peach Tree Inn
- Marsh at Johnson
- Johnson at Lizzie (S)
- Nipomo at Higuera
- Johnson at Bishop (S)
- Marsh at Broad
- Broad at Islay
- Johnson at Sydney
- Broad at Funston
- Johnson at La Cita
- Broad at Woodbridge
- Laurel at Augusta
- Broad at Sweeney (Brickyard)
- Laurel at Southwood
- Laurel at Camden
- Orcutt at Laurel
- Orcutt at Lawnwood
- Broad at Industrial (Damon-Garcia)
- Orcutt at Tiburon
- Johnson at Gregory
- Tiburon at Righetti
- Southwood at Woodside
- Righetti at Tank Farm
- Southwood at Laurel
- Laurel at Richard (Laurel Lane Market)
- Augusta at Laurel
- Broad at Tank Farm (Creekside)
- Augusta at Gerda
- Broad at Aerovista
- Augusta at Bishop
- San Luis Airport (Airport at Broad)
- Johnson at Bishop (N)
- Tank Farm at Hollyhock
- Johnson at Lizzie (N)
- Tank Farm at Poinsettia
- Johnson at Marsh
- Broad at Industrial (Marigold Center)
- Monterey at Toro
- Broad at Capitolio
- Broad at Rockview
- Broad at Sweeney (Brickyard)
- Tank Farm at Poinsettia
- Broad at Humbert
- Righetti at Tank Farm
- Broad at Alphonso (The Village)
- Tiburon at Hayfield
- Broad at Santa Barbara
- Ranch House at Cerro Cabrillo
- Broad at Leff
- Marsh at Chorro
- Marsh at Osos
- Santa Rosa at Higuera
- Nipomo at Pismo
- Pismo at Archer
- Higuera at South (S)
- Higuera at Bridge
- Madonna Rd at Madonna Plaza (W)
- Dalidio at Madonna (Promenade)
- Madonna at Oceanaire (W)
- Higuera at Prado (Social Services) (S)
- LOVR at Laguna Village (N)
- Higuera at Granada (S)
- LOVR at Oceanaire (N)
- Higuera at Silver City
- LOVR at Laguna Lane (Middle School)
- Higuera at Suburban
- Prefumo Canyon at Del Rio
- LOVR at Higuera (W)
- Del Rio at Descanso
- LOVR at Calle Joaquin
- LOVR at Auto Park Way
- LOVR at Laguna Lane (Middle School)
- LOVR at Oceanaire (S)
- LOVR at Laguna Village (S)
- LOVR at Madonna
- LOVR at Froom (Irish Hills)
- LOVR at Higuera (E)
- Higuera at Suburban
- Higuera at Hind
- Higuera at Prado (Social Services) (N)
- Higuera at Margarita (DMV)
- Higuera at Chumash
- Madonna at Oceanaire (E)
- Higuera at Elks
- Higuera at South (N)
- Madonna Rd at Madonna Plaza
- Marsh at Archer
- Santa Rosa at Marsh
- Mill at Santa Rosa (E)
- Santa Rosa at Pismo
- Mill at Johnson (E)
- Santa Barbara at Church (SB) serving Amtrak
- Santa Barbara at High (S)
- Mill at Pepper
- South at Meadow Park
- Mill at Grand
- South at King (W)
- Grand at Abbott
- South at Parker (W)
- California at Taft
- LOVR at Descanso
- LOVR at Diablo
- LOVR at Valle Vista (E)
- Kennedy Library (Cal Poly)
- Foothill at Narrow
- Foothill at La Entrada
- Foothill at Casa (Mustang Village)
- Ramona at S. Tassajara
- Foothill at University Square (W)
- Ramona at Palomar
- Foothill at Ferrini (W)
- Foothill at Chorro (E)
- Foothill at Cuesta (W)
- Foothill at Casa
- Foothill at Rosita
- Foothill at Narrow
- LOVR at Valle Vista (W)
- LOVR at Diablo
- LOVR at Descanso
- South at Parker (E)
- California at Stafford
- Grand at Wilson
- South at King (E)
- Mill at Park
- South at Meadow Park
- Mill at Pepper (W)
- Santa Barbara at High (N)
- Santa Barbara at Church (N)
- Mill at Johnson (W)
- Amtrak Station
- Santa Rosa at Leff
- Santa Rosa at Buchon (N)
- Santa Rosa at Oak (Santa Rosa Park)
- Santa Rosa at Murray (N)
- Monterey at Toro
- Foothill at Patricia
- Monterey at California
- Highland at Cuesta (E)
- Monterey at Grove
- Performing Arts Center (Cal Poly) (S)
- Grand at Monterey
- Grand at Fredricks
- Grand at Fredericks
- Grand at Mill
- Performing Arts Center (Cal Poly)
- Monterey at Grove
- Kennedy Library (Cal Poly)
- Monterey at California
- Highland at Mt. Bishop
- Highland at Cuesta (W)
- Highland at Jeffrey
- Patricia at Highland
- Patricia at Foothill
- Santa Rosa at Foothill
- Santa Rosa at Murray (Santa Rosa Park)
- Downtown Transit Center
- Margarita (DMV)
- Prado at Elks
- Dalidio at Froom Ranch
- Madonna Road at Dalidio
Over time
Overall score across the last 4 checks — unchanged since 2026-09-12.
Show the numbers
| Check | Score | Change |
|---|---|---|
| 2026-08-10 | 80.9 | first check |
| 2026-09-01 | 89.2 | up 8.3 |
| 2026-09-12 | 89.2 | no change |
| 2026-09-13 | 89.2 | no change |
What changed since your last check
- Correctness no change
- Freshness no change
- Rider experience no change
- Realtime quality no change
What changed over time
On 2026-08-10 this feed started at grade B. On 2026-09-13 the grade held, though the score rose from 81 to 89. As of 2026-09-13 it holds grade B.
A plain-language history of this feed, newest first.
- 2026-09-01 Score rose 8 points, realtime rose 41 points.
Everything we checked
6 findings, ordered by severity.
Show every finding
- Warning223 instances
Some route lines list the same point twice in a row.
Repeated points don't hurt riders, but they can skew distance math and hint at a shaky export.
Fix: Turn on shape cleanup in your export tool, or drop the repeated points from shapes.txt. (Usually one export setting.)
Finding code: equal_shape_distance_same_coordinates · Read the fix guide for equal_shape_distance_same_coordinates · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning157 instances
157 of 165 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 for scorecard_wheelchair_boarding_unknown · See GTFS Schedule reference (opens the GTFS Schedule reference on an external site)
- Warning5 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 for expired_calendar · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Info16 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 for unknown_column · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Info8 instances
The feed has a stretch of two weeks or more with no service running.
A long gap can mean dates were left out of the calendar. Apps then show no trips on those days.
Fix: Check whether the gap is real, like a seasonal break; if not, add the missing dates to the calendar. (A review of your calendar dates.)
Finding code: big_gap_in_service · Read the fix guide for big_gap_in_service · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Info1 instance
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 for unknown_file · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
NTD GTFS readiness Ready
Published at a public URL, valid, current, and identified with agency_id: the four feed checks for RY2026 all hold here. Only your own D-10 and P-50 filings make that official; this is a heads-up, not a determination.
- Published Ready
- Published at a public URL.
- Valid Ready
- Passes validation with no errors.
- Current Ready
- Service data covers the next 110 days.
- 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 171 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
One requirement remains for this feed to earn the conformance mark. States wheelchair access on 5% of stops and 100% of trips; the mark needs 90% of each.
- Valid Met
- Passes validation with no errors.
- Current Met
- Service data covers the next 110 days.
- Accessible Not yet
- States wheelchair access on 5% of stops and 100% 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.
Realtime reliability
The realtime feed responded on 100.0% of 200 checks in the 31 days to 2026-09-15, with 17s median lag.
Sampled on a schedule between full scores, so this tracks uptime and freshness over time rather than at a single moment. The window ends at the newest observation, which is not always today: if the monitor stops, this window stops with it.
Clears the Google and Apple Maps four-week coverage bar. This feed has 108 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.
The published guideline for this jurisdiction is California Transit Data Guidelines. Caltrans' published quality guidelines and compliance checklist; this rubric is anchored to them.
California Minimum GTFS Guidelines checklist (5 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 5% of stops and 100% of trips.
- Meets shapes.txt with a shape for every trip
All 171 trips have a shape in shapes.txt.
- Meets Fare data published, or the service marked fare-free
Fare data is published.
- Correctness 86 / 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 100 / 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 76 / 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.
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/city-of-san-luis-obispo-transit/2026-09-13.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-09-13. 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.