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?

Have had the same issue. With SD near an airfield when connection broken unable to mix.

If the merging isn't being allowed because the second log appears to start from takeoff, that means the GPS speed at the beginning of the log is quite low, indicating you're still on the ground.

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?

We could indeed. We would need to revisit the specification for the feature and determine a cost/benefit analysis for making this change, including considering any potential adverse consequences it might have. As always, if enough people would find the resulting change useful we would of course devote these resources.

Fine Tim - give it a check and see if it could be done.

In fact - why not let the user mix logs as they want - in the end it is the users own choice🤔