-
Notifications
You must be signed in to change notification settings - Fork 95
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
focal3D is not computing correct values #1057
Comments
I understand why you think it is wrong but the values on the right side are correct, I think. Your data are global lon/lat, so you need to consider that the right-most column is adjacent to the left-most column. So the low values in the fist column affects to results. This is not the case with any other crs.
But you were of course right that the
|
Hi Robert, Thank you very much for your quick response. I understood that the calculation was correct. Regarding the argument na.policy = "omit", I got another error when simulating a raster cell with NA.
|
Fixed. Thanks again! |
Dear Robert,
When applying the focal3D function, I noticed that the values on the right end (east side) of the raster are lower than they should be. Also, when using na.policy = "omit", it is returning an error even though there are no NAs in the raster.
I would appreciate it if you could help.
Here is an example code:
The text was updated successfully, but these errors were encountered: