Resource details

Format: gtfs-rt

Données position des véhicules en temps réel, au format GTFS-RT PROTOBUF, du réseau Corolis (urbain)

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

Download availability

2024-04-20
100%
2024-04-21
21.1%
2024-04-22
0%
2024-04-23
0%
2024-04-24
45.1%
2024-04-25
100%
2024-04-26
100%
2024-04-27
100%
2024-04-28
100%
2024-04-29
100%
2024-04-30
100%
2024-05-01
100%
2024-05-02
100%
2024-05-03
100%
2024-05-04
100%
2024-05-05
100%
2024-05-06
100%
2024-05-07
100%
2024-05-08
100%
2024-05-09
100%
2024-05-10
100%
2024-05-11
100%
2024-05-12
100%
2024-05-13
100%
2024-05-14
100%
2024-05-15
100%
2024-05-16
100%
2024-05-17
100%
2024-05-18
100%
2024-05-19
100%
2024-05-20
100%
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

⚠️4 warnings

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

Warnings

schedule_relationship not populated W009 4 errors

trip.schedule_relationship and stop_time_update.schedule_relationship should be populated

Sample errors
  • trip_id 8001-S08D1-______D does not have a schedule_relationship
  • trip_id 1049-JC1D1-______D does not have a schedule_relationship
  • trip_id 2047 does not have a schedule_relationship
  • trip_id 6011-C06D1-______D 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
W009 trip.schedule_relationship and stop_time_update.schedule_relationship should be populated 484 25 times (96 % 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. 48 22 times (85 % of validations)
W008 The data in a GTFS-realtime feed should always be less than one minute old 1 1 times (4 % of validations)

GTFS-RT feed content

Entities

Entities present in this feed at 2024-05-20 at 06:49 Europe/Paris.

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

Entities seen in the last 7 days.

vehicle_positions

Decoded GTFS-RT feed

See full payload

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

{ "entity": [ { "id": "VM:9004-MNAV-______D", "vehicle": { "current_status": "IN_TRANSIT_TO", "current_stop_sequence": 3, "position": { "bearing": 95.0, "latitude": 49.45985794067383, "longitude": 2.1084277629852295 }, "stop_id": "BKENN1", "timestamp": "1716180568", "trip": { "direction_id": 1, "route_id": "NA", "trip_id": "9004-MNAV-______D" }, "vehicle": { "id": "TBM30003" } } } ], "header": { "gtfs_realtime_version": "1.0", "timestamp": "1716180570" } }