gtfs-rt Transport open dataset - Horaires temps réel des lignes du réseau SYLVIA for Réseau urbain Sylvia

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

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

❌260 errors, 66 warnings

Validation carried out using the current GTFS file and the GTFS-RT the 2025-12-12 at 08:03 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 22 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 1-17760352 does not exist in the GTFS data and does not have schedule_relationship of ADDED
trip_id 1-17760354 does not exist in the GTFS data and does not have schedule_relationship of ADDED
trip_id 1-2835415041 does not exist in the GTFS data and does not have schedule_relationship of ADDED
trip_id 1-2852192257 does not exist in the GTFS data and does not have schedule_relationship of ADDED
trip_id 1-33620979 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 10 errors

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

Sample errors

route_id 169 does not exist in the GTFS data routes.txt
route_id 170 does not exist in the GTFS data routes.txt
route_id 20 does not exist in the GTFS data routes.txt
route_id 26 does not exist in the GTFS data routes.txt
route_id 30 does not exist in the GTFS data routes.txt

GTFS-rt stop_id does not exist in GTFS data E011 228 errors

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

Sample errors

trip_id 1-17760352 stop_id 211 does not exist in GTFS data stops.txt
trip_id 1-17760352 stop_id 213 does not exist in GTFS data stops.txt
trip_id 1-17760354 stop_id 492 does not exist in GTFS data stops.txt
trip_id 1-17760354 stop_id 368 does not exist in GTFS data stops.txt
trip_id 1-17760354 stop_id 151 does not exist in GTFS data stops.txt

Warnings

vehicle_id not populated W002 22 errors

vehicle_id should be populated for TripUpdates and VehiclePositions

Sample errors

trip_id 1-17760352 does not have a vehicle_id
trip_id 1-17760354 does not have a vehicle_id
trip_id 1-2835415041 does not have a vehicle_id
trip_id 1-2852192257 does not have a vehicle_id
trip_id 1-33620979 does not have a vehicle_id

schedule_relationship not populated W009 44 errors

trip.schedule_relationship and stop_time_update.schedule_relationship should be populated

Sample errors

trip_id 1-17760352 stop_sequence 30 (and potentially more for this trip) does not have a schedule_relationship
trip_id 1-17760352 does not have a schedule_relationship
trip_id 1-17760354 stop_sequence 2 (and potentially more for this trip) does not have a schedule_relationship
trip_id 1-17760354 does not have a schedule_relationship
trip_id 1-2835415041 stop_sequence 3 (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	703	26 times (87 % of validations)
W009	trip.schedule_relationship and stop_time_update.schedule_relationship should be populated	1 406	26 times (87 % 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.	86	15 times (50 % of validations)
W008	The data in a GTFS-realtime feed should always be less than one minute old	14	14 times (47 % of validations)
E022	stop_time_update arrival/departure times between sequential stops should always increase - they should never be the same or decrease.	18	3 times (10 % of validations)
E003	All trip_ids provided in the GTFS-rt feed must exist in the GTFS data, unless the schedule_relationship is ADDED	22	1 times (3 % of validations)
E004	All route_ids provided in the GTFS-rt feed must exist in the GTFS data	10	1 times (3 % of validations)
E011	All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt	228	1 times (3 % of validations)

GTFS-RT feed content

Entities

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

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

The timestamp field appears to be too old compared to the current time: the delay is 41 548 seconds. Try to update your feed at most every 30 seconds.

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-12 at 20:32 Europe/Paris. You can look at the GTFS-RT documentation.


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