Anshul Singhvi

> disk-backed DimTree more arguments for `lazy = :open` :)

@meggart, @felixcremer and I spoke about this on April 3 on the ESDL / big raster call. Here are some notes from there: 2 levels: I/O level: extremely simple, only...

Have you tried enclosing your loop / operation in `open(ras) do ras`? We need to make zonal open rasters on call, see https://github.com/rafaqz/Rasters.jl/pull/832. I just need to add a test...

A MWE of the behaviour one wants is: ```julia m = Raster(rand(X(1:4), Y(1:4), Ti(1:100)) dataset = RasterSeries([m[Ti(i:i)] for i in axes(m, Ti)], Ti) combine(dataset, Ti) == m ``` which does...

You can drop the extra dim that gets formed and then rebuild the entire thing with the new dims you want...except the dropping doesn't work with diskarrays: ```julia m =...

The simple way to test this with DiskArrays is: ```julia dataset = RasterSeries([m[Ti(i:i)] |> Rasters.DiskArrays.cache for i in axes(m, Ti)], :time) ``` (note that we're wrapping the dimarray in a...

Yeah but that's just construction...here we're starting out with a vector of 3d arrays that are lazy

Using `:geom` for geometry columns started because that was how ArchGDAL returned it, I think. Users might expect it now though? I'm not sure how that should be handled.

`GeometryOps.intersects.(geomA[:, first(GI.geometrycolumns(geomA))], geomB[:, first(GI.geometrycolumns(geomB))])` is the "correct" solution at this point but it's a mouthful. If you aren't using GeoDataFrames/ArchGDAL at all for vector features, then `:geometry` is your best...

Any non-GeoJSON thing loaded by GDAL has `:geom` as a geometry column, this includes everything returned by GeoDataFrames. That's the primary problem here. I had two proposals on GeoInterface to...