Resource details
This resource file is part of the dataset Réseau urbain Sète Agglopole 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
❌21 errors, 244 warnings
Validation carried out using the current GTFS file and the GTFS-RT the 2026-03-05 at 08:11 Europe/Paris using the MobilityData GTFS-RT validator.
Errors
Sequential stop_time_update times are not increasing E022 16 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 95118_260224-5446 stop_sequence 1 arrival_time 08:45:00 (1772696700) is less than previous stop arrival_time 08:48:44 (1772696924) - times must increase between two sequential stops
- trip_id 95118_260224-5446 stop_sequence 1 arrival_time 08:45:00 (1772696700) is less than previous stop departure_time 08:48:44 (1772696924) - times must increase between two sequential stops
- trip_id 95118_260224-5446 stop_sequence 1 departure_time 08:45:00 (1772696700) is less than previous stop departure_time 08:48:44 (1772696924) - times must increase between two sequential stops
- trip_id 95118_260224-5446 stop_sequence 1 departure_time 08:45:00 (1772696700) is less than previous stop arrival_time 08:48:44 (1772696924) - times must increase between two sequential stops
- trip_id 95106_260224-5446 stop_sequence 1 arrival_time 09:00:00 (1772697600) is less than previous stop arrival_time 09:10:42 (1772698242) - times must increase between two sequential stops
GTFS-rt stop_sequence not found in GTFS data E051 5 errors
All stop_time_update stop_sequences in GTFS-realtime data must appear in GTFS stop_times.txt for that trip
Sample errors
- GTFS-rt trip_id 95107_260224-5446 contains stop_sequence 0 that does not exist in GTFS stop_times.txt for this trip
- GTFS-rt trip_id 95118_260224-5446 contains stop_sequence 0 that does not exist in GTFS stop_times.txt for this trip
- GTFS-rt trip_id 95106_260224-5446 contains stop_sequence 0 that does not exist in GTFS stop_times.txt for this trip
- GTFS-rt trip_id 95117_260224-5446 contains stop_sequence 0 that does not exist in GTFS stop_times.txt for this trip
- GTFS-rt trip_id 95105_260224-5446 contains stop_sequence 0 that does not exist in GTFS stop_times.txt for this trip
Warnings
timestamp not populated W001 122 errors
Timestamps should be populated for all elements
Sample errors
- trip_id 96067_260224-5410 does not have a timestamp
- trip_id 96026_260224-5410 does not have a timestamp
- trip_id 96068_260224-5410 does not have a timestamp
- trip_id 96027_260224-5410 does not have a timestamp
- trip_id 96069_260224-5410 does not have a timestamp
schedule_relationship not populated W009 122 errors
trip.schedule_relationship and stop_time_update.schedule_relationship should be populated
Sample errors
- trip_id 96067_260224-5410 stop_sequence 4 (and potentially more for this trip) does not have a schedule_relationship
- trip_id 96026_260224-5410 stop_sequence 1 (and potentially more for this trip) does not have a schedule_relationship
- trip_id 96068_260224-5410 stop_sequence 1 (and potentially more for this trip) does not have a schedule_relationship
- trip_id 96027_260224-5410 stop_sequence 1 (and potentially more for this trip) does not have a schedule_relationship
- trip_id 96069_260224-5410 stop_sequence 1 (and potentially more for this trip) does not have a schedule_relationship
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 | 3,083 | 29 times (100 % of validations) |
| W009 | trip.schedule_relationship and stop_time_update.schedule_relationship should be populated | 3,083 | 29 times (100 % of validations) |
| E022 | stop_time_update arrival/departure times between sequential stops should always increase - they should never be the same or decrease. | 248 | 18 times (62 % of validations) |
| E003 | All trip_ids provided in the GTFS-rt feed must exist in the GTFS data, unless the schedule_relationship is ADDED | 1,471 | 14 times (48 % of validations) |
| E051 | All stop_time_update stop_sequences in GTFS-realtime data must appear in GTFS stop_times.txt for that trip | 51 | 13 times (45 % of validations) |
GTFS-RT feed content
Entities
Entities present in this feed at 2026-03-05 at 21:43 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 2026-03-05 at 21:43 Europe/Paris. You can look at the GTFS-RT documentation.
{
"header": {
"gtfsRealtimeVersion": "2.0",
"timestamp": "1772743400"
}
}