Détails de la ressource
Horaires de prochains passages aux arrêts
Cette ressource fait partie du jeu de données Réseau urbain Mistral.
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
❌250 erreurs, 73 avertissements
Validation effectuée en utilisant le fichier GTFS en vigueur et le GTFS-RT, le 02/11/2025 à 08h01 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 2 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 9525 does not exist in the GTFS data and does not have schedule_relationship of ADDED
- trip_id 9526 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 2 erreurs
All route_ids provided in the GTFS-rt feed must exist in the GTFS data
Exemples d'erreurs
- route_id 0095 does not exist in the GTFS data routes.txt
- route_id 0095 does not exist in the GTFS data routes.txt
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 9525 stop_id SEBRG2 does not exist in GTFS data stops.txt
- trip_id 9525 stop_id SEBRG3 does not exist in GTFS data stops.txt
- trip_id 9525 stop_id SEBRG4 does not exist in GTFS data stops.txt
- trip_id 9525 stop_id SEBRG5 does not exist in GTFS data stops.txt
- trip_id 9526 stop_id SEBRG2 does not exist in GTFS data stops.txt
Header timestamp should be greater than or equal to all other timestamps E012 66 erreurs
No timestamps for individual entities (TripUpdate, VehiclePosition) in the feeds should be greater than the header timestamp
Exemples d'erreurs
- trip_id 5456407 timestamp 1762067148 is greater than the header
- trip_id 5456399 timestamp 1762067148 is greater than the header
- trip_id 5456410 timestamp 1762066948 is greater than the header
- trip_id 5456409 timestamp 1762067158 is greater than the header
- trip_id 5456408 timestamp 1762067138 is greater than the header
Sequential stop_time_update times are not increasing E022 114 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 5456407 stop_id TOPASS arrival_time 08:00:40 (1762066840) is equal to previous stop departure_time 08:00:40 (1762066840) - times must increase between two sequential stops
- trip_id 5456407 stop_id TOPASS departure_time 08:00:40 (1762066840) is equal to previous stop departure_time 08:00:40 (1762066840) - times must increase between two sequential stops
- trip_id 5456407 stop_id TOBNRS arrival_time 08:04:15 (1762067055) is less than previous stop arrival_time 08:04:22 (1762067062) - times must increase between two sequential stops
- trip_id 5456407 stop_id TOBNRS arrival_time 08:04:15 (1762067055) is less than previous stop departure_time 08:04:22 (1762067062) - times must increase between two sequential stops
- trip_id 5456407 stop_id TOBNRS departure_time 08:04:15 (1762067055) is less than previous stop departure_time 08:04:22 (1762067062) - times must increase between two sequential stops
timestamp is in the future E050 58 erreurs
All timestamps must be less than the current time
Exemples d'erreurs
- trip_id 5456407 timestamp 08:05:48 (1762067148) is 4 min 38 sec greater than 08:01:09 (1762066869302) - the current time in milliseconds
- trip_id 5456399 timestamp 08:05:48 (1762067148) is 4 min 38 sec greater than 08:01:09 (1762066869302) - the current time in milliseconds
- trip_id 5456410 timestamp 08:02:28 (1762066948) is 1 min 18 sec greater than 08:01:09 (1762066869302) - the current time in milliseconds
- trip_id 5456409 timestamp 08:05:58 (1762067158) is 4 min 48 sec greater than 08:01:09 (1762066869302) - the current time in milliseconds
- trip_id 5456408 timestamp 08:05:38 (1762067138) is 4 min 28 sec greater than 08:01:09 (1762066869302) - the current time in milliseconds
Avertissements
vehicle_id not populated W002 72 erreurs
vehicle_id should be populated for TripUpdates and VehiclePositions
Exemples d'erreurs
- trip_id 5456399 does not have a vehicle_id
- trip_id 5456393 does not have a vehicle_id
- trip_id 5456404 does not have a vehicle_id
- trip_id 5456406 does not have a vehicle_id
- trip_id 5456396 does not have a vehicle_id
Header timestamp is older than 65 seconds W008 1 erreur
The data in a GTFS-realtime feed should always be less than one minute old
Exemples d'erreurs
- header.timestamp is 1 min 23 sec old which is greater than the recommended age of 65 seconds
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 |
|---|---|---|---|
| E012 | No timestamps for individual entities (TripUpdate, VehiclePosition) in the feeds should be greater than the header timestamp | 7 355 | 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. | 9 477 | 30 fois (100 % des validations) |
| E050 | All timestamps must be less than the current time | 6 775 | 30 fois (100 % des validations) |
| W002 | vehicle_id should be populated for TripUpdates and VehiclePositions | 6 329 | 30 fois (100 % des validations) |
| W008 | The data in a GTFS-realtime feed should always be less than one minute old | 30 | 30 fois (100 % des validations) |
| E003 | All trip_ids provided in the GTFS-rt feed must exist in the GTFS data, unless the schedule_relationship is ADDED | 77 | 28 fois (93 % des validations) |
| E004 | All route_ids provided in the GTFS-rt feed must exist in the GTFS data | 77 | 28 fois (93 % des validations) |
| E011 | All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt | 80 | 28 fois (93 % 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. | 31 | 18 fois (60 % des validations) |
| E002 | stop_time_updates for a given trip_id must be strictly sorted by increasing stop_sequence | 39 | 12 fois (40 % des validations) |
| E037 | Sequential GTFS-rt trip stop_time_updates shouldn't have the same stop_id | 1 528 | 12 fois (40 % des validations) |
Contenu du flux GTFS-RT
Entités
Entités présentes dans ce flux le 03/11/2025 à 00h57 Europe/Paris.
trip_updates (1) vehicle_positions (0) service_alerts (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 03/11/2025 à 00h57 Europe/Paris. Vous pouvez consulter la documentation GTFS-RT.
{
"entity": [
{
"id": "5459857",
"tripUpdate": {
"stopTimeUpdate": [
{
"arrival": {
"delay": 0,
"time": "1762126800"
},
"departure": {
"delay": 0,
"time": "1762126800"
},
"stopId": "SMPSMS"
},
{
"arrival": {
"delay": 0,
"time": "1762126920"
},
"departure": {
"delay": 0,
"time": "1762126920"
},
"stopId": "SMPPRO"
},
{
"departure": {
"delay": 0,
"time": "1762128120"
},
"stopId": "TOPTOS"
}
],
"timestamp": "1762127111",
"trip": {
"directionId": 1,
"routeId": "28M",
"scheduleRelationship": "SCHEDULED",
"tripId": "5459857"
},
"vehicle": {}
}
}
],
"header": {
"gtfsRealtimeVersion": "2.0",
"timestamp": "1762127841"
}
}