-
Notifications
You must be signed in to change notification settings - Fork 5
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
GDAL raster calculator RuntimeWarnings
#39
Comments
After checking and fixing #29, this is not because of it. It is because of raster not able to store the resultant value which is large enough. Possible solutions:
More details: |
@DaveEslinger @NSPECT do you remember what we settled for as a solution for this one? |
I believe we were going to test doing a conversion before accumulation on these variables as well. I think it will be similar to what you did to correct the units on erosion, but we need to go from mg to kg, to 10^6 instead of 10^3. Also, if there is already a conversion at the end, we'll need to drop that. Note: My comments are about the pollutants. I suspect your previous unit correction will have fixed the erosion issue. |
After investigating, it turns out that this is not an overflow issue but GDAL/NUMPY calculation issue. #61 is also caused by GDAL/NUMPY calculation. The raster values are nowhere close to overflow limit for A temporary fix has been put in place in 97ae3f1 that may or may not work for a different test area. A ticket has been filed with GDAL OSGeo/gdal#5609 Alternative tools were considered, like the QGIS processing raster calculator, but the idea was dropped because several bugs exist in the QGIS repo for the QGIS processing raster calculator. It is important to note that these messages are warnings, and doesn't seem to impact results |
RuntimeWarnings
during runoff calculations
RuntimeWarnings
during runoff calculationsRuntimeWarnings
Tested results of GDAL calculator with and without warnings and they are exactly the same. Thus changing the label from bug to warnings. |
@DaveEslinger when you get a chance can you please confirm if you are consistently getting this warning message at the same place in erosion modules for different test datasets. |
With a small 99x100 cell (cell size 30 m) artificial data set, I do NOT get the error at all. I do get an error about no NODATA values to fill. Note that I think I'm not really using good R-Factor values here since I'm getting 9,745 kg/year of soil from one 30x30m cell. That seems a lot. With real data for Hawaii and Puerto Rico I DO get the error, consistently at the same spot. I'm getting new data to test later. With HI data, get error here: FOR PUERTO RICO DATA error occurs same spot: WITH ARTIFICAL DATA, NO ERROR: |
The runoff calculations here cause runtime errors.
https://github.com/Dewberry/QNSPECT/blob/fbff1a01a10e5e40d58d71b3c8c8302b032b6cbe/algorithms/run_analysis/Runoff_Volume.py#L138
This might be because of #29
The text was updated successfully, but these errors were encountered: