Open mbostock opened 7 years ago
This also impacts d3.geoGilbert.
Fixed by using using precision = 1 in d3-geo/src/graticule.
This looks like a bug in the way geoGilbert handles resampling (i.e. it breaks resampling), rather than a problem with the graticule per se.
Currently you can configure the precision for longitude but not latitude. The latter is fixed at 90°:
For d3-geo this feature isn’t needed, but for projection systems that don’t support adaptive sampling, and particularly since we don’t have a d3.geoSegmentize yet (d3/d3-geo-projection#75), it can be useful to allow the latitude precision to be configured.