Resource details
This resource file is part of the dataset Navettes Paris - Saclay.
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
✅No error detected
Validation carried out using the current GTFS file and the GTFS-RT the 2025-04-10 at 09:10 Europe/Paris using the MobilityData GTFS-RT validator.
Validate this GTFS-RT nowPrevious validations
Here is a recap of all the error types encountered over the last 30 days.
| Error ID | Description | Errors count | Number of occurences |
|---|---|---|---|
| W002 | vehicle_id should be populated for TripUpdates and VehiclePositions | 9 | 8 times (27 % 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 | 9 | 8 times (27 % of 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. | 6 | 6 times (20 % of 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 times (3 % of validations) |
GTFS-RT feed content
Entities
Entities present in this feed at 2025-04-11 at 01: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 2025-04-11 at 01:47 Europe/Paris.
TECHNICAL_PROBLEM Unknown effect
Mesdames, Messieurs, En raison d'une panne sur la navette, les départs suivants ne seront pas réalisés - 12h00 - 12h09 - 12h17 - 12h45 - 12h54 - 13h02 Nous vous prions de bien vouloir nous excuser pour la gêne occasionnée.
Between 2025-04-10 at 04:00 Europe/Paris and 2025-04-11 at 04:00 Europe/Paris
INFORMATION Unknown effect
Mesdames, Messieurs, En raison d'une absence de conducteur les départs suivants ne seront pas réalisés. - 09h30 Pileu - 10h10 Perigord - 10h50 Pileu - 11h30 Perigord - 12h10 Pileu - 12h50 Perigord - 13h30 Pileu Nous vous prions de bien vouloir nous excuser pour la gêne occasionnée.
Between 2025-04-10 at 04:00 Europe/Paris and 2025-04-11 at 04:00 Europe/Paris
TECHNICAL_PROBLEM Unknown effect
Mesdames, Messieurs, En raison de la circulation, le départs de 09h30 Périgord sera effectue avec 10 minutes de retards. Nous vous prions de bien vouloir nous excuser pour la gêne occasionnée.
Between 2025-04-10 at 04:00 Europe/Paris and 2025-04-11 at 04:00 Europe/Paris
Decoded GTFS-RT feed
See full payload
Here is the decoded GTFS-RT feed Protobuf at 2025-04-11 at 01:47 Europe/Paris. You can look at the GTFS-RT documentation.
{
"entity": [
{
"alert": {
"active_period": [
{
"end": "1744336800",
"start": "1744250400"
}
],
"cause": "TECHNICAL_PROBLEM",
"description_text": {
"translation": [
{
"text": "Mesdames, Messieurs,\r\n\r\nEn raison d'une panne sur la navette, les départs suivants ne seront pas réalisés\r\n\r\n- 12h00\r\n- 12h09\r\n- 12h17\r\n- 12h45\r\n- 12h54\r\n- 13h02\r\n\r\nNous vous prions de bien vouloir nous excuser pour la gêne occasionnée."
}
]
},
"header_text": {
"translation": [
{
"text": "TECHNICAL_PROBLEM"
}
]
},
"informed_entity": [
{
"route_id": "zenbus:Line:353580001:LOC"
},
{
"route_id": "zenbus:Line:646330001:LOC"
}
]
},
"id": "4899282592202752"
},
{
"alert": {
"active_period": [
{
"end": "1744336800",
"start": "1744250400"
}
],
"cause": "OTHER_CAUSE",
"description_text": {
"translation": [
{
"text": "Mesdames, Messieurs,\r\n\r\nEn raison d'une absence de conducteur les départs suivants ne seront pas réalisés.\r\n\r\n- 09h30 Pileu\r\n- 10h10 Perigord\r\n- 10h50 Pileu\r\n- 11h30 Perigord\r\n- 12h10 Pileu\r\n- 12h50 Perigord\r\n- 13h30 Pileu\r\n\r\nNous vous prions de bien vouloir nous excuser pour la gêne occasionnée."
}
]
},
"header_text": {
"translation": [
{
"text": "INFORMATION"
}
]
},
"informed_entity": [
{
"route_id": "zenbus:Line:351080019:LOC"
}
]
},
"id": "4863481690980352"
},
{
"alert": {
"active_period": [
{
"end": "1744336800",
"start": "1744250400"
}
],
"cause": "TECHNICAL_PROBLEM",
"description_text": {
"translation": [
{
"text": "Mesdames, Messieurs,\r\n\r\nEn raison de la circulation, le départs de 09h30 Périgord sera effectue avec 10 minutes de retards.\r\n\r\nNous vous prions de bien vouloir nous excuser pour la gêne occasionnée."
}
]
},
"header_text": {
"translation": [
{
"text": "TECHNICAL_PROBLEM"
}
]
},
"informed_entity": [
{
"route_id": "zenbus:Line:351080019:LOC"
}
]
},
"id": "6486022222249984"
}
],
"header": {
"gtfs_realtime_version": "2.0",
"timestamp": "1744328851"
}
}