Détails de la ressource
GTFS-RT Mises à jour des trajets en temps réel
Cette ressource fait partie du jeu de données Réseau urbain Tango.
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
❌4 163 erreurs, 437 avertissements
Validation effectuée en utilisant le fichier GTFS en vigueur et le GTFS-RT, le 31/01/2025 à 08h13 Europe/Paris avec le validateur GTFS-RT de MobilityData.
Erreurs
GTFS-rt trip_id does not exist in GTFS data and does not have schedule_relationship of ADDED E003 278 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 2_58331694 does not exist in the GTFS data and does not have schedule_relationship of ADDED
- trip_id 2_58331296 does not exist in the GTFS data and does not have schedule_relationship of ADDED
- trip_id 2_58659066 does not exist in the GTFS data and does not have schedule_relationship of ADDED
- trip_id 2_58331692 does not exist in the GTFS data and does not have schedule_relationship of ADDED
- trip_id 2_58331895 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 3 730 erreurs
All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt
Exemples d'erreurs
- trip_id 2_58331694 stop_id 0:NLIBT2 does not exist in GTFS data stops.txt
- trip_id 2_58331296 stop_id 0:NPALO1 does not exist in GTFS data stops.txt
- trip_id 2_58331296 stop_id 0:MINT2A does not exist in GTFS data stops.txt
- trip_id 2_58331296 stop_id 0:JBABT2A does not exist in GTFS data stops.txt
- trip_id 2_58331296 stop_id 0:CBAT2A does not exist in GTFS data stops.txt
Sequential stop_time_update times are not increasing E022 155 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 2_58331296 stop_sequence 25 arrival_time 09:49:36 (1738313376) is less than previous stop arrival_time 09:49:41 (1738313381) - times must increase between two sequential stops
- trip_id 2_58331296 stop_sequence 25 arrival_time 09:49:36 (1738313376) is less than previous stop departure_time 09:49:41 (1738313381) - times must increase between two sequential stops
- trip_id 2_58331296 stop_sequence 25 departure_time 09:49:36 (1738313376) is less than previous stop departure_time 09:49:41 (1738313381) - times must increase between two sequential stops
- trip_id 2_58331296 stop_sequence 25 departure_time 09:49:36 (1738313376) is less than previous stop arrival_time 09:49:41 (1738313381) - times must increase between two sequential stops
- trip_id 2_58342630 stop_sequence 1 departure_time 09:00:00 (1738310400) is less than previous stop departure_time 09:03:37 (1738310617) - times must increase between two sequential stops
Avertissements
timestamp not populated W001 278 erreurs
Timestamps should be populated for all elements
Exemples d'erreurs
- trip_id 2_58331694 does not have a timestamp
- trip_id 2_58331296 does not have a timestamp
- trip_id 2_58659066 does not have a timestamp
- trip_id 2_58331692 does not have a timestamp
- trip_id 2_58331895 does not have a timestamp
vehicle_id not populated W002 159 erreurs
vehicle_id should be populated for TripUpdates and VehiclePositions
Exemples d'erreurs
- trip_id 2_58331694 does not have a vehicle_id
- trip_id 2_58331296 does not have a vehicle_id
- trip_id 2_58659066 does not have a vehicle_id
- trip_id 2_58331692 does not have a vehicle_id
- trip_id 2_58331895 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 |
|---|---|---|---|
| E003 | All trip_ids provided in the GTFS-rt feed must exist in the GTFS data, unless the schedule_relationship is ADDED | 4 600 | 20 fois (100 % des validations) |
| E011 | All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt | 59 543 | 20 fois (100 % des validations) |
| E022 | stop_time_update arrival/departure times between sequential stops should always increase - they should never be the same or decrease. | 1 566 | 20 fois (100 % des validations) |
| W001 | Timestamps should be populated for all elements | 4 606 | 20 fois (100 % des validations) |
| W002 | vehicle_id should be populated for TripUpdates and VehiclePositions | 2 678 | 20 fois (100 % 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 (5 % des validations) |
Contenu du flux GTFS-RT
Entités
Entités présentes dans ce flux le 02/02/2025 à 04h11 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 02/02/2025 à 04h11 Europe/Paris. Vous pouvez consulter la documentation GTFS-RT.
{
"header": {
"gtfs_realtime_version": "2.0",
"timestamp": "1738465916"
}
}