Sentinel 1 corregistration


#1

Hi,
I’m having a problem with sentinel 1 tops corregistration. When I perform the corregistration it produces 2 virtual bands (because I choose only vv). So, with the first band ist all ok, but with the slave band no image is set. Nothings appears in the screen. Can any one help me with tis?

Best Regards

Luis Leitão


#2

If the slave image consists of NoData, the coregistration failed. This can have several reasons

  • the images are of different tracks/orbits.
  • The bursts you selected in the TOPS Split operator do not overlap.
  • not enough GCPs were found.

Can you list the full names of the products and tell us what processing steps you undertook before the TOPS coregistration?


#3

Hi ABraun

These are the two images. They are from the same track.

S1A_IW_SLC__1SDV_20171215T183538_20171215T183606_019717_021841_2AE4
S1A_IW_SLC__1SDV_20171203T183539_20171203T183606_019542_0212CD_73D8

Is it possible that the problem is caused by the orbit files?
I think that SNAP (in my pc) does not apply the orbit files. I’ve tested to open these two files, after applying the orbit files in SNAP, in PCI Geomática 2018 (trial version) and it says that no orbit files were found.

Best Regards


#4

there are some problems reported regarding orbit files lately in the SNAP forum as well. Could be a reason, yes.


#5

Is it possible to insert orbit file manualy?


#6

yes, you can download them here (https://qc.sentinel1.eo.esa.int/) and place them in this folder
user folder/.snap/auxdata/orbits (there should be already some)