satpy icon indicating copy to clipboard operation
satpy copied to clipboard

Reading S3 data fails with Satpy 0.59.0

Open pnuu opened this issue 1 month ago • 1 comments

Describe the bug Reading of data on S3 object storage fails with Satpy 0.59.0.

To Reproduce

import hdf5plugin
from satpy import Scene

fname = "s3://satellite-data-eumetcast-geo-mtg-0deg-fci/W_XX-EUMETSAT-Darmstadt,IMG+SAT,MTI1+FCI-1C-RRAD-FDHSI-FD--CHK-BODY--DIS-NC4E_C_EUMT_20251208124049_IDPFI_OPE_20251208123908_20251208123923_N_JLS_O_0076_0040.nc"
scn = Scene(filenames=[fname], reader="fci_l1c_nc")

Naturally, the S3 URI needs to be changed to one that the user has access to.

Expected behavior No error message shown and reading the data works.

Actual results

[Errno 2] No such file or directory: 'satellite-data-eumetcast-geo-mtg-0deg-fci/W_XX-EUMETSAT-Darmstadt,IMG+SAT,MTI1+FCI-1C-RRAD-FDHSI-FD--CHK-BODY--DIS-NC4E_C_EUMT_20251208124049_IDPFI_OPE_20251208123908_20251208123923_N_JLS_O_0076_0040.nc'

Note that the protocol s3:// has been removed.

Screenshots

Environment Info:

  • OS: Linux
  • Satpy Version: 0.59.0

Additional context I've tracked the failure to commit 5e762d2fe116f98bb9f25175ac16014ed4d5a84c originating from https://github.com/pytroll/satpy/pull/3256

pnuu avatar Dec 08 '25 13:12 pnuu

The actual crash was caused by something else. The error message coming from the first engine to be tested just confused me. The actual cause is mystery, but it wasn't caused by the NetCDF4 engine change. I'll inspect more before closing.

pnuu avatar Dec 08 '25 13:12 pnuu