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

309 errors, 44 warnings

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

Errors

stop_times_updates not strictly sorted E002 10 errors

stop_time_updates for a given trip_id must be strictly sorted by increasing stop_sequence

Sample errors
  • trip_id 21323513 stop_sequence [22, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 23, 24, 25, 26, 27, 28, 29, 30, 31] is not strictly sorted by increasing stop_sequence
  • trip_id 21323512 stop_sequence [22, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 23, 24, 25, 26, 27, 28, 29, 30, 31] is not strictly sorted by increasing stop_sequence
  • trip_id 21323514 stop_sequence [22, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 23, 24, 25, 26, 27, 28, 29, 30, 31] is not strictly sorted by increasing stop_sequence
  • trip_id 21323612 stop_sequence [13, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22] is not strictly sorted by increasing stop_sequence
  • trip_id 21323614 stop_sequence [13, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22] is not strictly sorted by increasing stop_sequence

GTFS-rt trip_id does not exist in GTFS data and does not have schedule_relationship of ADDED E003 1 error

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 21323855 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 1 error

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

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

GTFS-rt stop_id does not exist in GTFS data E011 22 errors

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

Sample errors
  • trip_id 21323495 stop_id bsmtran2 does not exist in GTFS data stops.txt
  • trip_id 21323494 stop_id bsmtran2 does not exist in GTFS data stops.txt
  • trip_id 21323496 stop_id bsmtran2 does not exist in GTFS data stops.txt
  • trip_id 21323513 stop_id bsmtran2 does not exist in GTFS data stops.txt
  • trip_id 21323512 stop_id bsmtran2 does not exist in GTFS data stops.txt

Sequential stop_time_update times are not increasing E022 274 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 21323495 stop_sequence 1 departure_time 07:53:02 (1765435982) is less than previous stop departure_time 08:03:51 (1765436631) - times must increase between two sequential stops
  • trip_id 21323495 stop_sequence 1 departure_time 07:53:02 (1765435982) is less than previous stop arrival_time 08:03:51 (1765436631) - times must increase between two sequential stops
  • trip_id 21323495 stop_sequence 2 arrival_time 07:55:59 (1765436159) is less than previous stop arrival_time 08:03:51 (1765436631) - times must increase between two sequential stops
  • trip_id 21323495 stop_sequence 2 departure_time 07:56:02 (1765436162) is less than previous stop arrival_time 08:03:51 (1765436631) - times must increase between two sequential stops
  • trip_id 21323495 stop_sequence 6 arrival_time 08:00:15 (1765436415) is less than previous stop arrival_time 08:00:32 (1765436432) - times must increase between two sequential stops

GTFS-rt stop_sequence not found in GTFS data E051 1 error

All stop_time_update stop_sequences in GTFS-realtime data must appear in GTFS stop_times.txt for that trip

Sample errors
  • GTFS-rt trip_id 21323739 contains stop_sequence 1 that does not exist in GTFS stop_times.txt for this trip

Warnings

vehicle_id not populated W002 44 errors

vehicle_id should be populated for TripUpdates and VehiclePositions

Sample errors
  • trip_id 21725790 does not have a vehicle_id
  • trip_id 21725789 does not have a vehicle_id
  • trip_id 21725788 does not have a vehicle_id
  • trip_id 21323496 does not have a vehicle_id
  • trip_id 21323513 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 457 25 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 297 25 times (100 % of validations)
W002 vehicle_id should be populated for TripUpdates and VehiclePositions 937 25 times (100 % of validations)
E002 stop_time_updates for a given trip_id must be strictly sorted by increasing stop_sequence 216 22 times (88 % of validations)
E051 All stop_time_update stop_sequences in GTFS-realtime data must appear in GTFS stop_times.txt for that trip 24 20 times (80 % of validations)
E003 All trip_ids provided in the GTFS-rt feed must exist in the GTFS data, unless the schedule_relationship is ADDED 15 15 times (60 % of validations)
E004 All route_ids provided in the GTFS-rt feed must exist in the GTFS data 15 15 times (60 % of validations)
E045 If GTFS-rt stop_time_update contains both stop_sequence and stop_id, the values must match the GTFS data in stop_times.txt 17 7 times (28 % 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 2 2 times (8 % of validations)

GTFS-RT feed content

Could not decode the GTFS-RT feed.

The GTFS-RT feed should be accessible over HTTP, without authentication and use the Protobuf format.