Jeu de données ouvert gtfs-rt - Base de données multimodale des horaires aux arrêts des réseaux de transport public normands en temps réel pour Agrégat des réseaux urbains et interurbains de Normandie

Détails de la ressource

Nom du fichier : Base de données multimodale des horaires aux arrêts des réseaux de transport public normands en temps réel

Format : gtfs-rt

Télécharger

La base de données multimodale présente de manière agrégée les horaires et les arrêts des réseaux de transport public normands en temps réel. Elle est le support du calculateur d’itinéraires Atoumod.fr, piloté par le Syndicat mixte Atoumod.

Cette ressource fait partie du jeu de données Agrégat des réseaux urbains et interurbains de Normandie.

Disponibilité au téléchargement

Nous testons la disponibilité de cette ressource au téléchargement toutes les heures, en effectuant une requête HTTP de type HEAD dont le temps de réponse doit être inférieur à 5 secondes. Si nous détectons une indisponibilité, nous effectuons un nouveau test toutes les 10 minutes, jusqu'à ce que la ressource soit à nouveau disponible.

Pour les flux SIRI et SIRI Lite, nous effectuons une requête HTTP de type GET : nous considérons une réponse avec un code 401 ou 405 comme étant disponible. En cas d'erreur 500, nous considèrerons que le flux est indisponible, sauf si il semble contenir du SOAP.

Rapport de validation

❌8 065 erreurs, 666 avertissements

Les shapes présentes dans le GTFS ont été ignorées, certaines règles de validation n'ont pas été vérifiées.

Validation effectuée en utilisant le fichier GTFS en vigueur et le GTFS-RT, le 25/10/2025 à 09h04 Europe/Paris avec le validateur GTFS-RT de MobilityData.

Erreurs

stop_times_updates not strictly sorted E002 177 erreurs

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

Exemples d'erreurs

trip_id ATOUMOD003:ServiceJourney:4048282x2025x26xGSamHLiaxSamedix00:LOC stop_sequence [9, 46, 5] is not strictly sorted by increasing stop_sequence
trip_id ATOUMOD003:ServiceJourney:4155794x2025x26xGSamHTNIxSamedix00:LOC stop_sequence [23, 27, 29, 28] is not strictly sorted by increasing stop_sequence
trip_id ATOUMOD003:ServiceJourney:4011347x2025x26xGSamHLiaxSamedix00:LOC stop_sequence [43, 41] is not strictly sorted by increasing stop_sequence
trip_id ATOUMOD003:ServiceJourney:4048305x2025x26xGSamHLiaxSamedix00:LOC stop_sequence [28, 53, 31] is not strictly sorted by increasing stop_sequence
trip_id ATOUMOD005:ServiceJourney:279:LOC stop_sequence [19, 6] is not strictly sorted by increasing stop_sequence

GTFS-rt trip_id does not exist in GTFS data and does not have schedule_relationship of ADDED E003 8 erreurs

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

Exemples d'erreurs

trip_id ATOUMOD105:ServiceJourney:4897322119987200x6:LOC does not exist in the GTFS data and does not have schedule_relationship of ADDED
trip_id ATOUMOD105:ServiceJourney:6025701196038144x3:LOC does not exist in the GTFS data and does not have schedule_relationship of ADDED
trip_id ATOUMOD105:ServiceJourney:4925753863962624x2:LOC does not exist in the GTFS data and does not have schedule_relationship of ADDED
trip_id ATOUMOD105:ServiceJourney:4804422312919040x1:LOC does not exist in the GTFS data and does not have schedule_relationship of ADDED
trip_id ATOUMOD105:ServiceJourney:4897322119987200x3:LOC does not exist in the GTFS data and does not have schedule_relationship of ADDED

GTFS-rt stop_id does not exist in GTFS data E011 2 erreurs

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

Exemples d'erreurs

trip_id ATOUMOD041:ServiceJourney:4:LOC stop_id FR:76057:ZE:30050:ATOUMOD041 does not exist in GTFS data stops.txt
trip_id ATOUMOD041:ServiceJourney:8:LOC stop_id FR:76057:ZE:30050:ATOUMOD041 does not exist in GTFS data stops.txt

Sequential stop_time_update times are not increasing E022 7 425 erreurs

stop_time_update arrival/departure times between sequential stops should always increase - they should never be the same or decrease.

Exemples d'erreurs

