Resource details
GTFS-RT (protobuff) de la position des véhicules.
This resource file is part of the dataset Réseau urbain Néva.
Download availability
Learn more
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, 8 warnings
Validation carried out using the current GTFS file and the GTFS-RT the 2025-09-20 at 09:04 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 8 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 ATOUMOD105:ServiceJourney:6579938422423552x3:LOC does not exist in the GTFS data and does not have schedule_relationship of ADDED
- vehicle_id zenbus:Vehicle:4878731005919232:LOC trip_id ATOUMOD105:ServiceJourney:5931721724788736x4:LOC does not exist in the GTFS data and does not have schedule_relationship of ADDED
- vehicle_id zenbus:Vehicle:917760003:LOC trip_id ATOUMOD105:ServiceJourney:5456730419888128x2:LOC does not exist in the GTFS data and does not have schedule_relationship of ADDED
- vehicle_id zenbus:Vehicle:765710001:LOC trip_id ATOUMOD105:ServiceJourney:5456730419888128x3:LOC does not exist in the GTFS data and does not have schedule_relationship of ADDED
- vehicle_id zenbus:Vehicle:758770006:LOC trip_id ATOUMOD105:ServiceJourney:4852752590045184x2:LOC does not exist in the GTFS data and does not have schedule_relationship of ADDED
Warnings
schedule_relationship not populated W009 8 errors
trip.schedule_relationship and stop_time_update.schedule_relationship should be populated
Sample errors
- trip_id ATOUMOD105:ServiceJourney:6579938422423552x3:LOC does not have a schedule_relationship
- trip_id ATOUMOD105:ServiceJourney:5931721724788736x4:LOC does not have a schedule_relationship
- trip_id ATOUMOD105:ServiceJourney:5456730419888128x2:LOC does not have a schedule_relationship
- trip_id ATOUMOD105:ServiceJourney:5456730419888128x3:LOC does not have a schedule_relationship
- trip_id ATOUMOD105:ServiceJourney:4852752590045184x2:LOC does not have a schedule_relationship
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 |
|---|---|---|---|
| W009 | trip.schedule_relationship and stop_time_update.schedule_relationship should be populated | 150 | 21 times (68 % of validations) |
| E003 | All trip_ids provided in the GTFS-rt feed must exist in the GTFS data, unless the schedule_relationship is ADDED | 69 | 10 times (32 % of validations) |
| W008 | The data in a GTFS-realtime feed should always be less than one minute old | 9 | 9 times (29 % of validations) |
| E029 | The vehicle position should be within a certain distance of the GTFS shapes.txt data for the current trip unless there is a Service Alert with the Effect of DETOUR for this trip_id. | 3 | 3 times (10 % of validations) |
GTFS-RT feed content
Could not decode the GTFS-RT feed.
The GTFS-RT feed should be accessible over HTTP, without authentication and use the Protobuf format.