Do you know if that’s possible to enter this option (UTM / WGS 84 (Automatic) inside the xml graph?
For now I’m locked with lat/long. (the xml have to be generic)
please try this one:
<mapProjection>AUTO:42001</mapProjection>
1 Like
Perfect! Thank you!
@ABraun do you know aswell if there is a way to let the Terrain-Correction choose automatically the minimal resolution from source ?
< pixelSpacingInMeter>AUTO< /pixelSpacingInMeter>
< pixelSpacingInDegree>AUTO< /pixelSpacingInDegree>
If not possible, in other way, to fix the resolution in meters and find the corresponding degree?
(I know that’s according to the latitude and makes it delicate…)
I’m not sure, but if I had to guess, I would just remove these lines and have SNAP set the value automatically.
Some parameters are mandatory, the others can be skipped
I would love it, but using:
< pixelSpacingInMeter/>
< pixelSpacingInDegree/>
< mapProjection>AUTO:42001</mapProjection>
leads to:
Error: [NodeId: Terrain-Correction] Operator ‘RangeDopplerGeocodingOp’: Value for ‘Pixel Spacing (m)’ must be of type ‘double’.
and even:
< pixelSpacingInMeter>10< /pixelSpacingInMeter>
< pixelSpacingInDegree/>
< mapProjection>AUTO:42001< /mapProjection>
Error: [NodeId: Terrain-Correction] Operator ‘RangeDopplerGeocodingOp’: Value for ‘Pixel Spacing (deg)’ must be of type ‘double’.
Maybe it works when you insert 0.0
< pixelSpacingInMeter>0.0</pixelSpacingInMeter>
< pixelSpacingInDegree>0.0</pixelSpacingInDegree>
< mapProjection>AUTO:42001</mapProjection>
3 Likes
That works!!
Thanks a lot for this tips!
Could be good to move it in a new topic
good idea 