Etienne,
This workaround seems to have solved my problem, although I needed to
increase the value from 1000 to 2000 in some instances (some of the GRIB2
messages worked with 1000, others didn't).
So I am now using:
gdalwarp -wm 2000 --config GDAL_CACHEMAX 2000 -of netcdf -srcnodata
.0
I am experiencing strange behavior when reprojecting/converting a GRIB2
file to NetCDF using gdalwarp, where the resulting NetCDF file is missing
lots of data (or possibly being set incorrectly to NoData) west of a
certain longitude. However, if I instead reproject from GRIB2 to an
intermediate
You probably are experiencing a known bug, when the warping operation needs
more memory than the warp cache.
Try setting adding the following to the gdalwarp command (if it doesn't
work try a larger value).
--config GDAL_CACHEMAX 1000 -wm 1000
Also please update the ticket with any new
