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
Static feed for realtime
Based on the feed this agency publishes
down 1.5 since 2026-07-08
Ahead of 56% of all tracked agencies and 54% 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 15 minutes ago; last changed 15 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
Re-export with a validity window that reaches at least 60 days out.Likely your export tool
Service data runs out in 29 day(s). When the calendar runs out, trip planners stop showing this agency. Fixing it now is calmer than after riders notice.
⏱ One export setting.worth about +51 points
Agencies here usually clear this within about 1 week (based on 61 observed fixes).
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
136 of 136 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
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.
⏱ 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).
This feed is generated by your Passio system from the route and stop data they maintain. Send the fix list to your Passio contact.
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.
Re-export with a validity window that reaches at least 60 days out. · 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.
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_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.
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. This feed is generated by your Passio system from the route and stop data they maintain. Send the fix list to your Passio contact.
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 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.
Send the agency a note
Supporting this agency? Copy this and email it to them. It names what lapsed, why it matters to riders, and the one setting to change.
Score by category
The MobilityData validator flagged 5 kinds of issue across 61 instances (0 error, 60 warning, 1 informational).
Service data runs out in 29 day(s). Publish an updated feed soon or riders will lose trip planning.
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.
105 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 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.
- 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 |
This feed has 136 stops.
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
- Aldercret & SE Rusk Rd Southbound
- Beavercreek & Glen Oak Southbound
- Central Point Road & McCord Northbound
- Glen Oak and Beavercreek Northbound
- Jennings & SE Oatfield Northbound
- 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
Over time
Overall score across the last 20 checks — down 1.5 since 2026-07-08.
Show the numbers
| Check | Score | Change |
|---|---|---|
| 2026-06-19 | 60.5 | first check |
| 2026-06-20 | 67.5 | up 7.0 |
| 2026-06-21 | 67.5 | no change |
| 2026-06-22 | 67.5 | no change |
| 2026-06-23 | 67.5 | no change |
| 2026-06-24 | 67.5 | no change |
| 2026-06-25 | 67.5 | no change |
| 2026-06-26 | 67.5 | no change |
| 2026-06-27 | 67.5 | no change |
| 2026-06-28 | 67.5 | no change |
| 2026-06-29 | 67.5 | no change |
| 2026-06-30 | 67.5 | no change |
| 2026-07-01 | 67.5 | no change |
| 2026-07-02 | 67.5 | no change |
| 2026-07-04 | 67.5 | no change |
| 2026-07-05 | 67.5 | no change |
| 2026-07-06 | 67.5 | no change |
| 2026-07-07 | 67.5 | no change |
| 2026-07-08 | 67.2 | down 0.3 |
| 2026-07-09 | 65.7 | down 1.5 |
What changed since your last check
- Correctness down 4.0
- Freshness down 1.7
- Rider experience no change
- Realtime quality up 1.5
What changed in this feed
Overall score fell 1.5 points since 2026-07-08.
The feed file was re-published since 2026-07-08.
New since 2026-07-08 (2 findings)
- Warning1 instance
This feed's service calendar runs out within the next 30 days.
Validator rule: feed_expiration_date30_days · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning1 instance
Service data runs out in 29 day(s).
Validator rule: scorecard_feed_expiring_soon · Read the fix guide · See GTFS Best Practices (opens GTFS Best Practices on an external site)
Subscribe to this feed’s changes (Atom) to hear about grade drops in a reader, with no sign-up.
What changed over time
On 2026-06-19 this feed started at grade D. On 2026-06-20 it cleared scorecard_rt_trip_coverage. As of 2026-07-09 it holds grade D.
A plain-language history of this feed, newest first.
- 2026-06-20 Score rose 7 points, realtime rose 35 points.
Everything we checked
- Warning136 instances
136 of 136 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)
- Warning57 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.)
Agencies here usually clear this within about 1 week (based on 11 observed fixes).
Validator rule: 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 (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)
- Warning36 instances
36 of 45 trips have no headsign.
Riders at the stop can't tell which direction a bus is going.
Fix: Populate trip_headsign to match what the bus displays. (Usually a bulk edit in your scheduling software.)
Validator rule: scorecard_missing_headsigns · Read the fix guide · See GTFS Best Practices (opens GTFS Best Practices on an external site)
- Warning1 instance
This feed's service calendar runs out within the next 30 days.
If a new feed isn't published before it ends, trip planners will drop your agency and riders will see no service.
Fix: Schedule a feed re-export now so the new calendar is live well before the current one ends. (Usually a re-export from your scheduling software.)
Agencies here usually clear this within about 1 week (based on 24 observed fixes).
Validator rule: feed_expiration_date30_days · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning1 instance
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)
- Warning1 instance
Stop too far from shape using user distance (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'stop_too_far_from_shape_using_user_distance' 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: 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
Service data runs out in 29 day(s).
When the calendar runs out, trip planners stop showing this agency. Fixing it now is calmer than after riders notice.
Fix: Re-export with a validity window that reaches at least 60 days out. (One export setting.)
Agencies here usually clear this within about 1 week (based on 61 observed fixes).
Validator rule: scorecard_feed_expiring_soon · Read the fix guide · See GTFS Best Practices (opens GTFS Best Practices 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)
- Info1 instance
Service window outside feed period (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'service_window_outside_feed_period' 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 17 observed fixes).
Validator rule: service_window_outside_feed_period · Read the fix guide · 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 1 change
For example: 'route_long_name': 'Estacada ' -> 'Estacada'
Run it yourself on your own copy of the feed: scorecard autofix <feed.zip> --out corrected.zip
NTD certification readiness Needs attention
This feed is close to NTD-ready. Service data runs out in 29 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 29 days; renew before you certify.
- 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 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 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. Service data runs out in 29 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 29 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.
- 57 of 136 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 105 checks over the last 16 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 540 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 80 / 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 48 / 100
- The FTA National Transit Database expectation of a valid, current feed. Google Transit: an expired calendar drops the agency from Maps.
- Rider experience 33 / 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/clackco-connects-clackamas-county-2740/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.