Minor issue: Trip Planning APIs: Technical Documentation PDF

Real-time Public Transport
1

HI there - I’ve noticed a minor issue with one of the examples in section 4.3 of the Technical Documentation PDF (I’m using v3.3).

Example 4.3.1, among other things, calls out that to get trip duration you need to add up the ‘duration’ value for all the legs of that trip…. which is true, but it doesn’t take into account the waiting time between legs, so you’d only get an ‘actual time in motion’ figure.

While it’s probably possible to try and incorporate the wait time between legs, it would be much easier to just subtract leg 0\origin\departureTimeEstimated from last leg\destination\arrivalTimeEstimated.

Just an OCD-initiated FYI :slight_smile:

1 Like
2

Hi Andy,

thanks for letting us know! We’ll include that suggestion in the documentation.

Out of interest, are you a Trip Planner API enthusiast or using the api’s for work purposes? We note you’ve got extensive knowledge of the api’s!

Thanks,
Marcela

3

Thanks Marcela…

This is purely the former - I’ve created an integration for Home Assistant that leverages the API!

1 Like