Resource details

File name: Données en temps réel des horaires aux arrêts du réseau MOCA
Format: gtfs-rt

GTFS-RT (protobuff) des horaires aux arrêts.

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

Download availability

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

89 errors

Validation carried out using the current GTFS file and the GTFS-RT the 2024-12-20 at 08:16 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 4 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 5 does not exist in the GTFS data and does not have schedule_relationship of ADDED
  • trip_id 1 does not exist in the GTFS data and does not have schedule_relationship of ADDED
  • trip_id 6 does not exist in the GTFS data and does not have schedule_relationship of ADDED
  • trip_id 3 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 4 errors

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

Sample errors
  • route_id 1 does not exist in the GTFS data routes.txt
  • route_id 1 does not exist in the GTFS data routes.txt
  • route_id 2 does not exist in the GTFS data routes.txt
  • route_id 1 does not exist in the GTFS data routes.txt

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

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

Sample errors
  • trip_id 5 stop_id 30030 does not exist in GTFS data stops.txt
  • trip_id 5 stop_id 30029 does not exist in GTFS data stops.txt
  • trip_id 5 stop_id 30038 does not exist in GTFS data stops.txt
  • trip_id 5 stop_id 30035 does not exist in GTFS data stops.txt
  • trip_id 5 stop_id 30042 does not exist in GTFS data stops.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
E003 All trip_ids provided in the GTFS-rt feed must exist in the GTFS data, unless the schedule_relationship is ADDED 82 9 times (100 % of validations)
E004 All route_ids provided in the GTFS-rt feed must exist in the GTFS data 82 9 times (100 % of validations)
E011 All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt 1 393 9 times (100 % of validations)
E043 If a stop_time_update doesn't have a schedule_relationship of SKIPPED or NO_DATA, then either arrival or departure must be provided 81 5 times (56 % of validations)

GTFS-RT feed content

Entities

Entities present in this feed at 2024-12-22 at 05:10 Europe/Paris.

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

Entities seen in the last 7 days.

trip_updates

Decoded GTFS-RT feed

See full payload

Here is the decoded GTFS-RT feed Protobuf at 2024-12-22 at 05:10 Europe/Paris. You can look at the GTFS-RT documentation.

{ "header": { "gtfs_realtime_version": "2.0", "timestamp": "1734840632" } }