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

⚠️216 warnings

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

Warnings

timestamp not populated W001 108 errors

Timestamps should be populated for all elements

Sample errors

trip_id 96191_260409-6382 does not have a timestamp
trip_id 96201_260409-6382 does not have a timestamp
trip_id 96192_260409-6382 does not have a timestamp
trip_id 96231_260409-6391 does not have a timestamp
trip_id 96241_260409-6391 does not have a timestamp

schedule_relationship not populated W009 108 errors

trip.schedule_relationship and stop_time_update.schedule_relationship should be populated

Sample errors

trip_id 96191_260409-6382 stop_sequence 1 (and potentially more for this trip) does not have a schedule_relationship
trip_id 96201_260409-6382 stop_sequence 1 (and potentially more for this trip) does not have a schedule_relationship
trip_id 96192_260409-6382 stop_sequence 1 (and potentially more for this trip) does not have a schedule_relationship
trip_id 96231_260409-6391 stop_sequence 13 (and potentially more for this trip) does not have a schedule_relationship
trip_id 96241_260409-6391 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
W001	Timestamps should be populated for all elements	3,277	30 times (100 % of validations)
W009	trip.schedule_relationship and stop_time_update.schedule_relationship should be populated	3,277	30 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.	88	11 times (37 % of validations)
E051	All stop_time_update stop_sequences in GTFS-realtime data must appear in GTFS stop_times.txt for that trip	22	11 times (37 % of validations)
E003	All trip_ids provided in the GTFS-rt feed must exist in the GTFS data, unless the schedule_relationship is ADDED	161	2 times (7 % of validations)

GTFS-RT feed content

Entities

Entities present in this feed at 2026-04-10 at 00:56 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 2026-04-10 at 00:56 Europe/Paris. You can look at the GTFS-RT documentation.


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