I notice that if I use --depth=onetile OpenSeaDragon gets awfully confused -- presumably because the structure no longer matches the expected naming conventions?
However the default (onepixel) seems counter-intuitive -- zooming out beyond tile-size doesn't seem particularly useful -- and in my use case utilises additional CPU and disk space in creating them.
Perhaps I need to set it to onetile and work out how to "de-confuse" OpenSeaDragon?
Any thoughts?
harukizaemon
All 4 comments
Yes, onetile is for the google maps and zoomify mode, no deepzoom viewer will work with that.
You'd need to switch viewer I think.
jcupitt
on 9 Sep 2016
Ahh that's OK. I can live with the extra files. It just seemed odd to have them all the way down to a single pixel when. Thanks!
harukizaemon
on 9 Sep 2016
It's part of the deepzoom format. They allow images to be nested, so a single pixel in one image can expand into an entirely new image if you zoom far enough. To make this possible, you need to be able to zoom out to a single pixel.
jcupitt
on 9 Sep 2016
Ahh! I hadn't considered the nesting aspect. Right. I'll stick with it as is - I don't think OSD supports either of the other formats - and the additional data is in the hundreds of K which in comparison to the stuff I'm processing, is peanuts.
harukizaemon
on 9 Sep 2016
Related issues
Boojs
路
5Comments
BorntraegerMarc
路
3Comments
helloqhx
路
3Comments
binarykitchen
路
3Comments
huskier
路
4Comments
Most helpful comment
It's part of the deepzoom format. They allow images to be nested, so a single pixel in one image can expand into an entirely new image if you zoom far enough. To make this possible, you need to be able to zoom out to a single pixel.