Discussion about .ply for reconstruction.meshed.json
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 3.8k
- Forks
- 899
- PR merge metrics
- No merged PRs in 30d
Description
From my ignorance in the subject, why there is an exportation of the reconstruction.json into a file.ply but doesn't exist an exportation method from the reconstruction.meshed.json into the .ply format (https://paulbourke.net/dataformats/ply/ as it's said in the documentation) with the vertices and faces of the future mesh. Is there a real reason why it is not being done or simply a lack of time?
Contributor guide
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 locating the existing reconstruction.json-to-.ply export path and reviewing the documentation linked in the issue. Compare the available data in reconstruction.meshed.json with the PLY requirements, then define an export entry point that includes its vertices and faces; done means the meshed reconstruction can be exported as a valid .ply file.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- computer-vision
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100