<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body style="overflow-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;"><br id="lineBreakAtBeginningOfMessage"><div><br><blockquote type="cite"><div>On Dec 8, 2023, at 1:04 PM, Laurențiu Nicola via gdal-dev <gdal-dev@lists.osgeo.org> wrote:</div><br class="Apple-interchange-newline"><div><meta charset="UTF-8"><div style="caret-color: rgb(0, 0, 0); font-size: 18px; font-style: normal; font-variant-caps: normal; font-weight: 400; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none; font-family: Arial;"> - GeoTIFF DEFLATE 280 MB<br></div><div style="caret-color: rgb(0, 0, 0); font-size: 18px; font-style: normal; font-variant-caps: normal; font-weight: 400; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none; font-family: Arial;"> - Zarr BLOSC zlib NONE 281 MB<br></div><div style="caret-color: rgb(0, 0, 0); font-size: 18px; font-style: normal; font-variant-caps: normal; font-weight: 400; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none; font-family: Arial;"> - Zarr BLOSC zlib BIT 253 MB<br></div><div style="caret-color: rgb(0, 0, 0); font-size: 18px; font-style: normal; font-variant-caps: normal; font-weight: 400; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none; font-family: Arial;"> - Zarr BLOSC zlib BYTE 249 MB</div></div></blockquote></div><br><div>If floating point compression performance in TIFFs is the primary concern, don't sleep on investigating LERC. I'm curious what LERC with a stated precision (MAX_Z_ERROR) does for these. In my experience, it's tough to beat LERC with a stated precision for floating point content if your expected readers can consume the encoding. We use it all the time for elevation content, and both QGIS and ArcGIS can consume them without trouble. </div><div><br></div><div>LINZ wrote up a really nice report about LERC for their elevation content. </div><div><a href="https://github.com/linz/elevation/tree/master/docs/tiff-compression">https://github.com/linz/elevation/tree/master/docs/tiff-compression</a></div><div><br></div><div>Howard</div></body></html>