Benoit Bovy

There's an IntervalIndex updated example linked in #10116 that is working with CF coordinates `x` and `x_bounds`both propagated in DataArray.

That sounds like a reasonable plan. > a decoder that allows the user whether they want to index by time using pd.DatetimeIndex OR index by time_bounds using pd.IntervalIndex Would that...

(Re-activating this discussion after seeing @mattijn's nice [geopython 2023 talk](https://submit.geopython.net/geopython-2023/talk/FYV7BJ/)) > File formats for representing the data. CSV isn't terribly efficient for ND-array data, and it's quite easy to run...

Thanks @mattijn for the detailed and helpful explanations (I have to admit that I'm not familiar with Vega, Vega-lite nor Altair internals). > I noticed there is also a zarr...

From GDAL's GTI driver docs: > The tiles are listed as features of any GDAL supported vector format. This would translate much more naturally to a GeoPandas' GeoDataFrame of Xarray...

Also xref https://github.com/geoarrow/geoarrow/issues/24, which is relevant for this use case I think.

Xvec and vector data cubes in general work best with geometries having attributes that also depend on other, non-geospatial dimensions like time, etc. Here this is a bit different: each...

Thanks for the clarification @mdsumner ! So if I understand well GDAl GTI (collection of rasters -> virtual raster) is quite similar to stackstac (STAC items -> lazy xarray DataArray),...

FYI, I've just transferred a repo from my account to an organization (with Zenodo access enabled) on GitHub, logged in Zenodo and synced with GitHub, and it seems that Zenodo...

> @benbovy - don't suppose you've tried making a new release since the change to make sure this actually works now? Not yet unfortunately, but I'll try to report here...