You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I wondered if it's planned to enable support for serving up RTI images using IIIF tiles-on-demand instead of whole images, or does that not work with the new way the RTI data is stored ? (Possibly it would need to request 3 tiles simultaneously ?)
If it is planned to do that, I wondered (longer-term) whether the data in the info.json might be something that could be integrated into the IIIF Image API as an extension, so a single info.json provides the information needs for both IIIF tile retrieval and RTI calculations.
Apologies if I've mis-understand the architecture, still getting my head round how it all works.
The text was updated successfully, but these errors were encountered:
Openlime supports many different types of tiled images: deepzoom, zoomify, google and iiif.
Given the lack of rti standards and, moreover, lack of a rti standard for iiif, openlime follows relight json format. It is possible to use iiif served images, i just need to provide some documentation on how to do it and how to do it efficiently.
Ah thanks @ponchio, I had misunderstood a comment in the code and didn't think the relight images could be served up as tiled/zoom images. Docs would be really useful, thank you.
On the IIIF/RTI standard extension, perhaps that's something I can pick-up with you on email, if that would be of interest to pursue? We would be interested in supporting that.
I wondered if it's planned to enable support for serving up RTI images using IIIF tiles-on-demand instead of whole images, or does that not work with the new way the RTI data is stored ? (Possibly it would need to request 3 tiles simultaneously ?)
If it is planned to do that, I wondered (longer-term) whether the data in the info.json might be something that could be integrated into the IIIF Image API as an extension, so a single info.json provides the information needs for both IIIF tile retrieval and RTI calculations.
Apologies if I've mis-understand the architecture, still getting my head round how it all works.
The text was updated successfully, but these errors were encountered: