-
Notifications
You must be signed in to change notification settings - Fork 2.2k
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
Strange featuresAt behavior #1529
Labels
Comments
Weird. I'll investigate. |
OK, found the issue — featuresAt don't calculate the coordinates correctly if the tile extent is not the default 4096 (in this case it's 1024). |
Fixed in #1530 |
mourner
added a commit
that referenced
this issue
Sep 23, 2015
mourner
added a commit
that referenced
this issue
Sep 23, 2015
mourner
added a commit
that referenced
this issue
Sep 23, 2015
@mourner Well, that's a little embarrassing since I actually introduced a couple of those |
mourner
added a commit
that referenced
this issue
Sep 23, 2015
mourner
added a commit
that referenced
this issue
Sep 25, 2015
mourner
added a commit
that referenced
this issue
Sep 26, 2015
mourner
added a commit
that referenced
this issue
Sep 28, 2015
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Apologies for the incredibly vague subject line.
The problem: using a source of US county boundaries made with
tippecanoe
, featuresAt returns empty most of the time, and when it doesn't, it's significantly offset from the passed-in point.Reproduction here: http://bl.ocks.org/anandthakker/67ff3076df1235c3be44. Put your mouse in western Maryland and look in North Carolina.
The text was updated successfully, but these errors were encountered: