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
❌206 erreurs, 42 avertissements
Validation effectuée en utilisant le fichier GTFS en vigueur et le GTFS-RT, le 09/02/2026 à 08h13 Europe/Paris avec le validateur GTFS-RT de MobilityData.
Erreurs
stop_times_updates not strictly sorted E002 9 erreurs
stop_time_updates for a given trip_id must be strictly sorted by increasing stop_sequence
Exemples d'erreurs
- trip_id 21725823 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
- trip_id 21323514 stop_sequence [22, 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] is not strictly sorted by increasing stop_sequence
- trip_id 21323512 stop_sequence [22, 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] is not strictly sorted by increasing stop_sequence
- trip_id 21323513 stop_sequence [22, 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] is not strictly sorted by increasing stop_sequence
- trip_id 21323616 stop_sequence [13, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22] is not strictly sorted by increasing stop_sequence
GTFS-rt trip_id does not exist in GTFS data and does not have schedule_relationship of ADDED E003 1 erreur
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 21323855 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 1 erreur
All route_ids provided in the GTFS-rt feed must exist in the GTFS data
Exemples d'erreurs
- route_id SC does not exist in the GTFS data routes.txt
GTFS-rt stop_id does not exist in GTFS data E011 27 erreurs
All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt
Exemples d'erreurs
- trip_id 21323855 stop_id smbsand does not exist in GTFS data stops.txt
- trip_id 21323514 stop_id bsmtran2 does not exist in GTFS data stops.txt
- trip_id 21323512 stop_id bsmtran2 does not exist in GTFS data stops.txt
- trip_id 21323513 stop_id bsmtran2 does not exist in GTFS data stops.txt
- trip_id 21323496 stop_id bsmtran2 does not exist in GTFS data stops.txt
Sequential stop_time_update times are not increasing E022 159 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 21725823 stop_id outlep2 arrival_time 08:08:11 (1770620891) is equal to previous stop arrival_time 08:08:11 (1770620891) - times must increase between two sequential stops
- trip_id 21725823 stop_id outlep2 arrival_time 08:08:11 (1770620891) is less than previous stop departure_time 08:10:18 (1770621018) - times must increase between two sequential stops
- trip_id 21725823 stop_id outlep2 departure_time 08:10:18 (1770621018) is equal to previous stop departure_time 08:10:18 (1770621018) - times must increase between two sequential stops
- trip_id 21725823 stop_sequence 1 departure_time 07:58:31 (1770620311) is less than previous stop departure_time 08:10:59 (1770621059) - times must increase between two sequential stops
- trip_id 21725823 stop_sequence 1 departure_time 07:58:31 (1770620311) is less than previous stop arrival_time 08:10:59 (1770621059) - times must increase between two sequential stops
GTFS-rt stop_time_update stop_sequence and stop_id do not match GTFS E045 9 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 21725990 stop_sequence 25 has stop_id wimmair4 but GTFS stop_sequence 25 has stop_id wimmair2 - stop_ids should be the same
- GTFS-rt trip_id 21725979 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 21725957 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 21725967 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 21323583 stop_sequence 11 has stop_id smbheli but GTFS stop_sequence 11 has stop_id smbheli2 - stop_ids should be the same
Avertissements
vehicle_id not populated W002 42 erreurs
vehicle_id should be populated for TripUpdates and VehiclePositions
Exemples d'erreurs
- trip_id 21323842 does not have a vehicle_id
- trip_id 21323418 does not have a vehicle_id
- trip_id 21323514 does not have a vehicle_id
- trip_id 21323513 does not have a vehicle_id
- trip_id 21725788 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 | 289 | 24 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 414 | 24 fois (100 % des validations) |
| W002 | vehicle_id should be populated for TripUpdates and VehiclePositions | 843 | 24 fois (100 % des validations) |
| E002 | stop_time_updates for a given trip_id must be strictly sorted by increasing stop_sequence | 122 | 20 fois (83 % des validations) |
| E037 | Sequential GTFS-rt trip stop_time_updates shouldn't have the same stop_id | 35 | 15 fois (63 % des validations) |
| E003 | All trip_ids provided in the GTFS-rt feed must exist in the GTFS data, unless the schedule_relationship is ADDED | 13 | 13 fois (54 % des validations) |
| E004 | All route_ids provided in the GTFS-rt feed must exist in the GTFS data | 13 | 13 fois (54 % des validations) |
| E051 | All stop_time_update stop_sequences in GTFS-realtime data must appear in GTFS stop_times.txt for that trip | 18 | 11 fois (46 % 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 | 73 | 9 fois (38 % 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 | 2 | 2 fois (8 % 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. | 2 | 2 fois (8 % des validations) |
Contenu du flux GTFS-RT
Entités
Entités présentes dans ce flux le 10/02/2026 à 03h36 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 10/02/2026 à 03h36 Europe/Paris. Vous pouvez consulter la documentation GTFS-RT.
{
"header": {
"gtfsRealtimeVersion": "2.0",
"timestamp": "1770690984"
}
}