diff options
| author | Even Rouault <even.rouault@spatialys.com> | 2019-05-25 11:37:34 +0200 |
|---|---|---|
| committer | Even Rouault <even.rouault@spatialys.com> | 2019-05-25 11:37:34 +0200 |
| commit | eaeca6274ae71cdfaeb9f673b6fb0f3cfc0e6ce5 (patch) | |
| tree | aa2cdab52e14bb6bc73160c70e382c685484fb54 /libtiff/libtiff.def | |
| parent | 0f797bf3863011d0fdc1e3fb7cfe802b64d9b19c (diff) | |
| download | libtiff-git-eaeca6274ae71cdfaeb9f673b6fb0f3cfc0e6ce5.tar.gz | |
Add TIFFDeferStrileArrayWriting() and TIFFForceStrileArrayWriting()
Those advanced writing functions must be used in a particular sequence
to make their intended effect. Their aim is to control when/where
the [Strip/Tile][Offsets/ByteCounts] arrays are written into the file.
The purpose of this is to generate 'cloud-optimized geotiff' files where
the first KB of the file only contain the IFD entries without the potentially
large strile arrays. Those are written afterwards.
The typical sequence of calls is:
TIFFOpen()
[ TIFFCreateDirectory(tif) ]
Set fields with calls to TIFFSetField(tif, ...)
TIFFDeferStrileArrayWriting(tif)
TIFFWriteCheck(tif, ...)
TIFFWriteDirectory(tif)
... potentially create other directories and come back to the above directory
TIFFForceStrileArrayWriting(tif): emit the arrays at the end of file
See test/defer_strile_writing.c for a practical example.
Diffstat (limited to 'libtiff/libtiff.def')
| -rw-r--r-- | libtiff/libtiff.def | 2 |
1 files changed, 2 insertions, 0 deletions
diff --git a/libtiff/libtiff.def b/libtiff/libtiff.def index 413276b8..482224f2 100644 --- a/libtiff/libtiff.def +++ b/libtiff/libtiff.def @@ -20,6 +20,7 @@ EXPORTS TIFFAccessTagMethods TIFFDataWidth TIFFDefaultStripSize TIFFDefaultTileSize + TIFFDeferStrileArrayWriting TIFFError TIFFErrorExt TIFFFdOpen @@ -37,6 +38,7 @@ EXPORTS TIFFAccessTagMethods TIFFFindField TIFFFlush TIFFFlushData + TIFFForceStrileArrayWriting TIFFFreeDirectory TIFFGetBitRevTable TIFFGetClientInfo |