# How to Measure the Perimeter of Slices from a Full-Body 3D Model

**URL:** <https://discourse.slicer.org/t/how-to-measure-the-perimeter-of-slices-from-a-full-body-3d-model/43723>\
**Category:** Support\
**Created:** [July 15, 2025, 4:27am UTC](https://discourse.slicer.org/t/how-to-measure-the-perimeter-of-slices-from-a-full-body-3d-model/43723 "2025-07-15T04:27:14Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![chir.set](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/chir.set/32/66982_2.png) [@chir.set](https://discourse.slicer.org/u/chir.set)\
**Post date:** [July 15, 2025, 7:46am UTC](https://discourse.slicer.org/t/how-to-measure-the-perimeter-of-slices-from-a-full-body-3d-model/43723/3 "2025-07-15T07:46:58Z")

</div>

> [@lassoan](#):
>
> Can any of your modules in VMTK extension compute perimeter of the cross-section (or could be easily added)?

No, the perimeter of a cross-section was not a goal.

However, it should be scriptable fairly easily using [vtkvmtkPolyDataBoundaryExtractor](https://discourse.slicer.org/t/vmtk-cross-sectional-perimeter-calculation/37747/3).

It would mean pulling in the VMTK libraries. StenosisMeasurement2D would be the elect module to add this functionality, as @yoshi can get both the area and the perimeter. But then, how to integrate this calculation in the module, since it does not fit in the `spirit` of the module?

An independent script still using VMTK is also an option.

The last option would be to consider the cell ids: investigate their neighbourhood relationship, so as not to require VMTK. I may start delving into that in the coming days.

What’s your opinion about these options?

---

_[View the full topic](https://discourse.slicer.org/t/how-to-measure-the-perimeter-of-slices-from-a-full-body-3d-model/43723)._