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
When I look at the generated tile output, I only see
- full
- info.json
and no other subsequent folders, like I would for the tile output for a larger dimension image. Meanwhile, here is the tile output for a larger dimension image
My question is
Is there any error going on in the underlying tile process that I can attempt to check for, when an image is too small to be tiled? I have run the iiif_static.py module with the --verbose flag, but none of the output directly indicates that the image file is too small for tiling.
I'd like to catch such a scenario so that I can inform users that upload an image that the image is too small for tiling. Thank you!
Google Small Business
The text was updated successfully, but these errors were encountered:
I am opening this issue to understand the limitations the
iiif_static.py
module has when it comes to generating tile output for smaller sized images.I've attached an example image (it's just a small version of the Google Small Business logo) and I attempt to tile it with the command
When I look at the generated tile output, I only see
and no other subsequent folders, like I would for the tile output for a larger dimension image. Meanwhile, here is the tile output for a larger dimension image
My question is
Is there any error going on in the underlying tile process that I can attempt to check for, when an image is too small to be tiled? I have run the
iiif_static.py
module with the--verbose
flag, but none of the output directly indicates that the image file is too small for tiling.I'd like to catch such a scenario so that I can inform users that upload an image that the image is too small for tiling. Thank you!
Google Small Business
![google](https://user-images.githubusercontent.com/41299115/224391187-2ca65ba6-243d-4af7-ae4d-a9415d058d05.jpg)
The text was updated successfully, but these errors were encountered: