gtfs-rt Transport open dataset - Données en temps réel des horaires aux arrêts du réseau Astrobus for Réseau urbain Astrobus

Resource details

File name: Données en temps réel des horaires aux arrêts du réseau Astrobus

Format: gtfs-rt

GTFS-RT (protobuff) des horaires aux arrêts

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

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

❌252 errors, 39 warnings

Validation carried out using the current GTFS file and the GTFS-RT the 2025-06-30 at 09:10 Europe/Paris using the MobilityData GTFS-RT validator.

Errors

stop_times_updates not strictly sorted E002 6 errors

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

Sample errors

trip_id ATOUMOD036:ServiceJourney:4644982938927104x4:LOC stop_sequence [10, 2] is not strictly sorted by increasing stop_sequence
trip_id ATOUMOD036:ServiceJourney:5858591379554304x4:LOC stop_sequence [10, 14, 2, 12, 4, 3, 11, 9, 13, 1] is not strictly sorted by increasing stop_sequence
trip_id ATOUMOD036:ServiceJourney:4886062657699840x7:LOC stop_sequence [8, 12, 18, 7] is not strictly sorted by increasing stop_sequence
trip_id ATOUMOD036:ServiceJourney:5060085219852288x2:LOC stop_sequence [11, 4] is not strictly sorted by increasing stop_sequence
trip_id ATOUMOD036:ServiceJourney:4886062657699840x8:LOC stop_sequence [12, 16, 9] is not strictly sorted by increasing stop_sequence

Sequential stop_time_update times are not increasing E022 212 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 ATOUMOD036:ServiceJourney:4644982938927104x4:LOC stop_sequence 2 arrival_time 08:55:55 (1751266555) is less than previous stop arrival_time 09:03:32 (1751267012) - times must increase between two sequential stops
trip_id ATOUMOD036:ServiceJourney:4644982938927104x4:LOC stop_sequence 2 arrival_time 08:55:55 (1751266555) is less than previous stop departure_time 09:03:48 (1751267028) - times must increase between two sequential stops
trip_id ATOUMOD036:ServiceJourney:4644982938927104x4:LOC stop_sequence 2 departure_time 08:56:06 (1751266566) is less than previous stop departure_time 09:03:48 (1751267028) - times must increase between two sequential stops
trip_id ATOUMOD036:ServiceJourney:4644982938927104x4:LOC stop_sequence 2 departure_time 08:56:06 (1751266566) is less than previous stop arrival_time 09:03:32 (1751267012) - times must increase between two sequential stops
trip_id ATOUMOD036:ServiceJourney:4644982938927104x4:LOC stop_sequence 4 arrival_time 08:57:21 (1751266641) is less than previous stop arrival_time 09:03:18 (1751266998) - times must increase between two sequential stops

trip direction_id does not match GTFS data E024 13 errors

GTFS-rt trip direction_id must match the direction_id in GTFS trips.txt

Sample errors

GTFS-rt trip_id ATOUMOD036:ServiceJourney:4644982938927104x4:LOC trip.direction_id is 1 but GTFS trip.direction_id is 0 - direction_id does not match
GTFS-rt trip_id ATOUMOD036:ServiceJourney:5477981779656704x3:LOC trip.direction_id is 1 but GTFS trip.direction_id is 0 - direction_id does not match
GTFS-rt trip_id ATOUMOD036:ServiceJourney:5858591379554304x4:LOC trip.direction_id is 2 but GTFS trip.direction_id is 1 - direction_id does not match
GTFS-rt trip_id ATOUMOD036:ServiceJourney:5477981779656704x5:LOC trip.direction_id is 1 but GTFS trip.direction_id is 0 - direction_id does not match
GTFS-rt trip_id ATOUMOD036:ServiceJourney:4886062657699840x7:LOC trip.direction_id is 1 but GTFS trip.direction_id is 0 - direction_id does not match

