Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Discussion about .ply for reconstruction.meshed.json

Open
#1,087 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
python

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.

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?

Dominant language
Python
Stars
3.8k
Forks
898
PR merge metrics
No merged PRs in 30d

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from mapillary/OpenSfM

All issues in mapillary/OpenSfM

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.