Détails de la ressource
Cette ressource fait partie du jeu de données Réseau urbain Mouvé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
❌3 164 erreurs, 389 avertissements
De nombreuses erreurs de validation indiquent que les identifiants du GTFS-RT ne correspondent pas aux identifiants du GTFS.
Validation effectuée en utilisant le fichier GTFS en vigueur et le GTFS-RT, le 01/04/2026 à 09h07 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 5 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 TAD_1 does not exist in the GTFS data and does not have schedule_relationship of ADDED
- trip_id TAD_3 does not exist in the GTFS data and does not have schedule_relationship of ADDED
- trip_id TAD_4 does not exist in the GTFS data and does not have schedule_relationship of ADDED
- trip_id TAD_5 does not exist in the GTFS data and does not have schedule_relationship of ADDED
- trip_id TAD_6 does not exist in the GTFS data and does not have schedule_relationship of ADDED
GTFS-rt route_id does not exist in GTFS data E004 5 erreurs
All route_ids provided in the GTFS-rt feed must exist in the GTFS data
Exemples d'erreurs
- route_id TAD_1 does not exist in the GTFS data routes.txt
- route_id TAD_3 does not exist in the GTFS data routes.txt
- route_id TAD_4 does not exist in the GTFS data routes.txt
- route_id TAD_5 does not exist in the GTFS data routes.txt
- route_id TAD_6 does not exist in the GTFS data routes.txt
GTFS-rt stop_id does not exist in GTFS data E011 2 235 erreurs
All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt
Exemples d'erreurs
- trip_id TAD_1 stop_id ASO1 does not exist in GTFS data stops.txt
- trip_id TAD_1 stop_id ASO2 does not exist in GTFS data stops.txt
- trip_id TAD_1 stop_id ASO3 does not exist in GTFS data stops.txt
- trip_id TAD_1 stop_id ASO4 does not exist in GTFS data stops.txt
- trip_id TAD_1 stop_id ASO5 does not exist in GTFS data stops.txt
Sequential stop_time_update times are not increasing E022 919 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 TAD_1 stop_sequence 17 arrival_time 08:40:37 (1775025637) is less than previous stop departure_time 08:40:44 (1775025644) - times must increase between two sequential stops
- trip_id TAD_1 stop_sequence 18 arrival_time 08:40:38 (1775025638) is less than previous stop departure_time 08:40:45 (1775025645) - times must increase between two sequential stops
- trip_id TAD_1 stop_sequence 19 arrival_time 08:40:39 (1775025639) is less than previous stop departure_time 08:40:46 (1775025646) - times must increase between two sequential stops
- trip_id TAD_1 stop_sequence 20 arrival_time 08:40:40 (1775025640) is less than previous stop departure_time 08:40:47 (1775025647) - times must increase between two sequential stops
- trip_id TAD_1 stop_sequence 21 arrival_time 08:40:41 (1775025641) is less than previous stop departure_time 08:40:48 (1775025648) - times must increase between two sequential stops
Avertissements
timestamp not populated W001 203 erreurs
Timestamps should be populated for all elements
Exemples d'erreurs
- trip_id TAD_1 does not have a timestamp
- trip_id TAD_3 does not have a timestamp
- trip_id TAD_4 does not have a timestamp
- trip_id TAD_5 does not have a timestamp
- trip_id TAD_6 does not have a timestamp
vehicle_id not populated W002 186 erreurs
vehicle_id should be populated for TripUpdates and VehiclePositions
Exemples d'erreurs
- trip_id 4_R_16:40_(geo3797) does not have a vehicle_id
- trip_id 4_R_15:10_(geo3796) does not have a vehicle_id
- trip_id 4_R_13:40_(geo3795) does not have a vehicle_id
- trip_id 4_R_12:10_(geo3794) does not have a vehicle_id
- trip_id 4_R_10:40_(geo3793) 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 | 49 | 5 fois (83 % des validations) |
| E004 | All route_ids provided in the GTFS-rt feed must exist in the GTFS data | 49 | 5 fois (83 % des validations) |
| E011 | All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt | 10 100 | 5 fois (83 % des validations) |
| E022 | stop_time_update arrival/departure times between sequential stops should always increase - they should never be the same or decrease. | 3 263 | 5 fois (83 % des validations) |
| W001 | Timestamps should be populated for all elements | 1 045 | 5 fois (83 % des validations) |
| W002 | vehicle_id should be populated for TripUpdates and VehiclePositions | 940 | 5 fois (83 % 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. | 9 | 3 fois (50 % des validations) |
Contenu du flux GTFS-RT
Entités
Entités présentes dans ce flux le 01/04/2026 à 23h12 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 01/04/2026 à 23h12 Europe/Paris. Vous pouvez consulter la documentation GTFS-RT.
{
"header": {
"gtfsRealtimeVersion": "2.0",
"timestamp": "1775077943"
}
}