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

Resource details

Format: gtfs-rt

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

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

❌1 621 errors

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

Errors

GTFS-rt trip_id does not exist in GTFS data and does not have schedule_relationship of ADDED E003 56 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 3840340-B-PS-2324B-10SA-Samedi-0 does not exist in the GTFS data and does not have schedule_relationship of ADDED
trip_id 3840339-B-PS-2324B-10SA-Samedi-0 does not exist in the GTFS data and does not have schedule_relationship of ADDED
trip_id 3840374-B-PS-2324B-10SA-Samedi-0 does not exist in the GTFS data and does not have schedule_relationship of ADDED
trip_id 3840403-B-PS-2324B-11SA-Samedi-0 does not exist in the GTFS data and does not have schedule_relationship of ADDED
trip_id 3840436-B-PS-2324B-11SA-Samedi-0 does not exist in the GTFS data and does not have schedule_relationship of ADDED

GTFS-rt route_id does not exist in GTFS data E004 56 errors

All route_ids provided in the GTFS-rt feed must exist in the GTFS data

Sample errors

route_id 10 does not exist in the GTFS data routes.txt
route_id 10 does not exist in the GTFS data routes.txt
route_id 10 does not exist in the GTFS data routes.txt
route_id 11 does not exist in the GTFS data routes.txt
route_id 11 does not exist in the GTFS data routes.txt

GTFS-rt stop_id does not exist in GTFS data E011 1 403 errors

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

Sample errors

trip_id 3840340-B-PS-2324B-10SA-Samedi-0 stop_id 2623 does not exist in GTFS data stops.txt
trip_id 3840340-B-PS-2324B-10SA-Samedi-0 stop_id 2542 does not exist in GTFS data stops.txt
trip_id 3840340-B-PS-2324B-10SA-Samedi-0 stop_id 2601 does not exist in GTFS data stops.txt
trip_id 3840340-B-PS-2324B-10SA-Samedi-0 stop_id 3074 does not exist in GTFS data stops.txt
trip_id 3840340-B-PS-2324B-10SA-Samedi-0 stop_id 2201 does not exist in GTFS data stops.txt

Sequential stop_time_update times are not increasing E022 106 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 3840340-B-PS-2324B-10SA-Samedi-0 stop_id 2030 arrival_time 09:27:21 (1717226841) is less than previous stop arrival_time 09:27:28 (1717226848) - times must increase between two sequential stops
trip_id 3840340-B-PS-2324B-10SA-Samedi-0 stop_id 2030 arrival_time 09:27:21 (1717226841) is less than previous stop departure_time 09:27:28 (1717226848) - times must increase between two sequential stops
trip_id 3840340-B-PS-2324B-10SA-Samedi-0 stop_id 2030 departure_time 09:27:21 (1717226841) is less than previous stop departure_time 09:27:28 (1717226848) - times must increase between two sequential stops
trip_id 3840340-B-PS-2324B-10SA-Samedi-0 stop_id 2030 departure_time 09:27:21 (1717226841) is less than previous stop arrival_time 09:27:28 (1717226848) - times must increase between two sequential stops
trip_id 3840339-B-PS-2324B-10SA-Samedi-0 stop_id 2839 arrival_time 09:12:16 (1717225936) is equal to previous stop arrival_time 09:12:16 (1717225936) - times must increase between two sequential stops

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
E003	All trip_ids provided in the GTFS-rt feed must exist in the GTFS data, unless the schedule_relationship is ADDED	1 286	19 times (68 % of validations)
E004	All route_ids provided in the GTFS-rt feed must exist in the GTFS data	1 292	19 times (68 % of validations)
E011	All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt	31 595	19 times (68 % of validations)
E022	stop_time_update arrival/departure times between sequential stops should always increase - they should never be the same or decrease.	1 854	19 times (68 % of validations)
W002	vehicle_id should be populated for TripUpdates and VehiclePositions	39	13 times (46 % of validations)
E037	Sequential GTFS-rt trip stop_time_updates shouldn't have the same stop_id	22	1 times (4 % of validations)

GTFS-RT feed content

Entities

Entities present in this feed at 2024-06-02 at 04:41 Europe/Paris.

service_alerts (0) trip_updates (0) vehicle_positions (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 2024-06-02 at 04:41 Europe/Paris. You can look at the GTFS-RT documentation.


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