Resource details
GTFS-RT (protobuff) global, regroupant les horaires aux arrêts, la position des véhicules et les perturbations.
This resource file is part of the dataset Réseau urbain MOCA.
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
❌50 errors
Many validation errors indicate that the GTFS-RT identifiers do not match the GTFS identifiers.
Validation carried out using the current GTFS file and the GTFS-RT the 2026-08-01 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 4 errors
All trip_ids provided in the GTFS-rt feed must exist in the GTFS data, unless the schedule_relationship is ADDED
Sample errors
- vehicle_id 65c9ff526c306f8b5192db41 trip_id 9 does not exist in the GTFS data and does not have schedule_relationship of ADDED
- vehicle_id 67d29b626045b634aa4efebd trip_id 10 does not exist in the GTFS data and does not have schedule_relationship of ADDED
- trip_id 9 does not exist in the GTFS data and does not have schedule_relationship of ADDED
- trip_id 10 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 4 errors
All route_ids provided in the GTFS-rt feed must exist in the GTFS data
Sample errors
- vehicle_id 65c9ff526c306f8b5192db41 route_id 1 does not exist in the GTFS data routes.txt
- vehicle_id 67d29b626045b634aa4efebd route_id 2 does not exist in the GTFS data routes.txt
- route_id 1 does not exist in the GTFS data routes.txt
- route_id 2 does not exist in the GTFS data routes.txt
GTFS-rt stop_id does not exist in GTFS data E011 42 errors
All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt
Sample errors
- vehicle_id 65c9ff526c306f8b5192db41 stop_id 30032 does not exist in GTFS data stops.txt
- vehicle_id 67d29b626045b634aa4efebd stop_id 30024 does not exist in GTFS data stops.txt
- trip_id 9 stop_id 30030 does not exist in GTFS data stops.txt
- trip_id 9 stop_id 30029 does not exist in GTFS data stops.txt
- trip_id 9 stop_id 30038 does not exist in GTFS data stops.txt
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 | 2,973 | 28 times (93 % of validations) |
| E003 | All trip_ids provided in the GTFS-rt feed must exist in the GTFS data, unless the schedule_relationship is ADDED | 188 | 25 times (83 % of validations) |
| E004 | All route_ids provided in the GTFS-rt feed must exist in the GTFS data | 188 | 25 times (83 % of validations) |
| W003 | a trip_id that is provided in the VehiclePositions feed should be provided in the TripUpdates feed, and a vehicle_id that is provided in the TripUpdates feed should be provided in the VehiclePositions feed | 106 | 17 times (57 % of validations) |
| E047 | If separate `VehiclePositions` and `TripUpdates` feeds are provided, `VehicleDescriptor` or `TripDescriptor` ID value pairing should match between the two feeds. | 22 | 16 times (53 % of validations) |
| E043 | If a stop_time_update doesn't have a schedule_relationship of SKIPPED or NO_DATA, then either arrival or departure must be provided | 322 | 14 times (47 % of validations) |
| E022 | stop_time_update arrival/departure times between sequential stops should always increase - they should never be the same or decrease. | 63 | 5 times (17 % of validations) |
| W009 | trip.schedule_relationship and stop_time_update.schedule_relationship should be populated | 1 | 1 times (3 % of validations) |
GTFS-RT feed content
Entities
Entities present in this feed at 2026-08-02 at 05:54 Europe/Paris.
service_alerts (1) vehicle_positions (0) trip_updates (0)Entities seen in the last 7 days.
service_alerts trip_updates vehicle_positionsService alerts
Here is a display of service alerts contained in this feed at 2026-08-02 at 05:54 Europe/Paris.
déviation Moca 1 et 2 Detour
Enraison de travaux de réfection des canalisations d'eau potable sur la ruePierre et Marie Curie de Barentin, la rue est fermée dans le sensdescendant, Leslignes 1 et2 seront déviées parl’avenue Aristide Briand dans le sens zone commerciale direction Pavilly etVillers-Ecalles
Between 2026-07-10 at 00:00 Europe/Paris and 2026-08-14 at 23:59 Europe/Paris
Decoded GTFS-RT feed
See full payload
Here is the decoded GTFS-RT feed Protobuf at 2026-08-02 at 05:54 Europe/Paris. You can look at the GTFS-RT documentation.
{
"entity": [
{
"alert": {
"activePeriod": [
{
"end": "1786744740",
"start": "1783634400"
}
],
"cause": "CONSTRUCTION",
"descriptionText": {
"translation": [
{
"text": "Enraison de travaux de réfection des canalisations d'eau potable sur la ruePierre et Marie Curie de Barentin, la rue est fermée dans le sensdescendant, \n\nLeslignes 1 et2 seront déviées parl’avenue Aristide Briand dans le sens zone commerciale direction Pavilly etVillers-Ecalles"
}
]
},
"effect": "DETOUR",
"headerText": {
"translation": [
{
"text": "déviation Moca 1 et 2"
}
]
},
"informedEntity": [
{
"routeId": "1"
},
{
"routeId": "2"
}
]
},
"id": "alert:6a4b4d351837db300139131a"
}
],
"header": {
"gtfsRealtimeVersion": "2.0",
"timestamp": "1785642852"
}
}