Hey @koninklijke thanks for responding - and coming up with some great comments.
The 360 camera, a modified Insta360, doesn’t naturally maintain gps location with each shot so yes I’m using the first start shot time, adding a 30 frame/second difference to set the image time of the NEXT image and then geotagging the whole sequence. It has worked ok - But as you mention the clock speed on the camera over time appeared to have lagged, this happens when the camera stays in my bag. This lag is effectively reset when I communicate to the camera with the phone - so I’m got a new ‘startup’ procedure to ensure I communicate with the camera first, then I hit the buttons on the camera to start the video recording.
Also I’ve since updated my tagging scripts to allow adding a ‘fudge’ factor in the calculation of the tagging so I can + or - seconds of the image, before I map it with the geotagging gpx file.
I now also have started to take note of your point 1, and mark a intersection when I do some initial stills and noticed if I start the app first I gain approx +4 seconds on the image to the GPS location, so I can handle the drift more easily now.
Overall the recent server updates/privacy etc - it looks to my advantage that the servers have been reset and my June images have now gone yay me. I’m waiting a few days to see what happens and see if things come back before re-submitting my changed images.
If the bad ones come back - I’ll try and remove them.
Again appreciate your comments