Resource details

File name: GTFS-RT MATAWAN Trip
Format: gtfs-rt

Temps réel des courses issues de MATAWAN

This resource file is part of the dataset Réseau urbain Envia.

Download availability

2026-02-13
100%
2026-02-14
100%
2026-02-15
100%
2026-02-16
100%
2026-02-17
100%
2026-02-18
100%
2026-02-19
100%
2026-02-20
100%
2026-02-21
100%
2026-02-22
100%
2026-02-23
100%
2026-02-24
100%
2026-02-25
100%
2026-02-26
100%
2026-02-27
100%
2026-02-28
100%
2026-03-01
100%
2026-03-02
100%
2026-03-03
100%
2026-03-04
100%
2026-03-05
100%
2026-03-06
100%
2026-03-07
100%
2026-03-08
100%
2026-03-09
100%
2026-03-10
100%
2026-03-11
100%
2026-03-12
100%
2026-03-13
100%
2026-03-14
100%
2026-03-15
100%
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

258 errors, 31 warnings

Validation carried out using the current GTFS file and the GTFS-RT the 2026-03-15 at 08:07 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 2 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 1-526647300-101-______D does not exist in the GTFS data and does not have schedule_relationship of ADDED
  • trip_id 1-522387461-101-______D does not exist in the GTFS data and does not have schedule_relationship of ADDED

Sequential stop_time_update times are not increasing E022 256 errors

stop_time_update arrival/departure times between sequential stops should always increase - they should never be the same or decrease.

Sample errors
  • trip_id 1-594280449 stop_sequence 22 arrival_time 08:27:58 (1773559678) is equal to previous stop arrival_time 08:27:58 (1773559678) - times must increase between two sequential stops
  • trip_id 1-594280449 stop_sequence 22 arrival_time 08:27:58 (1773559678) is equal to previous stop departure_time 08:27:58 (1773559678) - times must increase between two sequential stops
  • trip_id 1-594280449 stop_sequence 22 departure_time 08:27:58 (1773559678) is equal to previous stop departure_time 08:27:58 (1773559678) - times must increase between two sequential stops
  • trip_id 1-594280449 stop_sequence 22 departure_time 08:27:58 (1773559678) is equal to previous stop arrival_time 08:27:58 (1773559678) - times must increase between two sequential stops
  • trip_id 1-594280449 stop_sequence 28 arrival_time 08:38:58 (1773560338) is equal to previous stop arrival_time 08:38:58 (1773560338) - times must increase between two sequential stops

Warnings

timestamp not populated W001 17 errors

Timestamps should be populated for all elements

Sample errors
  • trip_id 1-594280449 does not have a timestamp
  • trip_id 1-522387457 does not have a timestamp
  • trip_id 1-654508033 does not have a timestamp
  • trip_id 1-526647300-101-______D does not have a timestamp
  • trip_id 1-522387461-101-______D does not have a timestamp

vehicle_id not populated W002 14 errors

vehicle_id should be populated for TripUpdates and VehiclePositions

Sample errors
  • trip_id 1-526647300-101-______D does not have a vehicle_id
  • trip_id 1-522387461-101-______D does not have a vehicle_id
  • trip_id 1-526647298 does not have a vehicle_id
  • trip_id 1-596377610 does not have a vehicle_id
  • trip_id 1-594280455 does not have a vehicle_id
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
E022 stop_time_update arrival/departure times between sequential stops should always increase - they should never be the same or decrease. 38,539 30 times (100 % of validations)
W001 Timestamps should be populated for all elements 3,448 30 times (100 % of validations)
E003 All trip_ids provided in the GTFS-rt feed must exist in the GTFS data, unless the schedule_relationship is ADDED 117 29 times (97 % of validations)
W002 vehicle_id should be populated for TripUpdates and VehiclePositions 2,856 26 times (87 % of validations)
E004 All route_ids provided in the GTFS-rt feed must exist in the GTFS data 47 25 times (83 % of validations)
E037 Sequential GTFS-rt trip stop_time_updates shouldn't have the same stop_id 47 25 times (83 % 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. 20 16 times (53 % of validations)

GTFS-RT feed content

Entities

Entities present in this feed at 2026-03-15 at 23:36 Europe/Paris.

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

Entities seen in the last 7 days.

trip_updates

Decoded GTFS-RT feed

See full payload

Here is the decoded GTFS-RT feed Protobuf at 2026-03-15 at 23:36 Europe/Paris. You can look at the GTFS-RT documentation.

{ "header": { "gtfsRealtimeVersion": "2.0", "timestamp": "1773614161" } }