gtfs-rt Transport open dataset - GTFS-RT TripUpdate Marinéo Boulogne - horaires des prochains passages à l'arrêt for Réseau urbain Marinéo

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

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

❌156 errors, 38 warnings

Validation carried out using the current GTFS file and the GTFS-RT the 2026-02-14 at 08:04 Europe/Paris using the MobilityData GTFS-RT validator.

Errors

stop_times_updates not strictly sorted E002 7 errors

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

Sample errors

trip_id 21327370 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 21327371 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 21327369 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 21327510 stop_sequence [7, 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] is not strictly sorted by increasing stop_sequence
trip_id 21327358 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 stop_id does not exist in GTFS data E011 20 errors

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

Sample errors

trip_id 21327370 stop_id bsmtran2 does not exist in GTFS data stops.txt
trip_id 21327371 stop_id bsmtran2 does not exist in GTFS data stops.txt
trip_id 21327369 stop_id bsmtran2 does not exist in GTFS data stops.txt
trip_id 21327672 stop_id wimmair3 does not exist in GTFS data stops.txt
trip_id 21327656 stop_id wimmair4 does not exist in GTFS data stops.txt

Sequential stop_time_update times are not increasing E022 118 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 21327370 stop_sequence 1 departure_time 08:20:00 (1771053600) is less than previous stop departure_time 08:53:37 (1771055617) - times must increase between two sequential stops
trip_id 21327370 stop_sequence 1 departure_time 08:20:00 (1771053600) is less than previous stop arrival_time 08:53:37 (1771055617) - times must increase between two sequential stops
trip_id 21327370 stop_sequence 2 arrival_time 08:20:55 (1771053655) is less than previous stop arrival_time 08:53:37 (1771055617) - times must increase between two sequential stops
trip_id 21327370 stop_sequence 2 departure_time 08:20:55 (1771053655) is less than previous stop arrival_time 08:53:37 (1771055617) - times must increase between two sequential stops
trip_id 21327370 stop_sequence 26 arrival_time 08:53:37 (1771055617) is less than previous stop arrival_time 08:54:10 (1771055650) - times must increase between two sequential stops

GTFS-rt stop_time_update stop_sequence and stop_id do not match GTFS E045 11 errors

If GTFS-rt stop_time_update contains both stop_sequence and stop_id, the values must match the GTFS data in stop_times.txt

Sample errors

GTFS-rt trip_id 21327225 stop_sequence 33 has stop_id semcord but GTFS stop_sequence 33 has stop_id semcord2 - stop_ids should be the same
GTFS-rt trip_id 21327672 stop_sequence 1 has stop_id wimmair3 but GTFS stop_sequence 1 has stop_id wimmair - stop_ids should be the same
GTFS-rt trip_id 21327656 stop_sequence 43 has stop_id wimmair4 but GTFS stop_sequence 43 has stop_id wimmair2 - stop_ids should be the same
GTFS-rt trip_id 21327739 stop_sequence 4 has stop_id smbecol but GTFS stop_sequence 4 has stop_id smbecol3 - stop_ids should be the same
GTFS-rt trip_id 21327736 stop_sequence 13 has stop_id smbecol but GTFS stop_sequence 13 has stop_id smbecol3 - stop_ids should be the same

Warnings

vehicle_id not populated W002 38 errors

vehicle_id should be populated for TripUpdates and VehiclePositions

Sample errors

trip_id 21327387 does not have a vehicle_id
trip_id 21327390 does not have a vehicle_id
trip_id 21327391 does not have a vehicle_id
trip_id 21327370 does not have a vehicle_id
trip_id 21327371 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	411	29 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.	3,146	29 times (100 % of validations)
W002	vehicle_id should be populated for TripUpdates and VehiclePositions	1,046	29 times (100 % of validations)
E002	stop_time_updates for a given trip_id must be strictly sorted by increasing stop_sequence	165	25 times (86 % of validations)
E003	All trip_ids provided in the GTFS-rt feed must exist in the GTFS data, unless the schedule_relationship is ADDED	16	16 times (55 % of validations)
E004	All route_ids provided in the GTFS-rt feed must exist in the GTFS data	16	16 times (55 % of validations)
E037	Sequential GTFS-rt trip stop_time_updates shouldn't have the same stop_id	35	15 times (52 % 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	134	14 times (48 % of validations)
E051	All stop_time_update stop_sequences in GTFS-realtime data must appear in GTFS stop_times.txt for that trip	18	11 times (38 % 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 (7 % 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.	2	2 times (7 % of validations)

GTFS-RT feed content

Entities

Entities present in this feed at 2026-02-15 at 05:14 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-02-15 at 05:14 Europe/Paris. You can look at the GTFS-RT documentation.


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