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
We test this resource download availability every hour by making an HTTPHEAD 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.
Validation details
❌4 errors, 74 warnings
Validation carried out using the current GTFS file and the GTFS-RT the 2024-07-26 at 09:00 Europe/Paris using the MobilityData GTFS-RT validator.
Errors
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-33685519 stop_sequence 10 arrival_time 08:55:50 (1721976950) is less than previous stop arrival_time 08:57:13 (1721977033) - times must increase between two sequential stops
- trip_id 1-33685519 stop_sequence 10 arrival_time 08:55:50 (1721976950) is less than previous stop departure_time 08:57:13 (1721977033) - times must increase between two sequential stops
- trip_id 1-33685519 stop_sequence 10 departure_time 08:56:11 (1721976971) is less than previous stop departure_time 08:57:13 (1721977033) - times must increase between two sequential stops
- trip_id 1-33685519 stop_sequence 10 departure_time 08:56:11 (1721976971) is less than previous stop arrival_time 08:57:13 (1721977033) - times must increase between two sequential stops
Warnings
timestamp not populated W001 39 errors
Timestamps should be populated for all elements
Sample errors
- trip_id 1-67239943 does not have a timestamp
- trip_id 1-33685519 does not have a timestamp
- trip_id 1-16908301 does not have a timestamp
- trip_id 15-50397193 does not have a timestamp
- trip_id 1-33816604 does not have a timestamp
vehicle_id not populated W002 35 errors
vehicle_id should be populated for TripUpdates and VehiclePositions
Sample errors
- trip_id 1-33816604 does not have a vehicle_id
- trip_id 1-33685516 does not have a vehicle_id
- trip_id 1-33816588 does not have a vehicle_id
- trip_id 15-50528266 does not have a vehicle_id
- trip_id 1-16908304 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 | 873 | 29 times (97 % of validations) |
| W002 | vehicle_id should be populated for TripUpdates and VehiclePositions | 780 | 29 times (97 % of validations) |
| E022 | stop_time_update arrival/departure times between sequential stops should always increase - they should never be the same or decrease. | 12 | 3 times (10 % 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. | 2 | 2 times (7 % of validations) |
GTFS-RT feed content
Entities
Entities present in this feed at 2024-07-27 at 03:57 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-07-27 at 03:57 Europe/Paris. You can look at the GTFS-RT documentation.
{
"header": {
"gtfs_realtime_version": "2.0",
"timestamp": "1722045427"
}
}