Mike Bostock
Mike Bostock
It’s pretty easy to do generically: ```js projection = d3.geoProjection((x, y) => d3.geoEquirectangularRaw(-x, y).reverse()).rotate([0, 0, 90]) ```
Like d3.geoContains, but using planar coordinates, and applying the *path*’s transformation if any.
Currently to convert D3 and TopoJSON spherical coordinates to equirectangular WGS84 used by standard GeoJSON, you need to project through d3.geoEquirectangular with a scale of 180 / π, and then...
It’d be nice if this library were easier to use when saving spherically-clipped GeoJSON. For example: https://beta.observablehq.com/d/d706c7f9c6e46907 The tedious parts are: * You need to wrap the d3.geoClipPolygon instance with...
There are multiple butterfly projections, which refers to the shape of polyhedral layout, and the distinguishing characteristic of this one is that it uses the gnomonic face projection.
Currently it returns an empty Polygon, which is invalid! See https://bl.ocks.org/mbostock/83c0be21dba7602ee14982b020b12f51 for an example.
Consider the case of two polygons in a MultiPolygon, each with their own distinct hole, where the line BC is on the antimeridian: ``` A-----------------B-----------------J | | | | |...
Some GIS (GISes?) assume linear interpolation, even in spherical coordinate systems such as WGS84 / EPSG:4326. This is bad because it is rotation-variant. In contrast, D3 / TopoJSON assume great...
Consider the stitching of a single polygon where a single edge (DE…GH) lies on the antimeridian: ``` C-----D | | | E | / | F | \ | G...
I should tackle #1 and then push a 1.0 release now that D3 4.0 is out.