Some slippy map services (Bing maps in particular) use "quadkeys", a way of recursively partitioning the tile space. At the first zoom level, quadkey "0" is the top left tile, "1" is the top right, and "2" and "3" are the lower two. At the second zoom level, you add an extra digit to show which quarter of the higher level quarter you are in. So a quadkey of 112031 is zoom level 6. Details here https://docs.microsoft.com/en-us/bingmaps/articles/bing-maps-tile-system
Feature Request
Some slippy map services (Bing maps in particular) use "quadkeys", a way of recursively partitioning the tile space. At the first zoom level, quadkey "0" is the top left tile, "1" is the top right, and "2" and "3" are the lower two. At the second zoom level, you add an extra digit to show which quarter of the higher level quarter you are in. So a quadkey of 112031 is zoom level 6. Details here https://docs.microsoft.com/en-us/bingmaps/articles/bing-maps-tile-system
I've seen a couple of questions asking about quadkeys on SO recently, and found a python library with computations for them, and wrote an R function in response. https://gis.stackexchange.com/questions/359507/how-to-convert-quadkey-into-tiles-coordinates/359636#359636
So now i can go from quadkey to lat-long using:
Would this be suitable functionality for
slippymath
?