You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
With v.Lon and v.Lat not necessarily being on a tile boundary. I'm not sure, based on the results, whether QuadKeyString will represent a tile, or if it'll be different based on different points with a tile at the same level.
The text was updated successfully, but these errors were encountered:
What should happen is any points within a tile at the given quadKeyLevel should give you the same result.
I can dig into this. I've been using the quad key stuff a bunch over the last week and am getting the feeling like there could be some rounding issues.
I dug into this and everything seemed to work on my test cases. But I did make a change to indicated the correct output variables of the underlying projection 22637a0
Can you provide some examples of issues you're running into?
Ended up just being unfounded doubts in the middle of development - works perfectly, thanks for go.geo - it made osm-rune and osm-rune-viewer possible.
Currently I'm doing something like:
With
v.Lon
andv.Lat
not necessarily being on a tile boundary. I'm not sure, based on the results, whether QuadKeyString will represent a tile, or if it'll be different based on different points with a tile at the same level.The text was updated successfully, but these errors were encountered: