Resource details
Données en temps réel au format GTFS-RT (protobuf) du réseau Semo (Val-de-Reuil, Louviers, Seine Eure Agglo).
This resource file is part of the dataset Réseau urbain et scolaire SEMO.
Download availability
Learn more
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
⚠️126 warnings
Validation carried out using the current GTFS file and the GTFS-RT the 2025-12-20 at 08:04 Europe/Paris using the MobilityData GTFS-RT validator.
Warnings
vehicle_id not populated W002 42 errors
vehicle_id should be populated for TripUpdates and VehiclePositions
Sample errors
- trip_id ATOUMOD006:ServiceJourney:1x6487699:LOC does not have a vehicle_id
- trip_id ATOUMOD006:ServiceJourney:1x6487707:LOC does not have a vehicle_id
- trip_id ATOUMOD006:ServiceJourney:1x6470489:LOC does not have a vehicle_id
- trip_id ATOUMOD006:ServiceJourney:1x6470700:LOC does not have a vehicle_id
- trip_id ATOUMOD006:ServiceJourney:1x6470701:LOC does not have a vehicle_id
schedule_relationship not populated W009 84 errors
trip.schedule_relationship and stop_time_update.schedule_relationship should be populated
Sample errors
- trip_id ATOUMOD006:ServiceJourney:1x6487699:LOC stop_sequence 1 (and potentially more for this trip) does not have a schedule_relationship
- trip_id ATOUMOD006:ServiceJourney:1x6487699:LOC does not have a schedule_relationship
- trip_id ATOUMOD006:ServiceJourney:1x6487707:LOC stop_sequence 23 (and potentially more for this trip) does not have a schedule_relationship
- trip_id ATOUMOD006:ServiceJourney:1x6487707:LOC does not have a schedule_relationship
- trip_id ATOUMOD006:ServiceJourney:1x6470489:LOC stop_sequence 1 (and potentially more for this trip) 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 |
|---|---|---|---|
| W002 | vehicle_id should be populated for TripUpdates and VehiclePositions | 1 094 | 24 times (80 % of validations) |
| W009 | trip.schedule_relationship and stop_time_update.schedule_relationship should be populated | 2 188 | 24 times (80 % of validations) |
| E037 | Sequential GTFS-rt trip stop_time_updates shouldn't have the same stop_id | 6 | 3 times (10 % of validations) |
| E003 | All trip_ids provided in the GTFS-rt feed must exist in the GTFS data, unless the schedule_relationship is ADDED | 96 | 2 times (7 % of validations) |
| W008 | The data in a GTFS-realtime feed should always be less than one minute old | 2 | 2 times (7 % of validations) |
GTFS-RT feed content
Entities
Entities present in this feed at 2025-12-20 at 23:09 Europe/Paris.
vehicle_positions (0) service_alerts (0) trip_updates (0)Entities seen in the last 7 days.
trip_updatesDecoded GTFS-RT feed
See full payload
Here is the decoded GTFS-RT feed Protobuf at 2025-12-20 at 23:09 Europe/Paris. You can look at the GTFS-RT documentation.
{
"header": {
"gtfsRealtimeVersion": "1.0",
"timestamp": "1766268578"
}
}