Anshul Singhvi
Anshul Singhvi
If you don't know what `Base.SkipMissing` is then it doesn't really make sense I think, but will try and see if there's a nice way to add some info to...
We already have ```julia Base.:(==)(A1::AbstractDimArray, A2::AbstractDimArray) = parent(A1) == parent(A2) && dims(A1) == dims(A2) ``` in DD, which this falls back to. We should probably reorder this to ```julia Base.:(==)(A1::AbstractDimArray,...
WGLMakie probably needs to explicitly `import Makie: Button`
To do this with `mapslices` you would have to essentially remake `zonal` anyway (crop + mask and walk down the tree of geometry), but I can check the performance of...
It doesn't give you a rasterstack though, since it iterates over layers... Unless you mean changing the implementation? That would be breaking I think
Hmm, it could be a switch that does this internally?
There are two scenarios here - "set of rasters" (where you return multiple columns) or "linked rasters" (where you want a slice at those x and y coordinates)
The thing is that methods won't necessarily work the same in both, or work at all...
Hmm, with context `bylayer` does make sense. How would you treat 3d rasters in zonal then? Or a stack with a 3d timeseries raster and a 2d DEM or something