This behavior spoils the display of the results of my algorithms, because only from the VTK it is not clear where to get the same matrix as in the slicer
vtkImageData did not store image directions for many years, so we had to store image geometry (origin, spacing, and axis directions) in the MRML node, and removed it from vtkImageData (vtkImageData origin is always set to 0,0,0 and direction is set to identity). Therefore, right now, you must get the image geometry information from the MRML node.
In the not too distant future (maybe within a year) we’ll update Slicer to store image geometry in the vtkImageData, which will make things simpler.
1 Like