Incoherence with GCPs in BurstExtraction and SARDeburst application
Description
An incoherence is present with GCPs after extracting a burst from a S1 IW products.
GCPs in v8 API, are composed of GCP
elt (with cartesian coordinates and L/C index) and GCPTimes
. After a burst extraction, number of GCP
elts and GCPTimes
do not match anymore.
BurstExtraction
in SarSensorModel removes some GCPs in order to keep only GCPs which are inside the current burst. This operation was not applied on SARParam.GCPTimes
. It may have an impact on projection because GCPs are used to in SarSensorModel
.
NB : SARDeburst application has the same problem
Steps to reproduce
- Apply
SARBurstExtraction
on a given S1 IW product - Display
GCP
andGCPTimes
metadata.
For instance :
time otbApplicationLauncherCommandLine SARBurstExtraction -in ../../S1A_IW_SLC__1SDV_20171107T025348_20171107T025415_019153_02069A_D2C6.SAFE/measurement/s1a-iw3-slc-vv-20171107t025348-20171107t025413-0
19153-02069a-006.tiff -burstindex 4 -out out_burst_extract_v8.tiff -allpixels true
# Result : 210
gdalinfo out_burst_extract_0_v8.tiff | grep -in "GCPTimes" | wc -l
# Result : SAR.GCP.number=42
gdalinfo out_burst_extract_0_v8.tiff | grep -in "GCP.number"
Configuration information
OS centos 7.9 (HAL), OTB release-8.0
Edited by Gaëlle USSEGLIO