msautotest bilinear_float.map test in the gdal directory shows up grey instead of various strips of grey

[nsavard]

bilinear_float.png generated from the msautotest gdal directory, appears completly grey compared to multi-strips of grey tone.

This ticket is opened to have a confirmation that this is what we are expecting.

I tested on Ubuntu.

[warmerdam]

I have inspected the file msautotest/gdal/expected/bilinear_float.png from subversion. It appears correct which is a sort of ramp from top to bottom with the top line having the value -10.0 and the bottom row having the value 28.0. Note that the file is a floating point geotiff, and it is not going to be viewable in many simple imaging applications. It does appear as a greyscale ramp when opened in OpenEV.

So, I think everything is fine with the expected file.

[nsavard]

Frank,

I effectively use OpenEv? to test. When I generate the image with msautotest I got a uniform grey image without any ramp at all. The expected image is as you described. I'll attach the actual generated image.

[nsavard]

tgz file that contains bilinear_float.png

[nsavard]

As an additional note, this is the only generated image that shows up like this on my computer.

[nsavard]

Tom: Do you get the same output as one in the attachement?

[tomkralidis]

Norm: I get a PNG image which cannot be opened when try to open. Having said this, I cannot open the one in the attachment in this ticket either.

[warmerdam]

Norm, sorry for the misunderstanding.

I have confirmed the attached file is all zeros- not the expected values.

I have svn updated my mapserver and msautotest, and rendering bilinear_float.map and I get a ramp image matching the expected image. So it would appear this test *can* pass. Perhaps your failure has something to do with the platform, sub-libraries or other configuration issue?

My test was on my 64bit linux (ubuntu) system using development versions of mapserver, gdal, etc.

[nsavard]

Frank,

Thank you. I'll investigate on another computer.

[warmerdam]

I do not believe there is a release critical issue here, so I'm removing the milestone.

[warmerdam]

Normand,

Is this still a reproducable problem? Did you get a chance to try another computer?