mirror/openseadragon
1
0
Fork 0
mirror of https://github.com/openseadragon/openseadragon.git synced 2024-11-22 05:06:09 +03:00
Code Issues Projects Releases Wiki Activity

Updated The DZI File Format (markdown)

Ian Gilman 2017-11-14 14:05:36 -08:00
parent 6b74921c35
commit 7b719eb261
1 changed files with 6 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
The-DZI-File-Format.md

@ -1,15 +1,15 @@
For a general overview, see https://msdn.microsoft.com/en-us/library/cc645077(VS.95).aspx. For a general overview, see https://msdn.microsoft.com/en-us/library/cc645077(VS.95).aspx.
When creating a DZI image, you specify a size, format, and overlap. The [conversion tool](http://openseadragon.github.io/examples/creating-zooming-images/) then goes through the image, breaking it into tiles. It starts with the full resolution image, and starts creating tiles from the upper left corner, with the first tile being 0_0, the next in the top row being 1_0, etc. The first tile on the next row is 0_1, etc. When creating a DZI image, you specify a size, format, and overlap. The [conversion tool](http://openseadragon.github.io/examples/creating-zooming-images/) then goes through the image, breaking it into tiles. It starts with the full resolution image, and starts creating tiles from the upper left corner, with the first tile being 0_0, the next in the top row being 1_0, etc. The first tile on the next row is 0_1, etc. This becomes the highest-numbered layer.
Note that tile overlaps are on both sides of the join, so a one pixel overlap (for example) means tiles 0_0 and 1_0 have two columns of pixels in common. The tool then scales the image down to half width, rounding odd-sized image sizes up, and runs through and tiles it again, using the same numbering system. This becomes the next level.
The tool continues scaling down by half and outputting new levels until the image is down to approximately 1px wide. This is the lowest level, and it's designated level 0. The next level above it is level 1, etc.
Tile overlap (if any) is added in addition to the normal tile size. Note that tile overlaps are on both sides of the join, so a one pixel overlap (for example) means tiles 0_0 and 1_0 have two columns of pixels in common.
The tile size is usually chosen so that non-edge tiles are a power of two along the side. With overlap one and tile size 254, tile 0_0 will be 255x255, but all non-edge tiles will be 256x256. The tile size is usually chosen so that non-edge tiles are a power of two along the side. With overlap one and tile size 254, tile 0_0 will be 255x255, but all non-edge tiles will be 256x256.
Tiles are written even if they contribute no new pixels to the image. With overlap one, for example, you can have a two-pixel edge tile which simply repeats pixels in the previous tile. Tiles are written even if they contribute no new pixels to the image. With overlap one, for example, you can have a two-pixel edge tile which simply repeats pixels in the previous tile.
This becomes the highest-numbered layer. The tool then scales the image down to half width, rounding odd-sized image sizes up, and runs through and tiles it again, using the same numbering system. This becomes the next level.
The tool continues scaling down by half and outputting new levels until the image is down to approximately 1px wide. This is the lowest level, and it's designated level 0. The next level above it is level 1, etc.
Metadata about the file is stored in an XML file using either the .dzi or .xml file extension, e.g. example.dzi. The tiles are stored in a folder next to it, named e.g. example_files. The tile of the lowest level in this example would be `example_files/0/0_0.jpg`. Metadata about the file is stored in an XML file using either the .dzi or .xml file extension, e.g. example.dzi. The tiles are stored in a folder next to it, named e.g. example_files. The tile of the lowest level in this example would be `example_files/0/0_0.jpg`.