Resource details
File name:
Données en temps réel de la position des véhicules du réseau SEMO
Format: gtfs-rt
GTFS-RT (protobuff) de la position des véhicules.
This resource file is part of the dataset Réseau urbain et scolaire SEMO.
Download availability
2025-11-23
93.6%
2025-11-24
100%
2025-11-25
100%
2025-11-26
100%
2025-11-27
100%
2025-11-28
100%
2025-11-29
100%
2025-11-30
97%
2025-12-01
100%
2025-12-02
100%
2025-12-03
100%
2025-12-04
100%
2025-12-05
99.4%
2025-12-06
99.4%
2025-12-07
97%
2025-12-08
100%
2025-12-09
100%
2025-12-10
100%
2025-12-11
100%
2025-12-12
100%
2025-12-13
100%
2025-12-14
96.8%
2025-12-15
100%
2025-12-16
100%
2025-12-17
100%
2025-12-18
100%
2025-12-19
100%
2025-12-20
100%
2025-12-21
97.1%
2025-12-22
92.2%
2025-12-23
97.2%
Learn more
We test this resource download availability every hour by making an HTTP
For SIRI and SIRI Lite feeds, we perform a
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
⚠️18 warnings
Validation carried out using the current GTFS file and the GTFS-RT the 2025-12-22 at 08:10 Europe/Paris using the MobilityData GTFS-RT validator.
Warnings
schedule_relationship not populated W009 18 errors
trip.schedule_relationship and stop_time_update.schedule_relationship should be populated
Sample errors
- trip_id ATOUMOD006:ServiceJourney:4x1470519:LOC does not have a schedule_relationship
- trip_id ATOUMOD006:ServiceJourney:4x1470529:LOC does not have a schedule_relationship
- trip_id ATOUMOD006:ServiceJourney:4x1470518:LOC does not have a schedule_relationship
- trip_id ATOUMOD006:ServiceJourney:4x1480571:LOC does not have a schedule_relationship
- trip_id ATOUMOD006:ServiceJourney:4x1480520:LOC does not have a schedule_relationship
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 |
|---|---|---|---|
| W009 | trip.schedule_relationship and stop_time_update.schedule_relationship should be populated | 429 | 24 times (80 % of validations) |
| E029 | The vehicle position should be within a certain distance of the GTFS shapes.txt data for the current trip unless there is a Service Alert with the Effect of DETOUR for this trip_id. | 6 | 5 times (17 % of validations) |
| W008 | The data in a GTFS-realtime feed should always be less than one minute old | 4 | 4 times (13 % of validations) |
| E003 | All trip_ids provided in the GTFS-rt feed must exist in the GTFS data, unless the schedule_relationship is ADDED | 38 | 2 times (7 % 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.