-
Notifications
You must be signed in to change notification settings - Fork 6
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
Interpolation with NaN's, no overshoot and robustness #19
Comments
This should also be written to guarantee that interpolated values remain within the extrema of the source data. When this issue is being addressed it'll be a good idea to change the tolerances in test_interpolation_tsunami as indicated in the FIXME. |
Also observed this traceback (for the Kampung Bali data set). It was not reproducible, but hints at the need for more robust interpolation. Traceback:
Exception Type: error at /api/v1/calculate/ |
Write unit test using HOT data to reproduce this problem. |
Saw the same error today with the full HOT OSM dataset. |
…message than that mentioned in issue #19
Wrapped underlying interpolation function in try-except to provide a better error message: |
Updated code everywhere to use NaN internally for missing values: All 84 tests pass. |
…er necessary after issue #19 has been done
I think we can remove the dependency on scipy for now, but not game to just do it without having a fresh installation to test it on. |
…ple of tests. This should close ticket #19
Could close this now, except for a few minor outstanding issues: These have been moved to three new tickets: #165, #166, #167 |
Implement and test 2D interpolation where some numbers are NaN (IEEE Not-a-Number).
Apply this in the context of ASCII grids where NODATA of -9999 gets replaced by NaN.
The text was updated successfully, but these errors were encountered: