Mark Keller

**User story** Until #15 is implemented, we should warn/error when zarr v3 data is encountered. This may be more likely now that v3 support has been merged in zarr-python **Preferred...

**User story** Changes required ``` - model.draw(opts) + model.draw(this.context.renderPass) ``` Also, usage of uniform buffers https://deck.gl/docs/upgrade-guide#uniform-buffers **Preferred solution** **Possible alternatives**

**User story** In Vitessce the [ImageWrapper](https://github.com/vitessce/vitessce/blob/main/packages/utils/image-utils/src/ImageWrapper.ts) class makes it so that a consumer does not need to worry about whether an image is stored as OME-TIFF or OME-NGFF (unifies the...

**User story** For supporting label images, in Vitessce we use the standard viv.MultiscaleImageLayer ([code](https://github.com/vitessce/vitessce/blob/3287daea1dfb7443430f144f7a7aa8e61180d7fb/packages/view-types/spatial-beta/src/Spatial.js#L608)) combined with a custom renderSubLayers ([code](https://github.com/vitessce/vitessce/blob/3287daea1dfb7443430f144f7a7aa8e61180d7fb/packages/view-types/spatial-beta/src/utils.js#L211), [more code](https://github.com/vitessce/vitessce/blob/main/packages/gl/src/BitmaskLayerBeta.js), [utils](https://github.com/vitessce/vitessce/blob/main/packages/gl/src/bitmask-utils.js)) and custom [shaders](https://github.com/vitessce/vitessce/blob/main/packages/gl/src/bitmask-layer-beta-shaders.js) This code can be...

**User story** See https://github.com/ome/ngff/pull/255 In this proposal (and in current SpatialData), coordinate transformations are defined in terms of input/output coordinate systems. Multiple coordinate transformations can be chained together. These chains...

Geometry encoding parameter for shapes

1

Fixes https://github.com/scverse/spatialdata/issues/799 The [to_parquet](https://geopandas.org/en/stable/docs/reference/api/geopandas.GeoDataFrame.to_parquet.html) function supports a `geometry_encoding` parameter. When [geoarrow](https://geoarrow.org/), it will be more efficient to read/parse the geometries, as the data can stay in its parquet/arrow memory layout...

Design doc: Add note about on-disk locations of point metadata attributes

1

This PR clarifies how to access the attributes listed here when accessing the points data from the on-disk format. Is this correct that the coordinate transformations are in `"transform"` in-memory...

Design doc: Add intrinsic coordinate system name example

1

Hi, I wanted to clarify the logic for inferring the intrinsic coordinate system name here by adding an example. Please let me know if this understanding of how the intrinsic...

Easily enable sorting points along a Z-order curve

2

## The problem The current point representation does not enforce any spatial ordering. As people are already storing large datasets with tens of millions of points into spatialdata objects, this...

**Is your feature request related to a problem? Please describe.** There are currently two ways to store 2.5D data (points, images, labels) in a SpatialData object (as far as I...