It has been a few years but when I look into this filter there were quite a number of issues including several places where there were issues with physical spacing, orientation, and efficiency in the computation. As I recall the way this filter computes some geometry is to convert all pixels of a label into continuous index space, then do matrix computation on the full list. This was very memory inefficient for me causing up to 16X memory usage compared to the number of pixels.
I have spent effort adding all the features and computations that the LabelGeometryImageFilter into the LabelMap statistics filters. This includes quite comprehensive testing of many complex and corner cases. This OBB are computed very efficiently from just the started and ending pixels in the line.
IMHO, this filter is redundant and should be removed to a remote module. If there is something missing from the LabelMaps statistics filter we can add that there.
EDIT:
The other option is to make the LabelGeometry filter an adapter class to the calculations done in the LabelShapeStatistiscsImageFilter…