Détails de la ressource
GTFS-RT (protobuff) des horaires aux arrêts.
Cette ressource fait partie du jeu de données Réseau urbain Néva.
Disponibilité au téléchargement
En savoir plus
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 erreurs, 25 avertissements
Validation effectuée en utilisant le fichier GTFS en vigueur et le GTFS-RT, le 07/11/2025 à 08h13 Europe/Paris avec le validateur GTFS-RT de MobilityData.
Erreurs
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:5272474594836480x1:LOC does not exist in the GTFS data and does not have schedule_relationship of ADDED
- trip_id ATOUMOD105:ServiceJourney:5948264101707776x1:LOC does not exist in the GTFS data and does not have schedule_relationship of ADDED
- trip_id ATOUMOD105:ServiceJourney:5948264101707776x2:LOC does not exist in the GTFS data and does not have schedule_relationship of ADDED
- trip_id ATOUMOD105:ServiceJourney:5272474594836480x2:LOC does not exist in the GTFS data and does not have schedule_relationship of ADDED
- trip_id ATOUMOD105:ServiceJourney:6476671109562368x0:LOC does not exist in the GTFS data and does not have schedule_relationship of ADDED
Avertissements
vehicle_id not populated W002 8 erreurs
vehicle_id should be populated for TripUpdates and VehiclePositions
Exemples d'erreurs
- trip_id ATOUMOD105:ServiceJourney:5272474594836480x1:LOC does not have a vehicle_id
- trip_id ATOUMOD105:ServiceJourney:5948264101707776x1:LOC does not have a vehicle_id
- trip_id ATOUMOD105:ServiceJourney:5948264101707776x2:LOC does not have a vehicle_id
- trip_id ATOUMOD105:ServiceJourney:5272474594836480x2:LOC does not have a vehicle_id
- trip_id ATOUMOD105:ServiceJourney:6476671109562368x0:LOC does not have a vehicle_id
Header timestamp is older than 65 seconds W008 1 erreur
The data in a GTFS-realtime feed should always be less than one minute old
Exemples d'erreurs
- header.timestamp is 3 min 31 sec old which is greater than the recommended age of 65 seconds
schedule_relationship not populated W009 16 erreurs
trip.schedule_relationship and stop_time_update.schedule_relationship should be populated
Exemples d'erreurs
- trip_id ATOUMOD105:ServiceJourney:5272474594836480x1:LOC stop_sequence 22 (and potentially more for this trip) does not have a schedule_relationship
- trip_id ATOUMOD105:ServiceJourney:5272474594836480x1:LOC does not have a schedule_relationship
- trip_id ATOUMOD105:ServiceJourney:5948264101707776x1:LOC stop_sequence 11 (and potentially more for this trip) does not have a schedule_relationship
- trip_id ATOUMOD105:ServiceJourney:5948264101707776x1:LOC does not have a schedule_relationship
- trip_id ATOUMOD105:ServiceJourney:5948264101707776x2:LOC stop_sequence 1 (and potentially more for this trip) does not have a schedule_relationship
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 |
|---|---|---|---|
| E003 | All trip_ids provided in the GTFS-rt feed must exist in the GTFS data, unless the schedule_relationship is ADDED | 156 | 22 fois (73 % des validations) |
| W002 | vehicle_id should be populated for TripUpdates and VehiclePositions | 156 | 22 fois (73 % des validations) |
| W009 | trip.schedule_relationship and stop_time_update.schedule_relationship should be populated | 312 | 22 fois (73 % des validations) |
| W008 | The data in a GTFS-realtime feed should always be less than one minute old | 12 | 12 fois (40 % des validations) |
Contenu du flux GTFS-RT
Entités
Entités présentes dans ce flux le 07/11/2025 à 22h52 Europe/Paris.
trip_updates (2) vehicle_positions (0) service_alerts (0)Entités présentes dans ce flux lors des 7 derniers jours.
trip_updatesFlux GTFS-RT décodé
Voir le contenu du flux
Voici le flux GTFS-RT décodé au format Protobuf le 07/11/2025 à 22h52 Europe/Paris. Vous pouvez consulter la documentation GTFS-RT.
{
"entity": [
{
"id": "SM:ATOUMOD105:ServiceJourney:5272474594836480x18:LOC",
"tripUpdate": {
"stopTimeUpdate": [
{
"arrival": {
"delay": 11993,
"time": "1762552303"
},
"departure": {
"delay": 11993,
"time": "1762552313"
},
"stopId": "FR:50218:ZE:720520001:ATOUMOD105",
"stopSequence": 34
},
{
"arrival": {
"delay": 11981,
"time": "1762552361"
},
"stopId": "FR:50647:ZE:752300002:ATOUMOD105",
"stopSequence": 35
}
],
"timestamp": "1762552233",
"trip": {
"routeId": "ATOUMOD105:Line:348940035:LOC",
"tripId": "ATOUMOD105:ServiceJourney:5272474594836480x18:LOC"
}
}
},
{
"id": "SM:ATOUMOD105:ServiceJourney:6476671109562368x19:LOC",
"tripUpdate": {
"stopTimeUpdate": [
{
"arrival": {
"delay": 9892,
"time": "1762552312"
},
"stopId": "FR:50532:ZE:753630002:ATOUMOD105",
"stopSequence": 35
}
],
"timestamp": "1762552128",
"trip": {
"directionId": 1,
"routeId": "ATOUMOD105:Line:348940035:LOC",
"tripId": "ATOUMOD105:ServiceJourney:6476671109562368x19:LOC"
}
}
}
],
"header": {
"gtfsRealtimeVersion": "1.0",
"timestamp": "1762552362"
}
}