Andrian
Andrian
> Did you find out a (logical) way on how to get the correct octants of a given coordinate? Unfortunately not. Also, no idea how to get correct sub-octants more...
@LexSong Is the reverse also possible this way? Tried brute-forcing it but got duplicate midpoints for octants: 0 and 4 ``` $ python octant_to_latlong.py 210 Midpoint: (22.5, -67.5) Box: LatLonBox(north=45.0,...
edit: Wrote this script to convert lat long to octants: https://gist.github.com/retroplasma/a2511c08efb73d89699985fbdc0b5278. It uses your method and brute-forces through BulkMetadata. I committed this first but then noticed that it doesn't work...
Method using OBB ray intersection, please test: https://github.com/retroplasma/earth-reverse-engineering/blob/443a3622ce9cb12cd4460cc6dc7999cc703ae67f/experimental_latlong_to_octant.js Usage: ``` npm install node experimental_latlong_to_octant.js 37.420806884765625 -122.08419799804688 ```
> By the way, node experimental_latlong_to_octant.js 28 87 failed to find the octant. damn 😄 Yours is very elegant! What is the logic behind it btw? Guess there's some fixed...
Ah thanks! Think I got it, it works because the octants split at the proper angles. That's nice.
@LexSong please let me know if you want a PR or want me to directly implement it. planning to adapt it and add to README
sure, send it. we can continue to improve it. it's very useful already
@TysonGersh this is similar to [this issue](https://github.com/retroplasma/earth-reverse-engineering/issues/19). Try going up the octant path a bit. 214263605143426 should work. You can drill down from there. It looks like this at max-level...
@TysonGersh Most of it is at 214263605143426 (https://github.com/retroplasma/earth-reverse-engineering/issues/4#issuecomment-456944604) The rest can be found using LexSong's script (https://github.com/LexSong/earth-reverse-engineering/tree/find_overlaps): `python find_overlaps.py 42.322677 42.311888 -83.241127 -83.224605` From octant level 15: `node dump_obj.js 214263605142537...