← All agencies

Feed status · checked 2026-09-13

San Luis Obispo Regional Transit Authority (SLORTA)

Based on the feed source on file; publisher ownership is not verified

Service mode Bus

FDCBA

85.3 / 100

unchanged since 2026-09-12

Catalogued in California.

Covers 474 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 30 hours ago; last changed 28 days ago.

Measured 4 of 4 score categories from the feed URL on file (publisher not verified).

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 configured feed URL. Publisher ownership of that 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

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

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

421 of 421 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 feed_contact_email or feed_contact_url to feed_info.txt.Likely your export tool

feed_info.txt lists no contact email and no contact URL. Without a contact, apps like Google Maps can't reach you when they find a problem in the feed.

⏱ One field, set once in export settings.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: 353 of 353 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

Agency: San Luis Obispo Regional Transit Authority (SLORTA)
Finding: scorecard_wheelchair_boarding_unknown
Feed evidence: 353 of 353 stops don't say whether a wheelchair user can board there.
Why it matters: Riders who use wheelchairs can't plan a trip when accessibility is marked 'unknown'; apps show no information at all.
Requested change: 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.
Evidence: https://gtfsscorecard.org/agency/san-luis-obispo-regional-transit-authority-slorta/?finding=scorecard_wheelchair_boarding_unknown#finding-handoff

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.
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 for scorecard_wheelchair_accessible_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.
Add feed_contact_email or feed_contact_url to feed_info.txt. · Read the fix guide for missing_feed_contact_email_and_url
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 474 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: 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.

Hi,

Our GTFS feed (San Luis Obispo Regional Transit Authority (SLORTA)) scored B (85.3 out of 100) on the GTFS Scorecard. Could you review these in our export settings:

1. Set wheelchair_boarding to 1 (accessible) or 2 (not accessible) for every stop. A field survey can start with the busiest stops.
   What: 353 of 353 stops don't say whether a wheelchair user can board there.
   Finding code: scorecard_wheelchair_boarding_unknown
   Guide: https://gtfsscorecard.org/fix/scorecard_wheelchair_boarding_unknown/

2. Set wheelchair_accessible on every trip. If every vehicle is accessible, this may be one default; otherwise use the value for each trip.
   What: 421 of 421 trips don't say whether the vehicle is wheelchair accessible.
   Finding code: scorecard_wheelchair_accessible_unknown
   Guide: https://gtfsscorecard.org/fix/scorecard_wheelchair_accessible_unknown/

3. Add feed_contact_email or feed_contact_url to feed_info.txt.
   What: feed_info.txt lists no contact email and no contact URL.
   Finding code: missing_feed_contact_email_and_url
   Guide: https://gtfsscorecard.org/fix/missing_feed_contact_email_and_url/

Full scorecard: https://gtfsscorecard.org/agency/san-luis-obispo-regional-transit-authority-slorta/

Score by category

Correctness92.0 / 100

The MobilityData validator flagged 2 kinds of issue across 2 instances (0 error, 2 warning, 0 informational).

Freshness100.0 / 100

Service data covers the next 474 days.

Rider experience52.5 / 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 published.

Accessibility0 / 100

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

FaresLegacy fares

Fares are applied to trips.

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

10N (pink)
10S (pink)
12N (teal)
12S (teal)
14N (teal)
15N (purple)
15S (purple)
21 (gray)
24 (orange)
27 (teal)
28 (blue)
31 (green)
40 (teal)
41 (yellow)
42 (red)
9N (brown)
9S (brown)
A (purple)
B (red)

