Josh Day
Thanks for the report! Do you have a link to the update method you're using?
As posted in the other issue, I have a rewrite in the works that will fix this, but it'll be a few weeks!
Sorry for leaving this untouched for so long. Parsing is pretty ad-hoc/experimental/not well tested. I have a rewrite in the works that will make it better/well tested but it'll be...
Ah, yeah that should be inside an `__init__` function. A quick workaround is setting it yourself (untested): ``` PlotlyLight.plotly = PlotlyLight.PlotlyArtifacts(path="path/to/plotly.js") ```
Failing CI looks unrelated to this PR (Some Int64 vs Int32 error for Arrow compatibility on Windows, invalid kwarg to `makedocs` in the Documenter build)
I'm opting for `Base.show(io::IO, o::Object) = JSON3.write(io, o)` It seems the least disruptive and still a win.
This is probably fine, but why do NaNs occur when fitting the same vector? I might want this behavior to be opt-in if fitting the same vector is breaking assumptions.
A lot of the algorithms here are covered in my dissertation: https://repository.lib.ncsu.edu/server/api/core/bitstreams/1c760e12-e284-43e0-a6c4-0271cc84912b/content (PDF).
I actually have a lot of my use case done! I'll create a PR soon.
@wookay The PR I had in mind was turning pretty big, so I put my work here: https://github.com/joshday/HexEarth.jl The gist of the GeoInterface integration is presented here: https://joshday.github.io/HexEarth.jl/dev/geometry_to_cell/ Take a...