PointCloudLibrary / PointCloudLibrary/pcl
Deprecate duplicate vtk_lib_io file readers/writers
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 11.1k
- Forks
- 4.7k
- Avg merge
- 4d 10h
- Merged PRs (30d)
- 6
Description
Started digging into pcl::io::savePolygonFile and pcl::io::save which exhibit very similar behaviors and it looks like we have two types of reader writer implementations for the same formats.
Edit: Adding stuff as I'm finding more
Load into a pcl::TextureMesh
from OBJ file
pcl::io::loadPolygonFileOBJ (vtk_lib_io.cpp)
pcl::io::loadOBJFile (obj_io.h)
Load into a pcl::PolygonMesh
from OBJ file
pcl::io::loadPolygonFileOBJ (vtk_lib_io.cpp)
pcl::io::loadOBJFile (obj_io.h)
from PLY file
pcl::io::loadPolygonFilePLY (vtk_lib_io.cpp)
pcl::io::loadPLYFile (ply_io.h)
from STL file
pcl::io::loadPolygonFileSTL (vtk_lib_io.cpp)
from VTK file
pcl::io::loadPolygonFileVTK (vtk_lib_io.cpp)
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
Compare the implementations in io/src/vtk_lib_io.cpp, io/src/auto_io.cpp, io/include/pcl/io/obj_io.h, and io/include/pcl/io/ply_io.h, starting with the linked save and load entry points. Trace the overlapping readers and writers for OBJ, PLY, STL, and VTK formats. Done means the duplicate APIs and their deprecation scope are identified and addressed consistently.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- computer-vision
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100