No, the perimeter of a cross-section was not a goal.
However, it should be scriptable fairly easily using vtkvmtkPolyDataBoundaryExtractor.
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?