hm, in this case ASF does not host all the data takes which are available.
There’s no way to retrieve the data from NASA at a different format?
Thank you very much! I just found a file in the grd format in NASA. This should be able to be imported, but can I use the data in this format to continue to do the tomographic processing according to the steps you gave before?This data seems to have been processed with multiple views.
as long as it is complex, it is worth a try.
Thank you very much! I did the experiment with data in grd format, but according to the steps you gave before, the two data rows and column numbers are different when performing tomography. Is this a data problem? Is there any way to solve it? Looking forward to your answer!
maybe you first have to import them as Single products and use the coregistration to adjust all secondary products to the first one.
Uh, I have used “single data sets” to import every data, but I haven’t found a tool for registration, please help! thank you very much!
Hello, I imported a single data set separately and stored it in different folders. However, a new error appeared this time. What caused it?
Did you mess up the order? First import, then extract.
According to your screenshot the data lies outside the folder which you selected for extraction. Please watch out for a clean data structure.
Hello, I did not change the storage location this time, but still such an error occurred! Could you please tell me how to solve this problem?
could it be that the reason for this warning is that S2 matrix is required as input?
As you see in the screenshots of my example I extracted S2 and used the overall folder as “Main Input Directory”, noot the T3 subfolder.
Sorry, I did have a problem because I messed up the folder.I’m sorry to have caused you trouble.But now we have the problem of the number of rows and columns. What is the cause of this? I think it seems to be a problem with the data itself, don’t you? Looking forward to your reply!
Ah, this is grd data. Can you download the slc product?
I’m not very familiar with UAVSAR data to be honest, so I’m afraid I cannot give you much more advise here.
好的，那我自己再试试看，非常感谢！
Each dataset must be in a separate directory.
@ABraun You mention coregistration here. Is this happening within PolSARPro (PSP) or in SNAP? I’ve not found a coregistration tool within PSP so I’ve been trying to undertake coregistration within SNAP then export to PSP format. However, I’m not quite sure how to do this correctly. The SNAP coregistration tools produce a stack, so I’ve tried Stack Split to give separate files. But this avenue does not seem to allow for the generation of the required binaries when exporting to PSP format. When I do this, all I get is the configuration text file and no binaries.
Any suggestions on a basic Sentinel-1 workflow for ingest into PSP for tomoSAR (I know S-1 may not a suitable sensor for this task, it’s more of a trial data set)? My initial thought was this: Read > ApplyOrbitFile > RadioCal > DeBurst > Coreg > Subset. Thanks for any help
I am not sure how well PolSARpro coregisters the data to be honest. There is a “coarse coregistration” module, but as it says it is probably not accurate enough for PolInSAR approaches. All training material of PolSARpro already refers to well coregistered data products so I guess doing this before is a good idea.
If you want to coregister S1 data you apply BackGeocoding followed by ESD and then you deburst the data.
Yes, “coarse” coregistration does not sound very promising. Thank you for the suggestion. This seem to be a good workflow based on the trial run I did.
However, I’m still running into the issue of not getting the binary files I need. I’m not totally sure if this step is required, but it seems to me the co-registered stack needs to be split in order to be imported into PolSARpro. Any ideas on how this is done correctly? When I use the Stack Split tool, this does in fact split the stack as expected, but when I try to export each constituent into PolSARpro format, all I get in each exported folder is the config.txt file and no binaries.
Any thoughts? thanks
What happens when you export the entire stack into PolSARpro format?
The same thing. Only the configuration file is generated.
New developments on this however. This thread: Wrong polar-type argument in config.txt when data exported from snap was imported to PolSARpol and this paper Dual polarimetric radar vegetation index for crop growth monitoring using sentinel-1 SAR data.pdf (1014.6 KB) pretty much solves the issue.
1 Like