Resource details

Format: gtfs-rt

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

Download availability

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

Validation details

7 errors, 56 warnings

Validation carried out using the current GTFS file and the GTFS-RT the 2024-06-02 at 09:09 Europe/Paris using the MobilityData GTFS-RT validator.

Errors

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

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

Sample errors
  • trip_id OCESN4091F stop_id StopArea:OCE87478404 does not exist in GTFS data stops.txt
  • trip_id OCESN4091F stop_id StopArea:OCE87471003 does not exist in GTFS data stops.txt

All stop_ids referenced in GTFS-rt TripUpdates and VehiclePositions feeds must have the location_type = 0 E015 5 errors

All stop_ids referenced in GTFS-rt TripUpdates and VehiclePositions feeds must have the location_type = 0 in GTFS stops.txt

Sample errors
  • trip_id OCESN4091F stop_id StopArea:OCE87547000 does not have location_type=0 in GTFS stops.txt
  • trip_id OCESN4091F stop_id StopArea:OCE87393579 does not have location_type=0 in GTFS stops.txt
  • trip_id OCESN4091F stop_id StopArea:OCE87393009 does not have location_type=0 in GTFS stops.txt
  • trip_id OCESN4091F stop_id StopArea:OCE87394007 does not have location_type=0 in GTFS stops.txt
  • trip_id OCESN4091F stop_id StopArea:OCE87396002 does not have location_type=0 in GTFS stops.txt

Warnings

vehicle_id not populated W002 19 errors

vehicle_id should be populated for TripUpdates and VehiclePositions

Sample errors
  • trip_id OCESN3614F3167734:2024-05-24T00:27:00Z does not have a vehicle_id
  • trip_id OCESN4655F3064168:2024-06-02T00:25:55Z does not have a vehicle_id
  • trip_id OCESN4402F3236921:2024-06-02T00:25:55Z does not have a vehicle_id
  • trip_id OCESN14140F3206469:2024-06-02T00:25:55Z does not have a vehicle_id
  • trip_id OCESN4080F3032888:2024-05-10T00:31:12Z does not have a vehicle_id

schedule_relationship not populated W009 37 errors

trip.schedule_relationship and stop_time_update.schedule_relationship should be populated

Sample errors
  • trip_id OCESN3614F3167734:2024-05-24T00:27:00Z stop_id StopPoint:OCEINTERCITES-87594002 (and potentially more for this trip) does not have a schedule_relationship
  • trip_id OCESN3614F3167734:2024-05-24T00:27:00Z does not have a schedule_relationship
  • trip_id OCESN4655F3064168:2024-06-02T00:25:55Z stop_id StopPoint:OCEINTERCITES-87581009 (and potentially more for this trip) does not have a schedule_relationship
  • trip_id OCESN4655F3064168:2024-06-02T00:25:55Z does not have a schedule_relationship
  • trip_id OCESN4402F3236921:2024-06-02T00:25:55Z stop_id StopPoint:OCEINTERCITES-87481002 (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
E015 All stop_ids referenced in GTFS-rt TripUpdates and VehiclePositions feeds must have the location_type = 0 in GTFS stops.txt 220 29 times (100 % of validations)
W002 vehicle_id should be populated for TripUpdates and VehiclePositions 663 29 times (100 % of validations)
W009 trip.schedule_relationship and stop_time_update.schedule_relationship should be populated 1 275 29 times (100 % of validations)
E011 All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt 58 27 times (93 % of validations)
W008 The data in a GTFS-realtime feed should always be less than one minute old 11 11 times (38 % of validations)
E003 All trip_ids provided in the GTFS-rt feed must exist in the GTFS data, unless the schedule_relationship is ADDED 17 2 times (7 % of validations)
E022 stop_time_update arrival/departure times between sequential stops should always increase - they should never be the same or decrease. 2 1 times (3 % of validations)

GTFS-RT feed content

Entities

Entities present in this feed at 2024-06-03 at 02:52 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-06-03 at 02:52 Europe/Paris. You can look at the GTFS-RT documentation.

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