Feed status · checked 2026-08-01
Ride Connection
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 1 days ago; last changed 2 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
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
142 of 142 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
677 of 677 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
Remove retired stops from the export, or add them back to the trips that should serve them.Likely your export tool
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.
⏱ A review pass in your scheduling software.worth about +4 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
- 142 of 142 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
- 677 of 677 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
- Some stops exist in the feed but no trip ever stops at them.
- Next action
- Remove retired stops from the export, or add them back to the trips that should serve them.
- 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. 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_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. 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.
Remove retired stops from the export, or add them back to the trips that should serve them. · 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 is in 184 days.
- Published accessibility data
- Accessibility information is stated for 0% of stops and 0% of trips. This measures published data, not whether stops or vehicles are physically usable.
- Fare information
- Fare information is published using GTFS Fares v1.
- Realtime information
- 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.
Score by category
The MobilityData validator flagged 4 kinds of issue across 52 instances (0 error, 4 warning, 48 informational).
Service data covers the next 184 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 published.
0% of stops state accessibility (0% marked accessible). Reflects what the feed states, not verified physical usability.
1 accessibility depth signal
135 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set ("Forest Grove Senior Center (2037 Douglas St)", "Banks - Log Cabin Park (Sunset Ave & Main St)", "Banks - Greenville City Park (Arborpark Lp & Trellis Wy)", 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.
Fares are applied to trips.
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 142 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.
- GroveLink Employment Loop (green)
- Tualatin Shuttle Blue Line (blue)
- GroveLink Saturday (green)
- CorneliusLink Saturday (green)
- Tualatin Shuttle Red Line (red)
- North Hillsboro Link (green)
- WestLink (green)
- King City Link (green)
- CorneliusLink (green)
- GroveLink West Loop (green)
- GroveLink East Loop (green)
- BethanyLink (green)
| Route | Type | Line color |
|---|---|---|
| GroveLink Employment Loop | Bus | green |
| Tualatin Shuttle Blue Line | Bus | blue |
| GroveLink Saturday | Bus | green |
| CorneliusLink Saturday | Bus | green |
| Tualatin Shuttle Red Line | Bus | red |
| North Hillsboro Link | Bus | green |
| WestLink | Bus | green |
| King City Link | Bus | green |
| CorneliusLink | Bus | green |
| GroveLink West Loop | Bus | green |
| GroveLink East Loop | Bus | green |
| BethanyLink | Bus | green |
List every stop
- Forest Grove Senior Center (2037 Douglas St)
- Banks - Log Cabin Park (Sunset Ave & Main St)
- Banks - Greenville City Park (Arborpark Lp & Trellis Wy)
- North Plains - Downtown (Commercial St & 314th Ave)
- Hillsboro Transit Center - 100 Block SE 4th Ave
- Eldorado Mobile Villas (17055 Eldorado Dr)
- King City Plaza (15705 116th Ave)
- Durham Rd. Plaza (Albertson's)
- Safeway King City (15570 Pacific Hwy)
- 6000 Block Pinefarm Ct (SB)
- 6700 Block Bennett St (WB)
- 6700 Block Bennett St (EB)
- Willamina Ave & Strasburg Dr
- 19th Ave & Mountain View Ln
- 3800 Block Pacific Ave (TriMet stop)
- Cedar St and Pacific Ave
- North Plains - Pacific St & Glencoe Rd
- 19th Ave and Cedar St (TriMet stop)
- Homestead Community (4100 Block Heather St)
- Harleman Park (900 Block Heather St)
- Fred Meyer Cornelius (2200 Baseline St)
- Boones Ferry Rd & Martinazzi Ave (EB)
- Tualatin Park & Ride (SMART stop)
- Boones Ferry Rd & Martinazzi Ave (WB) (TriMet stop)
- Tualatin City Services (10699 Herman Rd)
- Juanita Pohl Center (8513 Tualatin Rd)
- Martinazzi Ave & Mohawk St (TriMet stop)
- Martinazzi Village Apts (2200 Martinazzi Ave)
- Boones Ferry Rd & Apache Dr (TriMet stop)
- Marquis Tualatin (8900 Block Nasoma Ln)
- Kaiser Tualatin (19185 SW 90th Ave)
- Fred Meyer Tualatin (19200 Martinazzi Ave) (TriMet stop)
- 19th Way & 19th Ave (TriMet stop)
- Pacific Ave & Oak St (EB) (TriMet stop)
- Cornelius Headstart (1389 Dogwood St)
- 26th Ave & Dogwood St
- Cornelius Cinemas (200 N 26th Ave)
- Holladay St & 20th Pl
- 17th Ave & Clark St
- Cornelius Library (1500 Block Adair St)
- Centro Cultural (100 Block N 12th Ave)
- Forest Hills Mobile Estates (570 N 10th Ave)
- Walmart Cornelius (100 Block N 4th Ave)
- Grand Lodge WB (3505 Pacific Ave) (TriMet stop)
- North Plains - North Ave & 313th Ave
- Glencoe High School (NB) (2800 Block Glencoe Rd) (TriMet stop)
- Glencoe High School (SB) (3100 Block Glencoe Rd) (TriMet stop)
- King City Civic Association (15245 116th Ave)
- King George Dr & King John Pl
- King George Dr & 123rd Ave
- 12400 Block King George Dr
- 126th Ave & King Richard Dr
- Fischer Rd & 123rd Ave
- Royalty Pkwy & Royalty Ct
- Durham Rd & Summerfield Dr (EB)
- Durham Rd & 108th Ave (EB)
- Durham Rd & Summerfield Dr (WB)
- Durham Rd & 98th Ave (WB)
- Durham Rd & 98th Ave (EB)
- Tigard High School (EB) (9000 Durham Road)
- Tigard High School (WB) (8700 Block Durham Rd)
- 8200 Block Durham Rd (WB) (TriMet stop)
- Durham Rd & 108th Ave (WB)
- 8300 Block Durham Rd (EB) (TriMet stop)
- Durham Rd & 79th Ave (WB) (TriMet stop)
- Durham Rd & 79th Ave (EB) (TriMet stop)
- Durham Rd & 76th Ave (EB) (TriMet stop)
- Durham Rd & Upper Boones Ferry Rd (WB) (TriMet stop)
- Bridgeport Village (WB) (7400 Block Bridgeport Rd)
- Bridgeport Village (EB) (7300 Block Bridgeport Rd)
- Lincoln Park (2700 Block Main St)
- Brooke St & David Hill Rd
- Rogers Park (2327 17th Ave)
- Sherwin Williams (EB) (3650 Pacific Ave)
- PCC Rock Creek Building 5 (17705 Springville Rd) (TriMet stop)
- Joss Ave & Rossetta St (NB)
- Joss Ave & Rossetta St (SB)
- Brugger Rd & 158th Ave (EB)
- Brugger Rd & 158th Ave (WB)
- Kaiser Rd & Springville Rd (NB)
- Kaiser Rd & Springville Rd (SB)
- Bethany Blvd & Kaiser Rd (NB) (TriMet stop)
- Bethany Blvd & Wismer Dr (SB) (TriMet stop)
- Bethany Blvd & Laidlaw Rd (NB) (TriMet stop)
- Bethany Blvd & Laidlaw Rd (SB) (TriMet stop)
- Bethany Village (WB) (15300 Block Central Dr)
- Bethany Village (EB) (15300 Block Central Dr)
- Central Dr & Huserik Dr (EB)
- Central Dr & Huserik Dr (WB)
- Kaiser Rd & 147th Ave (NB)
- Kaiser Rd & 147th Ave (SB)
- Kaiser Rd & West Union Rd (SB)
- 143rd Ave & Thompson Rd (NB)
- 143rd Ave & Oak Hills Dr (SB)
- 143rd Ave & Burton St (NB)
- 143rd Ave & Cornell Rd (SB)
- Science Park Dr & Cornell Rd (NB)
- Sunset High School (WB) (14300 Block Science Park Dr)
- Sunset High School (EB) (14300 Block Science Park Dr)
- Science Park Dr & Murray Blvd (WB)
- Science Park Dr & Murray Blvd (EB)
- Barnes Rd & Cedar Hills Blvd (EB) (TriMet stop)
- Barnes Rd & Cedar Hills Blvd (WB) (TriMet stop)
- Sunset Transit Center (shared w/ Forest Heights Shuttle)
- Royalty Pkwy & Queen Elizabeth St
- Pacific Ave & College Way (TriMet stop)
- Pacific Ave & Cedar St (TriMet stop)
- Casper Ct & Clara Ln (WB)
- THPRD Center
- Casper Court (EB) (Drop-off only)
- Forest Grove City Hall (1924 Council St)
- Maple St & 18th Ave (NB) (Saturday-only stop)
- Main St & Beal Rd
- Forest Grove High School (1401 Nichols Ln)
- Forest Gale Dr & Gales Creek Rd
- 19th Ave & B St
- Thatcher Rd & Gales Creek Rd
- Stites Park (2423 26th Ave)
- Safeway Forest Grove (2836 Pacific Ave)
- Maple St & 18th Ave (SB)
- 15th Ave & Cedar St (Saturday-only stop)
- Yew St & Adair Ave
- 4100 Block 24th Ave
- Main St & University Ave (NB)
- TTM Technologies (1521 Poplar St)
- University Ave & Main St (WB)
- Forest Gale Dr & Watercrest Rd
- Tualatin WES Station
- LAM/Fujimi (11200 Leveton Dr)
- Leveton Dr & 124th Ave
- Sagert at Martinazzi
- Tualatin Library (18878 Martinazzi Ave) (TriMet stop)
- Westmark Center (6999 NE Century Blvd)
- 6000 Block Pinefarm Ct (NB) (Drop-off only)
- 5600 Block Huffman St (WB)
- 5600 Block Huffman St (EB)
- Intel RS-5 (3100 Shute Rd)
- Orenco MAX Station (TriMet stop)
- Spokane Court
- 118th Ave & Myslony St
- Tualatin Rd & Teton Ave
- Teton Ave & Avery St
Over time
Overall score across the last 4 checks — unchanged since 2026-07-31.
Show the numbers
| Check | Score | Change |
|---|---|---|
| 2026-07-25 | 83.7 | first check |
| 2026-07-30 | 83.6 | down 0.1 |
| 2026-07-31 | 83.6 | no change |
| 2026-08-01 | 83.6 | 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
8 findings, ordered by severity.
Show every finding
- Warning677 instances
677 of 677 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)
- Warning162 instances
162 of 677 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)
- Warning142 instances
142 of 142 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)
- Warning4 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)
- Warning1 instance
This feed describes flexible (demand-responsive) service but has no booking_rules.txt.
Riders can see the service area but not how or when to reserve a trip, so they can't actually use the service.
Fix: Add booking_rules.txt saying how far ahead and how to book (phone, app, or web). (A small file; one rule often covers the whole service.)
Finding code: scorecard_flex_no_booking_rules · Read the fix guide · See GTFS Schedule reference (opens the GTFS Schedule reference on an external site)
- Info34 instances
Some files contain columns that are not part of the GTFS spec.
Harmless to riders, but apps ignore these columns and they can hide typos in real column names.
Fix: Check the flagged column names for misspellings of standard GTFS fields; remove them if they are vendor extras. (A quick look at the flagged files.)
Finding code: unknown_column · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Info8 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)
- Info6 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)
Beyond the grade
Opportunities that do not change your grade today: fare detail, on-demand service, and deeper accessibility data.
Flex zones are published but no booking_rules.txt is present.
Consider: Add booking_rules.txt with how far ahead and how to reserve (phone, app, or web).
NTD GTFS readiness Ready
Published at a public URL, valid, current, and identified with agency_id: the four feed checks for RY2026 all hold here. Only your own D-10 and P-50 filings make that official; this is a heads-up, not a determination.
- Published Ready
- Published at a public URL.
- Valid Ready
- Passes validation with no errors.
- Current Ready
- Service data covers the next 184 days.
- agency_id provided Ready
- agency.txt provides agency_id. For RY2026, keep one stable value for each NTD reporter represented in the feed and crosswalk each value on the P-50 form.
- agency_id equals your NTD ID (optional) Not checked yet
- This feed provides agency_id. For RY2026, keep one stable value for each NTD reporter represented in the feed and crosswalk it on the P-50 form. The value does not need to equal the five-digit NTD ID; we do not have that ID on file, so the optional equality comparison is not checked yet.
- shapes.txt covers your trips Ready
- All 677 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
- Service data covers the next 184 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.
Can riders use it?
Checks beyond structural validation: places where the feed is valid but a rider still could not travel.
- 4 of 142 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.
Clears the Google and Apple Maps four-week coverage bar. This feed has 184 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 94 / 100
- GTFS Schedule best practices, checked by the MobilityData validator. MobilityData grading covers stop locations, route names, and colors. Google Transit requires a feed to pass validation for publication. FTA NTD readiness also checks that the published feed is valid.
- Freshness 100 / 100
- GTFS Schedule best practices call for a dataset that stays current. An expired calendar can remove service from Google Transit and other rider trip planners. FTA NTD readiness also checks that the published feed is current.
- Rider experience 56 / 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/ride-connection/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.