LexSong

I will send the PR if you're OK with the current state. I think that there should be clearer way to determine child octants. However the script is already useful...

@TysonGersh I updated lat/long to octants script in my fork here: https://github.com/LexSong/earth-reverse-engineering Currently the output is like this: 42.317152, -83.231428 ------------- Octant Level: 2 { n: 90, s: 0, w:...

It looks like that the mesh is on an [ECEF](https://en.m.wikipedia.org/wiki/ECEF) coordinate system, but on a pure sphere not an ellipsoid in usual GIS systems.

I personally don't use the normalization script and use my own script to rotate and normalize the mesh by latitude and longitude. It's still have several KMs error but I...

See #30

> from google.protobuf import descriptor as _descriptor > ModuleNotFoundError: No module named 'google' > > any idea what might be going wrong? Thank you! you need to install [google protobuf](https://pypi.org/project/protobuf/)

I assume that the north latitude should larger than south latitude? Try `41.465113 41.340216 2.102509 2.270393`

See #30, I think it's better to normalize all tiles with the same reference point, instead of normalize each tile individually and try to fix the height differences later.

What I mean it's that you shouldn't use projections like WGS84. Just calculate latitudes and longitudes directly from XYZ, assume that the Google earth is a perfect sphere.

The formula is: R = sqrt (x^2+y^2+z^2) Latitude = arcsin(z/R)