Alex

Yes, agree - but the fundamental problem is that we have no way of knowing if local time has been set correctly. If it has then the above will work, as would using the lat and long to work back to GMT. The only positive method of establishing GMT is for the camera to take GMT from the satellite and write it to the file. The problem I have is trying to reliability correlate many files back to a known reference. This can be done with NEMA type files, but apparently not with Novatek files?

I notice that in the posting "https://exiftool.org/forum/index.php?topic=11199.0" that the .gpx data extracted is shown as being UTC/GMT with the suffix "Z", e.g. using the sample video produced as: <trkpt lat="37.7540933333333" lon="-122.424983333333"> 2020-05-19T16:23:38Z </trkpt> Now the time stamp coincides with the display time on the screen which is very likely local time and not Z time. If so, has anyone found the location of the GMT offset that is set during the camera setup?

I am wondering whether it is worth devloping a companion to the ASMBuild so that...

I am wondering whether it is worth devloping a companion to the ASMBuild so that...

If you go to Windows->Preferences you will see the ASM root in the builder options....

I am wondering whether it is worth devloping a companion to the ASMBuild so that...