Time interpolation of directional data - avoid interpolating over 360-0.
Open
bug
- Dominant language
- Python
- Stars
- 56
- Forks
- 9
- Avg merge
- 57m
- Merged PRs (30d)
- 3
Description
Currently, when working with directional data, there is not stopping from interpolating over 360-0 jump, which could lead to some wrong comparisons. One way to handle this would be to convert both obs and model to x- and y-components upon interpolation. For now a check could be made to ensure no interpolation is going on.
Contributor guide
Assessment
This issue has not been assessed yet.