Re: [PROJ] LIBERTIFF / Thread-safe TIFF reader
Even Rouault via gdal-dev <[email protected]> Fri, 20 Dec 2024 23:56:30 +0100
| Newsgroups | gmane.comp.gis.gdal.devel,gmane.comp.gis.proj-4.devel |
|---|---|
| Message-ID | <[email protected]> |
This is a multi-part message in MIME format.
--===============1324841676100592559==
Content-Type: multipart/alternative;
boundary="------------nqL5Gl2c0bow08aX97RfeSpt"
Content-Language: en-US
This is a multi-part message in MIME format.
--------------nqL5Gl2c0bow08aX97RfeSpt
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Le 20/12/2024 à 22:13, Kurt Schwehr via PROJ a écrit :
> In the long shot department...
>
> If you had to pick just one compressor, why not zstd? Yeah, I know
> that most things out there are deflate, but if we could break from
> that, would it make for a smaller faster world?
Besides reprocessing all of our existing grids,
https://github.com/geotiffjs/geotiff.js/tree/master/src/compression
seems to show that it doesn't support ZSTD, which would break at least
our wonderful cdn.proj.org interactive map
--
http://www.spatialys.com
My software is free, but my time generally not.
Butcher of all kinds of standards, open or closed formats. At the end, this is just about bytes.
Mood of the day: "Bien entendu, on peut sauter sur sa chaise comme un cabri en disant : les standards ! les standards ! les standards ! Mais ça n’aboutit à rien et ça ne signifie rien." ~ dixit De Gaulle
--------------nqL5Gl2c0bow08aX97RfeSpt
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 8bit
<!DOCTYPE html>
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<p><br>
</p>
<div class="moz-cite-prefix">Le 20/12/2024 à 22:13, Kurt Schwehr via
PROJ a écrit :<br>
</div>
<blockquote type="cite"
cite="mid:CACmBxyvFhxiKF7GjUSWZqJuncRooMHEOcP3Jz3WV6F5RMrXG_w@mail.gmail.com">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<div dir="ltr">In the long shot department...
<div><br>
</div>
<div>If you had to pick just one compressor, why not zstd? Yeah,
I know that most things out there are deflate, but if we could
break from that, would it make for a smaller faster world?</div>
</div>
</blockquote>
<p>Besides reprocessing all of our existing grids,
<a class="moz-txt-link-freetext" href="https://github.com/geotiffjs/geotiff.js/tree/master/src/compression">https://github.com/geotiffjs/geotiff.js/tree/master/src/compression</a>
seems to show that it doesn't support ZSTD, which would break at
least our wonderful cdn.proj.org interactive map</p>
<span style="white-space: pre-wrap">
</span>
<pre class="moz-signature" cols="72">--
<a class="moz-txt-link-freetext" href="http://www.spatialys.com">http://www.spatialys.com</a>
My software is free, but my time generally not.
Butcher of all kinds of standards, open or closed formats. At the end, this is just about bytes.
Mood of the day: "Bien entendu, on peut sauter sur sa chaise comme un cabri en disant : les standards ! les standards ! les standards ! Mais ça n’aboutit à rien et ça ne signifie rien." ~ dixit De Gaulle</pre>
</body>
</html>
--------------nqL5Gl2c0bow08aX97RfeSpt--
--===============1324841676100592559==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
_______________________________________________
gdal-dev mailing list
[email protected]
https://lists.osgeo.org/mailman/listinfo/gdal-dev
--===============1324841676100592559==--