Resource details

File name: Données en temps réel de la position des véhicules du réseau DeepMob.
Format: gtfs-rt

Données en temps réel de la position des véhicules du réseau DeepMob.

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

Download availability

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

15 errors, 9 warnings

Validation carried out using the current GTFS file and the GTFS-RT the 2026-04-01 at 09:14 Europe/Paris using the MobilityData GTFS-RT validator.

Errors

trip direction_id does not match GTFS data E024 3 errors

GTFS-rt trip direction_id must match the direction_id in GTFS trips.txt

Sample errors
  • GTFS-rt vehicle_id 0200001002FF7D53 trip_id ATOUMOD005:ServiceJourney:237:LOC trip.direction_id is 1 but GTFS trip.direction_id is 0 - direction_id does not match
  • GTFS-rt vehicle_id 0200001002FF821A trip_id ATOUMOD005:ServiceJourney:239:LOC trip.direction_id is 1 but GTFS trip.direction_id is 0 - direction_id does not match
  • GTFS-rt vehicle_id 0200001002FFD6C7 trip_id ATOUMOD005:ServiceJourney:255:LOC trip.direction_id is 1 but GTFS trip.direction_id is 0 - direction_id does not match

Vehicle position far from trip shape E029 4 errors

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 0200001002FF821A trip_id ATOUMOD005:ServiceJourney:239:LOC at (49.92294,1.065783) is more than 200.0 meters (0.12 mile(s)) from the GTFS trip shape - vehicle should be near trip shape or on DETOUR
  • vehicle.id 0200001002FF7DC6 trip_id ATOUMOD005:ServiceJourney:247:LOC at (49.92334,1.064739) is more than 200.0 meters (0.12 mile(s)) from the GTFS trip shape - vehicle should be near trip shape or on DETOUR
  • vehicle.id 0200001002FFD6C7 trip_id ATOUMOD005:ServiceJourney:255:LOC at (49.89864,1.074022) is more than 200.0 meters (0.12 mile(s)) from the GTFS trip shape - vehicle should be near trip shape or on DETOUR
  • vehicle.id 0300B827EB7D2196 trip_id ATOUMOD005:ServiceJourney:253:LOC at (49.93202,1.106706) is more than 200.0 meters (0.12 mile(s)) from the GTFS trip shape - vehicle should be near trip shape or on DETOUR

GTFS-rt trip.trip_id does not belong to GTFS-rt trip.route_id in GTFS trips.txt E035 8 errors

The GTFS-rt trip.trip_id should belong to the specified trip.route_id in GTFS trips.txt

Sample errors
  • GTFS-rt entity ID VM:ATOUMOD005:ServiceJourney:119:LOC trip_id ATOUMOD005:ServiceJourney:119:LOC has route_id ATOUMOD005:Line:2:LOC but belongs to GTFS route_id ATOUMOD005:Line:1:LOC in GTFS trips.txt
  • GTFS-rt entity ID VM:ATOUMOD005:ServiceJourney:217:LOC trip_id ATOUMOD005:ServiceJourney:217:LOC has route_id ATOUMOD005:Line:1:LOC but belongs to GTFS route_id ATOUMOD005:Line:15:LOC in GTFS trips.txt
  • GTFS-rt entity ID VM:ATOUMOD005:ServiceJourney:219:LOC trip_id ATOUMOD005:ServiceJourney:219:LOC has route_id ATOUMOD005:Line:1:LOC but belongs to GTFS route_id ATOUMOD005:Line:2:LOC in GTFS trips.txt
  • GTFS-rt entity ID VM:ATOUMOD005:ServiceJourney:235:LOC trip_id ATOUMOD005:ServiceJourney:235:LOC has route_id ATOUMOD005:Line:2:LOC but belongs to GTFS route_id ATOUMOD005:Line:14:LOC in GTFS trips.txt
  • GTFS-rt entity ID VM:ATOUMOD005:ServiceJourney:239:LOC trip_id ATOUMOD005:ServiceJourney:239:LOC has route_id ATOUMOD005:Line:3:LOC but belongs to GTFS route_id ATOUMOD005:Line:2:LOC in GTFS trips.txt

Warnings

schedule_relationship not populated W009 9 errors

trip.schedule_relationship and stop_time_update.schedule_relationship should be populated

Sample errors
  • trip_id ATOUMOD005:ServiceJourney:119:LOC does not have a schedule_relationship
  • trip_id ATOUMOD005:ServiceJourney:217:LOC does not have a schedule_relationship
  • trip_id ATOUMOD005:ServiceJourney:219:LOC does not have a schedule_relationship
  • trip_id ATOUMOD005:ServiceJourney:235:LOC does not have a schedule_relationship
  • trip_id ATOUMOD005:ServiceJourney:237:LOC does not have a schedule_relationship
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
W009 trip.schedule_relationship and stop_time_update.schedule_relationship should be populated 197 29 times (97 % 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. 21 10 times (33 % of validations)
E003 All trip_ids provided in the GTFS-rt feed must exist in the GTFS data, unless the schedule_relationship is ADDED 7 7 times (23 % of validations)
E004 All route_ids provided in the GTFS-rt feed must exist in the GTFS data 7 7 times (23 % of validations)
W008 The data in a GTFS-realtime feed should always be less than one minute old 4 4 times (13 % of validations)
E024 GTFS-rt trip direction_id must match the direction_id in GTFS trips.txt 3 1 times (3 % of validations)
E035 The GTFS-rt trip.trip_id should belong to the specified trip.route_id in GTFS trips.txt 8 1 times (3 % of validations)
E050 All timestamps must be less than the current time 1 1 times (3 % of validations)

GTFS-RT feed content

Entities

Entities present in this feed at 2026-04-02 at 00:25 Europe/Paris.

vehicle_positions (1) 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 2026-04-02 at 00:25 Europe/Paris. You can look at the GTFS-RT documentation.

{ "entity": [ { "id": "VM:ATOUMOD005:ServiceJourney:119:LOC", "vehicle": { "position": { "bearing": 87.0, "latitude": 49.92205047607422, "longitude": 1.0802220106124878 }, "timestamp": "1775022328", "trip": { "directionId": 1, "routeId": "ATOUMOD005:Line:2:LOC", "tripId": "ATOUMOD005:ServiceJourney:119:LOC" }, "vehicle": { "id": "0200001002FF7E23" } } } ], "header": { "gtfsRealtimeVersion": "1.0", "timestamp": "1775082315" } }