Hi all,
I am encountering an issue when applying terrain correction (range-Doppler) to S1 scenes around northern Greenland using the Copernicus 90m DEM (same for 30m though). I’ve noticed it when switching the DEM for operational processing of S1 scenes from GETASSE30 to Copernicus 90m. What’s really confusing is that some scenes process just fine, but others fail mid-process with this error message:
Cannot invoke "java.awt.image.Raster.getDataBuffer()" because "tile" is null
and succinctly:
Error: no product reader for band \'null\'
The issue appears to be independent from:
- input band
- output resolution
- output map projection
Mask out areas without elevationoption- SNAP Desktop or via graph processing tool
gpt - overall scene size
- processing resources (limited to 16 threads and 16GB of RAM on my machine)
When I say this happens only for northern Greenland I need to specify: I only know for sure for all scenes covering the Arctic and Antarctic, as this is what is processed on a daily routine. No clear geographical pattern emerges when looking at what scenes fail and which do not. The amount of intersection with land does not seem to matter. Repeat-passes however do seem to all be affected (tested only one time). The terrain-correction with GETASSE30 works just fine. Creating a merged tif from the downloaded Copernicus tiles and passing it via external DEM option also works.
I would dislike going back to GETASSE on these scenes now that I’ve seen the accuracy that the Copernicus DEMs bring along. Also I am stumped by the very specific conditions of this - do you have an idea on what could be the issue?
An example scene that does not work: S1C_EW_GRDM_1SDH_20250525T202405_20250525T202505_002492_005321_764B.SAFE.zip
An example scene that does work (close-by): S1C_EW_GRDM_1SDH_20250525T121628_20250525T121728_002487_005303_F1FA.SAFE.zip