# Differences between using component ITKImageIO and explicitly setting ITKIOTIFF

**URL:** <https://discourse.itk.org/t/differences-between-using-component-itkimageio-and-explicitly-setting-itkiotiff/697>\
**Category:** Engineering\
**Tags:** io, bug\
**Created:** [February 21, 2018, 7:29pm UTC](https://discourse.itk.org/t/differences-between-using-component-itkimageio-and-explicitly-setting-itkiotiff/697 "2018-02-21T19:29:09Z")\
**Posts on this page:** 1\
**Showing post:** 5

<div class="post-metadata">

**Author:** ![phcerdan](https://discourse.itk.org/user_avatar/discourse.itk.org/phcerdan/32/286_2.png) [@phcerdan](https://discourse.itk.org/u/phcerdan)\
**Post date:** [February 22, 2018, 12:28pm UTC](https://discourse.itk.org/t/differences-between-using-component-itkimageio-and-explicitly-setting-itkiotiff/697/5 "2018-02-22T12:28:38Z")

</div>

Thanks @matt.mccormick, I would go for your last suggestion.  
Fixing it will be way better of course, but maybe it’s not even a bug but a failure in converting the image from the microscopy format to tiff.

The bioformat reader is reading the image as a 4D:  
In itk: `Dimensions: ( 64 64 1 16 )`.  
In OME Metadata (from imageJ bioformats plugins):

```xml
<Pixels BigEndian="true" DimensionOrder="XYCZT" ID="Pixels:0" Interleaved="false" SignificantBits="16"
SizeC="1" SizeT="16" SizeX="64" SizeY="64" SizeZ="1" TimeIncrement="1.0" TimeIncrementUnit="s" Type="uint16">

```

So maybe it is just a metadata conversion error…

---

_[View the full topic](https://discourse.itk.org/t/differences-between-using-component-itkimageio-and-explicitly-setting-itkiotiff/697)._