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

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

162 errors, 19 warnings

Validation carried out using the current GTFS file and the GTFS-RT the 2025-12-29 at 08:04 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 2-857866252 does not exist in the GTFS data and does not have schedule_relationship of ADDED
  • trip_id 2-1006698507 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 2 errors

All route_ids provided in the GTFS-rt feed must exist in the GTFS data

Sample errors
  • route_id 51 does not exist in the GTFS data routes.txt
  • route_id 60 does not exist in the GTFS data routes.txt

Sequential stop_time_update times are not increasing E022 155 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 2-719650853 stop_sequence 29 arrival_time 08:07:02 (1766992022) is equal to previous stop arrival_time 08:07:02 (1766992022) - times must increase between two sequential stops
  • trip_id 2-719650853 stop_sequence 29 arrival_time 08:07:02 (1766992022) is equal to previous stop departure_time 08:07:02 (1766992022) - times must increase between two sequential stops
  • trip_id 2-719650853 stop_sequence 29 departure_time 08:07:02 (1766992022) is equal to previous stop departure_time 08:07:02 (1766992022) - times must increase between two sequential stops
  • trip_id 2-719650853 stop_sequence 29 departure_time 08:07:02 (1766992022) is equal to previous stop arrival_time 08:07:02 (1766992022) - times must increase between two sequential stops
  • trip_id 2-671154227 stop_sequence 21 arrival_time 08:03:45 (1766991825) is equal to previous stop departure_time 08:03:45 (1766991825) - times must increase between two sequential stops

stop_time_update departure time is before arrival time E025 1 error

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.

Sample errors
  • trip_id 2-522387457 stop_sequence 5 departure_time 08:03:52 (1766991832) is less than the same stop arrival_time 08:04:10 (1766991850) - departure time must be equal to or greater than arrival time

Sequential stop_time_updates have the same stop_id E037 2 errors

Sequential GTFS-rt trip stop_time_updates shouldn't have the same stop_id

Sample errors
  • trip_id 2-857866252 has repeating stop_id 812 at stop_sequence 2 - sequential stop_ids should be different
  • trip_id 2-1006698507 has repeating stop_id 421 at stop_sequence 2 - sequential stop_ids should be different

Warnings

timestamp not populated W001 19 errors

Timestamps should be populated for all elements

Sample errors
  • trip_id 2-857866252 does not have a timestamp
  • trip_id 2-719650853 does not have a timestamp
  • trip_id 2-1275199491 does not have a timestamp
  • trip_id 2-671154227 does not have a timestamp
  • trip_id 2-671285301 does not have a timestamp
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
W001 Timestamps should be populated for all elements 634 29 times (97 % of validations)
E022 stop_time_update arrival/departure times between sequential stops should always increase - they should never be the same or decrease. 4,357 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 73 24 times (80 % of validations)
E004 All route_ids provided in the GTFS-rt feed must exist in the GTFS data 47 24 times (80 % of validations)
E037 Sequential GTFS-rt trip stop_time_updates shouldn't have the same stop_id 47 24 times (80 % 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. 34 20 times (67 % of validations)

GTFS-RT feed content

Entities

Entities present in this feed at 2025-12-30 at 02:10 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 2025-12-30 at 02:10 Europe/Paris. You can look at the GTFS-RT documentation.

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