Resource details
This resource file is part of the dataset Réseau urbain Nemus.
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
❌2 083 errors, 7 warnings
Validation carried out using the current GTFS file and the GTFS-RT the 2024-11-21 at 08:13 Europe/Paris using the MobilityData GTFS-RT validator.
Errors
GTFS-rt trip_id does not exist in GTFS data and does not have schedule_relationship of ADDED E003 7 errors
All trip_ids provided in the GTFS-rt feed must exist in the GTFS data, unless the schedule_relationship is ADDED
Sample errors
- trip_id 4e637fdf2204bad094066faa2c3c0cc7 does not exist in the GTFS data and does not have schedule_relationship of ADDED
- trip_id 985a852ef3d4e461d72c3334528f962c does not exist in the GTFS data and does not have schedule_relationship of ADDED
- trip_id fe0cafba8bb5489af06e1e80b73083d4 does not exist in the GTFS data and does not have schedule_relationship of ADDED
- trip_id f1bf7b75e8ac90ed19ea49dfc5199011 does not exist in the GTFS data and does not have schedule_relationship of ADDED
- trip_id dbaa522c1c45abd762e8f7048af34a81 does not exist in the GTFS data and does not have schedule_relationship of ADDED
GTFS-rt route_id does not exist in GTFS data E004 3 errors
All route_ids provided in the GTFS-rt feed must exist in the GTFS data
Sample errors
- route_id 248 does not exist in the GTFS data routes.txt
- route_id 248 does not exist in the GTFS data routes.txt
- route_id 248 does not exist in the GTFS data routes.txt
GTFS-rt stop_id does not exist in GTFS data E011 633 errors
All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt
Sample errors
- trip_id 4e637fdf2204bad094066faa2c3c0cc7 stop_id 2529 does not exist in GTFS data stops.txt
- trip_id 4e637fdf2204bad094066faa2c3c0cc7 stop_id 2804 does not exist in GTFS data stops.txt
- trip_id 4e637fdf2204bad094066faa2c3c0cc7 stop_id 2518 does not exist in GTFS data stops.txt
- trip_id 4e637fdf2204bad094066faa2c3c0cc7 stop_id 2686 does not exist in GTFS data stops.txt
- trip_id 4e637fdf2204bad094066faa2c3c0cc7 stop_id 2609 does not exist in GTFS data stops.txt
Sequential stop_time_update times are not increasing E022 1 440 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 4e637fdf2204bad094066faa2c3c0cc7 stop_sequence 95 arrival_time 07:24:42 (1732170282) is less than previous stop arrival_time 07:52:19 (1732171939) - times must increase between two sequential stops
- trip_id 4e637fdf2204bad094066faa2c3c0cc7 stop_sequence 95 arrival_time 07:24:42 (1732170282) is less than previous stop departure_time 07:52:43 (1732171963) - times must increase between two sequential stops
- trip_id 4e637fdf2204bad094066faa2c3c0cc7 stop_sequence 95 departure_time 07:24:51 (1732170291) is less than previous stop departure_time 07:52:43 (1732171963) - times must increase between two sequential stops
- trip_id 4e637fdf2204bad094066faa2c3c0cc7 stop_sequence 95 departure_time 07:24:51 (1732170291) is less than previous stop arrival_time 07:52:19 (1732171939) - times must increase between two sequential stops
- trip_id 4e637fdf2204bad094066faa2c3c0cc7 stop_sequence 167 arrival_time 07:56:08 (1732172168) is less than previous stop arrival_time 08:07:46 (1732172866) - times must increase between two sequential stops
Warnings
timestamp not populated W001 7 errors
Timestamps should be populated for all elements
Sample errors
- trip_id 4e637fdf2204bad094066faa2c3c0cc7 does not have a timestamp
- trip_id 985a852ef3d4e461d72c3334528f962c does not have a timestamp
- trip_id fe0cafba8bb5489af06e1e80b73083d4 does not have a timestamp
- trip_id f1bf7b75e8ac90ed19ea49dfc5199011 does not have a timestamp
- trip_id dbaa522c1c45abd762e8f7048af34a81 does not have a timestamp
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 |
|---|---|---|---|
| E003 | All trip_ids provided in the GTFS-rt feed must exist in the GTFS data, unless the schedule_relationship is ADDED | 21 | 3 times (100 % of validations) |
| E004 | All route_ids provided in the GTFS-rt feed must exist in the GTFS data | 7 | 3 times (100 % of validations) |
| E011 | All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt | 1 477 | 3 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 576 | 3 times (100 % of validations) |
| W001 | Timestamps should be populated for all elements | 21 | 3 times (100 % of validations) |
GTFS-RT feed content
Entities
Entities present in this feed at 2024-11-21 at 17:32 Europe/Paris.
service_alerts (0) trip_updates (0) vehicle_positions (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 2024-11-21 at 17:32 Europe/Paris. You can look at the GTFS-RT documentation.
{
"header": {
"gtfs_realtime_version": "2.0",
"timestamp": "1732206750"
}
}