-
Notifications
You must be signed in to change notification settings - Fork 175
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
unable to open 'SRTM_NE_250m.tif' ul[0]: unbound variable #50
Comments
I am running into the same problem on OSX (Unix based.) Where would your suggested code be inserted? I manually performed the proposed changes and then ran:
And it produced the same error. I changed the file extension from .tif to .TIF and then ran:
and it worked. So, two problems I think. 1) File is in a subdirectory and 2) file has a lowercase extension. |
Thanks for the followup question. I put the code in The code I suggested might also not be targeting the correct directory for running within the docker image. It may need to be targeting
So this would be the entire
@kovar-ursa As for why you needed upper case .TIF instead of lower case .tif, I'm not sure. Is it possible that when you ran |
I am trying to run the docker image as specified in the documentation. The docker create-dataset.sh script works fine and downloads the tif files. It runs into issues when it tries to run the create-tiles.sh script. I get the error below.
I am almost certain this issue is because the download and use of the
unar
command results in three folders that contain the .tif files.The files have a path like this.
SRTM_NE_250m_TIF/SRTM_NE_250m.tif
But the script expects a path like this
./SRTM_NE_250m.tif
Which results in the unbound variable error seen above.
On Unix based systems, I believe the following code would fix the issue.
I'm running Ubuntu 20.04
Docker version 20.10.7, build 20.10.7-0ubuntu1~20.04.2
To reproduce this issue run the following commands (Exactly as specified in the documentation)
The text was updated successfully, but these errors were encountered: