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
❌146 erreurs, 34 avertissements
Validation effectuée en utilisant le fichier GTFS en vigueur et le GTFS-RT, le 20/09/2025 à 09h08 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 21323895 stop_sequence [11, 1] is not strictly sorted by increasing stop_sequence
- trip_id 21323896 stop_sequence [11, 1] is not strictly sorted by increasing stop_sequence
- trip_id 21327359 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
- trip_id 21327361 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
- trip_id 21327360 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 stop_sequence isn't provided for trip that visits same stop_id more than once E009 2 erreurs
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
Exemples d'erreurs
- trip_id 21323895 visits stop_id [bsmdal1] more than once and GTFS-rt stop_time_update is missing stop_sequence field - stop_sequence must be provided
- trip_id 21323896 visits stop_id [bsmdal1] more than once and GTFS-rt stop_time_update is missing stop_sequence field - stop_sequence must be provided
GTFS-rt stop_id does not exist in GTFS data E011 12 erreurs
All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt
Exemples d'erreurs
- trip_id 21327513 stop_id outmds does not exist in GTFS data stops.txt
- trip_id 21327338 stop_id bsmtran2 does not exist in GTFS data stops.txt
- trip_id 21327359 stop_id bsmtran2 does not exist in GTFS data stops.txt
- trip_id 21327361 stop_id bsmtran2 does not exist in GTFS data stops.txt
- trip_id 21327360 stop_id bsmtran2 does not exist in GTFS data stops.txt
Sequential stop_time_update times are not increasing E022 118 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 21327513 stop_sequence 1 departure_time 09:45:00 (1758354300) is less than previous stop departure_time 10:01:09 (1758355269) - times must increase between two sequential stops
- trip_id 21327513 stop_sequence 1 departure_time 09:45:00 (1758354300) is less than previous stop arrival_time 10:01:09 (1758355269) - times must increase between two sequential stops
- trip_id 21327513 stop_sequence 2 arrival_time 09:46:35 (1758354395) is less than previous stop arrival_time 10:01:09 (1758355269) - times must increase between two sequential stops
- trip_id 21327513 stop_sequence 2 departure_time 09:46:35 (1758354395) is less than previous stop arrival_time 10:01:09 (1758355269) - times must increase between two sequential stops
- trip_id 21327513 stop_sequence 16 arrival_time 10:01:48 (1758355308) is less than previous stop arrival_time 10:03:11 (1758355391) - times must increase between two sequential stops
GTFS-rt stop_time_update stop_sequence and stop_id do not match GTFS E045 2 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 21327695 stop_sequence 16 has stop_id wimcrec but GTFS stop_sequence 16 has stop_id wimcrec2 - stop_ids should be the same
- GTFS-rt trip_id 21327696 stop_sequence 16 has stop_id wimcrec but GTFS stop_sequence 16 has stop_id wimcrec2 - stop_ids should be the same
GTFS-rt stop_sequence not found in GTFS data E051 3 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 21323895 contains stop_sequence 1 that does not exist in GTFS stop_times.txt for this trip
- GTFS-rt trip_id 21323896 contains stop_sequence 1 that does not exist in GTFS stop_times.txt for this trip
- GTFS-rt trip_id 21327389 contains stop_sequence 1 that does not exist in GTFS stop_times.txt for this trip
Avertissements
vehicle_id not populated W002 34 erreurs
vehicle_id should be populated for TripUpdates and VehiclePositions
Exemples d'erreurs
- trip_id 21327675 does not have a vehicle_id
- trip_id 21323860 does not have a vehicle_id
- trip_id 21327513 does not have a vehicle_id
- trip_id 21327512 does not have a vehicle_id
- trip_id 21323887 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 |
|---|---|---|---|
| E002 | stop_time_updates for a given trip_id must be strictly sorted by increasing stop_sequence | 246 | 31 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. | 3 387 | 31 fois (100 % des validations) |
| W002 | vehicle_id should be populated for TripUpdates and VehiclePositions | 973 | 31 fois (100 % des validations) |
| E011 | All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt | 264 | 28 fois (90 % 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 | 57 | 17 fois (55 % 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 | 27 | 16 fois (52 % des validations) |
| E051 | All stop_time_update stop_sequences in GTFS-realtime data must appear in GTFS stop_times.txt for that trip | 26 | 15 fois (48 % des validations) |
| E037 | Sequential GTFS-rt trip stop_time_updates shouldn't have the same stop_id | 20 | 11 fois (35 % des validations) |
| E003 | All trip_ids provided in the GTFS-rt feed must exist in the GTFS data, unless the schedule_relationship is ADDED | 4 | 1 fois (3 % des validations) |
| E004 | All route_ids provided in the GTFS-rt feed must exist in the GTFS data | 4 | 1 fois (3 % 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 (3 % des validations) |
Contenu du flux GTFS-RT
Entités
Entités présentes dans ce flux le 21/09/2025 à 02h53 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 21/09/2025 à 02h53 Europe/Paris. Vous pouvez consulter la documentation GTFS-RT.
{
"header": {
"gtfsRealtimeVersion": "2.0",
"timestamp": "1758416023"
}
}