gtfs-rt Transport open dataset - Mises à jour des trajets en temps réel for Réseau urbain Sète Agglopole Mobilité

Resource details

File name: Mises à jour des trajets en temps réel

Format: gtfs-rt

This resource file is part of the dataset Réseau urbain Sète Agglopole Mobilité.

Download availability

Learn more

We test this resource download availability every hour by making an HTTP 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

❌175 errors, 218 warnings

Validation carried out using the current GTFS file and the GTFS-RT the 2025-06-04 at 09:10 Europe/Paris using the MobilityData GTFS-RT validator.

Errors

stop_times_updates not strictly sorted E002 11 errors

stop_time_updates for a given trip_id must be strictly sorted by increasing stop_sequence

Sample errors

trip_id 87060_250604-4288 stop_sequence [0, 0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 13, 14] is not strictly sorted by increasing stop_sequence
trip_id 87058_250604-4288 stop_sequence [0, 0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 13, 14] is not strictly sorted by increasing stop_sequence
trip_id 87096_250604-4290 stop_sequence [0, 0, 16, 19, 20] is not strictly sorted by increasing stop_sequence
trip_id 87094_250604-4290 stop_sequence [0, 0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 19, 20] is not strictly sorted by increasing stop_sequence
trip_id 87095_250604-4300 stop_sequence [0, 0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 19, 20] is not strictly sorted by increasing stop_sequence

GTFS-rt trip_id does not exist in GTFS data and does not have schedule_relationship of ADDED E003 109 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 68616_250604-4281 does not exist in the GTFS data and does not have schedule_relationship of ADDED
trip_id 68631_250604-4281 does not exist in the GTFS data and does not have schedule_relationship of ADDED
trip_id 87106_250604-4287 does not exist in the GTFS data and does not have schedule_relationship of ADDED
trip_id 87060_250604-4288 does not exist in the GTFS data and does not have schedule_relationship of ADDED
trip_id 87036_250604-4288 does not exist in the GTFS data and does not have schedule_relationship of ADDED

Sequential stop_time_update times are not increasing E022 44 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 87060_250604-4288 stop_sequence 1 arrival_time 09:10:00 (1749021000) is less than previous stop arrival_time 09:34:41 (1749022481) - times must increase between two sequential stops
trip_id 87060_250604-4288 stop_sequence 1 arrival_time 09:10:00 (1749021000) is less than previous stop departure_time 09:34:41 (1749022481) - times must increase between two sequential stops
trip_id 87060_250604-4288 stop_sequence 1 departure_time 09:10:00 (1749021000) is less than previous stop departure_time 09:34:41 (1749022481) - times must increase between two sequential stops
trip_id 87060_250604-4288 stop_sequence 1 departure_time 09:10:00 (1749021000) is less than previous stop arrival_time 09:34:41 (1749022481) - times must increase between two sequential stops
trip_id 87058_250604-4288 stop_sequence 1 arrival_time 10:10:00 (1749024600) is less than previous stop arrival_time 10:34:41 (1749026081) - times must increase between two sequential stops

Sequential stop_time_updates have the same stop_sequence E036 11 errors

Sequential GTFS-rt trip stop_time_updates should never have the same stop_sequence

Sample errors

trip_id 87060_250604-4288 has repeating stop_sequence 0 - stop_sequence must increase for each stop_time_update
trip_id 87058_250604-4288 has repeating stop_sequence 0 - stop_sequence must increase for each stop_time_update
trip_id 87096_250604-4290 has repeating stop_sequence 0 - stop_sequence must increase for each stop_time_update
trip_id 87094_250604-4290 has repeating stop_sequence 0 - stop_sequence must increase for each stop_time_update
trip_id 87095_250604-4300 has repeating stop_sequence 0 - stop_sequence must increase for each stop_time_update

Warnings

timestamp not populated W001 109 errors

Timestamps should be populated for all elements

Sample errors

trip_id 68616_250604-4281 does not have a timestamp
trip_id 68631_250604-4281 does not have a timestamp
trip_id 87106_250604-4287 does not have a timestamp
trip_id 87060_250604-4288 does not have a timestamp
trip_id 87036_250604-4288 does not have a timestamp

schedule_relationship not populated W009 109 errors

trip.schedule_relationship and stop_time_update.schedule_relationship should be populated

Sample errors

trip_id 68616_250604-4281 stop_sequence 1 (and potentially more for this trip) does not have a schedule_relationship
trip_id 68631_250604-4281 stop_sequence 1 (and potentially more for this trip) does not have a schedule_relationship
trip_id 87106_250604-4287 stop_sequence 14 (and potentially more for this trip) does not have a schedule_relationship
trip_id 87060_250604-4288 stop_sequence 0 (and potentially more for this trip) does not have a schedule_relationship
trip_id 87036_250604-4288 stop_sequence 1 (and potentially more for this trip) does not have a schedule_relationship

Validate this GTFS-RT now

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.	1 520	26 times (100 % of validations)
W001	Timestamps should be populated for all elements	2 565	26 times (100 % of validations)
W009	trip.schedule_relationship and stop_time_update.schedule_relationship should be populated	2 564	26 times (100 % of validations)
E051	All stop_time_update stop_sequences in GTFS-realtime data must appear in GTFS stop_times.txt for that trip	363	24 times (92 % of validations)
E002	stop_time_updates for a given trip_id must be strictly sorted by increasing stop_sequence	24	2 times (8 % of validations)
E003	All trip_ids provided in the GTFS-rt feed must exist in the GTFS data, unless the schedule_relationship is ADDED	222	2 times (8 % of validations)
E036	Sequential GTFS-rt trip stop_time_updates should never have the same stop_sequence	24	2 times (8 % of validations)

GTFS-RT feed content

Entities

Entities present in this feed at 2025-06-05 at 00:48 Europe/Paris.

vehicle_positions (0) service_alerts (0) trip_updates (0)

Entities seen in the last 7 days.

trip_updates

Decoded GTFS-RT feed

See full payload

Here is the decoded GTFS-RT feed Protobuf at 2025-06-05 at 00:48 Europe/Paris. You can look at the GTFS-RT documentation.


{
  "header": {
    "gtfsRealtimeVersion": "2.0",
    "timestamp": "1749077308"
  }
}