<html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /></head><body style='font-size: 10pt; font-family: Verdana,Geneva,sans-serif'>
<p>Hi Marco,</p>
<p>I agree. WebP would be interesting. It could potentially replace both png and jpeg - if encoding and decoding is fast and if filesize can compete. The good thing of WebP compared with JPEG is that it supports transparency. According to your brief study, it seems to score well regarding file size, but not so well performance wise - correct? The performance that you measure - is this about time to create the files - right? What about opening and rendering on the client? That's the other side of the medal.</p>
<p>Does qt support WebP?</p>
<p>Regarding your blog post: can you perhaps better explain what <span>PNG_JPEG</span> means? A PNG as a container with JPEG compression inside? Or what is it?</p>
<p>Regarding tif: could you share your creation parameters? In my experience tiff performs much better than what you experience (both in file size and speed) if you use proper compression and creation parameters. E.g. you can use JPEG compression inside tiff and then you should have more or less the same file size as with jpeg. tiff is just the container, but there are thousand of combinations of creation options that have a very, very significant impact on perfomance and file size.</p>
<p>Thanks,</p>
<p>Andreas</p>
<p id="reply-intro">On 2020-06-09 13:26, Matthias Kuhn wrote:</p>
<blockquote type="cite" style="padding: 0 0.4em; border-left: #1010ff 2px solid; margin: 0">
<div id="replybody1">
<div>
<p>Hi all,</p>
<p>At OPENGIS.ch we have recently looked into different raster formats. The results can be read here: <a class="v1moz-txt-link-freetext" href="https://www.opengis.ch/2020/06/09/offline-wms-benchmarking-raster-formats-for-qfield/" target="_blank" rel="noopener noreferrer">https://www.opengis.ch/2020/06/09/offline-wms-benchmarking-raster-formats-for-qfield/</a></p>
<p>Not that surprising, but one of the interesting findings was that webp is very efficient. Low filesize, reasonable rendering performance, support for transparency. In short, it has all the potential for being used as default transport format for WM(T)S.</p>
<p>Looking at our server implementation, this format is not supported. Did someone ever think about or even look into that?</p>
<p>Regards</p>
<div class="v1moz-signature">-- <br />
<div class="v1moz-signature">
<div class="v1moz-signature"><span style="text-align: left; color: #000000; font-family: 'Verdana', sans-serif; font-size: 10pt;">Matthias Kuhn</span><br /><a href="mailto:matthias@opengis.ch" rel="noreferrer"> <span style="text-align: left; color: #000000; font-family: 'Verdana', sans-serif; font-size: 8pt;">matthias@opengis.ch</span> </a><br /><span style="text-align: left; color: #000000; font-family: 'Verdana', sans-serif; font-size: 8pt;"><a href="tel:+41764356763" target="_blank" rel="noopener noreferrer">+41 (0)76 435 67 63</a></span><br />
<div><a href="http://www.opengis.ch" target="_blank" rel="noopener noreferrer"> <img src="cid:15917032705edf76e6be50a637552294@carto.net" alt="OPENGIS.ch Logo" width="200" height="80" /></a></div>
</div>
</div>
</div>
</div>
</div>
<br />
<div class="pre" style="margin: 0; padding: 0; font-family: monospace">_______________________________________________<br />QGIS-Developer mailing list<br /><a href="mailto:QGIS-Developer@lists.osgeo.org">QGIS-Developer@lists.osgeo.org</a><br />List info: <a href="https://lists.osgeo.org/mailman/listinfo/qgis-developer" target="_blank" rel="noopener noreferrer">https://lists.osgeo.org/mailman/listinfo/qgis-developer</a><br />Unsubscribe: <a href="https://lists.osgeo.org/mailman/listinfo/qgis-developer" target="_blank" rel="noopener noreferrer">https://lists.osgeo.org/mailman/listinfo/qgis-developer</a></div>
</blockquote>
<p><br /></p>
</body></html>