gtfs-rt Transport open dataset - Réseau Alternéo - RT - service Trip Update for Réseau urbain Alternéo - CA CIVIS (Communauté Intercommunale des Villes Solidaires)

Resource details

File name: Réseau Alternéo - RT - service Trip Update

Format: gtfs-rt

Flux GTFS-RT service Trip Update

This resource file is part of the dataset Réseau urbain Alternéo.

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

❌150 errors, 180 warnings

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

Errors

stop_times_updates not strictly sorted E002 2 errors

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

Sample errors

trip_id 0_61051550 stop_sequence [3, 4, 5, 6, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 23, 24, 25, 26, 27, 28, 29, 30, 31, 32, 33, 34, 35, 36] is not strictly sorted by increasing stop_sequence
trip_id 0_61051540 stop_sequence [3, 4, 5, 6, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 23, 24, 25, 26, 27, 28, 29, 30, 31, 32, 33, 34, 35, 36] is not strictly sorted by increasing stop_sequence

GTFS-rt stop_sequence isn't provided for trip that visits same stop_id more than once E009 2 errors

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

Sample errors

trip_id 0_61051623 visits stop_id [0:17800C, 0:05343C] more than once and GTFS-rt stop_time_update is missing stop_sequence field - stop_sequence must be provided
trip_id 0_61051629 visits stop_id [0:17800C, 0:05343C] more than once and GTFS-rt stop_time_update is missing stop_sequence field - stop_sequence must be provided

Sequential stop_time_update times are not increasing E022 70 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_61052300 stop_sequence 2 arrival_time 10:29:32 (1786170572) is equal to previous stop departure_time 10:29:32 (1786170572) - times must increase between two sequential stops
trip_id 0_61052300 stop_sequence 2 departure_time 10:29:32 (1786170572) is equal to previous stop departure_time 10:29:32 (1786170572) - times must increase between two sequential stops
trip_id 0_61052300 stop_sequence 24 arrival_time 10:49:33 (1786171773) is equal to previous stop arrival_time 10:49:33 (1786171773) - times must increase between two sequential stops
trip_id 0_61052300 stop_sequence 24 arrival_time 10:49:33 (1786171773) is equal to previous stop departure_time 10:49:33 (1786171773) - times must increase between two sequential stops
trip_id 0_61052300 stop_sequence 24 departure_time 10:49:33 (1786171773) is equal to previous stop departure_time 10:49:33 (1786171773) - times must increase between two sequential stops

GTFS-rt stop_time_update stop_sequence and stop_id do not match GTFS E045 76 errors

If GTFS-rt stop_time_update contains both stop_sequence and stop_id, the values must match the GTFS data in stop_times.txt

Sample errors

GTFS-rt trip_id 0_61051502 stop_sequence 10 has stop_id 0:04030C but GTFS stop_sequence 10 has stop_id 0:13010C - stop_ids should be the same
GTFS-rt trip_id 0_61051502 stop_sequence 11 has stop_id 0:04040C but GTFS stop_sequence 11 has stop_id 0:13020C - stop_ids should be the same
GTFS-rt trip_id 0_61051502 stop_sequence 12 has stop_id 0:04050C but GTFS stop_sequence 12 has stop_id 0:13030C - stop_ids should be the same
GTFS-rt trip_id 0_61051502 stop_sequence 13 has stop_id 0:04060C but GTFS stop_sequence 13 has stop_id 0:04050C - stop_ids should be the same
GTFS-rt trip_id 0_61051502 stop_sequence 14 has stop_id 0:04070C but GTFS stop_sequence 14 has stop_id 0:04060C - stop_ids should be the same

Warnings

timestamp not populated W001 111 errors

Timestamps should be populated for all elements

Sample errors

trip_id 0_61052300 does not have a timestamp
trip_id 0_61052301 does not have a timestamp
trip_id 0_61052553 does not have a timestamp
trip_id 0_61052548 does not have a timestamp
trip_id 0_61052509 does not have a timestamp

vehicle_id not populated W002 69 errors

vehicle_id should be populated for TripUpdates and VehiclePositions

Sample errors

trip_id 0_61052301 does not have a vehicle_id
trip_id 0_61052553 does not have a vehicle_id
trip_id 0_61052509 does not have a vehicle_id
trip_id 0_61052323 does not have a vehicle_id
trip_id 0_61051673 does not have a vehicle_id

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
E002	stop_time_updates for a given trip_id must be strictly sorted by increasing stop_sequence	112	29 times (100 % 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	61	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.	3,623	29 times (100 % of validations)
W001	Timestamps should be populated for all elements	2,863	29 times (100 % of validations)
W002	vehicle_id should be populated for TripUpdates and VehiclePositions	1,839	29 times (100 % of validations)
E045	If GTFS-rt stop_time_update contains both stop_sequence and stop_id, the values must match the GTFS data in stop_times.txt	1,292	24 times (83 % of validations)
E037	Sequential GTFS-rt trip stop_time_updates shouldn't have the same stop_id	6	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.	1	1 times (3 % of validations)
W008	The data in a GTFS-realtime feed should always be less than one minute old	1	1 times (3 % of validations)

GTFS-RT feed content

Entities

Entities present in this feed at 2026-08-08 at 23:18 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-08-08 at 23:18 Europe/Paris. You can look at the GTFS-RT documentation.


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