You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Band 9 Block=614x1 Type=Float64, ColorInterp=Undefined
Description = VGRD:planetary boundary layer:anl
terminate called after throwing an instance of 'std::logic_error'
what(): basic_string::_M_construct null not valid
Aborted (core dumped)
...and our loader throws basically the same error. gdalwarp has the same issue with an attempt to copy to a GeoTIFF.
If you hide the .idx file, we can load it, and both tools also run to completion, but apparently this isn't acceptable because the band indexing is mixed up.
The issue appears to be that the .idx file contains some fractional index numbers (e.g. 8.1 and 8.2)
We are currently building with 3.4.1 but I tried a build of 3.5.3 and it fails the same way.
I thought that PR #5569 might be related but apparently not, given the above.
The text was updated successfully, but these errors were encountered:
One of our customers has some files from NOAA which are causing our GDAL-based raster loader some issues.
An example file, and associated index file:
https://nomads.ncep.noaa.gov/pub/data/nccf/com/nam/prod/nam.20221101/nam.t00z.awphys00.tm00.grib2
https://nomads.ncep.noaa.gov/pub/data/nccf/com/nam/prod/nam.20221101/nam.t00z.awphys00.tm00.grib2.idx
gdalinfo fails after a few bands with:
Band 9 Block=614x1 Type=Float64, ColorInterp=Undefined
Description = VGRD:planetary boundary layer:anl
terminate called after throwing an instance of 'std::logic_error'
what(): basic_string::_M_construct null not valid
Aborted (core dumped)
...and our loader throws basically the same error. gdalwarp has the same issue with an attempt to copy to a GeoTIFF.
If you hide the .idx file, we can load it, and both tools also run to completion, but apparently this isn't acceptable because the band indexing is mixed up.
The issue appears to be that the .idx file contains some fractional index numbers (e.g. 8.1 and 8.2)
We are currently building with 3.4.1 but I tried a build of 3.5.3 and it fails the same way.
I thought that PR #5569 might be related but apparently not, given the above.
The text was updated successfully, but these errors were encountered: