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

2026-03-03
99.4%
2026-03-04
99.3%
2026-03-05
97.9%
2026-03-06
97.9%
2026-03-08
99.1%
2026-03-09
99.1%
2026-03-10
97.9%
2026-03-11
97.9%
2026-03-12
98.4%
2026-03-13
97.9%
2026-03-14
99.1%
2026-03-15
97.2%
2026-03-16
98.3%
2026-03-17
99.1%
2026-03-20
89.9%
2026-03-26
99.4%
2026-03-31
99.4%
2026-04-02
99.1%
2026-03-18
100%
2026-03-23
100%
2026-03-22
100%
2026-03-29
100%
2026-03-19
100%
2026-03-21
100%
2026-03-07
100%
2026-03-30
100%
2026-03-25
100%
2026-04-01
100%
2026-03-24
100%
2026-03-28
100%
2026-03-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-04-02 at 19:38 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-04-02 at 19:38 Europe/Paris. You can look at the GTFS-RT documentation.

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