Resource details

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

GTFS-RT (protobuff) de la position des véhicules.

This resource file is part of the dataset Réseaux urbain MOCA.

Download availability

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

6 errors, 2 warnings

Validation carried out using the current GTFS file and the GTFS-RT the 2025-09-29 at 09:02 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 2 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 65c9ff526c306f8b5192db41 trip_id 8 does not exist in the GTFS data and does not have schedule_relationship of ADDED
  • vehicle_id 67d29b626045b634aa4efebd trip_id 9 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 2 errors

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

Sample errors
  • vehicle_id 65c9ff526c306f8b5192db41 route_id 2 does not exist in the GTFS data routes.txt
  • vehicle_id 67d29b626045b634aa4efebd route_id 1 does not exist in the GTFS data routes.txt

GTFS-rt stop_id does not exist in GTFS data E011 2 errors

All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt

Sample errors
  • vehicle_id 65c9ff526c306f8b5192db41 stop_id 30028 does not exist in GTFS data stops.txt
  • vehicle_id 67d29b626045b634aa4efebd stop_id 30042 does not exist in GTFS data stops.txt

Warnings

schedule_relationship not populated W009 2 errors

trip.schedule_relationship and stop_time_update.schedule_relationship should be populated

Sample errors
  • trip_id 8 does not have a schedule_relationship
  • trip_id 9 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
E003 All trip_ids provided in the GTFS-rt feed must exist in the GTFS data, unless the schedule_relationship is ADDED 52 27 times (84 % of validations)
E004 All route_ids provided in the GTFS-rt feed must exist in the GTFS data 52 27 times (84 % of validations)
E011 All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt 52 27 times (84 % of validations)
W009 trip.schedule_relationship and stop_time_update.schedule_relationship should be populated 52 27 times (84 % of validations)

GTFS-RT feed content

Entities

Entities present in this feed at 2025-09-30 at 02:43 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-09-30 at 02:43 Europe/Paris. You can look at the GTFS-RT documentation.

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