after testing some tools (CanopyModel, GroundFilter, GridMetrics, etc), it seems that none of them return an output.
I checked the available logs and they appear a bit misleading:
the one in the tool's window shows a quite complete cmd line, but I don't understand why OUTPUT it is shown as a separate one (that could also be the reason why the run doesn't end well)
the one in the "History" log, shows this pretty messy result:
processing.run("fusion:canopymodel", {'INPUT':'D:\\test\\Bourra\\2011\\LAS\\_\\bourra_tot.laz','CELLSIZE':10,'XYUNITS':0,'ZUNITS':0,'OUTPUT_DTM':'C:/Users/spono/Desktop/chm_10m.dtm','GROUND':'','MEDIAN':'','SMOOTH':'','CLASS':'','SLOPE':False,'ASCII':True,'ADVANCED_MODIFIERS':''})
I tried to run the line reported at bullet 1 directly from the CMD line and it works fine, so it seems t be an issue related to the correct call to the exe file.
Do you have any idea where the problem may lie?
I tried and could not reproduce your issue. I am producing output files.
The reason why output is separated is just how the processing interface is designed. FUSION tools works since the output is generated by the fusion commands. Could there be an issue with your paths or maybe that the laz files is not loaded correctly. However, if you got an FUSION error that should have popped up in the log-window.
The log looks ok to me. The double \ is there since windows use backslash instead of forwardslash and therefore two of them is requried.
after testing some tools (CanopyModel, GroundFilter, GridMetrics, etc), it seems that none of them return an output. I checked the available logs and they appear a bit misleading:
processing.run("fusion:canopymodel", {'INPUT':'D:\\test\\Bourra\\2011\\LAS\\_\\bourra_tot.laz','CELLSIZE':10,'XYUNITS':0,'ZUNITS':0,'OUTPUT_DTM':'C:/Users/spono/Desktop/chm_10m.dtm','GROUND':'','MEDIAN':'','SMOOTH':'','CLASS':'','SLOPE':False,'ASCII':True,'ADVANCED_MODIFIERS':''})
I tried to run the line reported at bullet 1 directly from the CMD line and it works fine, so it seems t be an issue related to the correct call to the exe file. Do you have any idea where the problem may lie?