Renfe Cercanías y Rodalies

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

   1155 of 1155 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. Populate trip_headsign to match what the transit vehicle displays.

   127903 of 128144 trips have no headsign. Riders at the stop can't tell which direction a transit vehicle is going.

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