[digikam] [Bug 377292] Improve GPS Correlator UI

[Wolfgang Scheffner]

https://bugs.kde.org/show_bug.cgi?id=377292

--- Comment #6 from Wolfgang Scheffner <wscheffner3 at gmail.com> ---
Hi Simon,

I'd rather start with 2) because that will deliver also the anwer to 1):
I agree that nearly always interpolation is the better, because more precise
option. The only where it is not is when you moved from one GPS point to the
next not straight but in a really bad curve (like helmet camera in a slalom
skiing race. Poor example, I know, too fast for GPS). If the amplitude of that
curve is bigger than the distance between the two points you might get a worse
result than with direct match.

What you described under 1), interpolation being kind of a backup for direct
match, doesn't make sense to me as long as interpolation is considered the
better option anyway. And it would be everything else but intuitive. It would
really require a description within the GUI. And even with all the space I have
in the handbook it wouldn't be easy to explain (how it works yes, but what it
is good for ...?).

So I would still opt for the either - or solution and regarding the limits I
think it would even make sense to have a smaller max. value for interpolation.
The 2000 sec. from direct match, I mean that is more than half of an hour! Who
knows later what happend in this period of time and whether interpolation still
makes sense? If you really have such a time gap and don't know exactly how you
moved, direct match would be the safer option. And we could enforce that a bit
by limiting interpolation to, say, ten minutes or so (600 sec. of course). I
imagine a pedestrian with this. If we talk about a car for ex. we are away from
the max. values anyway.

Cheers
Wolfgang

-- 
You are receiving this mail because:
You are the assignee for the bug.