Détails de la ressource
horaires en temps réel du réseau Tedbus
Cette ressource fait partie du jeu de données Réseau urbain TEDbus.
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
❌72 erreurs, 34 avertissements
Validation effectuée en utilisant le fichier GTFS en vigueur et le GTFS-RT, le 24/06/2026 à 09h09 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 38 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
- vehicle_id 603e66d019dc980001999ec5 trip_id 1000618-1005608 does not exist in the GTFS data and does not have schedule_relationship of ADDED
- vehicle_id 603e66e4fde2aa000150fd62 trip_id 1000620-1005651 does not exist in the GTFS data and does not have schedule_relationship of ADDED
- vehicle_id 5e85e7ad43f08510097289b5 trip_id 1000661-1005796 does not exist in the GTFS data and does not have schedule_relationship of ADDED
- vehicle_id 603e6711ab91a400017598c7 trip_id 1000614-1005448 does not exist in the GTFS data and does not have schedule_relationship of ADDED
- vehicle_id 61c189e9f8f0f0c4ac7ed48b trip_id 1000615-1005489 does not exist in the GTFS data and does not have schedule_relationship of ADDED
Sequential stop_time_update times are not increasing E022 7 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 1000620-1005651 stop_sequence 16 arrival_time 09:31:00 (1782286260) is less than previous stop arrival_time 09:31:01 (1782286261) - times must increase between two sequential stops
- trip_id 1000620-1005651 stop_sequence 16 arrival_time 09:31:00 (1782286260) is less than previous stop departure_time 09:31:01 (1782286261) - times must increase between two sequential stops
- trip_id 1000620-1005651 stop_sequence 16 departure_time 09:31:00 (1782286260) is less than previous stop departure_time 09:31:01 (1782286261) - times must increase between two sequential stops
- trip_id 1000620-1005651 stop_sequence 16 departure_time 09:31:00 (1782286260) is less than previous stop arrival_time 09:31:01 (1782286261) - times must increase between two sequential stops
- trip_id 1000560-1004725 stop_sequence 11 arrival_time 09:08:36 (1782284916) is less than previous stop departure_time 09:09:00 (1782284940) - times must increase between two sequential stops
stop_time_update doesn't have arrival or departure E043 13 erreurs
If a stop_time_update doesn't have a schedule_relationship of SKIPPED or NO_DATA, then either arrival or departure must be provided
Exemples d'erreurs
- trip_id 1000617-1005572 stop_sequence 28 doesn't have arrival or departure
- trip_id 1000561-1004753 stop_sequence 7 doesn't have arrival or departure
- trip_id 1000561-1004753 stop_sequence 8 doesn't have arrival or departure
- trip_id 1000561-1004753 stop_sequence 9 doesn't have arrival or departure
- trip_id 1000561-1004753 stop_sequence 10 doesn't have arrival or departure
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 1000383-1003074 stop_sequence 8 has stop_id 1000660 but GTFS stop_sequence 8 has stop_id 1001406 - stop_ids should be the same
- GTFS-rt trip_id 1000383-1003074 stop_sequence 9 has stop_id 1001406 but GTFS stop_sequence 9 has stop_id 1001405 - stop_ids should be the same
- GTFS-rt trip_id 1000383-1003074 stop_sequence 10 has stop_id 1001405 but GTFS stop_sequence 10 has stop_id 1001404 - stop_ids should be the same
- GTFS-rt trip_id 1000383-1003074 stop_sequence 11 has stop_id 1001404 but GTFS stop_sequence 11 has stop_id 1001403 - stop_ids should be the same
- GTFS-rt trip_id 1000383-1003074 stop_sequence 12 has stop_id 1001403 but GTFS stop_sequence 12 has stop_id 1000676 - stop_ids should be the same
VehiclePosition and TripUpdate ID pairing mismatch E047 5 erreurs
If separate `VehiclePositions` and `TripUpdates` feeds are provided, `VehicleDescriptor` or `TripDescriptor` ID value pairing should match between the two feeds.
Exemples d'erreurs
- trip_id 1000616-1005510 and vehicle_id 603e66be8d0d800001d8f8c0 pairing in VehiclePositions does not match trip_id 1000614-1005474 and vehicle_id 603e66be8d0d800001d8f8c0 pairing in TripUpdates feed and trip block_ids aren't the same - ID pairing between feeds should match
- trip_id 1000620-1005651 and vehicle_id 603e66e4fde2aa000150fd62 pairing in VehiclePositions does not match trip_id 1000622-1005703 and vehicle_id 603e66e4fde2aa000150fd62 pairing in TripUpdates feed and trip block_ids aren't the same - ID pairing between feeds should match
- trip_id 1000379-1003051 and vehicle_id 674748ecdea1b1b93c742252 pairing in VehiclePositions does not match trip_id 1000623-1005716 and vehicle_id 674748ecdea1b1b93c742252 pairing in TripUpdates feed and trip block_ids aren't the same - ID pairing between feeds should match
- trip_id 1000614-1005448 and vehicle_id 603e6711ab91a400017598c7 pairing in VehiclePositions does not match trip_id 1000616-1005531 and vehicle_id 603e6711ab91a400017598c7 pairing in TripUpdates feed and trip block_ids aren't the same - ID pairing between feeds should match
- trip_id 1000618-1005608 and vehicle_id 603e66d019dc980001999ec5 pairing in VehiclePositions does not match trip_id 1000617-1005562 and vehicle_id 603e66d019dc980001999ec5 pairing in TripUpdates feed and trip block_ids aren't the same - ID pairing between feeds should match
Avertissements
ID in one feed missing from the other W003 34 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 1000617-1005555 is in TripUpdates but not in VehiclePositions feed
- trip_id 1000616-1005531 is in TripUpdates but not in VehiclePositions feed
- trip_id 1000670-1005808 is in TripUpdates but not in VehiclePositions feed
- trip_id 1000661-1005792 is in TripUpdates but not in VehiclePositions feed
- trip_id 1000561-1004753 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 |
|---|---|---|---|
| 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 | 1 043 | 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 | 872 | 26 fois (87 % des validations) |
| E022 | stop_time_update arrival/departure times between sequential stops should always increase - they should never be the same or decrease. | 220 | 26 fois (87 % des validations) |
| E047 | If separate `VehiclePositions` and `TripUpdates` feeds are provided, `VehicleDescriptor` or `TripDescriptor` ID value pairing should match between the two feeds. | 133 | 26 fois (87 % des validations) |
| E043 | If a stop_time_update doesn't have a schedule_relationship of SKIPPED or NO_DATA, then either arrival or departure must be provided | 347 | 25 fois (83 % 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 | 315 | 19 fois (63 % des validations) |
| E029 | The vehicle position should be within a certain distance of the GTFS shapes.txt data for the current trip unless there is a Service Alert with the Effect of DETOUR for this trip_id. | 1 | 1 fois (3 % des validations) |
Contenu du flux GTFS-RT
Entités
Entités présentes dans ce flux le 25/06/2026 à 03h33 Europe/Paris.
service_alerts (2) vehicle_positions (0) trip_updates (0)Entités présentes dans ce flux lors des 7 derniers jours.
service_alerts trip_updates vehicle_positionsService alerts (infos trafic)
Voici un aperçu des informations de trafic présentes dans ce flux le 25/06/2026 à 03h33 Europe/Paris.
ligne 11 - retard Retards importants
⚠️ INFO TRAFIC : LIGNE 11 En raison de travaux de voirie, la circulation est perturbée sur la ligne Lorgues ↔ Draguignan.Des retards sont à prévoir. Merci de votre compréhension.
LIGNE 6 - COURSE FLAY COLOR - 27 JUIN 2026 Arrêt déplacé
⚠️ INFO TRAFIC – PERTURBATIONsamedi 27 juin à partir de 09h00 En raison de la course "FLAY COLOR", les arrêts suivants ne seront pas desservis : Ligne 6 ❌ PLACE DU VILLAGE ❌LAVOIR Conseil : Nous invitons les voyageurs à anticiper leurs déplacementsou à se reporter sur les arrêts situés en amont et en aval des zones concernées. Le réseau TEDBUS vous remercie de votre compréhension pour la gêne occasionnée.
Du 25/06/2026 à 00h00 Europe/Paris au 27/06/2026 à 23h59 Europe/Paris
Flux GTFS-RT décodé
Voir le contenu du flux
Voici le flux GTFS-RT décodé au format Protobuf le 25/06/2026 à 03h33 Europe/Paris. Vous pouvez consulter la documentation GTFS-RT.
{
"entity": [
{
"alert": {
"cause": "CONSTRUCTION",
"descriptionText": {
"translation": [
{
"text": "⚠️ INFO TRAFIC : LIGNE 11\n\nEn raison de travaux de voirie, la circulation est perturbée sur la ligne Lorgues ↔ Draguignan.Des retards sont à prévoir.\n\nMerci de votre compréhension."
}
]
},
"effect": "SIGNIFICANT_DELAYS",
"headerText": {
"translation": [
{
"text": "ligne 11 - retard"
}
]
},
"informedEntity": [
{
"routeId": "1000003"
}
]
},
"id": "alert:6a2a7ed9e84cdb254819679b"
},
{
"alert": {
"activePeriod": [
{
"end": "1782597540",
"start": "1782338400"
}
],
"cause": "HOLIDAY",
"descriptionText": {
"translation": [
{
"text": "⚠️ INFO TRAFIC – PERTURBATIONsamedi 27 juin à partir de 09h00\n\nEn raison de la course \"FLAY COLOR\", les arrêts suivants ne seront pas desservis :\n\n Ligne 6\n\n❌ PLACE DU VILLAGE\n\n\n❌LAVOIR\n\n\n\n Conseil : Nous invitons les voyageurs à anticiper leurs déplacementsou à se reporter sur les arrêts situés en amont et en aval des zones concernées.\n\nLe réseau TEDBUS vous remercie de votre compréhension pour la gêne occasionnée."
}
]
},
"effect": "STOP_MOVED",
"headerText": {
"translation": [
{
"text": "LIGNE 6 - COURSE FLAY COLOR - 27 JUIN 2026"
}
]
},
"informedEntity": [
{
"routeId": "1000008"
}
]
},
"id": "alert:6a2bf5be8c84824b0c88da08"
}
],
"header": {
"gtfsRealtimeVersion": "2.0",
"timestamp": "1782351217"
}
}