Resource details
Les messages suivants du format GTFS-RT sont disponibles dans ce flux :
- TripUpdate
This resource file is part of the dataset Réseau urbain et scolaire Guingamp-Paimpol Mobilité.
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
❌304 errors, 105 warnings
Validation carried out using the current GTFS file and the GTFS-RT the 2024-11-21 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 28 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-923074561 does not exist in the GTFS data and does not have schedule_relationship of ADDED
- trip_id 1-587530241 does not exist in the GTFS data and does not have schedule_relationship of ADDED
- trip_id 1-739049473 does not exist in the GTFS data and does not have schedule_relationship of ADDED
- trip_id 1-755367937 does not exist in the GTFS data and does not have schedule_relationship of ADDED
- trip_id 1-604766209 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 28 errors
All route_ids provided in the GTFS-rt feed must exist in the GTFS data
Sample errors
- route_id 55 does not exist in the GTFS data routes.txt
- route_id 35 does not exist in the GTFS data routes.txt
- route_id 44 does not exist in the GTFS data routes.txt
- route_id 45 does not exist in the GTFS data routes.txt
- route_id 36 does not exist in the GTFS data routes.txt
GTFS-rt stop_id does not exist in GTFS data E011 243 errors
All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt
Sample errors
- trip_id 1-923074561 stop_id 17924 does not exist in GTFS data stops.txt
- trip_id 1-923074561 stop_id 11058 does not exist in GTFS data stops.txt
- trip_id 1-923074561 stop_id 8362 does not exist in GTFS data stops.txt
- trip_id 1-923074561 stop_id 11061 does not exist in GTFS data stops.txt
- trip_id 1-923074561 stop_id 11060 does not exist in GTFS data stops.txt
Sequential stop_time_update times are not increasing E022 4 errors
stop_time_update arrival/departure times between sequential stops should always increase - they should never be the same or decrease.
Sample errors
- trip_id 1-604766209 stop_sequence 11 arrival_time 07:21:00 (1732170060) is less than previous stop arrival_time 08:11:43 (1732173103) - times must increase between two sequential stops
- trip_id 1-604766209 stop_sequence 11 arrival_time 07:21:00 (1732170060) is less than previous stop departure_time 08:11:43 (1732173103) - times must increase between two sequential stops
- trip_id 1-604766209 stop_sequence 11 departure_time 07:21:10 (1732170070) is less than previous stop departure_time 08:11:43 (1732173103) - times must increase between two sequential stops
- trip_id 1-604766209 stop_sequence 11 departure_time 07:21:10 (1732170070) is less than previous stop arrival_time 08:11:43 (1732173103) - times must increase between two sequential stops
stop_time_update departure time is before arrival time E025 1 error
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.
Sample errors
- trip_id 1-655097857 stop_sequence 2 departure_time 08:02:03 (1732172523) is less than the same stop arrival_time 08:02:07 (1732172527) - departure time must be equal to or greater than arrival time
Warnings
timestamp not populated W001 59 errors
Timestamps should be populated for all elements
Sample errors
- trip_id 1-923074561 does not have a timestamp
- trip_id 1-587530241 does not have a timestamp
- trip_id 25-16908302 does not have a timestamp
- trip_id 1-739049473 does not have a timestamp
- trip_id 1-755367937 does not have a timestamp
vehicle_id not populated W002 46 errors
vehicle_id should be populated for TripUpdates and VehiclePositions
Sample errors
- trip_id 1-587595778 does not have a vehicle_id
- trip_id 25-16908308 does not have a vehicle_id
- trip_id 25-16908317 does not have a vehicle_id
- trip_id 25-16908291 does not have a vehicle_id
- trip_id 25-16908292 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 |
|---|---|---|---|
| W001 | Timestamps should be populated for all elements | 811 | 20 times (69 % of validations) |
| W002 | vehicle_id should be populated for TripUpdates and VehiclePositions | 640 | 19 times (66 % of validations) |
| E003 | All trip_ids provided in the GTFS-rt feed must exist in the GTFS data, unless the schedule_relationship is ADDED | 278 | 11 times (38 % of validations) |
| E004 | All route_ids provided in the GTFS-rt feed must exist in the GTFS data | 278 | 11 times (38 % of validations) |
| E011 | All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt | 2 229 | 11 times (38 % 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. | 5 | 5 times (17 % of validations) |
| E022 | stop_time_update arrival/departure times between sequential stops should always increase - they should never be the same or decrease. | 14 | 3 times (10 % of validations) |
GTFS-RT feed content
Entities
Entities present in this feed at 2024-11-21 at 21:40 Europe/Paris.
service_alerts (0) trip_updates (0) vehicle_positions (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 2024-11-21 at 21:40 Europe/Paris. You can look at the GTFS-RT documentation.
{
"header": {
"gtfs_realtime_version": "2.0",
"timestamp": "1732221630"
}
}