GTFS-rt stop_time_update stop_sequence and stop_id do not match GTFS E045 9 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 ATOUMOD036:ServiceJourney:5858591379554304x4:LOC stop_sequence 10 has stop_id FR:14366:ZE:5170005:ATOUMOD036 but GTFS stop_sequence 10 has stop_id FR:14366:ZE:605820044:ATOUMOD036 - stop_ids should be the same
GTFS-rt trip_id ATOUMOD036:ServiceJourney:4886062657699840x7:LOC stop_sequence 8 has stop_id FR:14366:ZE:25050002:ATOUMOD036 but GTFS stop_sequence 8 has stop_id FR:14366:ZE:1200004:ATOUMOD036 - stop_ids should be the same
GTFS-rt trip_id ATOUMOD036:ServiceJourney:4886062657699840x7:LOC stop_sequence 12 has stop_id FR:14366:ZE:5117418345070592:ATOUMOD036 but GTFS stop_sequence 12 has stop_id FR:14366:ZE:4784504850874368:ATOUMOD036 - stop_ids should be the same
GTFS-rt trip_id ATOUMOD036:ServiceJourney:4886062657699840x7:LOC stop_sequence 18 has stop_id FR:14366:ZE:33070004:ATOUMOD036 but GTFS stop_sequence 18 has stop_id FR:14366:ZE:5180281390628864:ATOUMOD036 - stop_ids should be the same
GTFS-rt trip_id ATOUMOD036:ServiceJourney:4800034672476160x5:LOC stop_sequence 12 has stop_id FR:14366:ZE:35180002:ATOUMOD036 but GTFS stop_sequence 12 has stop_id FR:14366:ZE:33090002:ATOUMOD036 - stop_ids should be the same

GTFS-rt stop_sequence not found in GTFS data E051 12 errors

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 ATOUMOD036:ServiceJourney:4644982938927104x4:LOC contains stop_sequence 2 that does not exist in GTFS stop_times.txt for this trip
GTFS-rt trip_id ATOUMOD036:ServiceJourney:5477981779656704x3:LOC contains stop_sequence 28 that does not exist in GTFS stop_times.txt for this trip
GTFS-rt trip_id ATOUMOD036:ServiceJourney:5477981779656704x5:LOC contains stop_sequence 28 that does not exist in GTFS stop_times.txt for this trip
GTFS-rt trip_id ATOUMOD036:ServiceJourney:4886062657699840x7:LOC contains stop_sequence 7 that does not exist in GTFS stop_times.txt for this trip
GTFS-rt trip_id ATOUMOD036:ServiceJourney:5060085219852288x2:LOC contains stop_sequence 4 that does not exist in GTFS stop_times.txt for this trip

Warnings

vehicle_id not populated W002 13 errors

vehicle_id should be populated for TripUpdates and VehiclePositions

Sample errors

trip_id ATOUMOD036:ServiceJourney:4644982938927104x4:LOC does not have a vehicle_id
trip_id ATOUMOD036:ServiceJourney:5477981779656704x3:LOC does not have a vehicle_id
trip_id ATOUMOD036:ServiceJourney:5858591379554304x4:LOC does not have a vehicle_id
trip_id ATOUMOD036:ServiceJourney:5477981779656704x5:LOC does not have a vehicle_id
trip_id ATOUMOD036:ServiceJourney:4886062657699840x7:LOC does not have a vehicle_id

schedule_relationship not populated W009 26 errors

trip.schedule_relationship and stop_time_update.schedule_relationship should be populated

Sample errors

trip_id ATOUMOD036:ServiceJourney:4644982938927104x4:LOC stop_sequence 10 (and potentially more for this trip) does not have a schedule_relationship
trip_id ATOUMOD036:ServiceJourney:4644982938927104x4:LOC does not have a schedule_relationship
trip_id ATOUMOD036:ServiceJourney:5477981779656704x3:LOC stop_sequence 22 (and potentially more for this trip) does not have a schedule_relationship
trip_id ATOUMOD036:ServiceJourney:5477981779656704x3:LOC does not have a schedule_relationship
trip_id ATOUMOD036:ServiceJourney:5858591379554304x4:LOC stop_sequence 10 (and potentially more for this trip) does not have a schedule_relationship

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
E002	stop_time_updates for a given trip_id must be strictly sorted by increasing stop_sequence	114	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 719	29 times (100 % of validations)
E024	GTFS-rt trip direction_id must match the direction_id in GTFS trips.txt	206	29 times (100 % 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	101	29 times (100 % of validations)
E051	All stop_time_update stop_sequences in GTFS-realtime data must appear in GTFS stop_times.txt for that trip	157	29 times (100 % of validations)
W002	vehicle_id should be populated for TripUpdates and VehiclePositions	230	29 times (100 % of validations)
W009	trip.schedule_relationship and stop_time_update.schedule_relationship should be populated	460	29 times (100 % of validations)
E003	All trip_ids provided in the GTFS-rt feed must exist in the GTFS data, unless the schedule_relationship is ADDED	24	12 times (41 % of validations)
E004	All route_ids provided in the GTFS-rt feed must exist in the GTFS data	11	9 times (31 % of validations)
E011	All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt	16	9 times (31 % of validations)

GTFS-RT feed content

Entities

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


{
  "header": {
    "gtfsRealtimeVersion": "1.0",
    "timestamp": "1751339126"
  }
}