Philippe Rivière

It looks like @harrystevens has an alternative here https://observablehq.com/@washpostgraphics/geo-albers-usa-pr

Hmmm… maybe it's the Mercator projection that's taking too short a shortcut? I wasn't able to reproduce though with d3.geoMercator.

I was wondering if the alternative was to fix mercatorRaw instead (in https://github.com/d3/d3-geo/blob/v3.0.1/src/projection/mercator.js#L6), but the same issue impacts all the projections that use lambda without trig, for example geoNaturalEarth1 and...

I'm happy with the first version.

Maybe add that transforms should offer an .invert() function (by default we could use numerical interpolation, w/o needing an explicit setup). [ I'm very excited by this as I already...

@mrnix please open a new issue with a link to a notebook with the settings that actually fail.

This also impacts d3.geoGilbert. Fixed by using using precision = 1 in d3-geo/src/graticule.

It would also make the chart at https://observablehq.com/@d3/contourdensity-linear-binning much nicer ### linear curve  ### curveBasisClosed 

yes it could be nice to have another argument for an "inset" (in degrees) around the feature related: this suggestion for an inset in pixels https://github.com/d3/d3-geo/issues/162

I agree it would be useful. Can we follow the conversation at https://github.com/d3/d3-geo/issues/138?