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

1 error

Validation carried out using the current GTFS file and the GTFS-RT the 2025-06-14 at 09:07 Europe/Paris using the MobilityData GTFS-RT validator.

Errors

Vehicle position far from trip shape E029 1 error

The vehicle position should be within a certain distance of the GTFS shapes.txt data for the current trip unless there is a Service Alert with the Effect of DETOUR for this trip_id.

Sample errors
  • vehicle.id 110 trip_id 314cf8b42d9c8d2e78d2b4645f17d925 at (48.752193,-0.584899) is more than 200.0 meters (0.12 mile(s)) from the GTFS trip shape - vehicle should be near trip shape or on DETOUR
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
E003 All trip_ids provided in the GTFS-rt feed must exist in the GTFS data, unless the schedule_relationship is ADDED 38 9 times (30 % of validations)
E004 All route_ids provided in the GTFS-rt feed must exist in the GTFS data 38 9 times (30 % of validations)
W001 Timestamps should be populated for all elements 3 3 times (10 % of validations)
E029 The vehicle position should be within a certain distance of the GTFS shapes.txt data for the current trip unless there is a Service Alert with the Effect of DETOUR for this trip_id. 2 2 times (7 % 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-06-14 at 21:19 Europe/Paris.

vehicle_positions (0) 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-06-14 at 21:19 Europe/Paris. You can look at the GTFS-RT documentation.

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