Détails de la ressource
Ce lien fournit les mises à jour en temps réel par rapport au référentiel gtfs-navineo.zip
Cette ressource fait partie du jeu de données Réseau urbain TCAT.
Ressources associées
gtfs-navineo.zip
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
❌38 erreurs, 30 avertissements
Validation effectuée en utilisant le fichier GTFS en vigueur et le GTFS-RT, le 27/07/2025 à 09h08 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 DFC1965979 stop_sequence [23, 1] is not strictly sorted by increasing stop_sequence
GTFS-rt stop_sequence isn't provided for trip that visits same stop_id more than once E009 2 erreurs
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
Exemples d'erreurs
- trip_id DFC1962730 visits stop_id [0:GAR01] more than once and GTFS-rt stop_time_update is missing stop_sequence field - stop_sequence must be provided
- trip_id DFC1962731 visits stop_id [0:GAR01] more than once and GTFS-rt stop_time_update is missing stop_sequence field - stop_sequence must be provided
Sequential stop_time_update times are not increasing E022 33 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 DFC1962730 stop_sequence 1 departure_time 09:30:00 (1753601400) is less than previous stop departure_time 09:44:47 (1753602287) - times must increase between two sequential stops
- trip_id DFC1962730 stop_sequence 1 departure_time 09:30:00 (1753601400) is less than previous stop arrival_time 09:44:47 (1753602287) - times must increase between two sequential stops
- trip_id DFC1962730 stop_sequence 2 arrival_time 09:31:25 (1753601485) is less than previous stop arrival_time 09:44:47 (1753602287) - times must increase between two sequential stops
- trip_id DFC1962730 stop_sequence 2 departure_time 09:31:25 (1753601485) is less than previous stop arrival_time 09:44:47 (1753602287) - times must increase between two sequential stops
- trip_id DFC1962731 stop_sequence 1 departure_time 09:57:00 (1753603020) is less than previous stop departure_time 10:11:47 (1753603907) - 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 DFC1966075 has repeating stop_id 0:CAm01 - sequential stop_ids should be different
GTFS-rt stop_sequence not found in GTFS data E051 1 erreur
All stop_time_update stop_sequences in GTFS-realtime data must appear in GTFS stop_times.txt for that trip
Exemples d'erreurs
- GTFS-rt trip_id DFC1965979 contains stop_sequence 1 that does not exist in GTFS stop_times.txt for this trip
Avertissements
timestamp not populated W001 15 erreurs
Timestamps should be populated for all elements
Exemples d'erreurs
- trip_id DFC1962730 does not have a timestamp
- trip_id DFC1962731 does not have a timestamp
- trip_id DFC1966136 does not have a timestamp
- trip_id DFC1965979 does not have a timestamp
- trip_id DFC1965980 does not have a timestamp
vehicle_id not populated W002 15 erreurs
vehicle_id should be populated for TripUpdates and VehiclePositions
Exemples d'erreurs
- trip_id DFC1962730 does not have a vehicle_id
- trip_id DFC1962731 does not have a vehicle_id
- trip_id DFC1966136 does not have a vehicle_id
- trip_id DFC1965979 does not have a vehicle_id
- trip_id DFC1965980 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. | 5 692 | 34 fois (100 % des validations) |
| E037 | Sequential GTFS-rt trip stop_time_updates shouldn't have the same stop_id | 85 | 34 fois (100 % des validations) |
| W001 | Timestamps should be populated for all elements | 2 599 | 34 fois (100 % des validations) |
| W002 | vehicle_id should be populated for TripUpdates and VehiclePositions | 1 621 | 34 fois (100 % des validations) |
| E002 | stop_time_updates for a given trip_id must be strictly sorted by increasing stop_sequence | 192 | 30 fois (88 % des validations) |
| E051 | All stop_time_update stop_sequences in GTFS-realtime data must appear in GTFS stop_times.txt for that trip | 170 | 30 fois (88 % 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 | 110 | 13 fois (38 % des validations) |
| E003 | All trip_ids provided in the GTFS-rt feed must exist in the GTFS data, unless the schedule_relationship is ADDED | 96 | 1 fois (3 % des validations) |
| E004 | All route_ids provided in the GTFS-rt feed must exist in the GTFS data | 75 | 1 fois (3 % des validations) |
| E011 | All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt | 2 183 | 1 fois (3 % des 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. | 1 | 1 fois (3 % des validations) |
Contenu du flux GTFS-RT
Entités
Entités présentes dans ce flux le 28/07/2025 à 03h40 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 28/07/2025 à 03h40 Europe/Paris. Vous pouvez consulter la documentation GTFS-RT.
{
"header": {
"gtfsRealtimeVersion": "2.0",
"timestamp": "1753666828"
}
}