gtfs-rt Transport open dataset - GTFS-RT MATAWAN POSITION for Réseau urbain Envia

Resource details

File name: GTFS-RT MATAWAN POSITION

Format: gtfs-rt

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

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

❌4 errors, 2 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

vehicle_id 195 trip_id 2-857866252 does not exist in the GTFS data and does not have schedule_relationship of ADDED
vehicle_id 196 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

vehicle_id 195 route_id 51 does not exist in the GTFS data routes.txt
vehicle_id 196 route_id 60 does not exist in the GTFS data routes.txt

Warnings

timestamp not populated W001 2 errors

Timestamps should be populated for all elements

Sample errors

vehicle_id 186 does not have a timestamp
vehicle_id 183 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
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)
W001	Timestamps should be populated for all elements	48	22 times (73 % of validations)
E029	The vehicle position should be within a certain distance of the GTFS shapes.txt data for the current trip unless there is a Service Alert with the Effect of DETOUR for this trip_id.	19	14 times (47 % of validations)
E052	Each vehicle should have a unique ID	9	9 times (30 % of validations)
W004	vehicle.position.speed has an unrealistic speed that may be incorrect	3	3 times (10 % of validations)

GTFS-RT feed content

Entities

Entities present in this feed at 2025-12-30 at 03:36 Europe/Paris.

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

Entities seen in the last 7 days.

vehicle_positions

Decoded GTFS-RT feed

See full payload

Here is the decoded GTFS-RT feed Protobuf at 2025-12-30 at 03:36 Europe/Paris. You can look at the GTFS-RT documentation.


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