CORS error when using Biigle storage

[EmmaPoliakova]

Hi,

I'm new to Biigle, and I'm trying to set up a project. I'm using the official storage offered on the website. I made a storage request and uploaded my .tif files. Once approved, I created a volume, selected the uploaded images, but I keep running into this error:

Is there some setting I'm missing? I had a look at the manual, but as the storage is not created by me, I'm not sure if I can change the CORS policy. This error happens when using Chrome. I get a different error on Safari:

Here, I can at least see the image, but the project needs to be accessible to multiple people who don't use Safari. There are no thumbnails displayed in either case.

There is another volume in the project where the tif image was uploaded by a different user, which displays without problems.

Many thanks for your help

[mzur]

Hi, there seems to be an error with the TIFF files. They use JPEG compression but also contain an alpha channel (Extra Samples: 1<unassoc-alpha> according to tiffinfo). This is not supported both by our backend library (vips) and the frontend library (utif2) that decodes the files. This is why there are no image thumbnails and you see the error message. I'll improve the error handling so a decoding error is no longer confused with a CORS error in the future. I believe Safari can display TIFFs natively so you can see it there.

The TIFF of the other user uses LZW instead of JPEG compression and is larger than 10,000 px so BIIGLE converts it to tiled JPEGs instead of showing the TIFF directly.

[EmmaPoliakova]

Thank you for getting back to me so quickly! Removing the alpha channel did fix the thumbnail issue. However, the main error still persists. Is this because Chrome doesn't support TIFF images, rather than a Biigle error?

[mzur]

No major browser supports TIFF natively, so BIIGLE has to use a frontend library to decode the files. It seems like our library (utif2) has issues with your new files because they contain JPEG tables. This seems to be a bug in the library rather than a malformed file this time. I'm looking into switching to a different library that has better support for various TIFF formats. I'll keep you updated here.

[EmmaPoliakova]

Thank you again for the explanation and your help with solving this problem!

[mzur]

I have just pushed an update with a different frontend decoding library that seems to work much better. It can display even the malformed TIFFs (with JPEG+alpha) although the backend library still won't process them.

[EmmaPoliakova]

This is fantastic! The TIFFs from yesterday are now working without problems.