should `multiscales` be a collection?
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Active
- Domain
- documentation
Research direction
Start by reading the current NGFF specification sections defining multiscales and the examples of ome-ngff containers. Review the issue discussion and investigate whether real-world data uses multiple multiscale metadata instances in one group. Done means reaching and documenting a consensus on the JSON shape and its implications for the specification and implementations.
Written by the indexing model from the issue text.
Description
The purpose of this issue is to discuss whether multiscales should be a collection of multiscale metadata, or just a single instance of multiscale metadata. I.e., should ome-ngff support multiple multiscale images in the same group. My current suspicion is that an overwhelming majority of ome-ngff containers will have just a single element in multiscales, and if that's true, we should re-evaluate whether multiscales should be a JSON array. The argument for not allowing multiple multiscale images to exist in the same multiscale group stems from the complexity it introduces to the spec and implementations. I'm happy to elaborate on this if necessary.
Speaking for the data I manage, I cannot foresee a situation where we would put multiple multiscale images in the same group. But I am curious how many data producers are using or planning to use this feature. Can someone point me to an ome-ngff "in the wild" that has multiple instances of multiscale metadata in multiscales?
- Dominant language
- Python
- Stars
- 171
- Forks
- 75
- Avg merge
- 2d 3h
- Merged PRs (30d)
- 20
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from ome/ngff
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
documentation
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
documentation
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
-
infra
Difficulty 1/5 Under an hour Newbie friendliness 65/100
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
bancolombia/sentinel#23 ·
-
test md OpenCI
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
-
integration:quickjs org:external priority:backlog topic:code-interpreter topic:middleware type:feature
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
langchain-ai/deepagents#6450 ·
-
bug client
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100