This very topic is an example. But there are many more examples that indicate that for many users and developers NIFTI is too complex and prone to misinterpretation:
- Flipped NIFTI image compared to original Nrrd File
- NIFTI Orientation Issues - nifti - ITK
- Direction/Orientation matrix DICOM vs Nifti - Algorithms - ITK
- Nifti (RPI orientation) file exported to DICOM - wrong orientation - ITK
- Nifti file sform and Slicer image origin seem to disagree
- Misalignment between Nifti image and mask
- Interactive lung lobe segmentation fails with NIFTI volume
- Ambiguous interpretation of a NIfTI-1 image · Issue #127 · NIFTI-Imaging/nifti_clib · GitHub
- dicom nrrd nifti spacing, origin mismatch. - ITK
- Nifti: ImageFileReader + ImageFileWriter changes orientation matrix - Beginner Questions - ITK
- Nifti file orientation change between 2019-08-26 and ITK v5.1rc01 - Engineering - ITK
- Miscellaneous - Generated mask is shown with different origin from the original image · Issue #211 · Project-MONAI/MONAILabel · GitHub
- [Slicer] ITK reader - orthonormal direction cosines · Issue #35 · Project-MONAI/MONAILabel · GitHub
- Nrrd vs nii regarding affine data and transforms
- NIFTI Problem with Reformatted Segmentations
- Saving non-orthogonal volume in Nifti format - Engineering - ITK
- 2D nifti sagittal slice won't open in 3DSlicer - #8 by lassoan
- Invalid NIFTI Orientation Reported
- SimpleITK writing NIfTI with invalid header - simpleitk - ITK
- Wrong Orientation/Origin for multichannel volumes (4D) using Slicer - Issue visualizing BRATS images on 3DSlicer · Issue #22 · Project-MONAI/MONAILabel · GitHub
- SimpleITK: how to save dicom header into nii.gz file? - ITK
- Python writing is not working correctly - Engineering - ITK