Resource details

File name: Données en temps réel des perturbations du réseau Néva
Format: gtfs-rt

GTFS-RT (protobuff) des perturbations.

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

Download availability

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

171 errors

Validation carried out using the current GTFS file and the GTFS-RT the 2025-01-23 at 08:09 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 14 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 zenbus:Vehicle:817050001:LOC trip_id 5110781483941888:1 does not exist in the GTFS data and does not have schedule_relationship of ADDED
  • trip_id 5110781483941888:1 does not exist in the GTFS data and does not have schedule_relationship of ADDED
  • vehicle_id zenbus:Vehicle:580690001:LOC trip_id 5110781483941888:2 does not exist in the GTFS data and does not have schedule_relationship of ADDED
  • trip_id 5110781483941888:2 does not exist in the GTFS data and does not have schedule_relationship of ADDED
  • vehicle_id zenbus:Vehicle:756460055:LOC trip_id 5119111304577024:1 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 14 errors

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

Sample errors
  • vehicle_id zenbus:Vehicle:817050001:LOC route_id zenbus:Line:350210009:LOC does not exist in the GTFS data routes.txt
  • route_id zenbus:Line:350210009:LOC does not exist in the GTFS data routes.txt
  • vehicle_id zenbus:Vehicle:580690001:LOC route_id zenbus:Line:350210009:LOC does not exist in the GTFS data routes.txt
  • route_id zenbus:Line:350210009:LOC does not exist in the GTFS data routes.txt
  • vehicle_id zenbus:Vehicle:756460055:LOC route_id zenbus:Line:348940035:LOC does not exist in the GTFS data routes.txt

GTFS-rt stop_id does not exist in GTFS data E011 141 errors

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

Sample errors
  • vehicle_id zenbus:Vehicle:817050001:LOC stop_id zenbus:StopPoint:SP:761950002:LOC does not exist in GTFS data stops.txt
  • trip_id 5110781483941888:1 stop_id zenbus:StopPoint:SP:748700002:LOC does not exist in GTFS data stops.txt
  • trip_id 5110781483941888:1 stop_id zenbus:StopPoint:SP:761950002:LOC does not exist in GTFS data stops.txt
  • trip_id 5110781483941888:1 stop_id zenbus:StopPoint:SP:756080004:LOC does not exist in GTFS data stops.txt
  • trip_id 5110781483941888:1 stop_id zenbus:StopPoint:SP:759830003:LOC does not exist in GTFS data stops.txt

Sequential stop_time_update times are not increasing E022 2 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 5119111304577024:2 stop_sequence 3 arrival_time 08:17:37 (1737616657) is less than previous stop departure_time 08:18:50 (1737616730) - times must increase between two sequential stops
  • trip_id 5119111304577024:2 stop_sequence 4 arrival_time 08:19:17 (1737616757) is less than previous stop departure_time 08:19:23 (1737616763) - times must increase between two sequential stops
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 83 6 times (86 % of validations)
E004 All route_ids provided in the GTFS-rt feed must exist in the GTFS data 83 6 times (86 % of validations)
E011 All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt 815 6 times (86 % of validations)
E022 stop_time_update arrival/departure times between sequential stops should always increase - they should never be the same or decrease. 8 6 times (86 % of validations)
W002 vehicle_id should be populated for TripUpdates and VehiclePositions 1 1 times (14 % of validations)
W003 a trip_id that is provided in the VehiclePositions feed should be provided in the TripUpdates feed, and a vehicle_id that is provided in the TripUpdates feed should be provided in the VehiclePositions feed 1 1 times (14 % of validations)

GTFS-RT feed content

Entities

Entities present in this feed at 2025-01-24 at 23:05 Europe/Paris.

service_alerts (3) trip_updates (0) vehicle_positions (0)

The timestamp field appears to be too old compared to the current time: the delay is 3 116 seconds. Try to update your feed at most every 30 seconds.

Entities seen in the last 7 days.

service_alerts trip_updates vehicle_positions

Service alerts

Here is a display of service alerts contained in this feed at 2025-01-24 at 23:05 Europe/Paris.

Unknown effect

Between 2024-11-23 at 04:00 Europe/Paris and 2025-04-05 at 04:00 Europe/Paris

Unknown effect

Between 2024-12-24 at 04:00 Europe/Paris and 2025-01-25 at 04:00 Europe/Paris

Unknown effect

Between 2024-12-25 at 04:00 Europe/Paris and 2025-01-25 at 04:00 Europe/Paris

Decoded GTFS-RT feed

See full payload

Here is the decoded GTFS-RT feed Protobuf at 2025-01-24 at 23:05 Europe/Paris. You can look at the GTFS-RT documentation.

