gtfs-rt Transport open dataset - GTFS RT Proxim iTi for Réseau urbain Proxim iTi

Resource details

Format: gtfs-rt

This resource file is part of the dataset Réseau urbain Proxim iTi.

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.

Validation details

❌518 errors

Validation carried out using the current GTFS file and the GTFS-RT the 2024-05-06 at 09:00 Europe/Paris using the MobilityData GTFS-RT validator.

Errors

stop_times_updates not strictly sorted E002 10 errors

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

Sample errors

trip_id 0_0_156 stop_sequence [0, 1, 2, 3, 4, 5, 6, 7, 7] is not strictly sorted by increasing stop_sequence
trip_id 0_1_2 stop_sequence [0, 1, 2, 3, 4, 4] is not strictly sorted by increasing stop_sequence
trip_id 0_1_18 stop_sequence [0, 1, 3, 4, 5, 6, 6] is not strictly sorted by increasing stop_sequence
trip_id 1_0_20 stop_sequence [1, 2, 4, 6, 8, 9, 10, 11, 11] is not strictly sorted by increasing stop_sequence
trip_id 0_0_222 stop_sequence [0, 1, 2, 2] is not strictly sorted by increasing stop_sequence

GTFS-rt stop_id does not exist in GTFS data E011 1 error

All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt

Sample errors

trip_id 0_0_237 stop_id FAUCIGNY - CHEZ LES BEL 1 does not exist in GTFS data stops.txt

Sequential stop_time_update times are not increasing E022 476 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_0_156 stop_sequence 7 arrival_time 09:03:00 (1714978980) is equal to previous stop arrival_time 09:03:00 (1714978980) - times must increase between two sequential stops
trip_id 0_0_156 stop_sequence 7 arrival_time 09:03:00 (1714978980) is equal to previous stop departure_time 09:03:00 (1714978980) - times must increase between two sequential stops
trip_id 0_0_156 stop_sequence 7 departure_time 09:03:00 (1714978980) is equal to previous stop departure_time 09:03:00 (1714978980) - times must increase between two sequential stops
trip_id 0_0_156 stop_sequence 7 departure_time 09:03:00 (1714978980) is equal to previous stop arrival_time 09:03:00 (1714978980) - times must increase between two sequential stops
trip_id 0_0_156 stop_sequence 8 arrival_time 09:07:00 (1714979220) is equal to previous stop arrival_time 09:07:00 (1714979220) - times must increase between two sequential stops

Sequential stop_time_updates have the same stop_sequence E036 10 errors

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

Sample errors

trip_id 0_0_156 has repeating stop_sequence 7 - stop_sequence must increase for each stop_time_update
trip_id 0_1_2 has repeating stop_sequence 4 - stop_sequence must increase for each stop_time_update
trip_id 0_1_18 has repeating stop_sequence 6 - stop_sequence must increase for each stop_time_update
trip_id 1_0_20 has repeating stop_sequence 11 - stop_sequence must increase for each stop_time_update
trip_id 0_0_222 has repeating stop_sequence 2 - stop_sequence must increase for each stop_time_update

Sequential stop_time_updates have the same stop_id E037 10 errors

Sequential GTFS-rt trip stop_time_updates shouldn't have the same stop_id

Sample errors

trip_id 0_0_156 has repeating stop_id 41 at stop_sequence 7 - sequential stop_ids should be different
trip_id 0_1_2 has repeating stop_id 313 at stop_sequence 4 - sequential stop_ids should be different
trip_id 0_1_18 has repeating stop_id 30 at stop_sequence 6 - sequential stop_ids should be different
trip_id 1_0_20 has repeating stop_id 9 at stop_sequence 11 - sequential stop_ids should be different
trip_id 0_0_222 has repeating stop_id Stop_22 at stop_sequence 2 - sequential stop_ids should be different

GTFS-rt stop_time_update stop_sequence and stop_id do not match GTFS E045 1 error

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_0_237 stop_sequence 13 has stop_id FAUCIGNY - CHEZ LES BEL 1 but GTFS stop_sequence 13 has stop_id FAUCIGNY - CHEZ LES BEL 1 - stop_ids should be the same

GTFS-rt stop_sequence not found in GTFS data E051 10 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 0_0_156 contains stop_sequence 7 that does not exist in GTFS stop_times.txt for this trip
GTFS-rt trip_id 0_1_2 contains stop_sequence 4 that does not exist in GTFS stop_times.txt for this trip
GTFS-rt trip_id 0_1_18 contains stop_sequence 6 that does not exist in GTFS stop_times.txt for this trip
GTFS-rt trip_id 1_0_20 contains stop_sequence 11 that does not exist in GTFS stop_times.txt for this trip
GTFS-rt trip_id 0_0_222 contains stop_sequence 2 that does not exist in GTFS stop_times.txt for this trip

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
E011	All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt	18	18 times (60 % 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	18	18 times (60 % of validations)
E022	stop_time_update arrival/departure times between sequential stops should always increase - they should never be the same or decrease.	5 622	14 times (47 % of validations)
E002	stop_time_updates for a given trip_id must be strictly sorted by increasing stop_sequence	127	13 times (43 % of validations)
E036	Sequential GTFS-rt trip stop_time_updates should never have the same stop_sequence	127	13 times (43 % of validations)
E037	Sequential GTFS-rt trip stop_time_updates shouldn't have the same stop_id	127	13 times (43 % of validations)
E051	All stop_time_update stop_sequences in GTFS-realtime data must appear in GTFS stop_times.txt for that trip	127	13 times (43 % 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.	3	3 times (10 % of validations)
E029	The vehicle position should be within a certain distance of the GTFS shapes.txt data for the current trip unless there is a Service Alert with the Effect of DETOUR for this trip_id.	1	1 times (3 % of validations)
E047	If separate `VehiclePositions` and `TripUpdates` feeds are provided, `VehicleDescriptor` or `TripDescriptor` ID value pairing should match between the two feeds.	1	1 times (3 % of validations)
W003	a trip_id that is provided in the VehiclePositions feed should be provided in the TripUpdates feed, and a vehicle_id that is provided in the TripUpdates feed should be provided in the VehiclePositions feed	1	1 times (3 % of validations)

GTFS-RT feed content

Entities

Entities present in this feed at 2024-05-06 at 23:07 Europe/Paris.

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

Entities seen in the last 7 days.

trip_updates vehicle_positions

Decoded GTFS-RT feed

See full payload

Here is the decoded GTFS-RT feed Protobuf at 2024-05-06 at 23:07 Europe/Paris. You can look at the GTFS-RT documentation.


{
  "header": {
    "gtfs_realtime_version": "2.0",
    "timestamp": "1715029652"
  }
}