Mark Keller

**User story** Support overlaying a network or graph in the spatial view. Depends on #1764 **Preferred solution** **Possible alternatives**

Look into dynamic import random not rendering issue

1

**Describe the bug** The higlass component does not render consistently despite higlass debug info appearing in the console consistently. It is probably related to either usage of dynamic import, react...

**User story** User has OME-TIFF segmentation bitmask which contains physical size metadata. **Preferred solution** Should be able to render the scale bar in the Spatial view using the physical size...

**User story** **Preferred solution** **Possible alternatives**

**User story** Also need an option to specify a spot size in physical units from the config **Preferred solution** **Possible alternatives**

**User story** **Preferred solution** **Possible alternatives**

Support a link or edge data type for visualizing distances such as from cell to nearest vessel

3

**User story** User feedback: > Limited Support for Visualizing Vasculature Links > Vitessce primarily supports cell visualization. However, with new concepts like the Vasculature Common Coordinate Framework (VCCF), the importance...

Discuss private data access in Data Hosting documentation page

4

**User story** User wants to use Vitessce to visualize private data stored in the cloud. **Preferred solution** Discuss solutions for both public and private data on the Data Hosting documentation...

**Describe the bug** **To Reproduce** **Data sharing** **Expected behavior** **Screenshots** **Configuration** **Environment:** - Release or git hash: - Browser: - Browser version:

WashU volume demo

1

#### Background For some reason, the OME-TIFF pyramids we converted on AWS have an empty `fileDirectory` object when loaded by `geotiff.js`. In this PR I added a hacky workaround for...