-
Notifications
You must be signed in to change notification settings - Fork 46
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Rows annotating multiple regions #34
Comments
So they have two representations for the same regions? How common is that? I think I'd be fine with making the metadata basically act as default arguments, then letting people specify they want to use a different region set with arguments. |
It actually will be very common when building graphs on top of labels, since you would have points (with the graph in Possible workaround following your suggestion: if the column corresponding to |
mmh think using indexes rather than explicit values would be tricky. What about using multiple |
I proposed a solution here: ome/ngff#64 (comment) |
Related #99 |
This is solved by the new multi-table PR #455. We don't allow to annotate multiple elements, but we have an helper function to quickly choose what the table is annotating: full_sdata.set_table_annotates_spatialelement("table", "poly") |
Just for completeness, you could potentially add now also two tables, one annotating |
In the
nanostring_cosmx
dataset each row of the annotation matrix is associated to two regions, since each set of cells is saved both as aLabels
and as aPoints
(with variable radius for the cells).With the current specification each row of the table can annotate only one regions, I think we should support the above case, we have to explore how.
The text was updated successfully, but these errors were encountered: