Société de transport de Lévis (STLévis)

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. Set wheelchair_boarding to 1 (accessible) or 2 (not accessible) for every stop. A field survey can start with the busiest stops.

   1206 of 1599 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.

2. Set trip_headsign to the trip's last stop or its overall destination.

   Some trip headsigns name a stop along the way, not the final destination. The sign should tell riders where the bus ends up, so a midpoint name can send them the wrong way.

   Estimated effort: Usually a bulk edit in your scheduling software.

3. Check the flagged file name for a typo of a standard GTFS file. Remove it if it is a vendor extra.

   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.

   Estimated effort: A quick look at the flagged file.