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
❌160 erreurs, 36 avertissements
Validation effectuée en utilisant le fichier GTFS en vigueur et le GTFS-RT, le 30/07/2026 à 09h10 Europe/Paris avec le validateur GTFS-RT de MobilityData.
Erreurs
GTFS-rt stop_id does not exist in GTFS data E011 15 erreurs
All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt
Exemples d'erreurs
- trip_id 21814425 stop_id bsmsgen does not exist in GTFS data stops.txt
- trip_id 21814426 stop_id bsmsgen does not exist in GTFS data stops.txt
- trip_id 21814181 stop_id bsmsgen does not exist in GTFS data stops.txt
- trip_id 21814183 stop_id bsmsgen does not exist in GTFS data stops.txt
- trip_id 21814176 stop_id bsmsgen does not exist in GTFS data stops.txt
stop_times_updates not strictly sorted E002 6 erreurs
stop_time_updates for a given trip_id must be strictly sorted by increasing stop_sequence
Exemples d'erreurs
- trip_id 21814299 stop_sequence [3, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17] is not strictly sorted by increasing stop_sequence
- trip_id 21814327 stop_sequence [3, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17] is not strictly sorted by increasing stop_sequence
- trip_id 21814089 stop_sequence [8, 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 21814090 stop_sequence [8, 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 21814120 stop_sequence [1, 1] is not strictly sorted by increasing stop_sequence
Sequential stop_time_update times are not increasing E022 134 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 21814425 stop_sequence 1 departure_time 08:49:31 (1785394171) is less than previous stop departure_time 09:18:49 (1785395929) - times must increase between two sequential stops
- trip_id 21814425 stop_sequence 1 departure_time 08:49:31 (1785394171) is less than previous stop arrival_time 09:18:49 (1785395929) - times must increase between two sequential stops
- trip_id 21814425 stop_sequence 2 arrival_time 08:50:31 (1785394231) is less than previous stop arrival_time 09:18:49 (1785395929) - times must increase between two sequential stops
- trip_id 21814425 stop_sequence 2 departure_time 08:50:31 (1785394231) is less than previous stop arrival_time 09:18:49 (1785395929) - times must increase between two sequential stops
- trip_id 21814426 stop_sequence 1 departure_time 09:42:00 (1785397320) is less than previous stop departure_time 10:11:40 (1785399100) - times must increase between two sequential stops
Sequential stop_time_updates have the same stop_id E037 3 erreurs
Sequential GTFS-rt trip stop_time_updates shouldn't have the same stop_id
Exemples d'erreurs
- trip_id 21814486 has repeating stop_id outlep2 - sequential stop_ids should be different
- trip_id 21814120 has repeating stop_id smbwica at stop_sequence 1 - sequential stop_ids should be different
- trip_id 21814121 has repeating stop_id smbwica at stop_sequence 1 - sequential stop_ids should be different
GTFS-rt stop_sequence not found in GTFS data E051 2 erreurs
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 21814120 contains stop_sequence 1 that does not exist in GTFS stop_times.txt for this trip
- GTFS-rt trip_id 21814121 contains stop_sequence 1 that does not exist in GTFS stop_times.txt for this trip
Avertissements
vehicle_id not populated W002 36 erreurs
vehicle_id should be populated for TripUpdates and VehiclePositions
Exemples d'erreurs
- trip_id 21814590 does not have a vehicle_id
- trip_id 21814591 does not have a vehicle_id
- trip_id 21814155 does not have a vehicle_id
- trip_id 21814147 does not have a vehicle_id
- trip_id 21814409 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 | 505 | 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 895 | 30 fois (100 % des validations) |
| W002 | vehicle_id should be populated for TripUpdates and VehiclePositions | 950 | 30 fois (100 % des validations) |
| E002 | stop_time_updates for a given trip_id must be strictly sorted by increasing stop_sequence | 103 | 28 fois (93 % des validations) |
| E037 | Sequential GTFS-rt trip stop_time_updates shouldn't have the same stop_id | 57 | 22 fois (73 % 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 | 30 | 11 fois (37 % des validations) |
| E051 | All stop_time_update stop_sequences in GTFS-realtime data must appear in GTFS stop_times.txt for that trip | 39 | 10 fois (33 % 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 | 122 | 5 fois (17 % 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 (7 % des validations) |
Contenu du flux GTFS-RT
Entités
Entités présentes dans ce flux le 30/07/2026 à 23h37 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 30/07/2026 à 23h37 Europe/Paris. Vous pouvez consulter la documentation GTFS-RT.
{
"header": {
"gtfsRealtimeVersion": "2.0",
"timestamp": "1785447421"
}
}