Prep for a call: printable one-page brief · For your board packet: printable one-pager · Fix log: every issue this feed has cleared · Compare with another agency · Watch this feed: get an email before it expires
Feed status · checked 2026-07-09
South Metro Area Regional Transit (SMART)
Based on the feed this agency publishes
unchanged since 2026-07-08
Ahead of 64% of all tracked agencies and 62% of mid-size agencies. Operates 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.1, validator 8.0.1.
Checked for changes 14 minutes ago; last changed 14 minutes 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
Set wheelchair_accessible on every trip (most small-agency fleets are 100% accessible, so this is often a single default).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.
⏱ Often one default setting in your export.worth about +15 points
Agencies here usually clear this within about 1 week (based on 5 observed fixes).
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
Agencies here usually clear this within about 1 week (based on 16 observed fixes).
Close the loop on each fix. Read the guide, make the change in your tool, and let the next run verify it — the scorecard shows the fix; the agency publishes it.
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.
Prove it cleared. The next scorecard run re-checks this automatically and, once it is gone, mints a dated receipt. See this feed's dated fix log.
Set wheelchair_accessible on every trip (most small-agency fleets are 100% accessible, so this is often a single default). · Read the fix guide
Make the change. Make this change in whatever tool produces your feed, then re-export.
Prove it cleared. The next scorecard run re-checks this automatically and, once it is gone, mints a dated receipt. See this feed's dated fix 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.
Prove it cleared. The next scorecard run re-checks this automatically and, once it is gone, mints a dated receipt. See this feed's dated fix log.
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 data covers the next 26838 days.
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 outside service hours: 3 of 3 feeds healthy.
Routes and stops
Each route is drawn once, using the longest shape its trips follow; stops are the dots.
Skip to route and stop dataBasemap: 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 |
This feed has 179 stops.
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 21 checks — unchanged since 2026-07-08.
Show the numbers
| Check | Score | Change |
|---|---|---|
| 2026-06-19 | 72.1 | first check |
| 2026-06-20 | 70.7 | down 1.4 |
| 2026-06-21 | 72.1 | up 1.4 |
| 2026-06-22 | 72.1 | no change |
| 2026-06-23 | 72.1 | no change |
| 2026-06-24 | 71.3 | down 0.8 |
| 2026-06-25 | 71.9 | up 0.6 |
| 2026-06-26 | 72.1 | up 0.2 |
| 2026-06-27 | 72.1 | no change |
| 2026-06-28 | 72.1 | no change |
| 2026-06-29 | 72.1 | no change |
| 2026-06-30 | 72.1 | no change |
| 2026-07-01 | 70.1 | down 2.0 |
| 2026-07-02 | 72.1 | up 2.0 |
| 2026-07-03 | 72.1 | no change |
| 2026-07-04 | 72.1 | no change |
| 2026-07-05 | 72.1 | no change |
| 2026-07-06 | 72.1 | no change |
| 2026-07-07 | 72.1 | no change |
| 2026-07-08 | 72.1 | no change |
| 2026-07-09 | 72.1 | no change |
What changed since your last check
- Correctness no change
- Freshness no change
- Rider experience no change
- Realtime quality no change
What changed in this feed
Overall grade and score held steady since 2026-07-08.
The feed file was re-published since 2026-07-08.
Subscribe to this feed’s changes (Atom) to hear about grade drops in a reader, with no sign-up.
Everything we checked
- 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 (most small-agency fleets are 100% accessible, so this is often a single default). (Often one default setting in your export.)
Agencies here usually clear this within about 1 week (based on 5 observed fixes).
Validator rule: 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.)
Validator rule: scorecard_wheelchair_boarding_unknown · Read the fix guide · See GTFS Schedule reference (opens the GTFS Schedule reference on an external site)
- Warning72 instances
Trip distance exceeds shape distance below threshold (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'trip_distance_exceeds_shape_distance_below_threshold' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Validator rule: 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
Route long name contains short name (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'route_long_name_contains_short_name' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Validator rule: route_long_name_contains_short_name · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning4 instances
Leading or trailing whitespaces (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'leading_or_trailing_whitespaces' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Validator rule: leading_or_trailing_whitespaces · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning2 instances
Equal shape distance same coordinates (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'equal_shape_distance_same_coordinates' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Validator rule: equal_shape_distance_same_coordinates · 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.)
Validator rule: 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.)
Agencies here usually clear this within about 2 weeks (based on 8 observed fixes).
Validator rule: 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.)
Agencies here usually clear this within about 1 week (based on 16 observed fixes).
Validator rule: 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.)
Validator rule: scorecard_no_fare_data · Read the fix guide · See GTFS Best Practices (opens GTFS Best Practices on an external site)
- Info44 instances
Trip headsign matches intermediate stop (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'trip_headsign_matches_intermediate_stop' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Validator rule: trip_headsign_matches_intermediate_stop · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Info3 instances
Unknown file (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'unknown_file' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Agencies here usually clear this within about 1 week (based on 6 observed fixes).
Validator rule: 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.)
Validator rule: service_extends_far_in_the_future · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
Some fixes we can make for you
These are the safe mechanical fixes, applied to a copy of your feed. They change only what is certain and leave everything else untouched. Review the diff before you publish.
Trimmed surrounding whitespace 6 changes
For example: 'stop_code': ' 11747313' -> '11747313'
Run it yourself on your own copy of the feed: scorecard autofix <feed.zip> --out corrected.zip
NTD certification readiness Ready
Published at a public URL, valid, and current: the three things the NTD GTFS requirement asks of a feed all hold here. Only your own D-10 certification makes 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 26838 days.
- agency_id matches your NTD ID Not checked yet
- Setting your GTFS agency_id to your five-digit NTD ID is an optional way to line a feed up with its National Transit Database record. FTA links the two on your P-50 form, so it is not a required feed change. We don't have your NTD ID on file, so this 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 and confirm it once a year. This box is a heads-up on whether yours looks ready; it is not the official sign-off.
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). Aligning agency_id with your NTD ID lets the feed line up with your NTD record; the July 2025 final rule links the two on the P-50 form rather than requiring that feed change, and 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
- Service data covers the next 26838 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 106 checks over the last 16 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.
Clears the Google and Apple Maps four-week coverage bar. This feed has 26838 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
A data-quality lens, not a compliance determination. Each category shows this feed's score and the standards it relates to: the FTA National Transit Database GTFS requirement, the MobilityData grading scheme, and the Google Transit gate. Read the full standards crosswalk.
Your state runs a transit-data program that can help: Oregon ODOT Public Transportation. ODOT's Public Transportation Division, which supports statewide GTFS. Your state publishes no quality rubric of its own, so the closest published bars a program can hold this feed to are the federal and industry ones below; the score maps to those.
- Correctness 68 / 100
- GTFS Schedule best practices, checked by the MobilityData validator. MobilityData grading: stop locations, route names and colors. Google Transit: a feed must pass validation to stay in Maps.
- Freshness 85 / 100
- The FTA National Transit Database expectation of a valid, current feed. Google Transit: an expired calendar drops the agency from Maps.
- Rider experience 45 / 100
- GTFS Best Practices for rider-facing fields. MobilityData grading: 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 live badge on your agency site or feed README. It updates daily 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-07-09.json and never overwritten, pinning the grade, category scores, rubric version, validator version, and the scored feed's sha256 as they stood on 2026-07-09. Use it in a board packet, an NTD narrative, 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.