James Trimble's ONS work

The README has two links to a [beeswarm plot on Observable](https://observablehq.com/@d3/beeswarm): one in the text and one an image. The current version of the plot on Observable is not force...

Compact beeswarm layout

6

I imagine that this may not fit in with the development priorities of Seaborn at the moment, but I'm opening the issue just in case. I came up with an...

Feature request - compact beeswarm

4

We recently added a new `"compactswarm"` method to the `beeswarm` package (version 0.4.0, on CRAN). We haven't yet added a vignette with nice examples, but you can see some examples...

"beeswarm" / "swarmplot" in documentation

2

Hi, The documentation for `swarmplot.type` mentions `"beeswarm"` and `"sinaplot"` https://github.com/ACCLAB/dabestr/blob/67ad4d5077d846cd4d8432466b792b0b379ddb14/R/plot.R#L51-L53 but the permitted options are `"swarmplot"` and `"sinaplot"` https://github.com/ACCLAB/dabestr/blob/67ad4d5077d846cd4d8432466b792b0b379ddb14/R/plot.R#L171 Should `"beeswarm"` in the documentation comment be changed to `"swarmplot"`? I...

**Describe the bug** Within the zipped .xlsx file, Excel normally writes the "Automatic" colour by omitting the `` tag within a `` tag. The dev version of gptables writes ``...

An alternative approach for auto column widths

1

**Is your feature request related to a problem? Please describe.** Automatically calculated column widths don't take account of numeric values in columns, and sometimes don't quite match the width of...

`dots` with `per-dot` can bias downward the number of dots in small categories

4

First, thank you for mapshaper. It's incredibly useful, and we use it all the time in the datavis team at the UK's Office for National Statistics. I wondered if I...

Improve compact beeswarm layout for input 1:n

4

A beeswarm using `method=compactswarm` looks worse than with `method=swarm` if the input is a sequence of numbers `1:n`. This is because the algorithm often has many points to choose from...

See issue #14 for details.

Use d3.geoBounds() instead of turf.extent()?

2

```js turf.extent(areas) // [-8.607227544131755,49.91001820137803,1.7629159475701766,60.84535348677859] d3.geoBounds(areas) // [[-8.607227544131755,49.91001820137803],[1.7629159475701766,60.84535348677859]] ``` It looks like we could avoid the 546 kB Turf JavaScript file by using `d3.geoBounds`.