Feed status · checked 2026-08-01
Sandy Area Metro (SAM) Realtime Static
Based on the feed this agency publishes
Service mode Bus
down 1.2 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 3 hours ago; last changed 3 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
256 of 256 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
Check with your AVL vendor that every vehicle assignment flows into TripUpdates, including school-day and tripper runs.
3 of 6 trips scheduled during the sampling window had no live predictions. Riders on those trips get schedule data dressed up as realtime. Caltrans expects every operating trip in TripUpdates.
⏱ A vendor data-mapping question.worth about +18 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
130 of 130 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
This feed is generated by your Passio system from the route and stop data they maintain. Send the fix list to your Passio contact.
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
- 256 of 256 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
- 3 of 6 trips scheduled during the sampling window had no live predictions.
- Next action
- Check with your AVL vendor that every vehicle assignment flows into TripUpdates, including school-day and tripper runs.
- 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
- 130 of 130 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
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. This feed is generated by your Passio system from the route and stop data they maintain. Send the fix list to your Passio contact.
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.
Check with your AVL vendor that every vehicle assignment flows into TripUpdates, including school-day and tripper runs. · Read the fix guide
Make the change. This feed is generated by your Passio system from the route and stop data they maintain. Send the fix list to your Passio contact.
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. This feed is generated by your Passio system from the route and stop data they maintain. Send the fix list to your Passio contact.
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 30 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
- No fare information is published in the feed.
- Realtime information
- Live-arrival data covered 50% 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 Passio a fix request
This feed is generated by your Passio system. Copy this and send it to your Passio contact; the fixes apply to the route and stop data behind your AVL setup. Each fix names the validator notice and a guide link.
Score by category
The MobilityData validator flagged 7 kinds of issue across 109 instances (0 error, 99 warning, 10 informational).
Service data covers the next 30 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.
1 accessibility depth signal
196 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set ("10000 Stevens Rd", "10010 Stevens Rd", "169th Ave and Misty Dr", 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; 50.0% of scheduled trips had live predictions; 100.0% of vehicles on their route; predictions ran a median of 142s behind schedule.
Routes and stops
Each route is drawn once, using the longest shape its trips follow; stops are the dots.
This feed has 256 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.
- EXP (red)
- MHX (green)
- SS (orange)
- EVS (teal)
- CTC (pink)
| Route | Type | Line color |
|---|---|---|
| EXP Sandy Local & Gresham Express | Bus | red |
| MHX Mt. Hood Express | Bus | green |
| SS Shopper Shuttle 2.0 | Bus | orange |
| EVS Estacada Village Shuttle 2.0 | Bus | teal |
| CTC Clackamas Town Center 2.0 | Bus | pink |
List every stop
- Hwy 26 & SE 362nd Dr Eastbound
- Hwy 26 and University Westbound
- Hwy 26 & Ruben Ln Westbound (Safeway)*
- Hwy 26 at Mt Hood Athletic Club
- Hwy 26 & Industrial Way Eastbound
- Hwy 26 & Ruben Ln Eastbound
- Hwy 26 & Bluff Rd Eastbound
- Pioneer Blvd at Senior Center Eastbound
- Pioneer Blvd & Scales Ave
- Pioneer Blvd & Shelly Ave (the Action Center)
- Proctor Blvd & Strauss Ave
- Proctor Blvd & Beers Ave
- Hwy 26 & Bluff Rd Westbound
- Powell Blvd & SE Rene Ave Westbound
- Powell Blvd & NE Cleveland Ave Westbound
- Gresham Transit Center
- Powell Blvd & SE Cleveland Ave Eastbound
- Powell Blvd & SE Rene Ave Eastbound
- Hwy 26 & University Ave Eastbound
- NE Hood St & NE 2nd St
- Estacada City Hall
- Eagle Creek Elementary Northbound
- Jackknife Rd
- Judd Rd North
- Hwy 211 & Barlow Trail Southbound
- Big Valley Westbound
- Judd Rd South
- Eagle Creek Elementary Southbound
- Hwy 211 & SE Eagle Creek Rd
- SE Eagle Creek Rd & SE Risberg Ln
- Eagle Creek Rd & Riverside Way
- Eagle Creek Rd & Folsom Rd
- Eagle Creek Rd at 27560
- Eagle Creek Rd & Heiple Rd Southbound
- Eagle Creek Rd at 29275
- Eagle Creek Rd at 29635
- Eagle Creek Rd & River Mill Rd
- Eagle Creek Rd & Strubhar Ln
- Estacada Public Library Northbound
- Main St and NE 3rd Ave
- Main St and 1st Ave
- Main St & SE 3rd Ave Southbound
- Main St and SE 4th Ave
- Hwy 211 & Barlow Trail Northbound
- Wolf Dr & McCormick Dr Southbound
- McCormick Dr & Wolf Dr Westbound
- McCormick Dr & Langensand Rd Northbound
- Evans St
- Cascadia Village Park Southbound
- Sandy Heights & Bluff Rd
- Sandy Marketplace
- Safeway Shopper Shuttle Stop
- Eastbound Sandy Operations Center 16610 Champion Way
- Best Western Government Camp Eastbound
- Bigfoot RV Park Eastbound
- Sleepy Hollow
- Wildwood Recreation
- Resort at the Mountain
- Hwy 26 & Veneer Ln
- Industrial Way-Fred Meyer Garden Center
- Sandy Ridge Trail
- Gov't Camp Loop-Summit Eastbound
- Bigfoot RV Park Westbound
- Cedar Ridge Middle School
- Bluff Park
- Sandy High School
- Gary St
- Sandy Transit Center Hoffman St
- Hwy 26 & E Greenwood Dr Westbound
- Heritage Square
- Shorty's Corner Eastbound
- Alder Creek Rd Eastbound
- Hoodland Senior Center Eastbound
- Welches Rd & Hwy 26
- Rhododendron Eastbound
- Hwy 26 & Kirkwood Rd
- Brightwood Store
- Fred Meyer
- Dorman Center-Salmon Rd
- Ski Bowl Eastbound
- Collins Lake Resort Eastbound
- Gov't Camp Loop-Summit Westbound
- Collins Lake Resort Westbound
- Timberline Lodge
- Hwy 26 & Champion Way
- Village Mart-Rhododendron
- Trailhead & Langensand Rd Southbound
- Dubarko Rd & Ross Ave
- Living Way Fellowship (Dubarko Rd.)
- Hwy 211 & Village Blvd Southbound
- Gresham Village
- Powell Blvd & SE 3rd St Westbound
- Powell Blvd & NE Hogan Dr
- Powell Blvd & NE Liberty Ave Westbound
- Powell Blvd & NE Elliot Westbound
- NE Kelly Ave & NE 8th St Gresham Transit Center
- Powell Blvd & SE Elliott Ave Eastbound
- Powell Blvd & SE Liberty Ave Eastbound
- Powell Blvd & SE Hogan Rd Eastbound
- Powell Blvd & SE 3rd St Eastbound
- SE Hwy 26 & Industrial Way
- SE Eagle Creek Rd at 27400
- SE Eagle Creek Rd at 28200
- SE Eagle Creek Rd & SE Duus Rd
- SE Eagle Creek Rd & NW Hill Way
- NE 6th Ave & NE Main St
- NW 3rd Ave & NE Main St Northbound
- NE 1st Ave & SE Main St
- SE 3rd Ave & SE Main St
- SE 4th Ave & SE Main St
- N Broadway St & NE 6th Ave
- 600 Block NW Wade St
- NW Hill Way & SE Eagle Creek Rd
- SE Hinman Ave & SE Eagle Creek Rd
- SE Eagle Creek Rd at 29900
- SE Eagle Creek Rd at 29200 Southbound
- SE Eagle Creek Rd at 28400
- SE Eagle Creek Rd & SE Heiple Rd
- SE Eagle Creek Rd & SE Currin Rd
- Eagle Crest Mobile Home Park
- SE Eagle Creek Rd & SE Wildcat Mountain Dr
- Eagle Creek Post Office
- Hwy 211 & SE Jackknife Rd
- Hwy 211 & Upper SE Jackknife Rd
- Hwy 211 & Village Blvd Northbound
- Dubarko Rd & SE Jacoby Rd
- St Micheal's Catholic Church, SE Langensand Rd
- SE Langensand Rd & McCormick Dr
- Sandy High School
- Procter Blvd & Strauss Ave
- 5th St & Hood Ave
- Hwy 26 & SE 362nd Eastbound
- SE Eagle Creek Rd & Hwy 211
- Vista Loop
- Barlow Ridge Park
- Sandy Transit Operations Center
- Sandy Cinema
- Hamilton Ridge Playground
- Cascadia Village Park Northbound
- Hwy 26 and SE 362nd Drive
- Orient Dr & Crescent Dr
- Orient Dr at Kelly's Corner Market
- Orient Dr at Backroads Pub and Grub
- Compton Rd & Hwy 26
- Hwy 212 at Boring Post Office
- SE Wally Road & Trailhead
- School Avenue & Fireman Way
- Safeway in Damascus Westbound
- 172 Ave & Rock Creek Blvd
- SE Sunnyside Rd & SE 169th Ave
- SE Sunnyside Road & 162nd Ave
- SE Sunnyside Road & 147th Ave Westbound
- SE Sunnyside Road & 119th Dr
- KAISER PERMANTE Emergency Entrance
- 10010 Stevens Rd
- Clackamas Town Center
- Clackamas Town Center Parking Garage
- 10000 Stevens Rd
- SE Sunnyside Rd (Kaiser Sunnyside)
- 169th Ave and Misty Dr
- 172nd Ave Eastbound
- Safeway in Damascus Eastbound
- Hwy 212 & Food Mart
- Hwy 212 & CC Bank
- SE Compton at Big Foot Museum
- Orient Dr & Bobby Bruce Ln
- Orient Dr at B and R Rental
- Orient Dr & Crescent Rd
- Pioneer Blvd & Scales Ave Eastbound
- Hwy 211 & Ponder Ln
- Hwy 26 & SE 362nd Dr Westbound
- Hwy 26 & Industrial Way
- Hwy 26 & Ruben Ln Eastbound
- Sandy Community Center
- Proctor Blvd & Strauss Ave
- Proctor Blvd & Beers Ave
- NE Hood Ave & NE 2nd St Southbound
- Hwy 211 & SE Judd Rd Southbound
- Big Valley Eastbound
- Hwy 211 & Barlow Trail Estates Eastbound
- SE Eagle Creek Rd & Hwy 211 Northbound
- SE Eagle Creek Rd & SE Risberg Ln
- SE Eagle Creek Rd & SE Riverside Way Southbound
- SE Eagle Creek Rd & Folsom Rd Southbound
- SE Eagle Creek Rd & SE Heiple Rd Southbound
- SE Eagle Creek Rd & SE Duus Rd Southbound
- 29600 Block SE Eagle Creek Rd Southbound
- SE Eagle Creek Rd & SE River Mill Rd Southbound
- SE Eagle Creek Rd & SE Strubhar Ln Southbound
- Estacada Public Library Southbound
- NE 6th Ave & NE Main St Eastbound
- NE Main St & NE 3rd Ave (Clackamas River Elementary School)
- NE Main St & E 1st Ave
- SE Main St & SE 3rd Ave Northbound
- Hwy 211 & Barlow Trail Estates Westbound
- McCormick Dr & Wolf Dr Eastbound
- McCormick Dr & SE Langensand Rd Southbound
- Best Western Government Camp Westbound
- Hwy 26 & E Sleepy Hollow Dr
- Hwy 26 & E Greenwood Dr Eastbound
- Kaiser Sunnyside Medical Center (SE 101st St)
- SE Orient Dr & SE Crescent Rd Westbound
- SE Orient Dr & SE Crescent Rd Eastbound
- Kelly’s Corner Market (SE Orient Dr & SE Kelso Rd)
- SE Compton Rd & Hwy 26 Westbound
- SE Compton Rd & Hwy 26 Eastbound
- Boring Post Office
- Hwy 212 at Clackamas County Bank
- SE 172nd Ave & SE Rock Creek Blvd
- SE Sunnyside Rd & SE 169th Ave Westbound
- SE Sunnyside Rd & SE 162nd Ave Westbound
- SE Sunnyside Rd & SE 162nd Ave Eastbound
- SE Sunnyside Rd & SE Misty Dr Westbound
- SE Sunnyside Rd & SE 147th Ave Eastbound
- SE Sunnyside Rd & SE 132nd Ave Westbound
- SE Sunnyside Rd & SE 132nd Ave Eastbound
- SE Sunnyside Rd & SE 119th Ave Westbound
- SE Sunnyside Rd & SE 119th Ave Eastbound
- SE Sunnyside Rd & SE Valley View Terr Westbound
- SE Sunnyside Rd & SE Valley View Terr Eastbound
- SE School Ave & SE Fireman Way
- SE Hwy 212 & SE Fireman Way Eastbound
- Kaiser Sunnyside Medical Center (SE Sunnyside Rd - Eastbound)
- Hwy 212 & SE 202nd Ave
- SE Orient Dr & SE Bobby Bruce Ln Eastbound
- SE Eagle Creek Rd & Hwy 211 Southbound
- SE Eagle Creek Rd & SE Wildcat Mountain Dr Southbound
- SE Eagle Creek Rd & SE Wildcat Mountain Dr Northbound
- SE Eagle Creek Rd & SE Currin Rd Northbound
- SE Eagle Creek Rd & SE Heiple Rd Northbound
- 28400 Block SE Eagle Creek Rd Northbound
- SE Eagle Creek Rd & SE Duus Rd Northbound
- 29200 Block SE Eagle Creek Rd Northbound
- SE Eagle Creek Rd & SE Hinman Ave Northbound
- SE Eagle Creek Rd & NW Hill Way Northbound
- SE Eagle Creek Rd & NW Hill Way Southbound
- NE 6th Ave & N Broadway St Westbound
- SE Vista Loop Dr & Hwy 26
- NE Hood Ave & NE 5th St Southbound
- Hwy 26 & Alder Creek Rd
- Hoodland Senior Center Westbound
- E Welches Rd & Hwy 26 Westbound
- Ski Bowl Westbound
- Hwy 26 & SE 362nd Dr
- Dubarko Rd & Pacific Ave
- Hwy 211 & SE Ponder Ln
- NW Campus Dr & NW Commerce Ct
- NW Campus Dr & NW Park Ave
- Brady's Brats/Bigfoot Growlers
- Rita's Bar
- and 6 more (see the full list on the map or in the GeoJSON)
Over time
Overall score across the last 2 checks — down 1.2 since 2026-07-31.
Show the numbers
| Check | Score | Change |
|---|---|---|
| 2026-07-31 | 64.4 | first check |
| 2026-08-01 | 63.2 | down 1.2 |
What changed since your last check
- Correctness no change
- Freshness no change
- Rider experience no change
- Realtime quality down 5.8
Everything we checked
11 findings, ordered by severity.
Show every finding
- Warning256 instances
256 of 256 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)
- Warning130 instances
130 of 130 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)
- Warning86 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 scheduled trips move faster between stops than a bus can.
Usually a typo'd stop time; riders get arrival times no bus can meet.
Fix: Check the flagged stop times for transposed minutes. (A few minutes per flagged trip.)
Finding code: fast_travel_between_consecutive_stops · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning3 instances
3 of 6 trips scheduled during the sampling window had no live predictions.
Riders on those trips get schedule data dressed up as realtime. Caltrans expects every operating trip in TripUpdates.
Fix: Check with your AVL vendor that every vehicle assignment flows into TripUpdates, including school-day and tripper runs. (A vendor data-mapping question.)
Finding code: scorecard_rt_trip_coverage · Read the fix guide · See GTFS-Realtime reference (opens the GTFS-Realtime reference on an external site)
- Warning2 instances
Fast travel between far stops (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'fast_travel_between_far_stops' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Finding code: fast_travel_between_far_stops · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning1 instance
Some stops sit far from the route line they belong to.
Trip planners may draw the bus route through the wrong streets or point riders to the wrong corner.
Fix: Check the flagged stops' coordinates and the route shape in your scheduling software; re-snap whichever is misplaced. (A few minutes per flagged stop.)
Finding code: stop_too_far_from_shape · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning1 instance
On some trips the stops fall along the route line in a different order than the schedule lists.
Trip planners can draw the bus doubling back or skipping ahead, which confuses riders reading the map.
Fix: Check the stop order and the shape direction in your scheduling software; the shape is often drawn backwards. (A few minutes per flagged trip.)
Finding code: stops_match_shape_out_of_order · 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)
- Info9 instances
Some service dates fall outside the date window set in feed_info.txt.
feed_info.txt should span every day your service runs, so apps know when the data applies.
Fix: Widen feed_start_date and feed_end_date to cover all service dates, or fix the dates that fall outside. (Two fields in feed_info.txt, or one export setting.)
Finding code: service_window_outside_feed_period · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Info1 instance
The feed has a stretch of two weeks or more with no service running.
A long gap can mean dates were left out of the calendar. Apps then show no trips on those days.
Fix: Check whether the gap is real, like a seasonal break; if not, add the missing dates to the calendar. (A review of your calendar dates.)
Finding code: big_gap_in_service · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
NTD GTFS readiness Needs attention
This feed is close to NTD-ready. Service data runs out in 30 days; renew before you certify.
- Published Ready
- Published at a public URL.
- Valid Ready
- Passes validation with no errors.
- Current Needs attention
- Service data runs out in 30 days; renew before you certify.
- 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 130 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. Service data runs out in 30 days; renew to qualify. 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 Not yet
- Service data runs out in 30 days; renew to qualify.
- 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.
- 86 of 256 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.
Realtime reliability
The realtime feed responded on 100.0% of 200 checks over the last 34 days, with 4s 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 142s late versus the schedule, and stayed within 930s nine times in ten. They were on time (about a minute early to five late) 58.3% 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 has 516 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.
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 73 / 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 50 / 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 82 / 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/sandy-area-metro-sam-2739/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.