TAD ligne Arrens-Marsous - Lourdes

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:

1. Publish the calendar for the current or next service period and set feed_info feed_end_date past it.

   This on-demand service has no published calendar. The last one ended 18 day(s) ago. Between service periods this is normal. But if buses are running with no published calendar, trip planners show nothing.

   This one is about the feed as a whole, so there is no share of it to count.

   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.

   9 of 33 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 9 of 33 stops, about 27% of them.

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

3. Review the rule documentation for 'equal_shape_distance_diff_coordinates_distance_below_threshold' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.

   Equal shape distance diff coordinates distance below threshold (flagged by the MobilityData validator). See the linked rule for what this affects.

   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: Varies.