My GoPro Max has excellent GPS, I’m finding! The paths the sequences go along are far more accurate than what my phone’s GPS can create.
But with 360° time lapse photos, it misplaces images about a full second ahead of where they were taken.
I use the following command:
mapillary_tools process --import_path Trip1 --cutoff_time 10 --duplicate_distance 1.5 --duplicate_angle 360 --interpolate_directions --offset_angle 0 --overwrite_EXIF_direction_tag --user_name jesseakaraccoon --advanced
I get a situation that looks like this:
Sequence: >==A=====a===B======b===C==>
Where A and B are the ACTUAL photo positions, and a and b are what their geotag says, and thus where they show up on mapillary, too far ahead. At faster speeds, this can be a difference of over 10 meters!
What additional commands or subprocesses can you suggest to correct this?
EDIT: Turns out the solution is exactly as simple as adding “–offset_time 1” to the command. It then looks like:
mapillary_tools process --import_path Trip1 --cutoff_time 10 --duplicate_distance 1.5 --duplicate_angle 360 --interpolate_directions --offset_angle 0 --offset_time 1 --overwrite_EXIF_direction_tag --user_name jesseakaraccoon --advanced
I’ll just leave this here, since the official readme is kinda lacking in real-world explanations of offset time. I was afraid I’d have to, like, create a GPX file, since the ONLY examples the readme gives for offset time involve a GPX file.