Resource details

File name: Données ligne estivale La Croix Valmer
Format: gtfs-rt

This resource file is part of the dataset Réseau urbain La Croix Valmer.

Download availability

2025-12-28
95.4%
2025-12-29
91.7%
2025-12-30
93.5%
2025-12-31
95.3%
2026-01-01
94.6%
2026-01-02
94.9%
2026-01-03
98.1%
2026-01-04
95%
2026-01-05
84.4%
2026-01-06
84.2%
2026-01-07
84.7%
2026-01-08
89.2%
2026-01-09
45.5%
2026-01-10
98.8%
2026-01-11
87.9%
2026-01-12
85.3%
2026-01-13
78.1%
2026-01-14
97.2%
2026-01-15
97.9%
2026-01-16
97.3%
2026-01-17
97.9%
2026-01-18
97.9%
2026-01-19
97.9%
2026-01-20
97.8%
2026-01-21
97.9%
2026-01-22
98.4%
2026-01-23
99.6%
2026-01-24
99.5%
2026-01-25
98.3%
2026-01-26
98.2%
2026-01-27
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

3 errors, 2 warnings

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

Errors

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 11 arrival_time 08:30:30 (1759213830) is less than previous stop departure_time 08:30:39 (1759213839) - times must increase between two sequential stops
  • trip_id 1 stop_sequence 11 departure_time 08:30:30 (1759213830) is less than previous stop departure_time 08:30:39 (1759213839) - times must increase between two sequential stops

VehiclePosition and TripUpdate ID pairing mismatch E047 1 error

If separate `VehiclePositions` and `TripUpdates` feeds are provided, `VehicleDescriptor` or `TripDescriptor` ID value pairing should match between the two feeds.

Sample errors
  • trip_id BASSE2 and vehicle_id 683afc1157e9bc33c08c9bb5 pairing in VehiclePositions does not match trip_id 1 and vehicle_id 683afc1157e9bc33c08c9bb5 pairing in TripUpdates feed and trip block_ids aren't the same - ID pairing between feeds should match

Warnings

ID in one feed missing from the other W003 2 errors

a trip_id that is provided in the VehiclePositions feed should be provided in the TripUpdates feed, and a vehicle_id that is provided in the TripUpdates feed should be provided in the VehiclePositions feed

Sample errors
  • trip_id 1 is in TripUpdates but not in VehiclePositions feed
  • trip_id BASSE is in TripUpdates but not in VehiclePositions feed
Validate this GTFS-RT now

GTFS-RT feed content

Entities

Entities present in this feed at 2026-01-27 at 16:27 Europe/Paris.

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

Decoded GTFS-RT feed

See full payload

Here is the decoded GTFS-RT feed Protobuf at 2026-01-27 at 16:27 Europe/Paris. You can look at the GTFS-RT documentation.

{ "header": { "gtfsRealtimeVersion": "2.0", "timestamp": "1769527633" } }