gtfs-rt Transport open dataset - Données gobales en temps réel du réseau MOCA for Réseau urbain MOCA - CC Caux

Resource details

File name: Données gobales en temps réel du réseau MOCA

Format: gtfs-rt

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

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

❌123 errors, 4 warnings

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-07-16 at 09:03 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

vehicle_id 65c9ff526c306f8b5192db41 trip_id 10 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
trip_id 7 does not exist in the GTFS data and does not have schedule_relationship of ADDED
trip_id 6 does not exist in the GTFS data and does not have schedule_relationship of ADDED
trip_id 2 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

vehicle_id 65c9ff526c306f8b5192db41 route_id 2 does not exist in the GTFS data routes.txt
route_id 2 does not exist in the GTFS data routes.txt
route_id 2 does not exist in the GTFS data routes.txt
route_id 2 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 97 errors

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

Sample errors

vehicle_id 65c9ff526c306f8b5192db41 stop_id 30024 does not exist in GTFS data stops.txt
alert entity ID alert:6a54f7f679f5b9d0efe88e04 stop_id 30030 does not exist in GTFS data stops.txt
trip_id 10 stop_id 30028 does not exist in GTFS data stops.txt
trip_id 10 stop_id 30024 does not exist in GTFS data stops.txt
trip_id 10 stop_id 30006 does not exist in GTFS data stops.txt

stop_time_update doesn't have arrival or departure E043 13 errors

If a stop_time_update doesn't have a schedule_relationship of SKIPPED or NO_DATA, then either arrival or departure must be provided

Sample errors

trip_id 7 stop_sequence 0 doesn't have arrival or departure
trip_id 7 stop_sequence 1 doesn't have arrival or departure
trip_id 7 stop_sequence 2 doesn't have arrival or departure
trip_id 6 stop_sequence 1 doesn't have arrival or departure
trip_id 6 stop_sequence 2 doesn't have arrival or departure

VehiclePosition and TripUpdate ID pairing mismatch E047 1 error

If separate `VehiclePositions` and `TripUpdates` feeds are provided, `VehicleDescriptor` or `TripDescriptor` ID value pairing should match between the two feeds.

Sample errors

trip_id 10 and vehicle_id 65c9ff526c306f8b5192db41 pairing in VehiclePositions does not match trip_id 3 and vehicle_id 65c9ff526c306f8b5192db41 pairing in TripUpdates feed and trip block_ids aren't the same - ID pairing between feeds should match

Warnings

ID in one feed missing from the other W003 4 errors

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

Sample errors

trip_id 2 is in TripUpdates but not in VehiclePositions feed
trip_id 3 is in TripUpdates but not in VehiclePositions feed
trip_id 6 is in TripUpdates but not in VehiclePositions feed
trip_id 7 is in TripUpdates but not in VehiclePositions feed

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	4,913	26 times (87 % of validations)
E003	All trip_ids provided in the GTFS-rt feed must exist in the GTFS data, unless the schedule_relationship is ADDED	280	25 times (83 % of validations)
E004	All route_ids provided in the GTFS-rt feed must exist in the GTFS data	280	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	188	25 times (83 % of validations)
E047	If separate `VehiclePositions` and `TripUpdates` feeds are provided, `VehicleDescriptor` or `TripDescriptor` ID value pairing should match between the two feeds.	38	24 times (80 % 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	181	13 times (43 % of validations)
E022	stop_time_update arrival/departure times between sequential stops should always increase - they should never be the same or decrease.	31	2 times (7 % 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-07-17 at 03:54 Europe/Paris.

service_alerts (2) vehicle_positions (0) trip_updates (0)

Entities seen in the last 7 days.

service_alerts trip_updates vehicle_positions

Service alerts

Here is a display of service alerts contained in this feed at 2026-07-17 at 03: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

travaux rue Freckenhorst Pavilly Stop moved

A partir de mercredi 15 juillet 2026. Enraison de travaux de réfection sur la rue de Freckenhorst à Pavilly, «l’arrêt Freckenhorst » est reporté 100 mètres plus hautpour faciliter la circulation en alterna mise en place.

Between 2026-07-13 at 00:00 Europe/Paris and 2026-07-31 at 23:59 Europe/Paris

Decoded GTFS-RT feed

See full payload

Here is the decoded GTFS-RT feed Protobuf at 2026-07-17 at 03: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"
    },
    {
      "alert": {
        "activePeriod": [
          {
            "end": "1785535140",
            "start": "1783893600"
          }
        ],
        "cause": "CONSTRUCTION",
        "descriptionText": {
          "translation": [
            {
              "text": "A partir de mercredi 15 juillet 2026.\n\nEnraison de travaux de réfection sur la rue de Freckenhorst à Pavilly, «l’arrêt Freckenhorst » est reporté 100 mètres plus hautpour faciliter la circulation en alterna mise en place."
            }
          ]
        },
        "effect": "STOP_MOVED",
        "headerText": {
          "translation": [
            {
              "text": "travaux rue Freckenhorst Pavilly"
            }
          ]
        },
        "informedEntity": [
          {
            "stopId": "30030"
          }
        ]
      },
      "id": "alert:6a54f7f679f5b9d0efe88e04"
    }
  ],
  "header": {
    "gtfsRealtimeVersion": "2.0",
    "timestamp": "1784253245"
  }
}