Resource details

File name: Données en temps réel de la position des véhicules du réseau SNGO
Format: gtfs-rt

GTFS-RT (protobuff) de la position des véhicules.

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

Download availability

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

10 errors, 5 warnings

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

Errors

GTFS-rt route_id does not exist in GTFS data E004 5 errors

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

Sample errors
  • vehicle_id 0200001002FD0758 route_id ATOUMOD007:Line:24:LOC does not exist in the GTFS data routes.txt
  • vehicle_id 0200001002FF7911 route_id ATOUMOD007:Line:22:LOC does not exist in the GTFS data routes.txt
  • vehicle_id 0200001002FD075E route_id ATOUMOD007:Line:21:LOC does not exist in the GTFS data routes.txt
  • vehicle_id 0200001002FD0734 route_id ATOUMOD007:Line:23:LOC does not exist in the GTFS data routes.txt
  • vehicle_id 0200001002FD0748 route_id ATOUMOD007:Line:26:LOC does not exist in the GTFS data routes.txt

trip direction_id does not match GTFS data E024 2 errors

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

Sample errors
  • GTFS-rt vehicle_id 0200001002FD075E trip_id ATOUMOD007:ServiceJourney:621:LOC trip.direction_id is 1 but GTFS trip.direction_id is 0 - direction_id does not match
  • GTFS-rt vehicle_id 0200001002FD0734 trip_id ATOUMOD007:ServiceJourney:599:LOC trip.direction_id is 1 but GTFS trip.direction_id is 0 - direction_id does not match

Vehicle position far from trip shape E029 2 errors

The vehicle position should be within a certain distance of the GTFS shapes.txt data for the current trip unless there is a Service Alert with the Effect of DETOUR for this trip_id.

Sample errors
  • vehicle.id 0200001002FD0734 trip_id ATOUMOD007:ServiceJourney:599:LOC at (49.09062,1.489472) is more than 200.0 meters (0.12 mile(s)) from the GTFS trip shape - vehicle should be near trip shape or on DETOUR
  • vehicle.id 0200001002FD0748 trip_id ATOUMOD007:ServiceJourney:597:LOC at (49.09396,1.472297) is more than 200.0 meters (0.12 mile(s)) from the GTFS trip shape - vehicle should be near trip shape or on DETOUR

timestamp is in the future E050 1 error

All timestamps must be less than the current time

Sample errors
  • header.timestamp 09:08:33 (1746860913) is 1 min 12 sec greater than 09:07:20 (1746860840547) - the current time in milliseconds

Warnings

schedule_relationship not populated W009 5 errors

trip.schedule_relationship and stop_time_update.schedule_relationship should be populated

Sample errors
  • trip_id ATOUMOD007:ServiceJourney:611:LOC does not have a schedule_relationship
  • trip_id ATOUMOD007:ServiceJourney:609:LOC does not have a schedule_relationship
  • trip_id ATOUMOD007:ServiceJourney:621:LOC does not have a schedule_relationship
  • trip_id ATOUMOD007:ServiceJourney:599:LOC does not have a schedule_relationship
  • trip_id ATOUMOD007:ServiceJourney:597:LOC 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
E004 All route_ids provided in the GTFS-rt feed must exist in the GTFS data 9 2 times (67 % of validations)
E029 The vehicle position should be within a certain distance of the GTFS shapes.txt data for the current trip unless there is a Service Alert with the Effect of DETOUR for this trip_id. 5 2 times (67 % of validations)
W009 trip.schedule_relationship and stop_time_update.schedule_relationship should be populated 9 2 times (67 % of validations)
E024 GTFS-rt trip direction_id must match the direction_id in GTFS trips.txt 2 1 times (33 % of validations)
E050 All timestamps must be less than the current time 1 1 times (33 % 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.