The API could remain mostly the same, we just need to add a few extra Get/Set methods:
- Origin(double[3])
- Spacing(double[3])
- Directions(vtkMatrix3x3*)
- IndexToVolumeMatrix(vtkMatrix4x4*)
We might add a few more for convenience/performance, something like these:
- VolumeToIndexMatrix(vtkMatrix4x4*)
- VolumeToIndexPosition(double[3], double[3])
- IndexToVolumePosition(double[3], double[3])
“Rotation” does not sound relevant to me. We don’t rotate anything but we directly define the a coordinate system axis directions.
Calling the volume’s physical coordinate system “Model” does not seem very intuitive to me. “Volume” may be a bit better, but there could be better ones.