Resource details

File name: Horaires temps réel des lignes du réseau ELSA
Format: gtfs-rt

This resource file is part of the dataset Réseau urbain ELSA.

Download availability

2026-10-03
100%
2026-10-04
100%
2026-10-05
100%
2026-10-06
100%
2026-10-07
100%
2026-10-08
100%
2026-10-09
100%
2026-10-10
100%
2026-10-11
100%
2026-10-12
100%
2026-10-13
100%
2026-10-14
100%
2026-10-15
100%
2026-10-16
100%
2026-10-17
100%
2026-10-18
100%
2026-10-19
100%
2026-10-20
100%
2026-10-21
100%
2026-10-22
100%
2026-10-23
100%
2026-10-24
100%
2026-10-25
100%
2026-10-26
100%
2026-10-27
100%
2026-10-28
100%
2026-10-29
100%
2026-10-30
100%
2026-10-31
100%
2026-11-01
100%
2026-11-02
100%
Learn more
We test this resource download availability every hour by making an HTTP HEAD request with a timeout of 5 seconds. If we detect a downtime, we perform subsequent tests every 10 minutes, until the resource is back online.

For SIRI and SIRI Lite feeds, we perform a GET request: a 401 or 405 status code is considered successful. In case of HTTP 500, the feed will be considered unavailable, unless the body appears to contain SOAP.

Validation details

❌9 errors, 64 warnings

Validation carried out using the current GTFS file and the GTFS-RT the 2026-11-02 at 08:23 Europe/Paris using the MobilityData GTFS-RT validator.

Errors

GTFS-rt trip_id does not exist in GTFS data and does not have schedule_relationship of ADDED E003 7 errors

All trip_ids provided in the GTFS-rt feed must exist in the GTFS data, unless the schedule_relationship is ADDED

Sample errors
  • trip_id JT_L_K110-0839 does not exist in the GTFS data and does not have schedule_relationship of ADDED
  • trip_id JT_L_K111-0759 does not exist in the GTFS data and does not have schedule_relationship of ADDED
  • trip_id JT_L_K111-0912 does not exist in the GTFS data and does not have schedule_relationship of ADDED
  • trip_id JT_L_K110-0801 does not exist in the GTFS data and does not have schedule_relationship of ADDED
  • trip_id JT_L_K110-0914 does not exist in the GTFS data and does not have schedule_relationship of ADDED

GTFS-rt route_id does not exist in GTFS data E004 1 error

All route_ids provided in the GTFS-rt feed must exist in the GTFS data

Sample errors
  • route_id ELSA_7 does not exist in the GTFS data routes.txt

GTFS-rt stop_id does not exist in GTFS data E011 1 error

All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt

Sample errors
  • trip_id JT_L_KELSA_7-1645 stop_id 0:ORSCHWILLER_Chapelle_A does not exist in GTFS data stops.txt

Warnings

vehicle_id not populated W002 21 errors

vehicle_id should be populated for TripUpdates and VehiclePositions

Sample errors
  • trip_id JT_L_K104-0907 does not have a vehicle_id
  • trip_id JT_L_K108-0837 does not have a vehicle_id
  • trip_id JT_L_K109-0807 does not have a vehicle_id
  • trip_id JT_L_K110-0839 does not have a vehicle_id
  • trip_id JT_L_K111-0759 does not have a vehicle_id

Header timestamp is older than 65 seconds W008 1 error

The data in a GTFS-realtime feed should always be less than one minute old

Sample errors
  • header.timestamp is 1 min 10 sec old which is greater than the recommended age of 65 seconds

schedule_relationship not populated W009 42 errors

trip.schedule_relationship and stop_time_update.schedule_relationship should be populated

Sample errors
  • trip_id JT_L_K104-0907 stop_sequence 1 (and potentially more for this trip) does not have a schedule_relationship
  • trip_id JT_L_K104-0907 does not have a schedule_relationship
  • trip_id JT_L_K108-0837 stop_sequence 1 (and potentially more for this trip) does not have a schedule_relationship
  • trip_id JT_L_K108-0837 does not have a schedule_relationship
  • trip_id JT_L_K109-0807 stop_sequence 1 (and potentially more for this trip) does not have a schedule_relationship
Validate this GTFS-RT now

Previous validations

Here is a recap of all the error types encountered over the last 30 days.

Error ID Description Errors count Number of occurences
W002 vehicle_id should be populated for TripUpdates and VehiclePositions 339 25 times (83 % of validations)
W009 trip.schedule_relationship and stop_time_update.schedule_relationship should be populated 676 25 times (83 % of validations)
E003 All trip_ids provided in the GTFS-rt feed must exist in the GTFS data, unless the schedule_relationship is ADDED 85 21 times (70 % of validations)
W008 The data in a GTFS-realtime feed should always be less than one minute old 12 12 times (40 % of validations)
E004 All route_ids provided in the GTFS-rt feed must exist in the GTFS data 3 2 times (7 % of validations)
E011 All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt 5 2 times (7 % of validations)

GTFS-RT feed content

Entities

Entities present in this feed at 2026-11-02 at 23:43 Europe/Paris.

vehicle_positions (0) service_alerts (0) trip_updates (0)

Entities seen in the last 7 days.

trip_updates

Decoded GTFS-RT feed

See full payload

Here is the decoded GTFS-RT feed Protobuf at 2026-11-02 at 23:43 Europe/Paris. You can look at the GTFS-RT documentation.

{ "header": { "gtfsRealtimeVersion": "1.0", "timestamp": "1793659395" } }