Steel Valley Regional Transit Authority

What this grade measures

The quality of the schedule data this agency publishes 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:

1. Confirm your next service period is published: export its calendar and set feed_info feed_end_date past it.

   The published calendar ended 213 day(s) ago at a boundary between the feed's own scheduled service periods. The calendar encodes distinct service periods (like academic terms), so this looks like a planned transition rather than a lapse — but trip planners still show nothing until the next period is published.

   Estimated effort: One export when the next period's schedule is set.

2. Set wheelchair_boarding to 1 (accessible) or 2 (not accessible) for every stop. A field survey can start with the busiest stops.

   133 of 133 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.

   Estimated effort: A column in stops.txt; your scheduling software likely has it.

3. 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.

   176 of 176 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.

   Estimated effort: Usually one value per route pattern in your scheduling source.