Détails de la ressource
horaires en temps réel format GTFS RT Trip Updates
Cette ressource fait partie du jeu de données Réseau SNCF TGV, Intercités et TER.
Disponibilité au téléchargement
En savoir plus
HEAD dont le temps de réponse doit être inférieur à 5 secondes. Si nous détectons une indisponibilité, nous effectuons un nouveau test toutes les 10 minutes, jusqu'à ce que la ressource soit à nouveau disponible.Pour les flux SIRI et SIRI Lite, nous effectuons une requête HTTP de type
GET : nous considérons une réponse avec un code 401 ou 405 comme étant disponible. En cas d'erreur 500, nous considèrerons que le flux est indisponible, sauf si il semble contenir du SOAP.Rapport de validation
❌761 erreurs, 5 240 avertissements
Validation effectuée en utilisant le fichier GTFS en vigueur et le GTFS-RT, le 28/10/2025 à 08h12 Europe/Paris avec le validateur GTFS-RT de MobilityData.
Erreurs
stop_times_updates not strictly sorted E002 1 erreur
stop_time_updates for a given trip_id must be strictly sorted by increasing stop_sequence
Exemples d'erreurs
- trip_id OCESN859407F6317734:2025-10-26T00:33:16Z stop_sequence for stop_ids [StopPoint:OCETrain TER-87744177, StopArea:OCE87481192, StopPoint:OCETrain TER-87481184, StopPoint:OCETrain TER-87481168, StopPoint:OCETrain TER-87481150, StopPoint:OCETrain TER-87481143, StopPoint:OCETrain TER-87481002] is not strictly sorted by increasing stop_sequence
GTFS-rt trip_id does not exist in GTFS data and does not have schedule_relationship of ADDED E003 51 erreurs
All trip_ids provided in the GTFS-rt feed must exist in the GTFS data, unless the schedule_relationship is ADDED
Exemples d'erreurs
- trip_id OCESN57812R6340729:2025-10-28T00:27:10Z does not exist in the GTFS data and does not have schedule_relationship of ADDED
- trip_id OCESN59746R6340518:2025-10-28T00:27:10Z does not exist in the GTFS data and does not have schedule_relationship of ADDED
- trip_id OCESN89046R6316086:2025-10-26T00:33:16Z does not exist in the GTFS data and does not have schedule_relationship of ADDED
- trip_id OCESN97006R6324942:2025-10-27T00:10:27Z does not exist in the GTFS data and does not have schedule_relationship of ADDED
- trip_id OCESN89043R6325887:2025-10-27T00:10:27Z does not exist in the GTFS data and does not have schedule_relationship of ADDED
GTFS-rt stop_id does not exist in GTFS data E011 383 erreurs
All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt
Exemples d'erreurs
- trip_id OCESN57812R6340729:2025-10-28T00:27:10Z stop_id StopPoint:OCECar-87201541 does not exist in GTFS data stops.txt
- trip_id OCESN57812R6340729:2025-10-28T00:27:10Z stop_id StopPoint:OCECar-87690156 does not exist in GTFS data stops.txt
- trip_id OCESN57812R6340729:2025-10-28T00:27:10Z stop_id StopPoint:OCECar-87689950 does not exist in GTFS data stops.txt
- trip_id OCESN57812R6340729:2025-10-28T00:27:10Z stop_id StopPoint:OCECar-87216663 does not exist in GTFS data stops.txt
- trip_id OCESN57812R6340729:2025-10-28T00:27:10Z stop_id StopPoint:OCECar-87644351 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 319 erreurs
All stop_ids referenced in GTFS-rt TripUpdates and VehiclePositions feeds must have the location_type = 0 in GTFS stops.txt
Exemples d'erreurs
- trip_id OCESN150010F stop_id StopArea:OCE87545244 does not have location_type=0 in GTFS stops.txt
- trip_id OCESN150010F stop_id StopArea:OCE87686006 does not have location_type=0 in GTFS stops.txt
- trip_id OCESN155810F stop_id StopArea:OCE87276279 does not have location_type=0 in GTFS stops.txt
- trip_id OCESN155810F stop_id StopArea:OCE87545244 does not have location_type=0 in GTFS stops.txt
- trip_id OCESN155812F stop_id StopArea:OCE87276279 does not have location_type=0 in GTFS stops.txt
Sequential stop_time_update times are not increasing E022 6 erreurs
stop_time_update arrival/departure times between sequential stops should always increase - they should never be the same or decrease.
Exemples d'erreurs
- trip_id OCESN876404F6345549:2025-10-28T00:27:10Z stop_id StopPoint:OCETrain TER-87767871 arrival_time 08:35:00 (1761636900) is less than previous stop arrival_time 08:36:00 (1761636960) - times must increase between two sequential stops
- trip_id OCESN876404F6345549:2025-10-28T00:27:10Z stop_id StopPoint:OCETrain TER-87767871 arrival_time 08:35:00 (1761636900) is less than previous stop departure_time 08:37:00 (1761637020) - times must increase between two sequential stops
- trip_id OCESN876404F6345549:2025-10-28T00:27:10Z stop_id StopPoint:OCETrain TER-87767871 departure_time 08:36:00 (1761636960) is less than previous stop departure_time 08:37:00 (1761637020) - times must increase between two sequential stops
- trip_id OCESN876404F6345549:2025-10-28T00:27:10Z stop_id StopPoint:OCETrain TER-87767871 departure_time 08:36:00 (1761636960) is equal to previous stop arrival_time 08:36:00 (1761636960) - times must increase between two sequential stops
- trip_id OCESN142264F stop_id StopArea:OCE87545244 departure_time 07:10:00 (1761631800) is equal to previous stop departure_time 07:10:00 (1761631800) - times must increase between two sequential stops
Sequential stop_time_updates have the same stop_id E037 1 erreur
Sequential GTFS-rt trip stop_time_updates shouldn't have the same stop_id
Exemples d'erreurs
- trip_id OCESN142264F has repeating stop_id StopArea:OCE87545244 - sequential stop_ids should be different
Avertissements
vehicle_id not populated W002 1 782 erreurs
vehicle_id should be populated for TripUpdates and VehiclePositions
Exemples d'erreurs
- trip_id OCESN3604F6321789:2025-10-26T00:33:16Z does not have a vehicle_id
- trip_id OCESN3624F6320805:2025-10-26T00:33:16Z does not have a vehicle_id
- trip_id OCESN5300F6319441:2025-10-26T00:33:16Z does not have a vehicle_id
- trip_id OCESN3614F6321791:2025-10-26T00:33:16Z does not have a vehicle_id
- trip_id OCESN8860F6314931:2025-10-26T00:33:16Z does not have a vehicle_id
schedule_relationship not populated W009 3 458 erreurs
trip.schedule_relationship and stop_time_update.schedule_relationship should be populated
Exemples d'erreurs
- trip_id OCESN3604F6321789:2025-10-26T00:33:16Z stop_id StopPoint:OCEINTERCITES-87594002 (and potentially more for this trip) does not have a schedule_relationship
- trip_id OCESN3604F6321789:2025-10-26T00:33:16Z does not have a schedule_relationship
- trip_id OCESN3624F6320805:2025-10-26T00:33:16Z stop_id StopPoint:OCEINTERCITES-87613000 (and potentially more for this trip) does not have a schedule_relationship
- trip_id OCESN3624F6320805:2025-10-26T00:33:16Z does not have a schedule_relationship
- trip_id OCESN5300F6319441:2025-10-26T00:33:16Z stop_id StopPoint:OCETGV INOUI-87481002 (and potentially more for this trip) does not have a schedule_relationship
Validations précédentes
Voici un récapitulatif des différents types d'erreurs constatés au cours des 30 derniers jours.
| Identifiant d'erreur | Description | Nombre d'erreurs | Nombre d'occurences |
|---|---|---|---|
| E003 | All trip_ids provided in the GTFS-rt feed must exist in the GTFS data, unless the schedule_relationship is ADDED | 1 636 | 21 fois (72 % des validations) |
| E011 | All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt | 6 370 | 21 fois (72 % des validations) |
| E015 | All stop_ids referenced in GTFS-rt TripUpdates and VehiclePositions feeds must have the location_type = 0 in GTFS stops.txt | 6 215 | 21 fois (72 % des validations) |
| E022 | stop_time_update arrival/departure times between sequential stops should always increase - they should never be the same or decrease. | 163 | 21 fois (72 % des validations) |
| W002 | vehicle_id should be populated for TripUpdates and VehiclePositions | 26 808 | 21 fois (72 % des validations) |
| W009 | trip.schedule_relationship and stop_time_update.schedule_relationship should be populated | 50 576 | 21 fois (72 % des validations) |
| E002 | stop_time_updates for a given trip_id must be strictly sorted by increasing stop_sequence | 66 | 20 fois (69 % des validations) |
| E037 | Sequential GTFS-rt trip stop_time_updates shouldn't have the same stop_id | 139 | 15 fois (52 % des validations) |
| E023 | For normal scheduled trips (i.e., not defined in frequencies.txt), the GTFS-realtime trip start_time must match the first GTFS arrival_time in stop_times.txt for this trip | 53 | 12 fois (41 % des validations) |
| W008 | The data in a GTFS-realtime feed should always be less than one minute old | 7 | 7 fois (24 % des validations) |
Contenu du flux GTFS-RT
Entités
Entités présentes dans ce flux le 29/10/2025 à 05h30 Europe/Paris.
vehicle_positions (0) service_alerts (0) trip_updates (0)Entités présentes dans ce flux lors des 7 derniers jours.
trip_updatesFlux GTFS-RT décodé
Voir le contenu du flux
Voici le flux GTFS-RT décodé au format Protobuf le 29/10/2025 à 05h30 Europe/Paris. Vous pouvez consulter la documentation GTFS-RT.
{
"header": {
"gtfsRealtimeVersion": "1.0",
"timestamp": "1761712226"
}
}