SNAPHU Unwrapping


#246

you don’t need cygwin any longer when you are using snaphu 1.4.2.

Please have a look here:


#247

this is what i am getting after defining system path for snaphu1.4.2 as u told


#248

Just add the snaphu\bin folder to your system’s path variable (http://www.computerhope.com/issues/ch000549.htm) and use the window command prompt instead (https://www.howtogeek.com/235101/10-ways-to-open-the-command-prompt-in-windows-10/)


#249

in the command prompt as well the problem is same, it is unable to read the snaphu.conf file


#250

the configuration file and the exported data must be in the folder where the command is called.


#251

config. file is in same exported snaphu folder.


#252

please elaborate, sorry i didnt get u…


#253

start snaphu in exacty this folder, then it will be able to read the conf file and the exported rasters.


#254

I did as u just told but as u can see again same issue, unable to read config file


#255

your screenshot indicates that you still open snaphu in the folder F:\snaphu

You have to navigate to your directory with the exported files or open the Power Shell directly in this folder …\ab\snahpu\subset…
Go ther, hold down your shift key, right click at some empty area and select “open windows power shell here”.

It’s not that hard…


#256

ok thanks, but now it is showing this message- pixel spacings be positive


#257

good to see it technically works. The error message about the pixel spacings is strange however. Which steps did you perform before the snaphu export?


#258

subset_1_of_RS2-SLC-FQ12-DES-13-Jan-2018_00_Stack_ifg_dinsar_flt
i have subsetted my images then coregistered both, then generated interferogram, then topographic phase removal and then phase filtering.


#259

Now I´m having the opposite problem.
I increased the number of tiles and rows to 20 each and still I get the message: “tiles too small or overlap too large for given input”.



#260

plz suggest what do i do for pixel spacings to be positive?


#261

leave the number of tiles. If the number is too high, the single tiles become too small.

You can try to remove the - in the conf file at RANGERES and AZRES and run again.

I generally advise to only use VV for InSAR, there is no need to calculate the interferogram for both polarizations. It only takes the double time and introducees possible errors.


#262

leave the number of tiles. If the number is too high, the single tiles become too small.

You can try to remove the - in the conf file at RANGERES and AZRES and run again.

I generally advise to only use VV for InSAR, there is no need to calculate the interferogram for both polarizations. It only takes the double time and introducees possible errors.


#263

leave the number of tiles. If the number is too high, the single tiles become too small.

You can try to remove the - in the conf file at RANGERES and AZRES and run again.

I generally advise to only use VV for InSAR, there is no need to calculate the interferogram for both polarizations. It only takes the double time and introduces possible errors.


#264

leave the number of tiles. If the number is too high, the single tiles become too small.

You can try to remove the - in the conf file at RANGERES and AZRES and run again.

I generally advise to only use VV for InSAR, there is no need to calculate the interferogram for both polarizations. It only takes the double time and introduces possible errors.


#265

this error i am getting while trying to import snaphu.
as soon as i entered unwrapped phase .hdr image , i encountered this error. please help to resolve it