Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

d3.geoGraticule should have a configurable latitude precision. #95

Open
mbostock opened this issue Apr 9, 2017 · 2 comments
Open

d3.geoGraticule should have a configurable latitude precision. #95

mbostock opened this issue Apr 9, 2017 · 2 comments
Assignees
Labels

Comments

@mbostock
Copy link
Member

mbostock commented Apr 9, 2017

Currently you can configure the precision for longitude but not latitude. The latter is fixed at 90°:

x = graticuleX(y0, y1, 90);
y = graticuleY(x0, x1, precision);
X = graticuleX(Y0, Y1, 90);
Y = graticuleY(X0, X1, precision);

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.

@mbostock mbostock self-assigned this Apr 9, 2017
@mbostock mbostock changed the title d3.geoGraticule’s should have a configurable precision for latitude. d3.geoGraticule should have a configurable latitude precision. Apr 9, 2017
@Fil
Copy link
Member

Fil commented Mar 13, 2019

This also impacts d3.geoGilbert.
geogilbert graticule

Fixed by using using precision = 1 in d3-geo/src/graticule.
geogilbert graticule 1

@Fil Fil added the idea label Jul 10, 2020
@jrus
Copy link
Contributor

jrus commented Jun 17, 2021

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Development

No branches or pull requests

3 participants