IIIF protocol: wrong aspect ratio when requesting a region with w, as the size parameter

[regisrob]

IIP doesn't seem to calculate the right height when requesting a region of an image with "w," in the {size} slot of the URI. Sometimes it retrieves an image with a wrong aspect ratio, and sometimes the image is corrupted too.

A few examples:
1024,1024,1024,1024/256,/0/default.jpg: outputs a 256x366 image (should be 256x256, like this)

...and another bug:
1024,1536,512,1024/256,/0/default.jpg : outputs a 256x366 image (should be 256x512)…
and when we check 1024,1536,512,1024/256,512/0/default.jpg the output image is scaled but still corrupted... unless you set an y value for region <= 1535 or >= 1537 (see 1024,1537,512,1024/256,512/0/default.jpg.
Weird.

Those bugs have been raised while testing the last version of IIP server (except latest commit a47a95f) with OpenSeadragon, which both support IIIF Image API 2.0: http://demos.biblissima-condorcet.fr/iip-osd/ (see)

@ruven: do you have an idea of what's going on? Could you confirm it's a problem on the server-side or not?

[rsinghal]

I am seeing the same issue, see http://images-dev.harvardx.harvard.edu/fcgi-bin/iipsrv.fcgi?iiif=1-10_18Sept1905_tiled.tif/40960,0,6302,6814/197,/0/default.jpg, which is setting the height to 28 pixels, instead of 213.

I don't think this is an issue with my image, because when I try the same image in OSD using DeepZoom vs IIIF, the DeepZoom is crisp, while the IIIF is blurry.

[rsinghal]

Any update?

[ruven]

OK, I've just uploaded a fix for these. Please test it out and tell me if anything else comes up.

[regisrob]

Now it's ok, it works fine. Thanks ;-)