Resource details

File name: Info trafic en temps réel du réseau SOLEA
Format: gtfs-rt

Information sur l’état du trafic en temps réel

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

Download availability

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

321 errors, 321 warnings

Validation carried out using the current GTFS file and the GTFS-RT the 2025-09-02 at 09:10 Europe/Paris using the MobilityData GTFS-RT validator.

Errors

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

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

Sample errors
  • alert entity ID SITRAM:6945 stop_id SITRAM:StopPoint:992 does not exist in GTFS data stops.txt
  • alert entity ID SITRAM:6945 stop_id SITRAM:StopPoint:993 does not exist in GTFS data stops.txt
  • alert entity ID SITRAM:6945 stop_id SITRAM:StopPoint:235 does not exist in GTFS data stops.txt
  • alert entity ID SITRAM:6945 stop_id SITRAM:StopPoint:344 does not exist in GTFS data stops.txt
  • alert entity ID SITRAM:6945 stop_id SITRAM:StopPoint:679 does not exist in GTFS data stops.txt

Alert does not have an informed_entity E032 1 error

All alerts must have at least one informed_entity.

Sample errors
  • alert ID SITRAM:7838 does not have an informed_entity - alerts must have at least one informed_entity

GTFS-rt agency_id does not exist in GTFS data E034 160 errors

All agency_ids provided in the GTFS-rt alert.informed_entity.agency_id should also exist in GTFS agency.txt

Sample errors
  • alert ID SITRAM:6945 agency_id SITRAM does not exist in the GTFS data agency.txt
  • alert ID SITRAM:6945 agency_id SITRAM does not exist in the GTFS data agency.txt
  • alert ID SITRAM:6945 agency_id SITRAM does not exist in the GTFS data agency.txt
  • alert ID SITRAM:6945 agency_id SITRAM does not exist in the GTFS data agency.txt
  • alert ID SITRAM:6945 agency_id SITRAM does not exist in the GTFS data agency.txt

Warnings

trip missing trip_id W006 160 errors

trip should include a trip_id

Sample errors
  • entity ID SITRAM:6945 does not contain a trip_id
  • entity ID SITRAM:6945 does not contain a trip_id
  • entity ID SITRAM:6945 does not contain a trip_id
  • entity ID SITRAM:6945 does not contain a trip_id
  • entity ID SITRAM:6945 does not contain a trip_id

Header timestamp is older than 65 seconds W008 1 error

The data in a GTFS-realtime feed should always be less than one minute old

Sample errors
  • header.timestamp is 83 min 10 sec old which is greater than the recommended age of 65 seconds

schedule_relationship not populated W009 160 errors

trip.schedule_relationship and stop_time_update.schedule_relationship should be populated

Sample errors
  • entity ID SITRAM:6945 does not have a schedule_relationship
  • entity ID SITRAM:6945 does not have a schedule_relationship
  • entity ID SITRAM:6945 does not have a schedule_relationship
  • entity ID SITRAM:6945 does not have a schedule_relationship
  • entity ID SITRAM:6945 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
E011 All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt 3 150 14 times (100 % of validations)
E034 All agency_ids provided in the GTFS-rt alert.informed_entity.agency_id should also exist in GTFS agency.txt 3 150 14 times (100 % of validations)
W006 trip should include a trip_id 3 150 14 times (100 % of validations)
W008 The data in a GTFS-realtime feed should always be less than one minute old 14 14 times (100 % of validations)
W009 trip.schedule_relationship and stop_time_update.schedule_relationship should be populated 3 150 14 times (100 % of validations)
E032 All alerts must have at least one informed_entity. 3 3 times (21 % 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.