Resource details
Ce lien fournit les mises à jour en temps réel par rapport au référentiel gtfs-navineo.zip
This resource file is part of the dataset Réseau urbain TCAT.
Related resources
gtfs-navineo.zip
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
❌95 errors, 164 warnings
Validation carried out using the current GTFS file and the GTFS-RT the 2025-09-29 at 09:13 Europe/Paris using the MobilityData GTFS-RT validator.
Errors
stop_times_updates not strictly sorted E002 6 errors
stop_time_updates for a given trip_id must be strictly sorted by increasing stop_sequence
Sample errors
- trip_id PS : Lu,Ma,Je,VeC1976349 stop_sequence [3, 1] is not strictly sorted by increasing stop_sequence
- trip_id PS : Lu,Ma,Je,VeC1977708 stop_sequence [23, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 23, 24, 25, 26, 27, 28, 29] is not strictly sorted by increasing stop_sequence
- trip_id PS : Lu,Ma,Je,VeC1977341 stop_sequence [1, 1] is not strictly sorted by increasing stop_sequence
- trip_id PS : Lu,Ma,Je,VeC1976356 stop_sequence [3, 1] is not strictly sorted by increasing stop_sequence
- trip_id PS : Lu,Ma,Je,VeC1976351 stop_sequence [3, 1] is not strictly sorted by increasing stop_sequence
Sequential stop_time_update times are not increasing E022 82 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 PS : Lu,Ma,Je,VeC1976529 stop_sequence 1 departure_time 09:48:00 (1759132080) is less than previous stop departure_time 10:04:17 (1759133057) - times must increase between two sequential stops
- trip_id PS : Lu,Ma,Je,VeC1976529 stop_sequence 1 departure_time 09:48:00 (1759132080) is less than previous stop arrival_time 10:04:17 (1759133057) - times must increase between two sequential stops
- trip_id PS : Lu,Ma,Je,VeC1976529 stop_sequence 2 arrival_time 09:49:35 (1759132175) is less than previous stop arrival_time 10:04:17 (1759133057) - times must increase between two sequential stops
- trip_id PS : Lu,Ma,Je,VeC1976529 stop_sequence 2 departure_time 09:49:35 (1759132175) is less than previous stop arrival_time 10:04:17 (1759133057) - times must increase between two sequential stops
- trip_id PS : Lu,Ma,Je,VeC1976349 stop_sequence 1 departure_time 09:27:00 (1759130820) is equal to previous stop departure_time 09:27:00 (1759130820) - times must increase between two sequential stops
Sequential stop_time_updates have the same stop_id E037 2 errors
Sequential GTFS-rt trip stop_time_updates shouldn't have the same stop_id
Sample errors
- trip_id PS : Lu,Ma,Je,VeC1977341 has repeating stop_id 0:Gar01 at stop_sequence 1 - sequential stop_ids should be different
- trip_id PS : Lu,Ma,Je,VeC1979750 has repeating stop_id 0:CAm01 - sequential stop_ids should be different
GTFS-rt stop_sequence not found in GTFS data E051 5 errors
All stop_time_update stop_sequences in GTFS-realtime data must appear in GTFS stop_times.txt for that trip
Sample errors
- GTFS-rt trip_id PS : Lu,Ma,Je,VeC1976349 contains stop_sequence 1 that does not exist in GTFS stop_times.txt for this trip
- GTFS-rt trip_id PS : Lu,Ma,Je,VeC1977341 contains stop_sequence 1 that does not exist in GTFS stop_times.txt for this trip
- GTFS-rt trip_id PS : Lu,Ma,Je,VeC1976356 contains stop_sequence 1 that does not exist in GTFS stop_times.txt for this trip
- GTFS-rt trip_id PS : Lu,Ma,Je,VeC1976351 contains stop_sequence 1 that does not exist in GTFS stop_times.txt for this trip
- GTFS-rt trip_id PS : Lu,Ma,Je,VeC1976347 contains stop_sequence 1 that does not exist in GTFS stop_times.txt for this trip
Warnings
timestamp not populated W001 104 errors
Timestamps should be populated for all elements
Sample errors
- trip_id PS : Lu,Ma,Je,VeC1976529 does not have a timestamp
- trip_id PS : Lu,Ma,Je,VeC1979408 does not have a timestamp
- trip_id PS : Lu,Ma,Je,VeC1978424 does not have a timestamp
- trip_id PS : Lu,Ma,Je,VeC1983918 does not have a timestamp
- trip_id PS : Lu,Ma,Je,VeC1979191 does not have a timestamp
vehicle_id not populated W002 60 errors
vehicle_id should be populated for TripUpdates and VehiclePositions
Sample errors
- trip_id PS : Lu,Ma,Je,VeC1976529 does not have a vehicle_id
- trip_id PS : Lu,Ma,Je,VeC1979408 does not have a vehicle_id
- trip_id PS : Lu,Ma,Je,VeC1983918 does not have a vehicle_id
- trip_id PS : Lu,Ma,Je,VeC1979492 does not have a vehicle_id
- trip_id PS : Lu,Ma,Je,VeC1983957 does not have a vehicle_id
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 |
|---|---|---|---|
| W001 | Timestamps should be populated for all elements | 3 022 | 33 times (100 % of validations) |
| W002 | vehicle_id should be populated for TripUpdates and VehiclePositions | 1 833 | 33 times (100 % of validations) |
| E022 | stop_time_update arrival/departure times between sequential stops should always increase - they should never be the same or decrease. | 2 294 | 32 times (97 % of validations) |
| E037 | Sequential GTFS-rt trip stop_time_updates shouldn't have the same stop_id | 85 | 31 times (94 % of validations) |
| E002 | stop_time_updates for a given trip_id must be strictly sorted by increasing stop_sequence | 72 | 24 times (73 % of validations) |
| E051 | All stop_time_update stop_sequences in GTFS-realtime data must appear in GTFS stop_times.txt for that trip | 41 | 23 times (70 % of validations) |
| E011 | All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt | 4 050 | 21 times (64 % 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 | 327 | 17 times (52 % of validations) |
| E003 | All trip_ids provided in the GTFS-rt feed must exist in the GTFS data, unless the schedule_relationship is ADDED | 506 | 5 times (15 % of validations) |
| E004 | All route_ids provided in the GTFS-rt feed must exist in the GTFS data | 187 | 2 times (6 % of validations) |
| E009 | If a GTFS trip contains multiple references to the same stop_id (i.e., the vehicle visits the same stop_id more than once in the same trip), then GTFS-rt stop_time_updates for this trip must include stop_sequence | 1 | 1 times (3 % of validations) |
GTFS-RT feed content
Entities
Entities present in this feed at 2025-09-30 at 03:15 Europe/Paris.
vehicle_positions (0) service_alerts (0) trip_updates (0)Entities seen in the last 7 days.
trip_updatesDecoded GTFS-RT feed
See full payload
Here is the decoded GTFS-RT feed Protobuf at 2025-09-30 at 03:15 Europe/Paris. You can look at the GTFS-RT documentation.
{
"header": {
"gtfsRealtimeVersion": "2.0",
"timestamp": "1759194925"
}
}