Resource details
This resource file is part of the dataset Réseau urbain Le Met'.
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
❌299 errors, 147 warnings
Validation carried out using the current GTFS file and the GTFS-RT the 2025-04-03 at 09:15 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 239 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 0_42678268 does not exist in the GTFS data and does not have schedule_relationship of ADDED
- trip_id 0_42678267 does not exist in the GTFS data and does not have schedule_relationship of ADDED
- trip_id 0_42039725 does not exist in the GTFS data and does not have schedule_relationship of ADDED
- trip_id 0_42678266 does not exist in the GTFS data and does not have schedule_relationship of ADDED
- trip_id 0_42039726 does not exist in the GTFS data and does not have schedule_relationship of ADDED
Sequential stop_time_update times are not increasing E022 60 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 0_42657319 stop_id 0:MARLY1 departure_time 10:09:00 (1743667740) is less than previous stop departure_time 10:15:45 (1743668145) - times must increase between two sequential stops
- trip_id 0_42657319 stop_id 0:MARLY1 departure_time 10:09:00 (1743667740) is less than previous stop arrival_time 10:15:45 (1743668145) - times must increase between two sequential stops
- trip_id 0_42657319 stop_id 0:M113A arrival_time 10:10:13 (1743667813) is less than previous stop arrival_time 10:15:45 (1743668145) - times must increase between two sequential stops
- trip_id 0_42657319 stop_id 0:M113A departure_time 10:10:13 (1743667813) is less than previous stop arrival_time 10:15:45 (1743668145) - times must increase between two sequential stops
- trip_id 0_42657318 stop_id 0:MARLY1 departure_time 09:09:32 (1743664172) is less than previous stop departure_time 09:16:17 (1743664577) - times must increase between two sequential stops
Warnings
vehicle_id not populated W002 147 errors
vehicle_id should be populated for TripUpdates and VehiclePositions
Sample errors
- trip_id 0_42039725 does not have a vehicle_id
- trip_id 0_42039726 does not have a vehicle_id
- trip_id 0_42657319 does not have a vehicle_id
- trip_id 0_42038036 does not have a vehicle_id
- trip_id 0_42038037 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 |
|---|---|---|---|
| E022 | stop_time_update arrival/departure times between sequential stops should always increase - they should never be the same or decrease. | 2 713 | 29 times (100 % of validations) |
| W002 | vehicle_id should be populated for TripUpdates and VehiclePositions | 4 114 | 29 times (100 % of validations) |
| E002 | stop_time_updates for a given trip_id must be strictly sorted by increasing stop_sequence | 405 | 28 times (97 % of validations) |
| E009 | If a GTFS trip contains multiple references to the same stop_id (i.e., the vehicle visits the same stop_id more than once in the same trip), then GTFS-rt stop_time_updates for this trip must include stop_sequence | 168 | 28 times (97 % 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) |
| E037 | Sequential GTFS-rt trip stop_time_updates shouldn't have the same stop_id | 5 | 2 times (7 % of validations) |
| E003 | All trip_ids provided in the GTFS-rt feed must exist in the GTFS data, unless the schedule_relationship is ADDED | 239 | 1 times (3 % of validations) |
GTFS-RT feed content
Entities
Entities present in this feed at 2025-04-04 at 03:46 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 03:46 Europe/Paris. You can look at the GTFS-RT documentation.
{
"header": {
"gtfs_realtime_version": "2.0",
"timestamp": "1743731171"
}
}