Hi,
I was recently updating the HLS tutorial to access version 2.0 and
discovered that the tutorial is no longer able to access the HLS data in
the cloud from a local Python environment. I've been trying to troubleshoot
for a couple days now with no positive results. The failure can be boiled
down
Another +1 here. As far as I understand, the only real point of the COG
driver is to be a quick way to get some sensible defaults for GeoTIFF
format, and compression is definitely one such sensible default.
Also, the COG spec's example GDAL command includes `-co COMPRESS=LZW`,
which might be anoth
I’ve compiled and used it on the aarch64 architecture on AWS Graviton2. Works
as expected and price/performance is better (as it is for pretty much
everything). Highly recommended if the rest of your code can be built for arm.
From: gdal-dev on behalf of Patrick Young
Date: Thursday, Septembe
I'd give LZW a go. I've got very good experience with that, in terms of
performance on weaker or embedded systems. However, some people still
think that the algorithm has a protection by patents.
Am 30.09.2021 um 15:46 schrieb Even Rouault:
should we enable a default compression scheme for the
Hi,
I was curious if anyone had any thoughts about GDAL and arm64. I saw that
Even had been playing with arm64 a bit
https://lists.osgeo.org/pipermail/gdal-dev/2021-July/054418.html
and AWS talks a lot about the efficiency of their Gravitron stuff. Does
anyone have thoughts about arm64 and GDA
Another option would be to emit a warning/suggestion when left unset. An
added benefit would be that folks possibly self discover that they can
control the compression scheme.
P
On Thu, Sep 30, 2021, 7:53 AM Vincent Sarago
wrote:
> +1
> I think it’s reasonable to have a default compression. In
+1
I think it’s reasonable to have a default compression. In rio-cogeo I’ve set
the default to `DEFLATE` but that’s was a personal preference.
Vincent
> On Sep 30, 2021, at 3:46 PM, Even Rouault wrote:
>
> Hi,
>
> should we enable a default compression scheme for the COG driver ? I've heard
Hi,
should we enable a default compression scheme for the COG driver ? I've
heard people "complaining" about that, or people just not realizing that
specifying a compression method was something reasonable to do. Likely a
lossless one to be conservative. ZSTD is probably not reasonable as it's
