I tried exceptionnaly the spliy-merge option for a project.
I am using ODM natively install on my Windows 10 machine.
All seems to work fine until I received an error pop-up for each submodel explaning that there are no defined app for opening “gdal_proximity.py” file. After verification it is the case on my machine no program was associated with the .py file format.
Checking the code we have: run('gdal_proximity.py "%s" "%s" -values %s' % (geotiff_path, output_path, nodata))
So this is why it ask for a default program, adding the program could solve this issue I guess: run('python gdal_proximity.py "%s" "%s" -values %s' % (geotiff_path, output_path, nodata))
Furthermore if we use the default programe we have no guaranty that it will be a compatible python version, it could be python 2.
Should we not provide it the path to “our” python version embedded by ODM ?
Hey @bernarde, thanks for reporting this. It sounds like a bug. On Windows calling python gdal_proximity.py should choose the Python version needed by ODM automatically (if called within the ODM environment).
Have you tried editing the commands.py file to see if it works?
Ok, I have to confess that I did not try to modify it but add python as my default program for py file, my bad.
What I was reporting is that the call to run does not call python but directly the py file.
If what you said is correct (i.e. calling python necessarily calls the ODM version) then whe only need to add python to the run call.