Resource details

File name: GTFS-RT Trip Updates
Format: gtfs-rt

This resource file is part of the dataset Réseau national Lignes Intercités SNCF.

Download availability

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

⚠️42 warnings

Validation carried out using the current GTFS file and the GTFS-RT the 2024-11-22 at 08:14 Europe/Paris using the MobilityData GTFS-RT validator.

Warnings

vehicle_id not populated W002 18 errors

vehicle_id should be populated for TripUpdates and VehiclePositions

Sample errors
  • trip_id OCESN3604F3656535:2024-11-15T00:27:05Z does not have a vehicle_id
  • trip_id OCESN3614F3655022:2024-11-18T16:25:31Z does not have a vehicle_id
  • trip_id OCESN5950F3132774:2024-11-22T00:29:45Z does not have a vehicle_id
  • trip_id OCESN5954F3650436:2024-11-22T00:29:45Z does not have a vehicle_id
  • trip_id OCESN4655F3672628:2024-11-22T00:29:45Z does not have a vehicle_id

schedule_relationship not populated W009 24 errors

trip.schedule_relationship and stop_time_update.schedule_relationship should be populated

Sample errors
  • trip_id OCESN5950F3132774:2024-11-22T00:29:45Z stop_id StopPoint:OCEINTERCITES-87734004 (and potentially more for this trip) does not have a schedule_relationship
  • trip_id OCESN5950F3132774:2024-11-22T00:29:45Z does not have a schedule_relationship
  • trip_id OCESN5954F3650436:2024-11-22T00:29:45Z stop_id StopPoint:OCEINTERCITES-87734004 (and potentially more for this trip) does not have a schedule_relationship
  • trip_id OCESN5954F3650436:2024-11-22T00:29:45Z does not have a schedule_relationship
  • trip_id OCESN4655F3672628:2024-11-22T00:29:45Z stop_id StopPoint:OCEINTERCITES-87581009 (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 631 27 times (96 % of validations)
W009 trip.schedule_relationship and stop_time_update.schedule_relationship should be populated 1 224 27 times (96 % of validations)
W008 The data in a GTFS-realtime feed should always be less than one minute old 9 9 times (32 % of validations)
E015 All stop_ids referenced in GTFS-rt TripUpdates and VehiclePositions feeds must have the location_type = 0 in GTFS stops.txt 64 7 times (25 % of validations)
E002 stop_time_updates for a given trip_id must be strictly sorted by increasing stop_sequence 2 2 times (7 % of validations)

GTFS-RT feed content

Entities

Entities present in this feed at 2024-11-23 at 02:53 Europe/Paris.

service_alerts (0) trip_updates (0) vehicle_positions (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 2024-11-23 at 02:53 Europe/Paris. You can look at the GTFS-RT documentation.

{ "header": { "gtfs_realtime_version": "1.0", "timestamp": "1732326819" } }