I have two halves of a flight which have been recorded as two tracks, the break caused by my GPS source (PilotAware) suffering a power interruption. The interruption occurred close to overhead an airfield, but despite the termination of the first log and the commencement of the second occurring at several thousand feet altitude, I am unable to merge them as SD thinks I am starting the second as a ‘take off’.

Can this be fixed please, by taking account of altitude?

Well actually, it’s my height above terrain the determines whether I’m on the ground or not! Helicopters can do 0 kts.

The second log fragment does indeed say 0 kts at 0.0 seconds, but I suggest that’s an artefact of the fact that I lost power and had to restart the PAW device.

Could you not use a different rule to allow a log to be merged, say height above terrain at that point rather than speed?