Resource details
Données en temps réel au format GTFS-RT (protobuf) du réseau de transport de Seine Normandie Agglomération.
This resource file is part of the dataset Réseau urbain SNgo!.
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
❌27 errors, 18 warnings
Validation carried out using the current GTFS file and the GTFS-RT the 2026-04-11 at 09:06 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 6 errors
All trip_ids provided in the GTFS-rt feed must exist in the GTFS data, unless the schedule_relationship is ADDED
Sample errors
- trip_id ATOUMOD007:ServiceJourney:573:LOC does not exist in the GTFS data and does not have schedule_relationship of ADDED
- trip_id ATOUMOD007:ServiceJourney:585:LOC does not exist in the GTFS data and does not have schedule_relationship of ADDED
- trip_id ATOUMOD007:ServiceJourney:597:LOC does not exist in the GTFS data and does not have schedule_relationship of ADDED
- trip_id ATOUMOD007:ServiceJourney:725:LOC does not exist in the GTFS data and does not have schedule_relationship of ADDED
- trip_id ATOUMOD007:ServiceJourney:719:LOC 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 6 errors
All route_ids provided in the GTFS-rt feed must exist in the GTFS data
Sample errors
- route_id ATOUMOD007:Line:23:LOC does not exist in the GTFS data routes.txt
- route_id ATOUMOD007:Line:24:LOC does not exist in the GTFS data routes.txt
- route_id ATOUMOD007:Line:25:LOC does not exist in the GTFS data routes.txt
- route_id ATOUMOD007:Line:24:LOC does not exist in the GTFS data routes.txt
- route_id ATOUMOD007:Line:26:LOC does not exist in the GTFS data routes.txt
GTFS-rt stop_id does not exist in GTFS data E011 15 errors
All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt
Sample errors
- trip_id ATOUMOD007:ServiceJourney:573:LOC stop_id FR:27681:ZE:10102:ATOUMOD007 does not exist in GTFS data stops.txt
- trip_id ATOUMOD007:ServiceJourney:585:LOC stop_id FR:27681:ZE:10102:ATOUMOD007 does not exist in GTFS data stops.txt
- trip_id ATOUMOD007:ServiceJourney:585:LOC stop_id FR:27681:ZE:10043:ATOUMOD007 does not exist in GTFS data stops.txt
- trip_id ATOUMOD007:ServiceJourney:585:LOC stop_id FR:27681:ZE:11000:ATOUMOD007 does not exist in GTFS data stops.txt
- trip_id ATOUMOD007:ServiceJourney:597:LOC stop_id FR:27681:ZE:10102:ATOUMOD007 does not exist in GTFS data stops.txt
Warnings
vehicle_id not populated W002 6 errors
vehicle_id should be populated for TripUpdates and VehiclePositions
Sample errors
- trip_id ATOUMOD007:ServiceJourney:573:LOC does not have a vehicle_id
- trip_id ATOUMOD007:ServiceJourney:585:LOC does not have a vehicle_id
- trip_id ATOUMOD007:ServiceJourney:597:LOC does not have a vehicle_id
- trip_id ATOUMOD007:ServiceJourney:725:LOC does not have a vehicle_id
- trip_id ATOUMOD007:ServiceJourney:719:LOC does not have a vehicle_id
schedule_relationship not populated W009 12 errors
trip.schedule_relationship and stop_time_update.schedule_relationship should be populated
Sample errors
- trip_id ATOUMOD007:ServiceJourney:573:LOC stop_sequence 1 (and potentially more for this trip) does not have a schedule_relationship
- trip_id ATOUMOD007:ServiceJourney:573:LOC does not have a schedule_relationship
- trip_id ATOUMOD007:ServiceJourney:585:LOC stop_sequence 1 (and potentially more for this trip) does not have a schedule_relationship
- trip_id ATOUMOD007:ServiceJourney:585:LOC does not have a schedule_relationship
- trip_id ATOUMOD007:ServiceJourney:597: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 |
|---|---|---|---|
| E003 | All trip_ids provided in the GTFS-rt feed must exist in the GTFS data, unless the schedule_relationship is ADDED | 582 | 25 times (83 % of validations) |
| E004 | All route_ids provided in the GTFS-rt feed must exist in the GTFS data | 582 | 25 times (83 % of validations) |
| E011 | All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt | 6,815 | 25 times (83 % of validations) |
| W002 | vehicle_id should be populated for TripUpdates and VehiclePositions | 582 | 25 times (83 % of validations) |
| W009 | trip.schedule_relationship and stop_time_update.schedule_relationship should be populated | 1,164 | 25 times (83 % of validations) |
| E022 | stop_time_update arrival/departure times between sequential stops should always increase - they should never be the same or decrease. | 8 | 8 times (27 % of validations) |
| E025 | Within the same stop_time_update, arrival and departures times can be the same, or the departure time can be later than the arrival time - the departure time should never come before the arrival time. | 16 | 8 times (27 % of validations) |
| W008 | The data in a GTFS-realtime feed should always be less than one minute old | 3 | 3 times (10 % of validations) |
GTFS-RT feed content
Entities
Entities present in this feed at 2026-04-11 at 22:26 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 2026-04-11 at 22:26 Europe/Paris. You can look at the GTFS-RT documentation.
{
"header": {
"gtfsRealtimeVersion": "1.0",
"timestamp": "1775939194"
}
}