Closed dgarciabriseno closed 8 months ago
This is working now, I don't know what I changed :( I had the BASE_URL set incorrectly at first and maybe my browser was caching the result.
Glad it's now working!
Note, however, that IIIF uses slashes to separate region, size, rotation parameters etc, so to avoid confusion when using sub-directories, it's best to URL encode the path name
I'm running into a problem with how images are organized on my filesystem.
I am running iipsrv via docker
docker run -it -p 9000:9000 -p 8080:80 -v $PWD/images:/images iipsrv/iipsrv
I have my images laid out in a particular way
year/month/day/type/image.jp2
When I access
info.json
via this path:http://localhost:8080/iiif/2024/02/11/testing/aia_304.jp2/info.json
it works, and I get the json response back.But accessing the jp2 file at
http://localhost:8080/iiif/2024/02/11/testing/aia_304.jp2
I get/images/2024 is neither a file nor part of an image sequence
It seems like the problem is mixing numbers and text, if I move the file to just
2024/02/11/aia_304.jp2
then it works.Edit: Live example: https://api.beta.helioviewer.org/images/iiif/HMI/2024/02/11/magnetogram/2024_02_11__07_48_24_100__SDO_HMI_HMI_magnetogram.jp2/info.json
Edit 2, Logs:
Accessing
info.json
Accessing the jp2