Weird Encoding for Lat/Lng

[dashcammer]

Hello,
I've an old Viofo 2k dash cam. When I use the exiftool to export the metadata gps, I get very strange values (mostly zeros) even though the values printed on the video is correct.
Also, I tried dashcamViewer app on Mac and it seems to be reading the lat/lng correctly (showing the location on map).

When I print metadata using exiftool I get this warning:
GPSLatitude/Longitude encryption is not yet known, so these will be wrong

Here is the file:
https://www.dropbox.com/s/hs8n1kdu51lmeyj/2022_0627_061324_086.MP4?dl=0
and I use this exiftool line:
exiftool -c %.6f -ee 'filename'

One more thing, I read along the lines that the format is NOVATEK which is 'according to some web pages' is an odd format for lat/lng

How can I fix this and get the correct lat/lng coordinates?

[StarGeek]

The data appears similar to another recent thread (which I can't find atm) where it turned out that the gps data was encrypted and Phil was unable to figure out a way to decode it.

Phil will probably check your video when he gets a chance, but don't get your hopes up.

[dashcammer]

Thanks StarGeek,

I believe the right word is 'encoded' not 'encrypted'. I think the problem I the unusual encoding which is not yet supported in exiftool (or requires a special way)..
What confirms my finding (that's just an encoding issue), is that some common dashcam viewers apps have the ability to read it correctly.

Thanks again and looking forward Phil response.

Best

[StarGeek]

I believe the right word is 'encoded' not 'encrypted'.

I wouldn't know, but encryption is the word Phil uses.  Also here.  And he has said in the past that some of the MakerNotes data can be encrypted and you can see mentions of that in the version history.

[Phil Harvey]

I'm pretty sure the encoding is IEEE floating point, but the bits are encrypted somehow using the time as a key.

- Phil