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-01
100%
2025-12-02
100%
2025-12-03
100%
2025-12-04
100%
2025-12-05
100%
2025-12-06
100%
2025-12-07
100%
2025-12-08
100%
2025-12-09
100%
2025-12-10
100%
2025-12-11
100%
2025-12-12
100%
2025-12-13
100%
2025-12-14
100%
2025-12-15
100%
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%
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

⚠️27 warnings

Validation carried out using the current GTFS file and the GTFS-RT the 2025-12-31 at 08:14 Europe/Paris using the MobilityData GTFS-RT validator.

Warnings

vehicle_id not populated W002 9 errors

vehicle_id should be populated for TripUpdates and VehiclePositions

Sample errors
  • trip_id 5-184614913 does not have a vehicle_id
  • trip_id 5-235339777 does not have a vehicle_id
  • trip_id 5-17236051 does not have a vehicle_id
  • trip_id 5-17301588 does not have a vehicle_id
  • trip_id 5-637665281 does not have a vehicle_id

schedule_relationship not populated W009 18 errors

trip.schedule_relationship and stop_time_update.schedule_relationship should be populated

Sample errors
  • trip_id 5-184614913 stop_sequence 1 (and potentially more for this trip) does not have a schedule_relationship
  • trip_id 5-184614913 does not have a schedule_relationship
  • trip_id 5-235339777 stop_sequence 1 (and potentially more for this trip) does not have a schedule_relationship
  • trip_id 5-235339777 does not have a schedule_relationship
  • trip_id 5-17236051 stop_sequence 21 (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 532 25 times (83 % of validations)
W009 trip.schedule_relationship and stop_time_update.schedule_relationship should be populated 1,064 25 times (83 % of validations)
W008 The data in a GTFS-realtime feed should always be less than one minute old 14 14 times (47 % 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. 49 9 times (30 % of validations)
E003 All trip_ids provided in the GTFS-rt feed must exist in the GTFS data, unless the schedule_relationship is ADDED 138 5 times (17 % of validations)
E004 All route_ids provided in the GTFS-rt feed must exist in the GTFS data 76 5 times (17 % of validations)
E011 All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt 1,603 5 times (17 % of validations)
E022 stop_time_update arrival/departure times between sequential stops should always increase - they should never be the same or decrease. 14 2 times (7 % of validations)

GTFS-RT feed content

Entities

Entities present in this feed at 2025-12-31 at 20:21 Europe/Paris.

trip_updates (1) vehicle_positions (0) service_alerts (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 2025-12-31 at 20:21 Europe/Paris. You can look at the GTFS-RT documentation.

{ "entity": [ { "id": "SM:5-17825810", "tripUpdate": { "stopTimeUpdate": [ { "arrival": { "delay": -114, "time": "1767207960" }, "departure": { "delay": -114, "time": "1767207966" }, "stopId": "207", "stopSequence": 29 }, { "arrival": { "delay": -123, "time": "1767208008" }, "departure": { "delay": -123, "time": "1767208017" }, "stopId": "209", "stopSequence": 30 }, { "arrival": { "delay": -113, "time": "1767208081" }, "departure": { "delay": -113, "time": "1767208087" }, "stopId": "211", "stopSequence": 31 }, { "arrival": { "delay": -130, "time": "1767208130" }, "stopId": "213", "stopSequence": 32 } ], "timestamp": "1767208110", "trip": { "routeId": "1", "tripId": "5-17825810" } } } ], "header": { "gtfsRealtimeVersion": "1.0", "timestamp": "1767208880" } }