# Account for non-uniform spacing

**URL:** <https://discourse.itk.org/t/account-for-non-uniform-spacing/2797>\
**Category:** Beginner Questions\
**Created:** [March 6, 2020, 8:39pm UTC](https://discourse.itk.org/t/account-for-non-uniform-spacing/2797 "2020-03-06T20:39:43Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![pieper](https://discourse.itk.org/user_avatar/discourse.itk.org/pieper/32/22_2.png) [@pieper](https://discourse.itk.org/u/pieper)\
**Post date:** [March 7, 2020, 2:16pm UTC](https://discourse.itk.org/t/account-for-non-uniform-spacing/2797/4 "2020-03-07T14:16:05Z")

</div>

If you import through Slicer’s dicom module, you can enable the acquisition transform correction option (in the preferences) which automatically creates a nonlinear transform to put every slice in the location specified by the headers. You can then resample the volume through this transform if you need to have a regularly sampled volume like a 3D itk image.

[https://www.slicer.org/wiki/Documentation/Nightly/Modules/DICOM](https://www.slicer.org/wiki/Documentation/Nightly/Modules/DICOM)

> [@trypag](#):
>
> I can not even trust SeriesInstanceUID…

Of course there’s not much that can be done if the data is corrupted, but the dicom patcher addresses some common cases.

[https://slicer.readthedocs.io/en/latest/user\_guide/module\_dicompatcher.html](https://slicer.readthedocs.io/en/latest/user_guide/module_dicompatcher.html)

---

_[View the full topic](https://discourse.itk.org/t/account-for-non-uniform-spacing/2797)._