Feed status · checked 2026-08-01
South Metro Area Regional Transit (SMART)
Based on the feed this agency publishes
Service mode Bus
up 0.1 since 2026-07-31 · C → C
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 14 hours ago.
Measured 4 of 4 score categories from the agency's own feed.
How we measured this
Confidence in this measurement: high.
- All four score categories were measured this run.
- Realtime was sampled in one bounded window of 9 snapshots.
- The feed was downloaded from the agency's own URL.
Confidence describes how much the pipeline could measure this run, not the feed itself. It never changes the grade.
Top things to fix
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
179 of 179 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
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
363 of 363 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
Add feed_info.txt with feed_start_date and feed_end_date to your export.Likely your export tool
feed_info.txt is missing its start/end dates Apps and this scorecard can't warn anyone before the feed goes stale without stated validity dates.
⏱ Two fields, set once in export settings.worth about +15 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
- 179 of 179 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
- 363 of 363 trips don't say whether the vehicle is wheelchair accessible.
- Next action
- Set wheelchair_accessible on every trip. If every vehicle is accessible, this may be one default; otherwise use the value for each trip.
- 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
- feed_info.txt is missing its start/end dates
- Next action
- Add feed_info.txt with feed_start_date and feed_end_date to your export.
- 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
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
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_info.txt with feed_start_date and feed_end_date to your export. · Read the fix guide
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 states that service is published through 2099-12-31. This may be intentional or a placeholder; confirm current service with the transit operator.
- 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
- Live-arrival data covered 100% of scheduled trips in the sampled window.
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 9 kinds of issue across 139 instances (0 error, 90 warning, 49 informational).
Service is published through 2099-12-31. It may be intentional, but confirm the end date before treating the feed as maintained.
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
2 route badge(s) pair a color and text color below the WCAG 4.5:1 contrast bar (4, 10X).
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.
111 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set ("Barber Street @ Serenity", "Barber Street @ San Miguel", "Costa Circle @ Davos", 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.
Sampled 9 times: 3 of 3 configured feeds healthy; 100.0% of scheduled trips had live predictions; 100.0% of vehicles on their route; predictions ran a median of 60s behind schedule.
Routes and stops
Each route is drawn once, using the longest shape its trips follow; stops are the dots.
This feed has 179 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 (red)
- 4 (green)
- V (gray)
- 1X (orange)
- 3X (purple)
- 5 (green)
- 6 (teal)
- 7 (yellow)
- 12X (gray)
- 10X (pink)
| Route | Type | Line color |
|---|---|---|
| 2X 2X-Tualatin | Bus | red |
| 4 4-Wilsonville Rd | Bus | green |
| V V-Villebois Shopping Shuttle | Bus | gray |
| 1X 1X-Salem | Bus | orange |
| 3X 3X-Canby | Bus | purple |
| 5 5-95th Ave | Bus | green |
| 6 6-Canyon Creek | Bus | teal |
| 7 7-Villebois | Bus | yellow |
| 12X 12X-Woodburn | Bus | gray |
| 10X 10X-Clackamas | Bus | pink |
List every stop
- Barber Street @ Serenity
- Barber Street @ San Miguel
- Costa Circle @ Davos
- Costa Circle @ Villebois
- Edelweiss Park
- Costa Circle @ Barber
- Barber Street @ San Miguel
- Barber Street @ Serenity
- Amazon- Woodburn
- Woodburn Transit Center
- Wilsonville Transit Center Bay 2
- Wilsonville Transit Center Bay 4
- Wilsonville Transit Center Bay 7
- Wilsonville Transit Center Bay 5
- Riverside High School
- West Linn
- Oregon City Shopping Center
- Clackamas Town Center TC
- Clackamas Town Center Mall
- Rolling Hills Community Church
- Clackamas Town Center TC
- Clackamas Town Center Mall
- Tualatin Park & Ride
- Elligsen Road @ Argyle Square
- Parkway Center Drive @ Argyle Square
- Burns Way @ Parkway Center - Eastbound
- Burns Way @ Canyon Creek Road
- Canyon Creek Apartments
- Canyon Creek Park
- Printer Pkwy at Canyon Creek Southbound
- E Printer Pkwy - Xerox Southbound
- Printer Pkwy at ESS Southbound
- Parkway Woods West Southbound
- Parkway Avenue @ Oregon Institute of Technology
- Parkway Avenue @ Boeckman Road
- Parkway Avenue @ Boeckman Road
- Parkway Avenue @ Ash Meadows Lane
- Parkway Avenue @ Ash Meadows Road
- Parkway Avenue @ Thunderbird Drive
- Parkway Court @ Town Center Loop
- Town Center Park
- Wilsonville City Hall - Eastbound
- Wilsonville City Hall - Southbound
- Wilsonville Community Center
- Wilsonville City Hall - Westbound
- Town Center Park- Northbound
- Parkway Court @ Town Center Loop
- Parkway Avenue @ Thunderbird Drive
- Parkway Avenue @ Ash Meadows Road
- Parkway Avenue @ Ash Meadows Lane
- Parkway Avenue @ Boeckman Road
- Parkway Avenue @ Oregon Institute of Technology
- Printer Pkwy at ESS Northbound
- E Printer Pkwy - Xerox Northbound
- Canyon Creek Road @ Murray - Northbound
- Canyon Creek Park- Northbound
- Canyon Creek Apartments
- Burns Way @ Canyon Creek - Westbound
- Burns Way @ Parkway Center - Westbound
- Parkway Center Drive @ Argyle Square
- Elligsen Road @ Argyle Square- Westbound
- Graham Oaks Nature Park
- Boones Ferry Primary School
- Wood Middle School
- Wilsonville Road @ Orchard Drive
- Wilsonville Road @ Brown Road
- Wilsonville Road @ Montebello Drive
- Wilsonville Road @ Kinsman
- Wilsonville Road @ Boones Ferry
- Boones Ferry Road @ Old Town Square - Southbound
- Bailey Street @ Old Town Square
- Boones Ferry Road @ Old Town Square - Northbound
- Park Place @ Town Center Loop
- Wilsonville Road @ Kolbe Lane
- Wilsonville Road @ Rose Lane
- Wilsonville High School
- Boeckman Creek Primary School
- Wilsonville Road @ Meadows Loop
- Wilsonville Road @ Landover Drive
- Meridian Creek Middle School
- Wilsonville Road @ Landover Drive
- Wilsonville Road @ Meadows Loop
- Boeckman Creek Primary School
- Wilsonville High School
- Wilsonville Road @ Rose Lane
- Wilsonville Road @ Kolbe Lane
- Town Center Park- Westbound
- Park Place @ Town Center Loop
- Wilsonville Road @ Boones Ferry
- Wilsonville Road @ Kinsman
- Wilsonville Road @ Montebello Drive
- Wilsonville Road @ Brown Road
- Wilsonville Road @ Orchard Drive
- Wood Middle School
- Boones Ferry Primary School
- Rain Garden Apartments
- Renaissance Court Apartments
- Charleston Apartments
- Villebois Community Center
- Sofia Park
- Costa Circle @ Charlotte
- Old Town Square - Fred Meyer
- Wilsonville Road @ Town Center Loop
- Wilsonville Road @ Wilsonville Public Library
- Town Center Shopping - Safeway
- Brown Road @ Wilsonville Road
- Brown Road @ Parkwood Lane
- Market @ Hawthorne
- Summer Street @ Union
- Summer @ Marion
- Center Street @ Capitol
- Court Street @ Capitol
- Salem Transit Center
- Capitol @ Marion
- Oregon State Capitol Building
- Market Street @ Savage
- Rockwell Collins Southbound
- FLIR Southbound
- Siemens Southbound
- Boeckman Road @ Parkway Avenue
- Wilsonville Road @ Wilsonville Public Library
- Wilsonville Road @ Town Center Loop
- Boones Ferry Road @ Wilsonville Road
- Barber Street @ Boberg Road
- Barber Street @ Boberg Road- Eastbound
- Boones Ferry Road @ Wilsonville Road
- Siemens Northbound
- FLIR Northbound
- Rockwell Collins Northbound
- Parkway Woods West Northbound
- Arndt Road @ Airport Road
- Knights Bridge Road @ Aspen Street
- Cedar Street @ Knights Bridge Road
- Cedar Street @ 6th Avenue
- Eccles Elementary School
- Cedar Street @ 3rd Avenue
- 2nd Avenue @ Elm Street
- 2nd Avenue @ Holly Street
- Canby Transit Center
- 2nd Avenue @ Holly Street
- 2nd Avenue @ Elm Street
- 2nd Avenue @ Cedar Street
- Eccles Elementary School
- Cedar Street @ 6th Avenue
- Cedar Street @ Knights Bridge Road
- Arndt Road @ Airport Road
- Kinsman Road @ Barber
- Kinsman Road @ Wilsonville Road
- Commerce Circle South
- 95th Avenue @ Ridder Road
- 26000 95th Avenue
- 95th Avenue @ Freeman Drive
- 95th Avenue @ Nike Drive
- 95th Avenue @ Hillman Court
- 27000 95th Avenue
- 95th Avenue @ Boeckman Road
- Boeckman Road @ 95th Avenue
- Boberg Road @ Boeckman Road
- Boberg Road @ Wilsonville Public Works
- Boberg Road @ Barber Street
- Boberg Road @ Barber Street
- Boberg Road @ Wilsonville Public Works
- Boberg Road @ Boeckman Road
- Wilsonville Transit Center Bay 1
- Wilsonville Transit Center - Drop off A
- Wilsonville Transit Center Bay 10
- Wilsonville Transit Center Bay 9
- Kinsman Road @ Barber
- Wilsonville Transit Center Bay 6
- Wilsonville Transit Center Bay 3
- Boeckman Road @ 95th Avenue
- Commerce Circle North
- Wilsonville Transit Center Bay 8
- Brown Road @ Parkwood Lane
- Brown Road @ Wilsonville Road
- Knights Bridge Road @ Aspen Street
- Wilsonville Road @ Willamette Way West
- 29000 Boones Ferry Road- Southbound
- Kinsman Road @ Wilsonville Road
Over time
Overall score across the last 4 checks — up 0.1 since 2026-07-31.
Show the numbers
| Check | Score | Change |
|---|---|---|
| 2026-07-25 | 69.8 | first check |
| 2026-07-30 | 71.4 | up 1.6 |
| 2026-07-31 | 72.0 | up 0.6 |
| 2026-08-01 | 72.1 | up 0.1 |
What changed since your last check
- Correctness no change
- Freshness no change
- Rider experience no change
- Realtime quality up 0.8
What changed in this feed
Overall score rose 0.1 points since 2026-07-31.
The feed file was re-published since 2026-07-31.
Subscribe to this feed’s changes (Atom) to hear about grade drops in a reader, with no sign-up.
What changed over time
On 2026-07-25 this feed started at grade D. On 2026-07-30 the grade moved from D to C. As of 2026-08-01 it holds grade C.
A plain-language history of this feed, newest first.
- 2026-07-30 Grade went D to C, realtime rose 8 points.
Everything we checked
13 findings, ordered by severity.
Show every finding
- Warning363 instances
363 of 363 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)
- Warning179 instances
179 of 179 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)
- Warning72 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)
- Warning10 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)
- Warning4 instances
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)
- Warning2 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 · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning1 instance
feed_info.txt does not state when this feed starts and ends.
Without stated dates, apps can't warn anyone before your data goes stale; it just disappears one day.
Fix: Fill in feed_start_date and feed_end_date in feed_info.txt. (Two fields, likely set once in your export settings.)
Finding code: missing_feed_info_date · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning1 instance
Some files leave out fields that GTFS asks for but does not require.
Recommended fields like agency_phone or stop descriptions make the feed more useful to riders and trip planners.
Fix: Review the flagged fields and fill in the ones your riders would use. (A field at a time; not urgent.)
Finding code: missing_recommended_field · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning1 instance
feed_info.txt is missing its start/end dates
Apps and this scorecard can't warn anyone before the feed goes stale without stated validity dates.
Fix: Add feed_info.txt with feed_start_date and feed_end_date to your export. (Two fields, set once in export settings.)
Finding code: scorecard_missing_feed_info_dates · 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)
- Info44 instances
Some trip headsigns name a stop along the way, not the final destination.
The sign should tell riders where the bus ends up, so a midpoint name can send them the wrong way.
Fix: Set trip_headsign to the trip's last stop or its overall destination. (Usually a bulk edit in your scheduling software.)
Finding code: trip_headsign_matches_intermediate_stop · See MobilityData GTFS Validator rules (opens the validator rules 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)
- Info2 instances
Service extends far in the future (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'service_extends_far_in_the_future' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Finding code: service_extends_far_in_the_future · 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
- The published window is current, but its service end date is unusually distant; confirm that date is intentional.
- 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 363 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. 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
- The published window is current, but its service end date is unusually distant; confirm that date is intentional.
- 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 over the last 34 days, with 0s median lag.
Sampled on a schedule between full scores, so this tracks uptime and freshness over time rather than at a single moment.
Live predictions vs schedule
Arrival predictions ran a median 60s late versus the schedule, and stayed within 193s nine times in ten. They were on time (about a minute early to five late) 96.2% of the time. 100.0% of reported vehicle positions sat on or near the published route shape.
From the last full realtime sample: how far live arrival predictions sat from the schedule, and whether vehicle positions fell on the route. These feed the realtime score; they change no other category.
Clears the Google and Apple Maps four-week coverage bar. This feed clears the four-week coverage window, but its service end date is unusually distant. Confirm that date is intentional before treating it as evidence of ongoing maintenance. 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.
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 68 / 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 85 / 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 45 / 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/south-metro-area-regional-transit-smart-2706/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.