> I believe that I used http url directly after reading some QGIS tutorial
> that suggested that /vsicurl/ is no more needed.
Depends on use cases. If you need to process the whole file and that it can
fit in RAM, then direct http[s:]// without /vsicurl might be slightly faster.
> You are right
statistics with gdal_edit.
-Jukka-
-Alkuperäinen viesti-
Lähettäjä: Even Rouault
Lähetetty: keskiviikko 8. tammikuuta 2020 19.44
Vastaanottaja: gdal-dev@lists.osgeo.org
Kopio: Vincent Sarago ; Rahkonen Jukka (MML)
Aihe: Re: [gdal-dev] Faster gdalinfo from COG
On mercredi 8 janvier 2020
On mercredi 8 janvier 2020 12:27:56 CET Vincent Sarago wrote:
> Hi Jukka,
> The time you are seeing is related to your configuration and not
> specifically to the file itself.
>
> If you set `GDAL_DISABLE_READDIR_ON_OPEN=EMPTY_DIR` in your env, you’ll see
> that gdalinfo will be much faster.
The
Hi Jukka,
The time you are seeing is related to your configuration and not specifically
to the file itself.
If you set `GDAL_DISABLE_READDIR_ON_OPEN=EMPTY_DIR` in your env, you’ll see
that gdalinfo will be much faster.
```
$ time GDAL_DISABLE_READDIR_ON_OPEN=EMPTY_DIR gdalinfo
/vsicurl/http:
Hi,
Cloud optimized GeoTIFF is rather fast for almost anything else but not for
checking what it is with gdalinfo. I wonder if we could have some "summary
only" mode in gdalinfo that reads just what is known to be fast to read from
the image metadata. What gdalinfo is actually doing when it spe
