Hello,
Since 1 week ago, I encounter a Terrain-Correction error when running a GPT chain (orthorectifying complex or GRD images) with several sensors:
- S1
- CSK, CSG
- TDX, TSX, PAZ
- RS2
- RCM
- ICEYE
- SAOCOM
The error I get is:
Error: [NodeId: Terrain-Correction] Operator 'RangeDopplerGeocodingOp': Unknown element 'outputComplex'
My terrain correction step is:
<node id="Terrain-Correction">
<operator>Terrain-Correction</operator>
<sources>
<sourceProduct refid="LinearToFromdB"/>
</sources>
<parameters class="com.bc.ceres.binding.dom.XppDomElement">
<sourceBands/>
<demName>${dem_name}</demName>
<externalDEMFile>${dem_path}</externalDEMFile>
<externalDEMNoDataValue>0.0</externalDEMNoDataValue>
<externalDEMApplyEGM>true</externalDEMApplyEGM>
<demResamplingMethod>BILINEAR_INTERPOLATION</demResamplingMethod>
<imgResamplingMethod>BILINEAR_INTERPOLATION</imgResamplingMethod>
<pixelSpacingInMeter>${res_m}</pixelSpacingInMeter>
<pixelSpacingInDegree>${res_deg}</pixelSpacingInDegree>
<mapProjection>${crs}</mapProjection>
<alignToStandardGrid>false</alignToStandardGrid>
<standardGridOriginX>0.0</standardGridOriginX>
<standardGridOriginY>0.0</standardGridOriginY>
<nodataValueAtSea>true</nodataValueAtSea>
<saveDEM>false</saveDEM>
<saveLatLon>false</saveLatLon>
<saveIncidenceAngleFromEllipsoid>false</saveIncidenceAngleFromEllipsoid>
<saveLocalIncidenceAngle>false</saveLocalIncidenceAngle>
<saveProjectedLocalIncidenceAngle>false</saveProjectedLocalIncidenceAngle>
<saveSelectedSourceBand>true</saveSelectedSourceBand>
<outputComplex>false</outputComplex>
<applyRadiometricNormalization>false</applyRadiometricNormalization>
<saveSigmaNought>false</saveSigmaNought>
<saveGammaNought>false</saveGammaNought>
<saveBetaNought>false</saveBetaNought>
<incidenceAngleForSigma0>Use projected local incidence angle from DEM</incidenceAngleForSigma0>
<incidenceAngleForGamma0>Use projected local incidence angle from DEM</incidenceAngleForGamma0>
<auxFile>Latest Auxiliary File</auxFile>
<externalAuxFile/>
</parameters>
</node>
(you can find the whole chains here)
This only happens when running SNAP on Linux (in a docker), and not when running SNAP on a classic environment on Windows. Both SNAP have been updated as much as possible.
Does anyone has any clue ? Does this field has disappeared ?
Best,
Rémi