Routes in San Luis Obispo Regional Transit Authority (SLORTA)'s feed
Route	Type	Line color
10N RTA - Santa Maria / San Luis Obispo	Bus	pink
10S RTA - San Luis Obispo / Santa Maria	Bus	pink
12N RTA - San Luis Obispo / Morro Bay / Los Osos	Bus	teal
12S RTA - Los Osos / Morro Bay / San Luis Obispo	Bus	teal
14N RTA - Government Center / CalPoly / Cuesta College	Bus	teal
15N RTA - Morro Bay / San Simeon	Bus	purple
15S RTA - San Simeon / Morro Bay	Bus	purple
21 SCT - Pismo Beach / Shell Beach / Grover Beach / Oceano / Arroyo Grande	Bus	gray
24 SCT - Arroyo Grande / Pismo Beach / Grover Beach	Bus	orange
27 SCT - Grover Beach / Arroyo Grande / Oceano	Bus	teal
28 SCT - Grover Beach / Oceano / Arroyo Grande	Bus	blue
31 RTA- Morro Bay Transit	Bus	green
40 SCT - Pismo Beach / Avila Beach / Port San Luis	Bus	teal
41 Morro Bay North Trolley	Bus	yellow
42 Morro Bay Downtown Trolley	Bus	red
9N RTA - Paso Robles / Cuesta College North / San Miguel	Bus	brown
9S RTA - Cuesta College North / Paso Robles	Bus	brown
A Paso Express - Route A	Bus	purple
B Paso Express - Route B	Bus	red

List every stop

