Détails de la ressource
Flux GTFS-RT service Trip Update
Cette ressource fait partie du jeu de données Réseau urbain Alternéo.
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
❌100 erreurs, 233 avertissements
Validation effectuée en utilisant le fichier GTFS en vigueur et le GTFS-RT, le 03/12/2024 à 08h16 Europe/Paris avec le validateur GTFS-RT de MobilityData.
Erreurs
stop_times_updates not strictly sorted E002 4 erreurs
stop_time_updates for a given trip_id must be strictly sorted by increasing stop_sequence
Exemples d'erreurs
- trip_id 0_2869391 stop_sequence [9, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 23, 24, 25, 26, 27, 28, 29, 30, 31, 32, 33, 34, 35, 36, 37, 38, 39, 40, 41, 42, 43, 44, 45, 46, 47] is not strictly sorted by increasing stop_sequence
- trip_id 0_2869390 stop_sequence [9, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 23, 24, 25, 26, 27, 28, 29, 30, 31, 32, 33, 34, 35, 36, 37, 38, 39, 40, 41, 42, 43, 44, 45, 46, 47] is not strictly sorted by increasing stop_sequence
- trip_id 0_2869389 stop_sequence [9, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 23, 24, 25, 26, 27, 28, 29, 30, 31, 32, 33, 34, 35, 36, 37, 38, 39, 40, 41, 42, 43, 44, 45, 46, 47] is not strictly sorted by increasing stop_sequence
- trip_id 0_2869392 stop_sequence [9, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 23, 24, 25, 26, 27, 28, 29, 30, 31, 32, 33, 34, 35, 36, 37, 38, 39, 40, 41, 42, 43, 44, 45, 46, 47] is not strictly sorted by increasing stop_sequence
Sequential stop_time_update times are not increasing E022 90 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 0_2869340 stop_sequence 24 arrival_time 11:53:20 (1733212400) is less than previous stop arrival_time 11:55:00 (1733212500) - times must increase between two sequential stops
- trip_id 0_2869340 stop_sequence 24 arrival_time 11:53:20 (1733212400) is less than previous stop departure_time 11:55:00 (1733212500) - times must increase between two sequential stops
- trip_id 0_2869340 stop_sequence 24 departure_time 11:53:20 (1733212400) is less than previous stop departure_time 11:55:00 (1733212500) - times must increase between two sequential stops
- trip_id 0_2869340 stop_sequence 24 departure_time 11:53:20 (1733212400) is less than previous stop arrival_time 11:55:00 (1733212500) - times must increase between two sequential stops
- trip_id 0_2869391 stop_sequence 1 departure_time 11:30:00 (1733211000) is less than previous stop departure_time 11:43:13 (1733211793) - times must increase between two sequential stops
Sequential stop_time_updates have the same stop_id E037 6 erreurs
Sequential GTFS-rt trip stop_time_updates shouldn't have the same stop_id
Exemples d'erreurs
- trip_id 0_2869391 has repeating stop_id 0:13030C - sequential stop_ids should be different
- trip_id 0_2869390 has repeating stop_id 0:13030C - sequential stop_ids should be different
- trip_id 0_2869389 has repeating stop_id 0:13030C - sequential stop_ids should be different
- trip_id 0_2868606 has repeating stop_id 0:14150P - sequential stop_ids should be different
- trip_id 0_2868606 has repeating stop_id 0:17770P - sequential stop_ids should be different
Avertissements
timestamp not populated W001 147 erreurs
Timestamps should be populated for all elements
Exemples d'erreurs
- trip_id 0_2869501 does not have a timestamp
- trip_id 0_2869472 does not have a timestamp
- trip_id 0_2869473 does not have a timestamp
- trip_id 0_2869461 does not have a timestamp
- trip_id 0_2869465 does not have a timestamp
vehicle_id not populated W002 86 erreurs
vehicle_id should be populated for TripUpdates and VehiclePositions
Exemples d'erreurs
- trip_id 0_2869445 does not have a vehicle_id
- trip_id 0_2869453 does not have a vehicle_id
- trip_id 0_2869434 does not have a vehicle_id
- trip_id 0_2871367 does not have a vehicle_id
- trip_id 0_2871365 does not have a vehicle_id
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 |
|---|---|---|---|
| E022 | stop_time_update arrival/departure times between sequential stops should always increase - they should never be the same or decrease. | 3 019 | 30 fois (100 % des validations) |
| W001 | Timestamps should be populated for all elements | 3 505 | 30 fois (100 % des validations) |
| E037 | Sequential GTFS-rt trip stop_time_updates shouldn't have the same stop_id | 111 | 28 fois (93 % des validations) |
| W002 | vehicle_id should be populated for TripUpdates and VehiclePositions | 2 173 | 28 fois (93 % des validations) |
| E002 | stop_time_updates for a given trip_id must be strictly sorted by increasing stop_sequence | 84 | 23 fois (77 % des validations) |
| E009 | If a GTFS trip contains multiple references to the same stop_id (i.e., the vehicle visits the same stop_id more than once in the same trip), then GTFS-rt stop_time_updates for this trip must include stop_sequence | 22 | 9 fois (30 % des validations) |
| E051 | All stop_time_update stop_sequences in GTFS-realtime data must appear in GTFS stop_times.txt for that trip | 2 | 1 fois (3 % des validations) |
Contenu du flux GTFS-RT
Entités
Entités présentes dans ce flux le 03/12/2024 à 18h35 Europe/Paris.
service_alerts (0) trip_updates (0) vehicle_positions (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 03/12/2024 à 18h35 Europe/Paris. Vous pouvez consulter la documentation GTFS-RT.
{
"header": {
"gtfs_realtime_version": "2.0",
"timestamp": "1733247306"
}
}