Resource details
This resource file is part of the dataset Réseau urbain Citéa.
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
❌476 errors, 283 warnings
Validation carried out using the current GTFS file and the GTFS-RT the 2025-06-05 at 09:08 Europe/Paris using the MobilityData GTFS-RT validator.
Errors
stop_times_updates not strictly sorted E002 35 errors
stop_time_updates for a given trip_id must be strictly sorted by increasing stop_sequence
Sample errors
- trip_id JeuHiv_3050325 stop_sequence [16, 17, 1] is not strictly sorted by increasing stop_sequence
- trip_id JeuHiv_3050492 stop_sequence [7, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 23, 24, 25] is not strictly sorted by increasing stop_sequence
- trip_id JeuHiv_3050326 stop_sequence [15, 16, 1] is not strictly sorted by increasing stop_sequence
- trip_id JeuHiv_3050300 stop_sequence [15, 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, 30, 31] is not strictly sorted by increasing stop_sequence
- trip_id JeuHiv_3050656 stop_sequence [13, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13] is not strictly sorted by increasing stop_sequence
Sequential stop_time_update times are not increasing E022 412 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 JeuHiv_3047694 stop_sequence 1 departure_time 08:40:06 (1749105606) is less than previous stop departure_time 08:58:11 (1749106691) - times must increase between two sequential stops
- trip_id JeuHiv_3047694 stop_sequence 1 departure_time 08:40:06 (1749105606) is less than previous stop arrival_time 08:58:11 (1749106691) - times must increase between two sequential stops
- trip_id JeuHiv_3047694 stop_sequence 2 arrival_time 08:41:07 (1749105667) is less than previous stop arrival_time 08:58:11 (1749106691) - times must increase between two sequential stops
- trip_id JeuHiv_3047694 stop_sequence 2 departure_time 08:41:07 (1749105667) is less than previous stop arrival_time 08:58:11 (1749106691) - times must increase between two sequential stops
- trip_id JeuHiv_3047696 stop_sequence 1 departure_time 09:08:29 (1749107309) is less than previous stop departure_time 09:23:09 (1749108189) - times must increase between two sequential stops
Sequential stop_time_updates have the same stop_id E037 14 errors
Sequential GTFS-rt trip stop_time_updates shouldn't have the same stop_id
Sample errors
- trip_id JeuHiv_3050300 has repeating stop_id 0:_LYT - sequential stop_ids should be different
- trip_id JeuHiv_3050301 has repeating stop_id 0:_LYT - sequential stop_ids should be different
- trip_id JeuHiv_3049328 has repeating stop_id 0:_LYT - sequential stop_ids should be different
- trip_id JeuHiv_3049594 has repeating stop_id 0:AURO - sequential stop_ids should be different
- trip_id JeuHiv_3049590 has repeating stop_id 0:AURO - sequential stop_ids should be different
GTFS-rt stop_sequence not found in GTFS data E051 15 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 JeuHiv_3050325 contains stop_sequence 1 that does not exist in GTFS stop_times.txt for this trip
- GTFS-rt trip_id JeuHiv_3050326 contains stop_sequence 1 that does not exist in GTFS stop_times.txt for this trip
- GTFS-rt trip_id JeuHiv_3050399 contains stop_sequence 1 that does not exist in GTFS stop_times.txt for this trip
- GTFS-rt trip_id JeuHiv_3050400 contains stop_sequence 1 that does not exist in GTFS stop_times.txt for this trip
- GTFS-rt trip_id JeuHiv_3049717 contains stop_sequence 1 that does not exist in GTFS stop_times.txt for this trip
Warnings
timestamp not populated W001 182 errors
Timestamps should be populated for all elements
Sample errors
- trip_id JeuHiv_3047694 does not have a timestamp
- trip_id JeuHiv_3049469 does not have a timestamp
- trip_id JeuHiv_3048681 does not have a timestamp
- trip_id JeuHiv_3050977 does not have a timestamp
- trip_id JeuHiv_3050077 does not have a timestamp
vehicle_id not populated W002 101 errors
vehicle_id should be populated for TripUpdates and VehiclePositions
Sample errors
- trip_id JeuHiv_3048681 does not have a vehicle_id
- trip_id JeuHiv_3050077 does not have a vehicle_id
- trip_id JeuHiv_3048598 does not have a vehicle_id
- trip_id JeuHiv_3049200 does not have a vehicle_id
- trip_id JeuHiv_3048947 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 |
---|---|---|---|
E022 | stop_time_update arrival/departure times between sequential stops should always increase - they should never be the same or decrease. | 5 744 | 18 times (100 % of validations) |
E037 | Sequential GTFS-rt trip stop_time_updates shouldn't have the same stop_id | 205 | 18 times (100 % of validations) |
W001 | Timestamps should be populated for all elements | 2 672 | 18 times (100 % of validations) |
W002 | vehicle_id should be populated for TripUpdates and VehiclePositions | 1 517 | 18 times (100 % of validations) |
E002 | stop_time_updates for a given trip_id must be strictly sorted by increasing stop_sequence | 461 | 17 times (94 % of validations) |
E051 | All stop_time_update stop_sequences in GTFS-realtime data must appear in GTFS stop_times.txt for that trip | 212 | 15 times (83 % of validations) |
GTFS-RT feed content
Entities
Entities present in this feed at 2025-06-05 at 23:38 Europe/Paris.
trip_updates (1) vehicle_positions (0) service_alerts (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-06-05 at 23:38 Europe/Paris. You can look at the GTFS-RT documentation.
{
"entity": [
{
"id": "3047960",
"tripUpdate": {
"stopTimeUpdate": [
{
"departure": {
"time": "1749133772",
"uncertainty": 120
},
"stopId": "0:_MIRE",
"stopSequence": 1
},
{
"arrival": {
"time": "1749136096"
},
"departure": {
"time": "1749136096"
},
"stopId": "0:_CVILRPI",
"stopSequence": 2
},
{
"arrival": {
"time": "1749136516"
},
"departure": {
"time": "1749136516"
},
"stopId": "0:_MIRE",
"stopSequence": 3
},
{
"arrival": {
"time": "1749136996"
},
"departure": {
"time": "1749136996"
},
"stopId": "0:_MMRPI",
"stopSequence": 4
},
{
"arrival": {
"time": "1749137596"
},
"departure": {
"time": "1749137596"
},
"stopId": "0:_SBVA 2",
"stopSequence": 5
},
{
"arrival": {
"time": "1749138196"
},
"stopId": "0:_MIRE",
"stopSequence": 6
}
],
"trip": {
"directionId": 1,
"routeId": "905",
"scheduleRelationship": "SCHEDULED",
"tripId": "JeuHiv_3047960"
},
"vehicle": {
"id": "3195",
"label": "3195"
}
}
}
],
"header": {
"gtfsRealtimeVersion": "2.0",
"timestamp": "1749159515"
}
}