Oak & 2nd
Walmart Shopping Center
Niblick & Nicklaus
Paso Robles High School
Rambouillet & Wade
Rambouillet & Torrey Pines
Stoney Creek Rd @ Dry Creek Apartments
Stoney Creek Rd @ Dry Creek Apartments
Creston & Myrtlewood
Scott @ Paso Robles Senior Center
Scott & Westfield
Scott & Westfield
Airport & Scott
Airport & Scott
Airport & Parkview
Sherwood & Quail Run
Creston & Niblick
Creston & Melody
Creston & Nickerson
Creston & Bolen
Creston & Shannon Hill
Creston & Capitol Hill
Riverside & 17th
Riverside & 20th
Riverside & 26th
Ysabel & 24th
Riverside & 24th
Riverside & 18th
Riverside & 14th
Spring & 14th
Spring & 17th
Spring & 21st
24th & Park
Spring & 24th
Spring & 28th
Spring & 30th
Oak & 34th
Spring & 34th
Spring & 32nd
Spring & 30th
Spring & 28th
Spring & 23rd
Spring & 22nd
Spring & 18th
Spring & 16th
El Camino Real & Patria
El Camino Real & Santa Clara
El Camino Real & Carmel
El Camino Real & Santa Margarita
Garden Farms
El Camino Real & Encina
El Camino Real & Encina
El Camino Real & Maria
El Camino Real & Pine
El Camino Real & Santa Margarita
El Camino Real & Carmel
El Camino Real & Santa Clara
Viejo Camino & Santa Barbara
Viejo Camino & Santa Barbara
Viejo Camino & Bocina
Viejo Camino & Bocina
El Camino Real & Buena Fortuna
El Camino Real & Musselman
El Camino Real & El Bordo
El Camino Real & Principal
El Camino Real & Solano
El Camino Real & Palomar
El Camino Real & Pueblo
El Camino Real & Highway 41
Atascadero Transit Center
El Camino Real & Traffic Way
El Camino Real & Rosario
El Camino Real & San Jacinto
El Camino Real & San Anselmo
El Camino Real & Maya
El Camino Real & San Benito
El Camino Real & Del Rio
Templeton Park & Ride
Theatre @ Gahan
Theatre @ Alexa
Target Shopping Center
Theatre & Via Santa Barbara
Morro Bay Park
Main & Errol
Main Street & Elena Street
Ocean & Old Creek
Ocean & 8th
Ocean & 3rd
South Bay & Quintana
South Bay & Quintana
Santa Ysabel & 15th
Santa Ysabel & 15th
11th & El Morro
11th & Ramona
10th & Santa Ynez
10th & Los Osos Valley
Los Osos Valley Rd & Palisades
Los Osos Valley Rd & Pine
Pine & Loma
Ramona & 7th
7th & El Morro
2nd & Santa Maria
Santa Ysabel & 7th
Cal Poly Library
Cal Poly Library
Cal Poly Performing Arts Center
Cal Poly Performing Arts Center
Santa Rosa & Murray
Spring & 26th
Spring & 13th
Spring & 11th
Spring & 10th
7th & Park
Creston & Capitol Hill
Creston & Bolen
Georgia Brown Elementary
Creston & Melody
Creston & Oak Meadow
Sherwood & Creston
Sherwood & Quail Run
Fontana & Linne
Airport & Turtle Creek
Scott @ Paso Robles Senior Center
Creston & Cedarwood
Rambouillet & Torrey Pines
Paso Robles High School
El Camino Real & Santa Cruz
El Camino Real & Atalaya
El Camino Real & Atalaya
El Camino Real & Del Rio
El Camino Real & San Benito
El Camino Real & Maya
K Mart
El Camino Real & San Anselmo
El Camino Real & Rosario
El Camino Real & Entrada
El Camino Real & Highway 41
El Camino Real & Pueblo
El Camino Real & Junipero
El Camino Real & Plata
El Camino Real @ Santa Rosa
El Camino Real & El Bordo
El Camino Real & Maple
Grand & McCollum
Grand & McCollum
Grand & Wilson
Grand @ AM PM
Grand & Halcyon
Grand & Alder
Grand & Elm
Grand & Courtland
Grand & 16th
Grand & 13th
West Grand Ave & Nth 6th St
Grand & 2nd
Highway 1 & Le Sage
Highway 1 & Le Sage
Grand & 3rd
Grand & 7th
Grand & 13th
Grand & 16th
Grand & Oak Park
Grand & Elm
Grand & Alder
Grand & Branch
Traffic & Firefighters Park
Arroyo Grande City Hall
Grand & Branch
Halcyon Park & Ride
Elm & Paul
Highway 1 & 25th
Highway 1 & 21st
13th & Highway 1
Ramona Garden Park
Dolliver & Frady
Dolliver @ Butterfly Tree
Pismo Coast Village
Dolliver & Pomeroy
Dolliver & Hinds
Dolliver & San Luis
Dolliver & Bay
Price & Stimson
Price & Hinds
Price & Wadsworth
Price & Harbor View
Lighthouse Inn North
Shell Beach & Seacliff
Shell Beach & Terrace
Shell Beach & Cuyama
Shell Beach & Cliff
Mattie & Foothill
Pismo Beach City Hall
Mattie & Valencia
James Way & 4th
James Way & Ridge
James Way & Oak Park
Branch & Vernon
South County Library
Carl's Junior
James Way & Oak Park
James Way & Ridge
James Way & 4th
Avila Hot Springs
Avila Beach & First
Port San Luis
Avila Beach & First
Shell Beach & Ebb Tide
Cayucos & Ocean
Ardath & Green
Ardath & Green
Burton & Lucille
Burton & Ardath
Burton & Burton Cir
Burton & Yorkshire
Burton & Patterson
Burton & Main
Burton & Main
Bluebird Inn
Main & Bluebird Inn
Main & Tamson
Main & Tamson
Main & Cambria Drive
Main & Cambria Drive
Main & Cornwall
Main & Arlington
Moonstone Beach & Windsor
Moonstone Beach & Windsor
Cambria Beach Lodge
Cambria Beach Lodge
Castle Inn
Moonstone & Fireside Inn
Oceanpoint Ranch
Oceanpoint Ranch
Castillo @ Quality Inn
Hearst Castle Visitor Center
Hearst & San Simeon
Ocean & Cayucos
Ocean & 3rd
Ocean & 9th
Ocean & Old Creek
Highway 1 & San Jacinto
James Way & Highland
Higuera & South
Marsh & Broad
Higuera & South
D M V
Nipomo High School
Tefft & Carillo
Hancock College
Cypress & Nicholson
and 103 more (see the full list on the map or in the GeoJSON)

