Resource details
Horaires en temps réel des 2 lignes régulières 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
❌23 errors
Validation carried out using the current GTFS file and the GTFS-RT the 2025-12-04 at 08:02 Europe/Paris using the MobilityData GTFS-RT validator.
Errors
GTFS-rt trip_id does not exist in GTFS data and does not have schedule_relationship of ADDED E003 4 errors
All trip_ids provided in the GTFS-rt feed must exist in the GTFS data, unless the schedule_relationship is ADDED
Sample errors
- vehicle_id zenbus:Vehicle:5087542386884608:LOC trip_id 9179{APILA_5}-API Ligne A Avril 2025 PS_001_LMWJV does not exist in the GTFS data and does not have schedule_relationship of ADDED
- trip_id 9179{APILA_5}-API Ligne A Avril 2025 PS_001_LMWJV does not exist in the GTFS data and does not have schedule_relationship of ADDED
- vehicle_id zenbus:Vehicle:5167542997876736:LOC trip_id 9169{APILA_5}-API Ligne A Avril 2025 PS_001_LMWJV does not exist in the GTFS data and does not have schedule_relationship of ADDED
- trip_id 9169{APILA_5}-API Ligne A Avril 2025 PS_001_LMWJV 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 4 errors
All route_ids provided in the GTFS-rt feed must exist in the GTFS data
Sample errors
- vehicle_id zenbus:Vehicle:5087542386884608:LOC route_id APILA_5 does not exist in the GTFS data routes.txt
- route_id APILA_5 does not exist in the GTFS data routes.txt
- vehicle_id zenbus:Vehicle:5167542997876736:LOC route_id APILA_5 does not exist in the GTFS data routes.txt
- route_id APILA_5 does not exist in the GTFS data routes.txt
GTFS-rt stop_id does not exist in GTFS data E011 13 errors
All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt
Sample errors
- vehicle_id zenbus:Vehicle:5087542386884608:LOC stop_id ISSCBIZ1 does not exist in GTFS data stops.txt
- trip_id 9179{APILA_5}-API Ligne A Avril 2025 PS_001_LMWJV stop_id ISSGUYN2 does not exist in GTFS data stops.txt
- trip_id 9179{APILA_5}-API Ligne A Avril 2025 PS_001_LMWJV stop_id ISSLJOD2 does not exist in GTFS data stops.txt
- trip_id 9179{APILA_5}-API Ligne A Avril 2025 PS_001_LMWJV stop_id ISSCBIZ1 does not exist in GTFS data stops.txt
- trip_id 9179{APILA_5}-API Ligne A Avril 2025 PS_001_LMWJV stop_id ISSPAMO2 does not exist in GTFS data stops.txt
GTFS-rt agency_id does not exist in GTFS data E034 2 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
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 | 60 | 30 times (100 % of validations) |
| E003 | All trip_ids provided in the GTFS-rt feed must exist in the GTFS data, unless the schedule_relationship is ADDED | 86 | 21 times (70 % of validations) |
| E004 | All route_ids provided in the GTFS-rt feed must exist in the GTFS data | 86 | 21 times (70 % of validations) |
| E011 | All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt | 377 | 21 times (70 % of validations) |
| W002 | vehicle_id should be populated for TripUpdates and VehiclePositions | 4 | 4 times (13 % 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 | 4 times (13 % of validations) |
GTFS-RT feed content
Entities
Entities present in this feed at 2025-12-05 at 05:34 Europe/Paris.
service_alerts (2) 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 2025-12-05 at 05:34 Europe/Paris.
TECHNICAL_PROBLEM Unknown effect
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
From 2025-10-20 at 04:00 Europe/Paris
UNKNOWN_CAUSE Unknown effect
La ligne A circule à nouveau. Avec nos excuses pour la gêne occasionnée
From 2025-10-20 at 04:00 Europe/Paris
Decoded GTFS-RT feed
See full payload
Here is the decoded GTFS-RT feed Protobuf at 2025-12-05 at 05:34 Europe/Paris. You can look at the GTFS-RT documentation.
{
"entity": [
{
"alert": {
"activePeriod": [
{
"start": "1760925600"
}
],
"cause": "TECHNICAL_PROBLEM",
"descriptionText": {
"translation": [
{
"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": [
{
"text": "TECHNICAL_PROBLEM"
}
]
},
"informedEntity": [
{
"agencyId": "Zenbus"
}
]
},
"id": "4786578602852352"
},
{
"alert": {
"activePeriod": [
{
"start": "1760925600"
}
],
"descriptionText": {
"translation": [
{
"text": "La ligne A circule à nouveau.\r\nAvec nos excuses pour la gêne occasionnée"
}
]
},
"headerText": {
"translation": [
{
"text": "UNKNOWN_CAUSE"
}
]
},
"informedEntity": [
{
"agencyId": "Zenbus"
}
]
},
"id": "4830522996948992"
}
],
"header": {
"gtfsRealtimeVersion": "2.0",
"timestamp": "1764909243"
}
}