-
Notifications
You must be signed in to change notification settings - Fork 160
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
clipCircle's precision is too low #270
Labels
Comments
Fil
added a commit
to observablehq/plot
that referenced
this issue
Apr 27, 2023
(for a nicer circle, I'd recommend we change the default precision of d3.geoCircle, cf. d3/d3-geo#270)
mbostock
pushed a commit
to observablehq/plot
that referenced
this issue
Apr 27, 2023
(for a nicer circle, I'd recommend we change the default precision of d3.geoCircle, cf. d3/d3-geo#270)
mbostock
pushed a commit
to observablehq/plot
that referenced
this issue
Apr 27, 2023
(for a nicer circle, I'd recommend we change the default precision of d3.geoCircle, cf. d3/d3-geo#270)
mbostock
added a commit
to observablehq/plot
that referenced
this issue
Apr 27, 2023
* remove precision(2), which introduces unnecessary complexity (for a nicer circle, I'd recommend we change the default precision of d3.geoCircle, cf. d3/d3-geo#270) * projection-aware * crs * show local time * sqrt is shorthand for pow * link threshold to the domain option * auto powers chart cell * micro-document autoSpec * avoid repetition * simpler reading? * infinite values are ignored * remove links to (valuable but not crucial) prior art * avoid repetition * add a non-unique selector example (a sampler) * remove unused energy table * explicit "interface" instead of API. An alternative might be to link to https://en.wikipedia.org/wiki/API, or use an abbr * ask yourself * named UTC intervals * Update projections.md * Update scales.md * Update scales.md * Update scales.md * Update area.md * Update auto.md * Update bar.md * fix links to sort mark option; document basic transforms * move interval scale option to scales * time, not necessarily UTC * necessarily UTC * infinity may not gap * edit * interval scale option tip * remove blank line * no ask yourself --------- Co-authored-by: Mike Bostock <[email protected]>
frontend-provider
pushed a commit
to frontend-provider/plot
that referenced
this issue
Sep 20, 2023
* remove precision(2), which introduces unnecessary complexity (for a nicer circle, I'd recommend we change the default precision of d3.geoCircle, cf. d3/d3-geo#270) * projection-aware * crs * show local time * sqrt is shorthand for pow * link threshold to the domain option * auto powers chart cell * micro-document autoSpec * avoid repetition * simpler reading? * infinite values are ignored * remove links to (valuable but not crucial) prior art * avoid repetition * add a non-unique selector example (a sampler) * remove unused energy table * explicit "interface" instead of API. An alternative might be to link to https://en.wikipedia.org/wiki/API, or use an abbr * ask yourself * named UTC intervals * Update projections.md * Update scales.md * Update scales.md * Update scales.md * Update area.md * Update auto.md * Update bar.md * fix links to sort mark option; document basic transforms * move interval scale option to scales * time, not necessarily UTC * necessarily UTC * infinity may not gap * edit * interval scale option tip * remove blank line * no ask yourself --------- Co-authored-by: Mike Bostock <[email protected]>
backend-devloper
pushed a commit
to backend-devloper/plot
that referenced
this issue
Nov 24, 2023
* remove precision(2), which introduces unnecessary complexity (for a nicer circle, I'd recommend we change the default precision of d3.geoCircle, cf. d3/d3-geo#270) * projection-aware * crs * show local time * sqrt is shorthand for pow * link threshold to the domain option * auto powers chart cell * micro-document autoSpec * avoid repetition * simpler reading? * infinite values are ignored * remove links to (valuable but not crucial) prior art * avoid repetition * add a non-unique selector example (a sampler) * remove unused energy table * explicit "interface" instead of API. An alternative might be to link to https://en.wikipedia.org/wiki/API, or use an abbr * ask yourself * named UTC intervals * Update projections.md * Update scales.md * Update scales.md * Update scales.md * Update area.md * Update auto.md * Update bar.md * fix links to sort mark option; document basic transforms * move interval scale option to scales * time, not necessarily UTC * necessarily UTC * infinity may not gap * edit * interval scale option tip * remove blank line * no ask yourself --------- Co-authored-by: Mike Bostock <[email protected]>
chaichontat
pushed a commit
to chaichontat/plot
that referenced
this issue
Jan 14, 2024
* remove precision(2), which introduces unnecessary complexity (for a nicer circle, I'd recommend we change the default precision of d3.geoCircle, cf. d3/d3-geo#270) * projection-aware * crs * show local time * sqrt is shorthand for pow * link threshold to the domain option * auto powers chart cell * micro-document autoSpec * avoid repetition * simpler reading? * infinite values are ignored * remove links to (valuable but not crucial) prior art * avoid repetition * add a non-unique selector example (a sampler) * remove unused energy table * explicit "interface" instead of API. An alternative might be to link to https://en.wikipedia.org/wiki/API, or use an abbr * ask yourself * named UTC intervals * Update projections.md * Update scales.md * Update scales.md * Update scales.md * Update area.md * Update auto.md * Update bar.md * fix links to sort mark option; document basic transforms * move interval scale option to scales * time, not necessarily UTC * necessarily UTC * infinity may not gap * edit * interval scale option tip * remove blank line * no ask yourself --------- Co-authored-by: Mike Bostock <[email protected]>
tigrevol8888
added a commit
to tigrevol8888/plot
that referenced
this issue
Jul 5, 2024
* remove precision(2), which introduces unnecessary complexity (for a nicer circle, I'd recommend we change the default precision of d3.geoCircle, cf. d3/d3-geo#270) * projection-aware * crs * show local time * sqrt is shorthand for pow * link threshold to the domain option * auto powers chart cell * micro-document autoSpec * avoid repetition * simpler reading? * infinite values are ignored * remove links to (valuable but not crucial) prior art * avoid repetition * add a non-unique selector example (a sampler) * remove unused energy table * explicit "interface" instead of API. An alternative might be to link to https://en.wikipedia.org/wiki/API, or use an abbr * ask yourself * named UTC intervals * Update projections.md * Update scales.md * Update scales.md * Update scales.md * Update area.md * Update auto.md * Update bar.md * fix links to sort mark option; document basic transforms * move interval scale option to scales * time, not necessarily UTC * necessarily UTC * infinity may not gap * edit * interval scale option tip * remove blank line * no ask yourself --------- Co-authored-by: Mike Bostock <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The clipCircle's precision is 6 degrees (like geoCircle's precision), and the resulting segments are visibly linear on any azimuthal projection's sphere. I would like to make it either configurable (with a default of 6), or to change the value to 2 degrees.
I would also argue that geoCircle's default precision could be set to 2 degrees instead of 6. The trade-offs for speed vs quality might be a bit different 10 years later, with faster computers everywhere.
The text was updated successfully, but these errors were encountered: