Resource details

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

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

Download availability

2025-12-16
100%
2025-12-17
100%
2025-12-18
100%
2025-12-19
100%
2025-12-20
100%
2025-12-21
100%
2025-12-22
100%
2025-12-23
100%
2025-12-24
100%
2025-12-25
100%
2025-12-26
100%
2025-12-27
100%
2025-12-28
100%
2025-12-29
100%
2025-12-30
100%
2025-12-31
100%
2026-01-01
100%
2026-01-02
100%
2026-01-03
100%
2026-01-04
100%
2026-01-05
99.3%
2026-01-06
100%
2026-01-07
100%
2026-01-08
100%
2026-01-09
100%
2026-01-10
100%
2026-01-11
100%
2026-01-12
100%
2026-01-13
100%
2026-01-14
100%
2026-01-15
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

2 errors, 70 warnings

Validation carried out using the current GTFS file and the GTFS-RT the 2026-01-15 at 08:07 Europe/Paris using the MobilityData GTFS-RT validator.

Errors

stop_time_update departure time is before arrival time E025 2 errors

Within the same stop_time_update, arrival and departures times can be the same, or the departure time can be later than the arrival time - the departure time should never come before the arrival time.

Sample errors
  • trip_id 1-1023476323 stop_sequence 3 departure_time 08:02:19 (1768460539) is less than the same stop arrival_time 08:02:24 (1768460544) - departure time must be equal to or greater than arrival time
  • trip_id 1-33685505 stop_sequence 11 departure_time 08:03:00 (1768460580) is less than the same stop arrival_time 08:03:02 (1768460582) - departure time must be equal to or greater than arrival time

Warnings

vehicle_id not populated W002 23 errors

vehicle_id should be populated for TripUpdates and VehiclePositions

Sample errors
  • trip_id 1-1694565363 does not have a vehicle_id
  • trip_id 1-1711734785 does not have a vehicle_id
  • trip_id 1-1728119815 does not have a vehicle_id
  • trip_id 1-1744897041 does not have a vehicle_id
  • trip_id 1-17760354 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 2 min 13 sec old which is greater than the recommended age of 65 seconds

schedule_relationship not populated W009 46 errors

trip.schedule_relationship and stop_time_update.schedule_relationship should be populated

Sample errors
  • trip_id 1-1694565363 stop_sequence 1 (and potentially more for this trip) does not have a schedule_relationship
  • trip_id 1-1694565363 does not have a schedule_relationship
  • trip_id 1-1711734785 stop_sequence 1 (and potentially more for this trip) does not have a schedule_relationship
  • trip_id 1-1711734785 does not have a schedule_relationship
  • trip_id 1-1728119815 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 378 24 times (80 % of validations)
W009 trip.schedule_relationship and stop_time_update.schedule_relationship should be populated 756 24 times (80 % of validations)
W008 The data in a GTFS-realtime feed should always be less than one minute old 13 13 times (43 % of validations)
E025 Within the same stop_time_update, arrival and departures times can be the same, or the departure time can be later than the arrival time - the departure time should never come before the arrival time. 13 8 times (27 % of validations)
E003 All trip_ids provided in the GTFS-rt feed must exist in the GTFS data, unless the schedule_relationship is ADDED 61 2 times (7 % of validations)
E004 All route_ids provided in the GTFS-rt feed must exist in the GTFS data 33 2 times (7 % of validations)
E011 All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt 853 2 times (7 % of validations)

GTFS-RT feed content

Entities

Entities present in this feed at 2026-01-15 at 23:11 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-01-15 at 23:11 Europe/Paris. You can look at the GTFS-RT documentation.

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