transport.data.gouv.fr transport.data.gouv.fr

Resource details

File name: REMI GTFS-RT SERVICE_ALERTS
Format: gtfs-rt
Download

Données en temps réel du réseau interurbain Région Centre Val de Loire REMI - service alerts

This resource file is part of the dataset Réseau interurbain Rémi.

Download availability

2026-06-23
88.3%
2026-06-24
77%
2026-06-25
75.1%
2026-06-26
88%
2026-06-27
64.3%
2026-06-28
72.7%
2026-06-29
71.6%
2026-06-30
67.8%
2026-07-01
75.2%
2026-07-02
64.2%
2026-07-03
71.4%
2026-07-04
77.3%
2026-07-05
76.7%
2026-07-06
74%
2026-07-07
76.3%
2026-07-08
67.9%
2026-07-09
71.3%
2026-07-10
86.4%
2026-07-11
90.4%
2026-07-12
80.9%
2026-07-13
91.1%
2026-07-14
69%
2026-07-15
79.2%
2026-07-16
82.3%
2026-07-17
66%
2026-07-18
68.9%
2026-07-19
73.8%
2026-07-20
68.3%
2026-07-21
62.2%
2026-07-22
73.9%
2026-07-23
79.2%
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

❌2 errors, 48 warnings

Validation carried out using the current GTFS file and the GTFS-RT the 2026-07-23 at 09:00 Europe/Paris using the MobilityData GTFS-RT validator.

Errors

Alert does not have an informed_entity E032 2 errors

All alerts must have at least one informed_entity.

Sample errors
  • alert ID 39511aee-c7c7-4b8d-b671-3d3476b77ee3 does not have an informed_entity - alerts must have at least one informed_entity
  • alert ID d48039ec-584e-4e97-b1c0-a788b4dd9263 does not have an informed_entity - alerts must have at least one informed_entity

Warnings

trip missing trip_id W006 24 errors

trip should include a trip_id

Sample errors
  • entity ID 00359e06-2040-41b8-9ac3-201e1288a93d does not contain a trip_id
  • entity ID 00359e06-2040-41b8-9ac3-201e1288a93d does not contain a trip_id
  • entity ID 32a5cce5-bded-46ed-bc28-f4e2be58cde1 does not contain a trip_id
  • entity ID 4cf8b19f-78fd-456d-9070-2e115fcf6fc9 does not contain a trip_id
  • entity ID 4cf8b19f-78fd-456d-9070-2e115fcf6fc9 does not contain a trip_id

schedule_relationship not populated W009 24 errors

trip.schedule_relationship and stop_time_update.schedule_relationship should be populated

Sample errors
  • entity ID 00359e06-2040-41b8-9ac3-201e1288a93d does not have a schedule_relationship
  • entity ID 00359e06-2040-41b8-9ac3-201e1288a93d does not have a schedule_relationship
  • entity ID 32a5cce5-bded-46ed-bc28-f4e2be58cde1 does not have a schedule_relationship
  • entity ID 4cf8b19f-78fd-456d-9070-2e115fcf6fc9 does not have a schedule_relationship
  • entity ID 4cf8b19f-78fd-456d-9070-2e115fcf6fc9 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
E032 All alerts must have at least one informed_entity. 47 15 times (100 % of validations)
W006 trip should include a trip_id 374 15 times (100 % of validations)
W009 trip.schedule_relationship and stop_time_update.schedule_relationship should be populated 374 15 times (100 % of validations)
W008 The data in a GTFS-realtime feed should always be less than one minute old 4 4 times (27 % of validations)

GTFS-RT feed content

Could not decode the GTFS-RT feed.

The GTFS-RT feed should be accessible over HTTP, without authentication and use the Protobuf format.