Resource details
Horaires en temps réel de la ligne régulière A du réseau Cherpa
This resource file is part of the dataset Réseau urbain Cherpa.
Download availability
Learn more
HEAD request with a timeout of 5 seconds. If we detect a downtime, we perform subsequent tests every 10 minutes, until the resource is back online.For SIRI and SIRI Lite feeds, we perform a
GET request: a 401 or 405 status code is considered successful. In case of HTTP 500, the feed will be considered unavailable, unless the body appears to contain SOAP.Validation details
❌16 errors
Validation carried out using the current GTFS file and the GTFS-RT the 2026-09-16 at 09:15 Europe/Paris using the MobilityData GTFS-RT validator.
Errors
GTFS-rt agency_id does not exist in GTFS data E034 3 errors
All agency_ids provided in the GTFS-rt alert.informed_entity.agency_id should also exist in GTFS agency.txt
Sample errors
- alert ID 4786578602852352 agency_id Zenbus does not exist in the GTFS data agency.txt
- alert ID 4830522996948992 agency_id Zenbus does not exist in the GTFS data agency.txt
- alert ID 4856953697206272 agency_id Zenbus does not exist in the GTFS data agency.txt
GTFS-rt stop_time_update stop_sequence and stop_id do not match GTFS E045 13 errors
If GTFS-rt stop_time_update contains both stop_sequence and stop_id, the values must match the GTFS data in stop_times.txt
Sample errors
- GTFS-rt trip_id 9182{APILA_5}-API Ligne A Avril 2025 PS_001_LMWJV stop_sequence 3 has stop_id ISSBARA2 but GTFS stop_sequence 3 has stop_id ISSBMER2 - stop_ids should be the same
- GTFS-rt trip_id 9182{APILA_5}-API Ligne A Avril 2025 PS_001_LMWJV stop_sequence 4 has stop_id ISSAGAI2 but GTFS stop_sequence 4 has stop_id ISSBARA2 - stop_ids should be the same
- GTFS-rt trip_id 9182{APILA_5}-API Ligne A Avril 2025 PS_001_LMWJV stop_sequence 5 has stop_id ISSAQUA2 but GTFS stop_sequence 5 has stop_id ISSAGAI2 - stop_ids should be the same
- GTFS-rt trip_id 9182{APILA_5}-API Ligne A Avril 2025 PS_001_LMWJV stop_sequence 6 has stop_id ISSAVGA2 but GTFS stop_sequence 6 has stop_id ISSAQUA2 - stop_ids should be the same
- GTFS-rt trip_id 9182{APILA_5}-API Ligne A Avril 2025 PS_001_LMWJV stop_sequence 7 has stop_id ISSPARC2 but GTFS stop_sequence 7 has stop_id ISSAVGA2 - stop_ids should be the same
Previous validations
Here is a recap of all the error types encountered over the last 30 days.
| Error ID | Description | Errors count | Number of occurences |
|---|---|---|---|
| E034 | All agency_ids provided in the GTFS-rt alert.informed_entity.agency_id should also exist in GTFS agency.txt | 88 | 29 times (100 % of 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 | 164 | 18 times (62 % of validations) |
| E051 | All stop_time_update stop_sequences in GTFS-realtime data must appear in GTFS stop_times.txt for that trip | 7 | 4 times (14 % of validations) |
| W002 | vehicle_id should be populated for TripUpdates and VehiclePositions | 4 | 1 times (3 % of 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 | 4 | 1 times (3 % of validations) |
GTFS-RT feed content
Entities
Entities present in this feed at 2026-09-16 at 12:47 Europe/Paris.
service_alerts (3) vehicle_positions (0) trip_updates (0)Entities seen in the last 7 days.
service_alerts trip_updates vehicle_positionsService alerts
Here is a display of service alerts contained in this feed at 2026-09-16 at 12:47 Europe/Paris.
Unknown effect
From 2025-10-20 at 04:00 Europe/Paris
Unknown effect
From 2025-10-20 at 04:00 Europe/Paris
Unknown effect
Decoded GTFS-RT feed
See full payload
Here is the decoded GTFS-RT feed Protobuf at 2026-09-16 at 12:47 Europe/Paris. You can look at the GTFS-RT documentation.
{
"entity": [
{
"alert": {
"activePeriod": [
{
"start": "1760925600"
}
],
"cause": "TECHNICAL_PROBLEM",
"descriptionText": {
"translation": [
{
"language": "fr",
"text": "Suite à un problème technique, nous ne sommes pas en mesure d'assurer le service de la ligne A - Nous revenons vers vous dès la reprise de la ligne avec un nouveau message"
}
]
},
"headerText": {
"translation": [
{
"language": "fr",
"text": "Problème technique"
}
]
},
"informedEntity": [
{
"agencyId": "Zenbus"
}
]
},
"id": "4786578602852352"
},
{
"alert": {
"activePeriod": [
{
"start": "1760925600"
}
],
"descriptionText": {
"translation": [
{
"language": "fr",
"text": "La ligne A circule à nouveau.\r\nAvec nos excuses pour la gêne occasionnée"
}
]
},
"headerText": {
"translation": [
{
"language": "fr",
"text": "Problème incconu"
}
]
},
"informedEntity": [
{
"agencyId": "Zenbus"
}
]
},
"id": "4830522996948992"
},
{
"alert": {
"cause": "TECHNICAL_PROBLEM",
"descriptionText": {
"translation": [
{
"language": "fr",
"text": "Bonjour,\r\nSuite problème technique,\r\n- le tour au départ de 16h12 GERMAIN TILLON n'a pu être réalisé. \r\n- le départ de 16h32 CHABRIER ne sera pas réalisé, le bus partira du Parc de l'hôpital. \r\n- le tour de 16h32 au départ de GERMAIN TILLON aura un léger retard.\r\nNous nous excusons pour la gêne occasionnée."
}
]
},
"headerText": {
"translation": [
{
"language": "fr",
"text": "Problème technique"
}
]
},
"informedEntity": [
{
"agencyId": "Zenbus"
}
]
},
"id": "4856953697206272"
}
],
"header": {
"gtfsRealtimeVersion": "2.0",
"timestamp": "1789555643"
}
}