Consideration of the response

    Updated on November 28th 2024

    AimedArrival/ DepartureTime:

    Theoretical timetable of departure and arrival established the day before by the carrier, taking into account the availability of drivers and vehicles. These times are not always available.

    ExpectedArrival/ DepartureTime:

    Prediction of times for next trips taking into account the actual position of the vehicle, the time remaining to reach a stop and the travel times observed on previous trips.

    Arrival/ DepartureStatus:

    Characterize the expected departure or arrival times (or measured if the vehicle is docked).

    These fields can have the following values:

    • onTime: At the scheduled time
    • Early: In advance
    • Delayed: Delayed
    • cancelled :Passage to a cancelled stop (does not concern the entire journey).
    • missed: The vehicle did not stop when it should have, but the race continues.
    • arrived: Arrived
    • Departed: Party
    • notExpected: Unplanned (case of DRT not yet triggered)
    • noReport: Not disclosed Default value: "onTime".

    Careful: The API response contains the data from 30 minutes before the time of the request until 2 hours after.

    DirectionRef:

    There is no shared referential  at the level of Île-de-France Mobilités, so the  field is optional. However, the "DestinationRef"  field (terminus of the ride) is still filled in.

    DatedvehicleJourney  Ref:

    The ride ID uniquely identifies a  ride for all carriers. In a response to a global query, the race is reconstructed because we  get the next passes at all the stops in that race.

    VehicleFeatureRef:

    Indicates the length of trains. This field can take two values:

    • The " shortTrain " value indicates that it  is a short train.
    • The value " longTrain " indicates that it  is a long train.

    However, this field is optional for carriers, so if it is not included in the response, it means that the carrier has not transmitted the information.

    Careful:

    The RATP does not provide trip identifiers but a technical counter with no business link to the notion of a trip.

    We then obtain in the response to the global query for the same line and the same direction all the vehicles stopping at the same time regardless of the stop. As a result, in the responses to global queries, RATP trips are not correctly reconstructed. However, the next stops are all indicated in the answer.