New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Geocode creates temp files but never completes it's process #191
Comments
Hi @TheJeran thanks for reaching out. Can you please run geocode(infile=check, outdir='test2', test=True) This will only create the workflow but not execute it.
This way you can get all the SNAP command line info and perhaps some insight into what is going on. |
Thanks for the response John. I ran that code and it exported a S1B__IW___A_20190403T020824_Cal_NR_Orb_ML_TF_TC_dB_proc.xml file. I don't know if this is the expected behavior or if it was supposed to be 'workflow.xml' My docker doesn't have a gpt funtion so
is the outcome. This lack of gpt functionality could be the cause? |
No no, from pyroSAR.examine import ExamineSnap
print(ExamineSnap().gpt) |
|
Okay so it found the /opt/snap/bin/gpt S1B__IW___A_20190403T020824_Cal_NR_Orb_ML_TF_TC_dB_proc.xml Or this: export PATH=$PATH:/opt/snap/bin
gpt S1B__IW___A_20190403T020824_Cal_NR_Orb_ML_TF_TC_dB_proc.xml |
Wonderful John! So it does seem to be a connection error and the connections time out. I checked the URLs in my browser and they throw me a 404. Any ideas? This is a SNAP thing right? |
This particular tile does not exist because this is an ocean area. The westernmost tile on that latitude is N44W125.SRTMGL1.hgt.zip. geocode(infile=check, outdir='test2', terrainFlattening=False) |
It's still trying to download the same files. :/
|
Actually, just do this: geocode(infile=check, outdir='test2', terrainFlattening=False, demName='GETASSE30') This GETASSE30 DEM is completely global, i.e., also has tiles over ocean. It's resolution is really low but this doesn't matter in your case. |
I just tried myself with this scene. Apologies, it is of course mostly over land and terrain flattening is a good idea.
If you are behind a proxy and SNAP cannot download those files then I don't have a workaround. However, the times I have observed SNAP having problems with this it did at least write a message saying it is not able to download. Are you sure the process hangs or is it just taking a long time to do anything (because of limited hardware resources)? |
I think it may be a proxy issue since I can access those URLs through the browser. I'll look into it. Do you know where these files get stored to? if in the worst case scenario I can download them manually. |
Some of the tiles you cannot download manually because they don't exist. There are no tiles over ocean. You can however create a custom DEM mosaic and pass that to See here for some more details about DEM handling in pyroSAR: https://pyrosar.readthedocs.io/en/latest/general/DEM.html |
I realize this is a different issue John. But I'm doin a local test on my Windows laptop to make sure its a proxy issue, but I can't seem to get pyroSAR to recognize my SNAP install in the PATH variable. Any idea how to solve this error for windows?
It's confusing since it can wget the files but not downloading them via gpt. |
Like it says in the message. Add the SNAP directory to the PATH environment variable. |
the PATH variable is for paths only, not executables. |
I figured. But that didn't seem to work, since the error message mentioned the executables I tried those as well to no avail. Does pyroSAR require a specific version? should snap64 work? |
Okay that's strange. The method pyroSAR.examine.ExamineSnap.__identify_snap checks whether the following exist:
Can you please check whether all these conditions are met? |
Oh yes, a never dying love. Do I know this Felix? import os
for path in os.environ.get('PATH').split(os.pathsep):
print(path) Also, please have a look at the file |
Ah of course, this Felix. I just didn't see the connection between him and you. Where do you know each other from? |
sigh if only it were that simple. Still the same after restart. Felix is at my institute and was the one who suggested pyroSAR, which should solve my sentinel-1 problems whenever iI can get it to function. I know another project I worked on earlier is probably going to start using Sentinel-1 data in the near future so would be good to get this working somewhere. I'll see what our session today yields. |
Okay so that is beyond the scope of pyroSAR then. You will have to find a way of how to get the path |
I am closing this because there hasn't been an update in several months. Feel free to reopen any time. |
Linux
Anaconda Docker env
'0.15.1' from conda
geocode(infile=check, outdir='test2')
none it just never ends. I think it's a SNAP issue actually but have not the knowledge to figure out what exactly.
The text was updated successfully, but these errors were encountered: