Journey Planner: Anyone using TimeAdjustments?

Hi everyone,

This concerns the JourneyResults functionality of the Unified API only.

We are likely to make changes to the TimeAdjustments object returned by JourneyResults. This object can be found by navigating ItineraryResult->searchCriteria->timeAdjustments.

The TimeAdjustments object has the properties earliest, earlier, later and latest, which are intended to support navigating backwards and forwards in time to access further journey results.

Currently, the times represented in these properties are not always useful. We are therefore considering changing how these times are calculated.

We are interested to know whether any of you are using TimeAdjustments and how. For example, are you using the times directly, or do you adjust them with some offset?

For reference, an example of a TimeAdjustments object is below:

{
    "$type": "Tfl.Api.Presentation.Entities.JourneyPlanner.TimeAdjustments, Tfl.Api.Presentation.Entities",
    "earliest": {
        "$type": "Tfl.Api.Presentation.Entities.JourneyPlanner.TimeAdjustment, Tfl.Api.Presentation.Entities",
        "date": "20230905",
        "time": "0300",
        "timeIs": "departing",
        "uri": "/journey/journeyresults/victoria%20underground%20station/to/battersea%20power%20station%20underground%20station?time=0300&date=20230905&timeIs=departing"
    },
    "earlier": {
        "$type": "Tfl.Api.Presentation.Entities.JourneyPlanner.TimeAdjustment, Tfl.Api.Presentation.Entities",
        "date": "20230905",
        "time": "0839",
        "timeIs": "departing",
        "uri": "/journey/journeyresults/victoria%20underground%20station/to/battersea%20power%20station%20underground%20station?time=0839&date=20230905&timeIs=departing"
    },
    "later": {
        "$type": "Tfl.Api.Presentation.Entities.JourneyPlanner.TimeAdjustment, Tfl.Api.Presentation.Entities",
        "date": "20230905",
        "time": "0850",
        "timeIs": "departing",
        "uri": "/journey/journeyresults/victoria%20underground%20station/to/battersea%20power%20station%20underground%20station?time=0850&date=20230905&timeIs=departing"
    },
    "latest": {
        "$type": "Tfl.Api.Presentation.Entities.JourneyPlanner.TimeAdjustment, Tfl.Api.Presentation.Entities",
        "date": "20230906",
        "time": "0300",
        "timeIs": "departing",
        "uri": "/journey/journeyresults/victoria%20underground%20station/to/battersea%20power%20station%20underground%20station?time=0300&date=20230906&timeIs=departing"
    }
}

If a response in the negative is also helpful: I have a basic journey planner in my app (currently only supporting “immediate” journeys - e.g. departing now), but since it’s still quite basic, I definitely don’t use this.

1 Like

A post was split to a new topic: Journey Planner disambiguation

hi mate, what api endpoint are you using for that? Thanks