From 91feab76063b3d6cf0f1bfe75f1b3750328c9504 Mon Sep 17 00:00:00 2001 From: Dan Fandrich Date: Mon, 19 Sep 2022 20:07:03 -0700 Subject: [PATCH] Document a scenario that --max-heading won't protect against --- doc/gpscorrelate-manpage.xml.in | 19 +++++++++++++++++-- 1 file changed, 17 insertions(+), 2 deletions(-) diff --git a/doc/gpscorrelate-manpage.xml.in b/doc/gpscorrelate-manpage.xml.in index cb0cdff..a2bcf9a 100644 --- a/doc/gpscorrelate-manpage.xml.in +++ b/doc/gpscorrelate-manpage.xml.in @@ -4,7 +4,7 @@ Stefano"> Zacchiroli"> - 01 May 2020"> + 19 Sep 2022"> 1"> zack@debian.org"> @@ -27,7 +27,7 @@ &dhsurname;, Till Maas - 2006-2020 + 2006-2022 &dhusername; &dhemail;, Till Maas, Dan Fandrich @@ -508,6 +508,21 @@ inaccurate because the image was taken during a sharp turn. This is off by default. + This option won't prevent writing an incorrect heading or + direction in the case where GPS points are sparser than the time it + takes the recording vehicle to make a nearly 360° + turn. For example, if the vehicle takes 8 seconds to turn + completely around but GPS tags are written every 10 seconds, + then the two points written at either end of the + turn could have headings that are very close (within + ) yet a picture taken in the + middle of the turn, 4 seconds after the first tag, + would have an interpolated heading that is around 180° + off the correct value. Prevent this kind of bad value from + being written by setting a that + is much less than the time it takes to turn around, such as + 4 in this example. +