Feed status · checked 2026-08-01
Cascades East Transit (CET)
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 fetch returned HTTP 403.
Measured 3 of 4 score categories from the Mobility Database's mirror copy of the feed.
How we measured this
Confidence in this measurement: provisional.
- Realtime quality was not measured this run. It does not count against the grade.
- The agency's own feed URL was unreachable, so the Mobility Database's hosted mirror copy was scored instead.
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 the feed with a calendar that reaches further out, and set feed_info feed_end_date past your next service change.Likely your export tool
Service data ended 830 day(s) ago. When the calendar runs out, trip planners stop showing this agency even though the buses are still running. Riders are told the service does not exist.
⏱ Usually one export setting; export on a schedule so it never lapses again.worth about +100 points in its category
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
323 of 323 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
574 of 574 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
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
- Service data ended 830 day(s) ago.
- Next action
- Re-export the feed with a calendar that reaches further out, and set feed_info feed_end_date past your next service change.
- 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
- 323 of 323 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
- 574 of 574 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.
Re-export the feed with a calendar that reaches further out, and set feed_info feed_end_date past your next service change. · Read the fix guide
Make the change. Make this change in whatever tool produces your feed, then re-export.
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_boarding to 1 (accessible) or 2 (not accessible) for every stop. A field survey can start with the busiest stops. · Read the fix guide
Make the change. Make this change in whatever tool produces your feed, then re-export.
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. Make this change in whatever tool produces your feed, then re-export.
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 was 830 days ago.
- 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 your vendor a fix request
You may not control the GTFS export yourself. Copy this and send it to whoever runs your scheduling software export. It names each fix with the validator notice and a guide link.
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 10 kinds of issue across 92 instances (0 error, 47 warning, 45 informational).
Service data ended 830 day(s) ago. Trip planners have likely already dropped this feed.
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.
3 accessibility depth signals
7 route badge(s) pair a color and text color below the WCAG 4.5:1 contrast bar (1, 2, 22, 26, 29, and more).
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.
302 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set ("6th Street @ Adams Avenue (S)", "3rd Street @ Madras DMV (E)", "Highway 126 @ Powell Butte Church (S)", and more).
Consider: Add tts_stop_name with the spoken form, e.g. 'Main Street and Second Avenue', for the affected stops.
This feed models stations or entrances but has no pathways.txt and levels.txt.
Consider: Add pathways.txt connecting entrances, platforms, and elevators, and levels.txt for each floor, so the step-free route is described.
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.
This agency publishes realtime, but the feed needs an access key we don't have 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 323 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.
- 22 (gray)
- 26 (red)
- 24 (teal)
- 30 (orange)
- 7 (green)
- 20 (yellow)
- 28 (purple)
- 29 (pink)
- 1 (red)
- 2 (gray)
- 3 (blue)
- 4 (blue)
- 5 (orange)
- 6 (purple)
- 11 (teal)
- 18 (teal)
- 25 (red)
- 9 (yellow)
| Route | Type | Line color |
|---|---|---|
| 31 LaPine/Sunriver | Bus | teal (no shape in feed) |
| 22 Redmond/Madras | Bus | gray |
| 26 Redmond/Prineville | Bus | red |
| 24 Redmond / Bend | Bus | teal |
| 30 LaPine/Bend | Bus | orange |
| 7 Greenwood | Bus | green |
| 20 Warm Springs/Madras | Bus | yellow |
| 28 Sisters/Redmond | Bus | purple |
| 19 Lava Butte | Bus | teal (no shape in feed) |
| 29 Sister/Bend | Bus | pink |
| 1 South 3rd Street | Bus | red |
| 2 Brookswood | Bus | gray |
| 3 Newport | Bus | blue |
| 4 North 3rd Street | Bus | blue |
| 5 Wells Acres/Reed Market | Bus | orange |
| 6 Reed Market/Wells Acres | Bus | purple |
| 11 Galveston/14th | Bus | teal |
| 18 Mountain Service | Bus | teal |
| 17 Ride The River | Bus | teal (no shape in feed) |
| 25 Crooked River Ranch/Redmond | Bus | red |
| 9 15th Street/Murphy Road | Bus | yellow |
List every stop
- 6th Street @ Adams Avenue (S)
- 3rd Street @ Madras DMV (E)
- Highway 126 @ Powell Butte Church (S)
- Sisters Park & Ride
- Burgess Road @ Wickiup Junction (E)
- Arrowleaf Trail @ Ray's Food Place (S)
- 11th Street @ Oliver Lemon's (W)
- 4th Street @ Stryker Park (N)
- Redmond Transit Center
- Franklin Avenue @ 2nd Street (N)
- Franklin Avenue @ Lava Road (N)
- Wall Street @ Downtown Library (W)
- Bond Street @ Scalehouse Loop (W)
- Bond Street @ Old Mill (W)
- Bond Street @ Reed Market Road (W)
- Brookswood Boulevard @ McClellan Road (W)
- Brookswood Boulevard @ Rock Bluff Lane (W)
- Brookswood Boulevard @ Powers Road (W)
- Brookswood Boulevard @ Copper Canyon Way (W)
- Brookswood Boulevard @ Powers Road (E)
- Brookswood Boulevard @ Rock Bluff Lane (E)
- Brookswood Boulevard @ Hillwood Court (E)
- Brookswood Boulevard @ Reed Market Road (E)
- Bond Street @ Powerhouse Drive (E)
- Bond Street @ Scalehouse Loop (E)
- Bond Street @ Industrial Way (E)
- Bond Street @ Colorado Avenue (E)
- Bond Street @ Kansas Avenue (E)
- Franklin Avenue @ Broadway Street (N)
- Drake Park
- Galveston Avenue @ Federal Street (N)
- Galveston Avenue @ 13th Street (S)
- Galveston Avenue @ 13th Street (N)
- Riverside Boulevard @ Tumalo Avenue (E)
- Franklin Avenue @ Wall Street (S)
- 14th Street @ Knoll Avenue (W)
- Simpson Avenue @ Columbia Street (N)
- 14th Street @ Cumberland Avenue (E)
- 14th Street @ Cumberland Avenue (W)
- Newport Avenue @ 14th Street (N)
- Newport Avenue @ College Way (N)
- Shevlin Park Road @ Torrey Pines Drive (N)
- Regency Street @ Mount Washington Drive (W)
- College Way @ COCC Library (W)
- College Way @ COCC Boyle Center (W)
- College Way @ Portland Avenue (W)
- Newport Avenue @ College Way (S)
- Newport Avenue @ 6th Street (S)
- Newport Avenue @ Awbrey Road (S)
- Newport Avenue @ Awbrey Road (N)
- Newport Avenue @ Harmon Boulevard (N)
- Newport Avenue @ 11th Street (N)
- Newport Avenue @ 11th Street (S)
- Greenwood Avenue @ Harriman Street (S)
- Greenwood Avenue @ 2nd Street (S)
- Greenwood Avenue @ 2nd Street (N)
- Butler Market Road @ Boyd Acres Road (S)
- Butler Market Road @ Jones Road (E)
- Butler Market Road @ Huettl Lane (S)
- Wells Acres Road @ Daggett Lane (S)
- Wells Acres Road @ Cordata Drive (S)
- Wells Acres Road @ Purcell Boulevard (E)
- Wells Acres Road @ MVHS (S)
- 27th Street @ Jack Harris Stadium MVHS (W)
- 27th Street @ Rosemary Drive (W)
- 27th Street @ Conners Avenue (W)
- 27th Street @ Wichita Way (W)
- Neff Road @ St. Charles (N)
- Purcell Boulevard @ Lotus Drive (W)
- Purcell Boulevard @ Sam's Loop (W)
- Purcell Boulevard @ Aspen Ridge Senior Care (W)
- Purcell Boulevard @ Paula Drive (W)
- Purcell Boulevard @ The Forum (Costco) (W)
- 27th Street @ Grand Way (E)
- 27th Street @ Forum Drive (E)
- 27th Street @ Snowberry Village (E)
- 27th Street @ Stone Lodge (E)
- 27th Street @ Conners Avenue (E)
- 27th Street @ Yellow Ribbon Drive (E)
- 27th Street @ Faith Drive (E)
- Wells Acres Road @ Weeping Willow Drive (N)
- Wells Acres Road @ Purcell Boulevard (W)
- Wells Acres Road @ Cordata Drive (N)
- Wells Acres Road @ Village Court (N)
- Butler Market Road @ Sandy Drive (N)
- Butler Market Road @ Jones Road (W)
- Butler Market Road @ Boyd Acres Road (N)
- Studio Road @ Foxhollow (W)
- Studio Road @ Underwood Avenue (W)
- 4th Street @ Seward Avenue (W)
- 4th Street @ Olney Avenue (W)
- Hawthorne Station
- 4th Street @ Penn Avenue (E)
- 4th Street @ Seward Avenue (E)
- Studio Road @ Underwood Avenue (E)
- Studio Road @ Majesty Lane (E)
- Studio Road @ Butler Market Road (E)
- 3rd Street @ Butler Market Road (E)
- 3rd Street @ Bend River Promenade (E)
- 3rd Street @ Sugar Loaf (E)
- Jamison Street @ Halfway Road (E)
- Jamison Street @ Highway 20 (E)
- 3rd Street @ ODOT Park n Ride (W)
- 3rd Street @ Burger King (W)
- 3rd Street @ North Subway (W)
- 3rd Street @ O.B. Riley Road (W)
- 3rd Street @ Vail Avenue (W)
- 3rd Street @ Seward Avenue (W)
- 3rd Street @ Penn Avenue (W)
- 3rd Street @ Dekalb Avenue (W)
- Brookswood Boulevard @ Pinebrook Boulevard (W)
- Lodgepole Drive @ Mahogany Street (W)
- Poplar Street @ Lodgepole Drive (N)
- Poplar Street @ Onyx Street (N)
- Poplar Street @ Brookswood Boulevard (N)
- Brookswood Boulevard @ River Rim Drive (E)
- Brookswood Boulevard @ Hollygrape Street (S)
- Brookswood Boulevard @ Montrose Pass Street (S)
- Brookswood Boulevard @ Lodgepole Drive (S)
- Brookswood Boulevard @ Pinebrook Boulevard (E)
- Brookswood Boulevard @ Copper Canyon Way (E)
- Franklin Avenue @ 6th Street (S)
- Franklin Avenue @ 9th Street (S)
- Bear Creek Road @ 13th Street (S)
- 27th Street @ Bear Creek Road (W)
- 27th Street @ Clairaway Avenue (W)
- 27th Street @ Reed Market Road (W)
- Reed Market Road @ Pettigrew Road (N)
- 15th Street @ Bronzewood Avenue (E)
- Reed Market Road @ Bend Senior Center (N)
- 15th Street @ Riviera Drive (E)
- Bear Creek Road @ 13th Street (N)
- Franklin Avenue @ 9th Street (N)
- Franklin Avenue @ 7th Street (N)
- 3rd Street @ Davis Avenue (W)
- 3rd Street @ Yew Lane (W)
- 3rd Street @ Cleveland Avenue (W)
- 3rd Street @ Reed Market Road (W)
- 3rd Street @ Fred Meyer Complex (W)
- 3rd Street @ Powers Road (W)
- 3rd Street @ Auto Lane (W)
- 3rd Street @ Walmart (W)
- 3rd Street @ Factory Outlet (E)
- 3rd Street @ Powers Road (E)
- 3rd Street @ Reed Lane (E)
- 3rd Street @ Fred Meyer Complex (E)
- 3rd Street @ Reed Market Road (E)
- 3rd Street @ Cleveland Avenue (E)
- 3rd Street @ Roosevelt Avenue (E)
- 3rd Street @ Yew Lane (E)
- 3rd Street @ Miller Avenue (E)
- 3rd Street @ Penn Avenue (E)
- 3rd Street @ Wagner Mall (E)
- 3rd Street @ Webster Avenue (E)
- Greenwood Avenue @ Bond Street (N)
- Newport Avenue @ 14th Street (S)
- Galveston Avenue @ Harmon Boulevard (S)
- Franklin Avenue @ Lava Road (S)
- Simpson Avenue @ Century Drive (N)
- 14th Street @ Knoll Avenue (E)
- 3rd Street @ Nels Anderson Road (E)
- 27th Street @ Anne Lane (W)
- Bond Street @ Industrial Way (W)
- Norton Avenue @ 4th Street (S)
- 5th Street @ Kearney Avenue (E)
- 5th Street @ Kearney Avenue (W)
- 5th Street @ Marshall High School (W)
- Norton Avenue @ 4th Street (N)
- Riverbend Park
- Cascade Lakes Byway @ Mt. Bachelor West Village (W)
- Simpson @ Safeway
- Columbia @ Simpson
- Columbia @ Colorado
- Columbia @ Emkay
- Century Drive @ Donovan Avenue (OSU) (E)
- Quail Trail @ Juniper Street (S)
- Warm Springs Street @ Warm Springs Market (S)
- Foster Street @ Bray Avenue (W)
- Tenino Road @ Warm Springs Community Center (E)
- Highway 97 @ Dollar Tree (W)
- 3rd Street @ Norton Avenue (E)
- Wall Street @ Arizona Avenue (W)
- Reed Market Road @ Fargo Lane (N)
- 27th Street @ Reed Market Road (E)
- Chandler @ The Bulletin
- 27th Street @ Bear Creek Road (E)
- E Street @ 1st Street (N)
- Highway 97 @ Robal Road (W)
- Robal Lane @ Hunnell Road (S)
- 2nd Street @ Crook County Library (S)
- 3rd Street @ Harwood Avenue (N)
- Main Avenue @ Cedar Street (N)
- Main Avenue @ Oak Street (N)
- 4th Street @ Huntington Road (N)
- Columbia @ Shevlin Hixon
- Hawthorne Station
- Hawthorne Station
- Hawthorne Station
- Hawthorne Station
- Hawthorne Station
- Cherry Lane @ Plateau Travel Plaza (S)
- Canal Boulevard @ Walmart (W)
- Sunriver Public Library
- St. Charles Family Clinic
- Great Hall Loop @ Sunriver Resort (W)
- Museum at Warm Springs
- Simpson @ Century
- Scout Drive @ Tribal Administration (S)
- Emkay @ Columbia (Temporary)
- SHARC Parking Lot (SW)
- Victory Way @ La Pine Senior Center (N)
- Shelvin Park @ Newport Hills (Temporary Stop)
- Holiday Street @ Warm Springs Department of Human Services (W)
- Mt. Bachelor Sunrise Lodge
- Mt. Bachelor Shop
- Mt. Bachelor Receiving
- 3rd Street @ Roosevelt Avenue (W)
- Baker Court @ Riverwoods Country Store (S)
- Drafter Rd at HWY 97
- Badger Road @ Chinook Drive (S)
- Old Fire Hall @ Shad Road (N)
- Panorama Park @ Panorama Road (N)
- Quail Road @ Chukkar Drive (W)
- Walmart @ Oak Tree Ln (S)
- Fred Meyer @ Veterans Way (E)
- Cascade Lakes Welcome Station
- Wanoga Sno Park
- Swampy Lakes
- Dutchman Flat
- Park & Float
- Robal Lane @ Hunnell Road (N)
- Jamison Street @ Highway 20 (W)
- Jamison Street @ Halfway (W)
- Jamison Street @ All Seasons RV (W)
- 9th Street @ Bend High (W)
- 9th Street @ Woodland Boulevard (W)
- Wilson Avenue @ Parr Lumber (S)
- 15th Street @ Hollis Lane (W)
- 15th Street @ Friar Tuck Lane (W)
- 15th Street @ Sherwood Forest Drive (W)
- 15th Street @ Alpenglow Park (W)
- 15th Street @ Caldera High (W)
- Brosterhous Road @ Nativity Lutheran (E)
- Brosterhous Road @ The Pines (E)
- Murphy Road @ Countryside Place (N)
- Murphy Road @ Mel Court (N)
- Parrell Road @ Murphy Road (E)
- Parrell Road @ Badger Road (E)
- Powers Road @ Parrell Road (N)
- Madras Adams @ Tracie
- and 73 more (see the full list on the map or in the GeoJSON)
Over time
Overall score across the last 4 checks — unchanged since 2026-07-31.
Show the numbers
| Check | Score | Change |
|---|---|---|
| 2026-07-25 | 48.4 | first check |
| 2026-07-30 | 48.4 | no change |
| 2026-07-31 | 48.4 | no change |
| 2026-08-01 | 48.4 | 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
16 findings, ordered by severity.
Show every finding
- Error1 instance
Service data ended 830 day(s) ago.
When the calendar runs out, trip planners stop showing this agency even though the buses are still running. Riders are told the service does not exist.
Fix: Re-export the feed with a calendar that reaches further out, and set feed_info feed_end_date past your next service change. (Usually one export setting; export on a schedule so it never lapses again.)
Finding code: scorecard_feed_expired · Read the fix guide · See GTFS Best Practices (opens GTFS Best Practices on an external site)
- Warning574 instances
574 of 574 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)
- Warning323 instances
323 of 323 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)
- Warning39 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
9 of 574 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)
- Warning3 instances
Some service calendars in the feed have already ended.
Expired calendars are dead weight and can hide real schedule problems from your staff and vendors.
Fix: Remove past service periods the next time you export the feed. (One setting in most export tools.)
Finding code: expired_calendar · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning1 instance
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)
- Warning1 instance
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
This feed's service calendar runs out within the next 7 days.
When the calendar ends, Google Maps and other trip planners drop your agency entirely. Riders see no service at all.
Fix: Export and publish an updated GTFS feed that covers at least the next 30 days of service. (Usually a re-export from your scheduling software.)
Finding code: feed_expiration_date7_days · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning1 instance
Some rider-facing names are in ALL CAPS or all lowercase.
ALL-CAPS stop and headsign names are harder to read in apps and are read awkwardly by screen readers.
Fix: Use mixed case for stop names and headsigns (e.g. 'Main St & 2nd Ave', not 'MAIN ST & 2ND AVE'). (Often a bulk fix in your scheduling software.)
Finding code: mixed_case_recommended_field · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning1 instance
Many of the feed's trips don't run at all in the next 7 days.
It usually means old service periods are still in the export, making the feed bigger and harder to check.
Fix: Trim past service periods the next time you export. (One setting in most export tools.)
Finding code: trip_coverage_not_active_for_next7_days · 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)
- Warning1 instance
This feed models stations or entrances but has no pathways.txt.
Trip planners can't guide riders through the station, and there is no step-free route information for wheelchair users.
Fix: Add pathways.txt connecting entrances, platforms, and any elevators, with a level for each. (Worth it for multi-level or large stations; flat stops don't need it.)
Finding code: scorecard_station_no_pathways · 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)
- Info3 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 Not ready
Resolve this before you certify on the D-10. Service data expired 830 days ago, so FTA would find the link out of date.
- Published Ready
- Published at a public URL.
- Valid Ready
- Passes validation with no errors.
- Current Not ready
- Service data expired 830 days ago, so FTA would find the link out of date.
- 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 574 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 expired 830 days ago. 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 expired 830 days ago.
- 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.
- 39 of 322 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.
Below the Google and Apple Maps four-week coverage bar. This feed's last day of service has passed, so Google and Apple Maps will stop showing your agency. Re-export with a calendar that covers at least the next four weeks.
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 68 / 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 0 / 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 60 / 100
- GTFS Best Practices for rider-facing fields. MobilityData grading covers stop names and headsigns.
- Realtime quality Access needed to measure
- 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/cascades-east-transit-cet/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.