trip_id ATOUMOD003:ServiceJourney:4048282x2025x26xGSamHLiaxSamedix00:LOC stop_sequence 5 arrival_time 09:13:37 (1761376417) is less than previous stop arrival_time 09:56:00 (1761378960) - times must increase between two sequential stops
trip_id ATOUMOD003:ServiceJourney:4048282x2025x26xGSamHLiaxSamedix00:LOC stop_sequence 5 arrival_time 09:13:37 (1761376417) is less than previous stop departure_time 09:56:00 (1761378960) - times must increase between two sequential stops
trip_id ATOUMOD003:ServiceJourney:4048282x2025x26xGSamHLiaxSamedix00:LOC stop_sequence 5 departure_time 09:13:37 (1761376417) is less than previous stop departure_time 09:56:00 (1761378960) - times must increase between two sequential stops
trip_id ATOUMOD003:ServiceJourney:4048282x2025x26xGSamHLiaxSamedix00:LOC stop_sequence 5 departure_time 09:13:37 (1761376417) is less than previous stop arrival_time 09:56:00 (1761378960) - times must increase between two sequential stops
trip_id ATOUMOD003:ServiceJourney:4048282x2025x26xGSamHLiaxSamedix00:LOC stop_sequence 48 arrival_time 09:59:38 (1761379178) is less than previous stop arrival_time 10:03:00 (1761379380) - times must increase between two sequential stops

trip direction_id does not match GTFS data E024 213 erreurs

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

Exemples d'erreurs

GTFS-rt trip_id ATOUMOD003:ServiceJourney:4048282x2025x26xGSamHLiaxSamedix00:LOC trip.direction_id is 1 but GTFS trip.direction_id is 0 - direction_id does not match
GTFS-rt trip_id ATOUMOD003:ServiceJourney:4155794x2025x26xGSamHTNIxSamedix00:LOC trip.direction_id is 2 but GTFS trip.direction_id is 1 - direction_id does not match
GTFS-rt trip_id ATOUMOD003:ServiceJourney:4011347x2025x26xGSamHLiaxSamedix00:LOC trip.direction_id is 1 but GTFS trip.direction_id is 0 - direction_id does not match
GTFS-rt trip_id ATOUMOD003:ServiceJourney:4048305x2025x26xGSamHLiaxSamedix00:LOC trip.direction_id is 2 but GTFS trip.direction_id is 1 - direction_id does not match
GTFS-rt trip_id ATOUMOD005:ServiceJourney:279: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 58 erreurs

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

Exemples d'erreurs

GTFS-rt trip_id ATOUMOD003:ServiceJourney:4155794x2025x26xGSamHTNIxSamedix00:LOC stop_sequence 23 has stop_id FR:76239:ZE:5110:ATOUMOD003 but GTFS stop_sequence 23 has stop_id FR:76596:ZE:5106:ATOUMOD003 - stop_ids should be the same
GTFS-rt trip_id ATOUMOD003:ServiceJourney:4155794x2025x26xGSamHTNIxSamedix00:LOC stop_sequence 27 has stop_id FR:76296:ZE:4444:ATOUMOD003 but GTFS stop_sequence 27 has stop_id FR:76296:ZE:4442:ATOUMOD003 - stop_ids should be the same
GTFS-rt trip_id ATOUMOD003:ServiceJourney:4155794x2025x26xGSamHTNIxSamedix00:LOC stop_sequence 29 has stop_id FR:76305:ZE:4529:ATOUMOD003 but GTFS stop_sequence 29 has stop_id FR:76305:ZE:3395:ATOUMOD003 - stop_ids should be the same
GTFS-rt trip_id ATOUMOD003:ServiceJourney:4011347x2025x26xGSamHLiaxSamedix00:LOC stop_sequence 43 has stop_id FR:76447:ZE:3220:ATOUMOD003 but GTFS stop_sequence 43 has stop_id FR:76447:ZE:3120:ATOUMOD003 - stop_ids should be the same
GTFS-rt trip_id ATOUMOD007:ServiceJourney:805:LOC stop_sequence 8 has stop_id FR:27681:ZE:10071:ATOUMOD007 but GTFS stop_sequence 8 has stop_id FR:27562:ZE:10104:ATOUMOD007 - stop_ids should be the same

GTFS-rt stop_sequence not found in GTFS data E051 182 erreurs

All stop_time_update stop_sequences in GTFS-realtime data must appear in GTFS stop_times.txt for that trip

Exemples d'erreurs

GTFS-rt trip_id ATOUMOD003:ServiceJourney:4048282x2025x26xGSamHLiaxSamedix00:LOC contains stop_sequence 5 that does not exist in GTFS stop_times.txt for this trip
GTFS-rt trip_id ATOUMOD003:ServiceJourney:4155794x2025x26xGSamHTNIxSamedix00:LOC contains stop_sequence 28 that does not exist in GTFS stop_times.txt for this trip
GTFS-rt trip_id ATOUMOD003:ServiceJourney:4011347x2025x26xGSamHLiaxSamedix00:LOC contains stop_sequence 41 that does not exist in GTFS stop_times.txt for this trip
GTFS-rt trip_id ATOUMOD003:ServiceJourney:4048305x2025x26xGSamHLiaxSamedix00:LOC contains stop_sequence 31 that does not exist in GTFS stop_times.txt for this trip
GTFS-rt trip_id ATOUMOD005:ServiceJourney:279:LOC contains stop_sequence 6 that does not exist in GTFS stop_times.txt for this trip