{ "entity": [ { "alert": { "active_period": [ { "end": "1743818400", "start": "1732330800" } ], "cause": "CONSTRUCTION", "description_text": { "translation": [ { "language": "FR", "text": "TRAVAUX - À PARTIR DU 10 JANVIER - ARRÊT CENTRE-VILLE\r\nLigne 1 : L’arrêt \"Centre-Ville\" ne sera pas desservi.\r\nSe reporter à l’arrêt \"Le Boscq\".\r\nLigne 2 : L’arrêt \"Centre-Ville\" ne sera pas desservi en direction de \"YQUELON-Haute-Lande\". Se reporter aux arrêts \"Le Boscq\" et \"Plat Gousset\".\r\nNous vous prions de bien vouloir nous excuser pour la gêne occasionnée." } ] }, "effect": "UNKNOWN_EFFECT", "header_text": { "translation": [ { "language": "FR", "text": "CONSTRUCTION" } ] }, "informed_entity": [ { "agency_id": "ATOUMOD105:Network:105:LOC", "route_id": "ATOUMOD105:Line:348940035:LOC", "trip": { "direction_id": 1, "route_id": "ATOUMOD105:Line:348940035:LOC" } }, { "agency_id": "ATOUMOD105:Network:105:LOC", "route_id": "ATOUMOD105:Line:348940035:LOC", "trip": { "direction_id": 2, "route_id": "ATOUMOD105:Line:348940035:LOC" } }, { "agency_id": "ATOUMOD105:Network:105:LOC", "route_id": "ATOUMOD105:Line:350210009:LOC", "trip": { "direction_id": 1, "route_id": "ATOUMOD105:Line:350210009:LOC" } }, { "agency_id": "ATOUMOD105:Network:105:LOC", "route_id": "ATOUMOD105:Line:350210009:LOC", "trip": { "direction_id": 2, "route_id": "ATOUMOD105:Line:350210009:LOC" } } ], "severity_level": "UNKNOWN_SEVERITY" }, "id": "NEVA:4872288429146112" }, { "alert": { "active_period": [ { "end": "1737774000", "start": "1735009200" } ], "cause": "OTHER_CAUSE", "description_text": { "translation": [ { "language": "FR", "text": "DÉVIATION - VENDREDI 24 JANVIER - de 8h30 à 11h\r\nLigne 2 : Les arrêts \"ST-PAIR - Centre-Bourg\" et \"ST-PAIR – École/Mairie\" ne seront pas \r\ndesservis.\r\nSe reporter aux arrêts \"ST-PAIR – Vieux Château\" et \"GRANVILLE - Fourneau\".\r\nNous vous prions de bien vouloir nous excuser pour la gêne occasionnée." } ] }, "effect": "UNKNOWN_EFFECT", "header_text": { "translation": [ { "language": "FR", "text": "INFORMATION" } ] }, "informed_entity": [ { "agency_id": "ATOUMOD105:Network:105:LOC", "route_id": "ATOUMOD105:Line:348940035:LOC", "trip": { "direction_id": 1, "route_id": "ATOUMOD105:Line:348940035:LOC" } }, { "agency_id": "ATOUMOD105:Network:105:LOC", "route_id": "ATOUMOD105:Line:348940035:LOC", "trip": { "direction_id": 2, "route_id": "ATOUMOD105:Line:348940035:LOC" } } ], "severity_level": "UNKNOWN_SEVERITY" }, "id": "NEVA:4872634366951424" }, { "alert": { "active_period": [ { "end": "1737774000", "start": "1735095600" } ], "cause": "OTHER_CAUSE", "description_text": { "translation": [ { "language": "FR", "text": "PERTURBATIONS - VENDREDI 24 JANVIER\r\nLigne 2 : la circulation est revenue à la normale sur la ligne.\r\nMerci de votre compréhension." } ] }, "effect": "UNKNOWN_EFFECT", "header_text": { "translation": [ { "language": "FR", "text": "INFORMATION" } ] }, "informed_entity": [ { "agency_id": "ATOUMOD105:Network:105:LOC", "route_id": "ATOUMOD105:Line:348940035:LOC", "trip": { "direction_id": 1, "route_id": "ATOUMOD105:Line:348940035:LOC" } }, { "agency_id": "ATOUMOD105:Network:105:LOC", "route_id": "ATOUMOD105:Line:348940035:LOC", "trip": { "direction_id": 2, "route_id": "ATOUMOD105:Line:348940035:LOC" } } ], "severity_level": "UNKNOWN_SEVERITY" }, "id": "NEVA:5397182078255104" } ], "header": { "gtfs_realtime_version": "1.0", "timestamp": "1737756312" } }