Hello Phil,
First of all, I want to say a huge thank you for taking the time and handling it.
I'll try to answer everything as best of my knowledge, let's hope I don't forget anything.
1. From the dump of Vid_050:
Tue Feb 19 09:26:37 2019 0 0 A 32.08812121 N 34.85583249 E 0 0 0 0 0 3.38151264190674
Tue Feb 19 09:26:38 2019 0 0 A 32.08811989 N 34.85583259 E 0 1.62999999523163 64 3.67499995231628 0 3.37774848937988
in the first line, I'm guessing that the info we have here is: longitude, latitude, elevation.
on the second line, I have no idea what are the rest of this stuff: 1.62999999523163 64 3.67499995231628
2. As far as I know, accuracy of longitude and latitude data is measured up to 7 numbers after the floating point.
here I can count 8, which means that it's accurate to about 1 meter, 7 is fine by me (accurate to about 10 meters)
for me accuracy of elevation data of 4 numbers after the floating point is also sufficient.
I don't mind the extra accuracy, but just to let you know what I consider "accurate data measurement"
3. Regarding time code: I know that the video is 30 FPS, is this helping?
I don't think that the phone is sampling the GPS data every second, but I might be mistaking.
4. Regarding 0x101:
Yes, IXE3518NYGDB3N is the camera S/N.
Insta360 is the name of the company
One2 is the technical name of the One X (just like phones, where Samsung Galaxy S5 is SM-G900F)
V1.17.16 is my firmware version.
lines 30 and onward - I have no idea.
5. Record 0x200 also makes no sense to me.
6. Just like you said, 0x300 seems like 6 axis data to me.
I have no idea how to interpret it (what axis is what number) but I'm assuming it's in the following order:
Roll: rotation around the front-to-back axis, Pitch: rotation around the side-to-side axis, Yaw: rotation around the vertical axis
And then the next 3 numbers are from the accelerometer.
I have a friend who might be able to help a bit, I'll run it by him.
7. Regarding recorded 0x400, can it be that 96 is Fahrenheit of the phone? does it fluctuate much?
8. When looking at Vid_050 dump:
Tue Feb 19 09:26:44 2019 0 0 A 32.08812709 N 34.85585249 E 224 1.80249989032745 0 3.23828125 0 3.35669207572937
Can it be that the two 0 before the "A" is altitude? and that's why it's 0? (don't know why you got 0 twice though)
And after the "E", 224 looks like a direction to me, like SW on a compass.
9. Vid_051 is when the phone is stationary and the camera moves.
So, logicly, the speed should be 0
(because the base assumption is that the camera don't get a GPS signal, only the phone)
I've checked the video, the data I see in the app for Vid_052 at 00:00 is:
speed: 0.58 km/h
elevation: 58.33
slope: 0.0%
routh: 0.00km
direction: 293° NW
location: 32°5'16"N , 34°51'22"E
And at 00:03 (approx when I put my phone down and start walking around with the camera):
speed: 0.00 km/h
elevation: 58.33
slope: 29.7%
routh: 0.00km
direction: 0° N
location: 32°5'16"N , 34°51'22"E
I found out in the app that for Vid_050 at 00:15 I get to speed of 2.99 km/h, here is the full data:
speed: 2.99 km/h
elevation: 89.96M
slope: 100.0%
routh: 0.00km
direction: 86° E
location: 32°5'17"N , 34°51'21"E
Sorry this post got so long,
for me all of this is really an uncharted territory and this is the first time I'm dealing with this kind of a challenge
Thanks again
-Or