Resource details
GTFS-RT des horaires aux arrêts du réseau DeepMob.
This resource file is part of the dataset Réseau urbain DeepMob.
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
❌1 491 errors, 42 warnings
Validation carried out using the current GTFS file and the GTFS-RT the 2025-04-04 at 09:05 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 52 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 177 does not exist in the GTFS data and does not have schedule_relationship of ADDED
- trip_id 235 does not exist in the GTFS data and does not have schedule_relationship of ADDED
- trip_id 325 does not exist in the GTFS data and does not have schedule_relationship of ADDED
- trip_id 399 does not exist in the GTFS data and does not have schedule_relationship of ADDED
- trip_id 485 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 52 errors
All route_ids provided in the GTFS-rt feed must exist in the GTFS data
Sample errors
- route_id 2 does not exist in the GTFS data routes.txt
- route_id 2 does not exist in the GTFS data routes.txt
- route_id 2 does not exist in the GTFS data routes.txt
- route_id 2 does not exist in the GTFS data routes.txt
- route_id 2 does not exist in the GTFS data routes.txt
GTFS-rt stop_id does not exist in GTFS data E011 1 387 errors
All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt
Sample errors
- trip_id 177 stop_id 18038 does not exist in GTFS data stops.txt
- trip_id 177 stop_id 18101 does not exist in GTFS data stops.txt
- trip_id 177 stop_id 18321 does not exist in GTFS data stops.txt
- trip_id 177 stop_id 18023 does not exist in GTFS data stops.txt
- trip_id 177 stop_id 18323 does not exist in GTFS data stops.txt
Warnings
vehicle_id not populated W002 42 errors
vehicle_id should be populated for TripUpdates and VehiclePositions
Sample errors
- trip_id 235 does not have a vehicle_id
- trip_id 325 does not have a vehicle_id
- trip_id 399 does not have a vehicle_id
- trip_id 485 does not have a vehicle_id
- trip_id 271 does not have a vehicle_id
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 | 1 560 | 30 times (100 % of validations) |
E004 | All route_ids provided in the GTFS-rt feed must exist in the GTFS data | 1 560 | 30 times (100 % of validations) |
E011 | All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt | 43 770 | 30 times (100 % of validations) |
W002 | vehicle_id should be populated for TripUpdates and VehiclePositions | 1 319 | 30 times (100 % of validations) |
GTFS-RT feed content
Entities
Entities present in this feed at 2025-04-04 at 20:58 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-04-04 at 20:58 Europe/Paris. You can look at the GTFS-RT documentation.
{
"header": {
"gtfs_realtime_version": "2.0",
"timestamp": "1743793099"
}
}