Thanks guys for clarification!
On Wed, Sep 4, 2019, 5:53 PM Even Rouault
wrote:
> On mercredi 4 septembre 2019 17:26:14 CEST Denis Rykov wrote:
> > Thanks for quick reply, I've uploaded grib file here:
> > https://transfer.sh/5JCVX/download.grib
>
> Turns out that my guess wasn't so bad after al
On mercredi 4 septembre 2019 17:26:14 CEST Denis Rykov wrote:
> Thanks for quick reply, I've uploaded grib file here:
> https://transfer.sh/5JCVX/download.grib
Turns out that my guess wasn't so bad after all. The uncompressed file size is
3601x1801x14(bands)x8(bytes_per_pixel) = 693 MB
whereas a G
Thanks for quick reply, I've uploaded grib file here:
https://transfer.sh/5JCVX/download.grib
On Wed, Sep 4, 2019 at 5:04 PM Even Rouault
wrote:
> On mercredi 4 septembre 2019 08:50:09 CEST Sean Gillies wrote:
> > Hi Denis,
> >
> > rio-convert lacks some of the features of gdal_translate (advanc
On mercredi 4 septembre 2019 08:50:09 CEST Sean Gillies wrote:
> Hi Denis,
>
> rio-convert lacks some of the features of gdal_translate (advanced metadata
> translation, statistics, &c) and it may be that the cost of those features
> is being especially felt in the GRIB case.
For a plain gdal_tra
Hi Denis,
rio-convert lacks some of the features of gdal_translate (advanced metadata
translation, statistics, &c) and it may be that the cost of those features
is being especially felt in the GRIB case. In fact, the core of
gdal_translate has some GRIB-specific code that rasterio does not use:
ht
Why gdal_translate so slow compared to rio translate from rasterio?
rio convert:
$ time rio convert download.grib download.tif
Warning: Inside GRIB2Inventory, Message # 15
ERROR: Ran out of file reading SECT0
Warning: Inside GRIB2Inventory, Message # 15
ERROR: Ran out of file reading SECT0
rio co
