Feed status · checked 2026-08-01
South Metro Area Regional Transit (SMART)
Based on the feed this agency publishes
Service mode Bus
unchanged since 2026-07-31
Catalogued in Oregon.
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 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 1073 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
Re-generate shape distances in your export; flag to your vendor if it persists.Likely your export tool
Some trips have stop times whose distances along the route go backwards. Apps can show buses jumping backwards or mis-order stops.
⏱ Usually an export-tool fix, not hand editing.worth about +18 points in its category
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
181 of 181 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
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 1073 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
- Some trips have stop times whose distances along the route go backwards.
- Next action
- Re-generate shape distances in your export; flag to your vendor if it persists.
- 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
- 181 of 181 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.
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.
Re-generate shape distances in your export; flag to your vendor if it persists.
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.
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. 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 1073 days ago.
- 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
- 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 11 kinds of issue across 77 instances (18 error, 56 warning, 3 informational).
Service data ended 1073 day(s) ago. Trip planners have likely already dropped this feed.
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.
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 (4 - Wilsonville Rd, V - Villebois Shuttle, 1X - Salem, 6 - Canyon Creek).
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.
143 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set ("Tualatin Park & Ride South", "Argyle Square NE at Elligsen Rd SB", "Parkway Center Dr at Jack Burns Blvd - Costco SB", 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.
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 181 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.
- 2X - Tualatin (red)
- 4 - Wilsonville Rd (green)
- V - Villebois Shuttle (yellow)
- 1X - Salem (orange)
- 3X - Canby (purple)
- 5 - 95th Ave (green)
- 6 - Canyon Creek (teal)
| Route | Type | Line color |
|---|---|---|
| 2X - Tualatin | Bus | red |
| 4 - Wilsonville Rd | Bus | green |
| V - Villebois Shuttle | Bus | yellow |
| 1X - Salem | Bus | orange |
| 3X - Canby | Bus | purple |
| 5 - 95th Ave | Bus | green |
| 6 - Canyon Creek | Bus | teal |
| 7 - Villebois (Commuter) | Bus | yellow (no shape in feed) |
| M - Medical Shuttle | Bus | blue (no shape in feed) |
List every stop
- Tualatin Park & Ride South
- Argyle Square NE at Elligsen Rd SB
- Parkway Center Dr at Jack Burns Blvd - Costco SB
- Burns Way at Parkway Center Dr SB
- Burns Way at Canyon Creek Rd SB
- Canyon Creek Rd at Canyon Creek Apts SB
- Canyon Creek Rd at Carriage Oaks Ln SB
- Printer Pkwy at Canyon Creek SB
- E Printer Pkwy - Xerox SB
- Printer Pkwy at ESS SB
- Parkway Woods West SB
- Parkway Ave - Pioneer Pacific College SB
- Parkway Ave at Boeckman Rd SB
- Parkway Ave at South Boeckman Rd
- Parkway Ave at Ash Meadows Ln - Terrene Apts SB
- Parkway Ave at Ash Meadows Rd - Jory Trail Apts SB
- Parkway Ave at Town Center Lp SB
- Parkway Ct at Town Center Loop - Regal Cinema SB
- Parkway Ct at Courtside Dr
- Goodwill at Courtside Dr
- City Hall at Courtside Dr EB
- City Hall / Civic Center
- Community Center / Civic Center
- City Hall at Courtside Dr WB
- Town Center Park at Parkway Ct NB
- Parkway Ct at Town Center Loop NB
- Parkway Ave at Town Center Lp - Wood Leaf Apts NB
- Parkway Ave at Ash Meadows Rd - Jory Trail Apts NB
- Parkway Ave at Ash Meadows Ln - Terrene Apts NB
- Parkway Ave at Boeckman Rd NB
- Parkway Ave - Pioneer Pacific College NB
- Printer Pkwy at ESS NB
- E Printer Pkwy - Xerox NB
- Canyon Creek Rd at Murray St
- Canyon Creek Rd at Carriage Oaks Ln NB
- Canyon Creek Rd at Canyon Creek Apts NB
- Burns Way at Canyon Creek Rd NB
- Burns Way at Parkway Center Dr NB
- Parkway Center Dr at Jack Burns Blvd - Costco NB
- Argyle Square NE at Elligsen Rd NB
- Wilsonville Rd at Graham Oaks Nature Park
- Wilsonville Rd at Willamette Way E - Valley Christian EB
- Wood Middle School / Autumn Park Apts EB
- Wilsonville Rd at Orchard Dr EB
- Wilsonville Rd at Brown Rd EB
- Wilsonville Rd at Montebello Dr EB
- Wilsonville Rd at Kinsman Rd - Oregon Lottery EB
- Wilsonville Rd at Boones Ferry Rd EB
- Lowrie Shopping Center at Boones Ferry Rd
- Bailey St - Subaru Dealership
- Boones Ferry Rd - Fred Meyer
- Park Place - Sharis EB
- Wilsonville Rd at Kolbe Ln EB
- Wilsonville Rd at Rose Ln EB
- Wilsonville High School EB
- Boeckman Creek Primary School EB
- Wilsonville Rd at Meadows Loop EB
- Wilsonville Rd at Landover Dr EB
- Meridian Creek Middle School
- Wilsonville Rd at Landover Dr WB
- Wilsonville Rd at Meadows Loop WB
- Boeckman Creek Primary School WB
- Wilsonville High School WB
- Wilsonville Rd at Rose Ln WB
- Wilsonville Rd at Kolbe Ln WB
- Town Center Park at Courtside Dr
- Park Place - Sharis
- Wilsonville Rd at Boones Ferry Rd WB
- Wilsonville Rd at Kinsman Rd WB
- Wilsonville Rd at Montebello Dr WB
- Wilsonville Rd at Brown Rd WB
- Wilsonville Rd at Guiss Way WB
- Wood Midldle School / Autumn Park Apts WB
- Wilsonville Rd at Willamette Way E - CREST Center WB
- Rain Garden Apts
- Renaissance Court Apts
- Charleston Apts
- Costa Cir at Zurich St
- Costa Cir at Villebois Dr- Sofia Park
- Costa Cir at Charlotte Ln
- Barber St at Yosemite St EB
- Old Town Square - Fred Meyer
- Wilsonville Rd at Town Center Loop W - AT&T
- Wilsonville Rd at Rebekah St - Library
- Town Center Shopping - Safeway
- Brown Rd at Camelot St - Wiedeman Park Apts
- Brown Rd at Parkwood Ln WB
- Barber St at Yosemite St WB
- Market St at Hawthorne Ave - Park & Ride
- Summer St at Union St - Employment Building SB
- Summer St at Marion SB
- Center St at Capitol St - McDonalds SB
- Court St at Capitol St
- Salem Transit Center
- Capitol St at Marion St NB
- Market St Park & Ride
- Capitol Building at State St NB
- Winter St at Chemeketa St SB
- Market St at Savage Rd NB
- Rockwell Collins SB
- FLIR SB
- Mentor Graphics SB
- Boeckman Rd at Mentor Graphics Driveway SB
- Wilsonville Rd at Rebekah St SB Library
- Wilsonville Rd at Town Center Loop W SB
- 29800 Boones Ferry Rd
- Barber St at Boberg Rd WB
- Barber St at Boberg Rd EB
- 29911 Boones Ferry Rd SB - Route 4
- Mentor Graphics NB
- FLIR NB
- Rockwell Collins NB
- Parkway Woods West NB
- Tualatin Park & Ride North
- Arndt Rd at Airport Rd SB
- Knights Bridge Rd at Aspen St SB
- Cedar St at Knights Bridge Rd SB
- Cedar St at 6th Ave SB
- Cedar St at 5th Ave- Eccles Elementary SB
- Cedar St at 2nd Ave SB
- 2nd Ave at Elm St SB
- 2nd Ave at Holly St SB
- Canby Transit Center
- 2nd Ave at Holly St NB
- 2nd Ave at Elm St NB
- 2nd Ave at Cedar St NB
- Cedar St at 5th Ave - Eccles Elementary NB
- Cedar St at Dahlia Pl NB
- Cedar St at Knights Bridge Rd NB
- Arndt Rd at Airport Rd NB
- Kinsman Rd at Barber St - Coca Cola WB
- Kinsman Rd at Fred Meyer Fueling WB
- 10100 Block SW Commerce Cir - Connect to TriMet 96
- 95th Ave at Ridder Rd SB
- 26277 95th Ave SB
- 95th Ave at Freeman Dr SB
- 95th Ave at Nike Dr SB
- 95th Ave at Hillman Ct SB
- 27695 95th Ave SB
- 95th Ave at Boeckman Rd SB
- 9805 Boeckman Rd SB
- Boberg Rd at Boeckman Rd SB
- 28465 Boberg Rd - Walnut Mobile Park SB
- Boberg Rd at Barber St - SMART Office SB
- Boberg Rd at Barber St - SMART Office NB
- 28440 Boberg Rd - Walnut Mobile Park NB
- Boberg Rd at Boeckman Rd NB
- Costa Circle at SW Mortiz Loop
- Legacy Meridian Park Medical Center
- Wilsonville Transit Center Bay 1
- WTC Drop off A
- WTC Drop off B
- Route 2X - Wilsonville Transit Center
- 3X
- Kinsman Rd at Fred Meyer Feuling EB
- Kinsman Rd at Barber St - Coca Cola EB
- 4 West
- 4 East
- 5 WTC
- 95th Ave at Boeckman Rd NB
- 27700 95th Ave NB
- 95th Ave at Hillman Ct NB
- 95th Ave at Nike Dr NB
- 95th Ave at Freeman Dr NB
- 26300 95th Ave NB
- 9600 Boeckman Rd NB
- Ridder Rd at 95th Av
- Ridder Rd at Peters Rd - Hartung Glass
- Coffee Creek
- 9400 Commerce Cir - Slicks BBQ
- 6 WTC
- 7 WTC
- Costa Cir at Villebois Dr N
- Paris Ave at Costa Cir
- 19260 Medical Plaza 2
- 19250 Medical Plaza 1
- Brown Rd at Parkwood Ln EB
- Brown Rd at Camelot St
- Knights Bridge Rd at AspenCt NB
- Wilsonville Rd at Willamette Way West EB
- Wilsonville Community Center - Front Door
Over time
Overall score across the last 4 checks — unchanged since 2026-07-31.
Show the numbers
| Check | Score | Change |
|---|---|---|
| 2026-07-25 | 30.1 | first check |
| 2026-07-30 | 30.1 | no change |
| 2026-07-31 | 30.1 | no change |
| 2026-08-01 | 30.1 | 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
16 findings, ordered by severity.
Show every finding
- Error18 instances
Some trips have stop times whose distances along the route go backwards.
Apps can show buses jumping backwards or mis-order stops.
Fix: Re-generate shape distances in your export; flag to your vendor if it persists. (Usually an export-tool fix, not hand editing.)
Finding code: decreasing_or_equal_stop_time_distance · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Error1 instance
Service data ended 1073 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)
- Warning261 instances
261 of 261 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)
- Warning181 instances
181 of 181 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)
- Warning18 instances
18 of 261 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 (opens GTFS Best Practices on an external site)
- Warning16 instances
On some trips the stop distances run a little past the end of the route line.
The stop and shape distance values don't quite line up, so any math that uses them can drift.
Fix: Re-generate shape_dist_traveled on export so stop and shape distances use the same units. (Usually an export-tool fix, not hand editing.)
Finding code: trip_distance_exceeds_shape_distance_below_threshold · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning15 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)
- Warning9 instances
Some route long names repeat the route's short name inside them.
Apps show both names together, so riders see the number twice, like '5 5 Downtown'.
Fix: Drop the short name from route_long_name and keep the long name descriptive, like 'Downtown via 5th Ave'. (One field per flagged route.)
Finding code: route_long_name_contains_short_name · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning6 instances
Route short name too long (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'route_short_name_too_long' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Finding code: route_short_name_too_long · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning5 instances
Some rider-facing names are in ALL CAPS or all lowercase.
ALL-CAPS stop and headsign names are harder to read in apps and are read awkwardly by screen readers.
Fix: Use mixed case for stop names and headsigns (e.g. 'Main St & 2nd Ave', not 'MAIN ST & 2ND AVE'). (Often a bulk fix in your scheduling software.)
Finding code: mixed_case_recommended_field · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning2 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)
- Warning1 instance
This feed's service calendar runs out within the next 7 days.
When the calendar ends, Google Maps and other trip planners drop your agency entirely. Riders see no service at all.
Fix: Export and publish an updated GTFS feed that covers at least the next 30 days of service. (Usually a re-export from your scheduling software.)
Finding code: feed_expiration_date7_days · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning1 instance
Some values have extra spaces at the start or end.
A stray space can break a match, so a stop or route may fail to link across files.
Fix: Trim leading and trailing spaces on export. The scorecard's auto-fixed copy already does this. (Usually one export setting.)
Finding code: leading_or_trailing_whitespaces · 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
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 (opens GTFS Best Practices on an external site)
- Info3 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)
NTD GTFS readiness Not ready
Resolve this before you certify on the D-10. 1 validator error to resolve. Service data expired 1073 days ago, so FTA would find the link out of date.
- Published Ready
- Published at a public URL.
- Valid Needs attention
- 1 validator error to resolve.
- Current Not ready
- Service data expired 1073 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 261 trips have a shape in shapes.txt.
In plain words: if you report to the federal transit database, you have to publish a working, up-to-date feed, provide a stable agency_id for each represented reporter, and confirm the feed and P-50 crosswalk each year. This box is a heads-up; your filings are the official check.
A readiness signal mapping this feed to the FTA National Transit Database GTFS requirement (Report Year 2023 onward: a public, valid, current feed, certified annually on the D-10). For RY2026, each represented reporter needs a stable agency_id, unique within the feed and crosswalked to its five-digit NTD ID on P-50; the values do not need to be equal. FTA also requires shapes.txt in the published GTFS: Full Reporters from Report Year 2025, and Reduced, Rural, and Tribal Reporters from Report Year 2026. Not an official determination; your certification is the official check.
Conformance mark Not yet
This feed is close to the conformance mark. 1 validator error to resolve. Service data expired 1073 days ago. States wheelchair access on 0% of stops and 0% of trips; the mark needs 90% of each.
- Valid Not yet
- 1 validator error to resolve.
- Current Not yet
- Service data expired 1073 days ago.
- 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.
- 15 of 181 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 18 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.
A local transit-data support resource is Oregon ODOT Public Transportation. ODOT's Public Transportation Division, which supports statewide GTFS. This resource supports agencies; it is not a scoring authority.
- Correctness 38 / 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 44 / 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/south-metro-area-regional-transit-smart/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.