Feed status · checked 2026-11-14
Western Reserve Transit Authority
Based on the feed source on file; publisher ownership is not verified
Service mode Bus
unchanged since 2026-11-13
Cataloged in Ohio.
Source feed: https://myvalleystops.wrtaonline.com/InfoPoint/gtfs-zip.ashx Version history on the Mobility Database
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.5, validator 8.0.1.
Checked for changes 16 hours ago; last changed 2 days ago.
Measured 3 of 4 score categories from the feed URL on file (publisher not verified).
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 configured feed URL. Publisher ownership of that URL is not verified.
Confidence describes how much the pipeline could measure this run, not the feed itself. It never changes the grade.
About this feed
Western Reserve Transit Authority’s published feed lists 23 bus routes, 1,129 scheduled trips and 973 stops. Its service dates run from 2026-11-23 through 2027-03-01. The published file last changed on 2026-11-12.
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
973 of 973 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.
Fixing this covers all 973 stops in the feed.
⏱ 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
1129 of 1129 trips don't say whether the vehicle is wheelchair accessible. Even with accessible stops, riders need to know the bus itself can take them.
Fixing this covers all 1,129 trips in the feed.
⏱ 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.
This one is about the feed as a whole, so there is no share of it to count.
⏱ A small file for most flat-fare systems.worth about +15 points in its category
Riders and need behind these fixes
- This feed carries no National Transit Database ID, so annual rider-trips are not known for it.
- Ohio as a whole measures lower on transit need. That is a statewide reading, not one for this feed's service area. Source: US Census ACS 5-year 2022, statewide overlay, as of 2026-11-02.
These describe this feed only. They do not rank agencies, and they do not change the grade or the order of the fixes.
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.
- Finding
- Fix 01 in Top things to fix: its feed evidence and the requested 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
- Finding
- Fix 02 in Top things to fix: its feed evidence and the requested 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
- Finding
- Fix 03 in Top things to fix: its feed evidence and the requested 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
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.
Fix 01 · Read the fix guide for scorecard_wheelchair_boarding_unknown
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. See this feed's finding-clearance log.
Fix 02 · Read the fix guide for scorecard_wheelchair_accessible_unknown
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. See this feed's finding-clearance log.
Fix 03 · Read the fix guide for scorecard_no_fare_data
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. 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 107 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
- 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.
Score by category
The MobilityData validator flagged 10 kinds of issue across 8936 instances (0 error, 8934 warning, 2 informational).
Service data covers the next 107 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
7 route badge(s) pair a color and text color below the WCAG 4.5:1 contrast bar (2, 4, 7, 8, 11, 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.
887 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set ("Tenny Ave & Struthers Liberty Rd", "Jacobs Rd & Gerwig Ave", "Gibson St & Samuel Ave (FLAG STOP), Youn", 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.
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 973 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.
- 1 (gray)
- 10 (gray)
- 11 (pink)
- 12 (yellow)
- 13 (white)
- 14 (purple)
- 15 (green)
- 2 (red)
- 24 (red)
- 25 (pink)
- 26 (teal)
- 27 (teal)
- 28 (red)
- 3 (brown)
- 4 (green)
- 5 (yellow)
- 56 (pink)
- 57 (red)
- 6 (white)
- 7 (teal)
- 8 (teal)
- 80 (yellow)
- 9 (white)
| Route | Type | Line color |
|---|---|---|
| 1 1 Elm St | Bus | gray |
| 10 10 Belmont Ave | Bus | gray |
| 11 11 Cornersburg | Bus | pink |
| 12 12 Lansdowne Blvd | Bus | yellow |
| 13 13 McGuffey Rd | Bus | white |
| 14 14 Mosier | Bus | purple |
| 15 15 Struthers | Bus | green |
| 2 2 Oak St | Bus | red |
| 24 24 Midlothian Blvd Crosstown | Bus | red |
| 25 25 Boardman-Canfield Loop | Bus | pink |
| 26 26 Boardman East Loop | Bus | teal |
| 27 27 Austintown Loop | Bus | teal |
| 28 28 Warren Express | Bus | red |
| 3 3 Wilson Ave | Bus | brown |
| 4 4 Steel St | Bus | green |
| 5 5 South Ave | Bus | yellow |
| 56 56 YSU White Loop | Bus | pink |
| 57 57 YSU Red Loop | Bus | red |
| 6 6 Fifth Ave | Bus | white |
| 7 7 Glenwood Ave | Bus | teal |
| 8 8 Market St | Bus | teal |
| 80 80 Lordstown Express | Bus | yellow |
| 9 9 Austintown | Bus | white |
List every stop
- Tenny Ave & Struthers Liberty Rd
- Jacobs Rd & Gerwig Ave
- Gibson St & Samuel Ave (FLAG STOP), Youn
- Cornersburg
- Connecticut Ave & N Meridian Rd
- Salt Springs Rd & N Meridian Rd
- N Meridian Rd & Oakwood Ave
- N Meridian Rd & Salt Springs Rd
- Burlington & Turin St.
- N Meridian Rd &Vestal Rd
- Meridian Place
- Phoenix House
- Turin & Burlington St.
- Mahoning Ave & N Wickliffe Circle
- Burkey Rd & Westgate Blvd
- Mahoning Ave & S Wickliffe Circle
- New Rd & Fountain Square Dr
- Kirk Rd & Evelyn Rd
- US Hwy 422 & Tibbetts-Wick Rd
- US Route 422 & Tibbits Wick
- Burlington St
- Rulli Brothers
- Mahoning Ave & Raccoon Rd
- S Raccoon Rd & Burkey Rd
- Burkey Rd & S Raccoon Rd
- Kirk Rd & S Raccoon Rd
- Glenwood & 224
- S Raccoon Rd & Kirk Rd
- Nantucket Dr & Woodhurst Dr
- US Route 422 & State Highway 46
- US Route 422 & State Highway 46
- Mahoning Ave & Evans Ave
- Westchester Dr & Idaho Rd
- Westchester Dr & Idaho Rd
- Exec Apt @ Westchester Dr
- Mahoning Ave & Westchester Dr
- Eastwood Mall
- McGuffey Rd & Miami St
- Canfield Circle
- Mahoning Ave & Canfield-Niles Rd
- Mahoning Ave & 46 @RubyTuesday
- Austintown Plaza
- Infocision
- Walmart Entrance (FLAG STOP)
- McGuffey Rd & Miami St
- US Route 422 & Adelaide Ave SE
- US Route 422 & Oak Knoll Ave SE
- Laird Ave SE & South St SE
- E Market St & Laird Ave SE
- E Market St & Chestnut Ave SE
- Kendis Circle
- Main Ave SW & Lane Dr SW
- Main Ave SE & 1St St SW
- Lane Dr SW & Valley Ave SW
- Highland Terrace
- Wilson Ave & Keystone St
- Shops @ Boardman Park
- Seneca Oaks
- McGuffey Rd & Berkley Ave
- Berkley Ave & McGuffey Rd
- Akron Childrens Hospital Beeghly
- 4th Street SW @ Tod Ave SW
- Belmont Ave & Liberty St
- Youngstown Poland Rd @ Hamilton Ave
- Youngstown Poland Rd @ Creed St (FLAG ST
- Main St @ Woodward Ave
- Youngstown Poland Rd @ Harvey St (FLAG S
- Youngstown Poland Rd @ Elm St (Flag Sto
- Youngstown Poland Rd @ Holbrook Rd (FLAG
- Youngstown Poland Rd @ Thalia Ave (FLAG
- Rt 224 @ Pennsylvania Ave
- Rt 224@Audubon Rd
- Marcs
- South Ave & Madonda St
- Sparkle Market
- Sparkle Market
- South Ave @ Midlothian Blvd
- Midlothian Blvd @ South Ave
- E Midlothian Blvd @ South Ave
- South Ave @ Midlothian Blvd
- Oak Hill Renaissance Center
- Oak Hill Renaissance Center
- Hillman Way @ Midlothian Blvd
- Hillman St & Midlothian Blvd
- VA Clinic
- Belmont Ave @ Citizens Bank
- Belmont Ave & Laurel St
- Belmont Ave (Cafaro Offices)
- Belmont Ave (Goodwill)
- Belmont Ave & Trumbull Ave
- Ferndale Ave & Firnley Ave
- Glenwood Ave & Devonshire Dr South
- Glenwood Ave & Brainard Dr
- Glenwood Ave @ Ewing Rd
- Salvation Army
- US Hwy 224 @ Ron Park Pl
- US Hwy 224 @ Starrs Centre Dr
- US Hwy 224 @ Seville Dr
- US Hwy 224 @ N Hillside Rd
- US Hwy 224 @ S Hillside Dr
- Mahoning County Career & Tec Center
- Mahoning Ave & Edwards St (FLAG STOP)
- Mahoning Ave & Four Mile Run Rd
- Mahoning Ave & Idaho Rd
- Mahoning Ave & S Kimberly Ave
- Mahoning Ave & Fitch Blvd
- Orrin Ave & Knapp St
- Struthers Liberty Rd & Blossom Ave
- 16th St & Tenney Ave
- Robinson Rd & 16th St
- 12th st & Tremble (Vasu Manor)
- McCarney Rd & Fincastle Ln
- McCartney Rd & Adeline Ave (Alta)
- Market St & Boardman St
- Market St E Warren Ave
- Market St & E Dewy Ave
- Market St & W Dewey Ave
- Market St & W Boston Ave
- Market St & Indianola Rd
- Market St & Maple Dr
- Market & Woodview Ave
- Market St & Wilda Ave
- Market St & Brookwood Rd
- Market St & Ridgewood Dr
- Market St & Brookfiels Ave
- Market St & S Cadillac Dr
- US Hwy 422 & Lafayette St
- Omar & 8th Street (Flag stop)
- Youngstown Poland Rd & Lynn Ave (FLAG ST
- Mahoning Ave & Whitney Ave S
- US Hwy 422 & Burlington St
- Mahoning Ave & Eleanor Ave
- US Hwy 422 & Amherst Ave
- US Hwy 422 & Trumbull Ave
- S State St & Crumlin Ave
- N State St & E Prospect St
- N State St & Churchill Rd
- N State St & Pittsburg Ave
- N State St & Center Ave
- Mahoning Ave & Four Mile Run
- ETI Technical College
- Mahoning Ave & N Beverly Ave
- Mahoning Ave & Raccoon Rd
- Mahoning Ave & Kleber Ave
- Mahoning Ave & Kimberly Ave
- Oak St & Early Rd
- Oak St & Shehy St
- High St NE & N Park Ave
- Main Ave SW & Franklin St SW
- Fincastle Ln & Rutledge Dr
- McCartney Rd & 6th St (FLAG STOP)
- McCartney Rd & Rutledge Dr (FLAG STOP)
- Coitsville Rd & Buell Ave
- Buell Ave & Coitsville Rd
- Lansdowne Blvd & Kimmel St
- Wilson Ave & S Center St
- Wilson Ave & S Jackson St
- Heritage Manor
- GLI Pool Products
- S Schenly Ave & Dogwood Dr
- Salt Spring R & Ameritech Blvd
- Meridian Services
- E Market St & Laird Ave NE
- E Market St & Linden Ave SE
- High St NE & N Park Ave
- Mahoning Ave NW & South St SW
- W Market St & Buckeye St NW
- Tod Ave NW & Front St SW
- Atkinson Ave & Lansdowne Blvd
- Lansdowne Blvd & Oak St
- Terrace St & Poland Ave
- Poland Ave & Wilson St
- Poland Ave & Omar St
- Extrudex Aluminum
- Moms Meals
- E High Ave & Sunshine Ave
- Mahoning Ave & N Baily Rd
- Warwick Ave & Nelson Ave
- W Front St & N Phelps St
- Oaktree Place
- Oaktree Place
- Lane Dr SW & Valley Ave SW
- Sunshine Ave & Stewart Ave
- McClurg Rd & Tod Ave
- McGuffey Rd & Sunshine Ave
- McGuffey Rd & Sunshine Ave
- Wilson Ave & N Center St
- Bennington Ave & Mackey St
- Bennington Ave & E High Ave
- Bennington Ave & Arch St
- Applewood & South Ave
- Rigby St & S Jackson St
- S Jackson St & Rigby Ave
- Shehy St & S Jackson St
- Oak St & N Jackson St
- Shehy St & S Jackson St
- McGuffey Rd & Magnolia Ave
- Wilson Ave & S Jackson St
- McGuffey Rd & Plazaview Ct
- Oak St & Excelsior Ave (Dollar General)
- E Midlothian Blvd & Louise Ave
- Midlothian Blvd & Port Dr (FLAG STOP)
- Victor Ave & Cedar Ln
- SR 46 & Silica Rd
- S Racoon Rd & New Rd
- Fountain Square Apts
- Kirk Rd & Evelyn Rd
- Schenely Ave & Canfield Rd
- S Schenley Ave & Oran Dr
- S Schenley Ave & Decamp Rd
- S Raccoon Rd & Kerrybrook Dr
- S Raccoon Rd & New Rd
- Joseph Knight Towers
- Home Goods
- Bailey Rd & Bailey Ct
- Macys
- Bailey Rd & Bailey Ct
- Red Roof Inn
- Midlothian Blvd & Rush
- Belmont Ave & Colonial Dr
- Belmont Ave @ Hampton Inn
- Rigby St & S Truesdale Ave
- Rigby St & S Truesdale Ave
- Oak St & N Truesdale Ave
- Shehy St & S Truesdale Ave
- Jacobs Rd & Arcadia Ave
- Norton Manor
- Oak St & N Bruce St (FLAG STOP)
- Shehy St & S Bruce St
- Berkley Ave & Springdale Ave
- Victor Ave & Wright Dr
- Wilson Ave & S Garland Ave
- McGuffey Rd & Jacobs Rd
- McGuffey Rd & N Garland Ave (FLAG STOP)
- Pearl St & Rigby St
- Rigby St & S Pearl St
- E.Dewey&Gibson
- S Pearl St & Shehy St
- S Pearl St & Shehy St
- Springdale Ave & Bentley Ave
- E Midlothian Blvd & Shirley Rd
- Rising Star
- Albert St & Kimmel St
- McGuffey Rd & Albert St
- McGuffey Rd & Albert St
- Albert St & Victor Ave
- Oak St & N Fruit St
- Oak St & N Fruit St
- BOARDMAN WALMART
- Dandridge Nursing Home
- and 723 more (see the full list on the map or in the GeoJSON)
Over time
Overall score across the last 6 checks — unchanged since 2026-11-13.
Show the numbers
| Check | Score | Change |
|---|---|---|
| 2026-11-09 | 44.1 | first check |
| 2026-11-10 | 43.7 | down 0.4 |
| 2026-11-11 | 43.3 | down 0.4 |
| 2026-11-12 | 60.8 | up 17.5 |
| 2026-11-13 | 60.8 | no change |
| 2026-11-14 | 60.8 | no change |
What changed since your last check
- Correctness no change
- Freshness no change
- Rider experience no change
Feed history
Every check on record for this feed, grouped by the published file, newest first. A new file means the published zip changed. Grades from earlier rubric versions are shown with their rubric and are not comparable with today’s grade or the trend above.
| Checked | Published file | Service dates through | Grade at the time |
|---|---|---|---|
| 2026-11-12 to 2026-11-14 (3 checks) | 9297227012bb | 2027-03-01 | Current rubric: see the trend above |
| 2026-11-09 to 2026-11-11 (3 checks) | 1fe36e4e2363 | 2026-11-28 | Current rubric: see the trend above |
| 2026-10-02 to 2026-11-06 (35 checks) | dc88094c88df | 2020-12-05 | F, 17 under rubric 1.4, an earlier scoring contract; not comparable with today’s grade |
| 2026-07-25 to 2026-10-01 (65 checks) | dc88094c88df | 2020-12-05 | F, 17 under rubric 1.3, an earlier scoring contract; not comparable with today’s grade |
| 2026-07-13 to 2026-07-24 (9 checks) | dc88094c88df | 2020-12-05 | F, 16.9 under rubric 1.2, an earlier scoring contract; not comparable with today’s grade |
| 2026-06-19 to 2026-07-12 (24 checks) | dc88094c88df | 2020-12-05 | F, 16.9 under rubric 1.1, an earlier scoring contract; not comparable with today’s grade |
What changed over time
On 2026-11-09 this feed started at grade F. On 2026-11-12 the grade moved from F to D. As of 2026-11-14 it holds grade D.
A plain-language history of this feed, newest first.
- 2026-11-12 Grade went F to D, freshness rose 72 points.
Everything we checked
14 findings, ordered by severity.
Show every finding
- Warning8664 instances
Some scheduled trips move faster between stops than a bus can.
Usually a typo'd stop time; riders get arrival times no bus can meet.
Fix: Check the flagged stop times for transposed minutes. (A few minutes per flagged trip.)
Finding code: fast_travel_between_consecutive_stops · Read the fix guide for fast_travel_between_consecutive_stops · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning1129 instances
1129 of 1129 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 for scorecard_wheelchair_accessible_unknown · See GTFS Schedule reference (opens the GTFS Schedule reference on an external site)
- Warning973 instances
973 of 973 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 for scorecard_wheelchair_boarding_unknown · See GTFS Schedule reference (opens the GTFS Schedule reference on an external site)
- Warning215 instances
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 for stop_too_far_from_shape_using_user_distance · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning26 instances
On some trips the stop distances run a little past the end of the route line.
The stop and shape distance values don't quite line up, so any math that uses them can drift.
Fix: Re-generate shape_dist_traveled on export so stop and shape distances use the same units. (Usually an export-tool fix, not hand editing.)
Finding code: trip_distance_exceeds_shape_distance_below_threshold · Read the fix guide for trip_distance_exceeds_shape_distance_below_threshold · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning23 instances
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)
- Warning2 instances
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 for mixed_case_recommended_field · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning2 instances
On some trips the stops fall along the route line in a different order than the schedule lists.
Trip planners can draw the bus doubling back or skipping ahead, which confuses riders reading the map.
Fix: Check the stop order and the shape direction in your scheduling software; the shape is often drawn backwards. (A few minutes per flagged trip.)
Finding code: stops_match_shape_out_of_order · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning1 instance
feed_info.txt lists no contact email and no contact URL.
Without a contact, apps like Google Maps can't reach you when they find a problem in the feed.
Fix: Add feed_contact_email or feed_contact_url to feed_info.txt. (One field, set once in export settings.)
Finding code: missing_feed_contact_email_and_url · Read the fix guide for missing_feed_contact_email_and_url · 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 for trip_coverage_not_active_for_next7_days · 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 for scorecard_no_fare_data · See GTFS Best Practices (opens GTFS Best Practices on an external site)
- Info1 instance
Future calendar (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'future_calendar' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Finding code: future_calendar · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Info1 instance
Future feed (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'future_feed' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Finding code: future_feed · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Info1 instance
feed_info.txt has no technical contact (feed_contact_email or feed_contact_url).
App makers and state data programs have nobody to email when they spot a problem. Small errors then sit in the feed for months.
Fix: Add feed_contact_email to feed_info.txt. (One field.)
Finding code: scorecard_no_feed_contact · Read the fix guide for scorecard_no_feed_contact · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
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 107 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 1129 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
One requirement remains for this feed to earn 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 107 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.
Clears the Google and Apple Maps four-week coverage bar. This feed has 106 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.
- Correctness 55 / 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 38 / 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.
Part of the Ohio portfolio: the same scorecards for every feed we track in that group, on one free page.
Similar feeds in Ohio
Other scorecards in Ohio, starting with the same kind of service at a similar size. Listed for comparison, not ranked.
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/western-reserve-transit-authority/2026-11-14.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-11-14. 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.