PointCloudLibrary / PointCloudLibrary/pcl

[surface] getArea(point cloud segment)

Open
#5,735 15 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

kind: request status: triage
Dominant language
C++
Stars
11.1k
Forks
4.7k
Avg merge
4d 10h
Merged PRs (30d)
6

Description

Is your feature request related to a problem? Please describe.

I am developing segmentation algorithms in which I need to calculate the area of segments to make selections and I think the implementation of area calculation i did works well and can be applied general purpouse, so it could be merged in PCL

Solution

Essentially there are a few steps:
(1) optional voxeling of the segment
(2) NormalEstimationOMP
(3) GreedyProjectionTriangulation
(4) Sum the area of greedy triangles
Loop: area += 0.5 * P.cross(Q).norm();
where P and Q are two vectorial sides of the triangles

Describe alternatives you've considered

one might consider alternative surface mesh/triangulations but this seems to work fine on the samples I tested it
there is a little are overestimate due to the fact that the mesh is not perfectly smooth. the voxeling is aimed at reducing this effect.

the area += loop is done as double

An alternative would be to extract optionally this info directly inside the greedy alg. as it comes available so to minimnize the total processing time

Contributor guide

Open the contributing guide

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.

Research direction

Start by reviewing the NormalEstimationOMP and GreedyProjectionTriangulation steps described in the issue, along with the proposed voxelization and triangle-area loop. Clarify where a general-purpose segment-area capability belongs and how the alternative of calculating it inside the greedy algorithm should be evaluated; done requires an agreed scope and validation on representative point-cloud segments.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp
Domain
computer-vision
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
32/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.