Resource details

File name: Données en temps réel des horaires aux arrêts du réseau Néva
Format: gtfs-rt

GTFS-RT (protobuff) des horaires aux arrêts.

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

Download availability

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

⚠️18 warnings

Validation carried out using the current GTFS file and the GTFS-RT the 2025-04-03 at 09:06 Europe/Paris using the MobilityData GTFS-RT validator.

Warnings

vehicle_id not populated W002 6 errors

vehicle_id should be populated for TripUpdates and VehiclePositions

Sample errors
  • trip_id ATOUMOD105:ServiceJourney:5119111304577024x2:LOC does not have a vehicle_id
  • trip_id ATOUMOD105:ServiceJourney:5119111304577024x3:LOC does not have a vehicle_id
  • trip_id ATOUMOD105:ServiceJourney:6253403040645120x1:LOC does not have a vehicle_id
  • trip_id ATOUMOD105:ServiceJourney:5192777811886080x2:LOC does not have a vehicle_id
  • trip_id ATOUMOD105:ServiceJourney:5192777811886080x3:LOC does not have a vehicle_id

schedule_relationship not populated W009 12 errors

trip.schedule_relationship and stop_time_update.schedule_relationship should be populated

Sample errors
  • trip_id ATOUMOD105:ServiceJourney:5119111304577024x2:LOC stop_sequence 26 (and potentially more for this trip) does not have a schedule_relationship
  • trip_id ATOUMOD105:ServiceJourney:5119111304577024x2:LOC does not have a schedule_relationship
  • trip_id ATOUMOD105:ServiceJourney:5119111304577024x3:LOC stop_sequence 8 (and potentially more for this trip) does not have a schedule_relationship
  • trip_id ATOUMOD105:ServiceJourney:5119111304577024x3:LOC does not have a schedule_relationship
  • trip_id ATOUMOD105:ServiceJourney:6253403040645120x1:LOC stop_sequence 1 (and potentially more for this trip) 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
W002 vehicle_id should be populated for TripUpdates and VehiclePositions 174 26 times (87 % of validations)
W009 trip.schedule_relationship and stop_time_update.schedule_relationship should be populated 348 26 times (87 % of validations)
W008 The data in a GTFS-realtime feed should always be less than one minute old 4 4 times (13 % of validations)

GTFS-RT feed content

Entities

Entities present in this feed at 2025-04-04 at 06:03 Europe/Paris.

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

Entities seen in the last 7 days.

trip_updates

Decoded GTFS-RT feed

See full payload

Here is the decoded GTFS-RT feed Protobuf at 2025-04-04 at 06:03 Europe/Paris. You can look at the GTFS-RT documentation.

{ "header": { "gtfs_realtime_version": "1.0", "timestamp": "1743739412" } }