Détails de la ressource
Cette ressource fait partie du jeu de données Réseau urbain Mariné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
❌48 erreurs, 38 avertissements
Validation effectuée en utilisant le fichier GTFS en vigueur et le GTFS-RT, le 07/03/2026 à 08h09 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 21327510 stop_sequence [7, 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] is not strictly sorted by increasing stop_sequence
GTFS-rt stop_id does not exist in GTFS data E011 8 erreurs
All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt
Exemples d'erreurs
- trip_id 21327511 stop_id outmds does not exist in GTFS data stops.txt
- trip_id 21327509 stop_id outmds does not exist in GTFS data stops.txt
- trip_id 21327672 stop_id wimmair3 does not exist in GTFS data stops.txt
- trip_id 21327656 stop_id wimmair4 does not exist in GTFS data stops.txt
- trip_id 21327695 stop_id wimmair3 does not exist in GTFS data stops.txt
Sequential stop_time_update times are not increasing E022 28 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 21327510 stop_id outlep2 arrival_time 08:43:33 (1772869413) is equal to previous stop arrival_time 08:43:33 (1772869413) - times must increase between two sequential stops
- trip_id 21327510 stop_id outlep2 arrival_time 08:43:33 (1772869413) is equal to previous stop departure_time 08:43:33 (1772869413) - times must increase between two sequential stops
- trip_id 21327510 stop_id outlep2 departure_time 08:43:33 (1772869413) is equal to previous stop departure_time 08:43:33 (1772869413) - times must increase between two sequential stops
- trip_id 21327510 stop_id outlep2 departure_time 08:43:33 (1772869413) is equal to previous stop arrival_time 08:43:33 (1772869413) - times must increase between two sequential stops
- trip_id 21327510 stop_sequence 1 departure_time 08:35:00 (1772868900) is less than previous stop departure_time 08:44:04 (1772869444) - times must increase between two sequential stops
GTFS-rt stop_time_update stop_sequence and stop_id do not match GTFS E045 11 erreurs
If GTFS-rt stop_time_update contains both stop_sequence and stop_id, the values must match the GTFS data in stop_times.txt
Exemples d'erreurs
- GTFS-rt trip_id 21327225 stop_sequence 33 has stop_id semcord but GTFS stop_sequence 33 has stop_id semcord2 - stop_ids should be the same
- GTFS-rt trip_id 21327672 stop_sequence 1 has stop_id wimmair3 but GTFS stop_sequence 1 has stop_id wimmair - stop_ids should be the same
- GTFS-rt trip_id 21327656 stop_sequence 43 has stop_id wimmair4 but GTFS stop_sequence 43 has stop_id wimmair2 - stop_ids should be the same
- GTFS-rt trip_id 21327739 stop_sequence 4 has stop_id smbecol but GTFS stop_sequence 4 has stop_id smbecol3 - stop_ids should be the same
- GTFS-rt trip_id 21327740 stop_sequence 6 has stop_id smbecol but GTFS stop_sequence 6 has stop_id smbecol3 - stop_ids should be the same
Avertissements
vehicle_id not populated W002 38 erreurs
vehicle_id should be populated for TripUpdates and VehiclePositions
Exemples d'erreurs
- trip_id 21327283 does not have a vehicle_id
- trip_id 21327284 does not have a vehicle_id
- trip_id 21327269 does not have a vehicle_id
- trip_id 21327260 does not have a vehicle_id
- trip_id 21327242 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 |
|---|---|---|---|
| E011 | All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt | 455 | 30 fois (100 % des validations) |
| E045 | If GTFS-rt stop_time_update contains both stop_sequence and stop_id, the values must match the GTFS data in stop_times.txt | 345 | 30 fois (100 % des validations) |
| W002 | vehicle_id should be populated for TripUpdates and VehiclePositions | 1 057 | 30 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. | 2 467 | 28 fois (93 % des validations) |
| E002 | stop_time_updates for a given trip_id must be strictly sorted by increasing stop_sequence | 136 | 26 fois (87 % des validations) |
| E003 | All trip_ids provided in the GTFS-rt feed must exist in the GTFS data, unless the schedule_relationship is ADDED | 9 | 9 fois (30 % des validations) |
| E004 | All route_ids provided in the GTFS-rt feed must exist in the GTFS data | 9 | 9 fois (30 % 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 | 1 | 1 fois (3 % des validations) |
Contenu du flux GTFS-RT
Entités
Entités présentes dans ce flux le 07/03/2026 à 22h22 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 07/03/2026 à 22h22 Europe/Paris. Vous pouvez consulter la documentation GTFS-RT.
{
"header": {
"gtfsRealtimeVersion": "2.0",
"timestamp": "1772918525"
}
}