# Color map issues with sequence of images

**URL:** https://discourse.paraview.org/t/color-map-issues-with-sequence-of-images/11556
**Category:** ParaView Support
**Created:** [March 3, 2023, 4:55am UTC](https://discourse.paraview.org/t/color-map-issues-with-sequence-of-images/11556 "2023-03-03T04:55:06Z")
**Posts on this page:** 5
**Page:** 1

<div class="post-metadata">

### Author: ![jdpellet](https://discourse.paraview.org/letter_avatar_proxy/v4/letter/j/b5a626/32.png) [@jdpellet](https://discourse.paraview.org/u/jdpellet)
#### Post date: [March 3, 2023, 4:55am UTC](https://discourse.paraview.org/t/color-map-issues-with-sequence-of-images/11556/1 "2023-03-03T04:55:06Z")

</div>

ParaView 5.10.1 seems to have some strange behavior when I try to visualize a sequence of rasters.

Here is the first raster loaded individually (results are as anticipated):

 ![first](https://discourse.paraview.org/uploads/default/original/2X/0/0dd41ef744cd975fad048abbbfef112cd1d0c07d.jpeg)

and the second loaded individually (slightly different from the first):

 ![second](https://discourse.paraview.org/uploads/default/original/2X/6/6eed75c401bb7d0371ffd6e01dcef53d73cd40b3.jpeg)

When I load the two rasters together as a sequence (for an animation), the first image appears the same as before but the second image is different:

 ![together](https://discourse.paraview.org/uploads/default/original/2X/d/d22230c11fb79e9190d2924c0a19ffd5cef11ec9.jpeg)

This seems to happen only when the data in the raster is highly bimodal (part of the image is close to one value and the rest is close to a different value).

---

<div class="post-metadata">

### Author: ![mwestphal](https://discourse.paraview.org/user_avatar/discourse.paraview.org/mwestphal/32/17_2.png) [@mwestphal](https://discourse.paraview.org/u/mwestphal)
#### Post date: [March 8, 2023, 12:13pm UTC](https://discourse.paraview.org/t/color-map-issues-with-sequence-of-images/11556/2 "2023-03-08T12:13:15Z")

</div>

Hi @jdpellet

Please share your data.

Best,

---

<div class="post-metadata">

### Author: ![jdpellet](https://discourse.paraview.org/letter_avatar_proxy/v4/letter/j/b5a626/32.png) [@jdpellet](https://discourse.paraview.org/u/jdpellet)
#### Post date: [March 8, 2023, 12:40pm UTC](https://discourse.paraview.org/t/color-map-issues-with-sequence-of-images/11556/3 "2023-03-08T12:40:58Z")

</div>

[soil\_1.tif](https://discourse.paraview.org/uploads/short-url/weuA83UzTLZ5yJ5FS0aqWqz2POt.tif) (5.3 KB)  
[soil\_2.tif](https://discourse.paraview.org/uploads/short-url/rlvEcvhdCilJXBJyiohlYljF3f4.tif) (20.4 KB)  
I didn’t save the exact same files but the two tif images above show the same issue. Here are the screenshots for these files loaded separately:

 ![soil1](https://discourse.paraview.org/uploads/default/original/2X/a/aab0fe7e7d1a69058b0b5d8e8ef54160531341f5.jpeg)  
 ![soil2](https://discourse.paraview.org/uploads/default/original/2X/b/b05a56853e777246ff5d643ef2ddeae5483c7686.jpeg)  
and then here is the screenshot of the second image with the images loaded together as a sequence using “open multiple files with the cntrl key”.  
 ![soil1and2](https://discourse.paraview.org/uploads/default/original/2X/5/5923c9a0ef952fd60ae6b383c4ee85d193a31db5.jpeg)  
After I loaded the sequence I turned off “read as image stack” and then made them visible using default colors/settings.

---

<div class="post-metadata">

### Author: ![Kenneth\_Moreland](https://discourse.paraview.org/user_avatar/discourse.paraview.org/kenneth_moreland/32/15033_2.png) [@Kenneth\_Moreland](https://discourse.paraview.org/u/Kenneth_Moreland)
#### Post date: [March 8, 2023, 1:58pm UTC](https://discourse.paraview.org/t/color-map-issues-with-sequence-of-images/11556/4 "2023-03-08T13:58:46Z")

</div>

I think the problem is that your two tiff files are of different formats. If you load `soil_1.tif` independently, ParaView reports that the data are represented as 8-bit unsigned integer values in the `Information` panel.

![image](https://discourse.paraview.org/uploads/default/original/2X/d/d124d0b681f1a151e153fc9752d67fa454af1e7e.png)

If you load `soil_2.tif` independently, ParaView reports that the data are represented as 32-bit floating point values.

![image](https://discourse.paraview.org/uploads/default/original/2X/a/a809ee738d2c336f977842335a21acdd92a126ab.png)

This explains why the file size of `soil_2.tif` is 4 times that of `soil_1.tif`.

Now the problem is that when you read the files as a stack, ParaView’s tiff reader (reasonably) assumes that the data format is consistent across all the files. So, it reads the first file and identifies the data as 8-bit unsigned integers. It then assumes the second file is the same and reads the 32-float values as 8-bit integers. The weird pattern you are seeing are the 4 bits of the IEEE floating point values.

---

<div class="post-metadata">

### Author: ![jdpellet](https://discourse.paraview.org/letter_avatar_proxy/v4/letter/j/b5a626/32.png) [@jdpellet](https://discourse.paraview.org/u/jdpellet)
#### Post date: [March 8, 2023, 2:07pm UTC](https://discourse.paraview.org/t/color-map-issues-with-sequence-of-images/11556/5 "2023-03-08T14:07:45Z")

</div>

Thank you. I used a batch gdal\_translate to convert the ascii xyz outputs from my mathematical model to geotiffs. I will seek out how to force gdal\_translate to produce 32-bit float for all files or try another converter. That should resolve.
