Feed status · checked 2026-08-01
ClackCo Connects (Clackamas County) Realtime Static
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 80 minutes ago; last changed 80 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
150 of 150 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
45 of 45 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 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.
The feed contains no fare information. Riders see 'fare unknown' in trip planners and can't budget their trip; visitors are most affected.
⏱ A small file for most flat-fare systems.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
- 150 of 150 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
- 45 of 45 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
- The feed contains no fare information.
- Next action
- 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.
- 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.
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.
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. · 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
- One or more realtime feeds were reachable; live-arrival coverage is not known.
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 4 kinds of issue across 74 instances (0 error, 73 warning, 1 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.
2 accessibility depth signals
4 route badge(s) pair a color and text color below the WCAG 4.5:1 contrast bar (CCC, CI, EST, OC).
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 ("10800 Block SE Highway 212", "130th Ave & Jennifer St", "15900 Block SE 82nd 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 outside service hours: 3 of 3 configured feeds healthy; vehicle position plausibility was not measurable.
Routes and stops
Each route is drawn once, using the longest shape its trips follow; stops are the dots.
This feed has 150 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.
- CI (teal)
- OC (green)
- CCC (purple)
- EST (orange)
| Route | Type | Line color |
|---|---|---|
| CI Clackamas Industrial Area Shuttle | Bus | teal |
| OC Oregon City Shuttle | Bus | green |
| CCC CCC Xpress | Bus | purple |
| EST Estacada | Bus | orange |
List every stop
- Oregon City Shopping Center
- Main & 15th
- Oregon City Transit Center Northbound
- Oregon City Senior Center
- Oregon City City Hall
- 5th & Monroe
- Linn & Oak
- Charman & Telford Road
- South End Road & Barker Road Southbound
- South End Road and Amanda Court
- South End Road and Lawton Road Southbound
- South End Road and Oregon City Christian Church
- South End & Lafayette Avenue Southbound
- Partlow Road & Pine Pl Southbound
- Central Point Road & McCord Southbound
- McCord Road & Orchard Grove Dr Southbound
- Leland Road & Reddaway Ave Southbound
- Leland Road & Meyers Southbound
- Meyers Road and Frontier Parkway
- Meyers Road & Gaffney Lane Southbound
- Meyers Road at Pioneer Ridge Southbound
- WinCo (Oregon City)
- CCC Oregon City Campus
- Molalla & Oregon City Post Office
- Molalla & Gaffney Ln
- Molalla & Clairmont
- Beavercreek & Safeway
- 300 Block Beavercreek Rd
- Beavercreek & Library Ct
- 200 Block Warner - Milne
- Warner - Milne & Linn
- Linn & Ethel
- Linn & Holmes
- Grocery Outlet
- Molalla & Pearl
- Molalla & Willamette
- Division & Selma
- Division & 13th
- Providence Willamette Falls
- 15th Street & Polk Street
- Jackson Street & 15th Street
- Jackson & 12th
- Washington & 16th
- Abernethy & Redland Rd
- McLoughlin & Oregon City Shopping Center Northbound
- Clackamas Town Center Transit Center Northbound
- SE 97th & Talbert Dr Southeast
- SE 97th & Lawnfield
- SE Lawnfield Road and SE Industrial Way
- Minuteman Way and SE Tolbert Street - Northbound
- SE 82nd Dr & Tolbert
- SE 82nd Drive and SE Clackamas Road
- 15900 Block SE 82nd Dr
- SE Hwy 212 & Evelyn
- 10800 Block SE Highway 212
- Hwy 212 & Fred Meyer Dc Entr
- Highway 212 & SE 122nd Avenue
- SE 122nd Avenue and SE Jennifer Street
- Jennifer & 114th
- SE Jennifer Street and SE 106th Street
- SE Jennifer Street and SE Evelyn Street
- 16700 Block SE 82nd Dr
- 16500 Block SE 82nd Dr
- SE 82nd Dr & Greenhouse Square
- SE 82nd Dr & Clackamas
- SE 82nd Drive and Tolbert Street
- Minuteman Way and SE Tolbert Street - Southbound
- SE 97th Avenue & SE Lawnfield Road
- SE 97th & Talbert Dr Northwest
- Clackamas Town Center Transit Center
- 98th ct & Lawnfield S
- 98th ct & Lawnfield
- 82nd Drive & SE Clackamas Road
- MinuteMan and Tolbert Northbound
- 82nd and 212 Eastbound
- CCC Harmony Campus Westbound
- 82nd & 212 East
- Minuteman and Tolbert - Northbound
- CCC Harmony Campus Eastbound
- Clairmont Dr - CCC Campus - Eastbound
- St. Philip Benizi Church Eastbound
- Main & 3rd Northbound
- Estacada City Hall Eastbound
- Main & 3rd Southbound
- Estacada City Hall Westbound
- St. Philip Benizi Church Westbound
- Zobrist and 3rd
- Oregon City High School Westbound
- Oregon City High School Eastbound
- Main & 4th
- Clairmont Dr - CCC Campus - Westbound
- S Redland Rd & S Ferguson Eastbound
- S Maplelane Rd & S Holly Ln Eastbound
- S Maplelane Rd
- S Maplelane Rd and Hwy 213
- S Maplelane Rd 2
- S Maplelane Rd & S Holly Ln Westbound
- S Redland Rd & S Ferguson Westbound
- S Beavercreekk & S Maplelane
- CCC Oregon City Campus Northbound
- 130th Ave & Jennifer St
- Highway 212 & 130th Ave
- S 2nd & Tumwater Northbound
- McLoughlin & W Arlington
- McLoughlin & W Gloucester Northbound
- McLoughlin & Glen Echo Northbound
- McLoughlin & Hull Northbound
- Jennings & SE Rose Northbound
- Jennings & SE Oatfield Northbound
- Oatfield & Thiessen Northbound
- Oatfield & Roethe Northbound
- Thiessen & SE Webster
- Thiessen & SE Hill Northbound
- Webster & Lake Rd
- SE 21st & Adams
- Washington & 21st Ave
- Rusk & Hwy 224
- Rusk Rd & SE Kellogg Creek Dr Northbound
- Aldercrest & SE Rusk Rd Northbound
- Milwaukie Community Center Southbound
- Hwy 213 & Glen Oak Southbound
- Hwy 213 & Glen Oak Northbound
- Glen Oak & Beavercreek Southbound
- Beavercreek & Glen Oak Northbound
- Aldercrest & SE Rusk Rd Southbound
- Beavercreek & Glen Oak Southbound
- Central Point Road & McCord Northbound
- Glen Oak and Beavercreek Northbound
- Jennings & SE Oatfield Southbound
- Jennings & Rose Southbound
- Oatfield & Thiessen Southbound
- Oregon City Shopping Center Southbound
- Oregon City Transit Center Southbound
- S 2nd & Tumwater Southbound
- Oatfield & Roethe Southbound
- Milwaukie Community Center Northbound
- Thiessan & SE Hill Southbound
- McLoughlin & Hull Southbound
- McLoughlin & Glen Echo Southbound
- McLoughlin & Gloucester Southbound
- Oak Lodge Library Southbound
- Oak Lodge Library Northbound
- Concord and SE River Rd Southbound
- River Rd and Concord Northbound
- River Road and Cooke Southbound
- River Road and Cooke Northbound
- River Road and Roethe Southbound
- River Road and Roethe Northbound
- River Road and Jennings Southbound
- River Road and Jennings Northbound
Over time
Overall score across the last 2 checks — unchanged since 2026-07-31.
Show the numbers
| Check | Score | Change |
|---|---|---|
| 2026-07-31 | 67.5 | first check |
| 2026-08-01 | 67.5 | 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-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.
Everything we checked
8 findings, ordered by severity.
Show every finding
- Warning150 instances
150 of 150 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)
- Warning71 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)
- Warning45 instances
45 of 45 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)
- Warning36 instances
36 of 45 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)
- Warning1 instance
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)
- Warning1 instance
Some stops sit far from the route line, going by the feed's own distance values.
Trip planners may draw the route down the wrong streets or point riders to the wrong corner.
Fix: Check the flagged stops' shape_dist_traveled against the route shape, and re-generate it on export if they disagree. (Usually an export-tool fix, not hand editing.)
Finding code: stop_too_far_from_shape_using_user_distance · 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)
- Info1 instance
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)
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 45 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.
- 71 of 150 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.
Clears the Google and Apple Maps four-week coverage bar. This feed has 517 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 84 / 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 33 / 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/clackco-connects-clackamas-county-2740/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.