Output name errors when saving SNAP files for PyRate

I have tried that and can give you a list of steps needed to make the Pyrate workflow running:

  1. Export the unwrapped phase dim-files with coherence as GAMMA FOR PYRATE file
  2. Export the used DEM in a separate file as GAMMA file
    !It is very important that all files have the same raster extent (same no of rows & cols)!
  3. Change the coherence file name endings, so that Pyrate recognizes the dates (e.g. 20201209-20201221.coh)
  4. open the elevation header file (e.g. elevation.par) and change or insert the following variables:
  • replace variable name ‘range_samples’ with ‘width’
  • replace variable name ‘azimuth_lines’ with ‘nlines’
  • insert variables ‘corner_lat’, ‘corner_lon’, ‘post_lat’ and ‘post_lon’
  • and enter the fitting parameters accordingly: y_origin, x_origin, y_resolution and x_resolution
  • enter information about the geodetic datum. example from pyrate:

‘ellipsoid_name: WGS 84\n’,
‘ellipsoid_ra: 6378137.000 m\n’,
‘ellipsoid_reciprocal_flattening: 298.2572236\n’,
‘\n’,
‘datum_name: WGS 1984\n’,
‘datum_shift_dx: 0.000 m\n’,
‘datum_shift_dy: 0.000 m\n’,
‘datum_shift_dz: 0.000 m\n’,
‘datum_scale_m: 0.00000e+00\n’,
‘datum_rotation_alpha: 0.00000e+00 arc-sec\n’,
‘datum_rotation_beta: 0.00000e+00 arc-sec\n’,
‘datum_rotation_gamma: 0.00000e+00 arc-sec\n’,
‘datum_country_list Global Definition, WGS84, World\n’

  1. adjust the parameters & the used files in ifgs.txt, … accordingly in the pyrate configuration file ‘input_parameters.conf’.

I cannot guarantee, that this list is complete. I’m currently working on a script to automatize the whole process. It already works on my system and I can generate some nice results. However, it still needs some debugging…

3 Likes