# Volumes display Image Spacing and Image Origin wrong?

**URL:** <https://discourse.slicer.org/t/volumes-display-image-spacing-and-image-origin-wrong/43587>\
**Category:** Support\
**Created:** [July 3, 2025, 9:46am UTC](https://discourse.slicer.org/t/volumes-display-image-spacing-and-image-origin-wrong/43587 "2025-07-03T09:46:53Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![StephenLeePeng](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/stephenleepeng/32/11892_2.png) [@StephenLeePeng](https://discourse.slicer.org/u/StephenLeePeng)\
**Post date:** [July 3, 2025, 9:46am UTC](https://discourse.slicer.org/t/volumes-display-image-spacing-and-image-origin-wrong/43587/1 "2025-07-03T09:46:53Z")

</div>

When I load a CT Lung series (axial) into Slicer 4.13, and switch to the “Volumes” Module, and the “Image Spacing” and “Image Origin” display: [1mm, 1mm, 1mm] and [0, 0, 0] as picture below.

 ![image](https://us1.discourse-cdn.com/flex002/uploads/slicer/original/3X/d/6/d6ceb979a18393accef68b7d879a2ca7d349164c.png)

But when I dcmdump the random dcm file, the relative DICOM tag values are:

(0020,0032) DS [-173.100 \ -180.000 \ -272.500] # 26, 3 ImagePositionPatient,

(0020,0037) DS [1.000000\0.000000\0.000000\0.000000\1.000000\0.000000] # 54, 6 ImageOrientationPatient

(0028,0030) DS [0.703125\0.703125] # 18, 2 PixelSpacing.

(0018,0050) DS [1.250000] # 8, 1 SliceThickness

And the dicom MPR image is as follow:

 ![image](https://us1.discourse-cdn.com/flex002/uploads/slicer/original/3X/a/f/af7dcd0fcae82f8a74c01452f63b6535e13a98f0.jpeg)

So, why Image Spacing of Volumes Module is: [1, 1, 1], not: [0.703125, 0.703125, 1.25].  
And the x, y of ImageOrigin is [0, 0], not: [-173.100, -180.00].

---

<div class="post-metadata">

**Author:** ![pieper](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/pieper/32/8_2.png) [@pieper](https://discourse.slicer.org/u/pieper)\
**Post date:** [July 3, 2025, 12:03pm UTC](https://discourse.slicer.org/t/volumes-display-image-spacing-and-image-origin-wrong/43587/2 "2025-07-03T12:03:18Z")

</div>

There’s probably more going on - check the logs to see if there are any error messages or other warnings. We try very hard to make sure DICOM files are properly interpreted in 3D, but weird things can happen, possibly due to inconsistencies in the data. If you can share a public example that replicates the issue for sure we’ll look into it.

---

<div class="post-metadata">

**Author:** ![StephenLeePeng](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/stephenleepeng/32/11892_2.png) [@StephenLeePeng](https://discourse.slicer.org/u/StephenLeePeng)\
**Post date:** [July 4, 2025, 8:06am UTC](https://discourse.slicer.org/t/volumes-display-image-spacing-and-image-origin-wrong/43587/3 "2025-07-04T08:06:01Z")

</div>

Thank you for your reply.

I have uploaded the sampleData to Google Driver, pop the sensitive dicom tags. Please download the data by link to look into why ImageOrigin and ImageSpacing is not displayed as expected.

link is: [https://drive.google.com/file/d/1RnD\_xzYptdIY5nfiPeQsDSlC4airhcx2/view?usp=drive\_link](https://drive.google.com/file/d/1RnD_xzYptdIY5nfiPeQsDSlC4airhcx2/view?usp=drive_link)

Thank you very much.

---

<div class="post-metadata">

**Author:** ![issakomi](https://avatars.discourse-cdn.com/v4/letter/i/b9e5f3/32.png) [@issakomi](https://discourse.slicer.org/u/issakomi)\
**Post date:** [July 6, 2025, 9:42am UTC](https://discourse.slicer.org/t/volumes-display-image-spacing-and-image-origin-wrong/43587/4 "2025-07-06T09:42:28Z")

</div>

The link to Google Drive is not public.  
What is the value of the _SOP Class UID_ `(0x0008,0x0016)`?  
Most likely the series is stored in _Secondary Capture IOD_.

Adding spatial information to the _Secondary Capture IOD_ is a fairly common practice, even if it was **not** part of the IOD until 2024, s. [CP-2330](https://dicom.nema.org/medical/dicom/Final/cp2330_ft_AddImagePlaneModuleToSC.pdf). Probably the recent version of Slicer will work with this series (you are using the old version 4.13).

---

<div class="post-metadata">

**Author:** ![StephenLeePeng](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/stephenleepeng/32/11892_2.png) [@StephenLeePeng](https://discourse.slicer.org/u/StephenLeePeng)\
**Post date:** [July 7, 2025, 1:19am UTC](https://discourse.slicer.org/t/volumes-display-image-spacing-and-image-origin-wrong/43587/5 "2025-07-07T01:19:51Z")

</div>

I’m so sorry the google drive link is private, I’m new to Google driver.

This is the new data link: [https://drive.google.com/file/d/1RnD\_xzYptdIY5nfiPeQsDSlC4airhcx2/view](https://drive.google.com/file/d/1RnD_xzYptdIY5nfiPeQsDSlC4airhcx2/view)  
anyone can download and view the data.

I have try this data with the Slicer 5.6.2-linux-amd64, and this problem always exist.

And I test this data with the most new stable Release: 5.8.1, and this problem have been solved. And I want to know why?

 ![5.8.1-pro](https://us1.discourse-cdn.com/flex002/uploads/slicer/original/3X/2/4/2495315cdfb7c3a2d0a6e6e06cbbae8594537b0a.png)

@issakomi @pieper @lassoan

---

<div class="post-metadata">

**Author:** ![issakomi](https://avatars.discourse-cdn.com/v4/letter/i/b9e5f3/32.png) [@issakomi](https://discourse.slicer.org/u/issakomi)\
**Post date:** [July 7, 2025, 1:27am UTC](https://discourse.slicer.org/t/volumes-display-image-spacing-and-image-origin-wrong/43587/6 "2025-07-07T01:27:30Z")

</div>

> anyone can download and view the data.

I have looked, yes, it is Secondary Capture IOD.

> And I want to know why?

S. the post above.