Resource details

File name: données mobilité - Ligne St Tropez
Format: gtfs-rt

Données mobilité GTFS-RT Saint Tropez

This resource file is part of the dataset Réseau urbain Navette Saint-Tropez.

Download availability

2025-08-23
100%
2025-08-24
99.5%
2025-08-25
99.7%
2025-08-26
99.6%
2025-08-27
99.5%
2025-08-28
99.5%
2025-08-29
99.6%
2025-08-30
99.6%
2025-08-31
100%
2025-09-01
100%
2025-09-02
100%
2025-09-03
99.5%
2025-09-04
99.6%
2025-09-05
99.5%
2025-09-06
100%
2025-09-07
98.8%
2025-09-08
99.6%
2025-09-09
99.5%
2025-09-10
99.5%
2025-09-11
99.5%
2025-09-12
99.5%
2025-09-13
100%
2025-09-14
99.4%
2025-09-15
100%
2025-09-16
99.5%
2025-09-17
99.4%
2025-09-18
99.5%
2025-09-19
99.5%
2025-09-20
100%
2025-09-21
98.7%
2025-09-22
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

19 errors

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

Errors

GTFS-rt stop_id does not exist in GTFS data E011 9 errors

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

Sample errors
  • vehicle_id 96ba71e88e101538 stop_id Place des Lices does not exist in GTFS data stops.txt
  • trip_id 2 stop_id Place des Lices does not exist in GTFS data stops.txt
  • trip_id 2 stop_id Plage des Salins does not exist in GTFS data stops.txt
  • trip_id 2 stop_id Etang des Salins does not exist in GTFS data stops.txt
  • trip_id 2 stop_id Capon Pinet does not exist in GTFS data stops.txt

Sequential stop_time_update times are not increasing E022 2 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 2 stop_sequence 35 arrival_time 08:59:38 (1758524378) is less than previous stop arrival_time 10:40:00 (1758530400) - times must increase between two sequential stops
  • trip_id 2 stop_sequence 35 arrival_time 08:59:38 (1758524378) is less than previous stop departure_time 10:40:00 (1758530400) - times must increase between two sequential stops

GTFS-rt stop_time_update stop_sequence and stop_id do not match GTFS E045 8 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 2 stop_sequence 0 has stop_id Place des Lices but GTFS stop_sequence 0 has stop_id Place des Lices - stop_ids should be the same
  • GTFS-rt trip_id 2 stop_sequence 18 has stop_id Plage des Salins but GTFS stop_sequence 18 has stop_id Plage des Salins - stop_ids should be the same
  • GTFS-rt trip_id 2 stop_sequence 19 has stop_id Etang des Salins but GTFS stop_sequence 19 has stop_id Etang des Salins - stop_ids should be the same
  • GTFS-rt trip_id 2 stop_sequence 29 has stop_id Capon Pinet but GTFS stop_sequence 29 has stop_id Capon Pinet - stop_ids should be the same
  • GTFS-rt trip_id 2 stop_sequence 32 has stop_id La Messardière but GTFS stop_sequence 32 has stop_id La Messardière - stop_ids should be the same
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 93 12 times (40 % 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 86 12 times (40 % of validations)
E022 stop_time_update arrival/departure times between sequential stops should always increase - they should never be the same or decrease. 10 5 times (17 % 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)

GTFS-RT feed content

Entities

Entities present in this feed at 2025-09-22 at 18:37 Europe/Paris.

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

Entities seen in the last 7 days.

service_alerts trip_updates vehicle_positions

Service alerts

Here is a display of service alerts contained in this feed at 2025-09-22 at 18:37 Europe/Paris.

Ligne 1 - Course 14h15 et 16h00 supprimées Modified service

Les Courses de  14h15 et 16h00 sont supprimées

Decoded GTFS-RT feed

See full payload

Here is the decoded GTFS-RT feed Protobuf at 2025-09-22 at 18:37 Europe/Paris. You can look at the GTFS-RT documentation.

{ "entity": [ { "alert": { "cause": "OTHER_CAUSE", "descriptionText": { "translation": [ { "text": "Les Courses de  14h15 et 16h00 sont supprimées" } ] }, "effect": "MODIFIED_SERVICE", "headerText": { "translation": [ { "text": "Ligne 1 - Course 14h15 et 16h00 supprimées" } ] }, "informedEntity": [ { "routeId": "L1" } ] }, "id": "alert:68d13076f0eb2a279b2779a5" } ], "header": { "gtfsRealtimeVersion": "2.0", "timestamp": "1758559052" } }