Error in terrain-correction results around 180deg longitude

Hi SNAP developers,

I am processing S1-A/B data covering the Ross Sea area in Antarctica. My processing graph is simple (see attached graph file) - the workflow is as follows:

Apply-Orbit-File -> Terrain-Correction -> Convert-Datatype -> Write

I am using a standard polar stereographic projection. The resulting images have an obvious fault along the 180deg longitude line - a ribbon of missing (zero) data. For example

S1A_EW_GRDM_1SDH_20190316T112545_20190316T112654_026362_02F2E4_62F9.zip

The raw S1 data does not have this fault. So it appears to be the terrain-correction process that is introducing the error. I have tested this in snap versions 7.0 and 8.0.

Any help in resolving this problem would be gratefully appreciated.

Regards,
Glenn.

sen2img_single.xml (4.2 KB)

Which DEM is used for the terrain correction? Maybe the gap is introduced by its resampling (you could try nearest neighbor)?
Is the “mask areas without elevation” option unchecked?

It’s an old issue with terrain correction and has not been fixed yet. The issue is tracked by ticket https://senbox.atlassian.net/browse/SITBX-647

Thank you for your reply @jun_lu and the link to the issue tracker.

I am somewhat dismayed that this is an old problem that has yet to be fixed.

I raised the priority of this issue to the highest category as it is indeed time to fix it.

The problem has been fixed. Please give it a try and let us know if the issue still persists.

Thank you @jun_lu for promptly attending to this issue. How do I test your fix? Do I have to wait for the next release?

You have to wait for the next release. Or if your SNAP is built from source, you can update your source code and build SNAP again. The fix should be there.

The latest release contains the fix - s1tbx v8.0.1 - and produces the correct result …

Many thanks for your help. A good start to the new year.

2 Likes