read_ibtracs_netcdf: fix for tracks crossing antimeridian#168
Merged
Conversation
Loading
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Usually, if an agency reports about a track that crosses the antimeridian, the longitude is always chosen positive within IBTrACS. However, it can happen that the TC crosses the antimeridian according to one agency, but not according to another. When mixing agency data, this can yield inconsistent sign changes in longitude. When using the
interpolate_missingoption, this will lead to wrong interpolated values.According to my analysis, this only affects a single storm in IBTrACS with the default settings: 2013224N12220. However, you never know what might change in the future in IBTrACS. Furthermore, this PR also makes sure that no longitude values are less than -180 (which can happen for some agencies).