Attempt to guess the end location for paths that end with nolos

[sobri909]

This one comes out of several users reporting airplane flights where the start of the flight has been recorded, but the end of the flight was only nolos (no location data). Currently these paths won't be sensibly fleshed out to the end, because reasons.

Because Reasons

If LocoKit has both ends of the flight recorded with location data, then it has an existing mechanism to sensibly merge over the nolo gap, based on the path speeds on either side (ie if both speeds imply that the user could have covered that distance in that time).

But there's no mechanism in LocoKit for dealing with the case where there's no speed relevant path on the other side of the gap. For example if there's 30 minutes of airplane speed, then nolos for 2 hours, then 1 minute of walking (ie getting off the plane at the airport), then it will nope out on the merge, because the average of the airplane speed and walking speed means that the two paths can't be merged. Which of course they shouldn't be.

Better Idea

But the airplane flight should still be able to look at its own speed, and the subsequent nolos gap, and then the first coordinate of the walking, and determine that it could have covered that distance in that time. The walking path's first coordinate could then be grafted onto the end of the airplane flight, and voila, a healed airplane trip.