I'll chime in a bit late on this that static file support is also a use 
case for IIIF and something we've kept in mindd while working on the
APIs. This is the model for "level0" compliance [6].

A while ago I made a little demo of OpenSeadragon over IIIF Image API 
1.1 using tiles and included a tile generator [7]. It is python using 
PIL and tile generation is not optimized!

Cheers,
Simeon


[6] http://www-sul.stanford.edu/iiif/image-api/1.1/compliance.html#level0
[7] https://github.com/zimeon/iiif/tree/master/demo


On 7/26/14 4:41 AM, raffaele messuti wrote:
> Jonathan Rochkind wrote:
>> For this project, there is really only a handful of big images, and simplicity of server-side is a priority -- so I think it's actually okay to pre-render all the tiles in advance, and avoid an actual image server -- to the extent tools can work with this.
>
> to make static tiles:
> for deepzoom vips[1] is the faster. as version 7.30[2] you can run
> $ vips dzsave huge.tif my_dz_dir
> deepzoom.py[3] is another option, but slower.
>
> if you want to consider zoomify (usable with a leaflet plugin)
> there is zoomifyimage[4]. inside the package in
> contrib/netpbm_shell_script you'll find a bash script[5] wrapping netpbm
>
>
> --
> raffaele, @atomotic
>
>
>
> [1] http://www.vips.ecs.soton.ac.uk/
> [2] http://www.vips.ecs.soton.ac.uk/index.php?title=What%27s_New_in_7.30
> [3] https://github.com/openzoom/deepzoom.py
> [4] http://sourceforge.net/projects/zoomifyimage
> [5] https://gist.github.com/anonymous/0f8e623561b7ae57ff88
>