Resource details

File name: GTFS-RT TripUpdate Marinéo Boulogne - horaires des prochains passages à l'arrêt
Format: gtfs-rt

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

Download availability

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

13 errors, 5 warnings

Validation carried out using the current GTFS file and the GTFS-RT the 2025-11-16 at 08:04 Europe/Paris using the MobilityData GTFS-RT validator.

Errors

GTFS-rt stop_id does not exist in GTFS data E011 1 error

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

Sample errors
  • trip_id 21328319 stop_id bsmtran2 does not exist in GTFS data stops.txt

Sequential stop_time_update times are not increasing E022 12 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 21328319 stop_sequence 1 departure_time 08:30:00 (1763278200) is less than previous stop departure_time 08:40:52 (1763278852) - times must increase between two sequential stops
  • trip_id 21328319 stop_sequence 1 departure_time 08:30:00 (1763278200) is less than previous stop arrival_time 08:40:52 (1763278852) - times must increase between two sequential stops
  • trip_id 21328319 stop_sequence 2 arrival_time 08:33:19 (1763278399) is less than previous stop arrival_time 08:40:52 (1763278852) - times must increase between two sequential stops
  • trip_id 21328319 stop_sequence 2 departure_time 08:33:19 (1763278399) is less than previous stop arrival_time 08:40:52 (1763278852) - times must increase between two sequential stops
  • trip_id 21328319 stop_sequence 9 arrival_time 08:40:55 (1763278855) is less than previous stop arrival_time 08:42:45 (1763278965) - times must increase between two sequential stops

Warnings

vehicle_id not populated W002 5 errors

vehicle_id should be populated for TripUpdates and VehiclePositions

Sample errors
  • trip_id 21328319 does not have a vehicle_id
  • trip_id 21328424 does not have a vehicle_id
  • trip_id 21328407 does not have a vehicle_id
  • trip_id 21328369 does not have a vehicle_id
  • trip_id 21328363 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
E011 All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt 499 30 times (100 % of validations)
E022 stop_time_update arrival/departure times between sequential stops should always increase - they should never be the same or decrease. 4 503 30 times (100 % of validations)
W002 vehicle_id should be populated for TripUpdates and VehiclePositions 931 30 times (100 % of validations)
E002 stop_time_updates for a given trip_id must be strictly sorted by increasing stop_sequence 239 26 times (87 % of validations)
E051 All stop_time_update stop_sequences in GTFS-realtime data must appear in GTFS stop_times.txt for that trip 26 20 times (67 % of validations)
E009 If a GTFS trip contains multiple references to the same stop_id (i.e., the vehicle visits the same stop_id more than once in the same trip), then GTFS-rt stop_time_updates for this trip must include stop_sequence 10 8 times (27 % of validations)
E003 All trip_ids provided in the GTFS-rt feed must exist in the GTFS data, unless the schedule_relationship is ADDED 7 7 times (23 % of validations)
E004 All route_ids provided in the GTFS-rt feed must exist in the GTFS data 7 7 times (23 % 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. 1 1 times (3 % of validations)
E037 Sequential GTFS-rt trip stop_time_updates shouldn't have the same stop_id 1 1 times (3 % of validations)

GTFS-RT feed content

Entities

Entities present in this feed at 2025-11-17 at 00:54 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-11-17 at 00:54 Europe/Paris. You can look at the GTFS-RT documentation.

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