Resource details

File name: Temps réel au format GTFS-RT (vehicle-position)
Format: gtfs-rt

This resource file is part of the dataset Réseau urbain Nemus.

Download availability

2025-03-20
100%
2025-03-21
100%
2025-03-22
100%
2025-03-23
100%
2025-03-24
100%
2025-03-25
100%
2025-03-26
100%
2025-03-27
100%
2025-03-28
100%
2025-03-29
100%
2025-03-30
100%
2025-03-31
100%
2025-04-01
100%
2025-04-02
100%
2025-04-03
100%
2025-04-04
99.9%
2025-04-05
100%
2025-04-06
100%
2025-04-07
100%
2025-04-08
100%
2025-04-09
100%
2025-04-10
100%
2025-04-11
100%
2025-04-12
100%
2025-04-13
100%
2025-04-14
100%
2025-04-15
100%
2025-04-16
100%
2025-04-17
100%
2025-04-18
100%
2025-04-19
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

10 errors

Validation carried out using the current GTFS file and the GTFS-RT the 2025-04-19 at 09:12 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 5 errors

All trip_ids provided in the GTFS-rt feed must exist in the GTFS data, unless the schedule_relationship is ADDED

Sample errors
  • vehicle_id 4 trip_id 290d8f3306d787dd986ae9e426c9e919 does not exist in the GTFS data and does not have schedule_relationship of ADDED
  • vehicle_id 170 trip_id ffe02b3c548631b71cf051f0c0d78f95 does not exist in the GTFS data and does not have schedule_relationship of ADDED
  • vehicle_id 110 trip_id 848c3c5893d8730020dbbf2625118540 does not exist in the GTFS data and does not have schedule_relationship of ADDED
  • vehicle_id 168 trip_id febd77b6adc97d19e72202e94bb8714d does not exist in the GTFS data and does not have schedule_relationship of ADDED
  • vehicle_id 167 trip_id b24273d6470a45249a1de155dfc3d80e 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 5 errors

All route_ids provided in the GTFS-rt feed must exist in the GTFS data

Sample errors
  • vehicle_id 4 route_id 250 does not exist in the GTFS data routes.txt
  • vehicle_id 170 route_id 250 does not exist in the GTFS data routes.txt
  • vehicle_id 110 route_id 251 does not exist in the GTFS data routes.txt
  • vehicle_id 168 route_id 249 does not exist in the GTFS data routes.txt
  • vehicle_id 167 route_id 249 does not exist in the GTFS data routes.txt
Validate this GTFS-RT now

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 6 5 times (17 % of validations)
E003 All trip_ids provided in the GTFS-rt feed must exist in the GTFS data, unless the schedule_relationship is ADDED 15 3 times (10 % of validations)
E004 All route_ids provided in the GTFS-rt feed must exist in the GTFS data 15 3 times (10 % of validations)
E052 Each vehicle should have a unique ID 1 1 times (3 % of validations)

GTFS-RT feed content

Entities

Entities present in this feed at 2025-04-19 at 15:22 Europe/Paris.

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

Entities seen in the last 7 days.

vehicle_positions

Decoded GTFS-RT feed

See full payload

Here is the decoded GTFS-RT feed Protobuf at 2025-04-19 at 15:22 Europe/Paris. You can look at the GTFS-RT documentation.

{ "entity": [ { "id": "335358", "vehicle": { "current_stop_sequence": 4, "position": { "bearing": 51.0, "latitude": 48.729827880859375, "longitude": -0.5824909806251526, "speed": 7.5 }, "stop_id": "2255", "timestamp": "1745068899", "trip": { "direction_id": 1, "route_id": "249", "schedule_relationship": "SCHEDULED", "start_date": "20250419", "start_time": "15:20:00", "trip_id": "4c7d56ef1e5781162af259c92e0a317a" }, "vehicle": { "id": "167", "label": "4101", "license_plate": "GV-645-AH" } } }, { "id": "335360", "vehicle": { "current_stop_sequence": 1, "stop_id": "2336", "trip": { "direction_id": 1, "route_id": "250", "schedule_relationship": "SCHEDULED", "start_date": "20250419", "start_time": "15:29:00", "trip_id": "745ad321cd1625f660fa6206047004c4" }, "vehicle": { "id": "4", "label": "4898", "license_plate": "CK-046-DD" } } }, { "id": "335357", "vehicle": { "current_stop_sequence": 7, "position": { "bearing": 249.0, "latitude": 48.74938201904297, "longitude": -0.5648059844970703, "speed": 7.5 }, "stop_id": "2256", "timestamp": "1745068940", "trip": { "direction_id": 0, "route_id": "249", "schedule_relationship": "SCHEDULED", "start_date": "20250419", "start_time": "15:15:00", "trip_id": "cee9356cdc62228180584b7e2a67dfeb" }, "vehicle": { "id": "168", "label": "4102", "license_plate": "GV-748-AH" } } } ], "header": { "gtfs_realtime_version": "2.0", "timestamp": "1745068961" } }