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

❌129 errors, 39 warnings

Validation carried out using the current GTFS file and the GTFS-RT the 2025-07-05 at 09:00 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 20477830 stop_sequence for stop_ids [leopet1, leobeau, leobeau2, leofle2, leobel2, leocite2, leofle1, bsmcca4, bsmdute, bsmlumi2, bsmaug1, bsmhenn2, bsmros2, bsmmade, smbplat2, leopite, leopet1, lebeau3, leocite, leobel1, leofle1, leopon1, leomair, leogal, leomou1, leoleod, leomou2, leogal2, leochat, isqresi, isqhame, isqmair, isqcast, isqegli, isqvill] is not strictly sorted by increasing stop_sequence
trip_id 20575985 stop_sequence for stop_ids [bsmfem1, bsmcca11, bsmdal1, bsmpalb, bsmedou, bsmeurv, bsmstad, bsmest, bsmvatre, bsmcenl, bsmbran3, smbgide, smbfbou, bsmrho, bsmval, bsmfem1, bsmmarc, bsmbell, bsmdocq, bsmpane, bsmqueh2, bsmmont, bsmampe, bsmhfa, bsmcase, bsmsncf, bsmdaun, bsmcc11r] is not strictly sorted by increasing stop_sequence
trip_id 20472984 stop_sequence for stop_ids [bsmfem1, bsmdal1, bsmpalb, bsmedou, bsmeurv, bsmstad, bsmest, bsmvatre, bsmcenl, bsmbran3, bsmval, bsmfem1, bsmmarc, bsmbell, bsmdocq, bsmpane, bsmqueh2, bsmmont, bsmampe, bsmhfa, bsmcase, bsmblum4, bsmboucl, bsmcolo, bsmdet1, bsmdute, bsmfbui, bsmjver, bsmdal1] is not strictly sorted by increasing stop_sequence
trip_id 20472983 stop_sequence for stop_ids [bsmfem1, bsmdal1, bsmeurv, bsmstad, bsmest, bsmvatre, bsmcenl, bsmbran3, bsmval, bsmfem1, bsmmarc, bsmbell, bsmdocq, bsmpane, bsmqueh2, bsmmont, bsmampe, bsmhfa, bsmcase, bsmblum4, bsmboucl, bsmcolo, bsmdet1, bsmdute, bsmfbui, bsmjver, bsmdal1] is not strictly sorted by increasing stop_sequence
trip_id 20477345 stop_sequence for stop_ids [outmds2, outcol3, outlep1, outlep2, outlep2, outplac2, equmin, outserv, outmont2, outpeu2, outorm2, outaisn4, outmds2, outrena2, outeco2, outmazu2, outkenn, outlep1, outplac2, outpost, outbiez, outpres2, outdeni3, outlibe2, outlal2, outnce2, outsir2, bsmvie, bsmsncf, bsmdaun, bsmcc11r] is not strictly sorted by increasing stop_sequence

GTFS-rt stop_sequence isn't provided for trip that visits same stop_id more than once E009 9 errors

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

Sample errors

trip_id 21274340 visits stop_id [bsmcaa] more than once and GTFS-rt stop_time_update is missing stop_sequence field - stop_sequence must be provided
trip_id 21274341 visits stop_id [bsmcap] more than once and GTFS-rt stop_time_update is missing stop_sequence field - stop_sequence must be provided
trip_id 20473017 visits stop_id [bsmdal1] more than once and GTFS-rt stop_time_update is missing stop_sequence field - stop_sequence must be provided
trip_id 20473018 visits stop_id [bsmdal1] more than once and GTFS-rt stop_time_update is missing stop_sequence field - stop_sequence must be provided
trip_id 20473019 visits stop_id [bsmdal1] more than once and GTFS-rt stop_time_update is missing stop_sequence field - stop_sequence must be provided

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 20477830 stop_id leobeau does not exist in GTFS data stops.txt

Sequential stop_time_update times are not increasing E022 108 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 20477515 stop_id wimmair departure_time 09:01:00 (1751698860) is less than previous stop departure_time 09:06:13 (1751699173) - times must increase between two sequential stops
trip_id 20477515 stop_id wimmair departure_time 09:01:00 (1751698860) is less than previous stop arrival_time 09:06:13 (1751699173) - times must increase between two sequential stops
trip_id 20477515 stop_id wimnapo2 arrival_time 09:02:18 (1751698938) is less than previous stop arrival_time 09:06:13 (1751699173) - times must increase between two sequential stops
trip_id 20477515 stop_id wimnapo2 departure_time 09:02:18 (1751698938) is less than previous stop arrival_time 09:06:13 (1751699173) - times must increase between two sequential stops
trip_id 20477507 stop_id wimmair departure_time 08:08:00 (1751695680) is less than previous stop departure_time 08:12:11 (1751695931) - times must increase between two sequential stops

Sequential stop_time_updates have the same stop_id E037 4 errors

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

Sample errors

trip_id 20477515 has repeating stop_id wimmair2 - sequential stop_ids should be different
trip_id 20477510 has repeating stop_id wimmair2 - sequential stop_ids should be different
trip_id 20477345 has repeating stop_id outlep2 - sequential stop_ids should be different
trip_id 20477347 has repeating stop_id outlep2 - sequential stop_ids should be different

Warnings

vehicle_id not populated W002 39 errors

vehicle_id should be populated for TripUpdates and VehiclePositions

Sample errors

trip_id 20477515 does not have a vehicle_id
trip_id 21274340 does not have a vehicle_id
trip_id 21274341 does not have a vehicle_id
trip_id 20477510 does not have a vehicle_id
trip_id 20759469 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
E022	stop_time_update arrival/departure times between sequential stops should always increase - they should never be the same or decrease.	2 333	31 times (100 % of validations)
W002	vehicle_id should be populated for TripUpdates and VehiclePositions	977	31 times (100 % of validations)
E002	stop_time_updates for a given trip_id must be strictly sorted by increasing stop_sequence	164	28 times (90 % of validations)
E011	All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt	59	28 times (90 % of validations)
E037	Sequential GTFS-rt trip stop_time_updates shouldn't have the same stop_id	83	28 times (90 % 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	81	24 times (77 % of validations)

GTFS-RT feed content

Entities

Entities present in this feed at 2025-07-06 at 03:35 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-07-06 at 03:35 Europe/Paris. You can look at the GTFS-RT documentation.


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