Resource details
Données mobilité GTFS-RT Saint Tropez
This resource file is part of the dataset Réseau urbain Navette Saint-Tropez.
Download availability
Learn more
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
❌11 errors
Validation carried out using the current GTFS file and the GTFS-RT the 2025-12-24 at 08:00 Europe/Paris using the MobilityData GTFS-RT validator.
Errors
GTFS-rt stop_id does not exist in GTFS data E011 5 errors
All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt
Sample errors
- vehicle_id 650d5ff63e8b2a90d30589d2 stop_id Place des Lices does not exist in GTFS data stops.txt
- trip_id 1 stop_id Place des Lices does not exist in GTFS data stops.txt
- trip_id 1 stop_id Plage des Salins does not exist in GTFS data stops.txt
- trip_id 1 stop_id Etang des Salins does not exist in GTFS data stops.txt
- trip_id 1 stop_id Place des Lices 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 1 stop_sequence 29 arrival_time 07:52:37 (1766559157) is less than previous stop arrival_time 08:31:50 (1766561510) - times must increase between two sequential stops
- trip_id 1 stop_sequence 29 arrival_time 07:52:37 (1766559157) is less than previous stop departure_time 08:31:50 (1766561510) - times must increase between two sequential stops
GTFS-rt stop_time_update stop_sequence and stop_id do not match GTFS E045 4 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 1 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 1 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 1 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 1 stop_sequence 29 has stop_id Place des Lices but GTFS stop_sequence 29 has stop_id Place des Lices - stop_ids should be the same
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 | 85 | 20 times (67 % 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 | 80 | 20 times (67 % of validations) |
| E022 | stop_time_update arrival/departure times between sequential stops should always increase - they should never be the same or decrease. | 16 | 8 times (27 % 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-12-25 at 01:38 Europe/Paris.
vehicle_positions (0) service_alerts (0) trip_updates (0)Entities seen in the last 7 days.
trip_updates vehicle_positionsDecoded GTFS-RT feed
See full payload
Here is the decoded GTFS-RT feed Protobuf at 2025-12-25 at 01:38 Europe/Paris. You can look at the GTFS-RT documentation.
{
"header": {
"gtfsRealtimeVersion": "2.0",
"timestamp": "1766623090"
}
}