Renfe (Alta Velocidad, Larga y Media Distancia)

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

Since the previous compatible check, 1 finding was no longer reported:

• Stop time with arrival before previous departure time (flagged by the MobilityData validator).

This records feed state, not who made a change or why.

What needs attention next

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

1. Add feed_start_date and feed_end_date to feed_info.txt and include calendar end dates in your export.

   Neither feed_info.txt nor the calendars state when service ends. Nobody can tell when this feed will go stale.

   Estimated effort: Likely a one-time export setting.

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

   1038 of 1038 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. Set wheelchair_accessible on every trip. If every vehicle is accessible, this may be one default; otherwise use the value for each trip.

   5550 of 5550 trips don't say whether the vehicle is wheelchair accessible. Even with accessible stops, riders need to know the transit vehicle itself can take them.

   Estimated effort: A default or per-trip field in your export.