Mesh specification
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 171
- Forks
- 75
- Avg merge
- 2d 3h
- Merged PRs (30d)
- 20
Description
As discussed in the feb. 2021 ngff community call, and following this image.sc thread
The idea is to follow PLY specification to store meshes in ome-zarr. A ply file is organised in:
- a header (translated in the .attrs of the zarr group)
- the points (a zarr.Array)
- for each element (e.g. faces) the list of vertices. Those are group by number of sides, with one zarr.Array per polygon.
There is a draft implementation here: https://github.com/centuri-engineering/ply-zarr
Some questions:
- I don't know how to deal with binary formats
- PLY allows for datatype specification at the column level, how to deal with that in zarr?
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.
Research direction
Start by reading the linked image.sc discussion and the draft implementation at centuri-engineering/ply-zarr, then review this issue's discussion. Done means an agreed NGFF mesh specification that addresses binary formats and PLY's column-level datatype requirements.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- data
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100