# Proposal: adding a \`vtkPointCloud\` data structure

**URL:** https://discourse.vtk.org/t/proposal-adding-a-vtkpointcloud-data-structure/3872
**Category:** Development
**Tags:** proposal
**Created:** [July 29, 2020, 7:26pm UTC](https://discourse.vtk.org/t/proposal-adding-a-vtkpointcloud-data-structure/3872 "2020-07-29T19:26:44Z")
**Posts on this page:** 1
**Showing post:** 17

<div class="post-metadata">

### Author: ![Yohann\_Bearzi](https://discourse.vtk.org/user_avatar/discourse.vtk.org/yohann_bearzi/32/671_2.png) [@Yohann\_Bearzi](https://discourse.vtk.org/u/Yohann_Bearzi)
#### Post date: [July 31, 2020, 4:08pm UTC](https://discourse.vtk.org/t/proposal-adding-a-vtkpointcloud-data-structure/3872/17 "2020-07-31T16:08:33Z")

</div>

We just had a small debate about this issue with other Kitware folks, and a potential solution that could satisfy everyone came up. What if `vtkPointSet` was not an abstract class anymore? It would make the class hierarchy almost untouched. You could then instantiate point sets without having to make it an unstructured grid or polydata and only have access to the wanted elements: points and their data. We would have to explicitly implement pure virtual methods related to cells, making them returning `nullptr` or zero when appropriate.

What do you you guys think about that?

---

_[View the full topic](https://discourse.vtk.org/t/proposal-adding-a-vtkpointcloud-data-structure/3872)._