Avertissements

vehicle_id not populated W002 222 erreurs

vehicle_id should be populated for TripUpdates and VehiclePositions

Exemples d'erreurs

trip_id ATOUMOD003:ServiceJourney:4048282x2025x26xGSamHLiaxSamedix00:LOC does not have a vehicle_id
trip_id ATOUMOD003:ServiceJourney:4155794x2025x26xGSamHTNIxSamedix00:LOC does not have a vehicle_id
trip_id ATOUMOD003:ServiceJourney:4011347x2025x26xGSamHLiaxSamedix00:LOC does not have a vehicle_id
trip_id ATOUMOD003:ServiceJourney:4048305x2025x26xGSamHLiaxSamedix00:LOC does not have a vehicle_id
trip_id ATOUMOD005:ServiceJourney:279:LOC does not have a vehicle_id

schedule_relationship not populated W009 444 erreurs

trip.schedule_relationship and stop_time_update.schedule_relationship should be populated

Exemples d'erreurs

trip_id ATOUMOD003:ServiceJourney:4048282x2025x26xGSamHLiaxSamedix00:LOC stop_sequence 9 (and potentially more for this trip) does not have a schedule_relationship
trip_id ATOUMOD003:ServiceJourney:4048282x2025x26xGSamHLiaxSamedix00:LOC does not have a schedule_relationship
trip_id ATOUMOD003:ServiceJourney:4155794x2025x26xGSamHTNIxSamedix00:LOC stop_sequence 23 (and potentially more for this trip) does not have a schedule_relationship
trip_id ATOUMOD003:ServiceJourney:4155794x2025x26xGSamHTNIxSamedix00:LOC does not have a schedule_relationship
trip_id ATOUMOD003:ServiceJourney:4011347x2025x26xGSamHLiaxSamedix00:LOC stop_sequence 43 (and potentially more for this trip) does not have a schedule_relationship

Valider ce GTFS-RT maintenant

Validations précédentes

Voici un récapitulatif des différents types d'erreurs constatés au cours des 30 derniers jours.

