Détails de la ressource
Cette ressource fait partie du jeu de données Réseau urbain CarSud.
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
❌821 erreurs, 4 avertissements
Validation effectuée en utilisant le fichier GTFS en vigueur et le GTFS-RT, le 26/12/2024 à 08h18 Europe/Paris avec le validateur GTFS-RT de MobilityData.
Erreurs
Sequential stop_time_update times are not increasing E022 4 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 543 stop_sequence 27 arrival_time 11:22:10 (1735197730) is less than previous stop departure_time 11:22:51 (1735197771) - times must increase between two sequential stops
- trip_id 543 stop_sequence 28 arrival_time 11:22:42 (1735197762) is less than previous stop departure_time 11:23:10 (1735197790) - times must increase between two sequential stops
- trip_id 543 stop_sequence 29 arrival_time 11:23:26 (1735197806) is equal to previous stop departure_time 11:23:26 (1735197806) - times must increase between two sequential stops
- trip_id 352 stop_sequence 26 arrival_time 11:24:53 (1735197893) is less than previous stop departure_time 11:25:01 (1735197901) - times must increase between two sequential stops
GTFS-rt stop_time_update stop_sequence and stop_id do not match GTFS E045 810 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 215 stop_sequence 10 has stop_id SJ03940P but GTFS stop_sequence 10 has stop_id SJ00025P - stop_ids should be the same
- GTFS-rt trip_id 215 stop_sequence 11 has stop_id SJ00010P but GTFS stop_sequence 11 has stop_id SJ03940P - stop_ids should be the same
- GTFS-rt trip_id 215 stop_sequence 12 has stop_id SJ00010C but GTFS stop_sequence 12 has stop_id SJ00010P - stop_ids should be the same
- GTFS-rt trip_id 215 stop_sequence 13 has stop_id SJ03940C but GTFS stop_sequence 13 has stop_id SJ00010C - stop_ids should be the same
- GTFS-rt trip_id 215 stop_sequence 14 has stop_id SJ00025C but GTFS stop_sequence 14 has stop_id SJ03940C - stop_ids should be the same
GTFS-rt stop_sequence not found in GTFS data E051 7 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 878 contains stop_sequence 0 that does not exist in GTFS stop_times.txt for this trip
- GTFS-rt trip_id 546 contains stop_sequence 0 that does not exist in GTFS stop_times.txt for this trip
- GTFS-rt trip_id 545 contains stop_sequence 0 that does not exist in GTFS stop_times.txt for this trip
- GTFS-rt trip_id 547 contains stop_sequence 0 that does not exist in GTFS stop_times.txt for this trip
- GTFS-rt trip_id 430 contains stop_sequence 55 that does not exist in GTFS stop_times.txt for this trip
Avertissements
vehicle_id not populated W002 2 erreurs
vehicle_id should be populated for TripUpdates and VehiclePositions
Exemples d'erreurs
- trip_id 539 does not have a vehicle_id
- trip_id 430 does not have a vehicle_id
ID in one feed missing from the other W003 2 erreurs
a trip_id that is provided in the VehiclePositions feed should be provided in the TripUpdates feed, and a vehicle_id that is provided in the TripUpdates feed should be provided in the VehiclePositions feed
Exemples d'erreurs
- trip_id 430 is in TripUpdates but not in VehiclePositions feed
- trip_id 539 is in TripUpdates but not in VehiclePositions feed
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 |
|---|---|---|---|
| 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 | 17 950 | 29 fois (97 % des validations) |
| E051 | All stop_time_update stop_sequences in GTFS-realtime data must appear in GTFS stop_times.txt for that trip | 250 | 29 fois (97 % des validations) |
| E022 | stop_time_update arrival/departure times between sequential stops should always increase - they should never be the same or decrease. | 220 | 24 fois (80 % des validations) |
| W002 | vehicle_id should be populated for TripUpdates and VehiclePositions | 62 | 23 fois (77 % des validations) |
| W003 | a trip_id that is provided in the VehiclePositions feed should be provided in the TripUpdates feed, and a vehicle_id that is provided in the TripUpdates feed should be provided in the VehiclePositions feed | 62 | 23 fois (77 % des validations) |
| E023 | For normal scheduled trips (i.e., not defined in frequencies.txt), the GTFS-realtime trip start_time must match the first GTFS arrival_time in stop_times.txt for this trip | 45 | 1 fois (3 % des validations) |
| E024 | GTFS-rt trip direction_id must match the direction_id in GTFS trips.txt | 17 | 1 fois (3 % des validations) |
| E028 | The vehicle position should be inside the agency coverage area. This is defined as within roughly 1/8 of a mile (200 meters) of the GTFS shapes.txt data, or stops.txt locations if the GTFS feed doesn't include shapes.txt. | 1 | 1 fois (3 % des validations) |
| E035 | The GTFS-rt trip.trip_id should belong to the specified trip.route_id in GTFS trips.txt | 37 | 1 fois (3 % des validations) |
Contenu du flux GTFS-RT
Entités
Entités présentes dans ce flux le 27/12/2024 à 00h14 Europe/Paris.
service_alerts (0) trip_updates (0) vehicle_positions (0)Entités présentes dans ce flux lors des 7 derniers jours.
trip_updates vehicle_positionsFlux GTFS-RT décodé
Voir le contenu du flux
Voici le flux GTFS-RT décodé au format Protobuf le 27/12/2024 à 00h14 Europe/Paris. Vous pouvez consulter la documentation GTFS-RT.
{
"header": {
"gtfs_realtime_version": "2.0",
"timestamp": "1735254880"
}
}