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
{{ message }}
This repository has been archived by the owner on Nov 7, 2018. It is now read-only.
The d3 projection method has the handy dandy center() function that allows you to reset the translate values to your area of choice. What are the chances someone who's better at math then me would want to make something similar for the geo.tile plugin.
I like to think of myself as a fairly smart guy... But looking at the calculations going on here makes my brain hurt.
Jamie
The text was updated successfully, but these errors were encountered:
Personally, my inclination is to leave d3.geo.tile to operate only in pixel coordinates and not be tied to latitude & longitude; a better name would be d3.geom.tile. The way I intend it to be used is with a geographic projection:
varprojection=d3.geo.mercator().center([-76.3429,38.7351])// geographic center.scale(1<<12)// zoom level in tile coordinates.translate([width/2,height/2]);vartile=d3.geo.tile().scale(projection.scale()).translate(projection([0,0])).size([width,height]);
But there’s definitely an opportunity to make this usage more obvious. Open to suggestions.
I love the geo.tile plugin.
The d3 projection method has the handy dandy center() function that allows you to reset the translate values to your area of choice. What are the chances someone who's better at math then me would want to make something similar for the geo.tile plugin.
I like to think of myself as a fairly smart guy... But looking at the calculations going on here makes my brain hurt.
Jamie
The text was updated successfully, but these errors were encountered: