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

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

16 errors

Validation carried out using the current GTFS file and the GTFS-RT the 2024-11-21 at 08:13 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 7 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 15 trip_id 985a852ef3d4e461d72c3334528f962c does not exist in the GTFS data and does not have schedule_relationship of ADDED
  • vehicle_id 170 trip_id b3a0a84d695977541d0342f467d9c27e does not exist in the GTFS data and does not have schedule_relationship of ADDED
  • vehicle_id 167 trip_id f1bf7b75e8ac90ed19ea49dfc5199011 does not exist in the GTFS data and does not have schedule_relationship of ADDED
  • vehicle_id 83 trip_id 4e637fdf2204bad094066faa2c3c0cc7 does not exist in the GTFS data and does not have schedule_relationship of ADDED
  • vehicle_id 169 trip_id dbaa522c1c45abd762e8f7048af34a81 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 3 errors

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

Sample errors
  • vehicle_id 15 route_id 248 does not exist in the GTFS data routes.txt
  • vehicle_id 83 route_id 248 does not exist in the GTFS data routes.txt
  • vehicle_id 84 route_id 248 does not exist in the GTFS data routes.txt

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

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

Sample errors
  • vehicle_id 15 stop_id 2115 does not exist in GTFS data stops.txt
  • vehicle_id 83 stop_id 3166 does not exist in GTFS data stops.txt
  • vehicle_id 84 stop_id 2854 does not exist in GTFS data stops.txt

Vehicle position outside agency coverage area E028 3 errors

The vehicle position should be inside the agency coverage area. This is defined as within roughly 1/8 of a mile (200 meters) of the GTFS shapes.txt data, or stops.txt locations if the GTFS feed doesn't include shapes.txt.

Sample errors
  • vehicle.id 15 at (48.684784,-0.489889) is more than 1609.0 meters (1.00 mile(s)) outside entire GTFS stops.txt coverage area - vehicle should be within area
  • vehicle.id 83 at (48.69146,-0.520155) is more than 1609.0 meters (1.00 mile(s)) outside entire GTFS stops.txt coverage area - vehicle should be within area
  • vehicle.id 84 at (48.674053,-0.523426) is more than 1609.0 meters (1.00 mile(s)) outside entire GTFS stops.txt coverage area - vehicle should be within area
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 14 2 times (100 % of validations)
E004 All route_ids provided in the GTFS-rt feed must exist in the GTFS data 5 2 times (100 % of validations)
E011 All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt 4 2 times (100 % of validations)
E028 The vehicle position should be inside the agency coverage area. This is defined as within roughly 1/8 of a mile (200 meters) of the GTFS shapes.txt data, or stops.txt locations if the GTFS feed doesn't include shapes.txt. 3 1 times (50 % of validations)

GTFS-RT feed content

Entities

Entities present in this feed at 2024-11-21 at 17:26 Europe/Paris.

service_alerts (0) trip_updates (0) vehicle_positions (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 2024-11-21 at 17:26 Europe/Paris. You can look at the GTFS-RT documentation.

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