You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Looking at the documentation, this 'area' is actually the number of pixels/voxels in an object (since version 0.20 those pixels/voxels are scaled by the pixel/voxel size given by an extra optional argument called spacing).
So, in 3D, this would actually be a volume. The term 'area' might be misleading.
One potential simple fix here suggested by @haesleinhuepf to keep backwards compatibility would be to add an extra column named 'volume' for 3D data which has the same content as 'area'.
The text was updated successfully, but these errors were encountered:
scikit-image regionprops returns the same feature called 'area' for 2D and 3D images.
Looking at the documentation, this 'area' is actually the number of pixels/voxels in an object (since version 0.20 those pixels/voxels are scaled by the pixel/voxel size given by an extra optional argument called
spacing
).So, in 3D, this would actually be a volume. The term 'area' might be misleading.
One potential simple fix here suggested by @haesleinhuepf to keep backwards compatibility would be to add an extra column named 'volume' for 3D data which has the same content as 'area'.
The text was updated successfully, but these errors were encountered: