dzsave: IIIF: use named region of 'full' when no crop takes place #4578
Conversation
Should improve conformance with IIIF v2 and v3, the specs of which both mandate support for the 'full' region. Also adds a couple of initial, basic IIIF layout tests
411255d to
a932370
Compare
|
Hi @lovell, I'm so confused :( I thought If it just means a one-tile version of the image (a tile that contains the |
|
Yes, I think the confusion stems from IIIFv2 using the concept of "full" to represent both "region" and "size" but with different meanings. IIIFv3 fixes the naming things is hard problem for "size" by replacing "full" with "max". The discussion about this will be celebrating its 10th birthday later this year - see IIIF/api#620 |
Yare yare, as jojo says 🙄 |
Will improve compliance with IIIF v2 and v3, the specs of which both mandate support for the "full" region.
I've checked OpenLayers and OpenSeadragon and they both contain the same logic so it should address most of #2036
This PR only handles the "region" part of the URL and doesn't touch the "size" as (I think) as long as the tile size is smaller than the original image size in either (or both) dimensions then a "max" tile will not be requested. If the tile size is larger than the original image in both dimensions then there's only one tile/layer, so you don't really need dzsave.
I've also added a couple of initial, basic IIIF layout tests as there were none. I used the sample dimensions from #4576 for these as it should be fixed too.