| 26 May 2015 10:20 AM |
|
|
Hello everyone,
I am performing PS Interferometry analysis on a stack of Cosmo-Skymmed Images.
When reaching the Geocoding step, the PS Map (.shp and .kml files) is properly generated providing the information I'm interested in. However, I have checked the Make Geocoded Raster flag in order to obtain the displacement velocity map as a raster, and It has not been created ( note I have also unchecked the Create Geocoded Shape).
And, by the way, is it possible to make the PS map less dense? It has consumed a lot of computing time. Only by increasing the coherence threshold the number of points can be reduced?
Thanks,
Santiago
|
|
|
|
Deleted User
Basic Member
Posts:228  
| 26 May 2015 11:53 AM |
|
|
Which version of SARscape are you using? Is it the latest version, which is 5.1.2? Also, are you using SARscape from the main ENVI interface, or from ENVI Classic? This information will help us track down whether you might be experiencing a known bug related to this behavior.
- Peg
Exelis VIS
|
|
|
|
Deleted User
New Member
Posts: 
| 26 May 2015 01:17 PM |
|
|
Hello,
I am using version 5.1.1. I am executing Sarscape from the main ENVI interface, not the Classic one.
Thanks,
Santago
|
|
|
|
Deleted User
Basic Member
Posts:228
| 27 May 2015 12:21 PM |
|
|
There is a but that we've recently discovered in SARscape 5.1 that results in the output raster _VD file (vertical displacement) being overwritten by the output raster _SD (slope displacement) if they are both chosen as output. So, to get the vertical displacement file, you will want to run the Geocoding step twice. The first time you will choose only the vertical displacement as output. Then you will want to rename the output raster (*_SD) to *_VD. Then you can run the Geocoding step again, choosing only the slope displacement as output.
This problem should be resolved in the upcoming release of SARscape 5.2, which we expect later this summer.
- Peg
Exelis VIS
|
|
|
|
Deleted User
New Member
Posts:
| 28 May 2015 06:29 AM |
|
|
Thanks a lot, this has worked.
And as for the PS map, by increasing the coherence threshold as you suggested, Sarscape was able to finish the geocoding much faster (it was a highly coherent area, within 5 km2 I had 30 million points using a threshold of 0.75!!)
Regards,
Santiago
|
|
|
|
Deleted User
New Member
Posts:
| 17 Jun 2015 03:17 AM |
|
|
Hello,
I have a new doubt regarding PS Geocoding outputs.
I have processed my stack with a Coher. Thr. of 0.85, but the resulting point cloud and geocoded velocity raster do not seem to be consistent. I have merged the shapefiles into a single file and I can see that the points with coherence > 0.85 cover a larger area than the geocoded Velocity map.Is this ok, or the Velocity map should cover more o less the same area than the point cloud?
I've made a screenshot of both the point cloud and velocity map, they can be downloaded from here :
https://www.dropbox.com/s/gv09caczq9f3hil/PS_85.zip?dl=01
Thanks,
Santiago
|
|
|
|