Bug #1198

shift_topo does not work correctly for Sentinel-1

Added by Eric 7 months ago.

Status:NewStart date:2018-02-14
Priority:NormalDue date:
Assignee:-% Done:

0%

Category:-Estimated time:0.10 hour
Target version:-
Affected version:5.4.x-svn Platform:

Description

I've noticed that in the example files for Sentinel-1 data, shift_topo is always set to zero, while it is set to 1 for the other satellites. If I set this to 1 for Sentinel, it will cause the rest of the processing chain to fail because topo_shift.grd is created with the wrong dimensions in intf_tops.csh. If this step of the processing is not required for TOPS data, it should be removed from intf_tops entirely to prevent this error.

OFFSET_TOPO - START
 range decimation is: 4
file dimensions do not match (must have same width)
OFFSET_TOPO - END

Also available in: Atom PDF