Resource details

File name: Position des véhicules des lignes 26 et 530 du réseau Astuce exploitées par TNI
Format: gtfs-rt

Ce fichier au format GTFS-RT (protobuf) contient la position des véhicules (vehicle position) pour les lignes 26 et 530 du réseau Astuce exploitées par TNI.

La position des véhicules est rafraîchie à chaque évènement qui se produit sur la course ou, au plus tard, toutes les 3 minutes (message de vie).

Afin de pouvoir réutiliser ces données, il est nécessaire de faire le lien avec le GTFS spécifique à TNI (ressource disponible via ce même jeu de données) et non le GTFS global du réseau Astuce disponible par ailleurs.

This resource file is part of the dataset Réseau urbain Astuce - lignes 26 et 530 (temps-réel).

Download availability

2025-03-16
100%
2025-03-17
100%
2025-03-18
100%
2025-03-19
100%
2025-03-20
100%
2025-03-21
100%
2025-03-22
100%
2025-03-23
100%
2025-03-24
100%
2025-03-25
100%
2025-03-26
100%
2025-03-27
100%
2025-03-28
100%
2025-03-29
100%
2025-03-30
100%
2025-03-31
100%
2025-04-01
100%
2025-04-02
100%
2025-04-03
100%
2025-04-04
100%
2025-04-05
100%
2025-04-06
100%
2025-04-07
100%
2025-04-08
100%
2025-04-09
100%
2025-04-10
100%
2025-04-11
100%
2025-04-12
100%
2025-04-13
100%
2025-04-14
100%
2025-04-15
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. In case of HTTP 500, the feed will be considered unavailable, unless the body appears to contain SOAP.

Validation details

No error detected

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

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
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. 2 2 times (7 % of validations)
E035 The GTFS-rt trip.trip_id should belong to the specified trip.route_id in GTFS trips.txt 1 1 times (3 % of validations)

GTFS-RT feed content

Entities

Entities present in this feed at 2025-04-15 at 15:12 Europe/Paris.

vehicle_positions (2) 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 2025-04-15 at 15:12 Europe/Paris. You can look at the GTFS-RT documentation.

{ "entity": [ { "id": "4275", "vehicle": { "position": { "bearing": 66.0, "latitude": 49.48162078857422, "longitude": 0.877269446849823 }, "timestamp": "1744722706", "trip": { "route_id": "530", "schedule_relationship": "SCHEDULED", "trip_id": "155" }, "vehicle": { "id": "0200001002FF8218", "label": "7602" } } }, { "id": "4276", "vehicle": { "position": { "bearing": 261.0, "latitude": 49.44940185546875, "longitude": 1.0627694129943848 }, "timestamp": "1744722708", "trip": { "route_id": "26", "schedule_relationship": "SCHEDULED", "trip_id": "165" }, "vehicle": { "id": "0200001002FF7E0B", "label": "7605" } } } ], "header": { "gtfs_realtime_version": "2.0", "timestamp": "1744722753" } }