I’m currently working with the NDR module of the Invest model, and I’ve encountered an issue. While the model runs smoothly through all the steps and doesn’t show any errors, the output folder does not appear in the results directory after the simulation finishes. Additionally, no other expected output files are generated.
Here are the steps I’ve already checked:
Verified that the input data formats and file paths are correct.
Reviewed the log files, and no obvious errors were found.
The model does not seem to terminate unexpectedly or with any errors.
Despite everything appearing to run normally, the output folder is not generated, and I’m unsure if I missed a specific setting or configuration that could be causing this.
I would appreciate any help or advice from others who have used the NDR module. Thanks in advance!
I have uploaded the logfile as requested. After reviewing it again, I still haven’t found any clear indications of what might be causing the issue with the missing output folder.
Could you please help me investigate further? Is there anything specific in the model setup or configuration that I might be missing?
I appreciate any advice or guidance you can provide.
HI @zxl , thank you for sharing your logfile. From the log, I can see that InVEST is interpreting your output workspace to be: E:/a大论文/2035现有情景水质净化
Thank you for your response and for pointing out the folder name issue.
I have upgraded to the latest version of the InVEST Workbench as you recommended, but unfortunately, I’m still encountering the same problem after running the model again. The output folder is still not being generated, and the issue persists.
I have attached the new logfile from the latest version for your review. Could you please help me identify what might be causing this issue despite the update?
Hi @zxl , thank you for updating InVEST and posting your logfile again. The log now indicates an error that could be helpful.
Do you know if you have an environment variable called PROJ_LIB defined on your system? Or one called PROJ_DATA?
At a Windows CMD prompt, could you type: set PROJ_LIB
and set PROJ_DATA
This will tell you if either of these are defined. And if one or both are defined, but point to a location that does not contain a proj.db file, then this would explain the error. It can be resolved by removing the environment variable(s). Though if you remove the variable, you may wish to remember the value so you can reset it again if you wish. Other software besides InVEST might be expecting it to be present.
These variables could have become defined if you have another installation of GDAL on your system besides the one that comes with InVEST. I think in the future we can include a fix to InVEST to avoid this problem altogether.
If you can, please try this development version of the Workbench. I believe it may solve the problem described in my previous post, without requiring you to modify any of the environment variables on your system.