# Reading correct orientations of Analyze 7.5 data into 3D Slicer

**URL:** <https://discourse.slicer.org/t/reading-correct-orientations-of-analyze-7-5-data-into-3d-slicer/24770>\
**Category:** Support\
**Created:** [August 15, 2022, 7:18pm UTC](https://discourse.slicer.org/t/reading-correct-orientations-of-analyze-7-5-data-into-3d-slicer/24770 "2022-08-15T19:18:06Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![jsother](https://avatars.discourse-cdn.com/v4/letter/j/7bcc69/32.png) [@jsother](https://discourse.slicer.org/u/jsother)\
**Post date:** [August 15, 2022, 7:18pm UTC](https://discourse.slicer.org/t/reading-correct-orientations-of-analyze-7-5-data-into-3d-slicer/24770/1 "2022-08-15T19:18:06Z")

</div>

Problem report for Slicer 5.0.2 win-amd64: [please describe expected and actual behavior]

When loading an axial Analyze 7.5 dataset (\*.img, \*.hdr), anterior/posterior directions are incorrectly flipped. I know documentation says “Image orientation is specified ambiguously in this format, therefore its use is strongly discouraged,” however this is a fairly easy fix for what is likely the most common orientation. Can a patch be drafted or is there some global import setting I am overlooking?

JS

---

<div class="post-metadata">

**Author:** ![muratmaga](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/muratmaga/32/3622_2.png) [@muratmaga](https://discourse.slicer.org/u/muratmaga)\
**Post date:** [August 15, 2022, 9:37pm UTC](https://discourse.slicer.org/t/reading-correct-orientations-of-analyze-7-5-data-into-3d-slicer/24770/2 "2022-08-15T21:37:34Z")

</div>

I highly suspect anyone would spend any time to create a patch for such old format.

If you are certain the flip is in A/P axis, you can create a transform matrix in which the third diagonal element is -1, assign your volume to it, harden the transform (right click in the data) and save it as nrrd.