Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

QuadKey tile #6

Closed
tmcw opened this issue Oct 22, 2014 · 3 comments
Closed

QuadKey tile #6

tmcw opened this issue Oct 22, 2014 · 3 comments

Comments

@tmcw
Copy link

tmcw commented Oct 22, 2014

Currently I'm doing something like:

quadkey := geo.NewPoint(v.Lon, v.Lat).QuadkeyString(quadKeyLevel)

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.

@paulmach
Copy link
Owner

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.

@paulmach
Copy link
Owner

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?

@tmcw
Copy link
Author

tmcw commented Oct 23, 2014

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.

@tmcw tmcw closed this as completed Oct 23, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants