This question is likely for @jmhuie, as it is a question with the Segment Geometry extension. I noticed that the number of rows in the table for computed values (area in my instance) is the number of slices in the segment, not the number of slices in the volume. I’m actually comparing the slice-by-slice surface area of two separate segments, which have different geometries, so one has fewer rows than the other and if I plot them next to each other, they don’t line up. Is there an option to use the geometry of the volume, rather than the segment, so each computation has the same number of slices?

I’m also happy to take a stab at implementing this if it sounds generally useful and if you could point me in the right general direction.

Unfortunately not intuitively. A segment is required otherwise the area will just be the dimensions of the volume. I have two suggestive work arounds that may provide the results you want

You could add dummy slices to the ends of the actual segments that extend to the length of the volume. This way, the outputs of your different structures will be the same length. You could just add a single pixel per slice so it’s obvious as to which which slices are the dummy slices.

You could perform the computations on every slice of the structures and not downsample to just 100. That’ll preserve the number of slices that make up each structure.