Lazaro Alonso

Indeed. Things should be unified. There is an open issue about it as well: https://github.com/JuliaDataCubes/YAXArrays.jl/issues/309. Some work needs to be done also here.

@dpabon ``` site_2 = site_cube[site=Where(!=("Sentinel2__L2A__uuid"))] Cube(site_2) ``` if there is an error here, it will probably be on the YAXArrays side, since the type is a little bit different when...

since the time axis is different, you cannot have a `YAXArray`, what I would do and normally do, if they need to be in the same file is to put...

thanks for opening this issue. I removed this because now all indexing is handle by DD, and there are several examples across the docs. However, I do agree that a...

there is section on that nowadays. https://juliadatacubes.github.io/YAXArrays.jl/stable/UserGuide/select.html#Select-elements

what do you mean? The output for `GridChunks` is a list of tuples with all chunks and sizes, as in here: https://juliadatacubes.github.io/YAXArrays.jl/dev/examples/generated/UserGuide/setchuncks/?h=chunking#set-chunking-by-variable what's the expected output that you want after...

you could continue on your own branch. And then do a normal PR as usual. No need to push to someone else's branch, actually you shouldn't do it :D.

this should be fix now by https://github.com/JuliaDataCubes/YAXArrays.jl/pull/444

should I merge this? or close it? is still relevant?

ahhh, again this issue. @meggart did fixed it before, but I don't see the commit anywhere now 😢 . Also see https://github.com/JuliaDataCubes/YAXArrays.jl/issues/165 Ahh, this one was suppose to fix it...