Over time

Overall score across the last 4 checks — unchanged since 2026-09-12.

Show the numbers

Overall score by check, with the change from the previous check
Check	Score	Change
2026-08-10	84.8	first check
2026-09-01	84.9	up 0.1
2026-09-12	85.3	up 0.4
2026-09-13	85.3	no change

What changed since your last check

Correctness no change
Freshness no change
Rider experience no change
Realtime quality no change

Everything we checked

5 findings, ordered by severity.

Show every finding

Warning421 instances
421 of 421 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 for scorecard_wheelchair_accessible_unknown · See GTFS Schedule reference (opens the GTFS Schedule reference on an external site)
Warning353 instances
353 of 353 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)
Warning1 instance
feed_info.txt lists no contact email and no contact URL.
Without a contact, apps like Google Maps can't reach you when they find a problem in the feed.
Fix: Add feed_contact_email or feed_contact_url to feed_info.txt. (One field, set once in export settings.)
Finding code: missing_feed_contact_email_and_url · Read the fix guide for missing_feed_contact_email_and_url · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
Warning1 instance
Some route colors don't contrast with their text color.
Route badges get hard to read, most of all for riders with low vision.
Fix: Pick a darker/lighter route_text_color for the flagged routes. (One field per route.)
Finding code: route_color_contrast · Read the fix guide for route_color_contrast · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
Info1 instance
feed_info.txt has no technical contact (feed_contact_email or feed_contact_url).
App makers and state data programs have nobody to email when they spot a problem. Small errors then sit in the feed for months.
Fix: Add feed_contact_email to feed_info.txt. (One field.)
Finding code: scorecard_no_feed_contact · Read the fix guide for scorecard_no_feed_contact · 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 474 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 421 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 0% of stops and 0% of trips; the mark needs 90% of each.

Valid Met: Passes validation with no errors.
Current Met: Service data covers the next 474 days.
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.

Realtime reliability

The realtime feed responded on 100.0% of 200 checks in the 31 days to 2026-09-15, with 8s 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 472 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 (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.
Gap Designate a technical contact in feed_info.txt's feed_contact_email
feed_info.txt has no feed_contact_email or feed_contact_url.
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 421 trips have a shape in shapes.txt.
Meets Fare data published, or the service marked fare-free
Fare data is published.

Correctness 92 / 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 52 / 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.

[![San Luis Obispo Regional Transit Authority (SLORTA) GTFS data quality grade: B](https://gtfsscorecard.org/data/artifacts/san-luis-obispo-regional-transit-authority-slorta/badge.svg)](https://gtfsscorecard.org/agency/san-luis-obispo-regional-transit-authority-slorta/)

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/san-luis-obispo-regional-transit-authority-slorta/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.

GTFS Scorecard. (2026). San Luis Obispo Regional Transit Authority (SLORTA) GTFS feed-quality record, dated 2026-09-13 (grade B (85.3/100), rubric v1.3, gtfs-validator 8.0.1, reader archive profile raw-v1, feed sha256 dbd2685b9f48…). https://gtfsscorecard.org/data/artifacts/san-luis-obispo-regional-transit-authority-slorta/2026-09-13.json

@misc{gtfsscorecard-san-luis-obispo-regional-transit-authority-slorta-2026-09-13,
  title        = {San Luis Obispo Regional Transit Authority (SLORTA) GTFS feed-quality record},
  author       = {GTFS Scorecard},
  year         = {2026},
  howpublished = {\url{https://gtfsscorecard.org/data/artifacts/san-luis-obispo-regional-transit-authority-slorta/2026-09-13.json}},
  note         = {Checked 2026-09-13; rubric v1.3; gtfs-validator 8.0.1; reader archive profile raw-v1; grade B (85.3/100)}
}

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