Open alexdutton opened 2 years ago
There's a couple of things that have changed since we made that assumption:
One thing you could do would be if the straight line distance is between X and Y, kick off requests for both ?mode=walking
and ?mode=driving
in parallel (to reduce the IO wait time), get them both back and then make the decision of which to show (by default) based on the responses rather than the straight line distance. The downside would be increased google API costs.
In feedback 118519 the user says:
The headline distance on the WDIV address view is:
However, that's the driving distance, and the walking distance is closer to 1.3 miles along footpaths, and the user hasn't necessarily realised this.
It's possible we should be clearer about both walking/driving options as opposed to using the 1.5km straight line distance to pick between without the user's input.