Issue When Using Logarithmic Altitude in GES

[bacon1986]

Good morning.
Thank you for the great resource, I've managed to use it on a single, short route without any issues.
I've then been trying to do a project with 7 connected routes so I've got an earth studio project with 14 track points (one for the start and end of each route) and 7 KML files (one for each route) but when I import any one of the routes into Blender it's placing the curve at some -264km on the Z axis.
(I'm not using "Follow Terrain" yet, hopefully that'll follow later)
Also, if I import a route that starts at anything but the first track point in the file once I've fixed the issue with the Z positioning it's still placed at some incorrect position on the XY plane.
I'm working in 4k so the whole project is over 8GB. Do you have any suggestions for how I could go about debugging the issue or common mistakes I may be making?
Many Thanks
Simon

[bacon1986]

After much experimentation I worked out what's going wrong.
At the end of my flyover I zoom out to show the entire route so to make that look nicer I enabled Logarithmic Altitude.
With that enabled at the time of export from Google Earth Studio the error occurs when I import the route in Blender.
If I re-export the tracking data with Logarithmic Altitude disabled then the import of the route works correctly, until the altitude of the camera changes, then everything gets out of alignment (as would be expected as I didn't re-render the images).

I can roughly comprehend what's going on in the python, but the geo-maths that's going on there is well beyond my ability to understand 😝