Identifiant d'erreur	Description	Nombre d'erreurs	Nombre d'occurences
E002	stop_time_updates for a given trip_id must be strictly sorted by increasing stop_sequence	10 849	30 fois (100 % des validations)
E022	stop_time_update arrival/departure times between sequential stops should always increase - they should never be the same or decrease.	496 714	30 fois (100 % des validations)
E024	GTFS-rt trip direction_id must match the direction_id in GTFS trips.txt	12 766	30 fois (100 % des 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	3 390	30 fois (100 % des validations)
E051	All stop_time_update stop_sequences in GTFS-realtime data must appear in GTFS stop_times.txt for that trip	9 954	30 fois (100 % des validations)
W002	vehicle_id should be populated for TripUpdates and VehiclePositions	13 655	30 fois (100 % des validations)
W009	trip.schedule_relationship and stop_time_update.schedule_relationship should be populated	27 101	30 fois (100 % des validations)
E003	All trip_ids provided in the GTFS-rt feed must exist in the GTFS data, unless the schedule_relationship is ADDED	886	26 fois (87 % des 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.	273	25 fois (83 % des validations)
E011	All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt	45	21 fois (70 % des validations)
E050	All timestamps must be less than the current time	12	12 fois (40 % des validations)
E004	All route_ids provided in the GTFS-rt feed must exist in the GTFS data	15	6 fois (20 % des validations)
E037	Sequential GTFS-rt trip stop_time_updates shouldn't have the same stop_id	5	5 fois (17 % des validations)
E040	All stop_time_updates must contain stop_id or stop_sequence - both fields cannot be left blank	13	2 fois (7 % des validations)
E043	If a stop_time_update doesn't have a schedule_relationship of SKIPPED or NO_DATA, then either arrival or departure must be provided	13	2 fois (7 % des validations)

Contenu du flux GTFS-RT

Entités

Entités présentes dans ce flux le 26/10/2025 à 05h57 Europe/Paris.

trip_updates (1) vehicle_positions (0) service_alerts (0)

Entités présentes dans ce flux lors des 7 derniers jours.

trip_updates

Flux GTFS-RT décodé

Voir le contenu du flux

Voici le flux GTFS-RT décodé au format Protobuf le 26/10/2025 à 05h57 Europe/Paris. Vous pouvez consulter la documentation GTFS-RT.


{
  "entity": [
    {
      "id": "SM:ATOUMOD003:ServiceJourney:4110791x2025x26xGDimTRAxDimanchex00:LOC",
      "tripUpdate": {
        "stopTimeUpdate": [
          {
            "arrival": {
              "delay": 47,
              "time": "1761454667"
            },
            "departure": {
              "delay": 47,
              "time": "1761454667"
            },
            "stopId": "FR:76351:ZE:3988:ATOUMOD003",
            "stopSequence": 3
          },
          {
            "arrival": {
              "delay": 34,
              "time": "1761456034"
            },
            "departure": {
              "delay": 34,
              "time": "1761456034"
            },
            "stopId": "FR:76351:ZE:3998:ATOUMOD003",
            "stopSequence": 15
          },
          {
            "arrival": {
              "delay": 54,
              "time": "1761455694"
            },
            "departure": {
              "delay": 54,
              "time": "1761455694"
            },
            "stopId": "FR:76351:ZE:3960:ATOUMOD003",
            "stopSequence": 11
          },
          {
            "arrival": {
              "delay": 38,
              "time": "1761455918"
            },
            "departure": {
              "delay": 38,
              "time": "1761455918"
            },
            "stopId": "FR:76351:ZE:3965:ATOUMOD003",
            "stopSequence": 14
          },
          {
            "arrival": {
              "delay": 11,
              "time": "1761454511"
            },
            "departure": {
              "delay": 11,
              "time": "1761454511"
            },
            "stopId": "FR:76351:ZE:3954:ATOUMOD003",
            "stopSequence": 2
          },
          {
            "arrival": {
              "delay": 90,
              "time": "1761454770"
            },
            "departure": {
              "delay": 90,
              "time": "1761454770"
            },
            "stopId": "FR:76351:ZE:4004:ATOUMOD003",
            "stopSequence": 4
          },
          {
            "arrival": {
              "delay": 62,
              "time": "1761455582"
            },
            "departure": {
              "delay": 62,
              "time": "1761455582"
            },
            "stopId": "FR:76351:ZE:4000:ATOUMOD003",
            "stopSequence": 10
          },
          {
            "arrival": {
              "delay": 37,
              "time": "1761454897"
            },
            "departure": {
              "delay": 37,
              "time": "1761454897"
            },
            "stopId": "FR:76351:ZE:3976:ATOUMOD003",
            "stopSequence": 5
          },
          {
            "arrival": {
              "delay": 56,
              "time": "1761455276"
            },
            "departure": {
              "delay": 56,
              "time": "1761455276"
            },
            "stopId": "FR:76351:ZE:3970:ATOUMOD003",
            "stopSequence": 8
          },
          {
            "departure": {
              "time": "1761454380"
            },
            "stopId": "FR:76481:ZE:4891:ATOUMOD003",
            "stopSequence": 1
          },
          {
            "arrival": {
              "delay": 73,
              "time": "1761456133"
            },
            "stopId": "FR:76351:ZE:3984:ATOUMOD003",
            "stopSequence": 16
          },
          {
            "arrival": {
              "delay": 81,
              "time": "1761455001"
            },
            "departure": {
              "delay": 81,
              "time": "1761455001"
            },
            "stopId": "FR:76351:ZE:3992:ATOUMOD003",
            "stopSequence": 6
          },
          {
            "arrival": {
              "delay": 92,
              "time": "1761455792"
            },
            "departure": {
              "delay": 92,
              "time": "1761455792"
            },
            "stopId": "FR:76351:ZE:3981:ATOUMOD003",
            "stopSequence": 12
          },
          {
            "arrival": {
              "delay": 85,
              "time": "1761455485"
            },
            "departure": {
              "delay": 85,
              "time": "1761455485"
            },
            "stopId": "FR:76351:ZE:3990:ATOUMOD003",
            "stopSequence": 9
          },
          {
            "arrival": {
              "delay": 79,
              "time": "1761455119"
            },
            "departure": {
              "delay": 79,
              "time": "1761455119"
            },
            "stopId": "FR:76351:ZE:3972:ATOUMOD003",
            "stopSequence": 7
          }
        ],
        "timestamp": "1761454595",
        "trip": {
          "directionId": 1,
          "routeId": "ATOUMOD003:Line:A:LOC",
          "tripId": "ATOUMOD003:ServiceJourney:4110791x2025x26xGDimTRAxDimanchex00:LOC"
        }
      }
    }
  ],
  "header": {
    "gtfsRealtimeVersion": "1.0",
    "timestamp": "1761454661"
  }
}