Trevor Manz

Thanks for the clarification. I guess I'm fairly naive here, and speaking mostly from how I've observed the adoption of Arrow on the web for columnar data (which often _feels_...

> In that the installation in python is enormous, and in many zarr/xarray or other array-based workloads would only be doing this one job. I think this is a really...

Sorry for the delay on response. I'll look into updating this example with the library I've written (and updated reference): https://github.com/manzt/reference-spec-reader

Steps to reproduce: - Download https://cf.10xgenomics.com/samples/xenium/1.0.1/Xenium_FFPE_Human_Breast_Cancer_Rep1/Xenium_FFPE_Human_Breast_Cancer_Rep1_he_image.ome.tif ```sh mkdir geotiff-bug cd geotiff-bug npm init -y npm install geotiff touch index.js # add following code ``` ```js // index.mjs import * as...

> The only alternative that comes to mind here requires a big refactor where the ID mapping is exposed to the JS kernel to allow client-side only ID matching. Yeah,...

Thanks for the issue. The title was not very clear. I added one. does that capture the essence of this issue?

Sorry for my limited availability to address this PR right now. The end of the year push is pretty intense for me, and I'm hoping I'll be able to have...

> I think this is really the way to go. The alternative would probably be to convert everything to the new OMENGFF spec for transforms and then use that internally,...

Will the layers still take a modelMatrix as a prop? I think it would make sense to have a priority order of `modelMatrix` passed as a prop > `modelMatrix` from...

Thanks for opening the issue @kylebarron and kicking off the discussion! > I am eager to join this effort. Great! > Other possible loaders would include (Cloud-Optimized) (Geo)TIFF and Zarr...