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

2026-02-08
87%
2026-02-09
99.5%
2026-02-10
100%
2026-02-11
100%
2026-02-12
100%
2026-02-13
100%
2026-02-14
100%
2026-02-15
100%
2026-02-16
100%
2026-02-17
100%
2026-02-18
99.8%
2026-02-19
100%
2026-02-20
100%
2026-02-21
100%
2026-02-22
100%
2026-02-23
100%
2026-02-24
100%
2026-02-25
100%
2026-02-26
100%
2026-02-27
100%
2026-02-28
100%
2026-03-01
100%
2026-03-02
100%
2026-03-03
98.1%
2026-03-04
100%
2026-03-05
100%
2026-03-06
100%
2026-03-07
100%
2026-03-08
96.6%
2026-03-09
100%
2026-03-10
100%
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

8 errors, 4 warnings

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

Errors

GTFS-rt trip_id does not exist in GTFS data and does not have schedule_relationship of ADDED E003 4 errors

All trip_ids provided in the GTFS-rt feed must exist in the GTFS data, unless the schedule_relationship is ADDED

Sample errors
  • vehicle_id 0200001002FD0758 trip_id ATOUMOD007:ServiceJourney:307:LOC does not exist in the GTFS data and does not have schedule_relationship of ADDED
  • vehicle_id 0200001002FD0734 trip_id ATOUMOD007:ServiceJourney:281:LOC does not exist in the GTFS data and does not have schedule_relationship of ADDED
  • vehicle_id 0200001002FD0751 trip_id ATOUMOD007:ServiceJourney:379:LOC does not exist in the GTFS data and does not have schedule_relationship of ADDED
  • vehicle_id 0200001002FD0748 trip_id ATOUMOD007:ServiceJourney:409:LOC 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 4 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:26:LOC does not exist in the GTFS data routes.txt
  • vehicle_id 0200001002FD0734 route_id ATOUMOD007:Line:22:LOC does not exist in the GTFS data routes.txt
  • vehicle_id 0200001002FD0751 route_id ATOUMOD007:Line:26:LOC does not exist in the GTFS data routes.txt
  • vehicle_id 0200001002FD0748 route_id ATOUMOD007:Line:25:LOC does not exist in the GTFS data routes.txt

Warnings

schedule_relationship not populated W009 4 errors

trip.schedule_relationship and stop_time_update.schedule_relationship should be populated

Sample errors
  • trip_id ATOUMOD007:ServiceJourney:307:LOC does not have a schedule_relationship
  • trip_id ATOUMOD007:ServiceJourney:281:LOC does not have a schedule_relationship
  • trip_id ATOUMOD007:ServiceJourney:379:LOC does not have a schedule_relationship
  • trip_id ATOUMOD007:ServiceJourney:409: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
E003 All trip_ids provided in the GTFS-rt feed must exist in the GTFS data, unless the schedule_relationship is ADDED 97 26 times (87 % of validations)
E004 All route_ids provided in the GTFS-rt feed must exist in the GTFS data 97 26 times (87 % of validations)
W009 trip.schedule_relationship and stop_time_update.schedule_relationship should be populated 97 26 times (87 % of validations)
E028 The vehicle position should be inside the agency coverage area. This is defined as within roughly 1/8 of a mile (200 meters) of the GTFS shapes.txt data, or stops.txt locations if the GTFS feed doesn't include shapes.txt. 6 6 times (20 % of validations)
W008 The data in a GTFS-realtime feed should always be less than one minute old 1 1 times (3 % of validations)

GTFS-RT feed content

Entities

Entities present in this feed at 2026-03-10 at 08:28 Europe/Paris.

vehicle_positions (4) service_alerts (0) trip_updates (0)

Entities seen in the last 7 days.

vehicle_positions

Decoded GTFS-RT feed

See full payload

Here is the decoded GTFS-RT feed Protobuf at 2026-03-10 at 08:28 Europe/Paris. You can look at the GTFS-RT documentation.

{ "entity": [ { "id": "VM:ATOUMOD007:ServiceJourney:409:LOC", "vehicle": { "position": { "bearing": 231.0, "latitude": 49.10103988647461, "longitude": 1.4494309425354004 }, "timestamp": "1773127623", "trip": { "directionId": 1, "routeId": "ATOUMOD007:Line:25:LOC", "tripId": "ATOUMOD007:ServiceJourney:409:LOC" }, "vehicle": { "id": "0200001002FD0748" } } }, { "id": "VM:ATOUMOD007:ServiceJourney:397:LOC", "vehicle": { "position": { "bearing": 207.0, "latitude": 49.10789108276367, "longitude": 1.499750018119812 }, "timestamp": "1773127610", "trip": { "directionId": 1, "routeId": "ATOUMOD007:Line:24:LOC", "tripId": "ATOUMOD007:ServiceJourney:397:LOC" }, "vehicle": { "id": "0200001002FD0734" } } }, { "id": "VM:ATOUMOD007:ServiceJourney:461:LOC", "vehicle": { "position": { "bearing": 139.0, "latitude": 49.079750061035156, "longitude": 1.4872939586639404 }, "timestamp": "1773127619", "trip": { "routeId": "ATOUMOD007:Line:23:LOC", "tripId": "ATOUMOD007:ServiceJourney:461:LOC" }, "vehicle": { "id": "0200001002FD0758" } } }, { "id": "VM:ATOUMOD007:ServiceJourney:495:LOC", "vehicle": { "position": { "latitude": 49.10382843017578, "longitude": 1.4435969591140747 }, "timestamp": "1773127582", "trip": { "routeId": "ATOUMOD007:Line:26:LOC", "tripId": "ATOUMOD007:ServiceJourney:495:LOC" }, "vehicle": { "id": "0200001002FD0751" } } } ], "header": { "gtfsRealtimeVersion": "1.0", "timestamp": "1773127736" } }