Hello!
I’m trying to build a storwater retention model for the city of São Paulo, but I’m getting very strange results. Mainly in places where there are rivers, the retention and runoff values return absurdly large values. But I can’t figure out what I’m doing wrong.
In the attached folder you can find the material I used and the results I got:
https://drive.google.com/drive/folders/1PpjUDdxWIBanZUM8orxRmCm_K02TYvKd?usp=sharing
If anyone knows what I might be doing wrong, I’d appreciate it =)
Hello, I just posted about this issue.
"Hello, users and developers.
I am using the Urban Stormwater Retention model for my project. For the past few months, I have been noticing an error in the retention volume and runoff output. The error appears with multiple lines displaying extremely large values, which are then translated as #inf (infinity). I noticed that, for a moment, the values are classified as very large numbers, but then they are converted to #inf in versions 3.14.02 and 3.14.03.
After running a new test on version 3.14.0 of InVEST, this error disappeared, and the values were computed correctly for both volume data columns. For example, in the newer versions, the value 34.5698777… (the real value, which appears in version 3.14.0) was displayed as 345,698,777,123,258,555,789 (#inf). It seems to be an issue related to decimal place identification. I hope this information helps.
I suggest that users of this model revert to version 3.14.0 to avoid this issue until a possible fix is provided for the newer versions of InVEST.
If I can provide any further information, feel free to contact me at anievaz@gmail.com or stephanievaz@usp.br."
Good luck!
Hi @Stephanie_Vaz and @nathalia.schmuziger,
Thank you both for reporting this issue and for sharing your data! I believe I’ve determined the cause and will let you know when this gets fixed. In the meantime, yes, I believe InVEST 3.14.0 should give you the correct results.
Hi @Stephanie_Vaz and @nathalia.schmuziger,
Wanted to let you both know that this bug has been addressed in the latest InVEST release, 3.15.0 Thanks again for reporting this issue.