Strange featuresAt behavior

[anandthakker]

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.

[mourner]

Weird. I'll investigate.

[mourner]

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).

[mourner]

Fixed in #1530

[anandthakker]

@mourner Well, that's a little embarrassing since I actually introduced a couple of those 4096 magic numbers myself. Thanks for the quick fix!