Board packet · transit data quality · checked 2026-10-08

Laketran

Grade C · 77.0 / 100

Unchanged since 2026-10-07.

What this grade measures

The quality of the schedule data in the feed scored here for trip-planning apps: whether riders using Google Maps, Apple Maps, or Transit see current, correct, and complete information. It measures the data feed, not service quality or operations.

Progress this period

No newly cleared items this period. The score and trend above reflect where the feed stands today.

What needs attention next

Three improvements, in priority order, each sized so the board can see what it is approving:

Set wheelchair_accessible on every trip. If every vehicle is accessible, this may be one default; otherwise use the value for each trip.
568 of 568 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 568 trips in the feed.
Estimated effort: A default or per-trip field in your export.
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.
Estimated effort: A small file for most flat-fare systems.
Use mixed case for stop names and headsigns (e.g. 'Main St & 2nd Ave', not 'MAIN ST & 2ND AVE').
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.
This is a validator notice, and the validator decides what each instance covers, so no share of the network can be read from it here.
Estimated effort: Often a bulk fix in your scheduling software.

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-10-05.

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.

Feed evidence: 568 of 568 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

Agency: Laketran
Finding: scorecard_wheelchair_accessible_unknown
Feed evidence: 568 of 568 trips don't say whether the vehicle is wheelchair accessible.
Why it matters: Even with accessible stops, riders need to know the bus itself can take them.
Requested change: 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.
Evidence: https://gtfsscorecard.org/agency/laketran/?finding=scorecard_wheelchair_accessible_unknown#finding-handoff

Produced by the GTFS Scorecard, an open-source data quality tool. A data-quality read to support the board conversation, not an official compliance determination. Live scorecard: https://gtfsscorecard.org/agency/laketran/. Rubric v1.4, validator 8.0.1.