Resource details
GTFS-RT (protobuff) des horaires aux arrêts.
This resource file is part of the dataset Réseaux urbain MOCA.
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
❌136 errors
Validation carried out using the current GTFS file and the GTFS-RT the 2025-07-03 at 09:08 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 6 errors
All trip_ids provided in the GTFS-rt feed must exist in the GTFS data, unless the schedule_relationship is ADDED
Sample errors
- trip_id 1 does not exist in the GTFS data and does not have schedule_relationship of ADDED
- trip_id 5 does not exist in the GTFS data and does not have schedule_relationship of ADDED
- trip_id 7 does not exist in the GTFS data and does not have schedule_relationship of ADDED
- trip_id 10 does not exist in the GTFS data and does not have schedule_relationship of ADDED
- trip_id 3 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 6 errors
All route_ids provided in the GTFS-rt feed must exist in the GTFS data
Sample errors
- route_id 1 does not exist in the GTFS data routes.txt
- route_id 1 does not exist in the GTFS data routes.txt
- route_id 1 does not exist in the GTFS data routes.txt
- route_id 2 does not exist in the GTFS data routes.txt
- route_id 1 does not exist in the GTFS data routes.txt
GTFS-rt stop_id does not exist in GTFS data E011 124 errors
All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt
Sample errors
- trip_id 1 stop_id 30030 does not exist in GTFS data stops.txt
- trip_id 1 stop_id 30029 does not exist in GTFS data stops.txt
- trip_id 1 stop_id 30038 does not exist in GTFS data stops.txt
- trip_id 1 stop_id 30035 does not exist in GTFS data stops.txt
- trip_id 1 stop_id 30042 does not exist in GTFS data stops.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 |
---|---|---|---|
E003 | All trip_ids provided in the GTFS-rt feed must exist in the GTFS data, unless the schedule_relationship is ADDED | 144 | 25 times (86 % of validations) |
E004 | All route_ids provided in the GTFS-rt feed must exist in the GTFS data | 144 | 25 times (86 % of validations) |
E011 | All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt | 2 601 | 25 times (86 % of 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 | 21 | 9 times (31 % of validations) |
E025 | Within the same stop_time_update, arrival and departures times can be the same, or the departure time can be later than the arrival time - the departure time should never come before the arrival time. | 1 | 1 times (3 % of validations) |
GTFS-RT feed content
Entities
Entities present in this feed at 2025-07-04 at 04:28 Europe/Paris.
vehicle_positions (0) service_alerts (0) trip_updates (0)Entities seen in the last 7 days.
trip_updatesDecoded GTFS-RT feed
See full payload
Here is the decoded GTFS-RT feed Protobuf at 2025-07-04 at 04:28 Europe/Paris. You can look at the GTFS-RT documentation.
{
"header": {
"gtfsRealtimeVersion": "2.0",
"timestamp": "1751596120"
}
}